EXTENDING THE REACH AND EFFECTIVENESS OF HEADER COMPRESSION IN ACCESS NETWORKS USING SDN

• US 20140169158A1
• Filed: 12/17/2012
• Published: 06/19/2014
• Est. Priority Date: 12/17/2012
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Mishra, Ramesh, Subrahmaniam, Ramesh, Manghirmalani, Ravi
• Granted Patent: US 9,246,847 B2
• Time in Patent Office: Days
• US Class Current: 370/228
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 49/3009 Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

A method is executed by a controller in a software defined network to conserve bandwidth over the software defined networking (SDN) network by compressing Internet protocol (IP) headers of data packets traversing the SDN network. The IP headers of the data packets remain compressed as the data packets traverse the SDN network. The ingress switch is an entry point for the data packets as the data packets traverse the SDN network. The egress switch is an exit point for the data packets as the data packets traverse the SDN network. The method includes configuring a flow table of the ingress switch to forward the data packets to a header compressor module in the ingress switch, configuring the ingress switch to instantiate the header compressor module, and configuring a group table of the ingress switch to manage forwarding of the data packets toward the egress switch.

Claims

1. A method executed by a controller in a software defined network (SDN) to conserve bandwidth over the SDN network by compressing Internet protocol (IP) headers of data packets traversing the SDN network, where the controller implements a control plane of the SDN network, where the SDN network includes a plurality of switches implementing a data plane of the SDN network, and where the IP headers of the data packets remain compressed as the data packets travers the plurality of switches between an ingress switch and an egress switch in the plurality of switches, the ingress switch being an entry point for the data packets as the data packets traverse the SDN network, the egress switch being an exit point for the data packets as the data packets traverse the SDN network, the method comprising the steps of:

configuring a flow table of the ingress switch to forward the data packets to a header compressor module in the ingress switch;

configuring the ingress switch to instantiate the header compressor module; and

configuring a group table of the ingress switch to manage forwarding of the data packets toward the egress switch.

2. The method of claim 1, further comprising the step of:

configuring a receive thread for the header compression module to receive the data packets from the flow table of the ingress switch.

3. The method of claim 1, further comprising the step of:

configuring a transmit thread for the header compression module to transmit the data packets after compression to the group table.

4. The method of claim 1, wherein configuring the group table further comprises the step of:

calculating a data flow to destination switch identifier flow mapping; and

writing the mapping to the group table of the ingress switch.

5. The method of claim 1, wherein configuring the group table further comprises the steps of:

calculating a shortest path between each ingress switch and egress switch pair;

creating a group identifier for each egress switch for the ingress switch; and

writing the group identifier and a push egress switch label action as an entry in the group table.

6. The method of claim 1, further comprising the step of:

configuring intermediate switches between the egress switch and ingress switch with a flow table entry to match an ether type and incoming label and perform a swap label action for a next hop toward the egress switch.

7. The method of claim 1, further comprising the step of:

configuring the egress switch to pop the incoming label and forward data packets to a header decompressor module in the egress switch.

8. The method of claim 1, further comprising the steps of:

receiving notice of a link failure;

identifying each path carrying compressed data packets that traverse the software defined network and includes the link failure;

calculating an alternative path traversing the software defined network for each path carrying compressed data packets that traverses the link failure;

configuring all switches along the alternate path to enable forwarding of the data packets along the alternate path.

9. A network element to execute a controller in a software defined networking (SDN) network to conserve bandwidth over the SDN network by compressing Internet protocol (IP) headers of data packets traversing the SDN network, where the controller implements a control plane of the SDN network, where the SDN network includes a plurality of switches implementing a data plane of the SDN network, and where the IP headers of the data packets remain compressed as the data packets traverse the plurality of switches between an ingress switch and an egress switch in the plurality of switches, the ingress switch being an entry point for the data packets as the data packets traverse the SDN network, the egress switch being an exit point for the data packets as the data packets traverse the SDN network, the network element comprising:

a set of ingress ports configured to receive data from the plurality of switches;

a set of egress ports configured to transmit data to the plurality of switches, and

a network processor coupled to the set of ingress ports and egress ports, the network processor configured to execute a switch configuration module, the switch configuration module to configure a flow a flow table of the ingress switch to forward the data packets to a header compressor module in the ingress switch, to configure the ingress switch to instantiate the header compressor module, and to configure a group table of the ingress switch to manage forwarding of the data packets toward the egress switch.

