Memory and processor efficient network communications protocol

• US 8,774,184 B2
• Filed: 10/13/2009
• Issued: 07/08/2014
• Est. Priority Date: 11/09/2004
• Status: Active Grant

• Current Assignee: Texas Instruments, Inc.
• Original Assignee: Texas Instruments, Inc.
• Inventors: Gupta, Sunil, Udayamurthy, Sekar, Brady, Corey, Andrews, Tanner R., Cole, David M., Milheron, Patrick M.
• Primary Examiner(s): ROBERTS, BRIAN S
• Application Number:
  US12/578,333
• Publication Number:
  US 20100027565A1
• Time in Patent Office: 1,729 Days
• Field of Search: None
• US Class Current: 370/392
• CPC Class Codes: H04L 1/0041 Arrangements at the transmitter end
• CPC Class Codes: H04L 1/0061 Error detection codes
• CPC Class Codes: H04L 1/0072 Error control for data other than payload data, e.g. control data
• CPC Class Codes: H04L 1/1841 Resequencing
• CPC Class Codes: H04L 2101/663 Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• 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

System and method for a full featured network communications protocol that is both memory and processor efficient. A preferred embodiment comprises a method for transmitting information between electronic devices, the method comprising creating a connection between a pair of electronic devices, sending a packet between the pair, acknowledging a receipt of the packet by a receiver of the packet, and dissolving the connection when it is no longer needed. The creating of the connection comprises assigning a port number to the connection at an initiating electronic device and then transmitting a connection request containing the port number to a servicing electronic device. After the transmitting, the creating further comprises receiving a second port number to the connection from the servicing electronic device.

Claims

1. A method of communicating a sequence of transmission packets, the method comprising:

communicating the transmission packets from a source device to a destination device through multiple connections that are virtual links, wherein each of the multiple connections is for communication between only a respective pair of applications executing on the source device and the destination device respectively, wherein each particular one of the transmission packets comprises a respective header and a respective data payload, and wherein the respective header includes;

an identifier field comprising data to distinguish traffic type;

a source address field comprising an address of the source device and a source port of a particular one of the multiple connections through which the particular transmission packet is communicated, wherein the source port is assigned to the particular connection from among multiple ports of the source device;

a destination address field comprising an address of the destination device and a destination port of the particular connection, wherein the destination port is assigned to the particular connection from among multiple ports of the destination device, and wherein the source port and the destination port together make the particular connection unique from another one of the multiple connections;

a payload error check code field comprising an error check for the respective data payload;

a payload size field comprising a size indicator of the respective data payload;

a hop count field comprising a count of a maximum number of routes the particular transmission packet can traverse;

a sequencing field comprising a respective value for ordering the particular transmission packet, wherein the respective value is always a sequence number of the particular transmission packet within the sequence of all transmission packets communicated from the source device to the destination device through the multiple connections; and

a header error check code field comprising an error check for the respective header.

2. The method of claim 1, wherein the respective header is a sixteen byte binary stream.

3. The method of claim 2, wherein the identifier field comprises a two byte binary stream, wherein the source address field comprises a four byte binary stream, wherein the destination address field comprises a four byte binary stream, wherein the payload error check code field comprises a two byte binary stream, wherein the payload size field comprises a one byte binary stream, wherein the hop count field comprises a one byte binary stream, wherein the sequencing field comprises a one byte binary stream, and wherein the header error check code field comprises a one byte binary stream.

4. The method of claim 1, wherein the error check in the payload error check code field comprises a cyclic redundancy code error check.

5. The method of claim 1, wherein the respective value ranges from 1 to 254.

6. The method of claim 1, wherein the respective data payload follows the respective header in the particular one of the transmission packets.

7. A system for communicating a sequence of transmission packets, the system comprising:

a source device for communicating the transmission packets to a destination device through multiple connections that are virtual links, wherein each of the multiple connections is for communication between only a respective pair of applications executing on the source device and the destination device respectively, wherein each particular one of the transmission packets comprises a respective header and a respective data payload, and wherein the respective header includes;

an identifier field comprising data to distinguish traffic type;

a source address field comprising an address of the source device and a source port of a particular one of the multiple connections through which the particular transmission packet is communicated, wherein the source port is assigned to the particular connection from among multiple ports of the source device;

a destination address field comprising an address of the destination device and a destination port of the particular connection, wherein the destination port is assigned to the particular connection from among multiple ports of the destination device, and wherein the source port and the destination port together make the particular connection unique from another one of the multiple connections;

a payload error check code field comprising an error check for the respective data payload;

a payload size field comprising a size indicator of the respective data payload;

a hop count field comprising a count of a maximum number of routes the particular transmission packet can traverse;

a sequencing field comprising a respective value for ordering the particular transmission packet, wherein the respective value is always a sequence number of the particular transmission packet within the sequence of all transmission packets communicated from the source device to the destination device through the multiple connections; and

a header error check code field comprising an error check for the respective header.

8. The system of claim 7, wherein the respective header is a sixteen byte binary stream.

9. The system of claim 8, wherein the identifier field comprises a two byte binary stream, wherein the source address field comprises a four byte binary stream, wherein the destination address field comprises a four byte binary stream, wherein the payload error check code field comprises a two byte binary stream, wherein the payload size field comprises a one byte binary stream, wherein the hop count field comprises a one byte binary stream, wherein the sequencing field comprises a one byte binary stream, and wherein the header error check code field comprises a one byte binary stream.

10. The system of claim 7, wherein the error check in the payload error check code field comprises a cyclic redundancy code error check.

11. The system of claim 7, wherein the respective value ranges from 1 to 254.

12. The system of claim 7, wherein the respective data payload follows the respective header in the particular one of the transmission packets.