System and method for service chaining with tunnel chains in software defined network

US9565135B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9565135-B2
Application numberUS-201414530278-A
CountryUS
Kind codeB2
Filing dateOct 31, 2014
Priority dateOct 31, 2014
Publication dateFeb 7, 2017
Grant dateFeb 7, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

An embodiment method of service chaining in a software defined network (SDN) having SDN switches includes receiving a service chain requirement having a plurality of services. Respective tunnels are then defined for the plurality of services. The method then configures the SDN switches to establish the respective tunnels and form a tunnel chain.

First claim

Opening claim text (preview).

What is claimed is: 1. A method of service chaining in a software defined network (SDN) having SDN switches, the method comprising: receiving a service chain requirement having a plurality of services; defining respective tunnels for the plurality of services, wherein the defining comprises: parsing the plurality of services into adjacent service pairs; mapping the adjacent service pairs to the respective tunnels; and configuring the SDN switches to establish the respective tunnels and form a tunnel chain. 2. The method of claim 1 wherein the receiving comprises receiving a service chain policy from an orchestrator or SDN application over a north-bound interface (NBI). 3. The method of claim 1 wherein the configuring comprises communicating the configurations to the SDN switches over a south-bound interface (SBI). 4. The method of claim 3 wherein the communicating over an SBI comprises sending the configurations using an OpenFlow protocol or another south-bound (SB) protocol. 5. The method of claim 1 wherein the defining further comprises: computing SDN switch configurations corresponding to the respective tunnels and the tunnel chain. 6. The method of claim 1 wherein parsing the plurality of services comprises defining a null service representing an ingress point for a service request from a user. 7. The method of claim 1 wherein the configuring is carried out before receipt of a service request from a user at an SDN edge node. 8. A software defined network (SDN) controller, comprising: a north-bound interface (NBI) over which a service chain policy is received, wherein the service chain policy defines a service chain having a plurality of services; a non-transitory computer-readable memory storing instructions; one or more processors in communication with the NBI and the memory, wherein the one or more processors execute the instructions to: decompose the service chain policy into respective tunnels corresponding to adjacent service pairs of the plurality of services, and compute configurations corresponding to the respective tunnels; and a south-bound interface (SBI), in communication with the one or more processors, and over which the configurations are communicated to an SDN switch layer to establish the respective tunnels and form a tunnel chain. 9. The SDN controller of claim 8 wherein the one or more processors execute the instructions to: parse the plurality of services into the adjacent service pairs; and map the adjacent service pairs to the respective tunnels. 10. The SDN controller of claim 8 wherein the one or more processors execute the instructions to compute additional configurations to concatenate the respective tunnels into the tunnel chain. 11. The SDN controller of claim 8 wherein the SBI is configured to communicate with the SDN switch layer according to an OpenFlow protocol or another south-bound (SB) protocol. 12. The SDN controller of claim 8 wherein the one or more processors execute the instructions to push the configurations to the SDN switch layer before an initial service request arrives at an ingress point in the SDN switch layer, and a packet-in packet is sent to the SDN controller. 13. A method of service chaining in a software defined network (SDN) having SDN switches, the method comprising: receiving, at an SDN controller, a service chain policy from an abstract layer over a north-bound interface (NBI), wherein the service chain policy defines a service chain having a plurality of services; parsing, by a service engine, the plurality of services into adjacent service pairs; mapping, by the service engine, the adjacent service pairs to respective tunnels; computing, by the service engine, first configurations corresponding to the respective tunnels; computing, by the service engine, second configurations for concatenating the respective tunnels into a tunnel chain; communicating, by the SDN controller, the first configurations and the second configurations to the SDN switches to establish the respective tunnels and the tunnel chain; and receiving, at the SDN controller, a packet-in from an SDN edge node of the SDN switches, and directing an initial request to the SDN edge node into the tunnel chain. 14. The method of claim 13 further comprising configuring, by the SDN controller, flow tables at the edge SDN switch after receiving the packet-in. 15. The method of claim 14 the flow tables comprise all of the plurality of services in an order specified by the service chain policy. 16. The method of claim 13 wherein the communicating the first configurations and the second configurations is carried out before receiving the packet-in. 17. The method of claim 13 wherein the plurality of services includes an intruder detection service (IDS), a network address translation (NAT) service, and an email service. 18. The method of claim 13 further comprising computing, by the service engine, flow configurations for start points of the respective tunnels to direct traffic into a next tunnel of the respective tunnels. 19. The method of claim 13 wherein each of the respective tunnels spans at least one SDN switch. 20. The method of claim 13 wherein the receiving from the abstract layer comprises receiving the service chain policy from an SDN application. 21. A software defined network (SDN) controller in an SDN having SDN switches, the SDN controller comprising: a non-transitory computer-readable memory storing instructions; one or more processors in communication with the memory, wherein the one or more processors execute the instructions for: receiving a service chain requirement having a plurality of services; defining respective tunnels for the plurality of services, wherein the defining comprises: parsing the plurality of services into adjacent service pairs; mapping the adjacent service pairs to the respective tunnels; and configuring the SDN switches to establish the respective tunnels and form a tunnel chain. 22. The SDN controller of claim 21 , wherein the defining further comprises computing SDN switch configurations corresponding to the respective tunnels and the tunnel chain. 23. A method of operating a software defined network (SDN) controller, the method comprising: receiving, by a north-bound interface (NBI) of the SDN controller, a service chain policy, wherein the service chain policy defines a service chain having a plurality of services; decomposing, by the SDN controller, the service chain policy into respective tunnels corresponding to adjacent service pairs of the plurality of services; computing, by the SDN controller, configurations corresponding to the respective tunnels; and communicating, by a south-bound interface (SBI) of the SDN controller, the configurations to an SDN switch layer to establish the respective tunnels and form a tunnel chain. 24. The method of claim 23 , further comprising: parsing, by the SDN controller, the plurality of services into the adjacent service pairs; and mapping, by the SDN controller, the adjacent service pairs to the respective tunnels.

Assignees

Inventors

Classifications

  • wherein the managed service relates to simple transport services, i.e. providing only network infrastructure · CPC title

  • for initial configuration or provisioning, e.g. plug-and-play · CPC title

  • Software-defined radio [SDR] systems, i.e. systems wherein components typically implemented in hardware, e.g. filters or modulators/demodulators, are implented using software, e.g. by involving an AD or DA conversion stage such that at least part of the signal processing is performed in the digital domain (digital baseband systems H04L25/00; digital modulation/demodulation H04L27/00; CDMA H04B1/707; TDMA H04B7/2643; image transmission H04N5/00) · CPC title

  • Service on demand, e.g. definition and deployment of services in real time · CPC title

  • H04L49/15Primary

    Interconnection of switching modules · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9565135B2 cover?
An embodiment method of service chaining in a software defined network (SDN) having SDN switches includes receiving a service chain requirement having a plurality of services. Respective tunnels are then defined for the plurality of services. The method then configures the SDN switches to establish the respective tunnels and form a tunnel chain.
Who is the assignee on this patent?
Futurewei Technologies Inc
What technology area does this patent fall under?
Primary CPC classification H04L49/15. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Feb 07 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).