Protocol extension in NSPP using an acknowledgment bit

• US 5,745,685 A
• Filed: 12/29/1995
• Issued: 04/28/1998
• Est. Priority Date: 12/29/1995
• Status: Expired due to Term

• Current Assignee: Shenzhen Technology Co. Ltd, Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: MCI Communications Corporation (Verizon Communications Inc.)
• Inventors: Reed, Norman, Kirchner, Michael, Krishnaswamy, Sridhar, Young, Greg
• Primary Examiner(s): Kim, Kenneth S.
• Application Number:
  US08/581,745
• Time in Patent Office: 851 Days
• Field of Search: 370/60, 370/94.1, 371/32, 371/33, 371/34, 395/200.09, 395/200.14
• US Class Current: 709/237
• CPC Class Codes: H04L 1/1685 the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
• CPC Class Codes: H04L 1/1809 Selective-repeat protocols
• CPC Class Codes: H04L 1/188 Time-out mechanisms
• CPC Class Codes: H04L 2001/0094 Bus
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/324 in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The invention provides a mechanism for acknowledging in a NSPP environment when a data packet has been received at a destination. The invention provides an Ack Bit in the NSPP header of a data packet. If acknowledgment of receipt is not received, the data packet is resent. A timer may be used to determine the length of time to wait for acknowledgment.

Claims

1. A method for acknowledging receipt of a data transfer between a client and a server in a NSPP environment, said method steps comprising:

(1) sending a packet from a source location to a destination location, wherein said packet includes an acknowledgment bit and a first sequence number stored in a NSPP header of said packet;

(2) receiving said packet at said destination location, wherein said acknowledgment bit triggers NSPP software;

(3) sending a control packet generated by said NSPP software from said destination location to said source location, wherein said control packet includes a second sequence number; and

(4) receiving said control packet at said source location and comparing said first sequence number and said second sequence number,

wherein receipt of said packet at said destination location is confirmed when said first sequence number matches said second sequence number.

2. The method according to claim 1, further comprising the step of:

resending said packet to said destination location if said first sequence number fails to match said second sequence number.

3. The method according to claim 1, further comprising the step of:

initializing said acknowledgment bit in said NSPP header of said packet.

4. The method according to claim 1, further comprising the step of:

resending said packet to said destination location if said control packet fails to be received within a specified time period.

5. The method of claim 1, further comprising the step of:

setting said acknowledgment bit with said NSPP software, wherein said acknowledgment bit is set by either the client or the server.

6. The method of claim 1, further comprising the step of:

turning said acknowledgment bit on or off without having to recompile said NSPP software.

7. The method of claim 2, further comprising the step of:

sending a further packet from said source location to said destination location prior to receiving said control packet from said destination location.

8. A system for enabling a packet to request acknowledgment of its receipt in a NSPP environment, the system comprising:

means for sending a packet from a source location to a destination location, wherein said packet includes an acknowledgment bit and a first sequence number stored in a NSPP header of said packet;

means for receiving said packet at said destination location, wherein said acknowledgment bit triggers NSPP software;

means for sending a control packet generated by said NSPP software from said destination location to said source location, wherein said control packet includes a second sequence number; and

means for receiving said control packet at said source location and comparing said first sequence number and said second sequence number,

wherein receipt of said packet at said destination location is confirmed when said first sequence number matches said second sequence number.

9. A system according to claim 8, further comprising:

means for resending said packet to said destination location if said first sequence number fails to match said second sequence number.

10. A system according to claim 8, further comprising:

means for initializing said acknowledgment bit in said NSPP header of said packet.

11. A system according to claim 8, further comprising:

means for resending said packet to said destination location if said control packet fails to be received within a specified time period.

12. The system of claim 8, further comprising:

means for setting said acknowledgment bit with said NSPP software, wherein said acknowledgment bit is set by either the client or the server.

13. The system of claim 8, further comprising:

means for turning said acknowledgment bit on or off without having to recompile said NSPP software.

14. The system of claim 9, further comprising:

means for sending a further packet from said source location to said destination location prior to receiving said control packet from said destination location.

15. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform method steps for acknowledging receipt of a data transfer between a client and a server in a NSPP environment, said method steps comprising:

(1) sending a packet from a source location to a destination location, wherein said packet includes an acknowledgment bit and a first sequence number stored in a NSPP header of said packet;

(2) receiving said packet at said destination location, wherein said acknowledgment bit triggers NSPP software;

(3) sending a control packet generated by said NSPP software from said destination location to said source location, wherein said control packet includes a second sequence number; and

(4) receiving said control packet at said source location and comparing said first sequence number and said second sequence number,

wherein receipt of said packet at said destination location is confirmed when said first sequence number matches said second sequence number.

16. The program storage device according to claim 15, further comprising the step of:

resending said packet to said destination location if said first sequence number fails to match said second sequence number.

17. The program storage device according to claim 15, further comprising the step of:

initializing said acknowledgment bit in said NSPP header of said packet.

18. The program storage device according to claim 15, further comprising the step of:

resending said packet to said destination location if said control packet fails to be received within a specified time period.

19. The program storage device according to claim 15, further comprising the step of:

setting said acknowledgment bit with said NSPP software, wherein said acknowledgment bit is set by either the client or the server.

20. The program storage device according to claim 15, further comprising the step of:

turning said acknowledgment bit on or off without having to recompile said NSPP software.

21. The program storage device according to claim 16, further comprising the step of:

sending a further packet from said source location to said destination location prior to receiving said control packet from said destination location.