10. The network element of claim 9, wherein the switch configuration module is further configured to create a receive thread for the header compression module to receive the data packets from the flow table of the ingress switch.

11. The network element of claim 9, wherein the switch configuration module is further configured to create a transmit thread for the header compression module to transmit the data packets after compression to the group table.

12. The network element of claim 9, wherein the switch configuration module is further configured to calculate a data flow to destination switch identifier flow mapping, and to write the mapping to the group table of the ingress switch.

13. The network element of claim 9, wherein the switch configuration module is further configured to obtain a shortest path between each ingress switch and egress switch pair from a shortest path module, to create a group identifier for each egress switch for the ingress switch, and to write the group identifier and a push egress switch label action as an entry in the group table.

14. The network element of claim 9, wherein the switch configuration module is further configured to configure intermediate switches between the egress switch and ingress switch with a flow table entry to match an ether type and incoming label and perform a swap label action for a next hop toward the egress switch.

15. The network element of claim 9, wherein the switch configuration module is further configured to configure the egress switch to pop the incoming label and forward data packets to a header decompressor module in the egress switch.

16. The network element of claim 9, wherein the switch configuration module is further configured to receive notice of a link failure, to identify each path carrying compressed data packets that traverse the software defined network and includes the link failure, to calculate an alternative path traversing the software defined network for each path carrying compressed data packets that traverses the link failure, to configuring all switches along the alternate path to enable forwarding of the data packets along the alternate path.

17. A method executed by a switch in a software defined networking (SDN) network to conserve bandwidth in the SDN network by compressing Internet protocol (IP) headers of data packets traversing the SDN network, where a controller implements a control plane of the SDN network, where the SDN network includes a plurality of switches implementing a data plane of the SDN network, and where the IP headers of the data packets remain compressed as the data packets traverse the plurality of switches between an ingress switch and an egress switch in the plurality of switches, the ingress switch being an entry point for the data packets as the data packets traverse the SDN network, the egress switch being an exit point for the data packets as the data packets traverse the SDN network, the method comprising the steps of:

receiving a data packet at the switch on an ingress port of the switch;

matching the data packet in a flow table pipeline by a destination and type of the data packet;

forwarding a matched data packet to a header compression module or header decompression module executed by a processing unit in the switch that is external to a flow table pipeline; and

executing a compression or decompression of the data packet by the processing unit.

18. The method of claim 17, further comprising the steps of:

forwarding the data packet to the group table of the flow table pipeline.

19. The method of claim 17, further comprising the step of:

setting a group identifier of the data packet to a destination switch identifier.

20. The method of claim 17, further comprising the step of:

setting the type of the data packet to multi-protocol label switching reachability.

21. The method of claim 17, further comprising the step of:

matching the data packet after compression by a group identifier and type defined in a flow table entry; and

executing defined actions of the flow table entry to prepare the data packet to be forwarded toward destination.

22. A network element to execute as a switch in a software defined networking (SDN) to conserve bandwidth over the SDN network by compressing Internet protocol (IP) headers of data packets traversing the SDN network, where a controller implements a control plane of the SDN network, where the SDN network includes a plurality of switches implementing a data plane of the SDN network, and where the IP headers of the data packets remain compressed as the data packets traverse the plurality of switches between an ingress switch and an egress switch in the plurality of switches, the ingress switch being an entry point for the data packets as the data packets traverse the SDN network, the egress switch being an exit point for the data packets as the data packets traverse the SDN network, the network element comprising:

an ingress port configured to receive a data packet at the switch;

a flow table pipeline configured to match the data packet by a destination and type of the data packet, and to forward a matched data packet to a header compression module or header decompression module

a processing unit configured to execute the header compression module or decompression module, where the processing unit is external to a flow table pipeline, the header compression module or decompression module to execute a compression or decompression of the data packet.

23. The network element of claim 22, wherein the processing unit is further configured to forward the data packet to the group table of the flow table pipeline.

24. The network element of claim 22, wherein the flow table pipeline is further configured to set a group identifier of the data packet to a destination switch identifier.

25. The network element of claim 22, wherein the flow able pipeline is further configured to set the type of the data packet to multi-protocol label switching reachability.

26. The network element of claim 22, wherein the flow table pipeline is further configured to match the data packet after compression by a group identifier and type defined in a flow table entry, and to execute defined actions of the flow table entry to prepare the data packet to be forwarded toward destination.