CN115118585A

CN115118585A - Service deployment method, device and system

Info

Publication number: CN115118585A
Application number: CN202111164145.1A
Authority: CN
Inventors: 陈重; 董斌; 王文强
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-03-18
Filing date: 2021-09-30
Publication date: 2022-09-27

Abstract

The embodiment of the application provides a service deployment method, device and system. In the method, a controller creates a service instance corresponding to a service, and creates a first network instance and a second network instance corresponding to the service in the service instance, wherein the first network instance is a network instance corresponding to a first device, the first network instance includes a device identifier of the first device, the second network instance is a network instance corresponding to a first cloud operator edge PE, the second network instance includes a device identifier of the first cloud PE, and the first cloud PE is used for connecting to the first cloud. The method simplifies the process of virtual cloud private network service deployment, reduces the complexity of service deployment, and improves the efficiency and accuracy of service deployment.

Description

Service deployment method, device and system

The present application claims priority of chinese patent application No. 202110293083.8 entitled "a method, apparatus and system for deploying services" filed on 18/3/2021, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for deploying a service.

Background

With the increasingly remarkable trend of enterprise service clouding, cloud services are widely used, so that the attention of enterprise users is shifted from network connectivity to aspects of service quality, experience, safety and the like. Service providers and operators want to provide enterprise users with services of a virtual cloud private network that can guarantee quality of service, experience, and security. However, the service provisioning and deployment need to be planned and deployed by a technician, the service deployment complexity is high, the deployment workload is large, and the service deployment efficiency is low and errors are prone to occur.

Disclosure of Invention

The embodiment of the application provides a service deployment method, a device and a system, a service instance corresponding to a service is created through a controller, and a corresponding network instance is created in the service instance, so that the service deployment process can be simplified, the service deployment complexity is reduced, and the service deployment efficiency and accuracy are improved.

In a first aspect, an embodiment of the present application provides a method for deploying a service, where the service is a virtual cloud private network provided by a tenant. The virtual cloud private network is used for the tenant to access the first cloud. The method is executed by a controller, and the controller creates a service instance corresponding to the service; the controller creates a first network instance and a second network instance in a business instance. The first network instance and the second network instance are used to deploy the service. The first network instance is a network instance corresponding to the first device, and the first network instance includes a device identifier of the first device. The device identification of the first device includes, but is not limited to, a device serial number, ESN, of the first device, a device name of the first device, or a media access control, MAC, address of the first device. The second network instance is a network instance corresponding to the first cloud operator edge PE, and the second network instance includes the device identifier of the first cloud PE. The device identification of the first cloud PE includes, but is not limited to, a device serial number ESN of the first cloud PE, a device name of the first cloud PE, and a media access control MAC address of the first cloud PE. The first cloud PE is used for connecting with a first cloud. The first device and the first cloud PE are edge devices of the virtual private cloud network. The tenant accesses the cloud through the first device and the first cloud PE. According to the method, the deployment process of the virtual cloud private network service is simplified into the creation of the service instance, the first network instance and the second network instance, the complexity of service deployment is reduced, and the efficiency and accuracy of service deployment are improved.

Optionally, before the controller creates the service instance, connection information of the first cloud PE to the first cloud is set. The connection information includes one or more of: the device identification of the first cloud PE, the position information of the first cloud PE, the identification of a first interface of the first cloud PE, the identification of a first virtual local area network VLAN of the first cloud PE, and the first interface configuration VLAN, wherein the first cloud PE is connected with the first cloud through the first VLAN. The connection information of the first cloud PE is set in the controller, and subsequently, when the service instance is created or the second network instance is created, information such as the equipment identifier of the first cloud PE can be associated through one or more pieces of information in the connection information, so that the setting times of network parameters in a service deployment process are reduced, and the efficiency of service deployment is further improved.

Optionally, the service instance includes an identifier of the service instance. The identification of the service instance includes, but is not limited to, a name of the service instance, an identifier ID of the service instance, and the like, which may identify the service instance. The service instance further includes one or more of: type of service instance, number of created network instances, tenant's order information.

Optionally, the type of the service instance includes a single cloud or multiple clouds, where a single cloud means that the tenant can access only one cloud through the first device, and a multiple cloud means that the tenant can access multiple clouds through the first device.

Optionally, the device type of the first device is a customer premises equipment, CPE. When the first device is a first CPE, the first network instance further includes one or more of: the location information of the first CPE, the network side IP address of the first CPE, the tenant side IP address of the first CPE, and the routing information from the first CPE to the local area network of the tenant.

Optionally, the device type of the first device is a cloud PE. When the first device is a second cloud PE, the second cloud PE is configured to connect to a second cloud. Namely, the edge devices of the private virtual cloud network are the second cloud PE and the first cloud PE. The first network instance further comprises one or more of: the location information of the second cloud PE, the provider information of the second cloud, and the IP address of the second cloud to which the second cloud PE is connected, the routing information of the second cloud to which the second cloud PE is connected, and the interface service quality information of the second cloud to which the second cloud PE is connected.

Optionally, the second network instance further comprises one or more of: the location information of the first cloud PE, the provider information of the first cloud, and the IP address of the first cloud PE connected to the first cloud, the routing information of the first cloud PE connected to the first cloud, and the interface service quality information of the first cloud PE connected to the first cloud.

Optionally, the controller determines the device identifier of the first cloud PE according to the location information of the first cloud PE and connection information of the first cloud PE to the first cloud.

Optionally, the controller deploys the first network instance and the second network instance. The network operation and maintenance personnel simplify the deployment process of the virtual cloud private network service into the steps of creating a service instance, creating a first network instance and a second network instance, and deploying the first network instance and the second network instance on the control through the method. The method further simplifies the process of service deployment, reduces the complexity of service deployment, and improves the efficiency and accuracy of service deployment. Optionally, the controller sends first configuration information for configuring the service to the first device; and sending second configuration information for configuring the service to the first cloud PE.

Optionally, the controller determines the first configuration information and the second configuration information according to the first network instance, the second network instance, and the first service template. Wherein the first service template indicates configuration information of the service instance. The configuration information of the service instance includes one or more of: tunnel configuration information, virtual private network VPN instance configuration information, or routing information. The controller sets a first service template according to the type of the service instance before deploying the first network instance and the second network instance. The purpose of setting the first service template is to template the configuration information of the service corresponding to the service instance in the aspects of configuring a tunnel, configuring a VPN instance, configuring a route and the like. In the service deployment process, each type of service instance corresponds to one service template, and the configuration information of the service instance can be quickly obtained, so that the problem that network operation and maintenance personnel need to set a large amount of configuration information for each service when deploying the services is solved. The method for acquiring the configuration information through the service template simplifies the process of acquiring the configuration information in the virtual cloud private network service deployment, and further improves the efficiency of the service deployment.

Optionally, the virtual private cloud network is also used for the tenant to access the third cloud. The controller creates a third network instance in the business instance. The third network instance is a network instance corresponding to a third cloud PE, and the third network instance includes a device identification of the third cloud PE. The third cloud PE is used for connecting with a third cloud.

Optionally, before the controller creates the service instance, the controller receives a first request sent by the service deployment device. The first request is for the service deployment device to call a first application programming interface, API, of the controller to create the service instance, the first request including an identification of the service instance. The first request further includes one or more of: the type of the service instance, the identity of the tenant, and the order information of the tenant.

Optionally, before the controller creates the first network instance and the second network instance, the controller receives a second request sent by the service deployment device. The second request is for the service deployment device to call a second API of the controller to create the first network instance and/or the second network instance. The second request includes information for creating the first network instance and/or information for creating the second network instance. The information used to create the first network instance includes an identification of the service instance, an identification of the first network instance, and a device identification of the first device. The information used to create the second network instance includes an identification of the service instance, an identification of the second network instance, and an identification of the device of the first cloud PE.

Optionally, when the first device is a first CPE, the information for creating the first network instance further includes one or more of: the location information of the first CPE, the network side IP address of the first CPE, the tenant side IP address of the first CPE, and the routing information from the first CPE to the local area network of the tenant.

Optionally, a second cloud PE is used to connect to the second cloud. When the first device is a second cloud PE, the information for creating the first network instance further includes one or more of: the location information of the second cloud PE, the provider information of the second cloud, and the IP address of the second cloud where the second cloud PE is connected, the routing information of the second cloud where the second cloud PE is connected, and the interface service quality information where the second cloud PE is connected to the second cloud.

Optionally, the information for creating the second network instance comprises one or more of: the location information of the first cloud PE, the provider information of the first cloud, and the IP address of the first cloud PE connected to the first cloud, the routing information of the first cloud PE connected to the first cloud, and the interface service quality information of the first cloud PE connected to the first cloud.

Optionally, before the controller deploys the first network instance and the second network instance, the controller receives a third request sent by the service deployment apparatus. The third request is for the service deployment device to call a third API of the controller to deploy the first network instance and/or the second network instance. The third request includes information for deploying the first network instance and/or information for deploying the second network instance. The information for deploying the first network instance includes an identification of the service instance and an identification of the first network instance. The information for deploying the second network instance includes an identification of the service instance and an identification of the second network instance.

Optionally, the controller sends the deployment result information of the first network instance and/or the deployment result information of the second network instance to the service deployment device. The deployment result information of the first network instance includes, but is not limited to: the deployment failure flag of the first network instance is used to indicate that the first network instance is not deployed. The deployment result information of the second network instance includes, but is not limited to: an identification of the second network instance, a deployment success flag for the second network instance, a deployment failure reason for the second network instance.

Optionally, the controller receives a fourth request sent by the service deployment apparatus, where the fourth request is used to call a fourth API of the controller to obtain deployment result information of the first network instance and/or deployment result information of the second network instance.

Optionally, the controller sends creation result information of the service instance to the service deployment device. The creation result information of the service instance includes, but is not limited to: the service instance identification, the service instance creation success mark, the service instance creation failure mark and the service instance creation failure reason.

Optionally, the controller receives a fifth request sent by the service deployment device, where the fifth request is used to call a fifth API of the controller to obtain the creation result information of the service instance.

Optionally, the controller sends creation result information of the first network instance and/or creation result information of the second network instance to the service deployment apparatus. The creation result information of the first network instance includes, but is not limited to: an identification of the first network instance, a creation success flag for the first network instance, a creation failure reason for the first network instance. The creation result information of the second network instance includes, but is not limited to: an identification of the second network instance, a creation success flag of the second network instance, a creation failure reason of the second network instance.

Optionally, the controller receives a sixth request sent by the service deployment device, where the sixth request is used to call a sixth API of the controller to obtain the creation result information of the first network instance and/or the creation result information of the second network instance. Optionally, the virtual private cloud network is configured such that at least one site for the tenant accesses the first cloud via at least one virtual private line.

Optionally, the first cloud comprises at least one virtual private cloud VPC.

Optionally, the type of each site of the at least one site of the tenant comprises: a branched network or a cloud.

In a second aspect, an embodiment of the present application provides a method for deploying a service, where the service is to provide a virtual cloud private network for a tenant. The virtual cloud private network is used for the tenant to access the first cloud. The method is executed by a service deployment device, the service deployment device sends a first request to a controller, the first request is used for calling a first Application Programming Interface (API) of the controller to create a service instance of the service, and the first request comprises an identifier of the service instance; and sending a second request to the controller, wherein the second request is used for calling a second API of the controller to create the first network instance and/or the second network instance. The second request includes information for creating the first network instance and/or information for creating the second network instance. The information used to create the first network instance includes an identification of the service instance, an identification of the first network instance, and a device identification of the first device. The information used to create the second network instance includes an identification of the service instance, an identification of the second network instance, and an identification of the device of the first cloud PE. Wherein the first network instance and the second network instance are used to deploy the service. The first network instance is a network instance corresponding to the first device, and the first network instance comprises a device identifier of the first device. The second network instance is a network instance corresponding to the first cloud operator edge PE, and the second network instance includes the device identifier of the first cloud PE. The first cloud PE is used for connecting with a first cloud. The first device and the first cloud PE are edge devices of a virtual cloud private network. The tenant accesses the cloud through the first device and the first cloud PE. Network personnel call a service interface provided by the controller through the service deployment device to deploy services, the process of virtual cloud private network service deployment is simplified into the steps of creating a service instance, creating a first network instance and creating a second network instance, the complexity of service deployment is reduced, and the efficiency and accuracy of service deployment are improved.

Optionally, the first request further includes one or more of the following: the type of the service instance, the identity of the tenant, and the order information of the tenant.

Optionally, the device type of the first device is a customer premises equipment, CPE. When the first device is a first CPE, the information for creating the first network instance further includes one or more of: the location information of the first CPE, the network side IP address of the first CPE, the tenant side IP address of the first CPE, and the routing information from the first CPE to the local area network of the tenant.

Optionally, the device type of the first device is a cloud PE. The second cloud PE is used for connecting with a second cloud. When the first device is a second cloud PE, the information for creating the first network instance further includes one or more of: the location information of the second cloud PE, the provider information of the second cloud, and the IP address of the second cloud where the second cloud PE is connected, the routing information of the second cloud where the second cloud PE is connected, and the interface service quality information where the second cloud PE is connected to the second cloud.

Optionally, the information for creating the second network instance comprises one or more of: the location information of the first cloud PE, the provider information of the first cloud, and the IP address of the first cloud PE connected to the first cloud, the routing information of the first cloud PE connected to the first cloud, and the interface service quality information of the first cloud PE connected to the first cloud. Optionally, the service deployment device sends a third request to the controller. The third request is for the service deployment device to call a third API of the controller to deploy the first network instance and/or the second network instance. The third request includes information for deploying the first network instance and/or information for deploying the second network instance. The information for deploying the first network instance includes an identification of the service instance and an identification of the first network instance, and the information for deploying the second network instance includes an identification of the service instance and an identification of the second network instance.

Optionally, the service deployment apparatus receives creation result information of the service instance sent by the controller. The creation result information of the service instance includes, but is not limited to: the service instance identification, the service instance creation success mark, the service instance creation failure mark and the service instance creation failure reason.

Optionally, the service deployment apparatus outputs creation result information of the service instance.

Optionally, the service deployment apparatus receives creation result information of the first network instance and/or creation result information of the second network instance sent by the controller. The creation result information of the first network instance includes, but is not limited to: an identification of the first network instance, a creation success flag for the first network instance, a creation failure reason for the first network instance. The creation result information of the second network instance includes, but is not limited to: an identification of the second network instance, a creation success flag of the second network instance, a creation failure reason of the second network instance.

Optionally, the service deployment apparatus outputs creation result information of the first network instance and/or creation result information of the second network instance.

Optionally, the service deployment apparatus receives deployment result information of the first network instance and/or deployment result information of the second network instance, which are sent by the controller. The deployment result information of the first network instance includes, but is not limited to: the identification of the first network instance, the deployment success flag of the first network instance, the deployment failure flag of the first network instance, and the deployment failure reason of the first network instance. The deployment result information of the second network instance includes, but is not limited to: an identification of the second network instance, a deployment success flag for the second network instance, a deployment failure reason for the second network instance.

Optionally, the service deployment apparatus outputs deployment result information of the first network instance and/or deployment result information of the second network instance.

Optionally, the types of service instances include: the tenant may access only one cloud through the first device, and the cloud may access a plurality of clouds through the first device.

Optionally, the virtual cloud private network is used for at least one site of the tenant to access the first cloud through at least one virtual private line.

Optionally, the first cloud comprises at least one virtual private cloud VPC.

