IP packet version converting apparatus and method

• US 20050068981A1
• Filed: 09/09/2004
• Published: 03/31/2005
• Est. Priority Date: 09/25/2003
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Park, Soo-hong, Kim, Young-keun, Kim, Pyung-soo, Kim, Sun-woo
• Granted Patent: US 7,474,675 B2
• Time in Patent Office: Days
• US Class Current: 370/466
• 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/166 IP fragmentation; TCP segmentation
• CPC Class Codes: H04L 69/167 Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 translation of Internet protocol [IP] addresses H04L61/2503
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

An IP packet version converting apparatus and method, the IP packet header converting method includes recognizing one of fields of a header of an IP packet of a first type, in which a value regarding an expansion function is recorded, the expansion function being incompatible between the IP packet of the first type and an IP packet of a second type; and converting the field recognized in one of the fields of the header of the IP packet into a field compatible with the IP packet of the second type.

Claims

1. An IP packet header converting method comprising:

recognizing one of a plurality of fields of a header of an IP packet of a first type, in which a value regarding an expansion function is recorded, the expansion function being incompatible between the IP packet of the first type and an IP packet of a second type; and

converting the recognized one of the plurality of fields into a field compatible with the IP packet of the second type.

2. The IP packet header converting method of claim 1, further comprising:

checking the plurality of fields of the header of the IP packet of the first type,

wherein if the value indicating that the expansion function attached to the IP packet of the first type is recorded in another one of the plurality of fields of the header of the IP packet of the first type, the recognized one of the plurality of fields in which the value regarding the expansion function is recorded is recognized the header of the IP packet of the first type using the value indicating that the expansion function is attached to the IP packet of the first type.

3. The IP packet header converting method of claim 1, further comprising:

converting another one of the plurality of fields of the header of the IP packet of the first type, in which a value regarding a basic function is recorded, into a field compatible with the IP packet of the second type, the basic function being compatible between the IP packets of the first and second types.

4. The IP packet header converting method of claim 3, further comprising:

generating a header of an IP packet of the second type that includes the fields obtained in converting the field recognized in the header of the IP packet of the first type and the field compatible with the IP packet of the second type.

5. The IP packet header converting method of claim 1, wherein the IP packet of the first type is an IPv4 packet, the IP packet of the second type is an IPv6 packet, and the IP packets of the first and second types are convertible from one to the other using a stateless IP/ICMP transistor (SIIT) defined in Request for Comments (RFC) 2765.

6. The IP packet header converting method of claim 5, wherein in recognizing one of the plurality of fields of the header of the IP packet of the first type, if the value indicating that the expansion function is attached to the IPv4 packet is recorded in a header length field of a header of the IPv4 packet, another field of the header of the IPv4 packet, in which the value regarding the expansion function is recorded, is recognized.

7. The IP packet header converting method of claim 5, wherein in recognizing one of the plurality of fields of the header of the IP packet of the first type, if a value indicating that a security function, which is a type of the expansion function, is attached to the IPv4 packet is recorded in a first bit of a flag field of the header of the IPv4 packet, an upper bit of a fragment offset field of the header of the IPv4 packet, in which a value regarding the security function is recorded, and converting the field recognized in the header of the IP packet of the first type, the upper bit of the fragment offset field of the header of the IPv4 packet is converted into an upper bit of a flow label field of a header of an IPv6 packet.

8. The IP packet header converting method of claim 1, wherein the IP packet of the first type is an IPv6 packet, the IP packet of the second type is an IPv4 packet, and the IP packets of the first and second types are convertible from one to the other using a stateless IP/ICMP transistor (SIIT) defined in Request for Comments (RFC) 2765.

9. The IP packet header converting method of claim 8, wherein in recognizing one of the plurality of fields of the header of the IP packet of the first type, if a value indicating an expansion header, in which the value regarding the expansion function is recorded, is recorded in a next header field of the header of the IPv6 packet, the next header field of the header of the IPv6 packet is recognized.

10. An IP packet version converting method comprising:

converting one of a plurality of fields of a header of an IP packet of a first type, in which a value regarding an expansion function is recorded, into a field of a header of an IP packet of a second type, the expansion function being incompatible between the IP packet of the first type and the packet of the second type; and

generating a payload of an IP packet of the second type including data written in a payload of the IP packet of the first type.

11. The IP packet version converting method of claim 10, wherein in the conversion of one of the plurality of fields of the header of the IP packet of the first type, if a value indicating that the expansion function attached to the IP packet of the first type is recorded in another one of the fields of the header of the IP packet of the first type, the field, in which the value regarding the expansion function is recorded, is recognized using the value indicating that the expansion function is attached to the IP packet of the first type, and the recognized field is converted into a field compatible with the IP packet of the second type, and a header of the IP packet of the second type including the field, into which the recognized field of the header of the IP packet of the first type is converted, is generated.

12. The IP packet version converting method of claim 10, wherein in the generation of the payload of the IP packet of the second type, if a value regarding the length of a payload of the IP packet of the first type is recorded in another one of the plurality of fields of the header of the IP packet of the first type, the payload of the IP packet of the first type is recognized using the value regarding the length of the payload of the IP packet of the first type, and a payload of an IP packet of the second type including data recorded in the recognized payload is generated.

13. The IP packet version converting method of claim 10, further comprising:

checking a version of a predetermined IP packet,

wherein in the conversion of one of the plurality of fields of the header of the IP packet of the first type, a header of the predetermined IP packet, which is identified by an IP packet of the first type, is converted into a header compatible with an IP packet of the second type.

14. The IP packet version converting method of claim 10 further comprising:

generating an IP packet of the second type including the header generated in the conversion of one of the plurality of fields of the header of the IP packet of the first type and the payload generated in the generation of the payload of the IP packet of the second type.

15. The IP packet version converting method of claim 10, wherein the IP packet of the first type is an IPv4 packet, the IP packet of the second type is an IPv6 packet, and the IP packets of the first and second types are convertible from one to the other using a stateless IP/ICMP transistor (SIIT) defined in Request for Comments (RFC) 2765.

16. The IP packet version converting method of claim 10, wherein the IP packet of the first type is an IPv6 packet, the IP packet of the second type is an IPv4 packet, and the IP packets of the first and second types are convertible from one to the other using a stateless IP/ICMP transistor (SIIT) defined in Request for Comments (RFC) 2765.

17. A computer-readable recording medium, on which a program enabling an IP packet header converting method is recorded, the IP packet header converting method comprising:

recognizing one of a plurality of fields of a header of an IP packet of a first type, in which a value regarding an expansion function is recorded, the expansion function being incompatible between the IP packet of the first type and an IP packet of a second type; and

converting the field recognized in one of the plurality of fields of the header of the IP packet of the first type into a field compatible with the IP packet of the second type.

18. A computer-readable recording medium, on which a program enabling an IP packet version converting method is recorded, the IP packet version converting method comprising:

converting one of a plurality of fields of a header of an IP packet of a first type, in which a value regarding an expansion function is recorded, into a field of a header of an IP packet of a second type, the expansion function being incompatible between the IP packets of the first and second types; and

generating a payload of an IP packet of the second type including data written in a payload of the IP packet of the first type.