NETWORK ELEMENT OF A SOFTWARE-DEFINED NETWORK

• US 20150263888A1
• Filed: 03/10/2015
• Published: 09/17/2015
• Est. Priority Date: 03/12/2014
• Status: Active Grant

• Current Assignee: Xieon Networks S.A.R.L. (Infinera Corp.)
• Original Assignee: Xieon Networks S.A.R.L. (Infinera Corp.)
• Inventors: HALLIVUORI, Ville, KUUSISAARI, Juhamatti
• Granted Patent: US 10,404,531 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 45/54 Organization of routing tables
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers

Abstract

A network element of a software-defined network comprises a data transfer interface (210) for receiving and transmitting data and a processing system (215) for constructing a software-defined data path and a fixed-functionality data path such as for example an IP/MPLS or L2 switching path. The software-defined data path comprises look-up tables for selecting software-defined actions and the fixed-functionality data path defines fixed-functionality actions. The processing system is adapted to convert metadata associated with data managed by the software-defined data path to a data format suitable for the fixed-functionality data path when one or more of the fixed-functionality actions are needed in conjunction with forwarding the data. One of the fixed-functionality actions is selected at least partly on the basis of which one of the look-up tables was most recently accessed, and the determined fixed-functionality action is carried out so as to initiate the one or more needed fixed-functionality actions.

Claims

1. A network element for a software-defined network, the network element comprising a data transfer interface for receiving and transmitting data and a processing system adapted to:

construct, in accordance with configuration data received from a controller of the software-defined network, a software-defined data path for managing first data to be forwarded, the software-defined data path comprising lookup tables for selecting software-defined actions and one or more of the software-defined actions modifying first metadata associated with the first data,

configure, in accordance with forwarding-parameter data received at the network element, a fixed-functionality data path for managing second data to be forwarded, the fixed-functionality data path defining fixed-functionality actions and one or more of the fixed-functionality actions modifying second metadata associated with the second data,

convert the first metadata associated with the first data being managed by the software-defined data path to a data format suitable for the fixed-functionality data path in response to a need to carry out one or more of the fixed-functionality actions in conjunction with forwarding the first data,

determine a first one of the fixed-functionality actions from among the fixed-functionality actions at least partly on the basis of which one of the look-up tables was most recently accessed when managing the first data, and

control the determined first one of the fixed-functionality actions to be carried out so as to initiate the needed one or more fixed-functionality actions to be carried out at least partly in accordance with the converted first metadata.

2. A network element according to claim 1, wherein the processing system is further adapted to:

convert the second metadata associated with the second data being managed by the fixed-functionality data path to a data format suitable for the software-defined data path in response to a need to carry out one or more of the software-defined actions in conjunction with forwarding the second data,

determine a first one of the look-up tables of the software-defined data path at least partly on the basis of which one of the fixed-functionality actions was most recently carried out when managing the second data, and

carry out a look-up from the determined first one of the look-up tables so as to initiate the one or more needed software-defined actions to be carried out at least partly in accordance with the converted second metadata.

3. A network element according to claim 1, wherein the processing system is further adapted to:

convert the converted first metadata back to a data format suitable for the software-defined data path in response to a need to carry out one or more of the software-defined actions after carrying out the needed one or more fixed-functionality actions,

determine a second one of the look-up tables of the software-defined data path at least partly on the basis of which one of the one or more needed fixed-functionality actions was most recently carried out when managing the first data by the fixed-functionality data path,

carry out a look-up from the determined second one of the look-up tables so as to initiate the one or more software-defined actions needed to be carried out after the one or more needed fixed-functionality actions and at least partly in accordance with the back converted first metadata.

4. A network element according to claim 2, wherein the processing system is further adapted to:

convert the converted second metadata back to the data format suitable for the fixed-functionality data path in response to a need to carry out one or more of the fixed-functionality actions after carrying out the needed one or more software-defined actions,

determine a second one of the fixed-functionality actions from among the fixed-functionality actions at least partly on the basis of which one of the look-up tables was most recently accessed when managing the second data by the software-defined data path,

control the determined second one of the fixed-functionality actions to be carried out so as to initiate the one or more fixed-functionality actions needed to be carried out after the one or more needed software-defined actions and at least partly in accordance with the back converted second metadata.