In a third aspect, an embodiment of the present application provides a device for service deployment. The business is to provide a virtual cloud private network for the tenant, and the virtual cloud private network is used for the tenant to access the first cloud. The device comprises: and the service instance creating module is used for creating the service instance corresponding to the service. The device includes: and the network instance creating module is used for creating the first network instance and the second network instance in the business instance. The first network instance and the second network instance are used to deploy the service. The first network instance is a network instance corresponding to the first device, and the first network instance includes a device identifier of the first device. The device identification of the first device includes, but is not limited to, a device serial number, ESN, of the first device, a device name of the first device, or a media access control, MAC, address of the first device. The second network instance is a network instance corresponding to the first cloud operator edge PE, and the second network instance includes the device identifier of the first cloud PE. The device identification of the first cloud PE includes, but is not limited to, a device serial number ESN of the first cloud PE, a device name of the first cloud PE, and a media access control MAC address of the first cloud PE. The first cloud PE is used for connecting with a first cloud. The first device and the first cloud PE are edge devices of a virtual cloud private network. The tenant accesses the cloud through the first device and the first cloud PE. By the device, the service deployment device deploys the virtual cloud private network service department, simplifies the service deployment process into creating the service instance, creating the first network instance and the second network instance, reduces the complexity of service deployment, and improves the efficiency and accuracy of service deployment.

Optionally, the apparatus further comprises: and the information setting module is used for setting the connection information of the first cloud PE connected with the first cloud. The connection information includes one or more of: the device identification of the first cloud PE, the position information of the first cloud PE, the identification of a first interface of the first cloud PE, and the identification of a first virtual local area network VLAN of the first cloud PE, wherein the first interface is used for connecting the first cloud PE with the first cloud, and the first VLAN is used for connecting the first cloud PE with the first cloud. By setting the connection information of the first cloud PE on the device, when a service instance is created or a second network instance is created, information such as equipment identification of the first cloud PE can be associated through one or more pieces of information in the connection information, the setting times of network parameters in a service deployment process are reduced, and the efficiency of service deployment is further improved. Optionally, the service instance comprises an identification of the service instance. The identification of the service instance includes, but is not limited to, the name of the service instance, an identifier ID of the service instance, and the like, which can identify the information of the service instance.

Optionally, the service instance further comprises one or more of: type of service instance, number of created network instances, tenant's order information.

Optionally, the device type of the first device is a customer premises equipment CPE. When the first device is a first CPE, the first network instance further includes one or more of: the location information of the first CPE, the network side IP address of the first CPE, the tenant side IP address of the first CPE, and the routing information from the first CPE to the local area network of the tenant.

Optionally, the device type of the first device is a cloud PE. The second cloud PE is used for connecting with a second cloud. When the first device is a second cloud PE, the first network instance further includes one or more of: the location information of the second cloud PE, the provider information of the second cloud, and the IP address of the second cloud to which the second cloud PE is connected, the routing information of the second cloud to which the second cloud PE is connected, and the interface service quality information of the second cloud to which the second cloud PE is connected.

Optionally, the apparatus further comprises: the network instance creating module is further configured to determine the device identifier of the first cloud PE according to the location information of the first cloud PE and the connection information of the first cloud PE connecting to the first cloud.

Optionally, the apparatus further comprises: and the network instance deployment module is used for deploying the first network instance and the second network instance. The device simplifies the deployment process of the virtual cloud private network service into the steps of creating a service instance, creating a first network instance and a second network instance, and deploying the first network instance and the second network instance on the control. The device further simplifies the flow of service deployment, reduces the complexity of service deployment, and improves the efficiency and accuracy of service deployment.

Optionally, the apparatus further comprises: the network instance deployment module is further configured to send first configuration information to the first device, where the first configuration information is used to configure a service; and the second configuration information is used for configuring the service.

Optionally, the apparatus further comprises: the network instance deployment module is further configured to determine first configuration information and second configuration information according to the first network instance, the second network instance, and the first service template. Wherein the first service template indicates configuration information of the service instance. The configuration information of the service instance includes one or more of: tunnel configuration information, virtual private network VPN instance configuration information, or routing information.

Optionally, the apparatus further comprises: and the information setting module is also used for setting a first service template according to the type of the service instance. The apparatus sets a first service template according to the type of the service instance prior to deploying the first network instance and the second network instance. The purpose of setting the first service template is to template the configuration information of the service corresponding to the service instance in the aspects of configuring a tunnel, configuring a VPN instance, configuring a route and the like. In the service deployment process, each type of service instance corresponds to one service template. The configuration information of the service instance can be quickly obtained according to the service template, so that the problem that network operation and maintenance personnel need to set a large amount of configuration information for each service when deploying the services is solved. The method for acquiring the configuration information through the service template simplifies the process of acquiring the configuration information in the virtual cloud private network service deployment, and further improves the efficiency of the service deployment. Optionally, the virtual private cloud network is also used for the tenant to access the third cloud. And the network instance creating module is also used for creating a third network instance in the business instance. The third network instance is a network instance corresponding to the third cloud PE, and the third network instance includes the device identifier of the third cloud PE. The third cloud PE is used for connecting with a third cloud.

Optionally, the apparatus further comprises: and the request message processing module is used for receiving a first request sent by the service deployment device. The first request is for invoking a first application programming interface, API, of the apparatus to create the service instance, the first request including an identification of the service instance.

Optionally, the first request further comprises one or more of: the type of the service instance, the identity of the tenant, and the order information of the tenant.

Optionally, the apparatus further comprises: and the request message processing module is further used for receiving a second request sent by the service deployment device. The second request is to invoke a second API of the apparatus to create the first network instance and/or the second network instance. The second request includes information for creating the first network instance and/or information for creating the second network instance. The information used to create the first network instance includes an identification of the service instance, an identification of the first network instance, and a device identification of the first device. The information used to create the second network instance includes an identification of the service instance, an identification of the second network instance, and an identification of the device of the first cloud PE.

Optionally, the device type of the first device is CPE. When the first device is a first CPE, the information for creating the first network instance further includes one or more of: the location information of the first CPE, the network side IP address of the first CPE, the tenant side IP address of the first CPE and the routing information from the first CPE to the local area network of the tenant.

Optionally, the device type of the first device is a cloud PE. The second cloud PE is for connecting to a second cloud. When the first device is a second cloud PE, the information for creating the first network instance further includes one or more of: the location information of the second cloud PE, the provider information of the second cloud, and the IP address of the second cloud to which the second cloud PE is connected, the routing information of the second cloud to which the second cloud PE is connected, and the interface service quality information of the second cloud to which the second cloud PE is connected.

Optionally, the information for creating the second network instance comprises one or more of: the location information of the first cloud PE, the provider information of the first cloud, and the IP address of the first cloud PE connected to the first cloud, the routing information of the first cloud PE connected to the first cloud, and the interface service quality information of the first cloud PE connected to the first cloud. Optionally, the apparatus further comprises: the request message processing module is further configured to receive a third request sent by the service deployment device. The third request is to invoke a third API of the apparatus to deploy the first network instance and/or the second network instance. The third request includes information for deploying the first network instance and/or information for deploying the second network instance. The information for deploying the first network instance includes an identification of the service instance and an identification of the first network instance. The information for deploying the second network instance includes an identification of the service instance and an identification of the second network instance.

Optionally, the apparatus further comprises: the request message processing module is further configured to receive a fourth request sent by the service deployment apparatus, where the fourth request is used to call a fourth API of the apparatus to obtain deployment result information of the first network instance and/or deployment result information of the second network instance. The deployment result information of the first network instance includes, but is not limited to: the deployment failure flag of the first network instance is used to indicate that the first network instance is not deployed. The deployment result information of the second network instance includes, but is not limited to: an identification of the second network instance, a deployment success flag for the second network instance, a deployment failure reason for the second network instance.

Optionally, the apparatus further comprises: and the result information processing module is used for sending the deployment result of the first network instance and/or the deployment result of the second network instance to the service deployment device.

Optionally, the apparatus further comprises: and the result information processing module is used for sending the creation result information of the service instance to the service deployment device. The creation result information of the service instance includes, but is not limited to: the service instance identification, the service instance creation success mark, the service instance creation failure mark and the service instance creation failure reason.

Optionally, the apparatus further comprises: and the result information processing module is used for receiving a fifth request sent by the service deployment device, and the fifth request is used for calling a fifth API of the controller to obtain the creation result information of the service instance.

Optionally, the apparatus further comprises: and the result information processing module is used for sending the creation result information of the first network instance and/or the creation result information of the second network instance to the service deployment device. The creation result information of the first network instance includes, but is not limited to: an identification of the first network instance, a creation success flag for the first network instance, a creation failure reason for the first network instance. The creation result information of the second network instance includes, but is not limited to: an identification of the second network instance, a creation success flag of the second network instance, a creation failure reason of the second network instance.

Optionally, the apparatus further comprises: and the result information processing module is used for receiving a sixth request sent by the service deployment device, and the sixth request is used for calling a sixth API of the controller to obtain the creation result information of the first network instance and/or the creation result information of the second network instance.

Optionally, the virtual private cloud network is configured such that at least one site for the tenant accesses the first cloud via at least one virtual private line.

Optionally, the first cloud comprises at least one virtual private cloud VPC.

In a fourth aspect, an embodiment of the present application provides a device for service deployment. The business is to provide a virtual cloud private network for the tenant, and the virtual cloud private network is used for the tenant to access the first cloud. The device includes: and the request message processing module is used for sending the first request to the controller. The first request is for calling a first application programming interface, API, of the controller to create a service instance of the service, the first request including an identification of the service instance. The device includes: and the request message processing module is also used for sending a second request to the controller. The second request is to invoke a second API of the controller to create the first network instance and/or the second network instance. The second request includes information for creating the first network instance and/or information for creating the second network instance. The information used to create the first network instance includes an identification of the service instance, an identification of the first network instance, and a device identification of the first device. The information used to create the second network instance includes an identification of the service instance, an identification of the second network instance, and an identification of the device of the first cloud PE. The first network instance and the second network instance are used for deploying services, and the first network instance is a network instance corresponding to the first device. The first network instance includes a device identification of the first device. The second network instance is a network instance corresponding to the first cloud operator edge PE, and the second network instance includes the device identifier of the first cloud PE. The first cloud PE is used for connecting with a first cloud. The first device and the first cloud PE are edge devices of a virtual cloud private network. The tenant accesses the cloud through the first device and the first cloud PE. The device carries out service deployment by calling the service interface provided by the controller, simplifies the process of virtual cloud private network service deployment into the creation of the service instance, the first network instance and the second network instance, reduces the complexity of service deployment, and improves the efficiency and accuracy of service deployment.

Optionally, the device type of the first device is a customer premises equipment CPE. When the first device is a first CPE, the information for creating the first network instance further includes one or more of: the location information of the first CPE, the network side IP address of the first CPE, the tenant side IP address of the first CPE, and the routing information from the first CPE to the local area network of the tenant.

Optionally, the device type of the first device is a cloud PE. The second cloud PE is for connecting to a second cloud. When the first device is a second cloud PE, the information for creating the first network instance further includes one or more of: the location information of the second cloud PE, the provider information of the second cloud, and the IP address of the second cloud where the second cloud PE is connected, the routing information of the second cloud where the second cloud PE is connected, and the interface service quality information where the second cloud PE is connected to the second cloud.

Optionally, the apparatus further comprises: the request message processing module is further configured to send a third request to the controller, where the third request is used to call a third API of the controller to deploy the first network instance and/or the second network instance. The third request includes information for deploying the first network instance and/or information for deploying the second network instance. The information for deploying the first network instance includes an identification of the service instance and an identification of the first network instance. The information for deploying the second network instance includes an identification of the service instance and an identification of the second network instance.

Optionally, the apparatus further comprises: and the result information processing module is used for receiving the creation result information of the service instance sent by the controller. The creation result information of the service instance includes, but is not limited to: the service instance identification, the service instance creation success mark, the service instance creation failure mark and the service instance creation failure reason.

Optionally, the apparatus further comprises: and the result information processing module is also used for outputting the creating result information of the service instance.

Optionally, the apparatus further comprises: and the result information processing module is also used for receiving the creation result information of the first network instance and/or the creation result information of the second network instance, which are sent by the controller. The creation result information of the first network instance includes, but is not limited to: an identification of the first network instance, a creation success flag for the first network instance, a creation failure reason for the first network instance. The creation result information of the second network instance includes, but is not limited to: an identification of the second network instance, a creation success flag of the second network instance, a creation failure reason of the second network instance.

Optionally, the apparatus further comprises: and the result information processing module is also used for outputting the creation result information of the first network instance and/or the creation result information of the second network instance. Optionally, the apparatus further comprises: and the result information processing module is also used for receiving the deployment result information of the first network instance and/or the deployment result information of the second network instance, which are sent by the controller. The deployment result information of the first network instance includes, but is not limited to: the identification of the first network instance, the deployment success flag of the first network instance, the deployment failure flag of the first network instance, and the deployment failure reason of the first network instance. The deployment result information of the second network instance includes, but is not limited to: the identification of the second network instance, the deployment success flag of the second network instance, the deployment failure flag of the second network instance, and the deployment failure reason of the second network instance. Optionally, the apparatus further comprises: and the result information processing module is also used for outputting the deployment result information of the first network instance and/or the deployment result information of the second network instance.

Optionally, the types of service instances include: the tenant may access only one cloud through the first device, and the cloud may be multiple clouds.

Optionally, the first cloud comprises at least one virtual private cloud VPC.

In a fifth aspect, an embodiment of the present application provides a service deployment system, where the system includes a controller and a service deployment device, where the controller implements the steps performed by the controller in the method in the above aspect, and the service deployment device implements the steps performed by the service deployment device in the method in the above aspect.

In a sixth aspect, an embodiment of the present application provides a communication apparatus, which includes a memory and a processor, where the memory includes instructions, and when the processor executes the instructions, the communication apparatus is caused to perform the steps performed by the controller in the method in the above aspect.

In a seventh aspect, an embodiment of the present application provides a communication device, where the communication device includes a memory and a processor, where the memory includes instructions, and when the processor executes the instructions, the communication device is caused to perform the steps performed by the service deployment apparatus in the method in the foregoing aspect. In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed by a processor, the method for deploying a service provided in any of the above aspects is implemented.

In a ninth aspect, the present application provides a computer program product containing instructions, and when the computer program product is executed by a processor, the method for deploying a service provided in any one of the above aspects and any one of the possible embodiments is implemented.

Drawings

Fig. 1(a) is a network topology and architecture diagram of a service deployment method provided in an embodiment of the present application;

fig. 1(b) is a network topology and architecture diagram of a service deployment method provided in an embodiment of the present application;

fig. 2(a) is an application scenario diagram of a service deployment method according to an embodiment of the present application;

fig. 2(b) is an application scenario diagram of a service deployment method according to an embodiment of the present application;

fig. 2(c) is an application scenario diagram of a service deployment method according to an embodiment of the present application;

fig. 3 is a schematic interface diagram illustrating setting of connection information in an embodiment of a service deployment method according to an embodiment of the present application;

fig. 4(a) is a flowchart of an embodiment of a service deployment method 400 provided in an embodiment of the present application;

fig. 4(b) is a flowchart of an embodiment of a method 4050 for deploying a service according to an embodiment of the present application;

fig. 4(c) is a flowchart of an embodiment of a method 40550 for deploying a service according to an embodiment of the present application;

fig. 5(a) is an interface schematic diagram of creating a service instance in an embodiment of a service deployment method provided in the embodiment of the present application;

fig. 5(b) is an interface schematic diagram of a service instance list in an embodiment of a method for deploying a service provided in the embodiment of the present application;

fig. 6(a) is an interface schematic diagram of creating a network instance in an embodiment of a service deployment method provided in the embodiment of the present application;

