Service Orchestration Method and Apparatus, and Service Provisioning Method and Apparatus

Patent metadata

Field	Value
Publication number	US-2018367409-A1
Application number	US-201816103290-A
Country	US
Kind code	A1
Filing date	Aug 14, 2018
Priority date	Aug 24, 2016
Publication date	Dec 20, 2018
Grant date	—

Abstract

This application belongs to the field of service orchestration and discloses a service orchestration method and apparatus, and a service provisioning method and apparatus. The method includes: obtaining a service template; obtaining a service identity, a service attribute, and a service policy that are entered by an operator and a default service parameter; substituting the options of the service template with the service attribute and the service policy that are entered by the operator and the default service parameter; associating the service template that is filled in with the service identity; and storing the service template that is associated with the service identity in a service type library, and publishing the service template to the user.

First claim

What is claimed is:

1 . A method, comprising:
obtaining a service template corresponding to a service, wherein the service template comprises a first field for a service attribute describing the service, a second field for a service policy for configuring the service, and a third field for a service parameter, wherein the service parameter field can be filled in by a user; obtaining, from an operator, a service identity, a service attribute, and a service policy, and obtaining a default service parameter; filling in the first field of the service template and the second field of the service template with the service attribute and the service policy obtained from the operator, and filling in the third field of the service template with the default service parameter, to form a completed service template; associating the completed service template with the service identity obtained from the operator; storing the completed service template that is associated with the service identity in a service type library; and publishing the completed service template to the user.

2 . The method according to claim 1 , wherein obtaining the service template comprises:
publishing a policy management interface using a northbound interface; and obtaining the service template using the policy management interface.

3 . The method according to claim 1 , wherein publishing the service template to the user comprises:
publishing a service creation interface using a northbound interface, causing the user to use the completed service template in the service type library using the service creation interface.

4 . The method according to claim 1 , wherein:
the service template comprises a first subtemplate corresponding to a first domain on a network and a second subtemplate corresponding to a second domain on the network, wherein the first domain is different from the second domain; and the first subtemplate is associated with an identifier of the first domain.

5 . The method according to claim 1 , wherein the service template corresponds to a virtual private network (VPN) service.

6 . The method according to claim 5 , wherein the service attribute obtained from the operator comprises: a topology type, a service type, a flow configuration, a service level agreement (SLA) parameter, and a layer parameter.

7 . The method according to claim 5 , wherein the service policy obtained from the operator comprises: an address pool policy, a quality of service (QoS) policy, a protection policy, and a routing policy.

8 . The method according to claim 5 , wherein the default service parameter comprises an identifier of a provider edge (PE) side access point and bandwidth information.

9 . A method, comprising:
obtaining a service identity entered by a user; selecting a corresponding service template from a service type library according to the service identity, wherein the corresponding service template comprises: a first field comprising a first service attribute describing a first service, a second field comprising a first service policy for configuring the first service, and third field comprising a first service parameter, wherein the first service parameter can be filled in by the user; calculating inter-domain routing according to the corresponding service template; selecting, for each domain on a path formed by the calculated inter-domain routing, a single-domain service template for configuring the respective domain, wherein each single-domain service template comprises: a second service attribute describing a second service, a second service policy to configure the second service, and a second service parameter, wherein the second service parameter can be filled in by the user; and delivering each single-domain service template to a controller in a corresponding domain, causing the controller to configure a network element in the corresponding domain.

10 . The method according to claim 9 , wherein obtaining the service identity entered by the user comprises:
obtaining, using a service creation interface, the service identity entered by the user, wherein the service creation interface is published using a northbound interface.

11 . The method according to claim 9 , wherein calculating inter-domain routing according to the corresponding service template comprises:
obtaining a routing rule from the service policy in the corresponding service template, wherein the routing rule comprises a routing condition and a route condition; calculating the inter-domain routing according to the routing condition and the route condition; and assigning, according to an address pool policy in the service policy, an address to a port of an edge device on a path formed by the inter-domain routing.

12 . The method according to claim 9 , wherein selecting, for each domain on the path formed by the calculated inter-domain routing, the single-domain service template for configuring the respective single domain comprises:
determining whether a domain is a specified domain; and when the domain is a specified domain, selecting a first subtemplate as a single-domain service template of the domain, and when the domain is not a specified domain, selecting a second subtemplate as the single-domain service template of the domain, wherein the single-domain service template comprises the first subtemplate corresponding to the specified domain on a network and the second subtemplate corresponds to a second domain on the network, wherein the second domain is different from the specified domain, and the first subtemplate is associated with an identifier of the specified domain.

13 . The method according to claim 9 , wherein delivering the single-domain service template to the controller in the corresponding domain comprises:
delivering the single-domain service template to the controller in the corresponding domain to request intra-domain routing; receiving the intra-domain routing returned by the controller; combining the intra-domain routing and the inter-domain routing into routing information; and delivering the routing information to the controller, causing the controller to configure the network element in the domain according to the routing information and the single-domain service template.

14 . The method according to claim 13 , further comprising:
obtaining a service parameter entered by the user; before the single-domain service template is delivered to the controller in the corresponding domain, replacing the service parameter in the single-domain service template with the service parameter entered by the user; and delivering the single-domain service template after replacement to the controller in the corresponding domain.

15 . The method according to claim 13 , further comprising:
receiving a result code returned by the controller after the controller calculates the intra-domain routing; determining, according to the result code, whether the intra-domain routing is successfully calculated; when the intra-domain routing is successfully calculated, receiving the intra-domain routing returned by the controller; and when the intra-domain routing fails to be calculated, generating an error prompt.

16 . The method according to claim 13 , further comprising:
returning the routing information to an operator; obtaining confirmation information returned by the operator, wherein the confirmation information is generated after the operator confirms whether the routing information meets a requirement; when the confirmation information indicates that the routing information does not meet

Assignees

• Huawei Tech Co Ltd

Inventors

• Zhang Liya
• Zhang Liang
• Wu Jian

Classifications

• H04L41/5003

  Managing SLA; Interaction between SLA and QoS · CPC title

• H04L12/4641

  Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272) · CPC title

• H04L41/0893 Primary

  Assignment of logical groups to network elements · CPC title

• H04L41/0894

  Policy-based network configuration management · CPC title

• H04L41/0895

  Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title