WO2022193897A1 - 一种业务的部署方法、装置及系统 - Google Patents

一种业务的部署方法、装置及系统 Download PDF

Info

Publication number
WO2022193897A1
WO2022193897A1 PCT/CN2022/076601 CN2022076601W WO2022193897A1 WO 2022193897 A1 WO2022193897 A1 WO 2022193897A1 CN 2022076601 W CN2022076601 W CN 2022076601W WO 2022193897 A1 WO2022193897 A1 WO 2022193897A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud
instance
network
service
information
Prior art date
Application number
PCT/CN2022/076601
Other languages
English (en)
French (fr)
Inventor
陈重
董斌
王文强
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN202111164145.1A external-priority patent/CN115118585A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22770252.9A priority Critical patent/EP4290819A4/en
Publication of WO2022193897A1 publication Critical patent/WO2022193897A1/zh
Priority to US18/468,136 priority patent/US20240007364A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5048—Automatic or semi-automatic definitions, e.g. definition templates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a service deployment method, device, and system.
  • the embodiments of the present application provide a method, device and system for deploying a service.
  • a service instance corresponding to a service is created by a controller, and a corresponding network instance is created in the service instance, which can simplify the process of service deployment and reduce the complexity of service deployment. complexity, and improve the efficiency and accuracy of business deployment.
  • an embodiment of the present application provides a method for deploying a service, where the service is that a tenant provides a virtual cloud private network.
  • the virtual cloud private network is used for tenants to access the first cloud.
  • the above method is executed by a controller, which creates a service instance corresponding to the service; the controller creates a first network instance and a second network instance in the service instance.
  • the first network instance and the second network instance are used to deploy services.
  • 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 identifier of the first device includes, but is not limited to, the device serial number ESN of the first device, the device name of the first device, or the media access control MAC address of the first device.
  • the second network instance is a network instance corresponding to the edge PE of the first cloud operator, and the second network instance includes the device identifier of the first cloud PE.
  • the device identifier of the first cloud PE includes but is not limited to the device serial number ESN of the first cloud PE, the device name of the first cloud PE, and the media access control MAC address of the first cloud PE.
  • the first cloud PE is used to connect to the first cloud.
  • the first device and the first cloud PE are edge devices of the virtual cloud private network.
  • the tenant accesses the cloud through the first device and the first cloud PE.
  • connection information for connecting the first cloud PE to the first cloud is set.
  • 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 the first interface of the first cloud PE, the identification of the first virtual local area network VLAN of the first cloud PE, The first interface is configured with a first VLAN, and the first cloud PE is connected to the first cloud through the first VLAN.
  • connection information of the first cloud PE By first setting the connection information of the first cloud PE in the controller, when subsequently creating a service instance or creating a second network instance, information such as the device identification of the first cloud PE can be associated with one or more pieces of information in the connection information, The number of network parameter settings in the service deployment process is reduced, and the efficiency of service deployment is further improved.
  • the above-mentioned service instance includes an identifier of the service instance.
  • the identifier of the service instance includes, but is not limited to, the name of the service instance, the identifier ID of the service instance, and other information that can identify the service instance.
  • the service instance further includes one or more of the following: the type of the service instance, the number of network instances that have been created, and the order information of the tenant.
  • the types of service instances include single cloud or multi-cloud.
  • Single cloud means that the tenant can access only one cloud through the first device
  • multi-cloud means that the tenant can access multiple clouds through the first device.
  • the device type of the first device is customer premises equipment CPE.
  • the first network instance further includes one or more of the following: location information of the first CPE, network-side IP address of the first CPE, tenant-side IP address of the first CPE, first CPE Routing information from the CPE to the tenant's LAN.
  • the device type of the first device is cloud PE.
  • the second cloud PE is used to connect to the second cloud. That is, the edge devices of the virtual cloud private network are the second cloud PE and the first cloud PE.
  • the first network instance further includes one or more of the following: location information of the second cloud PE, provider information of the second cloud, an IP address of the second cloud PE connected to the second cloud, and the second cloud PE connected to the second cloud. Routing information, and service quality information of the interface connecting the second cloud PE to the second cloud.
  • the second network instance further includes one or more of the following: location information of the first cloud PE, provider information of the first cloud, an IP address of the first cloud PE connecting to the first cloud, and the first cloud PE.
  • location information of the first cloud PE e.g., location information of the first cloud PE, provider information of the first cloud, an IP address of the first cloud PE connecting to the first cloud, and the first cloud PE.
  • the routing information of the cloud PE connecting to the first cloud e.g., and the service quality information of the interface connecting the first cloud PE to the first cloud.
  • the controller determines 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.
  • the controller deploys the first network instance and the second network instance.
  • the network operation and maintenance personnel simplifies the deployment process of the virtual cloud private network service through the above method to create a service instance in control, create a first network instance and a second network instance, and deploy the first network instance and the second network instance.
  • the method further simplifies the process of business deployment, reduces the complexity of business deployment, and improves the efficiency and accuracy of business deployment.
  • the controller sends first configuration information for configuring a service to the first device; and sends second configuration information for configuring a service to the first cloud PE.
  • 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.
  • the first service template indicates configuration information of the service instance.
  • the configuration information of the service instance includes one or more of the following: tunnel configuration information, virtual private network VPN instance configuration information, or routing information.
  • the controller sets the first service template according to the type of the service instance.
  • the purpose of setting the first service template is to template the configuration information of the service corresponding to the service instance in aspects such as configuring tunnels, configuring VPN instances, and configuring routes.
  • each type of service instance corresponds to a service template, and the configuration information of the service instance can be quickly obtained, thus solving the need for network operation and maintenance personnel to set a large amount of configuration information for each service when deploying services.
  • the problem. The method of obtaining configuration information through a service template simplifies the process of obtaining configuration information in virtual cloud private network service deployment, and further improves the efficiency of service deployment.
  • the virtual cloud private network is also used for the tenant to access the third cloud.
  • the controller creates a third network instance in the service 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 to connect the third cloud.
  • the controller before the controller creates the service instance, receives the first request sent by the service deployment apparatus.
  • the first request is for the service deployment apparatus to invoke the first application programming interface API of the controller to create a service instance, and the first request includes an identifier of the service instance.
  • the first request further includes one or more of the following: the type of the service instance, the identifier of the tenant, and the order information of the tenant.
  • the controller receives the second request sent by the service deployment apparatus.
  • the second request is for the service deployment apparatus to invoke the 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 the identifier of the service instance, the identifier of the first network instance, and the device identifier of the first device.
  • the information for creating the second network instance includes the identifier of the service instance, the identifier of the second network instance, and the device identifier of the first cloud PE.
  • the information for creating the first network instance further includes one or more of the following: location information of the first CPE, 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.
  • the second cloud PE is used to connect to the second cloud.
  • the information for creating the first network instance further includes one or more of the following: location information of the second cloud PE, provider information of the second cloud, and connection of the second cloud PE The IP address of the second cloud, the routing information for connecting the second cloud PE to the second cloud, and the service quality information for the interface for connecting the second cloud PE to the second cloud.
  • the information for creating the second network instance includes one or more of the following: location information of the first cloud PE, provider information of the first cloud, and IP of the first cloud PE connecting to the first cloud The address, the routing information of the first cloud PE connecting to the first cloud, and the service quality information of the interface of the first cloud PE connecting to the first cloud.
  • the controller before the controller deploys the first network instance and the second network instance, the controller receives the third request sent by the service deployment apparatus.
  • the third request is for the service deployment apparatus to invoke the 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 the identification of the service instance and the identification of the first network instance.
  • the information for deploying the second network instance includes the identification of the service instance and the identification of the second network instance.
  • 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 apparatus.
  • the deployment result information of the first network instance includes, but is not limited to: the identifier 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 reason for the deployment failure of the first network instance.
  • the deployment result information of the second network instance includes but is not limited to: the identifier 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 reason for the deployment failure of the second network instance.
  • the controller receives a fourth request sent by the service deployment apparatus, and the fourth request is used to call a fourth API of the controller to obtain the deployment result information of the first network instance and/or the deployment of the second network instance result information.
  • the controller sends the creation result information of the service instance to the service deployment apparatus.
  • the creation result information of the business instance includes, but is not limited to, the identifier of the business instance, the success mark of the business instance creation, the failure mark of the business instance creation, and the reason for the failure to create the business instance.
  • the controller receives a fifth request sent by the service deployment apparatus, and the fifth request is used to call a fifth API of the controller to obtain the creation result information of the service instance.
  • the controller sends the creation result information of the first network instance and/or the 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 identifier of the first network instance, a successful creation flag of the first network instance, a creation failure flag of the first network instance, and a failure reason for the creation of the first network instance.
  • the creation result information of the second network instance includes, but is not limited to, an identifier of the second network instance, a successful creation flag of the second network instance, a creation failure flag of the second network instance, and a failure reason for the creation of the second network instance.
  • the controller receives a sixth request sent by the service deployment apparatus, and 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 of the second network instance result information.
  • 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.
  • the first cloud includes at least one virtual private cloud VPC.
  • the type of each of the at least one site of the tenant includes: branch network or cloud.
  • the embodiments of the present application provide 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 tenants to access the First Cloud.
  • the above method is executed by a service deployment device, the service deployment device sends a first request to the controller, the first request is used to call the first application programming interface API of the controller to create a service instance of the service, and the first request includes the identifier of the service instance ; Send a second request to the controller, 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 used to create the first network instance includes the identifier of the service instance, the identifier of the first network instance, and the device identifier of the first device.
  • the information for creating the second network instance includes the identifier of the service instance, the identifier of the second network instance, and the device identifier of the first cloud PE.
  • the first network instance and the second network instance are used to deploy services.
  • 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 second network instance is a network instance corresponding to the edge PE of the first cloud operator, and the second network instance includes the device identifier of the first cloud PE.
  • the first cloud PE is used to connect to the first cloud.
  • the first device and the first cloud PE are edge devices of the virtual cloud private network.
  • the tenant accesses the cloud through the first device and the first cloud PE.
  • the network personnel call the service interface provided by the controller through the service deployment device for service deployment, which simplifies the process of virtual cloud private network service deployment to creating a service instance, creating a first network instance and a second network instance, reducing the complexity of service deployment. This improves the efficiency and accuracy of business deployment.
  • the above-mentioned first request further includes one or more of the following: the type of the service instance, the identifier of the tenant, and the order information of the tenant.
  • the device type of the first device is customer premises equipment CPE.
  • the information for creating the first network instance further includes one or more of the following: location information of the first CPE, network-side IP address of the first CPE, and tenant side of the first CPE. IP address, and routing information from the first CPE to the local area network of the tenant.
  • the device type of the first device is cloud PE.
  • the second cloud PE is used to connect to the second cloud.
  • the information for creating the first network instance further includes one or more of the following: location information of the second cloud PE, provider information of the second cloud, and connection of the second cloud PE The IP address of the second cloud, the routing information for connecting the second cloud PE to the second cloud, and the service quality information for the interface for connecting the second cloud PE to the second cloud.
  • the information for creating the second network instance includes one or more of the following: location information of the first cloud PE, provider information of the first cloud, and IP of the first cloud PE connecting to the first cloud The address, the routing information of the first cloud PE connecting to the first cloud, and the service quality information of the interface of the first cloud PE connecting to the first cloud.
  • the service deployment apparatus sends the third request to the controller.
  • the third request is for the service deployment apparatus to invoke the 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 the identification of the service instance and the identification of the first network instance
  • the information for deploying the second network instance includes the identification of the service instance and the identification of the second network instance.
  • the service deployment apparatus receives the creation result information of the service instance sent by the controller.
  • the creation result information of the business instance includes, but is not limited to: the identifier of the business instance, the success mark of the business instance creation, the failure mark of the business instance creation, and the reason for the failure of the business instance creation.
  • the service deployment apparatus outputs the creation result information of the service instance.
  • the service deployment apparatus receives the creation result information of the first network instance and/or the 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 identifier of the first network instance, a successful creation flag of the first network instance, a creation failure flag of the first network instance, and a failure reason for the creation of the first network instance.
  • the creation result information of the second network instance includes, but is not limited to, an identifier of the second network instance, a successful creation flag of the second network instance, a creation failure flag of the second network instance, and a failure reason for the creation of the second network instance.
  • the service deployment apparatus outputs the creation result information of the first network instance and/or the creation result information of the second network instance.
  • the service deployment apparatus receives the deployment result information of the first network instance and/or the deployment result information of the second network instance sent by the controller.
  • the deployment result information of the first network instance includes, but is not limited to: the identifier 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 reason for the deployment failure of the first network instance.
  • the deployment result information of the second network instance includes but is not limited to: the identifier 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 reason for the deployment failure of the second network instance.
  • the service deployment apparatus outputs the deployment result information of the first network instance and/or the deployment result information of the second network instance.
  • the types of service instances include: single cloud or multiple clouds.
  • Single cloud means that the tenant can access only one cloud through the first device
  • multi-cloud means that the tenant can access multiple clouds through the first device.
  • 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.
  • the first cloud includes at least one virtual private cloud VPC.
  • the type of each of the at least one site of the tenant includes: branch network or cloud.
  • an embodiment of the present application provides an apparatus for service deployment.
  • the business is to provide a virtual cloud private network for tenants, and the virtual cloud private network is used for tenants to access the First Cloud.
  • the device includes: a service instance creation module for creating a service instance corresponding to the service.
  • the device includes: a network instance creation module for creating a first network instance and a second network instance in the service instance.
  • the first network instance and the second network instance are used to deploy services.
  • 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 identifier of the first device includes, but is not limited to, the device serial number ESN of the first device, the device name of the first device, or the media access control MAC address of the first device.
  • the second network instance is a network instance corresponding to the edge PE of the first cloud operator, and the second network instance includes the device identifier of the first cloud PE.
  • the device identifier of the first cloud PE includes but is not limited to the device serial number ESN of the first cloud PE, the device name of the first cloud PE, and the media access control MAC address of the first cloud PE.
  • the first cloud PE is used to connect to the first cloud.
  • the first device and the first cloud PE are edge devices of the virtual cloud private network.
  • the tenant accesses the cloud through the first device and the first cloud PE.
  • the apparatus further includes: an information setting module, configured to set connection information for connecting the first cloud PE to the first cloud.
  • 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 the first interface of the first cloud PE, the identification of the first virtual local area network VLAN of the first cloud PE , the first interface is used for the first cloud PE to connect to the first cloud, and the first VLAN is used for the first cloud PE to connect to the first cloud.
  • the service instance includes an identifier of the service instance.
  • the identifier of the service instance includes, but is not limited to, the name of the service instance, the identifier ID of the service instance, and other information that can identify the service instance.
  • the service instance further includes one or more of the following: the type of the service instance, the number of network instances that have been created, and the order information of the tenant.
  • the types of service instances include single cloud or multi-cloud.
  • Single cloud means that the tenant can access only one cloud through the first device
  • multi-cloud means that the tenant can access multiple clouds through the first device.
  • the device type of the first device is customer premises equipment CPE.
  • the first network instance further includes one or more of the following: location information of the first CPE, network-side IP address of the first CPE, tenant-side IP address of the first CPE, first CPE Routing information from the CPE to the tenant's LAN.
  • the device type of the first device is cloud PE.
  • the second cloud PE is used to connect to the second cloud.
  • the first network instance further includes one or more of the following: location information of the second cloud PE, provider information of the second cloud, and IP of the second cloud PE connecting to the second cloud address, routing information for connecting the second cloud PE to the second cloud, and quality of service information for the interface connecting the second cloud PE to the second cloud.
  • the second network instance further includes one or more of the following: location information of the first cloud PE, provider information of the first cloud, an IP address of the first cloud PE connecting to the first cloud, and the first cloud PE.
  • location information of the first cloud PE e.g., location information of the first cloud PE, provider information of the first cloud, an IP address of the first cloud PE connecting to the first cloud, and the first cloud PE.
  • the routing information of the cloud PE connecting to the first cloud e.g., and the service quality information of the interface connecting the first cloud PE to the first cloud.
  • the apparatus further includes: a network instance creation module, 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.
  • the apparatus further includes: a network instance deployment module, configured to deploy the first network instance and the second network instance.
  • the device simplifies the deployment process of the virtual cloud private network service to create a service instance in control, create a first network instance and a second network instance, and deploy the first network instance and the second network instance.
  • the device further simplifies the process of business deployment, reduces the complexity of business deployment, and improves the efficiency and accuracy of business deployment.
  • the apparatus further includes: a network instance deployment module, further configured to send first configuration information to the first device, where the first configuration information is used to configure services; and configured to send the second configuration information to the first cloud PE configuration information, the second configuration information is used to configure services.
  • the apparatus further includes: a network instance deployment module, further configured to determine the first configuration information and the second configuration information according to the first network instance, the second network instance and the first service template.
  • the first service template indicates configuration information of the service instance.
  • the configuration information of the service instance includes one or more of the following: tunnel configuration information, virtual private network VPN instance configuration information, or routing information.
  • the apparatus further includes: an information setting module, further configured to set the first service template according to the type of the service instance.
  • the apparatus sets the first service template according to the type of the service instance.
  • the purpose of setting the first service template is to template the configuration information of the service corresponding to the service instance in aspects such as configuring tunnels, configuring VPN instances, and configuring routes.
  • each type of service instance corresponds to a service template.
  • the configuration information of the service instance can be quickly obtained according to the service template, thereby solving the problem that network operation and maintenance personnel need to set a large amount of configuration information for each service when deploying services.
  • the method of obtaining configuration information through a service template simplifies the process of obtaining configuration information in virtual cloud private network service deployment, and further improves the efficiency of service deployment.
  • the virtual cloud private network is also used for the tenant to access the third cloud.
  • the network instance creation module is also used for creating a third network instance in the service 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 to connect the third cloud.
  • the apparatus further includes: a request message processing module, configured to receive a first request sent by the service deployment apparatus.
  • the first request is used to call the first application programming interface API of the device to create a service instance, and the first request includes an identifier of the service instance.
  • the first request further includes one or more of the following: the type of the service instance, the identifier of the tenant, and the order information of the tenant.
  • the apparatus further includes: a request message processing module, further configured to receive a second request sent by the service deployment apparatus.
  • the second request is used to call a second API of the device 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 the identifier of the service instance, the identifier of the first network instance, and the device identifier of the first device.
  • the information for creating the second network instance includes the identifier of the service instance, the identifier of the second network instance, and the device identifier of the first cloud PE.
  • the device type of the first device is CPE.
  • the information for creating the first network instance further includes one or more of the following: location information of the first CPE, network-side IP address of the first CPE, and tenant side of the first CPE. IP address, and routing information from the first CPE to the local area network of the tenant.
  • the device type of the first device is cloud PE.
  • the second cloud PE is used to connect to the second cloud.
  • the information for creating the first network instance further includes one or more of the following: location information of the second cloud PE, provider information of the second cloud, and connection of the second cloud PE The IP address of the second cloud, the routing information for connecting the second cloud PE to the second cloud, and the service quality information for the interface for connecting the second cloud PE to the second cloud.
  • the information for creating the second network instance includes one or more of the following: location information of the first cloud PE, provider information of the first cloud, and IP of the first cloud PE connecting to the first cloud The address, the routing information of the first cloud PE connecting to the first cloud, and the service quality information of the interface of the first cloud PE connecting to the first cloud.
  • the apparatus further includes: a request message processing module, further configured to receive a third request sent by the service deployment apparatus.
  • the third request is for invoking a third API of the device 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 the identification of the service instance and the identification of the first network instance.
  • the information for deploying the second network instance includes the identification of the service instance and the identification of the second network instance.
  • the device further includes: a request message processing module, further configured to receive a fourth request sent by the service deployment device, where the fourth request is used to call a fourth API of the device to obtain the information of the first network instance.
  • Deployment result information and/or deployment result information of the second network instance includes, but is not limited to: the identifier 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 reason for the deployment failure of the first network instance.
  • the deployment result information of the second network instance includes but is not limited to: the identifier 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 reason for the deployment failure of the second network instance.
  • the apparatus further includes: a result information processing module, 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.
  • the apparatus further includes: a result information processing module, configured to send the creation result information of the service instance to the service deployment apparatus.
  • the creation result information of the business instance includes, but is not limited to: the identifier of the business instance, the success mark of the business instance creation, the failure mark of the business instance creation, and the reason for the failure of the business instance creation.
  • the apparatus further includes: a result information processing module, configured to receive a fifth request sent by the service deployment apparatus, where the fifth request is used to call a fifth API of the controller to obtain the creation result information of the service instance.
  • a result information processing module configured to receive a fifth request sent by the service deployment apparatus, where the fifth request is used to call a fifth API of the controller to obtain the creation result information of the service instance.
  • the apparatus further includes: a result information processing module, configured to send the creation result information of the first network instance and/or the 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 identifier of the first network instance, a successful creation flag of the first network instance, a creation failure flag of the first network instance, and a failure reason for the creation of the first network instance.
  • the creation result information of the second network instance includes, but is not limited to, an identifier of the second network instance, a successful creation flag of the second network instance, a creation failure flag of the second network instance, and a failure reason for the creation of the second network instance.
  • the device further includes: a result information processing module, configured to receive 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 of the first network instance information and/or creation result information of the second network instance.
  • a result information processing module configured to receive 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 of the first network instance information and/or creation result information of the second network instance.
  • 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.
  • the first cloud includes at least one virtual private cloud VPC.
  • the type of each of the at least one site of the tenant includes: branch network or cloud.
  • an embodiment of the present application provides an apparatus for service deployment.
  • the business is to provide a virtual cloud private network for tenants, and the virtual cloud private network is used for tenants to access the First Cloud.
  • the device includes: a request message processing module for sending a first request to the controller.
  • the first request is used to call the 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 device includes: a request message processing module, which is further configured to send a second request to the controller.
  • the second request is used to call the 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 the identifier of the service instance, the identifier of the first network instance, and the device identifier of the first device.
  • the information for creating the second network instance includes the identifier of the service instance, the identifier of the second network instance, and the device identifier of the first cloud PE.
  • the first network instance and the second network instance are used to deploy 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 edge PE of the first cloud operator, and the second network instance includes the device identifier of the first cloud PE.
  • the first cloud PE is used to connect to the first cloud.
  • the first device and the first cloud PE are edge devices of the virtual cloud private network.
  • the tenant accesses the cloud through the first device and the first cloud PE.
  • the above-mentioned device deploys services by invoking the service-oriented interface provided by the controller, and simplifies the process of virtual cloud private network service deployment to the creation of a service instance, a first network instance and a second network instance, which reduces the complexity of service deployment and improves the efficiency of service deployment. The efficiency and accuracy of business deployment are improved.
  • the first request further includes one or more of the following: the type of the service instance, the identifier of the tenant, and the order information of the tenant.
  • the device type of the first device is customer premises equipment CPE.
  • the information for creating the first network instance further includes one or more of the following: location information of the first CPE, network-side IP address of the first CPE, and tenant side of the first CPE. IP address, and routing information from the first CPE to the local area network of the tenant.
  • the device type of the first device is cloud PE.
  • the second cloud PE is used to connect to the second cloud.
  • the information for creating the first network instance further includes one or more of the following: location information of the second cloud PE, provider information of the second cloud, and connection of the second cloud PE The IP address of the second cloud, the routing information for connecting the second cloud PE to the second cloud, and the service quality information for the interface for connecting the second cloud PE to the second cloud.
  • the information for creating the second network instance includes one or more of the following: location information of the first cloud PE, provider information of the first cloud, and IP of the first cloud PE connecting to the first cloud The address, the routing information of the first cloud PE connecting to the first cloud, and the service quality information of the interface of the first cloud PE connecting to the first cloud.
  • the apparatus further includes: a request message processing module, 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 the identification of the service instance and the identification of the first network instance.
  • the information for deploying the second network instance includes the identification of the service instance and the identification of the second network instance.
  • the apparatus further includes: a result information processing module, configured to receive the creation result information of the service instance sent by the controller.
  • the creation result information of the business instance includes, but is not limited to: the identifier of the business instance, the success mark of the business instance creation, the failure mark of the business instance creation, and the reason for the failure of the business instance creation.
  • the apparatus further includes: a result information processing module, further configured to output the creation result information of the service instance.
  • the apparatus further includes: a result information processing module, further configured to receive the creation result information of the first network instance and/or the 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 identifier of the first network instance, a successful creation flag of the first network instance, a creation failure flag of the first network instance, and a failure reason for the creation of the first network instance.
  • the creation result information of the second network instance includes, but is not limited to, an identifier of the second network instance, a successful creation flag of the second network instance, a creation failure flag of the second network instance, and a failure reason for the creation of the second network instance.
  • the apparatus further includes: a result information processing module, further configured to output the creation result information of the first network instance and/or the creation result information of the second network instance.
  • the apparatus further includes: a result information processing module, further configured to receive the deployment result information of the first network instance and/or the deployment result information of the second network instance sent by the controller.
  • the deployment result information of the first network instance includes, but is not limited to: the identifier 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 reason for the deployment failure of the first network instance.
  • the deployment result information of the second network instance includes but is not limited to: the identifier 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 reason for the deployment failure of the second network instance.
  • the apparatus further includes: a result information processing module, further configured to output the deployment result information of the first network instance and/or the deployment result information of the second network instance.
  • the types of service instances include: single cloud or multiple clouds.
  • Single cloud means that the tenant can access only one cloud through the first device
  • multi-cloud means that the tenant can access multiple clouds through the first device.
  • 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.
  • the first cloud includes at least one virtual private cloud VPC.
  • the type of each of the at least one site of the tenant includes: branch network or cloud.
  • an embodiment of the present application provides a service deployment system, the system includes a controller and a service deployment device, the controller implements the steps performed by the controller in the method of the above aspect, and the service deployment device implements the above aspect. The steps in the method are performed by the service deployment apparatus.
  • an embodiment of the present application provides a communication device, the communication device includes a memory and a processor, the memory includes an instruction, and when the processor executes the instruction, the communication device is controlled to perform the method in the above aspect. the steps performed by the device.
  • an embodiment of the present application provides a communication device, the communication device includes a memory and a processor, the memory includes an instruction, and when the processor executes the instruction, the communication device is caused to execute the service in the method in the above aspect. The steps performed by the deployment appliance.
  • embodiments of the present application provide a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed by a processor, implement the method for deploying services provided in any of the foregoing aspects.
  • an embodiment of the present application provides a computer program product including instructions, which, when the computer program product is executed by a processor, implements a method for deploying services provided by any of the foregoing aspects and any possible implementation manner.
  • FIG. 1(a) is a network topology and architecture diagram of a method for deploying a service according to an embodiment of the present application
  • FIG. 1(b) is a network topology and architecture diagram of a service deployment method provided by an embodiment of the present application
  • FIG. 2(a) is a schematic diagram of an application scenario of a service deployment method provided by an embodiment of the present application
  • FIG. 2(b) is a schematic diagram of an application scenario of a service deployment method provided by an embodiment of the present application
  • FIG. 2(c) is a schematic diagram of an application scenario of a service deployment method provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of an interface for setting connection information in an embodiment of a service deployment method provided by an embodiment of the present application
  • FIG. 4(a) is a flowchart of an implementation manner of a service deployment method 400 provided by an embodiment of the present application
  • FIG. 4(b) is a flowchart of an implementation manner of a service deployment method 4050 provided by an embodiment of the present application.
  • FIG. 4(c) is a flowchart of an implementation of a service deployment method 40550 provided by an embodiment of the present application.
  • FIG. 5(a) is a schematic interface diagram of creating a service instance in an embodiment of a service deployment method provided by an embodiment of the present application;
  • FIG. 5(b) is a schematic interface diagram of a service instance list in an embodiment of a service deployment method provided by an embodiment of the present application;
  • FIG. 6(a) is a schematic interface diagram of creating a network instance in an embodiment of a service deployment method provided by an embodiment of the present application
  • FIG. 6(b) is a schematic interface diagram of creating a network instance in an embodiment of a service deployment method provided by an embodiment of the present application;
  • FIG. 6(c) is a schematic interface diagram of creating a network instance in an embodiment of a service deployment method provided by an embodiment of the present application;
  • FIG. 7 is a flowchart of an implementation manner of a service deployment method 700 provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of the architecture of a service deployment system provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a service deployment apparatus according to an embodiment of the present application.
  • the network architecture and service scenarios described in the embodiments of the present application are to illustrate the technical solutions of the present application by way of examples, and do not mean that the present application is only applicable to the following embodiments.
  • Those of ordinary skill in the art know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided in this application are also applicable to similar technical problems.
  • VPC is a virtual private network that provides access to the cloud for tenants or enterprise users. For example, through the virtual cloud private network, terminals or servers in tenant sites can access the cloud.
  • the service provider establishes one or more virtual private lines between the network device on the tenant site side and the network device on the cloud side, so that the terminal or server at the tenant site can access the cloud through the private line. Compared with the tenant accessing the cloud through the Internet line, the tenant accessing the cloud through the virtual cloud private network will obtain higher security and reliability.
  • Tenant site A network of the tenant, where terminals or servers need to access the cloud through the virtual cloud private network.
  • Types of tenant sites include, but are not limited to: branch network or cloud.
  • the service provider network is the network deployed, operated and maintained by the service provider.
  • the network is the network infrastructure that provides virtual cloud private network services for tenants. Based on this network, the service provider provides the tenant's business with a virtual private line from the tenant side to the cloud side, so that the terminal or server in the tenant site can access the cloud through the virtual cloud private network.
  • the schematic diagrams of the application scenarios shown in FIG. 1(a) and FIG. 1(b) describe the service provider system, tenant site, service provider network, and cloud network topology of the service provider of the virtual cloud private network in this embodiment and system architecture.
  • the service provider provides virtual cloud private network services for tenant A, tenant B and tenant C through the service provider system 1000 .
  • the service provider provides the tenant with an accessible cloud, the cloud including the first cloud 50 , the second cloud 60 and the third cloud 70 .
  • the type of cloud includes, but is not limited to, public cloud, private cloud or hybrid cloud.
  • the cloud accessed by the tenant can be one cloud, or one or more virtual private cloud VPCs (Virtual Private Cloud) virtualized by virtualization technology based on the cloud.
  • VPCs Virtual Private Cloud
  • the tenant site type of tenant A is a branch network.
  • Tenant A's tenant site includes branch network 10 .
  • the branch network 10 includes a terminal 101 .
  • Tenant B's tenant site type is a branch network.
  • Tenant B's tenant site includes branch network 20 .
  • the branch network 20 includes a terminal 201 .
  • Tenant C's tenant site type is cloud.
  • Tenant C's tenant site includes cloud 80 .
  • the cloud 80 includes a virtual private cloud VPC 801 .
  • the service provider network is a multi-domain network, including a network of network domain A 30 and network domain B 40.
  • the network domain A includes customer premises equipment CPE (Customer Premises Equipment) 301 , CPE 302 , and cloud operator edge PE (Provider Edge) 303 .
  • the CPE 301 is a network device deployed in the service provider network and located on the site side of tenant A.
  • the CPE 302 is a network device deployed in the service provider network and located on the side of the tenant B site.
  • the cloud PE 303 is a network device deployed in the service provider network and located on the side of the tenant C site.
  • the network domain A also includes other equipment of the service provider, which will not be described one by one here.
  • Network domain B includes network PE305, network PE306, cloud PE401, cloud PE402, and cloud PE403.
  • the network PE305 and the network PE306 are border devices deployed in the service provider network and located in the network domain A and the network domain B.
  • the cloud PE 401 is a device deployed in the service provider network and located on the side of the first cloud 50 .
  • the cloud PE 402 is a device deployed in the service provider network and located on the side of the second cloud 60 .
  • the cloud PE 403 is a device deployed in the service provider network and located on the side of the third cloud 70 .
  • the network domain B also includes other equipment of the service provider, which will not be described one by one here.
  • the service provider network is a single-domain network, including the network of network domain C 90.
  • Network domain C includes CPE301, CPE302, cloud PE303, cloud PE401, cloud PE402, and cloud PE403.
  • the CPE 301 is a network device deployed in the service provider network and located on the site side of tenant A.
  • the CPE 302 is a network device deployed in the service provider network and located on the side of the tenant B site.
  • the cloud PE 303 is a network device deployed in the service provider network and located on the side of the tenant C site.
  • the cloud PE 401 is a device deployed in the service provider network and located on the side of the first cloud 50 .
  • the cloud PE 402 is a device deployed in the service provider network and located on the side of the second cloud 60 .
  • the cloud PE 403 is a device deployed in the service provider network and located on the side of the third cloud 70 .
  • the network domain C also includes other equipment of the service provider, which will not be described one by one here.
  • tenant A The business requirement of tenant A is that the terminal 101 in the tenant A's site (branch network 10 ) only accesses the first cloud 50 .
  • tenant B The business requirement of tenant B is that the terminal 201 in the tenant B's site (branch network 20 ) accesses the second cloud 60 and the third cloud 70 .
  • the business requirement of Tenant C is that the server in Tenant C's site (cloud 80 ) only accesses the third cloud 70 .
  • the service provider divides the service types of the virtual cloud private network into single cloud or multi-cloud according to the business needs of the tenants.
  • Single cloud means that the tenant can access only one cloud through the devices on the tenant side.
  • Multi-cloud means that tenants can access multiple clouds through tenant-side devices.
  • tenant A's business requirement is that the terminal 101 only accesses the first cloud 50 through CPE301, so tenant A's business type is single cloud; tenant C's business requirement is that the server only accesses third cloud 70 through cloud PE303, so tenant C's business requirement is The business type is single cloud.
  • the service requirement of tenant B is that the terminal can access the second cloud 60 and the third cloud 70 through the CPE 302, so the service type of tenant B is multi-cloud.
  • a service provider system 1000 is a service deployment system provided by an embodiment of the present application, and the service provider system 1000 includes a service deployment apparatus 1100 and a controller corresponding to the service provider network 1200.
  • the service deployment device 1100 may be an operation and maintenance support system OSS (Operations Support System), a business support system (Business Support System), or a network service orchestrator NSO (Network Service Orchestrator), and the like.
  • the controller 1200 is a cross-domain controller, which is used to manage, operate and maintain the network devices in the network domain A 30 and the network domain B 40 . As shown in FIG.
  • the controller 1200 is a single domain controller, which is used to manage, operate and maintain the network devices in the network domain C 90. As shown in FIG. 1( a ) and FIG. 1( b ), the service deployment apparatus 1100 deploys the virtual cloud private network service by invoking one or more application programming interface APIs (Application Programming Interface) of the controller 1200 .
  • application programming interface APIs Application Programming Interface
  • the service provider needs to provide the tenant with one or more virtual private lines, which are used for terminals or servers in the tenant's site to access the cloud.
  • the above-mentioned virtual private line is a data transmission tunnel from the network equipment on the tenant side in the service provider network to the network equipment on the cloud side. Tunnel types include but are not limited to Layer 2 VPN (Virtual Private Network) tunnels or Layer 3 VPN tunnels.
  • the service provider provides a virtual cloud private network A for tenant A, and the service type of the virtual cloud private network A is single cloud.
  • the terminal 101 in the tenant A site sends a data packet for accessing the first cloud 50 , and the data packet is forwarded to the CPE 301 by the network device in the branch network 10 .
  • the CPE301 After receiving the packet, the CPE301 encapsulates the data packet into the tunnel (the virtual private line 500 between the CPE301 and the cloud PE401) according to the analysis result of the destination IP address.
  • the cloud PE 401 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.
  • the terminal 101 of the tenant A site can access the first cloud 50 through the above-mentioned processing flow of the data packet.
  • the service provider provides tenant B with a virtual private cloud network B, and creates two virtual private lines, including a virtual private line from CPE302 to cloud PE402 501 and a virtual private line 502 from CPE302 to cloud PE403.
  • the service provider provides a virtual private cloud network C for the tenant, and creates a virtual private line 503 from cloud PE303 to cloud PE403.
  • the service provider's network operation and maintenance personnel When the service provider's network operation and maintenance personnel receive the tenant's business requirements, they need to first determine the device information of the network devices deployed at the tenant's site and the device information of the cloud PE corresponding to the cloud service purchased by the tenant.
  • the network operation and maintenance personnel need to check the resource information of the network equipment of the service provider network from the equipment on the tenant site side to the cloud PE on the cloud side.
  • the purpose of checking is to plan a route from the equipment on the tenant site side to the cloud PE. Virtual Private Line.
  • the configuration interface of the network management system or the API interface of the network management system, configure the tunnel configuration information corresponding to the virtual private line, VPN instance configuration information, and routing information, etc.
  • network operation and maintenance personnel need to plan virtual private lines according to the business requirements of each tenant, query, identify and allocate network resources, and then set the configuration information to relevant network devices.
  • the process of service deployment is complex. , the workload is large, which leads to the inability to quickly deploy services, resulting in the slow launch of tenant services.
  • the embodiments of the present application provide a service deployment method, device and system.
  • the service deployment process is simplified and the complexity of service deployment is reduced to improve the efficiency and accuracy of business deployment.
  • FIG. 4(a) shows a schematic flowchart of a service deployment method 400 provided by the present application.
  • the network architecture of the application method 400 includes a controller, a service deployment apparatus, a first device and a first cloud PE.
  • the network architecture of the application method 400 may be, for example, the network architecture shown in FIG. 1( a ) or FIG. 1( b ).
  • 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 CPE302 shown in FIG.
  • the method 400 is executed by the controller, and specifically includes:
  • S401 Create a service instance corresponding to the service.
  • the controller creates a business instance corresponding to the business.
  • the network operation and maintenance personnel creates a service instance on the controller according to the service requirements.
  • the business instance includes the identification of the business instance.
  • the identifier of the service instance 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 the service type of the virtual cloud private network.
  • a business instance may also include the type of business instance.
  • the type of business instance indicates the business type, such as single cloud, multi-cloud, etc.
  • the type of the service instance is single cloud.
  • the type of the service instance is multi-cloud.
  • the business instance may further include tenant information, where the tenant information includes but is not limited to the tenant's identity or the tenant's order information.
  • the service instance may also include information about the network instance that has been created.
  • the information of the created network instance includes, but is not limited to, the number of network instances, the type of the network instance, and the identifier of the network instance.
  • the network instance is the instance corresponding to the edge device of the virtual cloud private network.
  • the network instances in the service instance corresponding to the virtual cloud private network A include but are not limited to the network instance corresponding to the CPE301 and the network instance corresponding to the cloud PE401.
  • 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 the network device corresponding to the network instance.
  • the device type of the virtual cloud private network edge device includes but is not limited to CPE or cloud PE.
  • the purpose of creating a business instance is to record the business to be deployed and provide resource information for the business.
  • 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.
  • the data transmission path includes creating a data transmission tunnel between devices from the tenant site side to the cloud side in the service provider network.
  • the service instance records service type information, information about the border nodes of the virtual cloud private network, and also records the tenant information corresponding to the service.
  • the virtual cloud private network service and edge devices are associated through service instances. In addition, through the business instance, the business and the tenant are associated.
  • Service providers can search for related services based on tenant information to facilitate subsequent business queries.
  • service instances are in one-to-one correspondence with 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 .
  • the input box corresponding to "Service Instance ID” is used to obtain the name of the service instance or the ID of the service instance, such as "Virtual Cloud Private Network A” ;
  • the input box corresponding to "Business Instance Type” is used to obtain the business type, such as "Single Cloud”;
  • the input box corresponding to "Tenant Name” is used to obtain the name or tenant ID of the tenant who purchased the business, such as “Tenant A”;
  • the input box corresponding to "Order Information” is used to obtain the business order information of the above tenant, such as the order ID, such as the order number "123456".
  • S403 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, wherein the first network instance is the first network instance The network instance corresponding to the device, the first network instance includes the device identifier of the first device, the second network instance is the network instance corresponding to the edge PE of the first cloud operator, and the second network instance includes the The device identifier of the first cloud PE, where the first cloud PE is used to connect to the first cloud.
  • the controller creates the first network instance and the second network instance in the service instance.
  • the first network instance and the second network instance are used to deploy services.
  • the first network instance is the 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 the virtual cloud private network.
  • the first device is a border device connecting the tenant site to the service provider network.
  • the tenant site is connected to the virtual private line of the virtual cloud private network through the first device.
  • the first cloud PE is a device connected to the cloud side in the service provider network. The tenant accesses the cloud through the first device and the first cloud PE.
  • the first device is a tenant site-side device in the 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 the cloud side
  • the second network instance is the first cloud operation
  • the first network instance includes a device identification of the first device.
  • the second network instance includes the device identification of the first cloud PE.
  • the service of the virtual cloud private network A involves the site of the tenant A and the first cloud 50
  • the service instance 2000 corresponding to the service of the virtual cloud private network A is involved.
  • the first device is CPE301 in FIG. 2( a ), and the first network instance is a network instance corresponding to CPE301 .
  • the first cloud PE is cloud PE401
  • the second network instance is a network instance corresponding to cloud PE401.
  • the controller 1200 creates a first network instance and a second network instance in the service instance 2000 .
  • the service instance 3000 corresponding to the service of the virtual cloud private network C corresponds to the service instance 3000 .
  • the first device is the cloud PE 403 in FIG. 2( c )
  • the first network instance is the network instance corresponding to the cloud PE 403 .
  • the first cloud PE is cloud PE402
  • the second network instance is a network instance corresponding to cloud PE402.
  • the controller 1200 creates a first network instance and a second network instance in the service instance 3000 .
  • the first network instance includes the device identification of the first device
  • the second network instance includes the device identification of the first cloud PE.
  • the device identification includes, but is not limited to, the name of the device, the device serial number ESN (Equipment Serial Number) of the device, the ID of the device or the MAC address of the device, and other identification information used to identify the device.
  • ESN Equipment Serial Number
  • the device type of the virtual cloud private network edge device includes but is not limited to CPE or cloud PE.
  • the device type of the first device corresponding to the first network instance is CPE, that is, the type of the tenant site is a branch network.
  • the service type of the virtual cloud private network A is single cloud.
  • the controller creates a service instance 2000 for the virtual cloud private network A.
  • tenant A only accesses the first cloud 50 through the CPE 301 .
  • the first network instance is the network instance corresponding to the CPE 301 .
  • the first network instance further includes the name of the first network instance, the location information of the CPE301, the network-side IP address of the CPE301, the tenant-side IP address of the CPE301, and the routing information from the CPE301 to the local area network of the branch network 10 of tenant A.
  • the network-side IP address of the CPE301 is the IP address of the interface of the CPE301 connected to the branch network 10 of the tenant A site.
  • 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 is connected.
  • the routing information from the CPE 301 to the branch network 10 of the tenant A is used to forward the access response data packet sent from the first cloud 50 from the CPE 301 to the local area network of the tenant A site.
  • the routing information includes but is not limited to the destination network segment and next-hop information.
  • FIG. 6(a) is an interface for creating a first network instance corresponding to CPE301.
  • the input box corresponding to "Network Instance Name” on the interface is used to obtain the name of the network instance corresponding to CPE301;
  • the input box corresponding to "Location Information” is used to obtain the location information of CPE301, such as "City A”;
  • the input box is used to obtain the device identification information of the CPE301, for example, the ESN is "111222333";
  • the input box corresponding to "IP address on the network side” is used to obtain the IP address "10.10.10.10/20" of the interface connecting the CPE301 to the tenant site;
  • the input box corresponding to "side IP address” is used to obtain the IP address "10.1.1.1/20” of the network device of the tenant site connected to the CPE301;
  • the input box corresponding to "Route Information” is used to obtain the 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 PE401.
  • the cloud PE 401 is used to connect to the first cloud 50 to be accessed by tenant A.
  • the second network instance also includes the name of the second network instance, the location information of the cloud PE401, the provider information of the cloud PE401, the IP address of the cloud PE401 connecting to the first cloud 50, the interface identifier of the cloud PE401 connecting to the first cloud 50, the cloud PE401
  • VLAN Virtual Local Area Network
  • the provider information of the cloud PE401 includes the provider information corresponding to the first cloud 50 to which the cloud PE401 is connected.
  • the IP address of the cloud PE401 connecting to the first cloud 50 is the IP address of the interface of the cloud PE401 connecting to the first cloud 50 .
  • the routing information for connecting the cloud PE401 to the first cloud 50 is routing information for forwarding data from the cloud PE401 to the first cloud 50, including destination network segment and next hop information.
  • the service quality information of the interface of the cloud PE401 connecting to the first cloud 50 is used to set the QoS (Quality of Service) information of the interface of the cloud PE401 connecting to the first cloud 50.
  • the service quality information includes but is not limited to bandwidth, delay, jitter, etc. information.
  • FIG. 6( c ) is an interface for creating a second network instance corresponding to the cloud PE401.
  • the input box corresponding to "Network Instance Name” on the interface is used to obtain the name of the network instance corresponding to Cloud PE401; the input box corresponding to "Location Information” is used to obtain the location information of Cloud PE401, such as "City A.
  • Device ID of Cloud PE401 It can be entered manually, or the device identification of the cloud PE401 can be associated with the location information of the cloud PE401 according to the connection information of the cloud PE401 set on the controller 1200.
  • the input box corresponding to "supplier information” is used to obtain the connection information of the cloud PE401.
  • the input box corresponding to "IP address of the cloud PE connecting to the cloud” is used to obtain the IP address "10.1.2.20/20" of the interface of the cloud PE401 connecting to the first cloud 50; the corresponding "VLAN”
  • the input box is used to obtain the VLAN ID set by the interface of the cloud PE401 connected to the first cloud 50.
  • the input box corresponding to "interface service quality information” is used to obtain the QoS information set by the interface of the cloud PE401 connected to the first cloud 50.
  • "Routing Information” The corresponding input box is used to obtain routing information from the cloud PE401 to the first cloud 50 .
  • the process for the controller to set the connection information of the cloud PE is as follows:
  • the controller Before the service provider provides the services of virtual cloud private network A, virtual cloud private network B, and virtual cloud private network C for tenants, the controller creates a network capable of connecting tenant site A, tenant site B, and tenant site C with the first The network of the cloud 50 and the second cloud 60, ie the service provider network shown in Fig. 1(a) or Fig. 1(b).
  • One or more cloud PEs are deployed in the above-mentioned service provider network to connect one or more clouds that the service provider can provide cloud services.
  • the deployed cloud PE401 is used to connect the first cloud 50;
  • the deployed cloud PE402 is used for It is used to connect to the second cloud 60;
  • the deployed cloud PE 403 is used to connect to the third cloud 70.
  • the connection information of the cloud PE is set in the service provider system.
  • connection information may be set in the controller 1200 , and in other embodiments, the above connection information may be set in the service deployment apparatus 1100 .
  • the connection information that needs to be set includes: the device ID of the cloud PE, the location information of the cloud PE, the ID of the interface of the cloud PE, and the ID of the VLAN of the cloud PE.
  • the device identifier of the cloud PE includes the device name or device identifier ID of the cloud PE, and the like.
  • the location information of the cloud PE refers to the name or identifier of the location of the cloud to which the cloud PE is connected.
  • the name of the area location is used as the location information, such as city A
  • the location identifier corresponding to the cloud is used as the location information, such as area B
  • an identifier of a service provider that can correspond to the location of the cloud such as vendor C-001
  • the interface of the cloud PE refers to the physical interface used to connect to the cloud, such as the physical interface Gigabit Ethernet1/0/31.
  • the VLAN of the cloud PE identifies that the above-mentioned VLAN needs to be configured on the above-mentioned interface, so that the above-mentioned cloud PE is connected to the corresponding cloud through the above-mentioned VLAN.
  • FIG. 3 presents a connection information setting interface for setting the connection information of the cloud PE 401 connected to the first cloud 50 in the embodiment.
  • the input box corresponding to "Device Name” is used to input the device ID of the cloud PE, such as the cloud PE 401 in Figure 3;
  • the input box corresponding to "Region Information” is used for the location information of the cloud PE, as shown in Figure 3 City A;
  • the input box corresponding to "Interface Information” is used to input the interface ID of the cloud PE, such as GE3/0/1 in Figure 3;
  • the input box corresponding to "VLAN” is used to input the VLAN ID of the cloud PE, as shown in Figure 3 of 100.
  • the service provider system 1000 stores and records the connection information of the cloud PE 401 connected to the first cloud 50 in the service provider network.
  • the location information of the cloud PE can be matched to the device identification and other connection 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 with the location information of the first cloud PE.
  • the controller 1200 creates the first network instance and the second network instance in the service instance 2000 .
  • the controller determines information of edge devices of the virtual cloud private network, such as device identification, device location information, routing information, and the like.
  • the controller creates a network instance in the service instance, such as the service instance list page shown in Figure 5(b).
  • the page includes information about two service instances, "Virtual Cloud Private Network A" and "Virtual Cloud Private Network B".
  • the "Service Instance Type” of "Virtual Cloud Private Network A” is "Single Cloud”
  • the "Order Information” is "123456”
  • the "Number of Network Instances” is the created network instance in the business instance of "Virtual Cloud Private Network A”
  • the quantity is "2".
  • the service type of the virtual cloud private network B is multi-cloud.
  • the controller creates a service instance 2001 corresponding to the service of the virtual cloud private network B.
  • a first network instance corresponding to the CPE302 a second network instance corresponding to the cloud PE401, and a third network instance corresponding to the cloud PE402 are created.
  • the first network instance is the network instance corresponding to the CPE 302 .
  • the first network instance also includes the name of the first network instance, the location information of the CPE302, the network-side IP address of the CPE3012, the tenant-side IP address of the CPE302, and the routing information from the CPE302 to the local area network of the branch network 20 of the tenant B.
  • the network-side IP address of the CPE 302 is the IP address of the interface of the CPE 302 connected to the branch network 20 of the tenant B site.
  • 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 from the CPE 302 to the local area network of the branch network 20 of the tenant B is the routing information for data forwarding from the CPE 302 to the local area network of the tenant B site, including the destination network segment and the next hop information.
  • the second network instance is the network instance corresponding to the cloud PE401, and the second network instance further includes the name of the second network instance, the location information of the cloud PE401, the provider information of the cloud PE401, and the IP address of the cloud PE401 connecting to the first cloud 50.
  • the third network instance is the network instance corresponding to the cloud PE402, and the third network instance includes the device identifier of the cloud PE402, the name of the third network instance, the location information of the cloud PE402, the provider information of the cloud PE402, and the cloud PE402 connecting to the second cloud 60.
  • the first network instance, the second network instance and the third network instance are created in the service instance 2001.
  • the "Service Instance Type" of "Virtual Cloud Private Network B” on the page is “Multi-cloud”
  • "Order Information” is "212345"
  • "Number of Network Instances” is " The number of network instances created in the service instance of virtual cloud private network B" is "3".
  • the type of the first device corresponding to the first network instance is cloud PE, that is, the type of the tenant site is cloud.
  • the virtual cloud private network C of tenant C is shown.
  • the controller creates a service instance 2002 corresponding to the service of the virtual cloud private network C.
  • the controller creates a first network instance and a second network instance in the service instance 2002 .
  • the first device corresponding to the first network instance is the cloud PE303, and the cloud PE303 is used to connect to the cloud 80 corresponding to the tenant C site.
  • the first network instance further includes the name of the first network instance, the location information of the cloud PE303, the provider information of the cloud PE303, the IP address of the cloud PE303 connecting to the cloud 80, the interface identifier of the cloud PE303 connecting to the cloud 80, and the interface identifier of the cloud PE303 connecting to the cloud 80.
  • VLAN ID routing information of cloud PE303 connecting to cloud 80
  • the provider information of the cloud PE303 includes the provider information corresponding to the cloud 80 to which the cloud PE303 is connected.
  • the IP address of the cloud PE303 connecting to the cloud 80 is the IP address of the interface of the cloud PE303 connecting to the cloud 80.
  • the routing information of the cloud PE303 connecting 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, including destination network segment and next hop information.
  • the service quality information of the interface of the cloud PE303 connected to the cloud 80 is used to set the service quality QoS information of the interface of the cloud PE303 connected to the cloud 80, including but not limited to information such as bandwidth, delay, and jitter.
  • FIG. 6(b) is an interface for creating a first network instance corresponding to the cloud PE303.
  • the input box corresponding to "Network instance name" on the interface is used to obtain the name of the network instance corresponding to the cloud PE403.
  • the input box corresponding to "Location Information” is used to obtain the location information of the cloud PE403, such as "City B".
  • the device ID can be obtained by entering in the input box.
  • the device identifier of the cloud PE 303 may also be associated with the location information of the cloud PE 303 according to the connection information of the cloud PE previously set on the controller 1200 .
  • the input box corresponding to "supplier information” is used to obtain the supplier name of the cloud 80 to which the cloud PE303 is connected.
  • the input box corresponding to "IP address of cloud PE connecting to cloud” is used to obtain the IP address "10.1.1.10/20" of the interface connecting cloud PE303 to cloud 80.
  • the input box corresponding to "VLAN” is used to obtain the VLAN ID set by the interface connecting the cloud PE303 to the cloud 80.
  • the input box corresponding to "interface service quality information” is used to obtain the QoS information set by the interface of the cloud PE303 connecting to the cloud 80.
  • the input box corresponding to "routing information” is used to obtain the routing information from cloud PE303 to cloud 80.
  • the network device corresponding to the second network instance is the cloud PE403.
  • the controller 1200 After creating the first network instance and the second network instance in the service instance 2002, the controller 1200 has created the first device on the tenant side of the service provider network corresponding to the service of the service instance 2002 and the first cloud connected to the cloud side Information such as the device identification, location information, IP address, and routing information of the PE is used for service deployment.
  • the service instance list page includes the information of the service instance of "Virtual Cloud Private Network C".
  • the "Service Instance Type" of "Virtual Cloud Private Network C” is "Single Cloud”
  • the "Order Information” is "311222”
  • the "Number of Network Instances” is the created network instance in the service instance of "Virtual Cloud Private Network C”
  • the quantity is "2”.
  • the controller creates a service instance corresponding to the virtual cloud private network service, and creates a corresponding first network instance and a second network instance in the service instance, which simplifies the service deployment process, reduces the complexity of service deployment, and improves services. Efficiency and accuracy of deployment.
  • S405 Deploy the first network instance and the second network instance.
  • the controller deploys the first network instance and the second network instance.
  • the controller has created the service instance corresponding to the service, as well as the first network instance and the second network instance.
  • the edge device and service type of the virtual cloud private network corresponding to the service to be deployed have been determined on the controller.
  • the network operation and maintenance personnel need to set the 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 on the first device and the first cloud PE includes but is not limited to:
  • the controller sends the first configuration information for configuring the service to the first device, and the controller sends the second configuration information for configuring the service to the first cloud PE.
  • the method 4050 for determining the first configuration information and the second configuration information according to the first network instance and the second network instance refer to the steps shown in FIG. 4(b) for details:
  • S4051 Acquire 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.
  • the first device and the first cloud PE are edge devices of the virtual cloud private network.
  • the tenant accesses the cloud through the first device and the first cloud PE.
  • the type of the first device is CPE.
  • the service provider provides the tenant with the first device, and the tenant deploys the first device at the tenant site.
  • the tenant site type is cloud
  • the type of the first device is cloud PE.
  • the service provider will deploy the above cloud PEs in the service provider network for the tenant.
  • the first network instance includes information such as the device identification of the first device
  • the second network instance includes information such as the device identification of the first cloud PE.
  • the controller may determine the device information of the first device and the device information of the first cloud PE according to the first network instance and the second network instance, that is, determine and obtain the device information of the endpoint device of the virtual private line.
  • the controller may query the controller for device information of the first device according to the identifier 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 valid configuration information of the first device.
  • the first cloud PE information includes but is not limited to the identifier of the first cloud PE, the management IP address of the first cloud PE, the location information of the first cloud PE, the information that the first cloud PE is connected to the cloud, the routing information of the first cloud PE, 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 usage information of the first cloud PE, CPU usage information of the first cloud PE, and valid configuration information of the first cloud PE.
  • the service of the virtual private network A of tenant A accesses the first cloud through the virtual private line 500 .
  • the service type of virtual cloud private network A is single cloud, that is, tenant A can access only one cloud.
  • the controller 1200 has created the first network instance corresponding to the CPE301 and the second network instance corresponding to the cloud PE401.
  • the controller 1200 acquires 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.
  • S4053 Acquire network resource information according to the device information of the first device and the device 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 the network set or network domain set through which the virtual private line passes according to the network topology information of the service provider network.
  • the purpose of the controller acquiring the network resource information is to acquire the resource information of the network or network domain through which the virtual private line passes.
  • the controller 1200 acquires the network resource information of each network domain in the above-mentioned network domain set.
  • the above-mentioned network resource information includes, but is not limited to, network topology information of the network domain, device information of each network element in the network domain, network connection information existing between network element devices, and the like.
  • the above device information includes but is not limited to the name of the network element device, the type of the network element device, the ESN of the network element device, the management IP address of the network element device, the network location of the network element device, and the like.
  • the above network connection information includes but is not limited to physical links and logical links.
  • Logical link types include but are not limited to Layer 2 VPN tunnels and Layer 3 VPN tunnels.
  • the controller 1200 obtains the network resource information of the network domain A, the network resource information includes but is not limited to: 1. the network topology information of the network domain A; 2. the information of each network element device in the network domain A, the network element device information includes ESN serial number of the element device, NE device type, device model, version information, management IP address, MAC address, etc.; 3. Port information of each NE device, including physical port and logical port information; 4. Between NEs link information, including physical link information, tunnel information, VPN information, etc.
  • S4055 The acquired first configuration information and the second configuration information.
  • the controller obtains 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 obtains the first configuration information and the second configuration information based on the above 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 need to be configured by the first device 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 need to be configured for the first cloud PE to implement the service.
  • the specific acquisition steps are the method 40550 shown in Figure 4(c):
  • S40551 Acquire tunnel configuration information in the first configuration information and 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 to configure 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 the tunnel configuration information that needs to be configured on the first cloud PE.
  • the service provider may define a virtual private line in a single cloud service as a Layer 3 VPN tunnel according to a service plan.
  • the virtual private line 500 in the virtual cloud private network A of tenant A is a Layer 3 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 acquired network resource information of the network domain A and the network domain B.
  • the controller 1200 analyzes whether the existing network resource information is sufficient to establish a Layer 3 VPN tunnel from the CPE301 to the cloud PE401 according to the above-mentioned network resource information.
  • the controller 1200 provides a configuration interface, and the network personnel plan the configuration information of the Layer 3 VPN tunnel that needs to be configured on the CPE301 and the cloud PE401 according to the configuration interface. .
  • the controller 1200 acquires 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 above business template is set before deploying the business instance.
  • the controller Before deploying a service instance, the controller sets a service template according to the service type corresponding to the service instance.
  • a service template indicates configuration information of a service.
  • the configuration information of the service includes but is not limited to tunnel configuration information, VPN instance configuration information or routing information.
  • Service templates include but are not limited to tunnel configuration information, VPN instance configuration information or routing information.
  • the controller creates the first network instance and the second network instance in the service instance, because the service instance has already created an association relationship with the service template, the first network instance and the second network instance have also created an association relationship with the service template.
  • the service templates include but are not limited to tunnel sub-service templates, VPN instance sub-service templates, and routing sub-service templates. Therefore, the first configuration information and the second configuration information can be determined according to the first network instance, the second network instance and each sub-service template.
  • the controller splits the configuration information in the tunnel sub-service template into the first device and the first cloud PE according to the dimensions of the first device and the first cloud PE, and generates the tunnel configuration information and the second configuration in the first configuration information The tunnel configuration information in the message.
  • 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 acquired. If the analysis result fails to establish an end-to-end tunnel to carry the Layer 3 VPN link, the administrator can be prompted to reselect the cloud PE or perform operations such as device expansion, and then obtain the tunnel configuration information.
  • S40553 Acquire VPN instance configuration information in the first configuration information and VPN instance configuration information in the second configuration information.
  • the controller acquires 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 the VPN instance from the first device and the first cloud PE.
  • the VPN instance configuration information in the first configuration information is the VPN instance configuration information that needs to be configured on the first device.
  • the VPN instance configuration information in the second configuration information is the VPN instance configuration information that needs to be configured on the first cloud PE.
  • the virtual private line type of the virtual private network A of the tenant A is a Layer 3 VPN, and it is necessary to obtain the configuration information of the VRF (VPN Routing and Forwarding) of the virtual private network of the CPE301 and the cloud PE401; in other cases
  • the virtual private line type of the virtual cloud private network A of tenant A is Layer 2 VPN, then it is necessary to obtain the Ethernet private virtual network EVPN (Ethernet Virtual Private Network) instance EVI (EVPN Instance) or virtual network of CPE301 and cloud PE401.
  • the controller 1200 may provide a configuration interface, and network personnel plan VPN instance configuration information that needs to be configured on the CPE 301 and the cloud PE 401 according to the configuration interface.
  • the controller 1200 acquires the VPN configuration information of the CPE301 and the cloud PE401 according to the service template corresponding to the service instance of the single cloud.
  • the above business template is set before deploying the business instance.
  • the controller Before deploying a service instance, the controller sets a service template according to the service type corresponding to the service instance.
  • a service template indicates configuration information of a service.
  • the configuration information of the service includes but is not limited to tunnel configuration information, VPN instance configuration information or routing information.
  • Service templates include but are not limited to tunnel configuration information, VPN instance configuration information or routing information.
  • the controller creates the first network instance and the second network instance in the service instance, because the service instance has already created an association relationship with the service template, the first network instance and the second network instance have also created an association relationship with the service template.
  • the service templates include but are not limited to tunnel sub-service templates, VPN instance sub-service templates, and routing sub-service templates. Therefore, the first configuration information and the second configuration information can be determined according to the first network instance, the second network instance and each sub-service template.
  • the controller splits the configuration information in the VPN instance sub-service template into the first device and the first cloud PE according to the dimensions of the first device and the first cloud PE, and generates the VPN instance configuration information and the first cloud PE in the first configuration information.
  • the VPN instance configuration information in the second configuration information.
  • S40555 Acquire routing configuration information in the first configuration information and routing configuration information in the second configuration information.
  • the controller acquires routing configuration information in the first configuration information and 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 to configure routing information of the first device and the first cloud PE.
  • the routing information of the first device is used for data forwarding and routing from the first device to the tenant site side.
  • the routing information of the first cloud PE is used for the 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.
  • the routing configuration information in the first configuration information is used to enable the first device to forward the response data packet from the cloud side to the tenant site.
  • the CPE 301 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 by the cloud PE to forward the data packets from the tenant site side accessing the cloud to the cloud.
  • the data packet from the tenant A site to access the first cloud 50 is forwarded to the first cloud 50 at the cloud PE 401 according to the routing configuration information.
  • the controller 1200 provides a configuration interface, and network personnel plan the routing configuration information that needs to be configured on the CPE301 and the cloud PE401 according to the interface.
  • 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 above business template is set before deploying the business instance.
  • the controller Before deploying a service instance, the controller sets a service template according to the service type corresponding to the service instance.
  • a service template indicates configuration information of a service.
  • the configuration information of the service includes but is not limited to tunnel configuration information, VPN instance configuration information or routing information.
  • Service templates include but are not limited to tunnel configuration information, VPN instance configuration information or routing information.
  • the controller creates the first network instance and the second network instance in the service instance, because the service instance has already created an association relationship with the service template, the first network instance and the second network instance have also created an association relationship with the service template.
  • the service templates include but are not limited to tunnel sub-service templates, VPN instance sub-service templates, and routing sub-service templates. Therefore, the first configuration information and the second configuration information can be determined according to the first network instance, the second network instance and each sub-service template.
  • the controller splits the configuration information in the routing sub-service template into the first device and the first cloud PE according to the dimensions of the first device and the first cloud PE, and generates the routing configuration information and the second configuration in the first configuration information The routing configuration information in the message.
  • the controller 1200 acquires the first configuration information and the second configuration information.
  • S4057 Send the first configuration information to the first device, and send 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 being managed by the controller or not being managed by the controller.
  • the controller can perform management operation and maintenance operations such as configuration management or device status query on the device.
  • the controller cannot obtain information about the device, and cannot manage the configuration of the device.
  • the controller when the controller queries that both the first device and the first cloud PE are already in the managed state, that is, the controller can send configuration information to the first device and the first cloud PE, the controller receives After the message of deploying the 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 controller can send the above configuration information through Simple Network Management Protocol SNMP (Simple Network Management Protocol), Telecom Network Protocol Telnet (Telecommunication Network Protocol), Network Configuration Protocol Netconf (Network Configuration Protocol) or based on User Datagram Protocol UDP (User Datagram Protocol). Datagram Protocol)/Transmission Control Protocol TCP (Transmission Control Protocol) private configuration protocol, etc.
  • the first device and the first cloud PE receive and take effect the first configuration information and the second configuration information.
  • the CPE301 on the tenant A's site side and the cloud PE401 on the first cloud 50 side have the first configuration information and the second configuration information take effect, then between CPE301 and cloud PE401 A virtual private line 500 is established for connecting the tenant A site branch network 10 and the first cloud 50 .
  • the first device or the first cloud PE when the state of the first device or the first cloud PE is not managed by the controller, the first device or the first cloud PE cannot be managed, operated and maintained by the controller, and cannot receive and take effect. configuration information or second configuration information.
  • the controller pre-stores the above configuration information, waits for the first device or the first cloud PE to complete the management and online process, the controller sends the first configuration information or the second configuration information to the first device or the first cloud PE, and completes the first network instance. or a second network instance deployment.
  • the controller automatically acquires the first configuration information corresponding to the first device and the second configuration information corresponding to the first cloud PE according to the first network instance, the second network instance and the preset information, and delivers the first configuration information and the second configuration information corresponding to the first cloud PE through the controller.
  • the second method of configuring information reduces the complexity of manual configuration and improves the efficiency of business deployment.
  • FIG. 7 is a schematic flowchart of a method 700 for service deployment in this application. The above method is executed by the service deployment apparatus 1100 and the controller 1200 in FIG. 2 , and the specific method includes:
  • the service deployment apparatus sends 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, where the first request includes the The ID of the business instance.
  • the service deployment apparatus sends a first request to the controller.
  • the first request is used to call the first API of the controller to create a service instance of the service.
  • the first request includes the identification of the service instance.
  • the service provider uses the service deployment apparatus 1100 shown in FIG. 1(a) to deploy the virtual cloud private network service
  • the controller 1200 provides the API of the service deployment apparatus for the service deployment apparatus 1100 to call to complete the service deploy.
  • Controller 1200 provides a business 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 the service.
  • the above-mentioned first request includes the identifier of the service instance, and the identifier of the service instance includes information that can identify the service instance, such as the name of the service instance or the ID of the service instance.
  • the above-mentioned first request further includes the type of the above-mentioned service instance, the identifier of the tenant, the order information of the tenant, and the like.
  • the types of business instances include single cloud, multi-cloud, etc.
  • the identifier of the tenant includes the name of the tenant, the tenant ID, and the like.
  • the tenant's order information includes order number, order name, and so on.
  • S703 The controller receives the first request sent by the service deployment apparatus.
  • the controller receives the first request sent by the service deployment apparatus.
  • the first request is used to call the first API of the controller to create a service instance of the service.
  • the controller 1200 as shown in FIG. 1( a ) receives the 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 identification of the service instance in the first request.
  • the controller 1200 shown in FIG. 1( a ) after receiving the above-mentioned first request, creates a corresponding service instance according to the identifier of the service instance in the first request.
  • the controller 1200 For the specific process of creating a service instance by the controller 1200, reference may be made to the relevant description of S401, which will not be repeated here.
  • S707 The controller sends the creation result information of the service instance to the service deployment apparatus.
  • the controller sends the creation result information of the service instance to the service deployment apparatus.
  • the controller 1200 shown in FIG. 1( a ) sends the above-mentioned service instance creation result information to the service deployment apparatus 1100 .
  • the creation result information of the business instance includes, but is not limited to: the identifier of the business instance, the success mark of the business instance creation, the failure mark of the business instance creation, and the reason for the failure of the business instance creation.
  • the controller 1200 as shown in FIG. 1( a ) sends the result information of the service instance creation to the service deployment apparatus 1100 after completing the creation of the above-mentioned service instance.
  • the service deployment apparatus 1100 as shown in FIG. 1(a) sends a service instance creation query request to the controller 1200, and the above query request is used to query the result information of the service instance creation by the controller 1200. .
  • the controller 1200 After receiving the above query request, the controller 1200 sends the service instance creation result information to the service deployment apparatus 1100 .
  • the service deployment apparatus receives the creation result information of the service instance sent by the controller.
  • the service deployment apparatus receives the creation result information of the service instance sent by the controller.
  • the controller 1200 as shown in FIG. 1( a ) sends the result information of the service instance creation to the service deployment apparatus 1100 after completing the creation of the above-mentioned service instance.
  • the service deployment apparatus 1100 receives the creation result information of the service instance sent by the controller.
  • the service deployment apparatus 1100 as shown in FIG. 1(a) sends a service instance creation query request to the controller 1200, and the above query request is used to query the result information of the service instance creation by the controller 1200. .
  • the controller 1200 After receiving the above query request, the controller 1200 sends the service instance creation result information 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 The service deployment apparatus outputs the creation result information of the service instance.
  • the service deployment apparatus outputs the creation result information of the service instance.
  • the service deployment apparatus 1100 shown in FIG. 1( a ) may display the acquired service instance creation result information on the display interface of the service deployment apparatus 1100 or the display interface of a third-party system.
  • the service deployment apparatus 1100 may also export the obtained service instance creation result information to the network personnel through file formats such as word, txt, and excel.
  • the service deployment apparatus 1100 may also open the obtained service instance creation result information to other service systems through an API. The manner in which the service deployment apparatus outputs the creation result information of the service instance is not described one by one here.
  • S713 A second request sent by the service deployment apparatus to the controller, where the second request is used to call a second API of the controller to create the first network instance and the second network instance.
  • the second request is used to call the second API of the controller to create the first network instance and the second network instance.
  • the controller 1200 shown in FIG. 1( a ) provides a third-party system with a second API for creating a network instance, and the second API supports creating one network instance or creating multiple network instances in batches.
  • the second request sent by the service deployment apparatus 1100 to the controller 1200 as shown in FIG. 1(a) is used to call the second API of the controller 1200 to Create the first network instance.
  • the second request includes information for creating a first network instance, and the information for creating a first network instance includes the identifier of the service instance, the identifier of the first network instance, and the device identifier of the first device, wherein,
  • the first network instance is 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 second request includes information for creating a second network instance, and the information for creating a second network instance includes the identifier of the service instance, the identifier of the second network instance, and the device identifier of the first cloud PE,
  • the second network instance is used to deploy services.
  • the above-mentioned 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 used to connect to the first cloud.
  • 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 first network instance.
  • the second request includes the information for creating the first network instance and the information for creating the second network instance
  • the information for creating the first network instance includes the identifier of the service instance, the identifier of the first network instance and the
  • the device identification of the first device the information used to create the second network instance includes the identification of the service instance, the identification of the second network instance, and the device identification of the first cloud PE, wherein the first network instance and the second network instance are identified.
  • the network instance is used to deploy services.
  • the first network instance is the network instance corresponding to the first device, the first network instance includes the device identifier of the first device, the second network instance is the network instance corresponding to the first cloud PE, and the second network instance is the network instance corresponding to the first cloud PE.
  • the device identifier of the first cloud PE is included, and the first cloud PE is used to connect to the first cloud.
  • S715 The controller receives the second request sent by the service deployment apparatus.
  • the controller receives the second request sent by the service deployment apparatus.
  • the second request is used to call the second API of the controller to create the first network instance and the second network instance.
  • the controller 1200 when the second API of the controller only supports the creation of one network instance, the controller 1200 as shown in FIG. 1(a) receives the second request sent by the service deployment apparatus 1100, The second API is used to create the first network instance, and the second request includes the identifier of the service instance, the identifier of the first network instance and the device identifier of the first device.
  • the controller 1200 receives the second request sent by the service deployment apparatus 1100, and the second request is used to call the second API of the controller to create a second network instance.
  • the second request includes the identifier of the service instance, the identifier of the second network instance, and the device identifier of the first cloud PE.
  • the controller 1200 receives the second request sent by the service deployment apparatus 1100, and the second request is used to call the second API of the controller to create the first network. instance and a second network instance, and the second request includes the identifier of the service instance, the identifier of the first network instance, the identifier of the second network instance, and the device identifier of the first cloud PE.
  • S717 The controller creates the first network instance and the second network instance.
  • the controller creates the first network instance and the second network instance according to the second request.
  • the controller 1200 shown in FIG. 1( a ) receives the above-mentioned second request, the controller 1200 creates a first network instance and a second network instance.
  • the controller 1200 creates a first network instance and a second network instance.
  • S403 For the specific process of creating a network instance by the controller 1200, reference may be made to the relevant description of S403, which will not be repeated here.
  • S719 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 apparatus.
  • 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 apparatus.
  • 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 .
  • the controller 1200 as shown in FIG. 1(a) after the controller 1200 as shown in FIG. 1(a) completes the creation of the above-mentioned network instance, it sends the result information of the network instance creation to the service deployment apparatus 1100, as created by the first network instance. Result information and result information created by the second network instance.
  • the service deployment apparatus 1100 as shown in FIG. 1(a) sends a network instance creation query request to the controller 1200, and the above query request is used to query the result information of the network instance creation by the controller 1200. .
  • the controller 1200 After receiving the above query request, the controller 1200 sends the creation result information of the network instance to the service deployment apparatus 1100 .
  • the service deployment apparatus receives the creation result information of the first network instance and the creation result of the second network instance sent by the controller.
  • the service deployment apparatus receives the creation result information of the first network instance and the creation result 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 identifier of the first network instance, a successful creation flag of the first network instance, a creation failure flag of the first network instance, and a failure reason for the creation of the first network instance.
  • the creation result information of the second network instance includes, but is not limited to, an identifier of the second network instance, a successful creation flag of the second network instance, a creation failure flag of the second network instance, and a failure reason for the creation of the second network instance.
  • the controller 1200 as shown in FIG. 1(a) after the controller 1200 as shown in FIG. 1(a) completes the creation of the above-mentioned network instance, it sends the result information of the network instance creation to the service deployment apparatus 1100, as created by the first network instance. Result information and result information created by the second network instance.
  • the service deployment apparatus 1100 receives the creation result information of the network instance sent by the controller.
  • the service deployment apparatus 1100 as shown in FIG. 1(a) sends a network instance creation query request to the controller 1200, and the above query request is used to query the result information of the network instance creation by the controller 1200. .
  • the controller 1200 After receiving the above 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.
  • the service deployment apparatus outputs the creation result information of the first network instance and the creation result of the second network instance.
  • the service deployment apparatus outputs the creation result information of the first network instance and the creation result of the second network instance.
  • the service deployment apparatus 1100 shown in FIG. 1( a ) may display the acquired network instance creation result information on the display interface of the service deployment apparatus 1100 or the display interface of a third-party system.
  • the service deployment apparatus 1100 may also export the obtained network instance creation result information to the network personnel through file formats such as word, txt, and excel.
  • the service deployment apparatus 1100 may also open the acquired network instance creation result information to other service systems through APIs and the like. The manner in which the service deployment apparatus outputs the creation result information of the network instance is not described one by one here.
  • S725 A third request sent by the service deployment apparatus to the controller, where the third request is used to call a third API of the controller to deploy the first network instance and the second network instance.
  • the third request is used to call the third API of the controller to deploy the first network instance and the second network instance.
  • the controller 1200 as shown in FIG. 1(a) provides a third API to the third-party system for deploying a network instance, and the third API is used for deploying one network instance and/or deploying multiple network instances in batches .
  • the third request sent by the service deployment apparatus 1100 to the controller 1200 as shown in FIG. 1(a) 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, and the information for deploying the first network instance includes the identifier of the service instance and the identifier of the first network instance.
  • the third request sent by the service deployment apparatus 1100 to the controller 1200 as shown in FIG. 1(a) is used to call the third API of the controller 1200 to Deploy the second network instance.
  • the third request includes information for deploying the second network instance, and the information for deploying the second network instance includes an identifier of a service instance and an identifier of the second network instance.
  • the third request sent by the service deployment apparatus 1100 to the controller 1200 as shown in FIG. 1( a ) 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, and the information for deploying the first network instance includes the identifier of the service instance and the first network instance 's identification.
  • the information for deploying the second network instance includes the identity of the service instance and the identity of the second network instance.
  • S727 The controller receives the third request sent by the service deployment apparatus.
  • the controller receives the third request sent by the service deployment apparatus.
  • the third request is used to call the 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 .
  • the controller 1200 provides the third-party system with a third API for deploying a network instance, and the third API is used for deploying one network instance and/or deploying multiple network instances in batches.
  • 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, and the information for deploying the first network instance includes the identifier of the service instance and the identifier of the first network instance.
  • the third request is used to call the third API of the controller 1200 to deploy the second network instance.
  • the third request includes information for deploying the second network instance, and the information for deploying the second network instance includes an identifier of a service instance and an identifier of the second network instance.
  • 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, and the information for deploying the first network instance includes the identifier of the service instance and the first network instance 's identification.
  • the information for deploying the second network instance includes the identification of the service instance and the identification of the second network instance.
  • S7029 The 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 the third request.
  • the controller 1200 shown in FIG. 1( a ) deploys the first network instance and the second network instance.
  • S405 For the specific process of deploying the first network instance and the second network instance by the controller 1200, reference may be made to the relevant description of S405, which will not be repeated here.
  • S731 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 apparatus.
  • 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 apparatus.
  • the deployment result information of the first network instance includes, but is not limited to: the identifier 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 reason for the deployment failure of the first network instance.
  • the deployment result information of the second network instance includes but is not limited to: the identifier 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 reason for the deployment failure of the second network instance.
  • the controller 1200 shown in FIG. 1( a ) sends 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 .
  • the controller 1200 as shown in FIG. 1(a) after the controller 1200 as shown in FIG. 1(a) completes the deployment of the above-mentioned network instance, it sends the result information of the network instance deployment to the service deployment apparatus 1100, such as the first network instance deployment result information.
  • the result information and the result information of the deployment of the second network instance are the result information of the network instance deployment to the service deployment apparatus 1100.
  • the service deployment apparatus 1100 as shown in FIG. 1(a) sends a network instance deployment query request to the controller 1200, and the above query request is used to query the result information of the network instance deployment of the controller 1200. . After receiving the above query request, the controller 1200 sends the deployment result information of the network instance to the service deployment apparatus 1100.
  • the service deployment apparatus receives the deployment result information of the first network instance and the deployment result information of the second network instance sent by the controller.
  • the service deployment apparatus receives the deployment result information of the first network instance and the deployment result information of the second network instance sent by the controller.
  • the controller 1200 as shown in FIG. 1(a) after the controller 1200 as shown in FIG. 1(a) completes the deployment of the above-mentioned network instance, it sends the result information of the network instance deployment to the service deployment apparatus 1100, such as the first network instance deployment result information.
  • the result information and the result information of the deployment of the second network instance The service deployment apparatus 1100 receives the deployment result information of the network instance sent by the controller.
  • the service deployment apparatus 1100 as shown in FIG. 1(a) sends a network instance deployment query request to the controller 1200, and the above query request is used to query the result information of the network instance deployment of the controller 1200. .
  • the controller 1200 After receiving the above query request, the controller 1200 sends the 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 Output the deployment result information of the first network instance and the deployment result information of the second network instance.
  • the service deployment apparatus outputs the deployment result information of the first network instance and the deployment result information of the second network instance.
  • the service deployment apparatus 1100 shown in FIG. 1( a ) may display the acquired network instance deployment result information on the display interface of the service deployment apparatus 1100 or the display interface of a third-party system.
  • the service deployment apparatus 1100 may also export the acquired network instance deployment result information to the network personnel through file formats such as word, txt, and excel.
  • the service deployment apparatus 1100 may also open the obtained network instance deployment result information to other service systems through APIs and 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 apparatus to the controller, where the fourth request is used to call a fourth API of the controller to delete the service instance.
  • the fourth request is used to call the fourth API of the controller to delete the service instance.
  • the fourth request sent by the service deployment apparatus 1100 to the controller 1200 as shown in FIG. 1( a ) is used to call the 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 the identifier of the service instance to be deleted.
  • S739 The controller receives the fourth request sent by the service deployment apparatus.
  • the controller receives the fourth request sent by the service deployment apparatus.
  • the fourth request is used to call the 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 .
  • the controller deletes the business instance.
  • the controller 1200 shown in FIG. 1(a) 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 controller first determines whether there is a deployed network instance in the service instance to be deleted. If there is no deployed network instance, the controller deletes the corresponding service instance on the controller according to the identifier of the service instance carried in the fourth request.
  • the controller obtains the information of the corresponding service instance according to the identifier of the service instance.
  • the information of the above service instance includes the type of the service instance, the information of the created network instance, the order information of the tenant, and the like. Obtain the created network instance through the information of the created network instance in the information of the service instance. Obtain the network device corresponding to the above network instance through the information of the created network instance.
  • the controller Before deleting the configuration information related to the above-mentioned service instance in the above-mentioned network device, the controller needs to determine whether there are network resources shared by other service instances in the above-mentioned network device. If there is no shared network resource, the controller deletes the above-mentioned service instance. Configure information, delete the network instance related to the service instance, and complete the deletion operation. If there are shared network resources, the controller does not delete the configuration information and ends the deletion operation.
  • the above configuration information includes tunnel configuration information, VPN instance information and routing information.
  • Directly create a service instance corresponding to the virtual cloud private network service by calling the service-oriented API of the controller in the service deployment device, and create the corresponding first network instance and second network instance in the service instance, and deploy the first network instance and the third network instance.
  • the second network instance reduces the number of interactions between the service deployment device and the controller, reduces the complexity of manual configuration and the difficulty of service deployment, and improves the efficiency of service deployment.
  • 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 execute the foregoing multiple embodiments through the service deployment apparatus 1100 and the controller 1200 shown in FIG. 7 , for example, the service deployment in the embodiments corresponding to FIG. 4( a )- FIG. 4( c ) The operation performed by the system.
  • the service deployment system 800 includes the following modules.
  • the service instance creation module 8001 is configured to create a service instance corresponding to the service.
  • a network instance creation 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, wherein the first network instance and the second network instance are used to deploy the service.
  • a 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 the edge PE of the first cloud operator
  • the first network instance is a network instance corresponding to the edge PE of the first cloud operator.
  • the second network instance includes the device identifier of the first cloud PE
  • the first cloud PE is used to connect to the first cloud.
  • the service deployment system 800 further includes: an information setting module 8003 .
  • An information setting module 8003 configured to set connection information for the first cloud PE to connect to the first cloud, where the connection information includes one or more of the following: the device identifier of the first cloud PE, the first cloud PE The location information of the cloud PE, the identifier of the first interface of the first cloud PE, the identifier of the first virtual local area network VLAN of the first cloud PE, the first interface is used for the first cloud PE to connect the A first cloud, where the first VLAN is used for the first cloud PE to connect to 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.
  • the service deployment system 800 further includes: a network instance deployment module 8004 .
  • the network instance deployment module 8004 is further configured to send the first configuration information to the first device.
  • the first configuration information is used to configure 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 the first service template.
  • the first service template indicates configuration information of the service instance, and the configuration information of the service instance includes one or more of the following: tunnel configuration information, virtual private network VPN instance configuration information, or routing information.
  • the service deployment system 800 further includes: a request message processing module 8005 .
  • the request message processing module 8005 is configured to receive the first request sent by the service deployment apparatus.
  • the first request is used for invoking a first application programming interface API of the controller to create the service instance, and the first request includes an identifier 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 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 a first network instance and/or information for creating a second network instance.
  • the information for creating the first network instance includes the identifier of the service instance, the identifier of the first network instance, and the device identifier of the first device.
  • the information for creating the second network instance includes the identifier of the service instance, the identifier of the second network instance, and the device identifier 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 used to call 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 identifier of the service instance and an identifier of the first network instance.
  • the information for deploying the second network instance includes an identifier of the service instance and an identifier of the second network instance.
  • the request message processing module 8005 is further configured to receive 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 the deployment result of the first network instance and/or or the deployment result of the second network instance.
  • the request message processing module 8005 is further configured to send the first request to the controller.
  • 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 8005 is further configured to send a second request to the controller.
  • 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.
  • 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 a device identifier of the first device.
  • the information for creating the second network instance includes the identifier of the service instance, the identifier of the second network instance, and the device identifier 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 includes a device identifier of the first device.
  • the second network instance is a network instance corresponding to the edge PE of the first cloud operator, and the second network instance includes the device identifier of the first cloud PE.
  • the first cloud PE is used to connect to the first cloud. It is also used 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 identifier of the service instance and an identifier of the first network instance.
  • the information for deploying the second network instance includes an identifier of the service instance and an identifier of the second network instance.
  • the service deployment system 800 further includes: a result information processing module 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.
  • the result information processing module 8006 is further configured to receive the creation result information of the service instance sent by the controller. It is also used to output the creation result information of the business instance. It is further configured to receive the creation result information of the first network instance and/or the creation result of the second network instance sent by the controller. It is also used to output the creation result information of the first network instance and/or the creation result of the second network instance. It 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 sent by the controller. It is also used to output the deployment result information of the first network instance and/or the deployment result information of the second network instance.
  • Each module shown in FIG. 8 may be a software function module, a virtual function module, or a hardware module.
  • each module in the service deployment system 800 may be deployed in the same physical device; in other embodiments, each module in the service deployment system 800 may be deployed in multiple different physical devices.
  • Each module in the service deployment system 800 may be a hardware module or a module combining software and hardware.
  • 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 can be deployed in a physical device for The method 700 performed by the controller 1200 in the embodiment shown in FIG. 7 is performed.
  • 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 to execute the method 700 of the service deployment apparatus 1100 in the embodiment shown in FIG. 7 .
  • FIG. 9 is a schematic structural diagram of a service deployment apparatus provided by an embodiment of the present application.
  • the service deployment apparatus 900 shown in FIG. 9 is configured to perform operations performed by the service deployment apparatus 1100 or the controller 1200 in the foregoing embodiments, for example, the embodiment corresponding to FIG. 7 .
  • the apparatus 900 includes at least one processor 901 , a connection line 902 , a memory 903 and at least one network interface 904 .
  • the memory 903 is used to store program modules and data.
  • the program modules stored in the memory 903 include a service instance creation module 9031 and a network instance creation module 9032 .
  • the service instance creation module 9031 When executed by the processor 901, the service instance creation module 9031 is configured to create a service instance corresponding to the service.
  • the network instance creation module 9032 is configured to create a first network instance and a second network instance in the service instance, and the first network instance and the second network instance are used for deploying all network instances.
  • the service 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, and the second network instance is a first cloud operator edge PE
  • the second network instance For a corresponding network instance, 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 program modules stored in the memory 903 include one or more of the following modules: an information setting module 9033 , a network instance deployment module 9034 , a request message processing module Module 9035, result information processing module 9036.
  • the information setting module 9033 is 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 first cloud PE The device identifier of the first cloud PE, the location information of the first cloud PE, the identifier of the first interface of the first cloud PE, the identifier of the first virtual local area network VLAN of the first cloud PE, and the first interface is used for all The first cloud PE is connected to the first cloud, and the first VLAN is used for the first cloud PE to connect to 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.
  • the network instance deployment module 9034 is configured to execute the method steps performed by the controller described in S405 in the method 400 shown in FIG. 4(a), which will not be repeated here.
  • the request message processing module 9035 when executed by the processor 901, is configured to execute the method steps performed by the controller 1200 as described in the method 700 shown in FIG. 7, which will not be repeated here.
  • the request message processing module 9035 when executed by the processor 901 , is configured to execute the method steps performed by the service deployment apparatus 1100 described in the method 700 shown in FIG. 7 , which will not be repeated here.
  • the processor 901 is, for example, a general-purpose central processing unit (central processing unit, CPU), a digital signal processor (digital signal processor, DSP), a network processor (network processor, NP), a graphics processor (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 solution of the present application.
  • CPU central processing unit
  • DSP digital signal processor
  • NP network processor
  • GPU Graphics Processing Unit
  • NPU neural-network processing unit
  • DPU data processing unit
  • microprocessor or one or more integrated circuits for implementing the solution of the present application.
  • the processor 901 includes an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the PLD is, for example, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. It can implement or execute various logical blocks, modules and circuits described in connection with the disclosure of the embodiments of the present application.
  • the processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
  • the service deployment apparatus 900 may also include a connection line 902 .
  • the connection line 902 is used to transfer information between the components of the service deployment apparatus 900 .
  • the bus may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, or the like.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • the memory 903 is, for example, a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, or a random access memory (random access memory, RAM) or a memory device that can store information and instructions.
  • Other types of dynamic storage devices such as electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disks storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of Any other medium accessed by a computer without limitation.
  • the memory 903 exists independently, for example, and is connected to the processor 901 through a bus.
  • the memory 903 may also be integrated with the processor 901 .
  • the network interface 904 uses any transceiver-like device for communicating with other devices or a communication network, such as Ethernet, Radio Access Network (RAN), or Wireless Local Area Networks (WLAN).
  • the network interface 904 may include a wired communication interface and may also include a wireless communication interface.
  • the network interface 904 may be an Ethernet (Ethernet) interface, a Fast Ethernet (FE) interface, a Gigabit Ethernet (GE) interface, an asynchronous transfer mode (Asynchronous Transfer Mode, ATM) interface, a wireless local area network ( wireless local area networks, WLAN) interfaces, cellular network communication interfaces, or a combination thereof.
  • the Ethernet interface can be an optical interface, an electrical interface or a combination thereof.
  • the network interface 904 may be used for the service deployment apparatus 900 to communicate with other devices.
  • the processor 901 may include one or more CPUs. Each of these processors can 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 (eg, computer program instructions).
  • the service deployment apparatus 900 may include multiple processors. Each of these processors can 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 (eg, computer program instructions).
  • the service deployment apparatus 900 may further include an output device and an input device.
  • the output device communicates with the processor 901 and can display information in a variety of ways.
  • 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, or the like.
  • the input device communicates with the processor 901 and can receive user input in a variety of ways.
  • the input device may be a mouse, a keyboard, a touch screen device, or a sensor device, or the like.
  • the service deployment apparatus 900 shown in FIG. 9 is configured to perform operations performed by the service deployment apparatus in the foregoing multiple embodiments, for example, the embodiment corresponding to FIG. 7 .
  • the service deployment apparatus 900 includes at least one processor 901 , and by executing the computer-readable program in the memory 903 , the service deployment apparatus 900 can execute the foregoing multiple embodiments, for example, the control in the embodiment corresponding to FIG. 7 . operations performed by the server 1200 or the service deployment device 1100.
  • Some embodiments of the present application provide a computer program product that, when executed by a computer, enables the computer to perform the operations performed by the service deployment systems in the 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 thereon. When the computer executes the computer-readable instructions, the operations performed by the service deployment systems in the embodiments of the present application can be performed.
  • Some embodiments of the present application provide a service deployment system including multiple modules, and the multiple modules work together to perform operations performed by the service deployment systems in the embodiments of the present application.
  • the multiple modules may be in the same hardware device, or may be in different hardware devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供了一种业务的部署方法、装置及系统。该方法中，控制器创建与业务对应的业务实例，并在业务实例中创建业务对应的第一网络实例和第二网络实例，其中，第一网络实例是第一设备对应的网络实例，第一网络实例包括第一设备的设备标识，第二网络实例是第一云运营商边缘PE对应的网络实例，第二网络实例包括第一云PE的设备标识，第一云PE用于连接所述第一云。该方法简化了虚拟云专网业务部署的流程，降低业务部署的复杂度，提升业务部署的效率和准确率。

Description

一种业务的部署方法、装置及系统
本申请要求于2021年3月18日提交的申请号为202110293083.8、发明名称为“一种业务部署的方法及系统”的中国专利申请的优先权，以及于2021年9月30日提交中国专利局、申请号为202111164145.1、发明创造名称为“一种业务的部署方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别涉及一种业务的部署方法、装置及系统。
背景技术
随着企业业务云化的趋势日趋显著对云服务的广泛使用，使得企业用户的关注点从网络连通性转移到业务质量、体验和安全等方面。服务提供商和运营商希望为企业用户提供可以保障业务质量、体验和安全的虚拟云专网的业务。但是业务的开通和部署需要依赖技术人员自行规划和部署，业务部署复杂程度高，部署工作量较大，导致业务部署效率低且易出错。
发明内容
本申请实施例提供了一种业务的部署方法、装置及系统，通过控制器创建与业务对应的业务实例，并在业务实例中创建对应的网络实例，可以简化业务部署的流程，降低业务部署的复杂度，提升业务部署的效率和准确率。
第一方面，本申请实施例提供了一种业务的部署方法，该业务是租户提供虚拟云专网。该虚拟云专网用于租户访问第一云。上述方法由控制器执行，该控制器创建与业务对应的业务实例；控制器在业务实例中创建第一网络实例和第二网络实例。第一网络实例和第二网络实例用于部署业务。其中，第一网络实例是第一设备对应的网络实例，第一网络实例包括第一设备的设备标识。第一设备的设备标识包括但不限于第一设备的设备序列号ESN、第一设备的设备名称、或第一设备的媒体接入控制MAC地址。第二网络实例是第一云运营商边缘PE对应的网络实例，第二网络实例包括第一云PE的设备标识。第一云PE的设备标识包括但不限于第一云PE的设备序列号ESN、第一云PE的设备名称、第一云PE的媒体接入控制MAC地址。第一云PE用于连接第一云。第一设备和第一云PE是该虚拟云专网的边缘设备。租户通过第一设备和第一云PE访问云。上述方法将虚拟云专网业务的部署流程简化为业务实例、第一网络实例和第二网络实例的创建，降低了业务部署的复杂度，提升了业务部署的效率和准确率。
在一种实现方式中，在控制器创建该业务实例之前，设置第一云PE连接第一云的连接信息。连接信息包括以下一项或多项：第一云PE的设备标识，第一云PE的位置信息，第一云PE的第一接口的标识，第一云PE的第一虚拟局域网VLAN的标识，第一接口配置第一VLAN，第一云PE通过第一VLAN连接第一云。通过在控制器先设置第一云PE的连接信息，后续在创建业务实例或创建第二网络实例时， 可以通过连接信息中的一个或多个信息关联出第一云PE的设备标识等信息，减少了业务部署流程中网络参数的设置次数，进一步提升了业务部署的效率。
在一种实现方式中，上述业务实例包括业务实例的标识。业务实例的标识包括但不限于业务实例的名称、业务实例的标识符ID等可标识业务实例的信息。该业务实例还包括以下一项或多项：业务实例的类型、已创建的网络实例的数量、租户的订单信息。
在一种实现方式中，业务实例的类型包括单云或多云，单云是指租户通过第一设备仅可访问一个云，多云是指租户通过第一设备可访问多个云。
在一种实现方式中，第一设备的设备类型为用户驻地设备CPE。当第一设备是第一CPE时，第一网络实例还包括以下一项或多项：第一CPE的位置信息、第一CPE的网络侧IP地址、第一CPE的租户侧IP地址、第一CPE至租户的局域网的路由信息。
在一种实现方式中，第一设备的设备类型为云PE。当第一设备是第二云PE时，第二云PE用于连接第二云。即虚拟云专网的边缘设备为第二云PE和第一云PE。第一网络实例还包括以下一项或多项：第二云PE的位置信息、第二云的供应商信息、第二云PE连接第二云的IP地址，第二云PE连接第二云的路由信息、第二云PE连接第二云的接口服务质量信息。
在一种实现方式中，第二网络实例还包括以下一项或多项：第一云PE的位置信息、第一云的供应商信息、第一云PE连接第一云的IP地址，第一云PE连接第一云的路由信息、第一云PE连接第一云的接口服务质量信息。
在一种实现方式中，控制器根据第一云PE的位置信息和第一云PE连接第一云的连接信息，确定第一云PE的设备标识。
在一种实现方式中，控制器部署第一网络实例和第二网络实例。网络运维人员通过上述方法将虚拟云专网业务的部署流程简化为在控制上创建业务实例、创建第一网络实例和第二网络实例、部署第一网络实例和第二网络实例。该方法进一步简化了业务部署的流程，降低了业务部署的复杂度，提升了业务部署的效率和准确率。在一种实现方式中，控制器向第一设备发送用于配置业务第一配置信息；向第一云PE发送用于配置业务第二配置信息。
在一种实现方式中，控制器根据第一网络实例、第二网络实例和第一业务模板确定第一配置信息和第二配置信息。其中，第一业务模板指示业务实例的配置信息。业务实例的配置信息包括以下一项或多项：隧道配置信息、虚拟专用网络VPN实例配置信息或路由信息。在部署第一网络实例和第二网络实例之前，控制器根据业务实例的类型设置了第一业务模板。设置第一业务模板的目的是将业务实例对应的业务在配置隧道、配置VPN实例、配置路由等方面的配置信息进行模板化。在业务部署过程之中，每个类型的业务实例对应一个业务模板，可以快速的获得该业务实例的配置信息，从而解决了网络运维人员在部署业务时需要为每一个业务设置大量的配置信息的问题。通过业务模板获取配置信息的方法简化了在虚拟云专网业务部署中获取配置信息的流程，进一步提升了业务部署的效率。
在一种实现方式中，虚拟云专网还用于租户访问第三云。控制器在业务实例中创建第三网络实例。第三网络实例是第三云PE对应的网络实例，第三网络实例包括第三云 PE的设备标识。第三云PE用于连接第三云。
在一种实现方式中，在控制器创建业务实例之前，控制器接收业务部署装置发送的第一请求。第一请求用于业务部署装置调用控制器的第一应用程序编程接口API来创建业务实例，第一请求包括业务实例的标识。第一请求还包括以下一项或多项：业务实例的类型、租户的标识、租户的订单信息。
在一种实现方式中，在控制器创建第一网络实例和第二网络实例前，控制器接收业务部署装置发送的第二请求。第二请求用于业务部署装置调用控制器的第二API来创建第一网络实例和/或第二网络实例。第二请求包括用于创建第一网络实例的信息和/或用于创建第二网络实例的信息。用于创建第一网络实例的信息包括业务实例的标识、第一网络实例的标识和第一设备的设备标识。用于创建第二网络实例的信息包括业务实例的标识、第二网络实例的标识和第一云PE的设备标识。
在一种实现方式中，当第一设备为第一CPE时，用于创建第一网络实例的信息还包括以下一项或多项：第一CPE的位置信息、第一CPE的网络侧IP地址、第一CPE的租户侧IP地址、第一CPE至所述租户的局域网的路由信息。
在一种实现方式中，第二云PE用于连接第二云。当第一设备为第二云PE时，用于创建第一网络实例的信息还包括以下一项或多项：第二云PE的位置信息、第二云的供应商信息、第二云PE连接第二云的IP地址，第二云PE连接第二云的路由信息、第二云PE连接第二云的接口服务质量信息。
在一种实现方式中，用于创建第二网络实例的信息包括以下一项或多项：第一云PE的位置信息、第一云的供应商信息、第一云PE连接第一云的IP地址，第一云PE连接第一云的路由信息、第一云PE连接第一云的接口服务质量信息。
在一种实现方式中，在控制器部署第一网络实例和第二网络实例之前，控制器接收业务部署装置发送的第三请求。第三请求用于业务部署装置调用控制器的第三API来部署第一网络实例和/或第二网络实例。第三请求包括用于部署第一网络实例的信息和/或用于部署第二网络实例的信息。用于部署第一网络实例的信息包括业务实例的标识和第一网络实例的标识。用于部署第二网络实例的信息包括业务实例的标识和第二网络实例的标识。
在一种实现方式中，控制器向业务部署装置发送第一网络实例的部署结果信息和/或第二网络实例的部署结果信息。第一网络实例的部署结果信息包括但不限于：第一网络实例的标识、第一网络实例的部署成功标记、第一网络实例的部署失败标记、第一网络实例的部署失败原因。第二网络实例的部署结果信息包括但不限于：第二网络实例的标识、第二网络实例的部署成功标记、第二网络实例的部署失败标记、第二网络实例的部署失败原因。
在一种实现方式中，控制器接收业务部署装置发送的第四请求，第四请求用于调用控制器的第四API来获得第一网络实例的部署结果信息和/或第二网络实例的部署结果信息。
在一种实现方式中，控制器向业务部署装置发送业务实例的创建结果信息。业务实例的创建结果信息包括但不限于：业务实例的标识、业务实例的创建成功标记、 业务实例的创建失败标记、业务实例的创建失败原因。
在一种实现方式中，控制器接收业务部署装置发送的第五请求，第五请求用于调用控制器的第五API来获得业务实例的创建结果信息。
在一种实现方式中，控制器向业务部署装置发送第一网络实例的创建结果信息和/或第二网络实例的创建结果信息。第一网络实例的创建结果信息包括但不限于：第一网络实例的标识、第一网络实例的创建成功标记、第一网络实例的创建失败标记、第一网络实例的创建失败原因。第二网络实例的创建结果信息包括但不限于：第二网络实例的标识、第二网络实例的创建成功标记、第二网络实例的创建失败标记、第二网络实例的创建失败原因。
在一种实现方式中，控制器接收业务部署装置发送的第六请求，第六请求用于调用控制器的第六API来获得第一网络实例的创建结果信息和/或第二网络实例的创建结果信息。在一种实现方式中，虚拟云专网用于租户的至少一个站点通过至少一条虚拟专用线路访问第一云。
在一种实现方式中，第一云包括至少一个虚拟私有云VPC。
在一种实现方式中，租户的至少一个站点中的每个站点的类型包括：分支网络或云。
第二方面，本申请实施例提供了一种业务的部署方法，业务是为租户提供虚拟云专网。虚拟云专网用于租户访问第一云。上述方法由业务部署装置执行，业务部署装置向控制器发送第一请求，第一请求用于调用控制器的第一应用程序编程接口API来创建业务的业务实例，第一请求包括业务实例的标识；向控制器发送第二请求，第二请求用于调用控制器的第二API来创建第一网络实例和/或第二网络实例。第二请求包括用于创建第一网络实例的信息和/或用于创建第二网络实例的信息。用于创建第一网络实例的信息包括业务实例的标识、第一网络实例的标识和第一设备的设备标识。用于创建第二网络实例的信息包括业务实例的标识、第二网络实例的标识和第一云PE的设备标识。其中，第一网络实例和第二网络实例用于部署业务。第一网络实例是第一设备对应的网络实例，第一网络实例包括第一设备的设备标识。第二网络实例是第一云运营商边缘PE对应的网络实例，第二网络实例包括第一云PE的设备标识。第一云PE用于连接第一云。第一设备和第一云PE是虚拟云专网的边缘设备。租户通过第一设备和第一云PE访问云。网络人员通过业务部署装置调用控制器提供的服务化接口进行业务部署，将虚拟云专网业务部署的流程简化为创建业务实例、创建第一网络实例和第二网络实例，降低了业务部署的复杂度，提升了业务部署的效率和准确率。
在一种实现方式中，上述第一请求还包括以下一项或多项：业务实例的类型、租户的标识、租户的订单信息。
在一种实现方式中，第一设备的设备类型为用户驻地设备CPE。当第一设备为第一CPE时，用于创建第一网络实例的信息还包括以下一项或多项：第一CPE的位置信息、第一CPE的网络侧IP地址、第一CPE的租户侧IP地址、第一CPE至所述租户的局域网的路由信息。
在一种实现方式中，第一设备的设备类型为云PE。第二云PE用于连接第二云。当第一设备为第二云PE时，用于创建第一网络实例的信息还包括以下一项或多项：第二 云PE的位置信息、第二云的供应商信息、第二云PE连接第二云的IP地址，第二云PE连接第二云的路由信息、第二云PE连接第二云的接口服务质量信息。
在一种实现方式中，用于创建第二网络实例的信息包括以下一项或多项：第一云PE的位置信息、第一云的供应商信息、第一云PE连接第一云的IP地址，第一云PE连接第一云的路由信息、第一云PE连接第一云的接口服务质量信息。在一种实现方式中，业务部署装置向控制器发送第三请求。第三请求用于业务部署装置调用控制器的第三API来部署第一网络实例和/或第二网络实例。第三请求包括用于部署第一网络实例的信息和/或用于部署第二网络实例的信息。用于部署第一网络实例的信息包括业务实例的标识和第一网络实例的标识，用于部署第二网络实例的信息包括业务实例的标识和第二网络实例的标识。
在一种实现方式中，业务部署装置接收控制器发送的业务实例的创建结果信息。业务实例的创建结果信息包括但不限于：业务实例的标识、业务实例的创建成功标记、业务实例的创建失败标记、业务实例的创建失败原因。
在一种实现方式中，业务部署装置输出业务实例的创建结果信息。
在一种实现方式中，业务部署装置接收控制器发送的第一网络实例的创建结果信息和/或第二网络实例的创建结果信息。第一网络实例的创建结果信息包括但不限于：第一网络实例的标识、第一网络实例的创建成功标记、第一网络实例的创建失败标记、第一网络实例的创建失败原因。第二网络实例的创建结果信息包括但不限于：第二网络实例的标识、第二网络实例的创建成功标记、第二网络实例的创建失败标记、第二网络实例的创建失败原因。
在一种实现方式中，业务部署装置输出第一网络实例的创建结果信息和/或第二网络实例的创建结果信息。
在一种实现方式中，业务部署装置接收控制器发送的第一网络实例的部署结果信息和/或第二网络实例的部署结果信息。第一网络实例的部署结果信息包括但不限于：第一网络实例的标识、第一网络实例的部署成功标记、第一网络实例的部署失败标记、第一网络实例的部署失败原因。第二网络实例的部署结果信息包括但不限于：第二网络实例的标识、第二网络实例的部署成功标记、第二网络实例的部署失败标记、第二网络实例的部署失败原因。
在一种实现方式中，业务部署装置输出第一网络实例的部署结果信息和/或第二网络实例的部署结果信息。
在一种实现方式中，业务实例的类型包括：单云或多云，单云是指租户通过第一设备仅可访问一个云，多云是指租户通过第一设备可访问多个云。
在一种实现方式中，虚拟云专网用于租户的至少一个站点通过至少一条虚拟专用线路访问第一云。
在一种实现方式中，第一云包括至少一个虚拟私有云VPC。
在一种实现方式中，租户的至少一个站点中的每个站点的类型包括：分支网络或云。
第三方面，本申请实施例提供了一种业务部署的装置。业务是为租户提供虚拟云专网，虚拟云专网用于租户访问第一云。该装置包括：业务实例创建模块，用于创建与业 务对应的业务实例。该装置包括：网络实例创建模块，用于在业务实例中创建第一网络实例和第二网络实例。第一网络实例和第二网络实例用于部署业务。其中，第一网络实例是第一设备对应的网络实例，第一网络实例包括第一设备的设备标识。第一设备的设备标识包括但不限于第一设备的设备序列号ESN、第一设备的设备名称、或第一设备的媒体接入控制MAC地址。第二网络实例是第一云运营商边缘PE对应的网络实例，第二网络实例包括第一云PE的设备标识。第一云PE的设备标识包括但不限于第一云PE的设备序列号ESN、第一云PE的设备名称、第一云PE的媒体接入控制MAC地址。第一云PE用于连接第一云。第一设备和第一云PE是虚拟云专网的边缘设备。租户通过第一设备和第一云PE访问云。通过上述装置，通过该业务部署装置部署虚拟云专网业务科将业务部署的流程简化为创建业务实例、创建第一网络实例和第二网络实例，降低了业务部署的复杂度，提升了业务部署的效率和准确率。
在一种实现方式中，该装置还包括：信息设置模块，用于设置第一云PE连接第一云的连接信息。该连接信息包括以下一项或多项：第一云PE的设备标识，第一云PE的位置信息，第一云PE的第一接口的标识，第一云PE的第一虚拟局域网VLAN的标识，第一接口用于第一云PE连接第一云，第一VLAN用于第一云PE连接第一云。通过在该装置上设置第一云PE的连接信息，在创建业务实例或创建第二网络实例时，可以通过连接信息中的一个或多个信息关联出第一云PE的设备标识等信息，减少了业务部署流程中网络参数的设置次数，进一步提升了业务部署的效率。在一种实现方式中，该业务实例包括业务实例的标识。业务实例的标识包括但不限于业务实例的名称、业务实例的标识符ID等可标识业务实例的信息。
在一种实现方式中，该业务实例还包括以下一项或多项：业务实例的类型、已创建的网络实例的数量、租户的订单信息。
在一种实现方式中，业务实例的类型包括单云或多云，单云是指租户通过第一设备仅可访问一个云，多云是指租户通过第一设备可访问多个云。
在一种实现方式中，第一设备的设备类型为用户驻地设备CPE。当第一设备是第一CPE时，第一网络实例还包括以下一项或多项：第一CPE的位置信息、第一CPE的网络侧IP地址、第一CPE的租户侧IP地址、第一CPE至租户的局域网的路由信息。
在一种实现方式中，第一设备的设备类型为云PE。第二云PE用于连接第二云。当第一设备为第二云PE时，第一网络实例还包括以下一项或多项：第二云PE的位置信息、第二云的供应商信息、第二云PE连接第二云的IP地址，第二云PE连接第二云的路由信息、第二云PE连接第二云的接口服务质量信息。
在一种实现方式中，第二网络实例还包括以下一项或多项：第一云PE的位置信息、第一云的供应商信息、第一云PE连接第一云的IP地址，第一云PE连接第一云的路由信息、第一云PE连接第一云的接口服务质量信息。
在一种实现方式中，该装置还包括：网络实例创建模块，还用于根据第一云PE的位置信息和第一云PE连接第一云的连接信息，确定第一云PE的设备标识。
在一种实现方式中，该装置还包括：网络实例部署模块，用于部署第一网络实例和第二网络实例。该装置将虚拟云专网业务的部署流程简化为在控制上创建业务实例、创 建第一网络实例和第二网络实例、部署第一网络实例和第二网络实例。该装置进一步简化了业务部署的流程，降低了业务部署的复杂度，提升了业务部署的效率和准确率。
在一种实现方式中，该装置还包括：网络实例部署模块，还用于向第一设备发送第一配置信息，第一配置信息用于配置业务；还用于向第一云PE发送第二配置信息，第二配置信息用于配置业务。
在一种实现方式中，该装置还包括：网络实例部署模块，还用于根据第一网络实例、第二网络实例和第一业务模板确定第一配置信息和第二配置信息。其中，第一业务模板指示业务实例的配置信息。业务实例的配置信息包括以下一项或多项：隧道配置信息、虚拟专用网络VPN实例配置信息或路由信息。
在一种实现方式中，该装置还包括：信息设置模块，还用于根据业务实例的类型，设置第一业务模板。在部署第一网络实例和第二网络实例之前，该装置根据业务实例的类型设置第一业务模板。设置第一业务模板的目的是将业务实例对应的业务在配置隧道、配置VPN实例、配置路由等方面的配置信息进行模板化。在业务部署过程中，每个类型的业务实例对应一个业务模板。根据业务模板可以快速的获得该业务实例的配置信息，从而解决了网络运维人员在部署业务时需要为每一个业务设置大量的配置信息的问题。通过业务模板获取配置信息的方法简化了在虚拟云专网业务部署中获取配置信息的流程，进一步提升了业务部署的效率。在一种实现方式中，虚拟云专网还用于租户访问第三云。网络实例创建模块，还用于在业务实例中创建第三网络实例。第三网络实例是第三云PE对应的网络实例，第三网络实例包括第三云PE的设备标识。第三云PE用于连接第三云。
在一种实现方式中，该装置还包括：请求消息处理模块，用于接收业务部署装置发送的第一请求。第一请求用于调用该装置的第一应用程序编程接口API来创建业务实例，第一请求包括业务实例的标识。
在一种实现方式中，该第一请求还包括以下一项或多项：业务实例的类型、租户的标识、租户的订单信息。
在一种实现方式中，该装置还包括：请求消息处理模块，还用于接收业务部署装置发送的第二请求。第二请求用于调用该装置的第二API来创建第一网络实例和/或第二网络实例。第二请求包括用于创建第一网络实例的信息和/或用于创建第二网络实例的信息。用于创建第一网络实例的信息包括业务实例的标识、第一网络实例的标识和第一设备的设备标识。用于创建第二网络实例的信息包括业务实例的标识、第二网络实例的标识和第一云PE的设备标识。
在一种实现方式中，第一设备的设备类型为CPE。当第一设备为第一CPE时，用于创建第一网络实例的信息还包括以下一项或多项：第一CPE的位置信息、第一CPE的网络侧IP地址、第一CPE的租户侧IP地址、第一CPE至所述租户的局域网的路由信息。
在一种实现方式中，第一设备的设备类型为云PE。第二云PE用于连接第二云。当第一设备为第二云PE时，用于创建第一网络实例的信息还包括以下一项或多项：第二云PE的位置信息、第二云的供应商信息、第二云PE连接第二云的IP地址， 第二云PE连接第二云的路由信息、第二云PE连接第二云的接口服务质量信息。
在一种实现方式中，用于创建第二网络实例的信息包括以下一项或多项：第一云PE的位置信息、第一云的供应商信息、第一云PE连接第一云的IP地址，第一云PE连接第一云的路由信息、第一云PE连接第一云的接口服务质量信息。在一种实现方式中，该装置还包括：请求消息处理模块，还用于接收业务部署装置发送的第三请求。第三请求用于调用该装置的第三API来部署第一网络实例和/或第二网络实例。第三请求包括用于部署第一网络实例的信息和/或用于部署第二网络实例的信息。用于部署第一网络实例的信息包括业务实例的标识和第一网络实例的标识。用于部署第二网络实例的信息包括业务实例的标识和第二网络实例的标识。
在一种实现方式中，该装置还包括：请求消息处理模块，还用于接收业务部署装置发送的第四请求，该第四请求用于调用该装置的第四API来获得第一网络实例的部署结果信息和/或第二网络实例的部署结果信息。第一网络实例的部署结果信息包括但不限于：第一网络实例的标识、第一网络实例的部署成功标记、第一网络实例的部署失败标记、第一网络实例的部署失败原因。第二网络实例的部署结果信息包括但不限于：第二网络实例的标识、第二网络实例的部署成功标记、第二网络实例的部署失败标记、第二网络实例的部署失败原因。
在一种实现方式中，该装置还包括：结果信息处理模块，用于向业务部署装置发送第一网络实例的部署结果和/或第二网络实例的部署结果。
在一种实现方式中，该装置还包括：结果信息处理模块，用于向业务部署装置发送业务实例的创建结果信息。业务实例的创建结果信息包括但不限于：业务实例的标识、业务实例的创建成功标记、业务实例的创建失败标记、业务实例的创建失败原因。
在一种实现方式中，该装置还包括：结果信息处理模块，用于接收业务部署装置发送的第五请求，第五请求用于调用控制器的第五API来获得业务实例的创建结果信息。
在一种实现方式中，该装置还包括：结果信息处理模块，用于向业务部署装置发送第一网络实例的创建结果信息和/或第二网络实例的创建结果信息。第一网络实例的创建结果信息包括但不限于：第一网络实例的标识、第一网络实例的创建成功标记、第一网络实例的创建失败标记、第一网络实例的创建失败原因。第二网络实例的创建结果信息包括但不限于：第二网络实例的标识、第二网络实例的创建成功标记、第二网络实例的创建失败标记、第二网络实例的创建失败原因。
在一种实现方式中，该装置还包括：结果信息处理模块，用于接收业务部署装置发送的第六请求，第六请求用于调用控制器的第六API来获得第一网络实例的创建结果信息和/或第二网络实例的创建结果信息。
在一种实现方式中，虚拟云专网用于租户的至少一个站点通过至少一条虚拟专用线路访问第一云。
在一种实现方式中，第一云包括至少一个虚拟私有云VPC。
在一种实现方式中，租户的至少一个站点中的每个站点的类型包括：分支网络或云。
第四方面，本申请实施例提供了一种业务部署的装置。业务是为租户提供虚拟云专网，虚拟云专网用于租户访问第一云。该装置包括：请求消息处理模块，用于向控制器 发送第一请求。该第一请求用于调用控制器的第一应用程序编程接口API来创建业务的业务实例，第一请求包括业务实例的标识。该装置包括：请求消息处理模块，还用于向控制器发送第二请求。该第二请求用于调用控制器的第二API来创建第一网络实例和/或第二网络实例。该第二请求包括用于创建第一网络实例的信息和/或用于创建第二网络实例的信息。用于创建第一网络实例的信息包括业务实例的标识、第一网络实例的标识和第一设备的设备标识。用于创建第二网络实例的信息包括业务实例的标识、第二网络实例的标识和第一云PE的设备标识。其中，第一网络实例和第二网络实例用于部署业务，第一网络实例是第一设备对应的网络实例。第一网络实例包括第一设备的设备标识。第二网络实例是第一云运营商边缘PE对应的网络实例，第二网络实例包括第一云PE的设备标识。第一云PE用于连接第一云。第一设备和第一云PE是虚拟云专网的边缘设备。租户通过第一设备和第一云PE访问云。上述装置通过调用控制器提供的服务化接口进行业务部署，将虚拟云专网业务部署的流程简化为业务实例、第一网络实例和第二网络实例的创建，降低了业务部署的复杂度，提升了业务部署的效率和准确率。
在一种实现方式中，该第一请求还包括以下一项或多项：业务实例的类型、租户的标识、租户的订单信息。
在一种实现方式中，第一设备的设备类型为用户驻地设备CPE。当第一设备为第一CPE时，用于创建第一网络实例的信息还包括以下一项或多项：第一CPE的位置信息、第一CPE的网络侧IP地址、第一CPE的租户侧IP地址、第一CPE至所述租户的局域网的路由信息。
在一种实现方式中，第一设备的设备类型为云PE。第二云PE用于连接第二云。当第一设备为第二云PE时，用于创建第一网络实例的信息还包括以下一项或多项：第二云PE的位置信息、第二云的供应商信息、第二云PE连接第二云的IP地址，第二云PE连接第二云的路由信息、第二云PE连接第二云的接口服务质量信息。
在一种实现方式中，用于创建第二网络实例的信息包括以下一项或多项：第一云PE的位置信息、第一云的供应商信息、第一云PE连接第一云的IP地址，第一云PE连接第一云的路由信息、第一云PE连接第一云的接口服务质量信息。
在一种实现方式中，该装置还包括：请求消息处理模块，还用于向控制器发送第三请求，该第三请求用于调用控制器的第三API来部署第一网络实例和/或第二网络实例。该第三请求包括用于部署第一网络实例的信息和/或用于部署第二网络实例的信息。用于部署第一网络实例的信息包括业务实例的标识和第一网络实例的标识。用于部署第二网络实例的信息包括业务实例的标识和第二网络实例的标识。
在一种实现方式中，该装置还包括：结果信息处理模块，用于接收控制器发送的业务实例的创建结果信息。业务实例的创建结果信息包括但不限于：业务实例的标识、业务实例的创建成功标记、业务实例的创建失败标记、业务实例的创建失败原因。
在一种实现方式中，该装置还包括：结果信息处理模块，还用于输出业务实例的创建结果信息。
在一种实现方式中，该装置还包括：结果信息处理模块，还用于接收控制器发送的 第一网络实例的创建结果信息和/或第二网络实例的创建结果信息。第一网络实例的创建结果信息包括但不限于：第一网络实例的标识、第一网络实例的创建成功标记、第一网络实例的创建失败标记、第一网络实例的创建失败原因。第二网络实例的创建结果信息包括但不限于：第二网络实例的标识、第二网络实例的创建成功标记、第二网络实例的创建失败标记、第二网络实例的创建失败原因。
在一种实现方式中，该装置还包括：结果信息处理模块，还用于输出第一网络实例的创建结果信息和/或第二网络实例的创建结果信息。在一种实现方式中，该装置还包括：结果信息处理模块，还用于接收控制器发送的第一网络实例的部署结果信息和/或第二网络实例的部署结果信息。第一网络实例的部署结果信息包括但不限于：第一网络实例的标识、第一网络实例的部署成功标记、第一网络实例的部署失败标记、第一网络实例的部署失败原因。第二网络实例的部署结果信息包括但不限于：第二网络实例的标识、第二网络实例的部署成功标记、第二网络实例的部署失败标记、第二网络实例的部署失败原因。在一种实现方式中，该装置还包括：结果信息处理模块，还用于输出第一网络实例的部署结果信息和/或第二网络实例的部署结果信息。
在一种实现方式中，业务实例的类型包括：单云或多云，单云是指租户通过第一设备仅可访问一个云，多云是指租户通过第一设备可访问多个云。
在一种实现方式中，虚拟云专网用于租户的至少一个站点通过至少一条虚拟专用线路访问第一云。
在一种实现方式中，第一云包括至少一个虚拟私有云VPC。
在一种实现方式中，租户的至少一个站点中的每个站点的类型包括：分支网络或云。
第五方面，本申请实施例提供了一种业务部署系统，该系统包括控制器和业务部署装置，该控制器实现上述方面的方法中由控制器执行的步骤，该业务部署装置实现上述方面的方法中由业务部署装置执行的步骤。
第六方面，本申请实施例提供了一种通信装置，该通信装置包括存储器和处理器，存储器中包括指令，当处理器执行该指令时，使得该通信装置执行上述方面中的方法中由控制器执行的步骤。
第七方面，本申请实施例提供了一种通信装置，该通信装置包括存储器和处理器，存储器中包括指令，当处理器执行该指令时，使得该通信装置执行上述方面中的方法中由业务部署装置执行的步骤。
第八方面，本申请实施例提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，该指令被处理器执行时，实现上述任一方面所提供的业务的部署方法。
第九方面，本申请实施例提供了一种包含指令的计算机程序产品，当该计算机程序产品被处理器执行时，实现上述任一方面及任一可能的实施方式所提供的业务的部署方法。
附图说明
图1(a)为本申请实施例提供的一种业务的部署方法的网络拓扑和架构图；
图1(b)为本申请实施例提供的一种业务的部署方法的网络拓扑和架构图；
图2(a)为本申请实施例提供的一种业务的部署方法的应用场景示意图；
图2(b)为本申请实施例提供的一种业务的部署方法的应用场景示意图；
图2(c)为本申请实施例提供的一种业务的部署方法的应用场景示意图；
图3为本申请实施例提供的一种业务的部署方法的实施例中的设置连接信息的界面示意图；
图4(a)为本申请实施例提供的一种业务的部署方法400的实施方式流程图；
图4(b)为本申请实施例提供的一种业务的部署方法4050的实施方式流程图；
图4(c)为本申请实施例提供的一种业务的部署方法40550的实施方式流程图；
图5(a)为本申请实施例提供的一种业务的部署方法的实施例中的创建业务实例的界面示意图；
图5(b)为本申请实施例提供的一种业务的部署方法的实施例中的业务实例列表的界面示意图；
图6(a)为本申请实施例提供的一种业务的部署方法的实施例中的创建网络实例的界面示意图；
图6(b)为本申请实施例提供的一种业务的部署方法的实施例中的创建网络实例的界面示意图；
图6(c)为本申请实施例提供的一种业务的部署方法的实施例中的创建网络实例的界面示意图；
图7为本申请实施例提供的一种业务的部署方法700的实施方式流程图；
图8为本申请实施例提供的一种业务部署系统的架构示意图；
图9为本申请实施例提供的一种业务部署装置的架构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。
本申请实施例描述的网络架构以及业务场景是为了通过实例的方式说明本申请的技术方案，并不表示本申请仅适用于以下实施例中。本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
以下对本申请涉及的术语进行解释：
虚拟云专网：虚拟云专网是一种为租户或企业用户访问云的虚拟专用网络。例如，通过虚拟云专网，租户站点中的终端或服务器可以访问云。服务提供商基于在租户站点侧的网络设备到云侧的网络设备间建立一条或多条虚拟专用线路，使得租户站点的终端或服务器能够通过专用线路访问云。相比于租户通过互联网线路访问云，租户通过虚拟云专网访问云会获得更高的安全性和可靠性。
租户站点：租户的一个网络，该网络中的终端或服务器需要通过虚拟云专网访问云。租户站点的类型包括但不限于：分支网络或云。
服务提供商网络：服务提供商网络是服务提供商部署运维的网络，该网络是为租户提供虚拟云专网业务的网络基础设施。服务提供商基于该网络为租户的业务提供从租户 侧到云侧的虚拟专用线路，使得租户站点中的终端或服务器可以通过虚拟云专网访问云。
图1(a)和图1(b)所示的应用场景示意图描述了本实施例中的虚拟云专网的服务提供商的服务提供商系统、租户站点、服务提供商网络和云的网络拓扑和系统架构。如图1(a)和图1(b)所示，服务提供商通过服务提供商系统1000为租户A、租户B和租户C提供虚拟云专网业务。服务提供商向租户提供可访问的云，云包括第一云50、第二云60和第三云70。云的类型包括但不限于公有云、私有云或混合云。租户访问的云可以是一个云，也可以是基于该云通过虚拟化技术虚拟出的一个或多个虚拟私有云VPC(Virtual Private Cloud)。
如图1(a)和图1(b)所示，租户A的租户站点类型是分支网络。租户A的租户站点包括分支网络10。分支网络10中包括终端101。租户B的租户站点类型是分支网络。租户B的租户站点包括分支网络20。分支网络20中包括终端201。租户C的租户站点类型是云。租户C的租户站点包括云80。云80中包括一个虚拟私有云VPC801。
如图1(a)所示，服务提供商网络是一个多域网络，包括网络域A 30和网络域B 40的网络。网络域A包括用户驻地设备CPE(Customer Premises Equipment)301、CPE302、云运营商边缘PE(Provider Edge)303。CPE301是被部署在服务提供商网络中，位于租户A站点侧的网络设备。CPE302是被部署在服务提供商网络中，位于租户B站点侧的网络设备。云PE303是被部署在服务提供商网络中，位于租户C站点侧的网络设备。网络域A还包括服务提供商的其他设备，在此不一一描述。网络域B包括网PE305、网PE306、云PE401、云PE402和云PE403。网PE305和网PE306是被部署在服务提供商网络中，位于网络域A和网络域B的边界设备。云PE401是被部署在服务提供商网络中，位于第一云50侧的设备。云PE402是被部署在服务提供商网络中，位于第二云60侧的设备。云PE403是被部署在服务提供商网络中，位于第三云70侧的设备。网络域B还包括服务提供商的其他设备，在此不一一描述。
如图1(b)所示，服务提供商网络是一个单域网络，包括网络域C 90的网络。网络域C包括CPE301、CPE302、云PE303、云PE401、云PE402和云PE403。CPE301是被部署在服务提供商网络中，位于租户A站点侧的网络设备。CPE302是被部署在服务提供商网络中，位于租户B站点侧的网络设备。云PE303是被部署在服务提供商网络中，位于租户C站点侧的网络设备。云PE401是被部署在服务提供商网络中，位于第一云50侧的设备。云PE402是被部署在服务提供商网络中，位于第二云60侧的设备。云PE403是被部署在服务提供商网络中，位于第三云70侧的设备。网络域C还包括服务提供商的其他设备，在此不一一描述。
租户A的业务需求为：租户A站点(分支网络10)中的终端101仅访问第一云50。
租户B的业务需求为：租户B站点(分支网络20)中的终端201访问第二云60和第三云70。
租户C的业务需求为：租户C站点(云80)中的服务器仅访问第三云70。
服务提供商根据租户的业务需求，将虚拟云专网的业务类型划分为单云或多云。单云是租户通过租户侧的设备仅可以访问一个云。多云是租户通过租户侧的设备可访问多个云。例如，租户A的业务需求是终端101通过CPE301仅访问第一云50，所以租户A 的业务类型是单云；租户C的业务需求是服务器通过云PE303仅访问第三云70，所以租户C的业务类型是单云。又例如，租户B的业务需求是终端通过CPE302可访问第二云60和第三云70，所以租户B的业务类型是多云。
如图1(a)和图1(b)所示，服务提供商系统1000是本申请实施例提供的业务部署系统，服务提供商系统1000包括业务部署装置1100和服务提供商网络对应的控制器1200。业务部署装置1100可以是运维支撑系统OSS(Operations Support System)、业务支撑系统(Business Support System)或网络业务编排器NSO(Network Service Orchestrator)等。如图1(a)所示，控制器1200是一个跨域控制器，用于对网络域A 30和网络域B 40中的网络设备进行管理运维。如图1(b)所示，控制器1200是一个单域控制器，用于对网络域C 90中的网络设备进行管理运维。如图1(a)和图1(b)所示，业务部署装置1100通过调用控制器1200的一个或多个应用程序编程接口API(Application Programming Interface)进行虚拟云专网业务的部署。
服务提供商为了为租户提供满足租户业务需求的虚拟云专网，服务提供商需要为租户提供一条或多条虚拟专用线路，上述虚拟专用线路用于租户站点中的终端或服务器访问云。上述虚拟专用线路是从服务提供商网络中租户侧的网络设备至云侧的网络设备的数据传输隧道。隧道类型包括但不限于二层虚拟私有网络VPN(Virtual Private Network)隧道或三层VPN隧道。如图2(a)所示，服务提供商为租户A提供了一个虚拟云专网A，虚拟云专网A的业务类型为单云。创建了一条从CPE301到云PE401的虚拟专用线路500。基于虚拟专用线路500，对来自租户A站点的终端101的访问第一云50的数据报文的数据转发流程如下：
1.租户A站点中的终端101发送访问第一云50的数据报文，该数据报文被分支网络10中的网络设备转发至CPE301。
2.CPE301接收到该报文后,根据目的IP地址的解析结果，将该数据报文封装入隧道(CPE301到云PE401之间的虚拟专用线路500)。
3.云PE401通过虚拟专用线路500接收到该数据报文，将该数据报文解封装，根据目的IP地址网段的路由信息将该数据报文转发到第一云50。
通过上述对数据报文的处理流程，租户A站点的终端101可以实现对第一云50的访问。如图2(b)所示，根据租户B的业务需求，服务提供商为租户B提供了一个虚拟云专网B，创建了两条虚拟专用线路，包括一条从CPE302到云PE402的虚拟专用线路501和一条从CPE302到云PE403的虚拟专用线路502。如图2(c)所示，根据租户C的业务需求，服务提供商为租户提供了一个虚拟云专网C，创建了一条从云PE303到云PE403的虚拟专用线路503。
如果服务提供商按照现有的业务部署上述租户业务，具体的业务部署流程如下：
1.服务提供商的网络运维人员收到租户的业务需求，需要到先确定租户站点侧部署的网络设备的设备信息以及租户购买的云服务对应的云PE的设备信息。
2.到上述设备对应的网络管理系统上查看对应的设备资源，如设备的接口信息，设备已有配置等。
3.网络运维人员需要查看从租户站点侧的设备到云侧的云PE间的服务提供商网 络的网络设备的资源信息，查看的目的是为了规划一条从租户站点侧设备到云PE的一条虚拟专用线路。
4.根据规划信息通过命令行、网络管理系统的配置界面或调用网络管理系统的API接口，为规划的虚拟专用线路经过的相关网络设备配置虚拟专用线路对应的隧道配置信息、VPN实例配置信息以及路由信息等。
通过上述流程描述可知，网络运维人员需要根据每个租户的业务需求规划虚拟专用线路，查询、识别和分配网络存量资源，然后再将配置信息设置到相关的网络设备上，业务部署的流程复杂，工作量较大，导致业务无法快速部署，导致租户业务上线速度缓慢。
本申请的实施例提供了一种业务的部署方法、装置及系统，通过创建与业务对应的业务实例，并在业务实例中创建对应的网络实例，简化了业务部署的流程，降低业务部署的复杂度，提升业务部署的效率和准确率。
图4(a)示出了本申请提供的一种业务部署的方法400的流程示意图，应用方法400的网络架构包括控制器，业务部署装置，第一设备以及第一云PE。其中，应用方法400的网络架构例如可以是图1(a)或图1(b)所示的网络架构。此时，控制器例如可以是图1(a)或图1(b)所示的控制器1200，业务部署装置例如可以是图1(a)或图1(b)所示的业务部署装置1100，第一设备例如可以是图1(a)或图1(b)所示的CPE301或CPE302，第一设备例如还可以是图1(a)或图1(b)所示的云PE303,第一云PE例如是图1(a)或图1(b)所示的云PE401、云PE402或云PE403。方法400由所述控制器执行，具体包括：
S401：创建与业务对应的业务实例。
控制器创建与业务对应的业务实例。在一些实施例中，当服务提供商接收到租户的虚拟云专网的业务需求，网络运维人员在控制器上根据业务需求创业务实例。业务实例包括业务实例的标识。业务实例的标识包括但不限于业务实例的名称、业务实例的标识符ID(Identifier)等。业务实例还标识虚拟云专网的业务类型。业务实例还可以包括业务实例的类型。业务实例的类型指示了业务类型，如单云、多云等。如图2(a)所示，如果要为虚拟云专网A创建对应的业务实例，该业务实例的类型为单云。如图2(b)所示，如果要为虚拟云专网B创建对应的业务实例，该业务实例的类型为多云。业务实例还可以包括租户信息，租户信息包括但不限于租户的标识或租户的订单信息。业务实例还可以包括已创建的网络实例的信息。已创建的网络实例的信息包括但不限于网络实例的数量、网络实例的类型、网络实例的标识。网络实例是虚拟云专网边缘设备对应的实例。如图2(a)所示，虚拟云专网A对应的业务实例中的网络实例包括但不限于CPE301对应的网络实例、云PE401对应的网络实例。已创建的网络实例的数量描述了业务实例中已经创建的网络实例的个数。网络实例的类型标识了网络实例对应的网络设备的类型。根据图2(a)-图2(c)所示，虚拟云专网边缘设备的设备类型包括但不限于CPE或云PE。创建业务实例的目的是为了记录待部署的业务并为此业务提供资源信息。具体的说，在控制器上进行业务部署时，需要在控制器中描述和记录业务信息，并且需要根据业务信息为业务部署提供资源信息。例如业务对应的网络设备的存量信息、业务对应的配置信息等。虚拟云专线业务的部署过程是创建一条从租户站点侧到云侧的数据传输路径，该数 据传输路径包括在服务提供商网络中租户站点侧至云侧的设备之间创建数据传输隧道。业务实例记录了业务类型信息、虚拟云专网的边界节点的信息、还记录了业务对应的租户信息。通过业务实例将虚拟云专网业务和边缘设备进行了关联。另外通过业务实例，将业务和租户关联起来。服务提供商可以根据租户信息查找相关业务，方便后续对业务的查询。在一些实施例中，业务实例是与需要为租户部署的业务一一对应的。例如，服务提供商为租户A提供虚拟云专网A的业务，则服务提供商需要在服务提供商系统1000中创建虚拟云专网A的业务对应的业务实例2000。
作为一种示例，如图5(a)中所示的业务实例创建页面，“业务实例标识”对应的输入框用于获取业务实例的名称或业务实例的ID，如“虚拟云专网A”；“业务实例类型”对应的输入框用于获取业务类型，如“单云”；“租户名称”对应的输入框用于获取购买业务的租户的名称或租户ID，如“租户A”；“订单信息”对应的输入框用于获取上述租户的业务订单信息，如订单标识，如订单号“123456”。
S403：在所述业务实例中创建第一网络实例和第二网络实例，所述第一网络实例和所述第二网络实例用于部署所述业务，其中，所述第一网络实例是第一设备对应的网络实例，所述第一网络实例包括所述第一设备的设备标识，所述第二网络实例是第一云运营商边缘PE对应的网络实例，所述第二网络实例包括所述第一云PE的设备标识，所述第一云PE用于连接所述第一云。
控制器在业务实例中创建第一网络实例和第二网络实例。第一网络实例和第二网络实例用于部署业务。第一网络实例时第一设备对应的网络实例。第二网络实例是第一云PE对应的网络实例。第一设备和第一云PE是虚拟云专网的边缘设备。第一设备是连接租户站点与服务提供商网络的边界设备。租户站点通过第一设备接入虚拟云专网的虚拟专用线路。第一云PE是服务提供商网络中连接云侧的设备。租户通过第一设备和第一云PE访问云。第一设备是在服务提供商网络中租户站点侧设备，第一网络实例是第一设备对应的网络实例，第一云PE是连接云侧的网络设备，第二设网络实例是第一云运营商边缘PE(Provider Edge)对应的网络实例。第一网络实例包括第一设备的设备标识。第二网络实例包括第一云PE的设备标识。例如，虚拟云专网A的业务涉及租户A站点和第一云50，虚拟云专网A的业务对应的业务实例2000。第一设备为图2(a)中的CPE301，第一网络实例是CPE301对应的网络实例。第一云PE为云PE401，第二网络实例为云PE401对应的网络实例。控制器1200在业务实例2000中创建第一网络实例和第二网络实例。在另一些实施例中，虚拟云专网C的业务对应的业务实例3000。则第一设备为图2(c)中的云PE 403，第一网络实例为云PE 403对应的网络实例。第一云PE为云PE402，第二网络实例为云PE402对应的网络实例。控制器1200在业务实例3000中创建第一网络实例和第二网络实例。
第一网络实例包括第一设备的设备标识，第二网络实例包括第一云PE的设备标识。设备标识包括但不限于设备的名称、设备的设备序列号ESN(Equipment Serial Number)、设备的ID或设备的媒体接入控制MAC地址等用于标识设备的标识信息。
根据图2(a)-图2(c)所示，虚拟云专网边缘设备的设备类型包括但不限于CPE或云PE。在一些实施例中，第一网络实例对应的第一设备的设备类型为CPE，即租户站点的 类型是分支网络。以图2(a)中租户A的虚拟云专网A的业务为例，虚拟云专网A的业务类型为单云。控制器为虚拟云专网A创建业务实例2000。如图1(a)或图1(b)所示，租户A通过CPE301仅访问第一云50。第一网络实例是CPE301对应的网络实例。第一网络实例还包括第一网络实例的名称、CPE301的位置信息、CPE301的网络侧IP地址、CPE301的租户侧IP地址、CPE301至所述租户A的分支网络10局域网的路由信息。CPE301的网络侧IP地址是CPE301连接租户A站点分支网络10的接口的IP地址。CPE301的租户侧IP地址是CPE301连接的租户A站点的网络设备接口的IP地址。CPE301至所述租户A的分支网络10的路由信息是用于将从第一云50发送的访问响应数据报文从CPE301转发至租户A站点的局域网。该路由信息包括但不限于目的网段和下一跳信息。
作为一种示例，图6(a)为创建CPE301对应的第一网络实例的界面。界面上“网络实例名称”对应的输入框用于获取CPE301对应的网络实例的名称；“位置信息”对应的输入框用于获取CPE301的位置信息，如“城市A”；“设备标识”对应的输入框用于获取CPE301的设备标识信息，如ESN为“111222333”；“网络侧IP地址”对应的输入框用于获取CPE301连接租户站点的接口的IP地址“10.10.10.10/20”；“租户侧IP地址”对应的输入框用于获取CPE301连接的租户站点的网络设备的IP地址“10.1.1.1/20”；“路由信息”对应的输入框用于获取CPE301到租户站点的局域网的路由信息。
第二网络实例是云PE401对应的网络实例。云PE401用于连接租户A要访问的第一云50。那么第二网络实例还包括第二网络实例的名称、云PE401的位置信息、云PE401的供应商信息、云PE401连接第一云50的IP地址，云PE401连接第一云50的接口标识、云PE401连接第一云50的虚拟局域网VLAN(Virtual Local Area Network)标识、云PE401连接第一云50的路由信息、云PE401连接第一云50的接口服务质量信息。云PE401的供应商信息包括云PE401连接的第一云50对应的供应商信息。云PE401连接第一云50的IP地址是云PE401连接第一云50的接口的IP地址。云PE401连接第一云50的路由信息是用于数据从云PE401转发至第一云50的路由信息，包括目的网段和下一跳信息。云PE401连接第一云50的接口服务质量信息是用于设置云PE401连接第一云50的接口的服务质量QoS(Quality of Service)信息，服务质量信息包括但不限于带宽、时延、抖动等信息。
作为一种示例，图6(c)为创建云PE401对应的第二网络实例的界面。界面上“网络实例名称”对应的输入框用于获取云PE401对应的网络实例的名称；“位置信息”对应的输入框用于获取云PE401的位置信息，如“城市A。云PE401的设备标识可以人工输入，还可以根据控制器1200上设置的云PE的连接信息，通过云PE401的位置信息可以关联到云PE401的设备标识。“供应商信息”对应的输入框用于获取云PE401连接的第一云50的供应商名称。“云PE连接云的IP地址”对应的输入框用于获取云PE401连接第一云50的接口的IP地址“10.1.2.20/20”；“VLAN”对应的输入框用于获取云云PE401连接第一云50的接口设置的VLAN标识。“接口服务质量信息”对应的输入框用于获取云PE401连接第一云50的接口设置的QoS信息。“路由信息”对应的输入框用于获取云PE401到第一云50的路由信息。
控制器设置云PE的连接信息的流程如下：
服务提供商在为租户提供虚拟云专网A、虚拟云专网B和虚拟云专网C的业务之前，在控制器创建一个有能够连接租户站点A、租户站点B和租户站点C与第一云50和第二云60的网络，即图1(a)或图1(b)所示的服务提供商网络。上述服务提供商网络中部署一个或多个云PE用于连接服务提供商可提供云服务的一个或多个云，例如，部署的云PE401用于连接第一云50；部署的云PE 402用于连接第二云60；部署的云PE 403用于连接第三云70。在一些实施例中，为了管理服务提供商网络中云侧的云PE和云的对应关系，服务提供商系统中设置云PE的连接信息。
在一些实施例中，上述连接信息可以设置在控制器1200中，在另外一些实施例中，上述连接信息可以设置在业务部署装置1100中。需要设置的连接信息包括：云PE的设备标识，云PE的位置信息，云PE的接口的标识，云PE的VLAN的标识。其中，云PE的设备标识包括云PE的设备名称或设备标识符ID等。云PE的位置信息是指上述云PE连接的云的位置的名称或标识，例如使用区域位置的名称作为位置信息，例如城市A，又例如使用云对应的位置标识作为位置信息，例如区域B，又例如使用能与云的位置对应的服务提供商的标识，如厂商C-001。云PE的接口是指连接云所使用的物理接口，例如物理接口Gigabit Ethernet1/0/31。云PE的VLAN标识了需要在上述接口配置上述VLAN,使得上述云PE通过上述VLAN连接对应的云。
作为一种示例，图3呈现了实施例中设置连接第一云50的云PE 401的连接信息的连接信息设置界面。具体的，“设备名称”对应的输入框用于输入云PE的设备标识，如图3中的云PE 401；“区域信息”对应的输入框用于云PE的位置信息，如图3中的城市A；“接口信息”对应的输入框用于输入云PE的接口标识，如图3中的GE3/0/1；“VLAN”对应的输入框用于输入云PE的VLAN标识，如图3中的100。设置完上述可连接信息后，服务提供商系统1000存储记录了在服务提供商网络中连接第一云50的云PE 401的连接信息。通过上述连接信息，可以通过云PE的位置信息匹配到云PE的设备标识及其他连接信息。所以网络运维人员在创建第二网络实例的过程中，在创建的界面上不需要录入第一云PE的设备标识，可以通过第一云PE的位置信息关联出第一云PE的设备标识。
经过上述流程，控制器1200在业务实例2000中创建第一网络实例和第二网络实例。控制器通过创建第一网络实例和第二网络实例，控制器确定了虚拟云专网的边缘设备的信息，如设备标识，设备的位置信息、路由信息等。
作为一种示例，控制器在业务示例中创建了网络示例，如图5(b)所示的业务实例列表页面。页面中包括“虚拟云专网A”和“虚拟云专网B”这两个业务实例的信息。“虚拟云专网A”的“业务实例类型”为“单云”，“订单信息”为“123456”，“网络实例数量”为“虚拟云专网A”的业务实例中已创建的网络实例数量为“2”。
在一些实施例中，如图2(b)所示，租户B的虚拟云专网B，虚拟云专网B的业务类型为多云。控制器创建虚拟云专网B的业务对应的业务实例2001。在业务实例2001中创建CPE302对应的第一网络实例、云PE401对应的第二网络实例和云PE402对应的第三网络实例。第一网络实例是CPE302对应的网络实例。第一网络实例还包括第一网络 实例的名称、CPE302的位置信息、CPE3012的网络侧IP地址、CPE302的租户侧IP地址、CPE302至所述租户B的分支网络20局域网的路由信息。CPE302的网络侧IP地址是CPE302连接租户B站点分支网络20的接口的IP地址。CPE302的租户侧IP地址是CPE302连接的租户B站点的网络设备接口的IP地址。CPE302至所述租户B的分支网络20局域网的路由信息是用于数据从CPE302转发至租户B站点的局域网的路由信息，包括目的网段和下一跳信息。
第二网络实例是云PE401对应的网络实例，第二网络实例还包括第二网络实例的名称、云PE401的位置信息、云PE401的供应商信息、云PE401连接第一云50的IP地址，云PE401连接第一云50的接口标识、云PE401连接第一云50的VLAN标识、云PE401连接第一云50的路由信息、云PE401连接第一云50的接口服务质量信息。第三网络实例是云PE402对应的网络实例，第三网络实例包括云PE402的设备标识、第三网络实例的名称、云PE402的位置信息、云PE402的供应商信息、云PE402连接第二云60的IP地址，云PE402连接第二云60的接口标识、云PE402连接第二云60的VLAN标识、云PE402连接第一云60的路由信息、云PE402连接第二云60的接口服务质量信息。
经过在业务实例2001中创建第一网络实例、第二网络实例和第三网络实例。如图5(b)所示的业务实例列表页面，页面中“虚拟云专网B”的“业务实例类型”为“多云”，“订单信息”为“212345”，“网络实例数量”为“虚拟云专网B”的业务实例中已创建的网络实例数量为“3”。
在一些实施例中，第一网络实例对应的第一设备的类型是云PE，即租户站点的类型是云。如图2(c)中的租户C的虚拟云专网C。控制器创建虚拟云专网C的业务对应的业务实例2002。控制器在业务实例2002中创建第一网络实例和第二网络实例。第一网络实例对应的第一设备是云PE303，云PE303用于连接租户C站点对应的云80。第一网络实例还包括第一网络实例的名称、云PE303的位置信息、云PE303的供应商信息、云PE303连接云80的IP地址，云PE303连接云80的接口标识、云PE303连接云80的VLAN标识、云PE303连接云80的路由信息、云PE303连接云80的接口服务质量信息。云PE303的供应商信息包括云PE303连接的云80对应的供应商信息。云PE303连接云80的IP地址是云PE303连接云80的接口的IP地址。云PE303连接云80的路由信息用于将从第三云70发送的响应数据从云PE303转发至租户C站点云80的路由信息，包括目的网段和下一跳信息。云PE303连接云80的接口服务质量信息是用于设置云PE303连接云80的接口的服务质量QoS信息，包括但不限于带宽、时延、抖动等信息。图6(b)为创建云PE303对应的第一网络实例的界面。界面上“网络实例名称”对应的输入框用于获取云PE403对应的网络实例的名称。“位置信息”对应的输入框用于获取云PE403的位置信息，如“城市B”。设备标识可以通过输入框中输入获取。还可以根据之前在控制器1200上设置的云PE的连接信息，通过云PE303的位置信息关联出云PE303的设备标识。“供应商信息”对应的输入框用于获取云PE303连接的云80的供应商名称。“云PE连接云的IP地址”对应的输入框用于获取云PE303连接云80的接口的IP地址“10.1.1.10/20”。“VLAN”对应的输入框用于获取云PE303连接云80 的接口设置的VLAN标识。“接口服务质量信息”对应的输入框用于获取云PE303连接云80的接口设置的QoS信息。“路由信息”对应的输入框用于获取云PE303到云80的路由信息。对于虚拟云专网C的业务对应的业务实例2002中的第二网络实例，第二网络实例对应的网络设备是云PE403。经过在业务实例2002中创建第一网络实例和第二网络实例，控制器1200中已创建了业务实例2002对应的业务在服务提供商网络中租户侧的第一设备和连接云侧的第一云PE的设备标识、位置信息、IP地址、路由信息等用于业务部署的信息。
经过在业务实例2002中创建第一网络实例和第二网络实例。如图5(b)所示的业务实例列表页面，页面中包括“虚拟云专网C”的业务实例的信息。“虚拟云专网C”的“业务实例类型”为“单云”，“订单信息”为“311222”，“网络实例数量”为“虚拟云专网C”的业务实例中已创建的网络实例数量为“2”。通过控制器创建与虚拟云专网业务对应的业务实例，并在业务实例中创建对应的第一网络实例和第二网络实例，使得业务部署的流程得到简化，降低业务部署的复杂度，提升业务部署的效率和准确率。
S405：部署所述第一网络实例和所述第二网络实例。
可选的，控制器部署第一网络实例和第二网络实例。通过S401所描述的步骤和S405所描述的步骤，控制器已经创建了的业务对应的业务实例，以及第一网络实例和第二网络实例。控制器上已经确定了待部署的业务对应的虚拟云专网的边缘设备、业务类型。网络运维人员需要根据业务类型，对已经确定的第一设备和第一云PE设置隧道配置信息、VPN实例配置信息和路由信息。对第一设备和第一云PE的设置配置信息的方法包括但不限于：
1.通过控制器上的隧道配置界面，向第一设备和第一云PE配置具体参数。通过控制器的VPN实例配置界面，向第一设备和第一云PE配置具体参数。通过控制器的路由配置界面，向第一设备和第一云PE配置具体参数。
2.通过控制器获得第一设备或第一云PE的管理IP地址。通过第一设备或第一云PE的管理IP地址及远程登陆的协议或工具，登录到上述设备的命令行界面对隧道配置信息、VPN实例配置信息和路由信息进行配置。
3.控制器向第一设备发送用于配置业务的第一配置信息，控制器向第一云PE发送用于配置业务的第二配置信息。
根据所述第一网络实例、所述第二网络实例确定所述第一配置信息和所述第二配置信息的方法4050,具体参见如图4(b)所示的步骤：
S4051：根据所述第一网络实例、所述第二网络实例获取第一设备的设备信息和第一云PE的设备信息。
第一设备和第一云PE是虚拟云专网的边缘设备。租户通过第一设备和第一云PE访问云。当租户站点类型是分支网络时，第一设备的类型为CPE。服务提供商向租户提供第一设备，租户会将第一设备部署在租户站点侧。当租户站点类型是云时，第一设备的类型为云PE。服务提供商会为租户在服务提供商网络中部署上述云PE。
第一网络实例包括了第一设备的设备标识等信息，第二网络实例包括第一云PE的设备标识等信息。控制器根据第一网络实例和第二网络实例可以确定第一设备的设备信 息和第一云PE的设备信息，即确定并获取了虚拟专用线路的端点设备的设备信息。控制器可以根据第一网络实例中的第一设备的标识，在控制器中查询到第一设备的设备信息。第一设备的设备信息包括但不限于第一设备的标识、第一设备的管理IP地址、第一设备的位置信息、第一设备的路由信息、第一设备的网络资源信息。第一设备的网络资源信息包括不限于第一设备的端口信息、第一设备的内存占用率信息、第一设备的CPU使用率信息、第一设备的已生效的配置信息。第一云PE信息包括但不限于第一云PE的标识、第一云PE的管理IP地址、第一云PE的位置信息、第一云PE连接云的信息、第一云PE的路由信息、第一云PE的网络资源信息。第一云PE的网络资源信息包括不限于第一云PE的端口信息、第一云PE的内存占用率信息、第一云PE的CPU使用率信息、第一云PE的已生效的配置信息。
如图2(a)所示，租户A的虚拟云专网A的业务，即在租户A的租户站点用户网络10中的终端通过虚拟专用线路500访问第一云。虚拟云专网A的业务类型为单云，即租户A仅可访问一个云。根据S403中描述的步骤，控制器1200已经创建了CPE301对应的第一网络实例和云PE401对应的第二网络实例。控制器1200根据第一网络实例和第二网络实例获取CPE301的设备信息和云PE401的设备信息。
S4053：根据第一设备的设备信息和第一云PE的设备信息获取网络资源信息。
控制器根据S4051中描述的步骤获取了第一设备的设备信息和第一云PE的设备信息。控制器可以根据服务提供商网络的网络拓扑信息确定虚拟专用线路经过的网络集合或网络域集合。控制器获取网络资源信息的目的是获取虚拟专用线路经过的网络或网络域的资源信息。
如图1(a)所示，控制器1200根据第一网络实例和第二网络实例获取CPE301的设备信息和云PE401的设备信息后，CPE301和云PE401之间经过网络域A和网络域B，网络域集合为(网络域A，网络域B)。控制器1200获取上述网络域集合内的每一个网络域的网络资源信息。上述网络资源信息包括但不限于网络域的网络拓扑信息，网络域中的各个网元的设备信息和网元设备之间存在的网络连接信息等等。上述设备信息包括但不限于网元设备名称、网元设备类型、网元设备的ESN、网元设备的管理IP地址、网元设备的网络位置等等。上述网络连接信息包括但不限于物理链路和逻辑链路。逻辑链路类型包括但不限于二层VPN隧道、三层VPN隧道。控制器1200获取网络域A的网络资源信息，网络资源信息包括但不限于：1、网络域A的网络拓扑信息；2、网络域A中的每一个网元设备信息，网元设备信息包括网元设备的ESN序列号，网元设备类型，设备型号，版本信息，管理IP地址，MAC地址等；3、每一个网元设备的端口信息，包括物理端口和逻辑端口信息；4、网元间的链路信息，包括物理链路信息，隧道信息，VPN信息等。
S4055：获取的第一配置信息和第二配置信息。
控制器根据S4051和S4053中描述的步骤获取的第一设备的设备信息、第一云PE的设备信息以及网络资源信息。控制器基于上述信息获取第一配置信息和第二配置信息。第一配置信息是第一设备对应的配置信息。第一配置信息包括第一设备为实现业务需要被配置的隧道配置信息、VPN实例配置信息和路由信息。第二配置信息是第一云PE对 应的配置信息。第二配置信息包括第一云PE为实现业务需要被配置的隧道配置信息、VPN实例配置信息和路由信息。具体的获取步骤如图4(c)所示的方法40550：
S40551：获取第一配置信息中的隧道配置信息和第二配置信息中的隧道配置信息。
控制器获取第一配置信息中的隧道配置信息和第二配置信息中的隧道配置信息。第一配置信息中的隧道配置信息和第二配置信息中的隧道配置信息用于配置从第一设备到第一云PE之间的数据传输隧道。第一配置信息中的隧道配置信息是第一设备上需要被配置的隧道配置信息。第二配置信息中的隧道配置信息是第一云PE上需要被配置的隧道配置信息。
在一些实施例中，服务提供商可以根据服务规划，将单云的业务中的虚拟专用线路定义为一条三层VPN隧道。例如，租户A的虚拟云专网A中的虚拟专用线路500是一条三层VPN隧道。控制器1200通过已获取的网络域A和网络域B的网络资源信息得到网络域A和网络域B的网络拓扑信息等网络资源信息。控制器1200根据上述网络资源信息分析现有的网络资源信息是否满足建立一条从CPE301到云PE401建立一条三层VPN隧道。如果分析结果是网络资源可以满足生成一条从CPE301到云PE401的一条三层VPN隧道，控制器1200提供配置界面，网络人员根据配置界面规划需要在CPE301和云PE401上配置的三层VPN隧道配置信息。
在另一些实施例中，控制器1200根据单云的业务实例对应的业务模板，获取CPE301和云PE401的隧道配置信息。上述业务模板是在部署业务实例之前被设置的。在部署业务实例之前，控制器根据业务实例对应的业务类型设置业务模板。业务模板指示业务的配置信息。业务的配置信息包括但不限于隧道配置信息、VPN实例配置信息或路由信息。业务模板包括但不限于隧道配置信息、VPN实例配置信息或路由信息。当创建业务实例时，通过业务的类型关联对应的业务模板。控制器在业务实例中创建第一网络实例和第二网络实例时，因为业务实例已经和业务模板生成了关联关系，则第一网络实例和第二网络实例也和业务模板生成了关联关系。业务模板中包括但不限于隧道子业务模板、VPN实例子业务模板和路由子业务模板。所以根据第一网络实例、第二网络实例和各个子业务模板可以确定第一配置信息和第二配置信息。控制器将隧道子业务模板中的配置信息，按照第一设备和第一云PE的维度，拆分给第一设备和第一云PE，生成第一配置信息中的隧道配置信息和第二配置信息中的隧道配置信息。
这样就获取到第一设备对应的第一配置信息中的隧道配置信息，第一云PE对应的第二配置信息中的隧道配置信息。如果分析结果无法满足建立一条端到端的隧道来承载三层VPN链路，那么可以提示管理人员重新选择云PE或者进行设备扩容等操作后，然后再获取隧道配置信息。S40553：获取第一配置信息中的VPN实例配置信息和第二配置信息中的VPN实例配置信息。
控制器获取第一配置信息中的VPN实例配置信息和第二配置信息中的VPN实例配置信息。第一配置信息中的VPN实例配置信息和第二配置信息中的VPN实例配置信息用于配置从第一设备和第一云PE的VPN实例。第一配置信息中的VPN实例配置信息是第一设备上需要被配置的VPN实例配置信息。第二配置信息中的VPN实例配置信息是第一云PE上需要被配置的VPN实例配置信息。在一些实施例中，租户A的虚拟云 专网A的虚拟专用线路类型是三层VPN，需要获取CPE301和云PE401的虚拟专用网络由转发VRF(VPN Routing and Forwarding)的配置信息；在另一些实施例中，租户A的虚拟云专网A的虚拟专用线路类型是二层VPN，那么需要获取CPE301和云PE401的以太网私有虚拟网络EVPN(Ethernet Virtual Private Network)实例EVI(EVPN Instance)或者虚拟交换实例VSI(Virtual Switch Instance)的配置信息。控制器1200可以提供配置界面，网络人员根据配置界面规划需要在CPE301和云PE401配置的VPN实例配置信息。
在一些实例中，控制器1200根据单云的业务实例对应的业务模板，获取CPE301和云PE401的VPN配置信息。上述业务模板是在部署业务实例之前被设置的。在部署业务实例之前，控制器根据业务实例对应的业务类型设置业务模板。业务模板指示业务的配置信息。业务的配置信息包括但不限于隧道配置信息、VPN实例配置信息或路由信息。业务模板包括但不限于隧道配置信息、VPN实例配置信息或路由信息。当创建业务实例时，通过业务的类型关联对应的业务模板。控制器在业务实例中创建第一网络实例和第二网络实例时，因为业务实例已经和业务模板生成了关联关系，则第一网络实例和第二网络实例也和业务模板生成了关联关系。业务模板中包括但不限于隧道子业务模板、VPN实例子业务模板和路由子业务模板。所以根据第一网络实例、第二网络实例和各个子业务模板可以确定第一配置信息和第二配置信息。控制器将VPN实例子业务模板中的配置信息，按照第一设备和第一云PE的维度，拆分给第一设备和第一云PE，生成第一配置信息中的VPN实例配置信息和第二配置信息中的VPN实例配置信息。
S40555：获取第一配置信息中的路由配置信息和第二配置信息中的路由配置信息。
控制器获取第一配置信息中的路由配置信息和第二配置信息中的路由配置信息。第一配置信息中的路由配置信息和第二配置信息中的路由配置信息用于配置第一设备和第一云PE的路由信息。第一设备的路由信息用于第一设备至租户站点侧的数据转发路由。第一云PE的路由信息用于第一云PE至云侧的数据转发路由。第一配置信息中的路由配置信息是第一设备上需要被配置的路由配置信息。第二配置信息中的路由配置信息是第一云PE上需要被配置的路由配置信息。
第一配置信息中的路由配置信息用于使得第一设备将来自云侧的响应数据报文转发给租户站点。例如，CPE301根据路由配置信息，将来自第一云50目的为租户站点终端101的数据报文转发给租户A站点分支网络10。第二配置信息中的路由配置信息用于云PE将来自租户站点侧的访问云的数据报文可转发到云上。例如，来自租户A站点访问第一云50的数据报文在云PE401根据路由配置信息转发到第一云50。控制器1200提供配置界面，网络人员根据界面规划需要在CPE301和云PE401上配置的路由配置信息。
在一些实施例中，控制器1200根据单云的业务实例对应的业务模板，获取CPE301和云PE401的路由配置信息。上述业务模板是在部署业务实例之前被设置的。在部署业务实例之前，控制器根据业务实例对应的业务类型设置业务模板。业务模板指示业务的配置信息。业务的配置信息包括但不限于隧道配置信息、VPN实例配置信息或路由信息。业务模板包括但不限于隧道配置信息、VPN实例配置信息或路由信息。当创建业务实例 时，通过业务的类型关联对应的业务模板。控制器在业务实例中创建第一网络实例和第二网络实例时，因为业务实例已经和业务模板生成了关联关系，则第一网络实例和第二网络实例也和业务模板生成了关联关系。业务模板中包括但不限于隧道子业务模板、VPN实例子业务模板和路由子业务模板。所以根据第一网络实例、第二网络实例和各个子业务模板可以确定第一配置信息和第二配置信息。控制器将路由子业务模板中的配置信息，按照第一设备和第一云PE的维度，拆分给第一设备和第一云PE，生成第一配置信息中的路由配置信息和第二配置信息中的路由配置信息。
通过执行S40551至S40555描述的步骤，控制器1200获取到第一配置信息和第二配置信息。
S4057：向第一设备发送第一配置信息，向第一云PE发送第二配置信息。
控制器向第一设备发送第一配置信息，控制器向第一云PE发送第二配置信息。
第一设备或第一云PE的状态包括被控制器纳管或未被控制器纳管。当设备处于被控制器纳管的状态的情况下，控制器可以对设备进行配置管理或设备状态查询等管理运维操作。当设备处于未被控制器纳管的状态的情况下，控制器无法获取设备的信息，也就无法对设备的配置进行管理。
在一些实施例中，当控制器查询第一设备和第一云PE均已经处于被纳管的状态，即控制器可以向第一设备和第一云PE发送配置信息，则在控制器接收到部署网络实例的消息后，控制器向第一设备发送第一配置信息，控制器向第一云PE发送第二配置信息。控制器送上述配置信息的方式可以通过简单网络管理协议SNMP(Simple Network Management Protocol)、电信网络协议Telnet(Telecommunication Network Protocol)、网络配置协议Netconf(Network Configuration Protocol)或基于用户数据报协议UDP(User Datagram Protocol)/传输控制协议TCP(Transmission Control Protocol)的私有配置协议等。当第一设备和第一云PE接收并生效了第一配置信息和第二配置信息。如图1(a)或图1(b)所示，租户A站点侧的CPE301和第一云50侧的云PE401生效了第一配置信息和第二配置信息，那么在CPE301和云PE401之间建立了一条虚拟专用线路500，用于连接租户A站点分支网络10和第一云50。
需要说明的是，当第一设备或第一云PE的状态处于未被控制器纳管状态时，第一设备或第一云PE不可以由控制器管理运维，也无法接收并生效第一配置信息或第二配置信息。控制器预存上述配置信息，等待第一设备或第一云PE完成纳管上线流程后，控制器向第一设备或第一云PE发送第一配置信息或第二配置信息，完成第一网络实例或第二网络实例部署。
通过控制器根据第一网络实例、第二网络实例和预置信息自动获取第一设备对应的第一配置信息和第一云PE对应的第二配置信息，通过控制器下发第一配置信息和第二配置信息的方法，降低了人工配置的复杂度，提高了业务部署的效率。
图7为本申请中的一种业务部署的方法700的流程示意图。上述方法是由图2中的业务部署装置1100和控制器1200执行的，具体的方法包括：
S701：业务部署装置向控制器发送第一请求，所述第一请求用于调用所述控制器的第一应用程序编程接口API来创建所述业务的业务实例，所述第一请求包括所述业务实 例的标识。
业务部署装置向控制器发送第一请求。第一请求用于调用控制器的第一API来创建所述业务的业务实例。第一请求包括所述业务实例的标识。
在一些实施例中，服务提供商使用如图1(a)所示的业务部署装置1100进行虚拟云专网业务部署，控制器1200提供业务部署装置的API供业务部署装置1100来调用来完成业务部署。控制器1200向第三方系统提供了业务实例创建API。业务部署装置1100向控制器1200发送第一请求，上述第一请求用于调用控制器1200的第一API，例如业务实例创建API，来创建业务的业务实例。上述第一请求包括业务实例的标识，业务实例的标识包括业务实例的名称或业务实例的ID等可标识业务实例的信息。上述第一请求还包括上述业务实例的类型、租户的标识、租户的订单信息等。业务实例的类型包括单云、多云等。租户的标识包括租户的名称、租户ID等。租户的订单信息包括订单号、订单名称等。
S703：控制器接收业务部署装置发送的第一请求。
控制器接收业务部署装置发送的第一请求。第一请求用于调用控制器的第一API来创建所述业务的业务实例。
在一些实例中，如图1(a)所示的控制器1200接收业务部署装置1100发送的第一请求。
S705：控制器创建所述业务实例。
控制器基于第一请求中的业务实例的标识，创建所述业务实例。
在一些实例中，如图1(a)所示的控制器1200接收到上述第一请求后，根据第一请求中的业务实例的标识，创建对应的业务实例。控制器1200创建业务实例的具体流程可参考S401的相关描述，在此不再赘述。
S707：控制器向业务部署装置发送所述业务实例的创建结果信息。
控制器向业务部署装置发送业务实例的创建结果信息。
在一些实例中，如图1(a)所示的控制器1200在创建一个业务实例后，向业务部署装置1100发送上述业务实例的创建结果信息。业务实例的创建结果信息包括但不限于：业务实例的标识、业务实例的创建成功标记、业务实例的创建失败标记、业务实例的创建失败原因。
可选的，在一些实施例中，如图1(a)所示的控制器1200在完成创建上述业务实例后，向业务部署装置1100发送业务实例创建的结果信息。
可选的，在另一些实施例中，如图1(a)所示的业务部署装置1100向控制器1200发送业务实例创建查询请求，上述查询请求用于查询控制器1200业务实例创建的结果信息。控制器1200接收上述查询请求后，向业务部署装置1100发送业务实例的创建结果信息。
S709：业务部署装置接收所述控制器发送的所述业务实例的创建结果信息。
业务部署装置接收控制器发送的业务实例的创建结果信息。
可选的，在一些实施例中，如图1(a)所示的控制器1200在完成创建上述业务实例后，向业务部署装置1100发送业务实例创建的结果信息。业务部署装置1100接收所述 控制器发送的业务实例的创建结果信息。
可选的，在另一些实施例中，如图1(a)所示的业务部署装置1100向控制器1200发送业务实例创建查询请求，上述查询请求用于查询控制器1200业务实例创建的结果信息。控制器1200接收上述查询请求后，向业务部署装置1100发送业务实例的创建结果信息。业务部署装置1100接收所述控制器发送的业务实例的创建结果信息。
S711：业务部署装置输出所述业务实例的创建结果信息。
业务部署装置输出业务实例的创建结果信息。
可选的，如图1(a)所示的业务部署装置1100可以将已获取的业务实例创建结果信息，通过在业务部署装置1100的显示界面或第三方系统的显示界面进行显示。业务部署装置1100还可以将已获取的业务实例创建结果信息通过word、txt、excel等文件格式导出给网络人员。业务部署装置1100还可以将已获取的业务实例创建结果信息通过API开放给其他的业务系统。业务部署装置输出所述业务实例的创建结果信息的方式不在此一一描述。
S713：业务部署装置向所述控制器发送的第二请求，所述第二请求用于调用所述控制器的第二API来创建所述第一网络实例和第二网络实例。
业务部署装置向控制器发送的第二请求。第二请求用于调用控制器的第二API来创建所述第一网络实例和第二网络实例。
在一些实施例中，如图1(a)所示的控制器1200为第三方系统提供第二API用于创建网络实例，上述第二API支持创建一个网络实例或批量创建多个网络实例。
当第二API仅支持创建一个网络实例时，如图1(a)所示的业务部署装置1100向控制器1200发送的第二请求，上述第二请求用于调用控制器1200的第二API来创建第一网络实例。第二请求包括用于创建第一网络实例的信息，用于创建第一网络实例的信息包括所述业务实例的标识、所述第一网络实例的标识和所述第一设备的设备标识其中，第一网络实例用于部署所述业务，第一网络实例是第一设备对应的网络实例，第一网络实例包括所述第一设备的设备标识。业务部署装置1100向控制器1200发送的第二请求，上述第二请求还用于调用控制器1200的第二API来创建第二网络实例。第二请求包括用于创建第二网络实例的信息，用于创建第二网络实例的信息包括所述业务实例的标识、所述第二网络实例的标识和所述第一云PE的设备标识，其中，第二网络实例用于部署业务。上述第二网络实例是第一云PE对应的网络实例，第二网络实例包括所述第一云PE的设备标识，第一云PE用于连接第一云。
当第二API仅支持批量创建多个网络实例时，业务部署装置1100向控制器1200发送的第二请求，上述第二请求用于调用控制器1200的第二API来创建第一网络实例和第二网络实例。第二请求包括用于创建第一网络实例的信息和用于创建所述第二网络实例的信息，用于创建第一网络实例的信息包括所述业务实例的标识、第一网络实例的标识和所述第一设备的设备标识，用于创建所述第二网络实例的信息包括业务实例的标识、第二网络实例的标识和第一云PE的设备标识，其中，第一网络实例和第二网络实例用于部署业务，第一网络实例是第一设备对应的网络实例，第一网络实例包括第一设备的设备标识，第二网络实例是第一云PE对应的网络实例，第二网络实例包括第一云PE 的设备标识，第一云PE用于连接所第一云。
S715：控制器接收业务部署装置发送的第二请求。
控制器接收业务部署装置发送的第二请求。第二请求用于调用控制器的第二API来创建所述第一网络实例和第二网络实例。
可选的，当控制器的第二API仅支持创建一个网络实例，如图1(a)所示的控制器1200接收业务部署装置1100发送的第二请求，第二请求用于调用控制器的第二API来创建第一网络实例，第二请求包括业务实例的标识、第一网络实例的标识和第一设备的设备标识。
可选的，当控制器的第二API仅支持创建一个网络实例，控制器1200接收业务部署装置1100发送的第二请求，第二请求用于调用控制器的第二API来创建第二网络实例，第二请求包括业务实例的标识、第二网络实例的标识和第一云PE的设备标识。
可选的，当控制器的第二API支持批量创建多个网络实例，控制器1200接收业务部署装置1100发送的第二请求，第二请求用于调用控制器的第二API来创建第一网络实例和第二网络实例，第二请求包括业务实例的标识、第一网络实例的标识、第二网络实例的标识和第一云PE的设备标识。
S717：控制器创建所述第一网络实例和第二网络实例。
控制器根据第二请求，创建第一网络实例和第二网络实例。
如图1(a)所示的控制器1200接收到上述第二请求后，控制器1200创建第一网络实例和第二网络实例。控制器1200创建网络实例的具体流程可参考S403的相关描述，在此不再赘述。
S719：控制器向业务部署装置发送所述第一网络实例的创建结果信息和所述第二网络实例的创建结果。
控制器向业务部署装置发送第一网络实例的创建结果信息和第二网络实例的创建结果。
如图1(a)所示的控制器1200向业务部署装置1100发送第一网络实例的创建结果信息和所述第二网络实例的创建结果。
可选的，在一些实施例中，如图1(a)所示的控制器1200在完成创建上述网络实例后，向业务部署装置1100发送网络实例创建的结果信息，如第一网络实例创建的结果信息和第二网络实例创建的结果信息。
可选的，在另一些实施例中，如图1(a)所示的业务部署装置1100向控制器1200发送网络实例创建查询请求，上述查询请求用于查询控制器1200网络实例创建的结果信息。控制器1200接收上述查询请求后，向业务部署装置1100发送网络实例的创建结果信息。
S721：业务部署装置接收所述控制器发送的所述第一网络实例的创建结果信息和所述第二网络实例的创建结果。
业务部署装置接收控制器发送的第一网络实例的创建结果信息和第二网络实例的创建结果。第一网络实例的创建结果信息包括但不限于：第一网络实例的标识、第一网络实例的创建成功标记、第一网络实例的创建失败标记、第一网络实例的创建失败原因。 第二网络实例的创建结果信息包括但不限于：第二网络实例的标识、第二网络实例的创建成功标记、第二网络实例的创建失败标记、第二网络实例的创建失败原因。
可选的，在一些实施例中，如图1(a)所示的控制器1200在完成创建上述网络实例后，向业务部署装置1100发送网络实例创建的结果信息，如第一网络实例创建的结果信息和第二网络实例创建的结果信息。业务部署装置1100接收所述控制器发送的网络实例的创建结果信息。
可选的，在另一些实施例中，如图1(a)所示的业务部署装置1100向控制器1200发送网络实例创建查询请求，上述查询请求用于查询控制器1200网络实例创建的结果信息。控制器1200接收上述查询请求后，向业务部署装置1100发送网络实例的创建结果信息。业务部署装置1100接收所述控制器发送的网络实例的创建结果信息。
S723：业务部署装置输出所述第一网络实例的创建结果信息和所述第二网络实例的创建结果。
业务部署装置输出第一网络实例的创建结果信息和第二网络实例的创建结果。
可选的，如图1(a)所示的业务部署装置1100可以将已获取的网络实例创建结果信息，通过在业务部署装置1100的显示界面或第三方系统的显示界面进行显示。业务部署装置1100还可以将已获取的网络实例创建结果信息通过word、txt、excel等文件格式导出给网络人员。业务部署装置1100还可以将已获取的网络实例创建结果信息通过API等方式开放给其他的业务系统。业务部署装置输出所述网络实例的创建结果信息的方式不在此一一描述。
S725：业务部署装置向所述控制器发送的第三请求，所述第三请求用于调用所述控制器的第三API来部署所述第一网络实例和所述第二网络实例。
业务部署装置向控制器发送的第三请求。第三请求用于调用控制器的第三API来部署第一网络实例和第二网络实例。
在一些实施例中，如图1(a)所示的控制器1200向第三方系统提供第三API用于部署网络实例，第三API用于部署一个网络实例和/或批量部署多个网络实例。
当第三API仅用于部署一个网络实例时，如图1(a)所示的业务部署装置1100向控制器1200发送的第三请求，第三请求用于调用控制器1200的第三API来部署第一网络实例。第三请求包括用于部署第一网络实例的信息，用于部署第一网络实例的信息包括业务实例的标识和第一网络实例的标识。
当第三API仅用于部署一个网络实例时，如图1(a)所示的业务部署装置1100向控制器1200发送的第三请求，第三请求用于调用控制器1200的第三API来部署第二网络实例。所第三请求包括用于部署所述第二网络实例的信息，用于部署所述第二网络实例的信息包括业务实例的标识和第二网络实例的标识。
当第三API用于批量部署多个网络实例时，如图1(a)所示的业务部署装置1100向控制器1200发送的第三请求，第三请求用于调用控制器1200的第三API来部署第一网络实例和第二网络实例。所第三请求包括用于部署所述第一网络实例的信息和用于部署所述第二网络实例的信息，用于部署所述第一网络实例的信息包括业务实例的标识和第一网络实例的标识。用于部署所述第二网络实例的信息包括业务实例的标识和第二网络 实例的标识。
S727：控制器接收业务部署装置发送的第三请求。
控制器接收业务部署装置发送的第三请求。第三请求用于调用控制器的第三API来部署第一网络实例和第二网络实例。
控制器1200接收业务部署装置1100发送的第三请求。
在一些实施例中，控制器1200向第三方系统提供第三API用于部署网络实例，第三API用于部署一个网络实例和/或批量部署多个网络实例。
当第三API仅用于部署一个网络实例时，第三请求用于调用控制器1200的第三API来部署第一网络实例。第三请求包括用于部署第一网络实例的信息，用于部署第一网络实例的信息包括业务实例的标识和第一网络实例的标识。
当第三API仅用于部署一个网络实例时，第三请求用于调用控制器1200的第三API来部署第二网络实例。所第三请求包括用于部署所述第二网络实例的信息，用于部署所述第二网络实例的信息包括业务实例的标识和第二网络实例的标识。
当第三API用于批量部署多个网络实例时，第三请求用于调用控制器1200的第三API来部署第一网络实例和第二网络实例。所第三请求包括用于部署所述第一网络实例的信息和用于部署所述第二网络实例的信息，用于部署所述第一网络实例的信息包括业务实例的标识和第一网络实例的标识。用于部署所述第二网络实例的信息包括业务实例的标识和第二网络实例的标识。
S7029：控制器部署所述第一网络实例和第二网络实例。
控制器根据第三请求部署所述第一网络实例和第二网络实例。
如图1(a)所示的控制器1200接收到上述第三消息后，部署第一网络实例和第二网络实例。控制器1200部署第一网络实例和第二网络实例的具体流程可参考S405的相关描述，在此不再赘述。
S731：控制器向业务部署装置发送所述第一网络实例的部署结果信息和所述第二网络实例的部署结果信息。
控制器向业务部署装置发送第一网络实例的部署结果信息和第二网络实例的部署结果信息。第一网络实例的部署结果信息包括但不限于：第一网络实例的标识、第一网络实例的部署成功标记、第一网络实例的部署失败标记、第一网络实例的部署失败原因。第二网络实例的部署结果信息包括但不限于：第二网络实例的标识、第二网络实例的部署成功标记、第二网络实例的部署失败标记、第二网络实例的部署失败原因。
如图1(a)所示的控制器1200向业务部署装置1100发送第一网络实例的部署结果信息和第二网络实例的部署结果信息。
可选的，在一些实施例中，如图1(a)所示的控制器1200在完成部署上述网络实例后，向业务部署装置1100发送网络实例部署的结果信息，如第一网络实例部署的结果信息和第二网络实例部署的结果信息。
可选的，在另一些实施例中，如图1(a)所示的业务部署装置1100向控制器1200发送网络实例部署查询请求，上述查询请求用于查询控制器1200网络实例部署的结果信息。控制器1200接收上述查询请求后，向业务部署装置1100发送网络实例的部署结果 信息。
S733：业务部署装置接收所述控制器发送的所述第一网络实例的部署结果信息和所述第二网络实例的部署结果信息。
业务部署装置接收控制器发送的第一网络实例的部署结果信息和第二网络实例的部署结果信息。
可选的，在一些实施例中，如图1(a)所示的控制器1200在完成部署上述网络实例后，向业务部署装置1100发送网络实例部署的结果信息，如第一网络实例部署的结果信息和第二网络实例部署的结果信息。业务部署装置1100接收所述控制器发送的网络实例的部署结果信息。
可选的，在另一些实施例中，如图1(a)所示的业务部署装置1100向控制器1200发送网络实例部署查询请求，上述查询请求用于查询控制器1200网络实例部署的结果信息。控制器1200接收上述查询请求后，向业务部署装置1100发送网络实例的部署结果信息。业务部署装置1100接收所述控制器发送的网络实例的部署结果信息。
S735：输出所述第一网络实例的部署结果信息和所述第二网络实例的部署结果信息。
业务部署装置输出第一网络实例的部署结果信息和第二网络实例的部署结果信息。
可选的，如图1(a)所示的业务部署装置1100可以将已获取的网络实例部署结果信息，通过在业务部署装置1100的显示界面或第三方系统的显示界面进行显示。业务部署装置1100还可以将已获取的网络实例部署结果信息通过word、txt、excel等文件格式导出给网络人员。业务部署装置1100还可以将已获取的网络实例部署结果信息通过API等方式开放给其他的业务系统。业务部署装置输出所述网络实例的部署结果信息的方式不在此一一描述。
S737：业务部署装置向所述控制器发送的第四请求，所述第四请求用于调用所述控制器的第四API来删除所述业务实例。
业务部署装置向控制器发送的第四请求。第四请求用于调用控制器的第四API来删除业务实例。
如图1(a)所示的业务部署装置1100向控制器1200发送的第四请求，第四请求用于调用控制器1200的第四API来删除业务实例以及业务实例中的网络实例。控制器1200的第四API用于删除已经创建的业务实例。第四请求包括待删除业务实例的标识。
S739：控制器接收业务部署装置发送的第四请求。
控制器接收业务部署装置发送的第四请求。第四请求用于调用控制器的第四API来删除业务实例。
如图1(a)所示的控制器1200接收业务部署装置1100发送的第四请求。
S741：控制器删除所述业务实例。
控制器删除业务实例。
如图1(a)所示的控制器1200接收业务部署装置1100发送的第四请求后，删除第四请求中指定的业务实例。
具体方法如下：
控制器先判断待删除的业务实例中是否有已部署的网络实例。如果没有已部署的网 络实例，控制器根据第四请求中携带的业务实例的标识，在控制器上删除对应的业务实例。
如果待删除的业务实例中含有已部署的网络实例，控制器根据业务实例的标识获取对应的业务实例的信息。上述业务实例的信息包括业务实例的类型、已创建的网络实例的信息、租户的订单信息等。通过业务实例的信息中的已创建的网络实例的信息获取已创建的网络实例。通过已创建的网络实例的信息获取上述网络实例对应的网络设备。在删除上述网络设备中和上述业务实例有关的配置信息前，控制器需要判断上述网络设备中是否有其他业务实例共用的网络资源，如果没有共用的网络资源，控制器删除和上述业务实例有关的配置信息，删除业务实例相关的网络实例，完成删除操作。如果存在共用的网络资源，控制器不删除配置信息，结束删除操作。上述配置信息包括隧道配置信息、VPN实例信息和路由信息。
通过在业务部署装置调用控制器的服务化API直接创建与虚拟云专网业务对应的业务实例，并在业务实例中创建对应的第一网络实例和第二网络实例，部署第一网络实例和第二网络实例减少了业务部署装置与控制器之间的交互次数，并降低了人工配置的复杂度和业务部署难度，提高了业务部署的效率。
图8为本申请一个实施例提供的业务部署系统800的结构示意图。所述业务部署系统600用于通过图7所示的业务部署装置1100和控制器1200执行前述多个实施例，例如，图4(a)-图4(c)对应的实施例中的业务部署系统所执行的操作。如图8中实线框对应的模块所示，业务部署系统800包括如下模块。
业务实例创建模块8001，用于创建与所述业务对应的业务实例。
网络实例创建模块8002，用于在所述业务实例中创建第一网络实例和第二网络实例，所述第一网络实例和所述第二网络实例用于部署所述业务，其中，所述第一网络实例是第一设备对应的网络实例，所述第一网络实例包括所述第一设备的设备标识，所述第二网络实例是第一云运营商边缘PE对应的网络实例，所述第二网络实例包括所述第一云PE的设备标识，所述第一云PE用于连接所述第一云。
在一些实施例中，如图8中虚线框对应的模块所示，业务部署系统800还包括：信息设置模块8003。信息设置模块8003，用于设置所述第一云PE连接所述第一云的连接信息，所述连接信息包括以下一项或多项：所述第一云PE的设备标识，所述第一云PE的位置信息，所述第一云PE的第一接口的标识，所述第一云PE的第一虚拟局域网VLAN的标识，所述第一接口用于所述第一云PE连接所述第一云，所述第一VLAN用于所述第一云PE连接所述第一云。信息设置模块8003还用于根据所述业务实例的类型，设置所述第一业务模板。
在一些实施例中，如图8中虚线框对应的模块所示，业务部署系统800还包括：网络实例部署模块8004。
网络实例部署模块8004，用于部署所述第一网络实例和所述第二网络实例。网络实例部署模块8004还用于向所述第一设备发送第一配置信息。所述第一配置信息用于配置所述业务。网络实例部署模块8004，还用于向所述第一云PE发送第二配置信息，所述第二配置信息用于配置所述业务。网络实例部署模块8004，还用于根据所述第一网络 实例、所述第二网络实例和第一业务模板确定所述第一配置信息和所述第二配置信息。其中，所述第一业务模板指示所述业务实例的配置信息，所述业务实例的配置信息包括以下一项或多项：隧道配置信息、虚拟专用网络VPN实例配置信息或路由信息。
在一些实施例中，如图8中虚线框对应的模块所示，业务部署系统800还包括：请求消息处理模块8005。
请求消息处理模块8005，用于接收业务部署装置发送的第一请求。所述第一请求用于调用所述控制器的第一应用程序编程接口API来创建所述业务实例，所述第一请求包括所述业务实例的标识。
请求消息处理模块8005，还用于接收所述业务部署装置发送的第二请求。所述第二请求用于调用所述控制器的第二API来创建所述第一网络实例和/或第二网络实例。所述第二请求包括用于创建第一网络实例的信息和/或用于创建第二网络实例的信息。所述用于创建第一网络实例的信息包括所述业务实例的标识、所述第一网络实例的标识和所述第一设备的设备标识。所述用于创建第二网络实例的信息包括所述业务实例的标识、所述第二网络实例的标识和所述第一云PE的设备标识。
请求消息处理模块8005，还用于接收所述业务部署装置发送的第三请求。所述第三请求用于调用所述控制器的第三API来部署所述第一网络实例和/或所述第二网络实例。所述第四请求包括用于部署所述第一网络实例的信息和/或用于部署所述第二网络实例的信息。所述用于部署所述第一网络实例的信息包括所述业务实例的标识和所述第一网络实例的标识。所述用于部署所述第二网络实例的信息包括所述业务实例的标识和所述第二网络实例的标识。
请求消息处理模块8005，还用于接收所述业务部署装置发送的第四请求，所述第四请求用于调用所述控制器的第四API来获得所述第一网络实例的部署结果和/或所述第二网络实例的部署结果。
在一些实施例中，请求消息处理模块8005，还用于向控制器发送第一请求。所述第一请求用于调用所述控制器的第一应用程序编程接口API来创建所述业务的业务实例，所述第一请求包括所述业务实例的标识。
请求消息处理模块8005，还用于向所述控制器发送的第二请求。所述第二请求用于调用所述控制器的第二API来创建第一网络实例和/或第二网络实例。所述第二请求包括用于创建所述第一网络实例的信息和/或用于创建所述第二网络实例的信息。所述用于创建所述第一网络实例的信息包括所述业务实例的标识、所述第一网络实例的标识和所述第一设备的设备标识。所述用于创建所述第二网络实例的信息包括所述业务实例的标识、所述第二网络实例的标识和所述第一云PE的设备标识。其中，所述第一网络实例和所述第二网络实例用于部署所述业务。所述第一网络实例是第一设备对应的网络实例，所述第一网络实例包括所述第一设备的设备标识。所述第二网络实例是第一云运营商边缘PE对应的网络实例，所述第二网络实例包括所述第一云PE的设备标识。所述第一云PE用于连接所述第一云。还用于向所述控制器发送的第三请求，所述第三请求用于调用所述控制器的第三API来部署所述第一网络实例和/或所述第二网络实例。所述第三请求包括用于部署所述第一网络实例的信息和/或用于部署所述第二网络实例的信息。 所述用于部署所述第一网络实例的信息包括所述业务实例的标识和所述第一网络实例的标识。所述用于部署所述第二网络实例的信息包括所述业务实例的标识和所述第二网络实例的标识。
在一些实施例中，如图8中虚线框对应的模块所示，业务部署系统800还包括：结果信息处理模块8006。
结果信息处理模块8006，用于向所述业务部署装置发送所述第一网络实例的部署结果和/或所述第二网络实例的部署结果。
在一些实施例中，结果信息处理模块8006，还用于接收所述控制器发送的所述业务实例的创建结果信息。还用于输出所述业务实例的创建结果信息。还用于接收所述控制器发送的所述第一网络实例的创建结果信息和/或所述第二网络实例的创建结果。还用于输出所述第一网络实例的创建结果信息和/或所述第二网络实例的创建结果。还用于接收所述控制器发送的所述第一网络实例的部署结果信息和/或所述第二网络实例的部署结果信息。还用于输出所述第一网络实例的部署结果信息和/或所述第二网络实例的部署结果信息。
图8所示的各个模块可以是软件功能模块或虚拟功能模块，也可以是硬件模块。在一些实施例中，业务部署系统800中的各个模块可以部署在同一个物理设备中；在另一些实施例中，业务部署系统800中的各个模块可以部署在多台不同的物理设备中。业务部署系统800中的各个模块可以是硬件模块或者软件和硬件相结合的模块。例如业务部署系统800中的业务实例创建模块8001、网络实例创建模块8002、信息设置模块8003、网络实例部署模块8004、请求消息处理模块8005和结果信息处理模块可以部署在一个物理设备中，用于执行图7所示的实施例中控制器1200的执行的方法700。如业务部署系统800中的请求消息处理模块8005和结果信息处理模块可以部署在另一个物理设备中，用于执行图7所示的实施例中业务部署装置1100的执行的方法700。
图9为本申请一个实施例提供的业务部署装置的结构示意图。图9所示的业务部署装置900用于执行前述多个实施例，例如与图7对应的实施例，中的业务部署装置1100或控制器1200所执行的操作。如图9所示，装置900包括至少一个处理器901、连接线902、存储器903以及至少一个网络接口904。存储器903用于存放程序模块和数据。在一些实施例中，如图9中的实线框对应的程序模块所示，存储器903中存放的程序模块包括业务实例创建模块9031和网络实例创建模块9032。
当被处理器901执行时，业务实例创建模块9031，用于创建与所述业务对应的业务实例。
当被处理器901执行时，网络实例创建模块9032，用于在所述业务实例中创建第一网络实例和第二网络实例，所述第一网络实例和所述第二网络实例用于部署所述业务，其中，所述第一网络实例是第一设备对应的网络实例，所述第一网络实例包括所述第一设备的设备标识，所述第二网络实例是第一云运营商边缘PE对应的网络实例，所述第二网络实例包括所述第一云PE的设备标识，所述第一云PE用于连接所述第一云。
在另一些实施例中，如图9中的虚线框对应的程序模块所示，存储器903中存放的程序模块包括一下一个或多个模块：信息设置模块9033、网络实例部署模块9034、请 求消息处理模块9035、结果信息处理模块9036。
当被处理器901执行时，信息设置模块9033，用于设置所述第一云PE连接所述第一云的连接信息，所述连接信息包括以下一项或多项：所述第一云PE的设备标识，所述第一云PE的位置信息，所述第一云PE的第一接口的标识，所述第一云PE的第一虚拟局域网VLAN的标识，所述第一接口用于所述第一云PE连接所述第一云，所述第一VLAN用于所述第一云PE连接所述第一云。信息设置模块8003还用于根据所述业务实例的类型，设置所述第一业务模板。
当被处理器901执行时，网络实例部署模块9034，用于执行如图4(a)所示的方法400中S405所描述的控制器执行的方法步骤，在此不再赘述。
在一些实施例中，当被处理器901执行时，请求消息处理模块9035，用于执行如图7所示的方法700所描述的控制器1200执行的方法步骤，在此不再赘述。
在一些实施例中，当被处理器901执行时，请求消息处理模块9035，用于执行如图7所示的方法700所描述的业务部署装置1100执行的方法步骤，在此不再赘述。
当被处理器901执行时，结果信息处理模块9036，用于执行如图7所示的方法700所描述的业务部署装置1100执行的方法步骤，在此不再赘述。处理器901例如是通用中央处理器(central processing unit，CPU)、数字信号处理器(digital signal processor，DSP)、网络处理器(network processer，NP)、图形处理器(Graphics Processing Unit，GPU)、神经网络处理器(neural-network processing units，NPU)、数据处理单元(Data Processing Unit，DPU)、微处理器或者一个或多个用于实现本申请方案的集成电路。例如，处理器901包括专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。PLD例如是复杂可编程逻辑器件(complex programmable logic device，CPLD)、现场可编程逻辑门阵列(field-programmable gate array，FPGA)、通用阵列逻辑(generic array logic，GAL)或其任意组合。其可以实现或执行结合本申请实施例公开内容所描述的各种逻辑方框、模块和电路。所述处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，DSP和微处理器的组合等等。
业务部署装置900还可以包括连接线902。连接线902用于在业务部署装置900的各组件之间传送信息。总线可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器903例如是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其它类型的静态存储设备，又如是随机存取存储器(random access memory，RAM)或者可存储信息和指令的其它类型的动态存储设备，又如是电可擦可编程只读存储器(electrically erasable programmable read-only Memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其它光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其它磁存储设备，或者是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任 何其它介质，但不限于此。存储器903例如是独立存在，并通过总线与处理器901相连接。存储器903也可以和处理器901集成在一起。
网络接口904使用任何收发器一类的装置，用于与其它设备或通信网络通信，通信网络可以为以太网、无线接入网(RAN)或无线局域网(wireless local area networks，WLAN)等。网络接口904可以包括有线通信接口，还可以包括无线通信接口。具体的，网络接口904可以为以太(Ethernet)接口、快速以太(Fast Ethernet，FE)接口、千兆以太(Gigabit Ethernet，GE)接口，异步传输模式(Asynchronous Transfer Mode，ATM)接口，无线局域网(wireless local area networks，WLAN)接口，蜂窝网络通信接口或其组合。以太网接口可以是光接口，电接口或其组合。在本申请实施例中，网络接口904可以用于业务部署装置900与其他设备进行通信。
在具体实现中，作为一种实施例，处理器901可以包括一个或多个CPU。这些处理器中的每一个可以是一个单核处理器，也可以是一个多核处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，业务部署装置900可以包括多个处理器。这些处理器中的每一个可以是一个单核处理器，也可以是一个多核处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，业务部署装置900还可以包括输出设备和输入设备。输出设备和处理器901通信，可以以多种方式来显示信息。例如，输出设备可以是液晶显示器(liquid crystal display，LCD)、发光二级管(light emitting diode，LED)显示设备、阴极射线管(cathode ray tube，CRT)显示设备或投影仪(projector)等。输入设备和处理器901通信，可以以多种方式接收用户的输入。例如，输入设备可以是鼠标、键盘、触摸屏设备或传感设备等。
图9所示的业务部署装置900用于执行前述多个实施例，例如与图7对应的实施例，中的业务部署装置所执行的操作。如图9所示，业务部署装置900包括至少一个处理器901通过执行存储器903中的计算机可读程序可以使业务部署装置900执行前述多个实施例，例如与图7对应的实施例中的控制器1200或业务部署装置1100所执行的操作。
本申请的说明书和权利要求书及上述附图中的操作顺序，不限于描述中特定的顺序或先后次序。应该理解这样使用的数据在适当情况下同时进行或可以改变顺序，以便描述的实施例能够以除了在附图中的图示或描述的内容以外的顺序实施。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
本申请的一些实施例提供一种计算机程序产品，所述计算机程序产品在被计算机执行时，能够使计算机执行本申请多个实施例中的业务部署系统所执行的操作。
本申请的一些实施例提供一种计算机可读存储介质，例如硬盘、内存、闪存等。所 述计算机存储介质中存储有计算机可读指令。当计算机执行所述计算机可读指令时，能够执行本申请多个实施例中的业务部署系统所执行的操作。
本申请的一些实施例提供一种包括多个模块的业务部署系统，所述多个模块协同工作，执行本申请多个实施例中的业务部署系统所执行的操作。所述多个模块可以在同一个硬件设备中，也可以在不同的硬件设备中。
以上所述，仅为本申请较佳的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉该技术的人在本申请所揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本申请的保护范围之内。

Claims (68)

  1. 一种业务的部署方法，所述业务是为租户提供虚拟云专网，所述虚拟云专网用于所述租户访问第一云，其特征在于，所述方法由控制器执行，所述方法包括：
    创建与所述业务对应的业务实例；
    在所述业务实例中创建第一网络实例和第二网络实例，所述第一网络实例和所述第二网络实例用于部署所述业务，其中，所述第一网络实例是第一设备对应的网络实例，所述第一网络实例包括所述第一设备的设备标识，所述第二网络实例是第一云运营商边缘PE对应的网络实例，所述第二网络实例包括所述第一云PE的设备标识，所述第一云PE用于连接所述第一云。
  2. 根据权利要求1所述的方法，其特征在于，在创建所述业务实例之前，所述方法还包括：
    设置所述第一云PE连接所述第一云的连接信息，所述连接信息包括以下一项或多项：所述第一云PE的设备标识，所述第一云PE的位置信息，所述第一云PE的第一接口的标识，所述第一云PE的第一虚拟局域网VLAN的标识，所述第一接口配置所述第一VLAN,所述第一云PE通过所述第一VLAN连接所述第一云。
  3. 根据权利要求1或2所述的方法，其特征在于，所述业务实例包括所述业务实例的标识。
  4. 根据权利要求3述的方法，其特征在于，所述业务实例还包括以下一项或多项：所述业务实例的类型、已创建的网络实例的数量、所述租户的订单信息。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述业务实例的类型包括单云或多云，所述单云是指所述租户通过所述第一设备仅可访问一个云，所述多云是指所述租户通过所述第一设备可访问多个云。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述第一设备是第一用户驻地设备CPE。
  7. 根据权利要求6所述的方法，其特征在于，所述第一网络实例还包括以下一项或多项：所述第一CPE的位置信息、所述第一CPE的网络侧IP地址、所述第一CPE的租户侧IP地址、所述第一CPE至所述租户的局域网的路由信息。
  8. 根据权利要求1-5中任一项所述的方法，其特征在于，所述第一设备是第二云PE，所述第二云PE用于连接第二云。
  9. 根据权利要求8所述的方法，其特征在于，所述第一网络实例还包括以下一项或多项：所述第二云PE的位置信息、所述第二云的供应商信息、所述第二云PE连接所述第二云的IP地址，所述第二云PE连接所述第二云的路由信息、所述第二云PE连接所述第二云的接口服 务质量信息。
  10. 根据权利要求1-9中任一项所述的方法，其特征在于，所述第二网络实例还包括以下一项或多项：所述第一云PE的位置信息、所述第一云的供应商信息、所述第一云PE连接所述第一云的IP地址，所述第一云PE连接所述第一云的路由信息、所述第一云PE连接所述第一云的接口服务质量信息。
  11. 根据权利要求1-10中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述第一云PE的位置信息和所述第一云PE连接所述第一云的连接信息，确定所述第一云PE的设备标识。
  12. 根据权利要求1-11中任一项所述的方法，其特征在于，所述方法还包括：
    部署所述第一网络实例和所述第二网络实例。
  13. 根据权利要求1-12中任一项所述的方法，其特征在于，所述部署所述第一网络实例和所述第二网络实例，包括：
    向所述第一设备发送用于配置所述业务的第一配置信息；
    向所述第一云PE发送用于配置所述业务的第二配置信息。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    根据所述第一网络实例、所述第二网络实例和第一业务模板确定所述第一配置信息和所述第二配置信息，其中，所述第一业务模板指示所述业务实例的配置信息，所述业务实例的配置信息包括以下一项或多项：隧道配置信息、虚拟专用网络VPN实例配置信息或路由信息。
  15. 根据权利要求14所述的方法，其特征在于，在部署所述第一网络实例和所述第二网络实例之前，所述方法还包括：
    根据所述业务实例的类型，设置所述第一业务模板。
  16. 根据权利要求1-15中任一项所述的方法，其特征在于，所述虚拟云专网还用于所述租户访问第三云，所述方法还包括：
    在所述业务实例中创建第三网络实例，所述第三网络实例是第三云PE对应的网络实例，所述第三网络实例包括所述第三云PE的设备标识，所述第三云PE用于连接所述第三云。
  17. 根据权利要求1-16中任一项所述的方法，其特征在于，在创建所述业务实例之前，所述方法还包括：
    接收业务部署装置发送的第一请求，所述第一请求用于调用所述控制器的第一应用程序编程接口API来创建所述业务实例，所述第一请求包括所述业务实例的标识。
  18. 根据权利要求17所述的方法，其特征在于，所述第一请求还包括以下一项或多项：所述业务实例的类型、所述租户的标识、所述租户的订单信息。
  19. 根据权利要求17或18所述的方法，其特征在于，在创建所述第一网络实例和所述第二网络实例前，所述方法还包括：
    接收所述业务部署装置发送的第二请求，所述第二请求用于调用所述控制器的第二API来创建所述第一网络实例和/或第二网络实例，所述第二请求包括用于创建第一网络实例的信息和/或用于创建第二网络实例的信息，所述用于创建第一网络实例的信息包括所述业务实例的标识、所述第一网络实例的标识和所述第一设备的设备标识，所述用于创建第二网络实例的信息包括所述业务实例的标识、所述第二网络实例的标识和所述第一云PE的设备标识。
  20. 根据权利要求17-19中任一项所述的方法，其特征在于，在部署所述第一网络实例和所述第二网络实例之前，所述方法还包括：
    接收所述业务部署装置发送的第三请求，所述第三请求用于调用所述控制器的第三API来部署所述第一网络实例和/或所述第二网络实例，所述第三请求包括用于部署所述第一网络实例的信息和/或用于部署所述第二网络实例的信息，所述用于部署所述第一网络实例的信息包括所述业务实例的标识和所述第一网络实例的标识，所述用于部署所述第二网络实例的信息包括所述业务实例的标识和所述第二网络实例的标识。
  21. 根据权利要求17-20中任一项所述的方法，其特征在于，所述方法还包括：
    向所述业务部署装置发送所述第一网络实例的部署结果信息和/或所述第二网络实例的部署结果信息。
  22. 根据权利要求17-21中任一项所述的方法，其特征在于，所述方法还包括：
    接收所述业务部署装置发送的第四请求，所述第四请求用于调用所述控制器的第四API来获得所述第一网络实例的部署结果信息和/或所述第二网络实例的部署结果信息。
  23. 根据权利要求1-22中任一项所述的方法，其特征在于，所述虚拟云专网用于所述租户的至少一个站点通过至少一条虚拟专用线路访问所述第一云。
  24. 根据权利要求1-23中任一项所述的方法，其特征在于，所述第一云包括至少一个虚拟私有云VPC。
  25. 根据权利要求1-24中任一项所述的方法，其特征在于，所述租户的至少一个站点中的每个站点的类型包括：分支网络或云。
  26. 一种业务的部署方法，所述业务是为租户提供虚拟云专网，所述虚拟云专网用于所述租户访问第一云，所述特征在于，所述方法由业务部署装置执行，所述方法包括：
    向控制器发送第一请求，所述第一请求用于调用所述控制器的第一应用程序编程接口API来创建所述业务的业务实例，所述第一请求包括所述业务实例的标识；
    向所述控制器发送第二请求，所述第二请求用于调用所述控制器的第二API来创建第一网络实例和/或第二网络实例，其中，所述第一网络实例和/或所述第二网络实例用于部署所述 业务，所述第一网络实例是第一设备对应的网络实例，所述第二网络实例是第一云运营商边缘PE对应的网络实例，所述第一云PE用于连接所述第一云，所述第二请求包括用于创建所述第一网络实例的信息和/或用于创建所述第二网络实例的信息，所述用于创建所述第一网络实例的信息包括所述业务实例的标识、所述第一网络实例的标识和所述第一设备的设备标识，所述用于创建所述第二网络实例的信息包括所述业务实例的标识、所述第二网络实例的标识和所述第一云PE的设备标识，所述第一网络实例包括所述第一设备的设备标识，所述第二网络实例包括所述第一云PE的设备标识。
  27. 根据权利要求26所述的方法，其特征在于，所述第一请求还包括以下一项或多项：所述业务实例的类型、所述租户的标识、所述租户的订单信息。
  28. 根据权利要求26或27所述的方法，其特征在于，所述第一设备是第一用户驻地设备CPE。
  29. 根据权利要求28所述的方法，其特征在于，所述用于创建所述第一网络实例的信息还包括以下一项或多项：所述第一CPE的位置信息、所述第一CPE的网络侧IP地址、所述第一CPE的租户侧IP地址、所述第一CPE至所述租户的局域网的路由信息。
  30. 根据权利要求26-29中任一项所述的方法，其特征在于，所述第一设备是第二云PE，所述第二云PE用于连接第二云。
  31. 根据权利要求30所述的方法，其特征在于，所述用于创建所述第一网络实例的信息还包括以下一项或多项：所述第二云PE的位置信息、所述第二云的供应商信息、所述第二云PE连接所述第二云的IP地址，所述第二云PE连接所述第二云的路由信息、所述第二云PE连接所述第二云的接口服务质量信息。
  32. 根据权利要求26-31中任一项所述的方法，其特征在于，所述用于创建所述第二网络实例的信息包括以下一项或多项：所述第一云PE的位置信息、所述第一云的供应商信息、所述第一云PE连接所述第一云的IP地址，所述第一云PE连接所述第一云的路由信息、所述第一云PE连接所述第一云的接口服务质量信息。
  33. 根据权利要求26-32中任一项所述的方法，其特征在于，所述方法还包括：
    向所述控制器发送第三请求，所述第三请求用于调用所述控制器的第三API来部署所述第一网络实例和/或所述第二网络实例，所述第三请求包括用于部署所述第一网络实例的信息和/或用于部署所述第二网络实例的信息，所述用于部署所述第一网络实例的信息包括所述业务实例的标识和所述第一网络实例的标识，所述用于部署所述第二网络实例的信息包括所述业务实例的标识和所述第二网络实例的标识。
  34. 根据权利要求26-33中任一项所述的方法，其特征在于，所述方法还包括：
    接收所述控制器发送的所述业务实例的创建结果信息。
  35. 根据权利要求34所述的方法，其特征在于，所述方法还包括：
    输出所述业务实例的创建结果信息。
  36. 根据权利要求26-35中任一项所述的方法，其特征在于，所述方法还包括：
    接收所述控制器发送的所述第一网络实例的创建结果信息和/或所述第二网络实例的创建结果信息。
  37. 根据权利要求36所述的方法，其特征在于，所述方法还包括：
    输出所述第一网络实例的创建结果信息和/或所述第二网络实例的创建结果信息。
  38. 根据权利要求26-37中任一项所述的方法，其特征在于，所述方法还包括：
    接收所述控制器发送的所述第一网络实例的部署结果信息和/或所述第二网络实例的部署结果信息。
  39. 根据权利要求38所述的方法，其特征在于，所述方法还包括：
    输出所述第一网络实例的部署结果信息和/或所述第二网络实例的部署结果信息。
  40. 根据权利要求26至39中任一项所述的方法，其特征在于，所述业务实例的类型包括：单云或多云，所述单云是指所述租户通过所述第一设备仅可访问一个云，所述多云是指所述租户通过所述第一设备可访问多个云。
  41. 根据权利要求26-40中任一项所述的方法，所述虚拟云专网用于所述租户的至少一个站点通过至少一条虚拟专用线路访问所述第一云。
  42. 根据权利要求26-41中任一项所述的方法，其特征在于，所述第一云包括至少一个虚拟私有云VPC。
  43. 根据权利要求26-42中任一项所述的方法，其特征在于，所述租户的至少一个站点中的每个站点的类型包括：分支网络或云。
  44. 一种业务部署的装置，其特征在于，所述业务是为租户提供虚拟云专网，所述虚拟云专网用于所述租户访问第一云，其特征在于，所述装置包括：
    业务实例创建模块，用于创建与所述业务对应的业务实例；
    网络实例创建模块，用于在所述业务实例中创建第一网络实例和第二网络实例，所述第一网络实例和所述第二网络实例用于部署所述业务，其中，所述第一网络实例是第一设备对应的网络实例，所述第一网络实例包括所述第一设备的设备标识，所述第二网络实例是第一云运营商边缘PE对应的网络实例，所述第二网络实例包括所述第一云PE的设备标识，所述第一云PE用于连接所述第一云。
  45. 根据权利要求44所述的装置，其特征在于，所述装置还包括：
    信息设置模块，用于设置所述第一云PE连接所述第一云的连接信息，所述连接信息包括以下一项或多项：所述第一云PE的设备标识，所述第一云PE的位置信息，所述第一云PE的第一接口的标识，所述第一云PE的第一虚拟局域网VLAN的标识，所述第一接口用于所述第一云PE连接所述第一云，所述第一VLAN用于所述第一云PE连接所述第一云。
  46. 根据权利要求44或45所述的装置，其特征在于，所述业务实例包括所述业务实例的标识。
  47. 根据权利要求44-46中任一项所述的装置，其特征在于，所述装置还包括：
    网络实例部署模块，用于部署所述第一网络实例和所述第二网络实例。
  48. 根据权利要求44-47中任一项所述的装置，其特征在于，所述装置还包括：
    所述网络实例部署模块，还用于向所述第一设备发送用于配置所述业务的第一配置信息；
    还用于向所述第一云PE发送用于配置所述业务的第二配置信息。
  49. 根据权利要求44-48中任一项所述的装置，其特征在于，所述装置还包括：
    所述网络实例部署模块，还用于根据所述第一网络实例、所述第二网络实例和第一业务模板确定所述第一配置信息和所述第二配置信息，其中，所述第一业务模板指示所述业务实例的配置信息，所述业务实例的配置信息包括以下一项或多项：隧道配置信息、虚拟专用网络VPN实例配置信息或路由信息。
  50. 根据权利要求49所述的装置，其特征在于，所述装置还包括：
    所述信息设置模块，还用于根据所述业务实例的类型，设置所述第一业务模板。
  51. 根据权利要求44-50中任一项所述的装置，其特征在于，所述装置还包括：
    请求消息处理模块，用于接收业务部署装置发送的第一请求，所述第一请求用于调用所述装置的第一应用程序编程接口API来创建所述业务实例，所述第一请求包括所述业务实例的标识。
  52. 根据权利要求51所述的装置，其特征在于，所述装置还包括：
    所述请求消息处理模块，还用于接收所述业务部署装置发送的第二请求，所述第二请求用于调用所述装置的第二API来创建所述第一网络实例和/或第二网络实例，所述第二请求包括用于创建第一网络实例的信息和/或用于创建第二网络实例的信息，所述用于创建第一网络实例的信息包括所述业务实例的标识、所述第一网络实例的标识和所述第一设备的设备标识，所述用于创建第二网络实例的信息包括所述业务实例的标识、所述第二网络实例的标识和所述第一云PE的设备标识。
  53. 根据权利要求51或52所述的装置，其特征在于，所述装置还包括：
    所述请求消息处理模块，还用于接收所述业务部署装置发送的第三请求，所述第三请求用于调用所述装置的第三API来部署所述第一网络实例和/或所述第二网络实例，所述第三请 求包括用于部署所述第一网络实例的信息和/或用于部署所述第二网络实例的信息，所述用于部署所述第一网络实例的信息包括所述业务实例的标识和所述第一网络实例的标识，所述用于部署所述第二网络实例的信息包括所述业务实例的标识和所述第二网络实例的标识。
  54. 根据权利要求51-53中任一项所述的装置，其特征在于，所述装置还包括：
    所述请求消息处理模块，还用于接收所述业务部署装置发送的第四请求，所述第四请求用于调用所述装置的第四API来获得所述第一网络实例的部署结果信息和/或所述第二网络实例的部署结果信息。
  55. 根据权利要求51-54所述的装置，其特征在于，所述装置还包括：
    结果信息处理模块，用于向所述业务部署装置发送所述第一网络实例的部署结果信息和/或所述第二网络实例的部署结果信息。
  56. 一种业务部署的装置，所述业务是为租户提供虚拟云专网，所述虚拟云专网用于所述租户访问第一云，其特征在于，所述装置包括：
    请求消息处理模块，用于向控制器发送第一请求，所述第一请求用于调用所述控制器的第一应用程序编程接口API来创建所述业务的业务实例，所述第一请求包括所述业务实例的标识；
    所述请求消息处理模块，还用于向所述控制器发送第二请求，所述第二请求用于调用所述控制器的第二API来创建第一网络实例和/或第二网络实例，其中，所述第一网络实例和/或所述第二网络实例用于部署所述业务，所述第一网络实例是第一设备对应的网络实例，所述第二网络实例是第一云运营商边缘PE对应的网络实例，所述第一云PE用于连接所述第一云，所述第二请求包括用于创建所述第一网络实例的信息和/或用于创建所述第二网络实例的信息，所述用于创建所述第一网络实例的信息包括所述业务实例的标识、所述第一网络实例的标识和所述第一设备的设备标识，所述用于创建所述第二网络实例的信息包括所述业务实例的标识、所述第二网络实例的标识和所述第一云PE的设备标识，所述第一网络实例包括所述第一设备的设备标识，所述第二网络实例包括所述第一云PE的设备标识。
  57. 根据权利要求56所述的装置，其特征在于，所述装置还包括：
    所述请求消息处理模块，还用于向所述控制器发送第三请求，所述第三请求用于调用所述控制器的第三API来部署所述第一网络实例和/或所述第二网络实例，所述第三请求包括用于部署所述第一网络实例的信息和/或用于部署所述第二网络实例的信息，所述用于部署所述第一网络实例的信息包括所述业务实例的标识和所述第一网络实例的标识，所述用于部署所述第二网络实例的信息包括所述业务实例的标识和所述第二网络实例的标识。
  58. 根据权利要求56或57所述的装置，其特征在于，所述装置还包括：
    结果信息处理模块，用于接收所述控制器发送的所述业务实例的创建结果信息。
  59. 根据权利要求56-59中任一项所述的装置，其特征在于，所述装置还包括：
    所述结果信息处理模块，还用于输出所述业务实例的创建结果信息。
  60. 根据权利要求56-59中任一项所述的装置，其特征在于，所述装置还包括：
    所述结果信息处理模块，还用于接收所述控制器发送的所述第一网络实例的创建结果信息和/或所述第二网络实例的创建结果信息。
  61. 根据权利要求56-60中任一项所述的装置，其特征在于，所述装置还包括：
    所述结果信息处理模块，还用于输出所述第一网络实例的创建结果信息和/或所述第二网络实例的创建结果信息。
  62. 根据权利要求56-61中任一项所述的装置，其特征在于，所述装置还包括：
    所述结果信息处理模块，还用于接收所述控制器发送的所述第一网络实例的部署结果信息和/或所述第二网络实例的部署结果信息。
  63. 根据权利要求56-62中任一项所述的装置，其特征在于，所述装置还包括：
    所述结果信息处理模块，还用于输出所述第一网络实例的部署结果信息和/或所述第二网络实例的部署结果信息。
  64. 一种业务部署系统，所述系统包括控制器和业务部署装置，其特征在于，所述控制器实现如权利要求1-25中任一所述的方法，所述业务部署装置实现如权利要求26-43中任一项所述的方法。
  65. 一种通信装置，用作控制器，其特征在于，所述通信装置包括：
    存储器，包括指令；
    处理器，当所述处理器执行所述指令时，使得所述通信装置实现权利要求1-25中任一所述的方法。
  66. 一种通信装置，用作业务部署装置，其特征在于，所述通信装置包括：
    存储器，包括指令；
    处理器，当所述处理器执行所述指令时，使得所述通信装置实现权利要求26-43中任一所述的方法。
  67. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时，实现如权利要求1-43中任一所述的方法。
  68. 一种计算机程序产品，其特征在于，包括计算机程序，所述计算机程序被处理器执行时，实现如权利要求1-43任一项所述的方法。
PCT/CN2022/076601 2021-03-18 2022-02-17 一种业务的部署方法、装置及系统 WO2022193897A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22770252.9A EP4290819A4 (en) 2021-03-18 2022-02-17 SERVICE PROVISION METHOD, APPARATUS AND SYSTEM
US18/468,136 US20240007364A1 (en) 2021-03-18 2023-09-15 Method, Apparatus, and System for Deploying Service

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110293083.8 2021-03-18
CN202110293083 2021-03-18
CN202111164145.1A CN115118585A (zh) 2021-03-18 2021-09-30 一种业务的部署方法、装置及系统
CN202111164145.1 2021-09-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/468,136 Continuation US20240007364A1 (en) 2021-03-18 2023-09-15 Method, Apparatus, and System for Deploying Service

Publications (1)

Publication Number Publication Date
WO2022193897A1 true WO2022193897A1 (zh) 2022-09-22

Family

ID=83321515

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/076601 WO2022193897A1 (zh) 2021-03-18 2022-02-17 一种业务的部署方法、装置及系统

Country Status (3)

Country Link
US (1) US20240007364A1 (zh)
EP (1) EP4290819A4 (zh)
WO (1) WO2022193897A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6487581B1 (en) * 1999-05-24 2002-11-26 Hewlett-Packard Company Apparatus and method for a multi-client event server
CN103905508A (zh) * 2012-12-28 2014-07-02 华为技术有限公司 云平台应用部署方法及装置
CN107786593A (zh) * 2016-08-25 2018-03-09 阿里巴巴集团控股有限公司 任务部署方法、实例部署方法、装置及设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107689882B (zh) * 2016-08-05 2020-04-21 华为技术有限公司 一种虚拟化网络中业务部署的方法和装置
US10009443B1 (en) * 2017-06-06 2018-06-26 IP Company 8, LLC Provisioning remote application servers on a service provider infrastructure as a service platform
US11388054B2 (en) * 2019-04-30 2022-07-12 Intel Corporation Modular I/O configurations for edge computing using disaggregated chiplets

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6487581B1 (en) * 1999-05-24 2002-11-26 Hewlett-Packard Company Apparatus and method for a multi-client event server
CN103905508A (zh) * 2012-12-28 2014-07-02 华为技术有限公司 云平台应用部署方法及装置
CN107786593A (zh) * 2016-08-25 2018-03-09 阿里巴巴集团控股有限公司 任务部署方法、实例部署方法、装置及设备

Also Published As

Publication number Publication date
EP4290819A4 (en) 2024-06-26
US20240007364A1 (en) 2024-01-04
EP4290819A1 (en) 2023-12-13

Similar Documents

Publication Publication Date Title
US11362986B2 (en) Resolution of domain name requests in heterogeneous network environments
US10547463B2 (en) Multicast helper to link virtual extensible LANs
US8774054B2 (en) Network policy configuration method, management device, and network management center device
KR101714279B1 (ko) 폴리시 기반 데이터센터 네트워크 자동화를 제공하는 시스템 및 방법
CN115918139A (zh) 网络切片的主动保证
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
EP3676699B1 (en) Apparatus and method for configuring and monitoring virtual applications
EP3637687B1 (en) Method for orchestrating software defined network, and sdn controller
US20210058295A1 (en) Vendor agnostic profile-based modeling of service access endpoints in a multitenant environment
WO2017162089A1 (zh) 网络服务的业务配置方法和装置
WO2014166247A1 (zh) 一种虚拟网络管理的实现方法和系统
US10778465B1 (en) Scalable cloud switch for integration of on premises networking infrastructure with networking services in the cloud
US11469998B2 (en) Data center tenant network isolation using logical router interconnects for virtual network route leaking
US11165653B2 (en) Node discovery mechanisms in a switchless network
CN115118585A (zh) 一种业务的部署方法、装置及系统
US20210051077A1 (en) Communication system, communication apparatus, method, and program
WO2021218627A1 (zh) 一种通信方法及相关设备
US20220350637A1 (en) Virtual machine deployment method and related apparatus
US20200412637A1 (en) Systems and methods for implementing multi-part virtual network functions
WO2022193897A1 (zh) 一种业务的部署方法、装置及系统
KR100821401B1 (ko) 네트워크의 설계 및 기술을 위한 시스템 및 방법
JP5063726B2 (ja) 仮想ノード装置のコンフィグ制御方法
WO2021244483A1 (zh) 一种虚拟化的网络服务的部署方法及装置
WO2024093315A1 (zh) 一种针对多资源池网络的管理方法、云管理平台及装置
US12009998B1 (en) Core network support for application requested network service level objectives

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22770252

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022770252

Country of ref document: EP

Effective date: 20230906

NENP Non-entry into the national phase

Ref country code: DE