fig. 6(b) is an interface schematic diagram of creating a network instance in an embodiment of a service deployment method provided in the embodiment of the present application;

fig. 6(c) is an interface schematic diagram of creating a network instance in an embodiment of a service deployment method provided in the embodiment of the present application;

fig. 7 is a flowchart of an implementation manner of a service deployment method 700 according to an embodiment of the present application;

fig. 8 is a schematic architecture diagram of a service deployment system according to an embodiment of the present application;

fig. 9 is a schematic architecture diagram of a service deployment apparatus according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the accompanying drawings, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all embodiments.

The network architecture and the service scenario described in the embodiment of the present application are for illustrating the technical solution of the present application by way of example, and do not mean that the present application is only applicable to the following embodiments. As can be known to those skilled in the art, with the evolution of network architecture and the emergence of new service scenarios, the technical solution provided in the present application is also applicable to similar technical problems.

The terms referred to in the present application are explained below:

virtual cloud private network: a virtual cloud private network is a virtual private network that accesses the cloud for tenant or enterprise users. For example, through a virtual cloud private network, a terminal or server in a tenant site may access the cloud. The service provider establishes one or more virtual private lines from the network device on the tenant site side to the network device on the cloud side, so that a terminal or a server of the tenant site can access the cloud through the private lines. Compared with the situation that the tenant accesses the cloud through the internet line, the tenant accesses the cloud through the virtual cloud private network to obtain higher safety and reliability.

A tenant site: the tenant is a network, and a terminal or a server in the network needs to access the cloud through a virtual cloud private network. Types of tenant sites include, but are not limited to: a branched network or a cloud.

Service provider network: the service provider network is a network where the service provider deploys operation and maintenance, and the network is a network infrastructure for providing virtual cloud private network services for tenants. The service provider provides virtual private lines from the tenant side to the cloud side for the tenant services based on the network, so that terminals or servers in the tenant site can access the cloud through the virtual cloud private network.

The application scenario diagrams shown in fig. 1(a) and 1(b) describe the network topology and system architecture of the service provider system, tenant site, service provider network and cloud of the service provider of the virtual cloud private network in the present embodiment. As shown in fig. 1(a) and 1(B), a service provider provides virtual cloud private network services for tenant a, tenant B, and tenant C through a service provider system 1000. The service provider provides accessible clouds including a first cloud 50, a second cloud 60, and a third cloud 70 to the tenant. Types of clouds include, but are not limited to, public clouds, private clouds, or hybrid clouds. The cloud accessed by the tenant can be a cloud, and also can be one or more virtual Private clouds (vpcs) (virtual Private cloud) virtualized by a virtualization technology based on the cloud.

As shown in fig. 1(a) and 1(b), the tenant site type of tenant a is a branched network. The tenant site of tenant a includes a branch network 10. The branch network 10 includes a terminal 101. The tenant site type of tenant B is a branch network. The tenant site of tenant B comprises a branch network 20. The branch network 20 includes a terminal 201. Tenant site type of tenant C is cloud. Tenant site of tenant C includes cloud 80. A virtual private cloud VPC801 is included in cloud 80.

As shown in fig. 1(a), the service provider network is a multi-domain network, including a network domain a 30 and a network domain B40. Network domain a includes customer Premises equipment CPE (customer Premises equipment)301, CPE302, cloud operator edge pe (provider edge) 303. CPE301 is a network device deployed in the service provider network, on the tenant a site side. CPE302 is a network device deployed in the service provider network on the site side of tenant B. The cloud PE303 is a network device deployed in the service provider network, located on the tenant C site side. Network domain a also includes other devices of the service provider, which are not described herein. Network domain B includes network PE305, network PE306, cloud PE401, cloud PE402, and cloud PE 403. Mesh PE305 and mesh PE306 are boundary devices deployed in a service provider network, located at network domain a and network domain B. The cloud PE401 is a device deployed in the service provider network, located on the first cloud 50 side. Cloud PE402 is a device deployed in a service provider network on the second cloud 60 side. The cloud PE403 is a device deployed in the service provider network on the third cloud 70 side. Network domain B also includes other devices of the service provider, not described herein.

As shown in fig. 1(b), the service provider network is a single domain network, including the network of network domain C90. Network domain C includes CPE301, CPE302, cloud PE303, cloud PE401, cloud PE402, and cloud PE 403. CPE301 is a network device deployed in the service provider network, on the tenant a site side. CPE302 is a network device deployed in the service provider network on the site side of tenant B. The cloud PE303 is a network device deployed in the service provider network, located on the tenant C site side. The cloud PE401 is a device deployed in the service provider network, located on the first cloud 50 side. Cloud PE402 is a device deployed in a service provider network on the second cloud 60 side. The cloud PE403 is a device deployed in the service provider network, located on the third cloud 70 side. Network domain C also includes other devices of the service provider, not described herein.

The service requirements of tenant A are: the terminal 101 in the tenant a site (the branch network 10) accesses only the first cloud 50.

The service requirements of the tenant B are as follows: the terminal 201 in the tenant B site (the branch network 20) accesses the second cloud 60 and the third cloud 70.

The service requirements of tenant C are: servers in the tenant C site (cloud 80) only access the third cloud 70.

And the service provider divides the service type of the virtual cloud private network into single cloud or multiple clouds according to the service requirement of the tenant. The single cloud is that the tenant can access only one cloud through the equipment on the tenant side. The multi-cloud is that the tenant can access a plurality of clouds through the equipment on the tenant side. For example, the service requirement of tenant a is that terminal 101 only accesses first cloud 50 through CPE301, so the service type of tenant a is a single cloud; the service requirement of tenant C is that the server only accesses the third cloud 70 through the cloud PE303, so the service type of tenant C is a single cloud. As another example, the business requirement of tenant B is that the terminal has access to the second cloud 60 and the third cloud 70 through the CPE302, so the business type of tenant B is cloudy.

As shown in fig. 1(a) and fig. 1(b), the service provider system 1000 is a service deployment system provided in the embodiment of the present application, and the service provider system 1000 includes a service deployment apparatus 1100 and a controller 1200 corresponding to a service provider network. The Service deployment apparatus 1100 may be an operation and maintenance Support System oss (operations Support System), a Service Support System (Business Support System), or a network Service organizer (network Service organizer). As shown in fig. 1(a), the controller 1200 is a cross-domain controller, and is configured to manage and maintain network devices in the network domain a 30 and the network domain B40. As shown in fig. 1(b), the controller 1200 is a single domain controller, and is configured to manage, operate and maintain network devices in the network domain C90. As shown in fig. 1(a) and 1(b), the service deployment apparatus 1100 performs deployment of the virtual cloud private network service by calling one or more application Programming interfaces (apis) of the controller 1200.

In order to provide a virtual cloud private network meeting the business requirements of tenants for the tenants, a service provider needs to provide one or more virtual private lines for the tenants, and the virtual private lines are used for terminals or servers in tenant sites to access the cloud. The virtual private line is a data transmission tunnel from a network device on the tenant side to a network device on the cloud side in the service provider network. The tunnel type includes, but is not limited to, a two-layer Virtual Private Network (VPN) tunnel or a three-layer VPN tunnel. As shown in fig. 2(a), the service provider provides tenant a virtual cloud private network a, and the service type of virtual cloud private network a is a single cloud. A virtual private line 500 is created from CPE301 to cloud PE 401. Based on the virtual private line 500, the data forwarding process of the data packet from the terminal 101 of the tenant a site accessing the first cloud 50 is as follows:

1) the terminal 101 in the tenant a site sends a data packet that accesses the first cloud 50, which is forwarded to the CPE301 by the network devices in the branch network 10.

2) After receiving the packet, the CPE301 encapsulates the packet into a tunnel (the virtual private line 500 from the CPE301 to the cloud PE 401) according to the result of the resolution of the destination IP address.

3) The cloud PE401 receives the data packet through the virtual private line 500, decapsulates the data packet, and forwards the data packet to the first cloud 50 according to the routing information of the destination IP address network segment.

Through the above processing flow of the data packet, the terminal 101 of the tenant a site can access the first cloud 50. As shown in fig. 2(B), according to the service requirement of tenant B, the service provider provides tenant B with a virtual cloud private network B, and creates two virtual private lines, including a virtual private line 501 from CPE302 to cloud PE402 and a virtual private line 502 from CPE302 to cloud PE 403. As shown in fig. 2(C), according to the business requirement of tenant C, the service provider provides tenant with a virtual cloud private network C, and creates a virtual private line 503 from cloud PE303 to cloud PE 403.

If the service provider deploys the tenant service according to the existing service, the specific service deployment process is as follows:

1) network operation and maintenance personnel of a service provider receive business requirements of tenants and need to determine equipment information of network equipment deployed on a site side of the tenants and equipment information of cloud PEs corresponding to cloud services purchased by the tenants.

2) And viewing corresponding equipment resources, such as interface information of the equipment, existing configuration of the equipment and the like, on the network management system corresponding to the equipment.

3) The network operation and maintenance personnel need to check resource information of network equipment of a service provider network from equipment on the tenant site side to the cloud PE on the cloud side, and the check aims to plan a virtual private line from the equipment on the tenant site side to the cloud PE.

4) And according to the planning information, configuring tunnel configuration information, VPN instance configuration information, routing information and the like corresponding to the virtual private line for the related network equipment through which the planned virtual private line passes through by a command line, a configuration interface of a network management system or an API (application program interface) interface of the network management system.

According to the above description, network operation and maintenance staff need to plan a virtual private line according to the service requirement of each tenant, query, identify and allocate network inventory resources, and then set configuration information to relevant network equipment, and the service deployment process is complex, the workload is large, and the service cannot be rapidly deployed, so that the online speed of the tenant service is slow.

Embodiments of the present application provide a method, an apparatus, and a system for deploying a service, which simplify a flow of service deployment, reduce complexity of service deployment, and improve efficiency and accuracy of service deployment by creating a service instance corresponding to a service and creating a corresponding network instance in the service instance.

Fig. 4(a) shows a flowchart of a method 400 for service deployment, where a network architecture to which the method 400 is applied includes a controller, a service deployment apparatus, a first device, and a first cloud PE. The network architecture to which the method 400 is applied may be, for example, the network architecture shown in fig. 1(a) or fig. 1 (b). At this time, the controller may be, for example, the controller 1200 shown in fig. 1(a) or fig. 1(b), the service deployment apparatus may be, for example, the service deployment apparatus 1100 shown in fig. 1(a) or fig. 1(b), the first device may be, for example, the CPE301 or the CPE302 shown in fig. 1(a) or fig. 1(b), the first device may also be, for example, the cloud PE303 shown in fig. 1(a) or fig. 1(b), and the first cloud PE is, for example, the cloud PE401, the cloud PE402, or the cloud PE403 shown in fig. 1(a) or fig. 1 (b). The method 400 is executed by the controller, and specifically includes:

s401: a service instance corresponding to the service is created.

The controller creates a service instance corresponding to the service. In some embodiments, when the service provider receives the service requirement of the virtual cloud private network of the tenant, the network operation and maintenance personnel creates a service instance on the controller according to the service requirement. The service instance includes an identification of the service instance. The service instance identification includes, but is not limited to, the name of the service instance, the identifier id (identifier) of the service instance, and the like. The service instance also identifies a service type of the virtual cloud private network. The service instance may also include a type of the service instance. The type of the service instance indicates the service type, such as single cloud, multiple clouds, and the like. As shown in fig. 2(a), if a corresponding service instance is to be created for the virtual cloud private network a, the type of the service instance is single cloud. As shown in fig. 2(B), if a corresponding service instance is to be created for the virtual cloud private network B, the type of the service instance is a multi-cloud. The service instance may also include tenant information including, but not limited to, an identity of the tenant or order information of the tenant. The service instance may also include information of the created network instance. The information of the created network instances includes, but is not limited to, the number of network instances, the type of network instances, and the identity of network instances. The network instance is an instance corresponding to the virtual cloud private network edge device. As shown in fig. 2(a), the network instance in the service instance corresponding to the virtual cloud private network a includes, but is not limited to, a network instance corresponding to the CPE301 and a network instance corresponding to the cloud PE 401. The number of network instances that have been created describes the number of network instances that have been created in the service instance. The type of the network instance identifies the type of network device to which the network instance corresponds. As shown in fig. 2(a) -2 (c), the device types of the virtual private cloud network edge device include, but are not limited to, CPE or cloud PE. The purpose of creating a service instance is to record the service to be deployed and to provide resource information for this service. Specifically, when a service is deployed on a controller, service information needs to be described and recorded in the controller, and resource information needs to be provided for service deployment according to the service information. Such as inventory information of network devices corresponding to the services, configuration information corresponding to the services, and the like. The deployment process of the virtual cloud private line service is to create a data transmission path from the tenant site side to the cloud side, wherein the data transmission path comprises a data transmission tunnel created between devices from the tenant site side to the cloud side in the service provider network. The service instance records service type information, information of boundary nodes of the virtual cloud private network and tenant information corresponding to the service. And associating the virtual cloud private network service with the edge equipment through the service instance. In addition, the service is associated with the tenant through the service instance. The service provider can search related services according to the tenant information, and subsequent service query is facilitated. In some embodiments, the service instances are one-to-one corresponding to services that need to be deployed for tenants. For example, if the service provider provides the service of the virtual cloud private network a for the tenant a, the service provider needs to create a service instance 2000 corresponding to the service of the virtual cloud private network a in the service provider system 1000.

As an example, the service instance creation page shown in fig. 5(a) is an input box corresponding to "service instance ID" for obtaining a name of a service instance or an ID of the service instance, such as "virtual cloud private network a"; the input box corresponding to the service instance type is used for acquiring the service type, such as 'single cloud'; the input box corresponding to the tenant name is used for acquiring the name or the tenant ID of the tenant purchasing the service, such as tenant A; the input box corresponding to the "order information" is used to obtain the service order information of the tenant, such as an order identifier, for example, the order number "123456".

S403: creating a first network instance and a second network instance in the service instance, where the first network instance and the second network instance are used to deploy the service, where the first network instance is a network instance corresponding to a first device, the first network instance includes a device identifier of the first device, the second network instance is a network instance corresponding to a first cloud operator edge PE, the second network instance includes a device identifier of the first cloud PE, and the first cloud PE is used to connect to the first cloud.

The controller creates a first network instance and a second network instance in a business instance. The first network instance and the second network instance are used to deploy the service. The first network instance is a network instance corresponding to the first device. The second network instance is a network instance corresponding to the first cloud PE. The first device and the first cloud PE are edge devices of a virtual cloud private network. The first device is an edge device that connects the tenant site with the service provider network. And the tenant site accesses a virtual private line of the virtual cloud private network through the first device. The first cloud PE is a device in the service provider network that connects to the cloud side. The tenant accesses the cloud through the first device and the first cloud PE. The first device is a tenant site side device in a service provider network, the first network instance is a network instance corresponding to the first device, the first cloud PE is a network device connected to a cloud side, and the second network instance is a network instance corresponding to a first cloud operator edge PE (provider edge). The first network instance includes a device identification of the first device. The second network instance includes a device identification of the first cloud PE. For example, the service of the virtual private cloud network a relates to the tenant a site and the first cloud 50, and the service instance 2000 corresponding to the service of the virtual private cloud network a. The first device is the CPE301 in fig. 2(a), and the first network instance is a network instance corresponding to the CPE 301. The first cloud PE is cloud PE401, and the second network instance is a network instance corresponding to cloud PE 401. The controller 1200 creates the first network instance and the second network instance in the business instance 2000. In other embodiments, the service of the virtual private cloud network C corresponds to the service instance 3000. The first device is the cloud PE403 in fig. 2(c), and the first network instance is a network instance corresponding to the cloud PE 403. The first cloud PE is cloud PE402 and the second network instance is a network instance corresponding to cloud PE 402. The controller 1200 creates a first network instance and a second network instance in the service instance 3000.

