Routing data packets in a compressed-header domain

• US 20060075134A1
• Filed: 09/30/2002
• Published: 04/06/2006
• Est. Priority Date: 09/30/2002
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Aalto, Mika, Raisainen, Vilho
• Application Number:
  US10/529,195
• Publication Number:
  US 20060075134A1
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC

Abstract

The invention concerns routing of data packets in a header-compressed domain. According to the method described, routing a data packet with a compressed header section and an uncompressed payload section comprises steps of receiving the data packet at an ingress interface, routing the data packet to an egress interface, and forwarding the data packet to the egress interface. According to this method, the compressed header section remains unchanged between the ingress interface and the egress interface. Various implementations of this method are described, including the use of the header compression context identifier (HCCID) by for routing the packets to the correct egress interface. Accordingly, a decompressor and a router are also disclosed.

Claims

1. A method for routing a data packet comprising a header section and a pay-load section, said header section comprising a compressed header section containing coded information including routing information, comprising the steps of:

receiving said data packet at an input interface

routing said data packet to an output interface

forwarding said data packet to said output interface, wherein said routing step comprises ascertaining said routing information from said compressed header section, and wherein said coded information is left unchanged in said routing and forwarding steps.

2. A method according to claim 1, wherein said ascertaining step comprises a step of reading a first header compression context identifier from said com- pressed header section.

3. A method according to claim 1, wherein said routing step comprises a step of assigning a second header compression context identifier to said data packet and a step of-replacing said first header compression context identifier by said second header compression context identifier in said data packet.

4. A method according to claim 3, wherein said second header compression context identifier is one of a predetermined set of numbers.

5. A method according to claim 3, wherein said assigning step comprises a step of looking up said second header compression context identifier in a switching table, said switching table uniquely assigning to said first header compression context identifier said second header compression identifier and one of a plurality of output interfaces.

6. A method according to claim 5, further comprising a step of maintaining said switching table.

7. A method according to claim 6, wherein said maintaining step comprises receiving and saving an incoming header compression context.

8. A method according to claim 7, wherein said maintaining step further comprises reading said first header compression context identifier and a destination address from said header compression context.

9. A method according to claim 8, wherein said maintaining step further comprises assigning one of a plurality of output interfaces to said first header compression context identifier based on a routing table, said routing table assigning said output interface to said destination address.

10. A method according to claim 9, wherein said maintaining step further comprises a step of assigning said second header compression context identifier to said first header compression context identifier.

11. A method according to claim 10, wherein said maintaining step further comprises a step of creating a new entry in said switching table for each incoming header compression context, said entry comprising said first header compression context identifier, said second header compression context identifier, and said output port.

12. A method according to claim 6, wherein said maintaining step comprises a step of erasing an entry from said switching table given a predetermined condition.

13. A method according to claim 1, comprising, before said routing step, a step of decompressing said routing information from said compressed header section.

14. A method according to claim 13 wherein said decompressing step comprises decompressing said complete compressed header section.

15. A method according to claim 13, wherein said decompressing step comprises decompressing an address of a destination network node.

16. A method according to claim 13, wherein said decompressing step comprises decompressing a service classification code element.

17. A method according to claim 13, comprising, after said decompressing step, a step of including at least a part of said decompressed header section into said data packet.

18. A method according to claim 17, wherein said part of said decompressed header is attached to said data packet in front of said header section, such that said part of said decompressed header can be forwarded before said header section.

19. A method according to claim 17, comprising, a step of removing at least a part of said decompressed header from said data packet.

20. A method according to claim 19, wherein said removing step is performed after said routing step.

21. A method according to claim 2, comprising a step of classifying said data packet according to a service class.

22. A method according to claim 21, wherein said classifying step is performed after said routing step.

23. A method according to claim 21, wherein said classifying step comprises a step of reading a service classification code element from a header compression context table.

24. A method according to claim 22, wherein said classifying step is performed before said removing step.

25. A method according to claim 19, wherein said removing step comprises removing said decompressed header data except for said service classification code element.

26. A method according to claim 21, wherein said forwarding step comprises a step of placing said data packet into one of a plurality of queues, the chosen queue corresponding to a value of said classification code point.

27. A method according to claim 25, comprising a step of removing said service classification code element before said placing step.

28. A method according to claim 1, wherein said forwarding step comprises radio or microwave transmission of said data packet.

