Controlled data network error recovery
A method, a system and network nodes use an indication of possible duplicates of units, so that these units can be handled differently than other units. The unit is indicated to be a possible duplicate to the entity to which it is resent because no response was received from the entity it was sent to.
1. A method, comprising:
sending a first packet from a gateway support node to a first network entity that comprises a charging gateway function, where the first packet is comprised of a call detail record; and
in response to determining that a response is not received from the first network entity, where the response if received would indicate that the first packet was received at the first network entity, resending the first packet as a resent packet to a second network entity that also comprises a charging gateway function, where the resent packet is marked with an indication that the response was not received from the first network entity and that the resent packet is a potential duplicate of the first sent packet in the event that the first packet was actually received by the first network entity.
2. The method of claim 1 , further comprising:
one of sending a command to the second network entity to release the resent packet and send it towards a destination, or sending a command to the second network entity to cancel the resent packet and not send it towards the destination, where the destination is a billing system associated with a general packet radio service system.
3. The method of claim 1 , where the first packet is sent with a message, and where the message comprises the indication.
4. The method of claim 1 , further comprising sending an empty packet to the first network entity, where the empty packet comprises a same sequence number as the first packet.
5. A method, comprising:
receiving at a first charging gateway function a message from a gateway support node, the message comprising a call detail record;
determining if the received message comprises an indication that a response was not received by the gateway support node from a second charging gateway function when the call detail record was previously sent to the second charging gateway function, where the indication indicates that the call detail record is a potential duplicate of the previously sent call detail record in the event that the previously sent call detail record was actually received by the second charging gateway function;
in response to determining that the received message does comprise the indication, storing at least the call detail record at the first charging gateway function; and
one of receiving a command from the gateway support node to release the stored call detail record and send it towards a destination, or receiving a command from the gateway support node to cancel the stored call detail record and not send it towards the destination.
6. The method of claim 5 , where the destination is a billing system associated with a general packet radio service system.
7. An apparatus, comprising:
a memory; and
a processor connected to the memory, said processor configured to send a first packet from a gateway support node to a first network entity that comprises a charging gateway function, where the first packet is comprised of a call detail record; and
in response to determining that a response is not received from the first network entity, where the response if received would indicate that the first packet was received at the first network entity, to resend the first packet as a resent packet to a second network entity that also comprises a charging gateway function, where the resent packet is marked with an indication that the response was not received from the first network entity and that the resent packet is a potential duplicate of the first sent packet in the event that the first packet was actually received by the first network entity.
8. The apparatus of claim 7 , where said processor is further configured to one of send a command to the second network entity to release the resent packet and send it towards a destination, or to send a command to the second network entity to cancel the resent packet and not send it towards the destination, where the destination is a billing system associated with a general packet radio service system.
9. The apparatus of claim 7 , where the first packet is sent with a message, and where the message comprises the indication.
10. The apparatus of claim 7 , where said processor is further configured to send an empty packet to the first network entity, where the empty packet comprises a same sequence number as the first packet.
11. An apparatus, comprising:
a memory; and
a processor connected to the memory, said processor configured to receive at a first charging gateway function a message from a gateway support node, the message comprising a call detail record;
to determine if the received message comprises an indication that a response was not received by the gateway support node from a second charging gateway function when the call detail record was previously sent to the second charging gateway function, where the indication indicates that the call detail record is a potential duplicate of the previously sent call detail record in the event that the previously sent call detail record was actually received by the second charging gateway function;
said processor further configured, in response to determining that the received message does comprise the indication, to store at least the call detail record at the first charging gateway function; and
to one of receive a command from the gateway support node to release the stored call detail record and send it towards a destination, or to receive a command from the gateway support node to cancel the stored call detail record and not send it towards the destination.
12. The apparatus of claim 11 , where the destination is a billing system associated with a general packet radio service system.