Method and apparatus for communicating using labeled data packets in a network

• US 7,212,527 B2
• Filed: 05/09/2001
• Issued: 05/01/2007
• Est. Priority Date: 05/09/2001
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Minturn, Dave B., Shah, Hemal V.
• Primary Examiner(s): Pham; Chi
• Assistant Examiner(s): LY, ANH VU H
• Application Number:
  US09/852,433
• Publication Number:
  US 20020191600A1
• Time in Patent Office: 2,183 Days
• Field of Search: 370/389, 370/392, 370/395.3, 370/395.32, 370/400, 370/401, 370/471, 370/474, 370/475, 709/201, 709/203, 709/217, 709/227, 709/228
• US Class Current: 370/389
• 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/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/165 Combined use of TCP and UDP protocols; selection criteria therefor
• CPC Class Codes: H04L 69/169 Special adaptations of TCP, UDP or IP for interworking of IP based networks with other networks protocols for interworking, protocol conversion H04L69/08
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and apparatus for transmitting data packets between a client and a server comprising, a network node receiving a data packet from a client; determining whether an identity (hereafter session id) exists for a communication session with the client. The network node transmits the data packet to a server if no session id exists. The server generates the session id, and transmits the session id to the network node. The network node transmits subsequent data packets received from the client to the server along with the session id. The server transmits subsequent data packets to the network node along with the session id. The network node removes at least the session id prior to transmitting the data packets to the client.

Claims

1. A method comprising:

receiving a data packet from source;

determining whether a session identity exists for a commmmunication session with the source;

encapsulating the received data packet in a flow header including at least two of a flow message type field, a flow option field, a source port identity field, a destination identity field and a session identity field;

transmitting the flow header with the received data packet to a destination if no session identity exists;

receiving the session identity from the destination using the flow header; and

transmitting subsequent data packets received from the source along with the session identity to the destination.

2. The method of claim 1 wherein determining whether a session identity exists for a communication session with the source comprises:

obtaining address information from the data packet; and

searching a table using the address information for the session identity.

3. The method of claim 2 wherein searching a table using the address information for the session identity comprises:

using the address information in a hash function to obtain a hash value; and

using the hash value to find the session identity.

4. The method of claim 1 further comprising:

removing a header prior to transmitting data packets received from the destination to the source; and

using information in the header to transmit data packets received from the destination to the source.

5. The method of claim 4 wherein the information in the header comprises the source port identity.

6. The method of claim 1 wherein transmitting subsequent data packets received from the source along with the session identity to the destination comprises:

adding a header including at least one of a flow message type field, a flow option field, a source port identity field, a destination identity field, and a session identity field; and

not transmitting at least part of address information in the received subsequent data packets to the destination.

7. A method comprising:

receiving a data packet from a source through a network node;

determining whether a session identity exists for a communication session with the source;

in response to the data packet, encapsulating another data packet in

a flow header including at least two of a flow message type field, a flow option field, a source port identity field, a destination identity field and a session identity field;

generating a session identity of no session identity exists; and

transmitting the flow header including the encapsulated another data packet to communicate the session identity to the network node.

8. The method of claim 7 wherein determining whether a session identity exists for a communication session with the source comprises:

obtaining the session identity from the data packet if one is included in the data packet;

obtaining address information of the network node; and

transmitting data to the network node using the address information.

9. The method of claim 8 wherein obtaining address information of the network node using the session identity comprises using the session identity as a pointer to the network node'"'"'s address information.

10. The method of claim 8 wherein transmitting data to the network node using the address information comprises not transmitting at least part of the source'"'"'s address information in the received data packet.

11. An article of manufacture comprising:

a computer-readable medium including instructions that, when executed by a computer, causes the computer to perform operations comprising;

receiving a data packet from a source;

determining whether a session identity exists for a communication session with the source;

encapsulating the received data packet in a flow header including at least two of a flow message type field, a flow option field, a source port identity field, a destination identity field and a session identity field;

transmitting the flow header with the received data packet to a destination if no session identity exists;

receiving the session identity from the destination using the flow header; and

transmitting subsequent data packets received from the source along with the session identity to the destination.

12. An article of manufacture as in claim 11 wherein instructions for determining whether a session identity exists for a communication session with the source comprises further instructions for:

obtaining address information from the data packet; and

searching a table using the address information for the session identity.

13. An article of manufacture as in claim 12 wherein instructions for searching a table using the address information for the session identity comprises further instructions for

