Method and controller for chaining applications in a software defined network

Patent metadata

Field	Value
Publication number	US-2016283290-A1
Application number	US-201615174006-A
Country	US
Kind code	A1
Filing date	Jun 6, 2016
Priority date	Dec 6, 2013
Publication date	Sep 29, 2016
Grant date	—

Abstract

A method and a software defined network (SDN) controller for chaining applications in a SDN. A service data table is created in the SDN controller. In the service data table a plurality of applications are associated with a plurality of application types. Furthermore, at least one service chain is created in the SDN controller. The at least one service chain defines an order of application types running on the SDN controller. At least one application is registered to the service chain based on its application type as associated with the application in the service data table.

First claim

What is claimed is:

1 . A method for chaining applications in a software defined network (SDN), the method comprising:
creating a service data table in an SDN controller, wherein a plurality of applications is associated with a plurality of application types in the service data table; creating at least one service chain defining an order of application types in the SDN controller; and registering at least one application to the at least one service chain based on the application type associated with the at least one application in the service data table.

2 . The method according to claim 1 , further comprising:
exposing the at least one service chain and the service data table to applications through at least one application programming interface (API).

3 . The method according to claim 1 , further comprising:
creating, in the at least one service chain, a plurality of service insertion points for applications, wherein each service insertion point accepts applications of one or more application types associated to the service insertion point.

4 . The method according to claim 3 , wherein each service insertion point is exposed to applications through at least one application programming interface (API).

5 . The method according to claim 1 , wherein the registering comprises:
determining, by the SDN controller, the application type of the at least one application according to the service data table; and associating, by the SDN controller, the at least one application with at least one service insertion point according to the determined application type.

6 . The method according to claim 5 , wherein the registering comprises:
creating, by the SDN controller, a new application type in the service data table, if the at least one application is determined not to be associated with an application type in the service data table; and associating, by the SDN controller, the at least one application with at least one service insertion point according to the created application type.

7 . The method according to claim 1 , further comprising:
routing, by the SDN controller, at least one flow comprising at least one data packet according to the at least one service chain of applications.

8 . The method according to claim 7 , further comprising:
extracting, by the at least one application, metadata from the flow, and storing the extracted metadata as information about the flow in a flow table.

9 . The method according to claim 8 , wherein the metadata extracted from the flow comprises an application type, a specific application ID, a user ID and/or a flow content ID.

10 . The method according to claim 8 , wherein the metadata extracted from the flow comprises frame information about each frame of the flow.

11 . The method according to claim 10 , wherein the frame information comprises one or more of a frame marked for dropping, a changed header, and previous header information.

12 . The method according to claim 8 , wherein a plurality of applications share the metadata stored in the flow table.

13 . The method according to claim 8 , wherein the flow table is created in the SDN controller.

14 . The method according to claim 13 , wherein the at least one flow is routed through the SDN controller according to the at least one service chain of applications.

15 . The method according to claim 8 , wherein the flow table is created in a chaining module connected to the SDN controller.

16 . The method according to claim 15 , further comprising:
creating, by the SDN controller, network paths between the at least one application and the chaining module according to the order of application types defined by the service chain.

17 . The method according to claim 16 , wherein the at least one flow is routed through the chaining module and the network paths created by the SDN controller according to the at least one service chain of applications.

18 . The method according to claim 8 , wherein the flow table is distributed over the at least one application and a further application registered to the service chain.

19 . The method according to claim 18 , wherein the at least one flow is routed through the at least one application and the further application according to the at least one service chain of applications by using a message passing mechanism.

20 . The method according to claim 8 , further comprising:
querying, by the at least one application, the flow table, in order to obtain the stored information about the flow.

21 . The method according to claim 1 , wherein creating the at least one service chain comprises:
creating, by the SDN controller, a plurality of service chains; and customizing, by the SDN controller, each service chain for a different customer.

22 . The method according to claim 8 , further comprising:
associating, by the SDN controller, a plurality of flows to the at least one service chain using user defined filtering.

23 . A computer system, comprising a memory storing a software defined network (SDN) controller, for chaining applications in a SDN, wherein:
a service data table is installed in the SDN controller, wherein a plurality of applications are associated with a plurality of application types in the service data table; at least one service chain defining an order of application types is implemented on the SDN controller; and the SDN controller is configured to register at least one application to the service chain based on the application type associated with the application in the service data table.

24 . The computer system according to claim 23 , wherein the SDN controller is configured to create in the at least one service chain a plurality of service insertion points for applications, wherein each service insertion point accepts applications of one or more application types associated to the service insertion point.

25 . The computer system according to claim 23 , wherein the SDN controller is configured to:
determine the application type of the at least one application according to the service data table; and associate the at least one application with at least one service insertion point according to the determined application type.

26 . The computer system according to claim 25 , wherein the SDN controller is configured to:
create a new application type in the service data table, if the at least one application is determined not to be associated with an application type in the service data table; and associated the at least one application with at least one service insertion point according to the created application type.

27 . The computer system according to claim 23 , wherein:
the SDN controller is configured to route at least one flow comprising at least one data packet according to the at least one service chain of applications; and a flow table is installed in the SDN controller, wherein in the flow table metadata extracted by the applications from the flow is stored as information about the flow.

28 . The computer system according to claim 27 , wherein:
the flow table is created in the SDN controller; or the flow table is distributed over the at least one application and a further application registered to the service chain; or the system further comprises a chaining module connected to the SDN controller and the flow table is created in

Assignees

• Huawei Tech Co Ltd

Inventors

• Porat Hayim

Classifications

• G06F9/54 Primary

  Interprogram communication · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L67/567

  Integrating service provisioning from a plurality of service providers · CPC title