The first network instance includes a device identification of the first device and the second network instance includes a device identification of the first cloud PE. The device identification includes, but is not limited to, a name of the device, a device Serial number esn (equipment Serial number) of the device, an ID of the device, or a media access control MAC address of the device, and the like.

As shown in fig. 2(a) -2 (c), the device types of the virtual private cloud network edge device include, but are not limited to, CPE or cloud PE. In some embodiments, the device type of the first device corresponding to the first network instance is CPE, i.e., the type of the tenant site is a branch network. Taking the service of the virtual cloud private network a of the tenant a in fig. 2(a) as an example, the service type of the virtual cloud private network a is a single cloud. The controller creates a service instance 2000 for virtual cloud private network a. As shown in fig. 1(a) or fig. 1(b), tenant a accesses only the first cloud 50 through CPE 301. The first network instance is the network instance to which CPE301 corresponds. The first network instance also includes a name of the first network instance, location information of the CPE301, a network-side IP address of the CPE301, a tenant-side IP address of the CPE301, routing information of the CPE301 to the branch network 10 local area network of tenant a. The network-side IP address of the CPE301 is the IP address of the interface where the CPE301 connects to the tenant a site branch network 10. The tenant-side IP address of the CPE301 is the IP address of the network device interface of the tenant a site to which the CPE301 connects. The routing information of the CPE301 to the branch network 10 of tenant a is a local area network for forwarding the access response data packet sent from the first cloud 50 from the CPE301 to the tenant a site. The routing information includes, but is not limited to, destination network segment and next hop information.

As an example, fig. 6(a) is an interface to create a first network instance corresponding to CPE 301. An input box corresponding to the network instance name on the interface is used for acquiring the name of the network instance corresponding to the CPE 301; the input box corresponding to the "location information" is used to obtain the location information of the CPE301, such as "city a"; the input box corresponding to the "device identifier" is used to obtain the device identifier information of the CPE301, for example, the ESN is "111222333"; the input box corresponding to the "network side IP address" is used to obtain the IP address "10.10.10.10/20" of the interface where the CPE301 connects to the tenant site; the input box corresponding to the "tenant-side IP address" is used to acquire the IP address "10.1.1.1/20" of the network device of the tenant site to which the CPE301 is connected; the input box corresponding to the "routing information" is used to obtain routing information from the CPE301 to the local area network of the tenant site.

The second network instance is a network instance corresponding to cloud PE 401. Cloud PE401 is used to connect a first cloud 50 to be accessed by tenant a. The second network instance further includes a name of the second network instance, location information of the cloud PE401, provider information of the cloud PE401, an IP address of the cloud PE401 connected to the first cloud 50, an interface identifier of the cloud PE401 connected to the first cloud 50, a virtual Local Area network vlan (virtual Local Area network) identifier of the cloud PE401 connected to the first cloud 50, routing information of the cloud PE401 connected to the first cloud 50, and interface service quality information of the cloud PE401 connected to the first cloud 50. The provider information of the cloud PE401 includes provider information corresponding to the first cloud 50 to which the cloud PE401 is connected. The IP address of the cloud PE401 connected to the first cloud 50 is an IP address of an interface of the cloud PE401 connected to the first cloud 50. The routing information of the cloud PE401 connected to the first cloud 50 is routing information for forwarding data from the cloud PE401 to the first cloud 50, and includes destination network segment and next hop information. The interface service quality information of the cloud PE401 connected to the first cloud 50 is information for setting quality of service qos (quality of service) of the interface of the cloud PE401 connected to the first cloud 50, and the service quality information includes, but is not limited to, information such as bandwidth, delay, jitter, and the like.

As an example, fig. 6(c) is an interface for creating a second network instance corresponding to the cloud PE 401. An input box corresponding to the network instance name on the interface is used for acquiring the name of the network instance corresponding to the cloud PE 401; the input box corresponding to the "location information" is used to acquire location information of the cloud PE401, such as "city a". The device identifier of the cloud PE401 may be manually input, and may be associated with the device identifier of the cloud PE401 through the location information of the cloud PE401 according to the connection information of the cloud PE set on the controller 1200. The input box corresponding to the "provider information" is used to acquire the provider name of the first cloud 50 to which the cloud PE401 is connected. The input box corresponding to the "IP address of cloud PE connected cloud" is used to obtain the IP address "10.1.2.20/20" of the interface of the cloud PE401 connected to the first cloud 50; the input box corresponding to the "VLAN" is used to obtain a VLAN id set by the interface of the cloud PE401 connected to the first cloud 50. The input box corresponding to the "interface quality of service information" is used to obtain QoS information set by the interface of the cloud PE401 connected to the first cloud 50. The input box corresponding to the "routing information" is used to acquire routing information from the cloud PE401 to the first cloud 50.

The process of setting the connection information of the cloud PE by the controller is as follows:

before providing the tenant with the services of the virtual cloud private network a, the virtual cloud private network B and the virtual cloud private network C, the service provider creates a network capable of connecting the tenant site a, the tenant site B and the tenant site C with the first cloud 50 and the second cloud 60, that is, the service provider network shown in fig. 1(a) or fig. 1(B), at the controller. One or more cloud PEs are deployed in the service provider network for connecting to one or more clouds in which the service provider may provide cloud services, for example, cloud PE401 is deployed for connecting to first cloud 50; deployed cloud PE402 is used to connect to second cloud 60; the deployed cloud PE403 is used to connect to the third cloud 70. In some embodiments, in order to manage the correspondence between the cloud PE and the cloud on the cloud side in the service provider network, the service provider system sets connection information of the cloud PE.

In some embodiments, the connection information may be provided in the controller 1200, and in other embodiments, the connection information may be provided in the service deployment apparatus 1100. The connection information to be set includes: the device identification of the cloud PE, the position information of the cloud PE, the identification of the interface of the cloud PE, and the identification of the VLAN of the cloud PE. The device identifier of the cloud PE includes a device name or a device identifier ID of the cloud PE. The location information of the cloud PE refers to a name or an identifier of a location of a cloud to which the cloud PE is connected, for example, a name of an area location is used as the location information, for example, a city a, a location identifier corresponding to the cloud is used as the location information, for example, an area B, and an identifier of a service provider, for example, a vendor C-001, which can correspond to the location of the cloud. The interface of the cloud PE refers to a physical interface used for connecting the cloud, such as a physical interface Gigabit Ethernet 1/0/31. The VLAN of the cloud PE identifies that the VLAN needs to be configured at the interface, so that the cloud PE connects to a corresponding cloud through the VLAN.

As an example, fig. 3 presents a connection information setting interface for setting connection information of the cloud PE401 connected to the first cloud 50 in the embodiment. Specifically, an input box corresponding to the "device name" is used to input a device identifier of the cloud PE, such as the cloud PE401 in fig. 3; an input box corresponding to the "area information" is used for the location information of the cloud PE, such as city a in fig. 3; the input box corresponding to the "interface information" is used for inputting the interface identification of the cloud PE, such as GE3/0/1 in FIG. 3; the input box corresponding to "VLAN" is used to input the VLAN identification of the cloud PE, 100 in fig. 3. After the above connectable information is set, the service provider system 1000 stores and records the connection information of the cloud PE401 connected to the first cloud 50 in the service provider network. Through the connection information, the device identification and other connection information of the cloud PE can be matched through the position information of the cloud PE. Therefore, in the process of creating the second network instance, the network operation and maintenance personnel do not need to enter the device identifier of the first cloud PE on the created interface, and can associate the device identifier of the first cloud PE through the location information of the first cloud PE.

Through the above-described procedure, the controller 1200 creates the first network instance and the second network instance in the service instance 2000. The controller determines information of the edge device of the virtual private cloud network, such as device identification, device location information, routing information and the like, by creating the first network instance and the second network instance.

As an example, the controller creates a network instance in a service instance, such as the service instance list page shown in FIG. 5 (b). The page includes information of two service instances, namely a virtual cloud private network A and a virtual cloud private network B. The "service instance type" of the "virtual cloud private network a" is "single cloud", "order information" is "123456", and the "network instance number" is "2" as the number of network instances that have been created in the service instance of the "virtual cloud private network a".

In some embodiments, as shown in fig. 2(B), the virtual private cloud network B of tenant B has a multi-cloud traffic type. The controller creates a service instance 2001 corresponding to the service of the virtual cloud private network B. A first network instance corresponding to CPE302, a second network instance corresponding to cloud PE401, and a third network instance corresponding to cloud PE402 are created in service instance 2001. The first network instance is the network instance to which CPE302 corresponds. The first network instance also includes a name of the first network instance, location information of the CPE302, a network side IP address of the CPE3012, a tenant side IP address of the CPE302, routing information of the CPE302 to a branch network 20 local area network of the tenant B. The network-side IP address of the CPE302 is the IP address of the interface where the CPE302 connects to the tenant B site branch network 20. The tenant-side IP address of the CPE302 is the IP address of the network device interface of the tenant B site to which the CPE302 is connected. The routing information of the CPE302 to the local area network of the tenant B's branch network 20 is the routing information for the data forwarded from the CPE302 to the local area network of the tenant B site, including the destination segment and the next hop information.

The second network instance is a network instance corresponding to the cloud PE401, and further includes a name of the second network instance, location information of the cloud PE401, provider information of the cloud PE401, and an IP address of the cloud PE401 connected to the first cloud 50, an interface identifier of the cloud PE401 connected to the first cloud 50, a VLAN identifier of the cloud PE401 connected to the first cloud 50, routing information of the cloud PE401 connected to the first cloud 50, and interface service quality information of the cloud PE401 connected to the first cloud 50. The third network instance is a network instance corresponding to the cloud PE402, and the third network instance includes a device identifier of the cloud PE402, a name of the third network instance, location information of the cloud PE402, vendor information of the cloud PE402, an IP address of the cloud PE402 connected to the second cloud 60, an interface identifier of the cloud PE402 connected to the second cloud 60, a VLAN identifier of the cloud PE402 connected to the second cloud 60, routing information of the cloud PE402 connected to the first cloud 60, and interface service quality information of the cloud PE402 connected to the second cloud 60.

By creating a first network instance, a second network instance, and a third network instance in the business instance 2001. As shown in fig. 5(B), in the service instance list page, the "service instance type" of the "virtual cloud private network B" in the page is "cloudy", the "order information" is "212345", and the "network instance number" is "3" as the number of network instances that have been created in the service instance of the "virtual cloud private network B".

In some embodiments, the type of the first device corresponding to the first network instance is a cloud PE, i.e., the type of the tenant site is a cloud. Such as virtual cloud private network C of tenant C in fig. 2 (C). The controller creates a service instance 2002 corresponding to the service of the virtual private cloud network C. The controller creates a first network instance and a second network instance in business instance 2002. The first device corresponding to the first network instance is a cloud PE303, and the cloud PE303 is used for connecting with a cloud 80 corresponding to the tenant C site. The first network instance further comprises a name of the first network instance, location information of the cloud PE303, provider information of the cloud PE303, an IP address of the cloud PE303 connected to the cloud 80, an interface identifier of the cloud PE303 connected to the cloud 80, a VLAN identifier of the cloud PE303 connected to the cloud 80, routing information of the cloud PE303 connected to the cloud 80, and interface service quality information of the cloud PE303 connected to the cloud 80. The provider information of the cloud PE303 includes provider information corresponding to the cloud 80 to which the cloud PE303 is connected. The IP address of the cloud PE303 connected to the cloud 80 is the IP address of the interface of the cloud PE303 connected to the cloud 80. The routing information of the cloud PE303 connected to the cloud 80 is used to forward the response data sent from the third cloud 70 from the cloud PE303 to the routing information of the tenant C site cloud 80, which includes the destination network segment and the next hop information. The interface service quality information of the cloud PE303 connected to the cloud 80 is information for setting the service quality QoS of the interface of the cloud PE303 connected to the cloud 80, and includes, but is not limited to, information such as bandwidth, delay, jitter, and the like. Fig. 6(b) is an interface for creating a first network instance corresponding to the cloud PE 303. An input box corresponding to the "network instance name" on the interface is used for acquiring the name of the network instance corresponding to the cloud PE 403. The input box corresponding to the "location information" is used to acquire location information of the cloud PE403, such as "city B". The device identification may be obtained by entering in an input box. The device identifier of the cloud PE303 may also be associated with the location information of the cloud PE303 according to the connection information of the cloud PE previously set on the controller 1200. The input box corresponding to "vendor information" is used to acquire the vendor name of the cloud 80 to which the cloud PE303 connects. The input box corresponding to the "IP address of cloud PE connection cloud" is used to acquire the IP address "10.1.1.10/20" of the interface of cloud PE303 connection cloud 80. The input box corresponding to the "VLAN" is used to obtain a VLAN id set by the interface of the cloud PE303 connected to the cloud 80. The input box corresponding to the "interface quality of service information" is used to acquire QoS information set by the interface of the cloud PE303 connected to the cloud 80. The input box corresponding to the "routing information" is used to acquire routing information from the cloud PE303 to the cloud 80. For the second network instance in the service instance 2002 corresponding to the service of the virtual cloud private network C, the network device corresponding to the second network instance is the cloud PE 403. By creating the first network instance and the second network instance in the service instance 2002, information for service deployment, such as device identification, location information, IP address, routing information, and the like of the first device on the tenant side and the first cloud PE connected to the cloud side of the service corresponding to the service instance 2002 in the service provider network has been created in the controller 1200.

By creating a first network instance and a second network instance in business instance 2002. As shown in fig. 5(b), the service instance list page includes information of the service instance of "virtual cloud private network C". The "service instance type" of the "virtual cloud private network C" is "single cloud", "order information" is "311222", and the "network instance number" is "2" as the number of network instances already created in the service instance of the "virtual cloud private network C". The method comprises the steps that a service instance corresponding to a virtual cloud private network service is created through a controller, and a first network instance and a second network instance corresponding to the service instance are created in the service instance, so that the service deployment process is simplified, the service deployment complexity is reduced, and the service deployment efficiency and accuracy are improved.

S405: deploying the first network instance and the second network instance.

Optionally, the controller deploys the first network instance and the second network instance. Through the steps described in S401 and S405, the controller has created a service instance corresponding to the service, and the first network instance and the second network instance. The controller determines the edge device and the service type of the virtual cloud private network corresponding to the service to be deployed. Network operation and maintenance personnel need to set tunnel configuration information, VPN instance configuration information and routing information for the determined first device and the first cloud PE according to the service type. The method for setting configuration information for the first device and the first cloud PE includes, but is not limited to:

1) and configuring specific parameters to the first device and the first cloud PE through a tunnel configuration interface on the controller. And configuring specific parameters to the first device and the first cloud PE through a VPN instance configuration interface of the controller. And configuring specific parameters to the first device and the first cloud PE through a routing configuration interface of the controller.

2) A management IP address of the first device or the first cloud PE is obtained by the controller. And logging in a command line interface of the equipment to configure the tunnel configuration information, the VPN instance configuration information and the routing information through a management IP address of the first equipment or the first cloud PE and a protocol or a tool of remote login.

3) The controller sends first configuration information for configuring the service to the first device, and the controller sends second configuration information for configuring the service to the first cloud PE.

A method 4050 of determining the first configuration information and the second configuration information according to the first network instance and the second network instance, see the steps shown in fig. 4 (b):

