Service Function Registration Mechanism And Capability Indexing

• US 20160248860A1
• Filed: 02/15/2016
• Published: 08/25/2016
• Est. Priority Date: 02/25/2015
• Status: Active Grant

• Current Assignee: Futurewei Technologies Incorporated (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Futurewei Technologies Incorporated (Huawei Investment & Holding Co., Ltd.)
• Inventors: Dunbar, Linda, Zhang, Hong
• Granted Patent: US 10,587,698 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/2589 over a relay server, e.g. traversal using relay for network address translation [TURN]
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A method implemented in a network engine comprising receiving, by a service function (SF) orchestrator in the network engine, a registration request message from a third-party SF manager requesting registration of a SF comprising one or more SF instances in a network, wherein the registration request message comprises vendor identification information identifying a vendor of the SF and SF identification information identifying the SF, receiving a capability information message from the third-party SF manager indicating vendor-specific capability information associated with the SF, receiving a service request message from a service client requesting a network service and one or more policies for the service, generating the network service by utilizing the one or more SF instances according to the one or more policies and the vendor-specific capability information, and sending the one or more policies to the one or more SF instances.

Claims

1. A method implemented in a network engine comprising:

receiving, by a service function (SF) orchestrator in the network engine, a registration request message from a third-party SF manager requesting registration of a SF comprising one or more SF instances in a network, wherein the registration request message comprises vendor identification information identifying a vendor of the SF and SF identification information identifying the SF;

receiving, by the SF orchestrator, a capability information message from the third-party SF manager indicating vendor-specific capability information associated with the SF;

receiving, by the SF orchestrator, a service request message from a service client requesting a network service and one or more policies for the service;

generating the network service by utilizing the one or more SF instances according to the one or more policies and the vendor-specific capability information; and

sending the one or more policies to the one or more SF instances to facilitate an execution of the network service requested by the service client.

2. The method of claim 1, wherein the vendor identification information comprises:

a vendor name of the vendor; and

a vendor identifier (ID) identifying the vendor, and

wherein the SF identification information comprises;

a SF name of the SF;

a SF type identifying a service type of the SF; and

a SF ID identifying the SF.

3. The method of claim 1, further comprising:

sending, by the SF orchestrator, an authentication request message to an authentication, authorization, and accounting (AAA) entity to request authentication for the vendor; and

receiving, by the SF orchestrator, an authentication grant message from the AAA entity comprising an authentication grant to the vendor.

4. The method of claim 3, further comprising sending, by the SF orchestrator, a session start message to the third-party SF manager to start a session with the third-party SF manager after receiving the authentication grant message, wherein the capability information message is received after sending the session start message.

5. The method of claim 4, wherein the SF identification information comprises a SF identifier (ID) identifying the SF, and wherein the session start message comprises:

a session ID identifying the session;

a session key associated with the session; and

the SF ID indicating that the SF is registered for the session.

6. The method of claim 1, further comprising:

receiving, by the SF orchestrator, a SF instance information message from the third-party SF manager indicating location information associated with the SF instance in the network; and

storing the location information in a SF instance database (DB).

7. The method of claim 1, further comprising receiving, by the SF orchestrator, a capability update message from the third-party SF manager indicating a dynamic update of the capability information of the SF.

8. The method of claim 1, wherein the capability information message indicates a policy supported by the SF, and wherein the policy comprises a packet-level inspection depth, a contextual state, and an action supported by the SF.

9. The method of claim 1, wherein the SF is associated with network security.

10. A virtual network function (VNF) controller comprising:

a receiver configured to receive a first service function (SF) configuration message from a network controller indicating a first policy for a first SF instance of a SF located in a network;

a processor coupled to the receiver and configured to determine that the first SF instance is one of a first plurality of SF instances of the SF in association with a first of a plurality of sub-controllers; and

a transmitter coupled to the processor and configured to send a second SF configuration message to the first sub-controller instructing the first sub-controller to dispatch the first policy to the first SF instance.

11. The VNF controller of claim 10, wherein the first SF instance is associated with a service flow in the network, wherein the processor is further configured to:

obtain information indicating that the service flow is reconfigured to associate with a second SF instance of the SF instead of the first SF instance; and

determine that the second SF instance is one of a second plurality of SF instances of the SF in association with a second of the plurality of sub-controllers, and

wherein the transmitter is further configured to send a third SF configuration message to the second sub-controller instructing the second sub-controller to dispatch the first policy to the second SF instance.

12. The VNF controller of claim 10, wherein the receiver is further configured to receive a third SF configuration message from the network controller indicating a second policy for a second SF instance of the SF located in the network, wherein the first policy and the second policy are different, wherein the processor is further configured to determine that the second SF instance is one of a second plurality of SF instances of the SF in association with a second of the plurality of sub-controllers, and wherein the transmitter is further configured to send a fourth SF configuration message to the second sub-controller instructing the second sub-controller to dispatch the second policy to the second SF instance.

13. The VNF controller of claim 10, wherein the first SF instance is associated with a service flow in the network, and wherein the transmitter is further configured to send a SF instance location message to a software-defined networking (SDN) controller indicating location information associated with the first SF instance to enable forwarding of traffic associated with the service flow towards the first SF instance.

14. A method implemented in a network engine comprising:

receiving, by a service function (SF) orchestrator in the network engine, a capability information message from a third-party SF manager indicating a SF name of a SF in a network and vendor-specific capability information associated with the SF;

indexing, by the SF orchestrator, the vendor-specific capability information in a SF catalog database (DB);

receiving, by the SF orchestrator, a service request message from a service client requesting a service in the network and a policy for the service;

determining, by the SF orchestrator, that the service is associated with the SF;

generating, by the SF orchestrator, a configuration for the SF according to the policy and the indexed vendor-specific capability information; and

sending, by the SF orchestrator, a SF configuration message to a network element (NE) to facilitate an execution of the SF according to the configuration.

15. The method of claim 14, wherein the capability information message comprises:

a supported header field indicating a packet-level inspection depth supported by the SF;

a supported context field indicating a contextual state maintained by the SF;

a supported action field indicating an action supported by the SF; and

a supported function field indicating a function supported by the SF in addition to functionalities of the SF.

16. The method of claim 15, wherein the packet-level inspection depth is associated with a service chain (SC) encapsulation protocol, a media access control (MAC) protocol, an Internet protocol version 4 (IPv4) protocol, an Internet protocol version 6 (IPv6) protocol, a transmission control protocol (TCP), an user datagram protocol (UDP), a hypertext transfer protocol (HTTP), or combinations thereof.

17. The method of claim 15, wherein the contextual state is associated with time, a traffic flow direction, an authentication state, an authorization state, an accounting state, a session state, or combinations thereof.

18. The method of claim 15, wherein the action is associated with a network security comprising an antivirus (AV) operation, an intrusion protection system (IPS) operation, an uniform resource locator (URL) filtering operation, a file blocking operation, a data filtering operation, an application control operation, or combinations thereof.

19. The method of claim 15, wherein indexing the vendor-specific capability information comprises:

indexing the SF name under a name category in the SF catalog DB;

indexing the supported header field under a subject category in the SF catalog DB;

indexing the supported context field under a context category in the SF catalog DB;

indexing the supported action field under an action category in the SF catalog DB; and

indexing the supported action field under a function category in the SF catalog DB.

20. The method of claim 15, wherein generating the configuration for the SF comprises:

generating a policy condition according to the supported header field and the supported context field in the capability information message and the policy in the service request message;

generating a policy action according to the supported action field in the context field in the capability information message and the policy in the service request message; and

generating a policy rule according to the policy condition and the policy action and the policy in the service request message.