using the address information in a hash function to obtain a hash value;

and

using the hash value to find the session identity.

14. An article of manufacture as in claim 11 comprising further instructions for removing a header prior to transmitting data packets received from the destination to the source;

and

using information in the header to transmit data packets received from the destination to the source.

15. An article of manufacture as in claim 14 wherein instructions for using information in the header to transmit data packets received from the destination to the source comprises instructions for using the source port identity to transmit data packets received from the destination to the source.

16. An article of manufacture as in claim 11 wherein instructions for transmitting subsequent data packets received from the source along with the session identity to the destination comprises further instructions for adding a header including at least one of a flow message type field, a flow option field, a source port identity field, a destination identity field, and a session identity field;

and not transmitting at least part of address information in the received subsequent data packets to the destination.

17. An article of manufacture comprising:

a computer-readable medium including instructions that, when executed by a computer, causes the computer to perform operations comprising;

receiving a data packet from a source through a network node;

determining whether a session identity exists for a communication session with the source;

in response to the received data packet, encapsulating another data packet in a flow header including at least two of a flow message type field, a flow option field, a source port identity field, a destination field and a session identity field;

generating a session identity if no session exists; and

transmitting the flow header including the encapsulated another data packet to communicate the session identity to the network node.

18. An article of manufacture as in claim 17 wherein determining whether a session identity exists for a communication session with the source comprises further instructions for:

obtaining the session identity from the data packet if one is included in the data packet;

obtaining address information of the network node; and

transmitting data to the network node using the address information.

19. An article of manufacture as in claim 18 wherein obtaining address information of the network node using the session identity comprises further instructions for using the session identity as a pointer to the network node'"'"'s address information.

20. An article of manufacture as in claim 17 wherein instructions for transmitting data to the network node using the address information comprises further instructions for not transmitting at least part of the source'"'"'s address information in the received data packet.

21. A computer system comprising:

a bus;

a data storage device coupled to said bus; and

a processor coupled to said data storage device, said processor operable to receive instructions which, when executed by the processor, cause the processor to perform a method comprising

receiving a data packet from a source;

determining whether a session identity exists for a communication session with the source;

encapsulating the received data packet in a flow header including at least two of a flow message type field, a flow option field, a source port identity field, a destination field and a session identity field;

transmitting the flow header with the received data packet to a destination if no session identity exists;

receiving the session identity from the destination using the flow header; and

transmitting subsequent data packets received from the source along with the session identity to the destination.

22. A computer system as in claim 21 wherein determining whether a session identity exists for a communication session with the source comprises:

obtaining address information from the data packet; and

searching a table using the address information for the session identity.

23. A computer system as in claim 22 wherein searching a table using the address information for the session identity comprises:

using the address information in a hash function to obtain a hash value; and

using the hash value to find the session identity.

24. A computer system as in claim 21 further comprising:

removing a header prior to transmitting data packets received from the destination to the source; and

using information in the header to transmit data packets received from the destination to the source.

25. A computer system as in claim 24 wherein the information in the header comprises the source port identity.

26. A computer system as in claim 21 wherein transmitting subsequent data packets received from the source along with the session identity to the destination comprises adding a header including at least one of a flow message type field, a flow option field, a source port identity field, a destination identity field, and a session identity field;

and not transmitting at least part of address information in the received subsequent data packets to the destination.

27. A computer system comprising:

a bus;

a data storage device couple to said bus; and

a processor couple to said data storage device, said processor operable to receive instructions which, when executed by the processor, cause the processor to perform a method comprising

receiving a data packet from a source through a network node;

determining whether a session identity exists for a communication session with the source;

in response to the received data packet, encapsulating another data packet in a flow header including at least two of a flow message type field, a flow option field, a source port identity field, a destination identity field and a session identity field;

generating a session identity if no session identity exists; and

transmitting the flow header including the encapsulated another data packet to communicate the session identity to the network node.

28. A computer system as in claim 27 wherein determining whether a session identity exists for a communication session with the source comprises:

obtaining the session identity from the data packet if one is included in the data packet;

obtaining address information of the network node using the session identity; and

transmitting data to the network node using the address information.

29. A computer system as in claim 28 wherein obtaining address information of the network node using the session identity comprises using the session identity as a pointer to the network node'"'"'s address information.

30. A computer system as in claim 28 wherein transmitting data to the network node using the address information comprises not transmitting at least part of the source'"'"'s address information in the received data packet.