Software Defined Network (SDN) Control Signaling for Traffic Engineering to Enable Multi-type Transport in a Data Plane

• US 20160308758A1
• Filed: 04/17/2015
• Published: 10/20/2016
• Est. Priority Date: 04/17/2015
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Li, Xu, Zhang, Hang
• Granted Patent: US 9,749,225 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/304 Route determination for signalling traffic
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/64 using an overlay routing layer

Abstract

Aspects of this disclosure provide techniques for dynamically configuring flow splitting via software defined network (SDN) signaling instructions. An SDN controller may instruct an ingress network node to split a traffic flow between two or more egress paths, and instruct the ingress network node, and perhaps downstream network nodes, to transport portions of the traffic flow in accordance with a forwarding protocol. In one example, the SDN controller instructs the network nodes to transport portions of the traffic flow in accordance with a link-based forwarding protocol. In other examples, the SDN controller instructs the network nodes to transport portions of the traffic flow in accordance with a path-based or source-based transport protocol.

Claims

1. A method comprising:

receiving, by a network node in a packet switched domain, a control signaling instruction from a controller, wherein the control signaling instruction comprises routing information, the routing information indicating at least one egress next-hop or egress pathway and at least one of a link-based flow transport protocol, a path-based flow transport protocol, and a source-based flow transport protocol, and wherein the at least one egress next-hop or egress pathway corresponds to one of the flow transport protocols;

receiving, by the network node, a traffic flow or a traffic flow portion over an ingress link; and

transmitting, by the network node, the traffic flow or the traffic flow portion to next hop network nodes over the at least one egress next-hop or egress pathway.

2. The method of claim 1, wherein routing information further comprise a protocol type field, and the protocol type field indicates at least one protocol type of a link-based flow transport protocol, a path-based flow transport protocol, and a source-based flow transport protocol.

3. The method of claim 1, wherein the control signaling instruction indicates the path-based transport protocol or the source-based transport protocol, and wherein transmitting the traffic flow or the traffic flow portion to next hop network nodes over the at least one egress next-hop or egress pathway comprises:

appending path information to packets in the respective portions of the traffic flow prior to forwarding respective portions of the traffic flow over the at least one egress next-hop or egress pathway.

4. The method of claim 3, wherein the path information includes a path identifier when the control signaling instruction indicates the path-based transport protocol, and

wherein the path information includes a list of next-hop identifiers when the control signaling instruction indicates the source-based transport protocol, the list of next-hop identifiers defining next-hop network nodes along the corresponding egress pathway.

5. The method of claim 4, wherein the list of next-hop identifiers is excluded from packets in the respective portions of the traffic flow when the control signaling instruction indicates the path-based transport protocol.

6. The method of claim 1, wherein before the transmitting step, the method further comprises:

splitting, by the by the network node, the traffic flow or the traffic flow portion into at least two sub traffic flows based on a splitting rule carried in the control signaling instruction.

7. The method of claim 6, wherein splitting the traffic flow or the traffic flow portion into at least two sub traffic flows based on the splitting rule carried in the control signaling instruction comprises:

communicating a first portion of the traffic flow over a first egress pathway; and

communicating a second portion of the traffic flow over a second egress pathway.

8. The method of claim 6, wherein a first subset of packets in the first portion of the traffic flow are excluded from the second portion of the traffic flow.

9. The method of claim 8, wherein a second subset of packets in the first portion of the traffic flow are included in the second portion of the traffic flow such that the second portion of the traffic flow is partially redundant with the first portion of the traffic flow.

10. The method of claim 9, wherein the flow splitting information specifies a maximum redundancy threshold between the first portion of the traffic flow and the second portion of the traffic flow, the maximum redundancy threshold constraining the amount of redundancy between portions of the traffic flow split over the two or more egress pathways.

11. The method of claim 6, wherein the second egress pathway diverges from the first egress pathway.

12. A network node in a packet switched domain, the network node comprising:

a processor; and

a computer readable storage medium storing programming for execution by the processor, the programming including instructions to;

receive a control signaling instruction from a controller, wherein the control signaling instruction comprises routing information, the routing information indicating at least one egress next-hop or egress pathway and at least one of a link-based flow transport protocol, a path-based flow transport protocol, and a source-based flow transport protocol, and wherein the at least one egress next-hop or egress pathway corresponds to one of the flow transport protocols;

receive a traffic flow or a traffic flow portion over an ingress link; and

transmit the traffic flow or the traffic flow portion to next hop network nodes over the at least one egress next-hop or egress pathway.

13. A method for implementing flow splitting in software defined networking (SDN) topologies, the method comprising:

communicating, by a controller, a control signaling instruction to a network node of a packet switched domain, wherein the control signaling instruction comprises routing information, the routing information indicating at least one egress next-hop or egress pathway and at least one of a link-based flow transport protocol, a path-based flow transport protocol, and a source-based flow transport protocol, and wherein the at least one egress next-hop or egress pathway corresponds to one of the flow transport protocols, and

wherein the routing information prompts the network node to forward a traffic flow or traffic flow portion over the at least one egress next-hop or egress pathway of the packet switched domain in accordance with a forwarding protocol indicated by the control signaling instruction.

14. The method of claim 13, wherein the control signaling instruction includes a splitting rule instructing the network node split the traffic flow or the traffic flow portion into at least two sub traffic flows.

15. The method of claim 14, wherein there is at least some redundancy between the at least two sub traffic flows.

16. The method of claim 14, wherein the control signaling instruction indicates the path-based transport protocol or the source-based transport protocol, and wherein splitting the traffic flow over two or more egress pathways comprises:

appending path information to packets in the respective portions of the traffic flow prior to forwarding respective portions of the traffic flow over the two or more egress pathways.

17. The method of claim 16, wherein the path information includes a path identifier when the control signaling instruction indicates the path-based transport protocol, and

wherein the path information includes a list of next-hop identifiers when the control signaling instruction indicates the source-based transport protocol, the list of next-hop identifiers defining next-hop network nodes along the corresponding egress pathway.

18. The method of claim 13, wherein the control signaling instruction indicates the link-based transport protocol, and wherein the method further comprises:

sending, by the network node, additional control signaling instructions to downstream nodes, wherein the additional control signaling instructions directly instruct the downstream nodes to forward portions of the traffic flow over next-hops along one or more pathways.

19. A controller comprising:

a processor; and

a computer readable storage medium storing programming for execution by the processor, the programming including instructions to;

communicate a control signaling instruction to a network node of a packet switched domain, wherein the control signaling instruction comprises routing information, the routing information indicating at least one egress next-hop or egress pathway and at least one of a link-based flow transport protocol, a path-based flow transport protocol, and a source-based flow transport protocol, and wherein the at least one egress next-hop or egress pathway corresponds to one of the flow transport protocols, and

wherein the routing information prompts the network node to forward a traffic flow or traffic flow portion over the at least one egress next-hop or egress pathway of the packet switched domain in accordance with a forwarding protocol indicated by the control signaling instruction.