s4051: and acquiring the equipment information of the first equipment and the equipment information of the first cloud PE according to the first network instance and the second network instance.

The first device and the first cloud PE are edge devices of a virtual cloud private network. The tenant accesses the cloud through the first device and the first cloud PE. When the tenant site type is a branch network, the type of the first device is CPE. The service provider provides the first device for the tenant, and the tenant deploys the first device on the site side of the tenant. When the tenant site type is cloud, the type of the first device is cloud PE. The service provider may deploy the cloud PE in a service provider network for the tenant.

The first network instance comprises information such as device identification of the first device, and the second network instance comprises information such as device identification of the first cloud PE. The controller may determine device information of the first device and device information of the first cloud PE according to the first network instance and the second network instance, that is, determine and acquire device information of an endpoint device of the virtual private line. The controller may query the controller for device information for the first device based on the identity of the first device in the first network instance. The device information of the first device includes, but is not limited to, an identifier of the first device, a management IP address of the first device, location information of the first device, routing information of the first device, and network resource information of the first device. The network resource information of the first device includes, but is not limited to, port information of the first device, memory occupancy information of the first device, CPU usage information of the first device, and validated configuration information of the first device. The first cloud PE information includes, but is not limited to, an identifier of the first cloud PE, a management IP address of the first cloud PE, location information of the first cloud PE, information of the first cloud PE connecting to the cloud, routing information of the first cloud PE, and network resource information of the first cloud PE. The network resource information of the first cloud PE includes, but is not limited to, port information of the first cloud PE, memory occupancy information of the first cloud PE, CPU utilization information of the first cloud PE, and validated configuration information of the first cloud PE.

As shown in fig. 2(a), the traffic of the virtual cloud private network a of tenant a, i.e., the terminals in the tenant site user network 10 of tenant a, accesses the first cloud through the virtual private line 500. The service type of the virtual cloud private network a is a single cloud, that is, the tenant a can only access one cloud. According to the step described in S403, the controller 1200 has created a first network instance corresponding to the CPE301 and a second network instance corresponding to the cloud PE 401. The controller 1200 acquires the device information of the CPE301 and the device information of the cloud PE401 from the first network instance and the second network instance.

S4053: and acquiring the network resource information according to the equipment information of the first equipment and the equipment information of the first cloud PE.

The controller acquires the device information of the first device and the device information of the first cloud PE according to the steps described in S4051. The controller may determine a set of networks or a set of network domains that the virtual private line passes through based on network topology information of the service provider network. The purpose of the controller to acquire the network resource information is to acquire resource information of a network or a network domain through which the virtual private line passes.

As shown in fig. 1(a), after the controller 1200 obtains the device information of the CPE301 and the device information of the cloud PE401 according to the first network instance and the second network instance, the CPE301 and the cloud PE401 pass through a network domain a and a network domain B, and the network domains are integrated into a network domain a and a network domain B. The controller 1200 acquires network resource information of each network domain in the network domain set. The network resource information includes, but is not limited to, network topology information of a network domain, device information of each network element in the network domain, and network connection information existing between network element devices. The device information includes, but is not limited to, a name of the network element device, a type of the network element device, an ESN of the network element device, a management IP address of the network element device, a network location of the network element device, and so on. The network connection information includes, but is not limited to, physical links and logical links. Logical link types include, but are not limited to, a two-layer VPN tunnel, a three-layer VPN tunnel. The controller 1200 obtains network resource information of the network domain a, which includes but is not limited to: 1. network topology information of network domain a; 2. each network element device information in the network domain A comprises an ESN serial number of the network element device, a type of the network element device, a device model, version information, a management IP address, an MAC address and the like; 3. the port information of each network element device comprises physical port and logic port information; 4. the link information between network elements includes physical link information, tunnel information, VPN information, and the like.

S4055: and acquiring the first configuration information and the second configuration information.

The controller acquires the device information of the first device, the device information of the first cloud PE, and the network resource information according to the steps described in S4051 and S4053. The controller acquires the first configuration information and the second configuration information based on the information. The first configuration information is configuration information corresponding to the first device. The first configuration information includes tunnel configuration information, VPN instance configuration information, and routing information that the first device needs to be configured to implement the service. The second configuration information is configuration information corresponding to the first cloud PE. The second configuration information includes tunnel configuration information, VPN instance configuration information, and routing information that the first cloud PE needs to be configured to implement the service. The specific acquisition procedure is as shown in fig. 4(c) method 40550:

s40551: and acquiring the tunnel configuration information in the first configuration information and the tunnel configuration information in the second configuration information.

The controller acquires the tunnel configuration information in the first configuration information and the tunnel configuration information in the second configuration information. The tunnel configuration information in the first configuration information and the tunnel configuration information in the second configuration information are used for configuring a data transmission tunnel from the first device to the first cloud PE. The tunnel configuration information in the first configuration information is the tunnel configuration information that needs to be configured on the first device. The tunnel configuration information in the second configuration information is tunnel configuration information that needs to be configured on the first cloud PE.

In some embodiments, the service provider may define a virtual private line in the single cloud traffic as a three-layer VPN tunnel according to the service plan. For example, the virtual private line 500 in the virtual cloud private network a of tenant a is a three-layer VPN tunnel. The controller 1200 obtains network resource information such as network topology information of the network domain a and the network domain B through the obtained network resource information of the network domain a and the network domain B. The controller 1200 analyzes whether the existing network resource information satisfies the establishment of a three-layer VPN tunnel from the CPE301 to the cloud PE401 according to the network resource information. If the analysis result indicates that the network resources can meet the requirement of generating a three-layer VPN tunnel from the CPE301 to the cloud PE401, the controller 1200 provides a configuration interface, and the network personnel plans the three-layer VPN tunnel configuration information that needs to be configured on the CPE301 and the cloud PE401 according to the configuration interface.

In other embodiments, the controller 1200 obtains the tunnel configuration information of the CPE301 and the cloud PE401 according to the service template corresponding to the service instance of the single cloud. The service template is set prior to deployment of the service instance. Before deploying the service instance, the controller sets a service template according to the service type corresponding to the service instance. The service template indicates configuration information of the service. Configuration information for the traffic includes, but is not limited to, tunnel configuration information, VPN instance configuration information, or routing information. The traffic template includes, but is not limited to, tunnel configuration information, VPN instance configuration information, or routing information. And when the service instance is created, the corresponding service template is associated through the type of the service. When the controller creates the first network instance and the second network instance in the service instance, because the service instance already generates the association relationship with the service template, the first network instance and the second network instance also generate the association relationship with the service template. The traffic templates include, but are not limited to, a tunnel sub-traffic template, a VPN instance sub-traffic template, and a route sub-traffic template. The first configuration information and the second configuration information may be determined from the first network instance, the second network instance, and the respective sub-service templates. The controller splits the configuration information in the tunnel sub-service template to the first device and the first cloud PE according to the dimensions of the first device and the first cloud PE, and generates tunnel configuration information in the first configuration information and tunnel configuration information in the second configuration information.

In this way, the tunnel configuration information in the first configuration information corresponding to the first device and the tunnel configuration information in the second configuration information corresponding to the first cloud PE are obtained. If the analysis result cannot meet the requirement of establishing an end-to-end tunnel to bear the three-layer VPN link, management personnel can be prompted to reselect the cloud PE or perform operations such as equipment capacity expansion and the like, and then tunnel configuration information is acquired. S40553: and acquiring VPN instance configuration information in the first configuration information and VPN instance configuration information in the second configuration information.

The controller obtains VPN instance configuration information in the first configuration information and VPN instance configuration information in the second configuration information. The VPN instance configuration information in the first configuration information and the VPN instance configuration information in the second configuration information are used to configure a VPN instance from the first device and the first cloud PE. The VPN instance configuration information in the first configuration information is VPN instance configuration information that needs to be configured on the first device. The VPN instance configuration information in the second configuration information is VPN instance configuration information that needs to be configured on the first cloud PE. In some embodiments, the virtual private line type of the virtual cloud private network a of the tenant a is a three-layer VPN, and configuration information of virtual private networks of the CPE301 and the cloud PE401, which is forwarded by a vrf (VPN Routing and forwarding), needs to be acquired; in other embodiments, the Virtual Private line type of the Virtual Private cloud network a of tenant a is a layer two VPN, and configuration information of the ethernet Private Virtual network evpn (ethernet Virtual Private network) instance evi (evpn instance) or the Virtual Switch instance vsi (Virtual Switch instance) of CPE301 and cloud PE401 needs to be acquired. Controller 1200 may provide a configuration interface according to which network personnel plan VPN instance configuration information that needs to be configured at CPE301 and cloud PE 401.

In some examples, the controller 1200 obtains VPN configuration information of the CPE301 and the cloud PE401 according to a service template corresponding to a service instance of a single cloud. The service template is set prior to deployment of the service instance. Before deploying the service instance, the controller sets a service template according to the service type corresponding to the service instance. The service template indicates configuration information of the service. The configuration information of the traffic includes, but is not limited to, tunnel configuration information, VPN instance configuration information, or routing information. The traffic template includes, but is not limited to, tunnel configuration information, VPN instance configuration information, or routing information. And when the service instance is created, the corresponding service template is associated through the type of the service. When the controller creates the first network instance and the second network instance in the service instance, because the service instance already generates the association relationship with the service template, the first network instance and the second network instance also generate the association relationship with the service template. The traffic templates include, but are not limited to, a tunnel sub-traffic template, a VPN instance sub-traffic template, and a route sub-traffic template. The first configuration information and the second configuration information may be determined from the first network instance, the second network instance, and the respective sub-service templates. The controller splits the configuration information in the VPN instance sub-service template to the first device and the first cloud PE according to the dimensionality of the first device and the first cloud PE, and generates VPN instance configuration information in the first configuration information and VPN instance configuration information in the second configuration information.

S40555: and acquiring the routing configuration information in the first configuration information and the routing configuration information in the second configuration information.

The controller acquires the routing configuration information in the first configuration information and the routing configuration information in the second configuration information. The routing configuration information in the first configuration information and the routing configuration information in the second configuration information are used for configuring routing information of the first device and the first cloud PE. And the routing information of the first equipment is used for data forwarding routing from the first equipment to the tenant site side. The routing information of the first cloud PE is used for a data forwarding route from the first cloud PE to the cloud side. The routing configuration information in the first configuration information is routing configuration information that needs to be configured on the first device. The routing configuration information in the second configuration information is routing configuration information that needs to be configured on the first cloud PE.

And the routing configuration information in the first configuration information is used for enabling the first equipment to forward the response data message from the cloud side to the tenant site. For example, the CPE301 forwards the data packet from the first cloud 50 destined for the tenant site terminal 101 to the tenant a site branch network 10 according to the routing configuration information. The routing configuration information in the second configuration information is used for forwarding data messages from the access cloud of the tenant site side to the cloud by the cloud PE. For example, a data packet from a tenant a site accessing the first cloud 50 is forwarded at cloud PE401 to the first cloud 50 according to the routing configuration information. Controller 1200 provides a configuration interface according to which network personnel plan routing configuration information that needs to be configured on CPE301 and cloud PE 401.

In some embodiments, the controller 1200 obtains the routing configuration information of the CPE301 and the cloud PE401 according to the service template corresponding to the service instance of the single cloud. The service template is set prior to deployment of the service instance. Before deploying the service instance, the controller sets a service template according to the service type corresponding to the service instance. The service template indicates configuration information of the service. The configuration information of the traffic includes, but is not limited to, tunnel configuration information, VPN instance configuration information, or routing information. The traffic template includes, but is not limited to, tunnel configuration information, VPN instance configuration information, or routing information. When the service instance is created, the corresponding service template is associated through the type of the service. When the controller creates the first network instance and the second network instance in the service instance, because the service instance already generates the association relationship with the service template, the first network instance and the second network instance also generate the association relationship with the service template. The traffic templates include, but are not limited to, a tunnel sub-traffic template, a VPN instance sub-traffic template, and a route sub-traffic template. The first configuration information and the second configuration information may be determined from the first network instance, the second network instance, and the respective sub-service templates. The controller splits the configuration information in the routing sub-service template to the first device and the first cloud PE according to the dimensionality of the first device and the first cloud PE, and generates routing configuration information in the first configuration information and routing configuration information in the second configuration information.

By performing the steps described in S40551 to S40555, the controller 1200 acquires the first configuration information and the second configuration information.

S4057: and sending the first configuration information to the first equipment, and sending the second configuration information to the first cloud PE.

The controller sends the first configuration information to the first device, and the controller sends the second configuration information to the first cloud PE.

The state of the first device or the first cloud PE includes managed by the controller or not managed by the controller. When the device is in the state managed by the controller, the controller may perform management operation and maintenance operations such as configuration management or device state query on the device. When the device is not managed by the controller, the controller cannot acquire information of the device, and thus cannot manage the configuration of the device.

In some embodiments, when the controller queries that both the first device and the first cloud PE are already in a managed state, that is, the controller may send configuration information to the first device and the first cloud PE, after the controller receives a message to deploy a network instance, the controller sends the first configuration information to the first device, and the controller sends the second configuration information to the first cloud PE. The mode of sending the Configuration information by the controller can be simple Network Management protocol (snmp), telecommunication Network protocol (telnet), Network Configuration protocol (Network Configuration protocol), or private Configuration protocol based on user Datagram protocol (udp)/user Datagram protocol (tcp). When the first device and the first cloud PE receive and validate the first configuration information and the second configuration information. As shown in fig. 1(a) or fig. 1(b), the CPE301 on the tenant a site side and the cloud PE401 on the first cloud 50 side validate the first configuration information and the second configuration information, and then a virtual private line 500 is established between the CPE301 and the cloud PE401 to connect the tenant a site branching network 10 and the first cloud 50.

It should be noted that, when the state of the first device or the first cloud PE is in a state not managed by the controller, the first device or the first cloud PE may not be managed by the controller, and may not receive and validate the first configuration information or the second configuration information. The controller prestores the configuration information, and after the first device or the first cloud PE finishes the admission online process, the controller sends the first configuration information or the second configuration information to the first device or the first cloud PE to finish the deployment of the first network instance or the second network instance.

The first configuration information corresponding to the first equipment and the second configuration information corresponding to the first cloud PE are automatically obtained through the controller according to the first network instance, the second network instance and the preset information, and the complexity of manual configuration is reduced and the efficiency of service deployment is improved through a method that the controller issues the first configuration information and the second configuration information.

Fig. 7 is a flowchart illustrating a method 700 for service deployment according to the present application. The method is executed by the service deployment apparatus 1100 and the controller 1200 in fig. 2, and the specific method includes:

s701: the service deployment device sends a first request to a controller, wherein the first request is used for calling a first Application Programming Interface (API) of the controller to create a service instance of the service, and the first request comprises the identification of the service instance.

The service deployment device sends a first request to the controller. The first request is for invoking a first API of a controller to create a service instance of the service. The first request includes an identification of the service instance.

In some embodiments, the service provider performs virtual cloud private network service deployment using the service deployment apparatus 1100 shown in fig. 1(a), and the controller 1200 provides an API of the service deployment apparatus for the service deployment apparatus 1100 to call to complete the service deployment. The controller 1200 provides a service instance creation API to third party systems. The service deployment apparatus 1100 sends a first request to the controller 1200, where the first request is used to call a first API of the controller 1200, such as a service instance creation API, to create a service instance of a service. The first request comprises the identification of the service instance, and the identification of the service instance comprises the name of the service instance or the ID of the service instance and other information capable of identifying the service instance. The first request further includes the type of the service instance, an identifier of the tenant, order information of the tenant, and the like. Types of business instances include single cloud, multiple clouds, and the like. The tenant identity includes the tenant name, tenant ID, etc. The order information of the tenant includes an order number, an order name, and the like.

