US5745685A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Protocol extension in NSPP using an acknowledgment bit
Assignee: Verizon Patent and Licensing Inc
•
Filing: 1995-12-29
•
Granted: 1998-04-28
•
Expires: 2015-12-29
Abstract
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.
Inventors
- 👤 Michael Kirchner
- 👤 Sridhar Krishnaswamy
- 👤 Norman Reed
- 👤 Greg Young
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-30 13:11
CPC Classifications
H; H04; H04L; H04L1/00; H04L1/12; H04L1/16; H04L1/18; H04L1/1809; H04L1/1607; H04L1/1685; H04L9/00; H04L9/40; H04L1/1867; H04L1/188; H04L2001/0092; H04L2001/0094; H04L69/00; H04L69/30; H04L69/32; H04L69/322; H04L69/324; H04L69/326
Claims Analysis
Total Claims: 24
Claim 1
Independent Claim
139 words
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.
Claim 2
Independent Claim
139 words
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.
Claim 3
Dependent Claim
30 words
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.
Claim 4
Dependent Claim
22 words
The method according to claim 1, further comprising the step of: initializing said acknowledgment bit in said NSPP header of said packet.
Claim 5
Dependent Claim
31 words
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.
Claim 6
Dependent Claim
31 words
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.
Claim 7
Dependent Claim
24 words
The method of claim 1, further comprising the step of: turning said acknowledgment bit on or off without having to recompile said NSPP software.
Claim 8
Dependent Claim
32 words
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.
Claim 9
Independent Claim
139 words
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.
Claim 10
Independent Claim
139 words
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.
Claim 11
Dependent Claim
29 words
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.
Claim 12
Dependent Claim
21 words
A system according to claim 8, further comprising: means for initializing said acknowledgment bit in said NSPP header of said packet.
Claim 13
Dependent Claim
30 words
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.
Claim 14
Dependent Claim
30 words
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.
Claim 15
Dependent Claim
23 words
The system of claim 8, further comprising: means for turning said acknowledgment bit on or off without having to recompile said NSPP software.
Claim 16
Dependent Claim
31 words
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.
Claim 17
Dependent Claim
159 words
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.
Claim 18
Dependent Claim
159 words
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.
Claim 19
Dependent Claim
32 words
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.
Claim 20
Dependent Claim
24 words
The program storage device according to claim 15, further comprising the step of: initializing said acknowledgment bit in said NSPP header of said packet.
Claim 21
Dependent Claim
33 words
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.
Claim 22
Dependent Claim
34 words
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.
Claim 23
Dependent Claim
27 words
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.
Claim 24
Dependent Claim
35 words
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.
References Cited (Backward Citations)
US4410889A
Cited
US4654654A
Cited
EP0186343A2
Cited
US4970714A
Cited
US5245616A
Cited
EP0409578A1
Cited
US5444849A
Cited
EP0570220A2
Cited
US5519699A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2001-04-27 | 2001-10-27 | 2002-04-28 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2005-04-27 | 2005-10-27 | 2006-04-28 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2009-04-27 | 2009-10-27 | 2010-04-28 | $7700.00 | Window Closed / Lapsed |