5. A network element according to claim 1, wherein the processing system is adapted to construct the software-defined data path in accordance with at least one of the following:

the OpenFlow protocol, the Forwarding and Control Element Separation ForCES protocol.

6. A network element according to claim 1, wherein the processing system is adapted to configure the fixed-functionality data path in accordance with at least one of the following:

one or more L3 network layer routing protocols, one or more L2 data link layer control protocols, one or more MultiProtocol Label Switching MPLS signaling protocols.

7. A network element according to claim 6, wherein:

the one or more L3 network layer routing protocols comprise at least one of the following;

the Open Shortest Path First OSPF, the Intermediate system-Intermediate system ISIS, the Border Gateway Protocol BGP, the Protocol Independent multicast Sparse Mode PIM-SM,

the one or more L2 data link layer control protocols comprise at least one of the following;

the Spanning Tree Protocol STP, the Rapid Spanning Tree Protocol RSTP, the multiple Spanning Tree Protocol MSTP, the Transparent Interconnection of Lots of Links TRILL, the Link Aggregation Control Protocol LACP, and

the one or more MultiProtocol Label Switching MPLS signaling protocols comprise at least one of the following;

Label Distribution Protocol LDP, Resource Reservation Protocol-Traffic Engineering RSVP-TE, the Border Gateway Protocol BGP.

8. A network element according to claim 1, wherein the software-defined data path comprises at least one of the following:

a look-up table suitable for selecting between the software-defined data path and the fixed-functionality data path, a look-up table suitable for quality-of-service QoS management, a look-up table suitable for MultiProtocol Label Switching MPLS, a look-up table suitable for Access Control List ACL filtering, a look-up table suitable for Internet Protocol IP routing, a look-up table suitable for Ethernet switching, a look-up table suitable for load balancing, a look-up table suitable for flow protection.

9. A network element according to claim 1, wherein the fixed-functionality data path is capable of carrying out at least one of the following:

Virtual Local Access Network VLAN management, Virtual Router Redundancy Protocol VRRP destination Media Access Control MAC filtering, quality-of-service management, MultiProtocol Label Switching MPLS, Access Control List ACL filtering, Internet Protocol IP routing, Ethernet switching, load balancing, flow protection, link aggregation, Outgoing Media Access Control MAC imposition.

10. A method for managing data in a network element of a software-defined network, the method comprising:

maintaining, in accordance with configuration data received from a controller of the software-defined network, a software-defined data path for managing first data to be forwarded, the software-defined data path comprising look-up tables for selecting software-defined actions and one or more of the software-defined actions modifying first metadata associated with the first data,

maintaining, in accordance with forwarding-parameter data received at the network element, a fixed-functionality data path for managing second data to be forwarded, the fixed-functionality data path defining fixed-functionality actions and one or more of the fixed-functionality actions modifying second metadata associated with the second data,

converting the first metadata associated with the first data being managed by the software-defined data path to a data format suitable for the fixed-functionality data path in response to a need to carry out one or more of the fixed-functionality actions in conjunction with forwarding the first data,

determining a first one of the fixed-functionality actions from among the fixed-functionality actions at least partly on the basis of which one of the look-up tables was most recently accessed when managing the first data, and

controlling the determined first one of the fixed-functionality actions to be carried out so as to initiate the needed one or more fixed-functionality actions to be carried out at least partly in accordance with the converted first metadata.

11. A method according to claim 10, wherein the method further comprises:

converting the second metadata associated with the second data being managed by the fixed-functionality data path to a data format suitable for the software-defined data path in response to a need to carry out one or more of the software-defined actions in conjunction with forwarding the second data,

determining a first one of the look-up tables of the software-defined data path at least partly on the basis of which one of the fixed-functionality actions was most recently carried out when managing the second data, and

carrying out a look-up from the determined first one of the look-up tables so as to initiate the one or more needed software-defined actions to be carried out at least partly in accordance with the converted second metadata.

12. A method according to claim 10, wherein the method further comprises:

converting the converted first metadata back to a data format suitable for the software-defined data path in response to a need to carry out one or more of the software-defined actions after carrying out the needed one or more fixed-functionality actions,

determining a second one of the look-up tables of the software-defined data path at least partly on the basis of which one of the one or more needed fixed-functionality actions was most recently carried out when managing the first data by the fixed-functionality data path,