S703: the controller receives a first request sent by a service deployment device.

The controller receives a first request sent by a service deployment device. The first request is for invoking a first API of a controller to create a service instance of the service.

In some examples, the controller 1200 as shown in fig. 1(a) receives a first request sent by the service deployment apparatus 1100.

S705: the controller creates the service instance.

The controller creates the service instance based on the identity of the service instance in the first request.

In some examples, after the controller 1200 shown in fig. 1(a) receives the first request, the corresponding service instance is created according to the identifier of the service instance in the first request. For a specific process of the controller 1200 creating the service instance, reference may be made to the related description of S401, which is not described herein again.

S707: and the controller sends the creation result information of the service instance to a service deployment device.

And the controller sends the creation result information of the service instance to the service deployment device.

In some examples, after creating a service instance, the controller 1200 shown in fig. 1(a) sends creation result information of the service instance to the service deployment apparatus 1100. The creation result information of the service instance includes, but is not limited to: the service instance identification, the service instance creation success mark, the service instance creation failure mark and the service instance creation failure reason.

Optionally, in some embodiments, after completing creating the service instance, the controller 1200 shown in fig. 1(a) sends result information of creating the service instance to the service deployment apparatus 1100.

Optionally, in other embodiments, the service deployment apparatus 1100 shown in fig. 1(a) sends a service instance creation query request to the controller 1200, where the query request is used to query result information created by the service instance of the controller 1200. After receiving the query request, the controller 1200 sends the creation result information of the service instance to the service deployment apparatus 1100.

S709: and the service deployment device receives the creation result information of the service instance sent by the controller.

And the service deployment device receives the creation result information of the service instance sent by the controller.

Optionally, in some embodiments, after completing creating the service instance, the controller 1200 shown in fig. 1(a) sends result information of creating the service instance to the service deployment apparatus 1100. The service deployment apparatus 1100 receives the creation result information of the service instance sent by the controller.

Optionally, in other embodiments, the service deployment apparatus 1100 shown in fig. 1(a) sends a service instance creation query request to the controller 1200, where the query request is used to query result information created by the service instance of the controller 1200. After receiving the query request, the controller 1200 sends the creation result information of the service instance to the service deployment apparatus 1100. The service deployment apparatus 1100 receives the creation result information of the service instance sent by the controller.

S711: and the service deployment device outputs the creation result information of the service instance.

And the service deployment device outputs the creation result information of the service instance.

Optionally, the service deployment apparatus 1100 shown in fig. 1(a) may display the acquired service instance creation result information on a display interface of the service deployment apparatus 1100 or a display interface of a third-party system. The service deployment apparatus 1100 may also export the acquired service instance creation result information to network personnel through word, txt, excel, and other file formats. The service deployment apparatus 1100 may also open the acquired service instance creation result information to other service systems through the API. The way in which the service deployment apparatus outputs the creation result information of the service instance is not described here one by one.

S713: a second request sent by the service deployment device to the controller, the second request for calling a second API of the controller to create the first network instance and a second network instance.

And the service deployment device sends a second request to the controller. The second request is to call a second API of the controller to create the first network instance and a second network instance.

In some embodiments, the controller 1200 as shown in fig. 1(a) provides a second API for third party systems to create network instances that supports the creation of one network instance or the batch creation of multiple network instances.

When the second API supports only creation of one network instance, the service deployment apparatus 1100 shown in fig. 1(a) sends a second request to the controller 1200, where the second request is used to call the second API of the controller 1200 to create the first network instance. The second request comprises information for creating a first network instance, wherein the information for creating the first network instance comprises an identifier of the service instance, an identifier of the first network instance and an equipment identifier of the first equipment, the first network instance is used for deploying the service, the first network instance is a network instance corresponding to the first equipment, and the first network instance comprises the equipment identifier of the first equipment. The service deployment apparatus 1100 sends a second request to the controller 1200, where the second request is further used to call a second API of the controller 1200 to create a second network instance. The second request includes information for creating a second network instance, the information for creating the second network instance including an identification of the service instance, an identification of the second network instance, and a device identification of the first cloud PE, wherein the second network instance is used to deploy the service. The second network instance is a network instance corresponding to the first cloud PE, the second network instance includes a device identifier of the first cloud PE, and the first cloud PE is configured to connect to the first cloud.

When the second API only supports batch creation of multiple network instances, the service deployment apparatus 1100 sends a second request to the controller 1200, where the second request is used to call the second API of the controller 1200 to create the first network instance and the second network instance. The second request comprises information for creating a first network instance and information for creating a second network instance, the information for creating the first network instance comprises an identifier of the service instance, an identifier of the first network instance and an equipment identifier of the first equipment, and the information for creating the second network instance comprises an identifier of the service instance, an identifier of the second network instance and an equipment identifier of the first cloud PE, wherein the first network instance and the second network instance are used for deploying the service, the first network instance is a network instance corresponding to the first equipment, the first network instance comprises an equipment identifier of the first equipment, the second network instance is a network instance corresponding to the first cloud PE, the second network instance comprises an equipment identifier of the first cloud PE, and the first cloud PE is used for connecting with the first cloud.

S715: the controller receives a second request sent by the service deployment device.

The controller receives a second request sent by the service deployment device. The second request is to call a second API of the controller to create the first network instance and a second network instance.

Optionally, when the second API of the controller only supports creation of one network instance, the controller 1200 shown in fig. 1(a) receives a second request sent by the service deployment apparatus 1100, where the second request is used to call the second API of the controller to create the first network instance, and the second request includes an identifier of the service instance, an identifier of the first network instance, and an equipment identifier of the first equipment.

Optionally, when the second API of the controller supports only creation of one network instance, the controller 1200 receives a second request sent by the service deployment apparatus 1100, where the second request is used to call the second API of the controller to create a second network instance, and the second request includes an identifier of the service instance, an identifier of the second network instance, and an identifier of the device of the first cloud PE.

Optionally, when the second API of the controller supports batch creation of multiple network instances, the controller 1200 receives a second request sent by the service deployment apparatus 1100, where the second request is used to call the second API of the controller to create the first network instance and the second network instance, and the second request includes an identifier of the service instance, an identifier of the first network instance, an identifier of the second network instance, and an equipment identifier of the first cloud PE.

S717: a controller creates the first network instance and a second network instance.

The controller creates a first network instance and a second network instance based on the second request.

After the controller 1200 shown in fig. 1(a) receives the second request, the controller 1200 creates a first network instance and a second network instance. The specific process of the controller 1200 creating the network instance may refer to the related description of S403, and is not described herein again.

S719: and the controller sends the creation result information of the first network instance and the creation result of the second network instance to a service deployment device.

The controller sends the creation result information of the first network instance and the creation result of the second network instance to the service deployment device.

The controller 1200 shown in fig. 1(a) sends the creation result information of the first network instance and the creation result of the second network instance to the service deployment apparatus 1100.

Optionally, in some embodiments, after completing creating the network instance, the controller 1200 shown in fig. 1(a) sends result information of creating the network instance, such as result information of creating the first network instance and result information of creating the second network instance, to the service deployment apparatus 1100.

Optionally, in other embodiments, the service deployment apparatus 1100 shown in fig. 1(a) sends a network instance creation query request to the controller 1200, where the query request is used to query result information created by the network instance of the controller 1200. After receiving the query request, the controller 1200 sends the creation result information of the network instance to the service deployment apparatus 1100.

S721: and the service deployment device receives the creation result information of the first network instance and the creation result of the second network instance which are sent by the controller.

And the service deployment device receives the creation result information of the first network instance and the creation result of the second network instance, which are sent by the controller. The creation result information of the first network instance includes, but is not limited to: the identification of the first network instance, a creation success flag for the first network instance, a creation failure flag for the first network instance, and a creation failure reason for the first network instance. The creation result information of the second network instance includes, but is not limited to: an identification of the second network instance, a creation success flag of the second network instance, a creation failure reason of the second network instance.

Optionally, in some embodiments, after completing creating the network instance, the controller 1200 shown in fig. 1(a) sends result information of creating the network instance, such as result information of creating the first network instance and result information of creating the second network instance, to the service deployment apparatus 1100. The service deployment apparatus 1100 receives the creation result information of the network instance sent by the controller.

Optionally, in other embodiments, the service deployment apparatus 1100 shown in fig. 1(a) sends a network instance creation query request to the controller 1200, where the query request is used to query result information created by the network instance of the controller 1200. After receiving the query request, the controller 1200 sends the creation result information of the network instance to the service deployment apparatus 1100. The service deployment apparatus 1100 receives the creation result information of the network instance sent by the controller.

S723: and the service deployment device outputs the creation result information of the first network instance and the creation result of the second network instance.

And the service deployment device outputs the creation result information of the first network instance and the creation result of the second network instance.

Optionally, as shown in fig. 1(a), the service deployment apparatus 1100 may display the acquired network instance creation result information through a display interface of the service deployment apparatus 1100 or a display interface of a third-party system. The service deployment apparatus 1100 may also export the acquired network instance creation result information to network personnel through word, txt, excel, and other file formats. The service deployment apparatus 1100 may also open the acquired network instance creation result information to other service systems through an API or the like. The way in which the service deployment apparatus outputs the creation result information of the network instance is not described here one by one.

S725: a third request sent by a service deployment device to the controller, the third request for calling a third API of the controller to deploy the first network instance and the second network instance.

And the service deployment device sends a third request to the controller. The third request is to invoke a third API of the controller to deploy the first network instance and the second network instance.

In some embodiments, the controller 1200 as shown in fig. 1(a) provides a third API to a third party system for deploying a network instance, the third API for deploying one network instance and/or deploying multiple network instances in bulk.

When the third API is used to deploy only one network instance, the service deployment apparatus 1100 shown in fig. 1(a) sends a third request to the controller 1200, and the third request is used to call the third API of the controller 1200 to deploy the first network instance. The third request includes information for deploying the first network instance, the information for deploying the first network instance including an identification of the service instance and an identification of the first network instance.

When the third API is used to deploy only one network instance, the service deployment apparatus 1100 shown in fig. 1(a) sends a third request to the controller 1200, and the third request is used to call the third API of the controller 1200 to deploy a second network instance. The third request includes information for deploying the second network instance, the information for deploying the second network instance including an identification of the service instance and an identification of the second network instance.

When the third API is used to deploy multiple network instances in batch, the service deployment apparatus 1100 shown in fig. 1(a) sends a third request to the controller 1200, where the third request is used to call the third API of the controller 1200 to deploy the first network instance and the second network instance. The third request includes information for deploying the first network instance and information for deploying the second network instance, the information for deploying the first network instance including an identification of a service instance and an identification of a first network instance. The information for deploying the second network instance includes an identification of the service instance and an identification of the second network instance.

S727: the controller receives a third request sent by the service deployment device.

The controller receives a third request sent by the service deployment device. The third request is to invoke a third API of the controller to deploy the first network instance and the second network instance.

The controller 1200 receives the third request sent by the service deployment apparatus 1100.

In some embodiments, controller 1200 provides a third API to third party systems for deploying a network instance, a third API for deploying one network instance and/or a bulk deployment of multiple network instances.

When the third API is used to deploy only one network instance, the third request is used to invoke the third API of the controller 1200 to deploy the first network instance. The third request includes information for deploying the first network instance, the information for deploying the first network instance including an identification of the service instance and an identification of the first network instance.

When the third API is used to deploy only one network instance, the third request is used to invoke the third API of the controller 1200 to deploy the second network instance. The third request includes information for deploying the second network instance, the information for deploying the second network instance including an identification of the service instance and an identification of the second network instance.

When the third API is used to deploy multiple network instances in bulk, the third request is used to call the third API of the controller 1200 to deploy the first network instance and the second network instance. The third request includes information for deploying the first network instance and information for deploying the second network instance, the information for deploying the first network instance including an identification of a service instance and an identification of a first network instance. The information for deploying the second network instance includes an identification of the service instance and an identification of the second network instance.

S7029: a controller deploys the first network instance and the second network instance.

The controller deploys the first network instance and the second network instance according to a third request.

After receiving the third message, the controller 1200 shown in fig. 1(a) deploys the first network instance and the second network instance. The specific process of the controller 1200 for deploying the first network instance and the second network instance may refer to the related description of S405, and is not described herein again.

S731: and the controller sends the deployment result information of the first network instance and the deployment result information of the second network instance to a service deployment device.

And the controller sends the deployment result information of the first network instance and the deployment result information of the second network instance to the service deployment device. The deployment result information of the first network instance includes, but is not limited to: the deployment failure flag of the first network instance is used to indicate that the first network instance is not deployed. The deployment result information of the second network instance includes, but is not limited to: an identification of the second network instance, a deployment success flag for the second network instance, a deployment failure reason for the second network instance.

The controller 1200 shown in fig. 1(a) transmits the deployment result information of the first network instance and the deployment result information of the second network instance to the service deployment apparatus 1100.

Optionally, in some embodiments, after completing the deployment of the network instance, the controller 1200 shown in fig. 1(a) sends result information of the deployment of the network instance, such as result information of the deployment of the first network instance and result information of the deployment of the second network instance, to the service deployment apparatus 1100.

Optionally, in other embodiments, the service deployment apparatus 1100 shown in fig. 1(a) sends a network instance deployment query request to the controller 1200, where the query request is used to query result information of network instance deployment of the controller 1200. After receiving the query request, the controller 1200 sends deployment result information of the network instance to the service deployment apparatus 1100.

S733: and the service deployment device receives the deployment result information of the first network instance and the deployment result information of the second network instance, which are sent by the controller.

And the service deployment device receives the deployment result information of the first network instance and the deployment result information of the second network instance, which are sent by the controller.

Optionally, in some embodiments, after completing the deployment of the network instance, the controller 1200 shown in fig. 1(a) sends result information of the deployment of the network instance, such as result information of the deployment of the first network instance and result information of the deployment of the second network instance, to the service deployment apparatus 1100. The service deployment apparatus 1100 receives the deployment result information of the network instance sent by the controller.

Optionally, in other embodiments, the service deployment apparatus 1100 shown in fig. 1(a) sends a network instance deployment query request to the controller 1200, where the query request is used to query result information of network instance deployment of the controller 1200. After receiving the query request, the controller 1200 sends deployment result information of the network instance to the service deployment apparatus 1100. The service deployment apparatus 1100 receives the deployment result information of the network instance sent by the controller.

S735: and outputting the deployment result information of the first network instance and the deployment result information of the second network instance.

And the service deployment device outputs the deployment result information of the first network instance and the deployment result information of the second network instance.

Optionally, the service deployment apparatus 1100 shown in fig. 1(a) may display the acquired network instance deployment result information through a display interface of the service deployment apparatus 1100 or a display interface of a third-party system. The service deployment apparatus 1100 may also export the acquired network instance deployment result information to network personnel through word, txt, excel, and other file formats. The service deployment apparatus 1100 may also open the acquired network instance deployment result information to other service systems through an API or the like. The manner in which the service deployment apparatus outputs the deployment result information of the network instance is not described one by one here.

S737: a fourth request sent by the service deployment device to the controller, the fourth request being used to call a fourth API of the controller to delete the service instance.

And the service deployment device sends a fourth request to the controller. The fourth request is to call a fourth API of the controller to delete the service instance.

The service deployment apparatus 1100 shown in fig. 1(a) sends a fourth request to the controller 1200, where the fourth request is used to call a fourth API of the controller 1200 to delete the service instance and the network instance in the service instance. The fourth API of the controller 1200 is used to delete an already created service instance. The fourth request includes an identification of the service instance to be deleted.

