Datagram identifier management

• US 7,924,881 B2
• Filed: 05/15/2006
• Issued: 04/12/2011
• Est. Priority Date: 04/10/2006
• Status: Expired due to Fees

• Current Assignee: Rateze Remote Mgmt. L.L.C. (Intellectual Ventures LLC)
• Original Assignee: Rateze Remote Mgmt. L.L.C. (Intellectual Ventures LLC)
• Inventors: Sharma, Rochak, Ludwig, Thomas Earl, Baughman, Samuel K., Hull, Richard W., Witchey, Nicholas J., Frank, Charles William, Adams, Mark, Khan, Adnan
• Primary Examiner(s): Sheikh; Ayaz R
• Assistant Examiner(s): Weidner; Timothy J
• Application Number:
  US11/435,239
• Publication Number:
  US 20070237157A1
• Time in Patent Office: 1,793 Days
• Field of Search: None
• US Class Current: 370/474
• CPC Class Codes: H04L 1/0079 Formats for control data H04L1/16 takes precedence; training sequences H04L25/00 and H04L27/00
• CPC Class Codes: H04L 43/0894 Packet rate
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/166 IP fragmentation; TCP segmentation
• CPC Class Codes: H04L 69/167 Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 translation of Internet protocol [IP] addresses H04L61/2503
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Systems and methods ensure that datagrams retain integrity in light of the problems associated with the internetworking protocol'"'"'s use of datagram identifiers drawn from a first pool of datagram identifiers. The methods involve controlling the use of datagram identifiers to ensure that only certain identifiers are allowable. A second pool of datagram identifiers is created that is different from the first pool. A datagram identifier is drawn from the second pool and assigned to a datagram in a manner that the datagram identifier is controlled from being reused during the lifetime of the datagram. In alternative embodiments the number of available datagram identifiers is either increased through optional header fields, or reduced through tracking allowed datagram identifiers. A first host notifies a second host of an allowed identifier. The second host uses the allowed identifier as a datagram identifier.

Claims

1. A method comprising:

selecting, by a first host device, a datagram identifier from a list of available datagram identifiers;

placing, by the first host device, the datagram identifier in a list of unavailable datagram identifiers;

transmitting, by the first host device, a datagram request to a second host device over a communication link, the datagram request including the datagram identifier;

receiving, by the first host device, a datagram response from the second host device including the datagram identifier to identify a datagram, the datagram response further including a fragment of the datagram;

removing, by the first host device, the datagram identifier from the list of unavailable datagram identifiers based at least in part on receipt of the datagram; and

placing, by the first host device, the datagram identifier in the list of available datagram identifiers based at least in part on said removing.

2. The method of claim 1, further comprising:

generating, by the first host device, the datagram request in a manner such that the datagram identifier is included in a payload of the datagram request.

3. The method of claim 1, wherein the datagram identifier does not identify a datagram transmitted by the first host device.

4. The method of claim 1, further comprising:

receiving a plurality of datagram responses including a corresponding plurality of fragments of the datagram;

assembling the plurality of fragments into the datagram; and

removing the datagram identifier from the list of unavailable datagram identifiers and placing the datagram identifier in the list of available datagram identifiers based at least in part on said assembling.

5. The method of claim 1, further comprising:

determining a timeout event associated with another datagram identifier in the list of unavailable datagram identifiers; and

removing the another datagram identifier from the list of unavailable datagram identifiers and placing the another datagram identifier in the list of available datagram identifiers based at least in part on said determining of the timeout event.

6. A computing device comprising:

a controller configured

to select a datagram identifier from a list of available datagram identifiers;

to place the datagram identifier in a list of unavailable datagram identifiers;

to generate a datagram request including the datagram identifier;

to remove the datagram identifier from the list of unavailable datagram identifiers based at least in part on receipt of a datagram to which the datagram identifier is associated; and

to place the datagram identifier in the list of available datagram identifiers when the datagram identifier is removed from the list of unavailable datagram identifiers; and

a transceiver coupled to the controller and configured

to transmit the datagram request to another computing device via a communication link; and

to receive a datagram response, which includes the datagram identifier and a fragment of the datagram, from the another computing device via the communication link.

7. The computing device of claim 6, wherein the controller is configured to generate the datagram request in a manner such that the datagram identifier is included in a payload of the datagram request.

8. The computing device of claim 6, wherein the datagram identifier does not identify a datagram transmitted by the computing device.

9. The computing device of claim 6, wherein the controller is further configured to:

assemble a plurality of fragments, including the fragment, into the datagram; and

remove the datagram identifier from the list of unavailable datagram identifiers based at least further in part on a successful assembly of the datagram.