carrying out a look-up from the determined second one of the look-up tables so as to initiate the one or more software-defined actions needed to be carried out after the one or more needed fixed-functionality actions and at least partly in accordance with the back converted first metadata.

13. A method according to claim 11, wherein the method further comprises:

converting the converted second metadata back to the data format suitable for the fixed-functionality data path in response to a need to carry out one or more of the fixed-functionality actions after carrying out the needed one or more software-defined actions,

determining a second one of the fixed-functionality actions from among the fixed-functionality actions at least partly on the basis of which one of the look-up tables was most recently accessed when managing the second data by the software-defined data path,

controlling the determined second one of the fixed-functionality actions to be carried out so as to initiate the one or more fixed-functionality actions needed to be carried out after the one or more needed software-defined actions and at least partly in accordance with the back converted second metadata.

14. A method according to claim 10, wherein the software-defined data path is maintained in accordance with at least one of the following:

the OpenFlow protocol, the Forwarding and Control Element Separation ForCES protocol.

15. A method according to claim 10, wherein the fixed-functionality data path is maintained in accordance with at least one of the following:

one or more L3 network layer routing protocols, one or more L2 data link layer control protocols, one or more MultiProtocol Label Switching MPLS signaling protocols.

16. A method according to claim 15, wherein:

the one or more L3 network layer routing protocols comprise at least one of the following;

the Open Shortest Path First OSPF, the Intermediate system-Intermediate system ISIS, the Border Gateway Protocol BGP, the Protocol Independent multicast Sparse Mode PIM-SM,

the one or more L2 data link layer control protocols comprise at least one of the following;

the Spanning Tree Protocol STP, the Rapid Spanning Tree Protocol RSTP, the multiple Spanning Tree Protocol MSTP, the Transparent Interconnection of Lots of Links TRILL, the Link Aggregation Control Protocol LACP, and

the one or more MultiProtocol Label Switching MPLS signaling protocols comprise at least one of the following;

Label Distribution Protocol LDP, Resource Reservation Protocol-Traffic Engineering RSVP-TE, the Border Gateway Protocol BGP.

17. A method according to claim 10, wherein the software-defined data path comprises at least one of the following:

a look-up table suitable for selecting between the software-defined data path and the fixed-functionality data path, a lookup table suitable for quality-of-service QoS management, a look-up table suitable for MultiProtocol Label Switching MPLS, a look-up table suitable for Access Control List ACL filtering, a look-up table suitable for Internet Protocol IP routing, a look-up table suitable for Ethernet switching, a look-up table suitable for load balancing, a look-up table suitable for flow protection.

18. A method according to claim 10, wherein the fixed-functionality data path is capable of carrying out at least one of the following:

Virtual Local Access Network VLAN management, Virtual Router Redundancy Protocol VRRP destination Media Access Control MAC filtering, quality-of-service management, MultiProtocol Label Switching MPLS, Access Control List ACL filtering, Internet Protocol IP routing, Ethernet switching, load balancing, flow protection, link aggregation, Outgoing Media Access Control MAC imposition.

19. A non-transitory computer readable medium encoded with a computer program comprising computer executable instructions for controlling a programmable processing system of a network element of a software-defined network to:

construct, in accordance with configuration data received from a controller of the software-defined network, a software-defined data path for managing first data to be forwarded, the software-defined data path comprising lookup tables for selecting software-defined actions and one or more of the software-defined actions modifying first metadata associated with the first data,

configure, in accordance with forwarding-parameter data received at the network element, a fixed-functionality data path for managing second data to be forwarded, the fixed-functionality data path defining fixed-functionality actions and one or more of the fixed-functionality actions modifying second metadata associated with the second data,

convert the first metadata associated with the first data being managed by the software-defined data path to a data format suitable for the fixed-functionality data path in response to a need to carry out one or more of the fixed-functionality actions in conjunction with forwarding the first data,

determine one of the fixed-functionality actions from among the fixed-functionality actions at least partly on the basis of which one of the look-up tables was most recently accessed when managing the first data, and

control the determined one of the fixed-functionality actions to be carried out so as to initiate the needed one or more fixed-functionality actions to be carried out at least partly in accordance with the converted first metadata.