S739: the controller receives a fourth request sent by the service deployment device.

The controller receives a fourth request sent by the service deployment device. The fourth request is to call a fourth API of the controller to delete the service instance.

The controller 1200 shown in fig. 1(a) receives the fourth request sent by the service deployment apparatus 1100.

S741: the controller deletes the service instance.

The controller deletes the service instance.

After receiving the fourth request sent by the service deployment apparatus 1100, the controller 1200 shown in fig. 1(a) deletes the service instance specified in the fourth request.

The specific method comprises the following steps:

the controller firstly judges whether the service instances to be deleted have deployed network instances. And if the deployed network instance does not exist, the controller deletes the corresponding service instance on the controller according to the service instance identifier carried in the fourth request.

And if the service instance to be deleted contains the deployed network instance, the controller acquires the information of the corresponding service instance according to the identifier of the service instance. The information of the service instance comprises the type of the service instance, the information of the created network instance, the order information of the tenant and the like. And acquiring the created network instance through the created network instance information in the service instance information. And acquiring the network equipment corresponding to the network instance through the created information of the network instance. Before deleting the configuration information related to the service instance in the network device, the controller needs to determine whether there is a network resource shared by other service instances in the network device, and if there is no shared network resource, the controller deletes the configuration information related to the service instance, deletes the network instance related to the service instance, and completes the deletion operation. If the shared network resource exists, the controller does not delete the configuration information and finishes the deletion operation. The configuration information includes tunnel configuration information, VPN instance information, and routing information.

The service instance corresponding to the virtual cloud private network service is directly created by calling the service API of the controller at the service deployment device, and the corresponding first network instance and second network instance are created in the service instance, so that the interaction times between the service deployment device and the controller are reduced by deploying the first network instance and the second network instance, the complexity of manual configuration and the difficulty of service deployment are reduced, and the efficiency of service deployment is improved.

Fig. 8 is a schematic structural diagram of a service deployment system 800 according to an embodiment of the present application. The service deployment system 600 is configured to perform operations performed by the service deployment apparatus 1100 and the controller 1200 shown in fig. 7, for example, the service deployment systems in the embodiments corresponding to fig. 4(a) -4 (c). As shown by the modules corresponding to the solid line boxes in fig. 8, the service deployment system 800 includes the following modules.

A service instance creating module 8001, configured to create a service instance corresponding to the service.

A network instance creating module 8002, configured to create a first network instance and a second network instance in the service instance, where the first network instance and the second network instance are used to deploy the service, where the first network instance is a network instance corresponding to a first device, the first network instance includes a device identifier of the first device, the second network instance is a network instance corresponding to a first cloud operator edge PE, the second network instance includes a device identifier of the first cloud PE, and the first cloud PE is used to connect to the first cloud.

In some embodiments, as shown by the modules corresponding to the dashed boxes in fig. 8, the service deployment system 800 further includes: information setting block 8003. An information setting module 8003, configured to set connection information that the first cloud PE connects to the first cloud, where the connection information includes one or more of the following: the device identification of the first cloud PE, the location information of the first cloud PE, the identification of a first interface of the first cloud PE, and the identification of a first VLAN of the first cloud PE, wherein the first interface is used for the first cloud PE to connect with the first cloud, and the first VLAN is used for the first cloud PE to connect with the first cloud. The information setting module 8003 is further configured to set the first service template according to the type of the service instance.

In some embodiments, as shown by the modules corresponding to the dashed boxes in fig. 8, the service deployment system 800 further includes: network instance deployment module 8004.

A network instance deployment module 8004, configured to deploy the first network instance and the second network instance. The network instance deployment module 8004 is further configured to send first configuration information to the first device. The first configuration information is used for configuring the service. The network instance deployment module 8004 is further configured to send second configuration information to the first cloud PE, where the second configuration information is used to configure the service. The network instance deployment module 8004 is further configured to determine the first configuration information and the second configuration information according to the first network instance, the second network instance, and a first service template. Wherein the first service template indicates configuration information of the service instance, and the configuration information of the service instance includes one or more of: tunnel configuration information, virtual private network VPN instance configuration information, or routing information.

In some embodiments, as shown by the modules corresponding to the dashed boxes in fig. 8, the service deployment system 800 further includes: request message processing block 8005.

The request message processing module 8005 is configured to receive a first request sent by a service deployment device. The first request is for invoking a first application programming interface, API, of the controller to create the service instance, the first request including an identification of the service instance.

The request message processing module 8005 is further configured to receive a second request sent by the service deployment apparatus. The second request is to invoke a second API of the controller to create the first network instance and/or a second network instance. The second request includes information for creating the first network instance and/or information for creating the second network instance. The information for creating the first network instance includes an identification of the service instance, an identification of the first network instance, and a device identification of the first device. The information for creating the second network instance includes an identification of the service instance, an identification of the second network instance, and a device identification of the first cloud PE.

The request message processing module 8005 is further configured to receive a third request sent by the service deployment apparatus. The third request is to invoke a third API of the controller to deploy the first network instance and/or the second network instance. The fourth request includes information for deploying the first network instance and/or information for deploying the second network instance. The information for deploying the first network instance includes an identification of the service instance and an identification of the first network instance. The information for deploying the second network instance includes an identification of the service instance and an identification of the second network instance.

The request message processing module 8005 is further configured to receive a fourth request sent by the service deployment apparatus, where the fourth request is used to call a fourth API of the controller to obtain a deployment result of the first network instance and/or a deployment result of the second network instance.

In some embodiments, the request message processing block 8005 is further configured to send the first request to the controller. The first request is used for calling a first Application Programming Interface (API) of the controller to create a service instance of the service, and the first request comprises an identification of the service instance.

The request message processing module 8005 is further configured to send a second request to the controller. The second request is to invoke a second API of the controller to create the first network instance and/or the second network instance. The second request includes information for creating the first network instance and/or information for creating the second network instance. The information for creating the first network instance includes an identification of the service instance, an identification of the first network instance, and a device identification of the first device. The information for creating the second network instance includes an identification of the service instance, an identification of the second network instance, and a device identification of the first cloud PE. Wherein the first network instance and the second network instance are used to deploy the service. The first network instance is a network instance corresponding to a first device, and the first network instance comprises a device identifier of the first device. The second network instance is a network instance corresponding to a first cloud operator edge PE, and the second network instance includes a device identifier of the first cloud PE. The first cloud PE is used for connecting the first cloud. And a third request to the controller, the third request to invoke a third API of the controller to deploy the first network instance and/or the second network instance. The third request includes information for deploying the first network instance and/or information for deploying the second network instance. The information for deploying the first network instance includes an identification of the service instance and an identification of the first network instance. The information for deploying the second network instance includes an identification of the service instance and an identification of the second network instance.

In some embodiments, as shown by the modules corresponding to the dashed boxes in fig. 8, the service deployment system 800 further includes: result information processing block 8006.

A result information processing module 8006, configured to send the deployment result of the first network instance and/or the deployment result of the second network instance to the service deployment apparatus.

In some embodiments, the result information processing module 8006 is further configured to receive creation result information of the service instance sent by the controller. And the service instance creation module is also used for outputting the creation result information of the service instance. And the controller is further configured to receive creation result information of the first network instance and/or a creation result of the second network instance sent by the controller. And the server is further used for outputting the creation result information of the first network instance and/or the creation result of the second network instance. And the controller is further configured to receive deployment result information of the first network instance and/or deployment result information of the second network instance sent by the controller. And the system is further configured to output deployment result information of the first network instance and/or deployment result information of the second network instance.

The respective modules shown in fig. 8 may be software functional modules or virtual functional modules, or may be hardware modules. In some embodiments, the modules in the service deployment system 800 may be deployed in the same physical device; in other embodiments, the modules in the service deployment system 800 may be deployed in multiple different physical devices. The various modules in the service deployment system 800 may be hardware modules or a combination of software and hardware modules. For example, the service instance creation module 8001, the network instance creation module 8002, the information setting module 8003, the network instance deployment module 8004, the request message processing module 8005, and the result information processing module in the service deployment system 800 may be deployed in one physical device for executing the method 700 executed by the controller 1200 in the embodiment shown in fig. 7. The request message processing module 8005 and the result information processing module in the service deployment system 800 may be deployed in another physical device, and are used to execute the method 700 executed by the service deployment apparatus 1100 in the embodiment shown in fig. 7.

Fig. 9 is a schematic structural diagram of a service deployment apparatus according to an embodiment of the present application. The service deployment apparatus 900 shown in fig. 9 is configured to perform the operations performed by the service deployment apparatus 1100 or the controller 1200 in the foregoing embodiments, for example, the embodiment corresponding to fig. 7. As shown in fig. 9, the apparatus 900 comprises at least one processor 901, a connection 902, a memory 903, and at least one network interface 904. Memory 903 is used to store program modules and data. In some embodiments, the program modules stored in the memory 903 include a service instance creation module 9031 and a network instance creation module 9032, as shown by the program modules corresponding to the solid line boxes in fig. 9.

A service instance creation module 9031, configured to create a service instance corresponding to the service when executed by the processor 901.

When executed by the processor 901, the network instance creating module 9032 is configured to create, in the service instance, a first network instance and a second network instance, where the first network instance and the second network instance are used to deploy the service, where the first network instance is a network instance corresponding to a first device, the first network instance includes a device identifier of the first device, the second network instance is a network instance corresponding to a first cloud operator edge PE, the second network instance includes a device identifier of the first cloud PE, and the first cloud PE is used to connect to the first cloud.

In other embodiments, the program modules stored in the memory 903 include one or more of the following: an information setting module 9033, a network instance deployment module 9034, a request message processing module 9035, and a result information processing module 9036.

When executed by processor 901, an information setting module 9033 is configured to set connection information of the first cloud PE to connect to the first cloud, where the connection information includes one or more of: the device identification of the first cloud PE, the location information of the first cloud PE, the identification of a first interface of the first cloud PE, and the identification of a first VLAN of the first cloud PE, wherein the first interface is used for the first cloud PE to connect with the first cloud, and the first VLAN is used for the first cloud PE to connect with the first cloud. The information setting module 8003 is further configured to set the first service template according to the type of the service instance.

When executed by the processor 901, the network instance deployment module 9034 is configured to execute the method step executed by the controller as described in S405 in the method 400 shown in fig. 4(a), which is not described herein again.

In some embodiments, when executed by processor 901, request message processing module 9035 is configured to perform the method steps performed by controller 1200 as described in method 700 shown in fig. 7, which are not described herein again.

In some embodiments, when executed by the processor 901, the request message processing module 9035 is configured to execute the method steps performed by the service deployment apparatus 1100 described in the method 700 shown in fig. 7, which are not described herein again.

When executed by processor 901, result information processing module 9036 is configured to execute the method steps performed by service deployment apparatus 1100 described in method 700 shown in fig. 7, which are not described herein again. The processor 901 is, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), a Network Processor (NP), a Graphics Processing Unit (GPU), a neural-Network Processing Unit (NPU), a Data Processing Unit (DPU), a microprocessor, or one or more integrated circuits for implementing the present disclosure. For example, the processor 901 may include an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. PLDs are, for example, Complex Programmable Logic Devices (CPLDs), field-programmable gate arrays (FPGAs), General Array Logic (GAL), or any combination thereof. Which may implement or perform the various logical blocks, modules, and circuits described in connection with the embodiment disclosure of the present application. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors in combination, a DSP and a microprocessor in combination, or the like.

The service deployment apparatus 900 may further comprise a connection line 902. Connecting lines 902 are used to communicate information between the components of service deployment apparatus 900. The bus may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 9, but this does not indicate only one bus or one type of bus.

The Memory 903 is, for example, a read-only Memory (ROM) or other type of static storage device that can store static information and instructions, such as a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, such as an electrically erasable programmable read-only Memory (EEPROM), a compact disk read-only Memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory 903 is, for example, independent and connected to the processor 901 via a bus. The memory 903 may also be integrated with the processor 901.

Network interface 904 may use any transceiver or the like for communicating with other devices or a communication network, such as an ethernet, a Radio Access Network (RAN), or a Wireless Local Area Network (WLAN). The network interface 904 may include a wired communication interface and may also include a wireless communication interface. Specifically, the network interface 904 may be an Ethernet (Ethernet) interface, a Fast Ethernet (FE) interface, a Gigabit Ethernet (GE) interface, an Asynchronous Transfer Mode (ATM) interface, a Wireless Local Area Network (WLAN) interface, a cellular network communication interface, or a combination thereof. The ethernet interface may be an optical interface, an electrical interface, or a combination thereof. In this embodiment, the network interface 904 may be used for the service deployment apparatus 900 to communicate with other devices.

In particular implementations, processor 901 may include one or more CPUs as one embodiment. Each of these processors may be a single-core processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In one embodiment, the service deployment apparatus 900 may include a plurality of processors. Each of these processors may be a single core processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores that process data, such as computer program instructions.

In a specific implementation, as an embodiment, the service deployment apparatus 900 may further include an output device and an input device. An output device, which is in communication with the processor 901, may display information in a variety of ways. For example, the output device may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device, which is in communication with the processor 901, may receive user input in a variety of ways. For example, the input device may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.

The service deployment apparatus 900 shown in fig. 9 is used to perform the operations performed by the service deployment apparatus in the foregoing embodiments, for example, the embodiment corresponding to fig. 7. As shown in fig. 9, the service deployment apparatus 900 includes at least one processor 901, which by executing a computer readable program in a memory 903, can cause the service deployment apparatus 900 to perform operations performed by a plurality of embodiments described above, such as the controller 1200 or the service deployment apparatus 1100 in the embodiment corresponding to fig. 7.

The order of operations in the description and claims of the present application, and in the drawings described above, is not limited to the specific order or sequence described. It is to be understood that the data so used are in parallel, or may be permuted as appropriate, so that the described embodiments can be practiced in sequences other than those illustrated or described in the figures.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.

Some embodiments of the present application provide a computer program product, which, when executed by a computer, enables the computer to perform the operations performed by the service deployment system in the various embodiments of the present application.

Some embodiments of the present application provide a computer-readable storage medium, such as a hard disk, a memory, a flash memory, and the like. The computer storage medium has computer readable instructions stored therein. The computer readable instructions, when executed by a computer, enable the operations performed by the service deployment system in the various embodiments of the present application to be performed.

Some embodiments of the present application provide a service deployment system including a plurality of modules, where the plurality of modules cooperate to perform operations performed by the service deployment system in the embodiments of the present application. The modules may be in the same hardware device or different hardware devices.

The above description is only a preferred embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by one skilled in the art within the technical scope of the present application are intended to be covered by the scope of the present application.

Claims

1. A method for deploying a service, wherein the service is a virtual cloud private network provided for a tenant, and the virtual cloud private network is used for the tenant to access a first cloud, and the method is executed by a controller, and the method comprises the following steps:

creating a service instance corresponding to the service;

creating a first network instance and a second network instance in the service instance, where the first network instance and the second network instance are used for deploying the service, where the first network instance is a network instance corresponding to a first device, the first network instance includes a device identifier of the first device, the second network instance is a network instance corresponding to a first cloud operator edge PE, the second network instance includes a device identifier of the first cloud PE, and the first cloud PE is a network instance corresponding to a first cloud PE

For connecting to the first cloud.

2. The method of claim 1, wherein prior to creating the service instance, the method further comprises:

setting connection information of the first cloud PE to connect the first cloud, wherein the connection information comprises one or more of the following items:

a device identifier of the first cloud PE, location information of the first cloud PE, an identifier of a first interface of the first cloud PE, an identifier of a first VLAN of the first cloud PE, the first interface configuring the first VLAN,