29. A method for routing a data packet with a header section and a payload section from an originating router to a destination router through at least one intermediate router, comprising the steps of

a) at said originating router, routing said data packet to said intermediate router

b) at said originating router, compressing at least a part of said header section containing routing information

c) forwarding said data packet from said originating router to said intermediate router

d) at said intermediate router, which is communicating with said originating router through said input interface, performing a routing method according to claim 1, said output interface communicating with a next intermediate router or said destination router, respectively,

e) repeating step d) for any further intermediate router,

f) at said destination router, decompressing said compressed header section

g) at said destination router, removing said compressed header section.

30. A method according to claim 29, comprising a step of transmitting a header compression context from said originating router to said intermediate routers and to said destination router before performing the method steps of claim 29.

31. A method according to claim 30, comprising, at said originating router, a step of assigning a header compression context identifier to said header compression context, and a step of including said header compression context identifier into said compressed header section.

32. A method according to claim 31, wherein said header compression context identifier contains a network address of said originating router.

33. A decompressor device, comprising an input interface adapted to receive at least one data packet containing compressed data, a decompressing means communicating with said input interface and adapted to decompress said compressed data such that decompressed data are created based on said compressed data, and an output interface communicating with said decompressing means and adapted to provide said decompressed data of said data packet, wherein said decompressing means is adapted to selectively decompress only compressed header data contained in a header section of said data packet.

34. A decompressor device according to claim 33, wherein said decompressing means has access to a header compression context table and is adapted to decompress said compressed data using data contained in at least one predetermined section of said header compression context table, and/or using at least one predetermined mathematical decompression rule.

35. A decompressor device according to claim 33, wherein said decompressing means is adapted to decompress from said compressed header section an identifier of an external network node that is the destination of said data packet.

36. A decompressor device according to claim 35, wherein said decompressing means is adapted to decompress only said identifier of said network node that is the destination of said data packet.

37. A decompressor device according to claim 33, wherein said decompressing means is adapted to decompress said complete compressed header section of said data packet.

38. A decompressor device according to claim 33, wherein said decompressing means is adapted to decompress a service classification code element from said compressed header section.

39. A router device, comprising at least one input port adapted to receive a data packet through at least one-first communication link, and a plurality of output ports, wherein said input port comprises a decompressor according to claim 33.

40. A router device according to claim 39, wherein said input port further comprises attaching means communicating with said decompressor and adapted to attaching to said data packet data received through said output of said decompressor.

41. A router device according to claim 40, wherein said attaching means is adapted to attaching said data to said data packet in front of said header section, such that said decompressed header data can be forwarded before said header.

42. A router device according to claim 39, further comprising routing means communicating with said attaching means and with said output ports, and comprising lookup means adapted to determine, based on routing information contained in said data packet and based on information contained in a routing table, at least one destination output port, and forwarding means communicating with said routing means and adapted to forward said data packet to said determined output port.

43. A router device according to claim 42, wherein said routing means further comprises or communicates with removing means communicating with said lookup means and with said forwarding means, said removing means being adapted to remove from said data packet said decompressed data attached by said attaching means.

48. A communication network, comprising a plurality of network nodes communicating with each other through a plurality communication links, characterized in that said communication network comprises a network node with a router device according to claim 39.

49. A communication network according to claim 48, wherein at least a part of said communication links is a radio or microwave communication link.

50. A communication network according to claim 48, wherein said network nodes use an Internet Protocol as a network layer protocol.

44. A router device for routing at least one data packet with a compressed header section, comprising at least one input port adapted to receive said data packet through at least one first communication link, and a plurality of output ports, wherein said input port comprises a reading unit adapted to read a first header compression context identifier from said compressed header section, and a switching unit adapted to replace said first header compression context identifier by a second header compression identifier.

45. A router device according to claim 44, wherein said switching unit communicates with a switching table assigning to said first header compression context identifier said second header compression context identifier and at least one output port identifier.

46. A router device according to claim 45, further comprising a control unit communicating with said reading unit and said switching table, and adapted to detect a new first header compression context identifier received at said reading unit, to assign a new second header compression context identifier and an output port identifier to said first header compression context identifier, and to create at least one entry in said switching table for said identifiers, one entry for each assignment of an output port.

47. A router device according to claim 46, wherein said control unit is additionally adapted to erase said entry in said switching table given a predetermined condition.