Network transfer protocol

• US 9,515,928 B1
• Filed: 01/14/2016
• Issued: 12/06/2016
• Est. Priority Date: 07/09/2008
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Qian, Jiang
• Primary Examiner(s): Zhu, Alvin
• Application Number:
  US14/995,364
• Time in Patent Office: 327 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 1/1607 Details of the supervisory signal
• CPC Class Codes: H04L 1/1874 Buffer management
• CPC Class Codes: H04L 1/188 Time-out mechanisms
• CPC Class Codes: H04L 12/40071 Packet processing; Packet format adaptation of digital video signals for transport over a specific network H04N21/2381, H04N21/4363, H04N21/4381; packet switches H04L49/00; intermediate storage or scheduling H04L49/90
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/193 at the transport layer, e.g. TCP related
• CPC Class Codes: H04L 47/27 Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
• CPC Class Codes: H04L 61/256 NAT traversal
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 69/03 Protocol definition or specification protocol conformance testing H04L1/244
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• 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/164 Adaptation or special uses of UDP protocol
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

Systems, methods and computer program products facilitate communication on a network by transmitting a communication on the network from a first node to a second node, the communication including a first segment and a second segment. The first segment consists essentially of a destination port and a data length of the communication, and the second segment includes a payload and at least one of a connection ID, a sequence number, and an opcode. A responsive communication is then received from the second node, the responsive communication acknowledging receipt of the communication transmitted from the first node.

Claims

1. A method comprising:

transferring a file from a first node on a network to a second node on the network through a sequence of packets that establish a connection between the first node and the second node and transmit the file across the connection, wherein each of the packets of the sequence of packets that establish the connection between the first node and the second node and transmit the file across the connection includes;

a header that includes a destination port of the second node on the network and a data length of the packet,

a data segment that includes (i) a connection identifier that identifies the connection, (ii) an op code that indicates a type of the packet, and (iii) a sequence number that indicates a sequential position of the packet in the sequence of packets directed to the second node on the network,

and does not include a field for a source port or a checksum.

2. The method of claim 1, wherein each of the packets includes exactly one header at the beginning of the packet.

3. The method of claim 1, wherein the header of each of the packets consists of only (i) the destination port of the second node on the network and (ii) the data length of the packet.

4. The method of claim 1, wherein the header of each of the packets consists of only (i) two bytes for the destination port of the second node on the network and (ii) two bytes for the data length of the packet.

5. The method of claim 1, wherein the connection and another connection are established using the destination port of the second node.

6. The method of claim 1, wherein the data segment of each of the packets includes a window size field that specifies a number of bytes that a sender of the data segment is currently willing to receive.

18. The method of claim 1, wherein the type of packets include a synchronization packet that sets up the connection and a data packet that includes data that represents at least a portion of the file.

19. The method of claim 18, wherein the type of packets further include an out-of-order acknowledgement packet that indicates a packet was received out of order, a normal acknowledgement packet that indicates a packet was received in order, a delay acknowledgement packet that indicates that a packet was received after a delay and in order, and a fin packet that closes the connection.

7. A system comprising:

one or more computers; and

one or more storage devices storing instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform operations comprising;

transferring a file from a first node on a network to a second node on the network through a sequence of packets that establish a connection between the first node and the second node and transmit the file across the connection, wherein each of the packets of the sequence of packets that establish the connection between the first node and the second node and transmit the file across the connection includes;

a header that includes a destination port of the second node on the network and a data length of the packet,

a data segment that includes (i) a connection identifier that identifies the connection, (ii) an op code that indicates a type of the packet, and (iii) a sequence number that indicates a sequential position of the packet in the sequence of packets directed to the second node on the network,

and does not include a field for a source port or a checksum.

8. The system of claim 7, wherein each of the packets includes exactly one header at the beginning of the packet.

9. The system of claim 7, wherein the header of each of the packets consists of only (i) the destination port of the second node on the network and (ii) the data length of the packet.

10. The system of claim 7, wherein the header of each of the packets consists of only (i) two bytes for the destination port of the second node on the network and (ii) two bytes for the data length of the packet.

11. The system of claim 7, wherein the connection and another connection are established using the destination port of the second node.

12. The system of claim 7, wherein the data segment of each of the packets includes a window size field that specifies a number of bytes that a sender of the data segment is currently willing to receive.

13. A non-transitory computer-readable medium storing software comprising instructions executable by one or more computers which, upon such execution, cause the one or more computers to perform operations comprising:

transferring a file from a first node on a network to a second node on the network through a sequence of packets that establish a connection between the first node and the second node and transmit the file across the connection, wherein each of the packets of the sequence of packets that establish the connection between the first node and the second node and transmit the file across the connection includes;

a header that includes a destination port of the second node on the network and a data length of the packet,

a data segment that includes (i) a connection identifier that identifies the connection, (ii) an op code that indicates a type of the packet, and (iii) a sequence number that indicates a sequential position of the packet in the sequence of packets directed to the second node on the network,

and does not include a field for a source port or a checksum.

14. The medium of claim 13, wherein each of the packets includes exactly one header at the beginning of the packet.

15. The medium of claim 13, wherein the header of each of the packets consists of only (i) the destination port of the second node on the network and (ii) the data length of the packet.

16. The medium of claim 13, wherein the header consists of only (i) two bytes for the destination port of the second node on the network and (ii) two bytes for the data length of the packet.

17. The medium of claim 13, wherein the header of each of the packets consists of only (i) two bytes for the destination port of the second node on the network and (ii) two bytes for the data length of the packet.