the first cloud PE is connected with the first cloud through the first VLAN.

3. The method of claim 1 or 2, wherein the service instance comprises an identification of the service instance.

4. The method of claim 3, wherein the service instance further comprises one or more of: the type of the service instance, the number of created network instances, and order information of the tenant.

5. The method according to any one of claims 1 to 4, wherein the type of the service instance includes a single cloud or multiple clouds, the single cloud being one cloud only accessible to the tenant through the first device, the multiple clouds being multiple clouds accessible to the tenant through the first device.

6. The method according to any of claims 1-5, wherein the first equipment is a first customer premises equipment, CPE.

7. The method of claim 6, wherein the first network instance further comprises one or more of: the location information of the first CPE, the network side IP address of the first CPE, the tenant side IP address of the first CPE, and the routing information from the first CPE to the local area network of the tenant.

8. The method according to any of claims 1-5, wherein the first device is a second cloud PE, the second cloud PE configured to connect to a second cloud.

9. The method of claim 8, wherein the first network instance further comprises one or more of: the location information of the second cloud PE, the provider information of the second cloud, and the IP address of the second cloud to which the second cloud PE is connected, the routing information of the second cloud to which the second cloud PE is connected, and the interface service quality information of the second cloud to which the second cloud PE is connected.

10. The method of any of claims 1-9, wherein the second network instance further comprises one or more of: the location information of the first cloud PE, the provider information of the first cloud, and the IP address of the first cloud where the first cloud PE is connected to the first cloud, the routing information of the first cloud and the interface service quality information of the first cloud where the first cloud PE is connected to the first cloud.

11. The method according to any one of claims 1-10, further comprising:

and determining the equipment identifier of the first cloud PE according to the position information of the first cloud PE and the connection information of the first cloud PE for connecting the first cloud PE with the first cloud.

12. The method according to any one of claims 1-11, further comprising:

deploying the first network instance and the second network instance.

13. The method according to any of claims 1-12, wherein the deploying the first network instance and the second network instance comprises:

sending first configuration information for configuring the service to the first device;

and sending second configuration information for configuring the service to the first cloud PE.

14. The method of claim 13, further comprising:

determining the first configuration information and the second configuration information according to the first network instance, the second network instance and a first service template, wherein the first service template indicates configuration information of the service instance, and the configuration information of the service instance includes one or more of: tunnel configuration information, virtual private network VPN instance configuration information, or routing information.

15. The method of claim 14, wherein prior to deploying the first network instance and the second network instance, the method further comprises:

and setting the first service template according to the type of the service instance.

16. The method of any of claims 1-15, wherein the virtual private cloud network is further used for the tenant to access a third cloud, the method further comprising:

and creating a third network instance in the service instance, wherein the third network instance is a network instance corresponding to a third cloud PE, the third network instance comprises the equipment identifier of the third cloud PE, and the third cloud PE is used for connecting with the third cloud.

17. The method of any of claims 1-16, wherein prior to creating the service instance, the method further comprises:

receiving a first request sent by a service deployment device, wherein the first request is used for calling a first Application Programming Interface (API) of the controller to create the service instance, and the first request comprises the identification of the service instance.

18. The method of claim 17, wherein the first request further comprises one or more of: the type of the service instance, the identity of the tenant, and the order information of the tenant.

19. The method according to claim 17 or 18, wherein before creating the first network instance and the second network instance, the method further comprises:

receiving a second request sent by the service deployment device, where the second request is used to call a second API of the controller to create the first network instance and/or the second network instance, the second request includes information for creating the first network instance and/or information for creating the second network instance, the information for creating the first network instance includes an identifier of the service instance, an identifier of the first network instance, and an equipment identifier of the first equipment, and the information for creating the second network instance includes an identifier of the service instance, an identifier of the second network instance, and an equipment identifier of the first cloud PE.

20. The method according to any of claims 17-19, wherein prior to deploying the first network instance and the second network instance, the method further comprises:

receiving a third request sent by the service deployment device, where the third request is used to call a third API of the controller to deploy the first network instance and/or the second network instance, the third request includes information for deploying the first network instance and/or information for deploying the second network instance, the information for deploying the first network instance includes an identifier of the service instance and an identifier of the first network instance, and the information for deploying the second network instance includes an identifier of the service instance and an identifier of the second network instance.

21. The method according to any one of claims 17-20, further comprising:

and sending the deployment result information of the first network instance and/or the deployment result information of the second network instance to the service deployment device.

22. The method according to any one of claims 17-21, further comprising:

receiving a fourth request sent by the service deployment device, where the fourth request is used to call a fourth API of the controller to obtain deployment result information of the first network instance and/or deployment result information of the second network instance.

23. The method of any of claims 1-22, wherein at least one site of the virtual cloud private network for the tenant accesses the first cloud via at least one virtual private line.

24. The method of any of claims 1-23, wherein the first cloud comprises at least one Virtual Private Cloud (VPC).

25. The method of any of claims 1-24, wherein the type of each site of the tenant's at least one site comprises: a branched network or a cloud.

26. A method for deploying a service, wherein the service is a virtual cloud private network provided for a tenant, and the virtual cloud private network is used for the tenant to access a first cloud, the method is performed by a service deploying device, and the method comprises the following steps:

sending a first request to a controller, the first request being used for calling a first Application Programming Interface (API) of the controller to create a service instance of the service, the first request comprising an identification of the service instance;

sending a second request to the controller, the second request being used for calling a second API of the controller to create a first network instance and/or a second network instance, wherein the first network instance and/or the second network instance are used for deploying the service, the first network instance is a network instance corresponding to a first device, the second network instance is a network instance corresponding to a first cloud operator edge PE, the first cloud PE is used for connecting with the first cloud, the second request comprises information for creating the first network instance and/or information for creating the second network instance, the information for creating the first network instance comprises an identification of the service instance, an identification of the first network instance and an equipment identification of the first device, and the information for creating the second network instance comprises an identification of the service instance, an identification of the first network instance, an identification of the second network instance, The identifier of the second network instance and the device identifier of the first cloud PE, the first network instance including the device identifier of the first device, the second network instance including the device identifier of the first cloud PE.

27. The method of claim 26, wherein the first request further comprises one or more of: the type of the service instance, the identity of the tenant, and the order information of the tenant.

28. The method according to claim 26 or 27, wherein the first equipment is a first customer premises equipment, CPE.

29. The method of claim 28, wherein the information for creating the first network instance further comprises one or more of: the location information of the first CPE, the network side IP address of the first CPE, the tenant side IP address of the first CPE, and the routing information from the first CPE to the local area network of the tenant.

30. The method of any of claims 26-29, wherein the first device is a second cloud PE, and wherein the second cloud PE is configured to connect to a second cloud.

31. The method of claim 30, wherein the information for creating the first network instance further comprises one or more of: the location information of the second cloud PE, the provider information of the second cloud, and the IP address of the second cloud to which the second cloud PE is connected, the routing information of the second cloud to which the second cloud PE is connected, and the interface service quality information of the second cloud to which the second cloud PE is connected.

32. The method of any of claims 26-31, wherein the information for creating the second network instance comprises one or more of: the location information of the first cloud PE, the provider information of the first cloud, and the IP address of the first cloud where the first cloud PE is connected to the first cloud, the routing information of the first cloud and the interface service quality information of the first cloud where the first cloud PE is connected to the first cloud.

33. The method according to any one of claims 26-32, further comprising:

sending a third request to the controller, the third request being for calling a third API of the controller to deploy the first network instance and/or the second network instance, the third request including information for deploying the first network instance and/or information for deploying the second network instance, the information for deploying the first network instance including an identification of the service instance and an identification of the first network instance, and the information for deploying the second network instance including an identification of the service instance and an identification of the second network instance.

34. The method according to any one of claims 26-33, further comprising:

and receiving the creation result information of the service instance sent by the controller.

35. The method of claim 34, further comprising:

and outputting the creating result information of the service instance.

36. The method according to any one of claims 26-35, further comprising:

and receiving the creation result information of the first network instance and/or the creation result information of the second network instance sent by the controller.

37. The method of claim 36, further comprising:

and outputting the creation result information of the first network instance and/or the creation result information of the second network instance.

38. The method according to any one of claims 26-37, further comprising:

and receiving the deployment result information of the first network instance and/or the deployment result information of the second network instance sent by the controller.

39. The method of claim 38, further comprising:

and outputting the deployment result information of the first network instance and/or the deployment result information of the second network instance.

40. The method according to any of claims 26 to 39, wherein the type of the service instance comprises: the tenant may access only one cloud through the first device, or multiple clouds, where the tenant may access multiple clouds through the first device.

41. The method of any of claims 26-40, the virtual cloud private network for at least one site of the tenant accessing the first cloud through at least one virtual private line.

42. The method of any of claims 26-41, wherein the first cloud comprises at least one Virtual Private Cloud (VPC).

43. The method of any of claims 26-42, wherein the type of each site of the tenant's at least one site comprises: a branched network or a cloud.

44. An apparatus for service deployment, wherein the service is to provide a virtual private cloud network for a tenant, and wherein the virtual private cloud network is used for the tenant to access a first cloud, and wherein the apparatus comprises:

a service instance creating module, configured to create a service instance corresponding to the service;

a network instance creating module, configured to create a first network instance and a second network instance in the service instance, where the first network instance and the second network instance are used to deploy the service, where the first network instance is a network instance corresponding to a first device, the first network instance includes a device identifier of the first device, the second network instance is a network instance corresponding to a first cloud operator edge PE, the second network instance includes a device identifier of the first cloud PE, and the first cloud PE is used to connect to the first cloud.

45. The apparatus of claim 44, further comprising:

an information setting module, configured to set connection information for connecting the first cloud PE to the first cloud, where the connection information includes one or more of the following: the device identification of the first cloud PE, the position information of the first cloud PE, the identification of a first interface of the first cloud PE, and the identification of a first Virtual Local Area Network (VLAN) of the first cloud PE, wherein the first interface is used for connecting the first cloud PE with the first cloud, and the first VLAN is used for connecting the first cloud PE with the first cloud.

46. The apparatus according to claim 44 or 45, wherein the service instance comprises an identification of the service instance.

47. The apparatus of any one of claims 44-46, further comprising:

a network instance deployment module to deploy the first network instance and the second network instance.

48. The apparatus of any one of claims 44-47, further comprising:

the network instance deployment module is further configured to send first configuration information for configuring the service to the first device; and further configured to send second configuration information for configuring the service to the first cloud PE.

49. The apparatus of any one of claims 44-48, further comprising:

the network instance deployment module is further configured to determine the first configuration information and the second configuration information according to the first network instance, the second network instance, and a first service template, where the first service template indicates configuration information of the service instance, and the configuration information of the service instance includes one or more of: tunnel configuration information, virtual private network VPN instance configuration information, or routing information.

50. The apparatus as claimed in claim 49, further comprising:

the information setting module is further configured to set the first service template according to the type of the service instance.

51. The apparatus of any one of claims 44-50, further comprising:

the request message processing module is used for receiving a first request sent by a service deployment device, the first request is used for calling a first Application Programming Interface (API) of the device to create the service instance, and the first request comprises the identification of the service instance.

52. The apparatus of claim 51, further comprising:

the request message processing module is further configured to receive a second request sent by the service deployment apparatus, where the second request is used to call a second API of the apparatus to create the first network instance and/or the second network instance, the second request includes information used to create the first network instance and/or information used to create the second network instance, the information used to create the first network instance includes an identifier of the service instance, an identifier of the first network instance, and an equipment identifier of the first equipment, and the information used to create the second network instance includes an identifier of the service instance, an identifier of the second network instance, and an equipment identifier of the first cloud PE.

53. The apparatus of claim 51 or 52, further comprising:

the request message processing module is further configured to receive a third request sent by the service deployment apparatus, where the third request is used to call a third API of the apparatus to deploy the first network instance and/or the second network instance, the third request includes information for deploying the first network instance and/or information for deploying the second network instance, the information for deploying the first network instance includes an identifier of the service instance and an identifier of the first network instance, and the information for deploying the second network instance includes an identifier of the service instance and an identifier of the second network instance.

54. The apparatus of any one of claims 51-53, further comprising:

the request message processing module is further configured to receive a fourth request sent by the service deployment apparatus, where the fourth request is used to call a fourth API of the apparatus to obtain deployment result information of the first network instance and/or deployment result information of the second network instance.

55. The apparatus of claims 51-54, further comprising:

and the result information processing module is used for sending the deployment result information of the first network instance and/or the deployment result information of the second network instance to the service deployment device.

56. An apparatus for service deployment, wherein the service is to provide a virtual cloud private network for a tenant, and the virtual cloud private network is used for the tenant to access a first cloud, the apparatus comprising:

a request message processing module, configured to send a first request to a controller, where the first request is used to call a first application programming interface API of the controller to create a service instance of the service, and the first request includes an identifier of the service instance;

the request message processing module is further configured to send a second request to the controller, where the second request is used to call a second API of the controller to create a first network instance and/or a second network instance, where the first network instance and/or the second network instance is used to deploy the service, the first network instance is a network instance corresponding to a first device, the second network instance is a network instance corresponding to a first cloud operator edge PE, the first cloud PE is used to connect to the first cloud, the second request includes information for creating the first network instance and/or information for creating the second network instance, and the information for creating the first network instance includes an identifier of the service instance, an identifier of the first network instance, and an identifier of the first device, the information for creating the second network instance includes an identifier of the service instance, an identifier of the second network instance, and a device identifier of the first cloud PE, the first network instance includes a device identifier of the first device, and the second network instance includes a device identifier of the first cloud PE.

57. The apparatus of claim 56, further comprising:

the request message processing module is further configured to send a third request to the controller, where the third request is used to call a third API of the controller to deploy the first network instance and/or the second network instance, the third request includes information for deploying the first network instance and/or information for deploying the second network instance, and the information for deploying the first network instance includes an identifier of the service instance and an identifier of the first network instance,

the information for deploying the second network instance includes an identification of the service instance and an identification of the second network instance.

58. The apparatus of claim 56 or 57, further comprising:

and the result information processing module is used for receiving the creation result information of the service instance sent by the controller.

59. The apparatus of any one of claims 56-59, further comprising:

and the result information processing module is also used for outputting the creation result information of the service instance.

60. The apparatus of any one of claims 56-59, further comprising:

the result information processing module is further configured to receive creation result information of the first network instance and/or creation result information of the second network instance, which are sent by the controller.

61. The apparatus of any one of claims 56-60, further comprising:

the result information processing module is further configured to output creation result information of the first network instance and/or creation result information of the second network instance.

62. The apparatus of any one of claims 56-61, further comprising:

the result information processing module is further configured to receive the deployment result information of the first network instance and/or the deployment result information of the second network instance, which is sent by the controller.

63. The apparatus of any one of claims 56-62, further comprising:

the result information processing module is further configured to output deployment result information of the first network instance and/or deployment result information of the second network instance.

64. A service deployment system comprising a controller and a service deployment apparatus, wherein the controller implements the method of any one of claims 1 to 25 and the service deployment apparatus implements the method of any one of claims 26 to 43.

65. A communication device for use as a controller, the communication device comprising:

a memory comprising instructions;

a processor that, when executing the instructions, causes the communication device to implement the method of any of claims 1-25.

66. A communication device for use as a service deployment device, the communication device comprising:

a memory comprising instructions;

a processor that when executing the instructions causes the communication device to implement the method of any of claims 26-43.

67. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-43.

68. A computer program product comprising a computer program which, when executed by a processor, carries out the method of any one of claims 1 to 43.