WO2021249432A1 - 网络自动化编排管理方法、实体、控制器及电子设备 - Google Patents

网络自动化编排管理方法、实体、控制器及电子设备 Download PDF

Info

Publication number
WO2021249432A1
WO2021249432A1 PCT/CN2021/099139 CN2021099139W WO2021249432A1 WO 2021249432 A1 WO2021249432 A1 WO 2021249432A1 CN 2021099139 W CN2021099139 W CN 2021099139W WO 2021249432 A1 WO2021249432 A1 WO 2021249432A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network element
parameters
configuration information
sdn
Prior art date
Application number
PCT/CN2021/099139
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
Application filed by 中国移动通信有限公司研究院, 中国移动通信集团有限公司 filed Critical 中国移动通信有限公司研究院
Publication of WO2021249432A1 publication Critical patent/WO2021249432A1/zh

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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • 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/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • 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/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • 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/0889—Techniques to speed-up the configuration process
    • 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

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a method, entity, controller, and electronic equipment for network automation orchestration management.
  • NFV Network Function Virtualization
  • NFVO Network Function Virtualization Orchestrator
  • the embodiments of the present disclosure provide a network automation orchestration management method, entity, controller, and electronic equipment to solve the problem of low configuration efficiency when performing network element network configuration.
  • the embodiments of the present disclosure provide a network automated orchestration management method for the network function virtualization orchestrator NFVO, including:
  • the network configuration information includes network parameters for the SDN controller to configure the network element.
  • the embodiments of the present disclosure provide a network automation orchestration management method for a software-defined network SDN controller, including:
  • the information and the networking relationship are obtained by NFVO analyzing the network service description NSD file corresponding to the network element type of the network element.
  • embodiments of the present disclosure provide an NFVO entity, the entity including a processor and a transceiver;
  • the processor is configured to parse the network service description NSD file of the network element corresponding to the network element type, determine the network relationship and network configuration information of the network element, and create a network instance according to the network relationship;
  • the transceiver is configured to send the network configuration information to a software-defined network SDN controller, where the network configuration information includes network parameters for the SDN controller to configure the network element.
  • an embodiment of the present disclosure provides an SDN controller, where the controller includes a processor and a transceiver;
  • the transceiver is configured to receive network configuration information sent by the network function virtualization orchestrator NFVO after creating a network instance according to the networking relationship of the network element, the network configuration information including information used for the SDN controller to configure the network element Network parameters, the network configuration information and the networking relationship are obtained by NFVO analyzing the network service description NSD file corresponding to the network element type of the network element;
  • the processor is configured to configure network parameters of the network element.
  • an NFVO entity including:
  • the parsing module is used to analyze the network service description NSD file of the network element corresponding to the network element type, and determine the networking relationship and network configuration information of the network element;
  • a creation module which is used to create a network instance according to the networking relationship
  • the sending module is configured to send the network configuration information to a software-defined network SDN controller, where the network configuration information includes network parameters for the SDN controller to configure the network element.
  • an SDN controller including:
  • the receiving module is configured to receive network configuration information sent by the network function virtualization orchestrator NFVO after creating a network instance according to the networking relationship of the network elements, the network configuration information including network parameters for the SDN controller to configure the network elements ,
  • the network configuration information and the networking relationship are obtained by NFVO analyzing the network service description NSD file corresponding to the network element type of the network element;
  • the configuration module is used to configure the network parameters of the network element.
  • an embodiment of the present disclosure provides an electronic device including a processor, a memory, and a computer program stored on the memory and capable of running on the processor.
  • the computer program is executed by the processor, The steps in the network automated orchestration management method as described in the first aspect are implemented, or, when the computer program is executed by the processor, the steps in the network automated orchestration management method as described in the second aspect are implemented.
  • embodiments of the present disclosure provide a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by the processor, the network as described in the first aspect is implemented.
  • the steps in the automated orchestration management method, or, when the computer program is executed by the processor, the steps in the network automated orchestration management method as described in the second aspect are implemented, or the computer program is executed by the processor When realizing the steps in the network automation orchestration management method as described in the third aspect.
  • the network relationships and network configuration information that need to be established for different types of network elements are pre-configured, and after the network relationships and network configuration information are parsed and determined, the SDN controller performs automatic configuration to achieve NFV and Efficient configuration of network element network parameters under the integration of SDN.
  • FIG. 1 is one of the flowcharts of a method for network automation orchestration management provided by an embodiment of the present disclosure
  • Figure 1a is a schematic diagram of a virtualization technology architecture provided by an embodiment of the present disclosure
  • FIG. 2 is the second flowchart of a network automated orchestration management method provided by an embodiment of the present disclosure
  • FIG. 3 is the third flowchart of a method for network automation orchestration management provided by an embodiment of the present disclosure
  • Figure 4 is a structural diagram of an NFVO entity provided by an embodiment of the present disclosure.
  • FIG. 5 is a structural diagram of an SDN controller provided by an embodiment of the present disclosure.
  • Fig. 6 is a structural diagram of another entity provided by an embodiment of the present disclosure.
  • FIG. 1 is a flowchart of a network automated orchestration management method provided by an embodiment of the present disclosure, which is used in a network function virtualization orchestrator (NFVO). As shown in FIG. 1, the network The automated orchestration management method includes the following steps:
  • Step 101 Analyze the network service description NSD file of the network element corresponding to the network element type, and determine the networking relationship and network configuration information of the network element.
  • the Network Service Description (NSD) file corresponds to the network element type of the network element.
  • NFVO can determine the network relationship and network configuration information of the network element by analyzing the NSD file corresponding to the network element type of the network element.
  • the networking relationship may include a network, a service link, etc., and the network configuration information includes network parameters used by a Software Defined Network (SDN) controller to configure the network element.
  • SDN Software Defined Network
  • the NSD file can include one or more network element information.
  • the NSD After NFVO reads and parses the NSD file to determine the network element requirements, the NSD will generate the configuration requirements of the virtual router (that is, vRouter), such as the information and requirements of the network elements linked to the vRouter
  • vRouter virtual router
  • the configured network element load-sharing routing information, dynamic routing configuration information between the network element and the gateway, etc.; at the same time, the dynamic routing configuration requirements of vRouter for external network routers, user routing configuration requirements, etc. will be generated in the NSD file.
  • Step 102 Create a network instance according to the networking relationship.
  • NFVO can create a network instance through a virtual infrastructure manager (Virtualized Infrastructure Manager, VIM) based on the NSD file.
  • VIM Virtualized Infrastructure Manager
  • Step 103 Send the network configuration information to the SDN controller, so that the SDN controller can configure the network parameters of the network element according to the network configuration information.
  • FIG. 1a shows the virtualization technology architecture provided for this application, including the SDN controller, the Virtualized Infrastructure Manager (VIM) is the key component of the fusion of NFV and SDN, and the VIM northbound docks with the NFV management orchestration system MANO.
  • VIM is connected to the SDN controller in the south direction, and the SDN controller takes care of other network equipment such as egress routers for network element network configuration and forwarding control.
  • NFVO parses the NSD file to determine the networking relationship and network configuration information of the network elements.
  • NFVO can create a network instance on the VIM based on the NSD file.
  • NFVO sends the network configuration information to the VIM.
  • the linkage of the two independent architectures of the NFV architecture and the SDN architecture is realized.
  • NFV virtualization technology
  • telecom network element functions are carried in the form of software on a unified resource pool to form a telecom cloud
  • SDN technology can realize centralized calculation of network routing through the SDN controller and deliver it to the network element to realize the network Smart scheduling.
  • the two are combined with each other and complement each other, and realize the softwareization, flexibility and automation of NFV network element network functions to a greater extent.
  • NFVO parses the network service description NSD file of the network element corresponding to the network element type, determines the network relationship and network configuration information of the network element; creates a network instance according to the network relationship;
  • the network configuration information is sent to the SDN controller, and the network configuration information includes network parameters for the SDN controller to configure the network element.
  • the SDN controller is used to automatically configure the network to achieve the integration of NFV and SDN. Efficient configuration of meta-network parameters.
  • the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.
  • NFVO can create a network instance on VIM based on the NSD file. Specifically, it can include the following steps:
  • vRouter According to the configuration requirements of the vRouter in the NSD file, create a vRouter in step c, and configure the vRouter in step c. In addition, you can also perform different configuration operations according to different network element requirements identified in the NSD file (described below). Configure vRouter.
  • Configuration information includes, but is not limited to, mounting NE network under vRouter, configuring NE load sharing routing information, configuring dynamic routing configuration information between NE and gateway, etc.; configuring dynamic routing of external network routers, configuring user routing, etc. at the same time.
  • the sending the network configuration information to the SDN controller specifically includes:
  • NFVO sends network configuration information to a Virtualized Infrastructure Manager (Virtualized Infrastructure Manager, VIM), which is transmitted to SDN through OpenStack native and extended interfaces, so that the SDN controller can configure the network parameters of the network element according to the network configuration information.
  • VIM Virtualized Infrastructure Manager
  • step 101 before parsing the network service description NSD file of the network element, and obtaining the networking relationship and network configuration information of the network element, the method further includes:
  • NSD file corresponding to the network element type of the network element is generated, and the NSD files corresponding to different network element types record different network parameters to be configured.
  • North-south communication demand information includes network element load sharing routing information, link detection requirements, dynamic routing configuration requirements between network elements and gateways, user routing configuration requirements, and whether the network elements share vRouter, etc.
  • NFVO can determine the network element type of the network element according to the north-south communication requirement information recorded in the Virtualised Network Function (VNF) package corresponding to the network element, so as to generate the corresponding NSD file according to the network element type.
  • VNF Virtualised Network Function
  • the operator can perform network service (Network Service, NS) design on NFVO, and NFVO generates NSD based on NS.
  • Network Service Network Service
  • Different network parameters can be configured according to different network element requirements identified in the NSD file.
  • the network parameters include at least one of the following parameters: route type, destination address, next hop address, and whether to enable link detection;
  • the network parameters include at least one of the following parameters: tenant, local subnet information, local AS number, opposite IP address information, opposite AS number, and, whether Route suppression
  • the network parameters include at least one of the following parameters: tenant, local network segment information, and opposite network segment information.
  • the extended static route is incrementally delivered on the Router.
  • the network parameters include at least one of the following parameters: routing type, destination address, next hop address, and whether to enable link detection.
  • the network parameters include at least one of the following parameters: tenant, local terminal network information, local AS number, opposite end IP address information, opposite end AS number, and whether to route suppression, etc.
  • a cross-router VPC connection interconnection is created, and the network parameters include at least one of the following parameters: tenant, local network segment information and pair End network segment information.
  • the network element type includes a first network element type and a second network element type
  • the network parameters to be configured recorded in the NSD file corresponding to the first network element type include static routing parameters between the SDN gateway and the external PE;
  • the network parameters to be configured recorded in the NSD file corresponding to the second network element type include static routing parameters between the SDN gateway and the external PE, the Border Gateway Protocol BGP routing parameters between the SDN gateway and the external PE, the SDN gateway and Static routing parameters between external VNFs, or BGP routing parameters between SDN gateways and VNFs.
  • the first network element type can be a main model interface
  • the second network element type can be a routing interface.
  • the first network element type and the second network element type correspond to different general network models and description methods, respectively.
  • the description method of the first network element type is: one or more virtual NICs (virtual NICs, vNIC for short, among which, network interface control
  • the network interface controller (NIC for short) shares an IP address, corresponding to the active/standby mode; the parameters that need to be configured on the network side are: static routing between the SDN gateway and the external PE.
  • the description of the second network element type is: multiple VMs share the IP, and reach the IP through one or more vNIC IP (load sharing); the parameters that need to be configured on the network side are: BGP or SDN gateway between the SDN gateway and the external PE Static routing with external PE; BGP between SDN gateway and VNF or static routing between SDN gateway and VNF.
  • the NSD file needs to add descriptions of four types of resources: BGP between SDN gateway and external PE, static routing between SDN gateway and external PE, BGP between SDN gateway and VNF, and static routing between SDN gateway and VNF.
  • BGP between SDN gateway and external PE and BGP between SDN gateway and VNF needs to include vRouter identifier, local IP address, local AS number, peer IP address, peer AS number, etc.
  • the description of the static route between the SDN gateway and the external PE needs to include the vRouter identifier, destination IP address, next hop IP address, route type, and whether to enable bidirectional forwarding detection (BFD), etc.
  • the description of the static route between the SDN gateway and the VNF needs to include the IP address corresponding to the external network of the VNF and whether it is load-sharing.
  • the network parameters to be configured recorded in the NSD file corresponding to the first network element type include static routing parameters between the SDN gateway and the external PE.
  • the network parameters to be configured recorded in the NSD file corresponding to the second network element type include static routing parameters between the SDN gateway and the external PE, the Border Gateway Protocol BGP routing parameters between the SDN gateway and the external PE, the SDN gateway and Static routing parameters between external VNFs, or BGP routing parameters between SDN gateways and VNFs.
  • the method after sending the network configuration information to the SDN, the method further includes:
  • NFVO initiates an application to create a network element to a virtual network function manager (English: virtualized network function manager, VNFM), and the VNFM parses a network element description file (Virtualised Network Function Descriptor, VNFD) to instantiate network element resources. After the network element resources are instantiated, the VNFM sends the configured Internet Protocol Address (IP) information of the virtual machine port to the NFVO.
  • VNFM virtualized network function manager
  • VNFD Virtualised Network Function Descriptor
  • IP Internet Protocol Address
  • NFVO generates the network element backhaul static route according to the virtual machine port IP address information reported by the VNFM, and sends it to the VIM.
  • the VIM sends it to the SDN controller, and the NFVO returns the network service creation to complete.
  • the way in which NFVO generates the backhaul static route of the network element is specifically as follows:
  • the port information includes the port IP address, the network element network where the port is located, and the UUID of the port instance. Determine whether the port is load-sharing and the IP address corresponding to the load-sharing by using the reported port information in the network element network field of the port and the description of the static route between the SDN gateway and the VNF in the NSD. If you need to configure load-sharing, The port IP address reported by the interface is used to determine the backhaul static route of the port. That is to say, in the case of determining that load sharing is required based on the virtual machine port IP address information and NSD, NFVO uses the virtual machine port IP address information Generate backhaul static routes for network elements.
  • the method proposed in this application can be applied to the instantiation process of the network service in the NFV and SDN convergence scenario, so as to realize the automatic opening and configuration of the NFV network element network, and improve the configuration efficiency of the network element network.
  • FIG. 2 is a flowchart of a method for network automation orchestration management provided by an embodiment of the present disclosure, which is used in a software defined network (Software Defined Network, SDN) controller.
  • SDN Software Defined Network
  • Step 201 Receive network configuration information sent by the network function virtualization orchestrator NFVO after creating a network instance according to the networking relationship of the network elements, where the network configuration information includes network parameters for the SDN controller to configure the network elements
  • the network configuration information and the networking relationship are obtained by NFVO analyzing the network service description NSD file corresponding to the network element type of the network element.
  • Step 202 Configure network parameters of the network element.
  • the Network Service Description (NSD) file corresponds to the network element type of the network element.
  • NFVO can determine the network relationship and network configuration information of the network element by analyzing the NSD file corresponding to the network element type of the network element.
  • the networking relationship may include networks, service links, etc., and the network configuration information includes network parameters used by the SDN controller to configure the network elements.
  • the NSD file can include one or more network element information.
  • the NSD After NFVO reads and parses the network element requirements, the NSD will generate the configuration requirements of the virtual router (that is, vRouter), such as the information of the network element linked to the vRouter and the network that needs to be configured. Meta load sharing routing information, dynamic routing configuration information between network elements and gateways, etc.; at the same time, the dynamic routing configuration requirements of vRouter for external network routers, user routing configuration requirements, etc. will be generated in the NSD file.
  • NFVO can create network instances through Virtualized Infrastructure Manager (VIM) based on NSD files.
  • VIP Virtualized Infrastructure Manager
  • the SDN receives network configuration information sent by NFVO after creating a network instance based on the networking relationship of the network elements, where the network configuration information includes network parameters for the SDN controller to configure the network elements, and
  • the network configuration information and the networking relationship are obtained by NFVO analyzing the network service description NSD file corresponding to the network element type of the network element; configuring the network parameters of the network element.
  • the network relationships and network configuration information that need to be established for different types of network elements are pre-configured, and these network relationships and network configuration information are determined through NFVO analysis.
  • the SDN controller realizes the automatic configuration of network parameters of the network elements according to the network configuration information. The efficient configuration of network element network parameters under the integration of NFV and SDN.
  • the network configuration information sent by the receiving network function virtualization orchestrator NFVO after creating a network instance according to the networking relationship of the network elements is specifically:
  • the virtual infrastructure manager VIM receives the network configuration information sent by the NFVO after the network instance is created based on the networking relationship of the network elements.
  • NFVO sends the network configuration information to the Virtualized Infrastructure Manager (VIM), which is transmitted to SDN through OpenStack native and extended interfaces, so that SDN can configure the network parameters of the network element according to the network configuration information.
  • VIP Virtualized Infrastructure Manager
  • the network element type includes a first network element type and a second network element type
  • the network parameters to be configured recorded in the NSD file corresponding to the first network element type include static routing parameters between the SDN gateway and the external PE;
  • the network parameters to be configured recorded in the NSD file corresponding to the second network element type include static routing parameters between the SDN gateway and the external PE, the Border Gateway Protocol BGP routing parameters between the SDN gateway and the external PE, the SDN gateway and Static routing parameters between external VNFs, or BGP routing parameters between SDN gateways and VNFs.
  • the first network element type can be a main model interface
  • the second network element type can be a routing interface.
  • the first network element type and the second network element type correspond to different general network models and description methods, respectively.
  • the description method of the first network element type is: one or more virtual NICs (virtual NICs, vNIC for short, among which, network interface control
  • the network interface controller (NIC for short) shares an IP address, corresponding to the active/standby mode; the parameters that need to be configured on the network side are: static routing between the SDN gateway and the external PE.
  • the description of the second network element type is: multiple VMs share the IP, and reach the IP through one or more vNIC IP (load sharing); the parameters that need to be configured on the network side are: BGP or SDN gateway between the SDN gateway and the external PE Static routing with external PE; BGP between SDN gateway and VNF or static routing between SDN gateway and VNF.
  • the NSD file needs to add descriptions of four types of resources: BGP between SDN gateway and external PE, static routing between SDN gateway and external PE, BGP between SDN gateway and VNF, and static routing between SDN gateway and VNF.
  • BGP between SDN gateway and external PE and BGP between SDN gateway and VNF needs to include vRouter identifier, local IP address, local AS number, peer IP address, peer AS number, etc.
  • the description of the static route between the SDN gateway and the external PE needs to include the vRouter identifier, destination IP address, next hop IP address, route type, and whether to enable bidirectional forwarding detection (BFD), etc.
  • the description of the static route between the SDN gateway and the VNF needs to include the IP address corresponding to the external network of the VNF and whether it is load-sharing.
  • the network parameters to be configured recorded in the NSD file corresponding to the first network element type include static routing parameters between the SDN gateway and the external PE.
  • the network parameters to be configured recorded in the NSD file corresponding to the second network element type include static routing parameters between the SDN gateway and the external PE, the Border Gateway Protocol BGP routing parameters between the SDN gateway and the external PE, the SDN gateway and Static routing parameters between external VNFs, or BGP routing parameters between SDN gateways and VNFs.
  • the method after receiving the network configuration information sent by the network function virtualization orchestrator NFVO after creating a network instance according to the networking relationship of the network elements, the method further includes:
  • the network element backhaul static route is generated by the NFVO based on the virtual machine port IP address information when the NFVO determines that load sharing is required based on the virtual machine port Internet Protocol IP address information and the NSD, so The virtual machine port IP address information is obtained by the NFVO after the virtual network function manager VNFM completes the instantiation of the network element.
  • the NFVO initiates an application to create a network element to a virtualized network function manager (Virtualized Network Function Manager, VNFM), and the VNFM parses a network element description file (Virtualised Network Function Descriptor, VNFD) to instantiate network element resources. After the network element resources are instantiated, the VNFM sends the configured Internet Protocol Address (IP) information of the virtual machine port to the NFVO.
  • VNFM Virtualized Network Function Manager
  • VNFD Virtualised Network Function Descriptor
  • NFVO generates the network element backhaul static route according to the virtual machine port IP address information reported by the VNFM, and sends it to the VIM.
  • the VIM sends it to the SDN controller, and the NFVO returns the network service creation to complete.
  • NFVO generates the backhaul static route of the network element
  • the port information includes the port IP address, the network element network where the port is located, and the UUID of the port instance. Determine whether the port is load-sharing and the IP address corresponding to the load-sharing by using the reported port information in the network element network field of the port and the description of the static route between the SDN gateway and the VNF in the NSD. If you need to configure load-sharing, The port IP address reported by the interface is used to determine the backhaul static route of the port.
  • NFVO uses the virtual machine port IP address information Generate the network element backhaul static route, and then send the network element backhaul static route to the SDN.
  • the method proposed in this application can be applied to the instantiation process of the network service in the NFV and SDN convergence scenario, so as to realize the automatic opening and configuration of the NFV network element network, and improve the configuration efficiency of the network element network.
  • the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.
  • NFVO can create a network instance on VIM based on the NSD file. Specifically, it can include the following steps:
  • vRouter According to the configuration requirements of the vRouter in the NSD file, create a vRouter in step c, and configure the vRouter in step c. In addition, you can also perform different configuration operations according to different network element requirements identified in the NSD file (described below). Configure vRouter.
  • Configuration information includes, but is not limited to, mounting NE network under vRouter, configuring NE load sharing routing information, configuring dynamic routing configuration information between NE and gateway, etc.; configuring dynamic routing of external network routers, configuring user routing, etc. at the same time.
  • the network parameters include at least one of the following parameters: route type, destination address, next hop address, and whether to enable link detection;
  • the network parameters include at least one of the following parameters: tenant, local subnet information, local autonomous system AS number, opposite IP address information, opposite AS number, and , Whether route suppression;
  • the network parameter includes at least one of the following parameters: tenant, local network segment information, and opposite network segment information.
  • the extended static route is incrementally delivered on the Router.
  • the network parameters include at least one of the following parameters: routing type, destination address, next hop address, and whether to enable link detection.
  • the network parameters include at least one of the following parameters: tenant, local terminal network information, local AS number, opposite end IP address information, opposite end AS number, and whether to route suppression, etc.
  • a cross-router VPC connection interconnection is created, and the network parameters include at least one of the following parameters: tenant, local network segment information and pair End network segment information.
  • FIG. 3 is a flowchart of a network automated orchestration management method provided by an embodiment of the application. As shown in Fig. 3, the steps of the network automated orchestration management method are as follows:
  • Step 11 NFVO receives the uploaded VNF network element package
  • Step 12 NFVO reads the north-south communication requirements of network elements from the VNF package (including network element load sharing routing information, link detection requirements, dynamic routing configuration requirements between network elements and gateways, user routing configuration requirements, and whether the network elements are shared vRouter, etc.), perform NSD design, generate network service description file NSD (NSD contains one or more network element information, after reading and analyzing network element requirements, NSD will generate vRouter configuration requirements, such as vRouter linked NE information, NE load sharing routing information that needs to be configured, dynamic routing configuration information between NEs and gateways, etc.; at the same time, the dynamic routing configuration requirements of vRouter for external network routers, user routing configuration requirements, etc. are generated.
  • NSD network service description file
  • vRouter configuration requirements such as vRouter linked NE information, NE load sharing routing information that needs to be configured, dynamic routing configuration information between NEs and gateways, etc.
  • Step 13 Initiate a network service instantiation process according to the selected NSD
  • Step 14 NFVO parses the network service description file NSD.
  • the NSD contains the north-south routing information of the network element, link detection requirements, user routing configuration requirements, etc. added in the embodiment of the present disclosure;
  • Step 15 NFVO creates an external network instance by going to VIM.
  • the network instance includes the network between network elements and subnets, vrouter, etc.; this step can include the following multiple steps:
  • Step 16 The NFVO issues network configuration parameters to the VIM, and the VIM transmits them to the SDN controller through the OpenStack native and extended interfaces; in this step, different configuration operations can be performed according to the needs of different network elements identified in the NSD.
  • the extended static route is issued incrementally on the Router, and the interface needs to include the route type, destination address, next hop address, and whether the link is enabled Testing, etc.;
  • the router and service network element BGP peer configuration and the peer configuration with external PE equipment are respectively issued on the Router.
  • the interface needs to include tenants, local subnet information, and local End AS number, peer IP address information, peer AS number, route suppression, etc.;
  • the interface needs to include tenants, local network segment information, and peer network segment information.
  • Step 17 The NFVO requests the VNFM to create a network element, and the VNFM parses the network element description file VNFD to instantiate the network element resources. After the network element resources are instantiated, the VNFM sends the configured virtual machine port IP address information to NFVO.
  • Step 18 The NFVO generates a backhaul static route for the network element according to the IP address information reported by the VNFM, and sends it to the VIM, which then sends it to the SDN controller.
  • Step 19 NFVO returns to the completion of the creation of the network service.
  • network elements can include two types of interfaces, host-type interfaces and routing-type interfaces, which correspond to different general network models and description methods respectively.
  • the network service description file NSD needs to add descriptions of four types of resources: BGP between SDN gateway and external PE, static routing between SDN gateway and external PE, BGP between SDN gateway and VNF, and static routing between SDN gateway and VNF.
  • BGP between SDN gateway and external PE and BGP between SDN gateway and VNF must include vRouter identifier, local IP address, local AS number, peer IP address, peer AS number, etc.
  • the description of the static route between the SDN gateway and the external PE needs to include the vRouter identifier, destination IP address, next hop IP address, route type, and whether to enable BFD, etc.
  • the description of the static route between the SDN gateway and the VNF needs to include the IP address corresponding to the external network of the VNF and whether it is load-sharing.
  • this application proposes a configuration method for backhaul static routing: adding port information to the original resource reporting interface.
  • the port information includes the port IP address, the network element network where the port is located, and the UUID of the port instance. Determine whether the port performs load sharing and the IP address corresponding to the load sharing based on the reported port information in the network element network field where the port is located, and the description of the static route between the SDN gateway and the VNF in the NSD. If you need to configure load balancing, then use the port IP address reported by the interface to determine the backhaul static route of the port.
  • the method proposed in this application can be applied to the instantiation process of the network service in the NFV and SDN convergence scenario, so as to realize the automatic opening and configuration of the NFV network element network, and improve the configuration efficiency of the network element network.
  • NFVO, VNFM, VIM, etc. can be deployed separately, or NFVO, VNFM, and VIM can be deployed on the same server.
  • FIG. 4 is a schematic structural diagram of an NFVO entity provided by an embodiment of the present disclosure.
  • the NFVO entity 400 includes:
  • the parsing module 401 is used to analyze the network service description NSD file of the network element corresponding to the network element type, and determine the networking relationship and network configuration information of the network element;
  • the creation module 402 is configured to create a network instance according to the networking relationship
  • the sending module 403 is configured to send the network configuration information to a software-defined network SDN controller, where the network configuration information includes network parameters for the SDN controller to configure the network element.
  • sending module 403 is also used for:
  • the network configuration information is sent to the SDN through the virtual infrastructure manager VIM.
  • the NFVO entity 400 also includes:
  • a determining module configured to determine the network element type of the network element according to the north-south communication demand information recorded in the virtual network function VNF package corresponding to the network element;
  • the first generating module is configured to generate NSD files corresponding to the network element types of the network elements, and different network parameters to be configured are recorded in the NSD files corresponding to different network element types.
  • the network element type includes a first network element type and a second network element type
  • the network parameters to be configured recorded in the NSD file corresponding to the first network element type include static routing parameters between the SDN gateway and the external PE;
  • the network parameters to be configured recorded in the NSD file corresponding to the second network element type include static routing parameters between the SDN gateway and the external PE, the Border Gateway Protocol BGP routing parameters between the SDN gateway and the external PE, the SDN gateway and Static routing parameters between external VNFs, or BGP routing parameters between SDN gateways and VNFs.
  • the NFVO entity 400 also includes:
  • the first receiving module is configured to receive the virtual machine port internet protocol IP address information of the network element sent by the virtual network function manager VNFM after the network element is instantiated;
  • the second generating module is configured to generate a network element backhaul static route according to the virtual machine port IP address information in the case of determining that load sharing is required according to the virtual machine port IP address information and the NSD;
  • the second sending module is configured to send the backhaul static route of the network element to the SDN controller.
  • the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.
  • the network parameters include at least one of the following parameters: route type, destination address, next hop address, and whether to enable link detection;
  • the network parameters include at least one of the following parameters: tenant, local subnet information, local autonomous system AS number, opposite IP address information, opposite AS number, and , Whether route suppression;
  • the network parameter includes at least one of the following parameters: tenant, local network segment information, and opposite network segment information.
  • the NFVO entity 400 can implement each process implemented by the NFVO entity in the method embodiment shown in FIG.
  • the NFVO entity 400 of the embodiment of the present disclosure parses the network service description NSD file of the network element corresponding to the network element type, determines the network relationship and network configuration information of the network element; creates a network instance according to the network relationship; sends The network configuration information is sent to the SDN controller, and the network configuration information includes network parameters for the SDN controller to configure the network element.
  • the SDN controller is used to automatically configure the network to achieve the integration of NFV and SDN. Efficient configuration of meta-network parameters.
  • FIG. 5 is a schematic structural diagram of an SDN controller provided by an embodiment of the present disclosure.
  • the SDN controller 500 includes:
  • the receiving module 501 is configured to receive network configuration information sent by the network function virtualization orchestrator NFVO after creating a network instance according to the networking relationship of the network element, the network configuration information including the network used by the SDN controller to configure the network element Parameters, the network configuration information and the networking relationship are obtained by NFVO analyzing the network service description NSD file corresponding to the network element type of the network element;
  • the configuration module 502 is used to configure the network parameters of the network element.
  • the receiving module 501 is used for:
  • the virtual infrastructure manager VIM receives the network configuration information sent by the NFVO after the network instance is created based on the networking relationship of the network elements.
  • the network element type includes a first network element type and a second network element type
  • the network parameters to be configured recorded in the NSD file corresponding to the first network element type include static routing parameters between the SDN gateway and the external PE;
  • the network parameters to be configured recorded in the NSD file corresponding to the second network element type include static routing parameters between the SDN gateway and the external PE, the Border Gateway Protocol BGP routing parameters between the SDN gateway and the external PE, the SDN gateway and Static routing parameters between external VNFs, or BGP routing parameters between SDN gateways and VNFs.
  • the SDN controller 500 further includes:
  • the second receiving module is configured to receive the backhaul static route of the network element, and the backhaul static route of the network element is determined by the NFVO according to the virtual machine port Internet Protocol IP address information and the NSD. Port IP address information is generated, and the virtual machine port IP address information is obtained by the NFVO after the virtual network function manager VNFM completes the instantiation of the network element.
  • the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.
  • the network parameters include at least one of the following parameters: route type, destination address, next hop address, and whether to enable link detection;
  • the network parameters include at least one of the following parameters: tenant, local subnet information, local autonomous system AS number, opposite IP address information, opposite AS number, and , Whether route suppression;
  • the network parameter includes at least one of the following parameters: tenant, local network segment information, and opposite network segment information.
  • the SDN controller 500 can implement each process implemented by the SDN controller in the method embodiment shown in FIG. 2. To avoid repetition, details are not described herein again.
  • the SDN controller 500 of the embodiment of the present disclosure receives network configuration information sent by NFVO after creating a network instance according to the networking relationship of the network elements, where the network configuration information includes the network used by the SDN controller to configure the network element
  • the parameters, the network configuration information and the networking relationship are obtained by NFVO analyzing the network service description NSD file corresponding to the network element type of the network element.
  • the NSD file of the network element is parsed by NFVO to obtain network configuration information, and the SDN controller 500 implements the automatic configuration of the network parameters of the network element according to the network configuration information, which improves the configuration efficiency of the network parameters of the network element.
  • an embodiment of the present disclosure also provides an entity, including a bus 601, a transceiver 602, an antenna 603, a bus interface 604, a processor 605, and a memory 606.
  • the entity is a network function virtualization orchestrator NFVO, and the entity includes a processor 605 and a transceiver 602;
  • the processor 605 is configured to parse the network service description NSD file of the network element corresponding to the network element type, determine the networking relationship and network configuration information of the network element, and create a network instance according to the networking relationship;
  • the transceiver 602 is configured to send the network configuration information to a software-defined network SDN controller, where the network configuration information includes network parameters for the SDN controller to configure the network element.
  • transceiver 602 is also used for:
  • the network configuration information is sent to the SDN controller through the virtual infrastructure manager VIM.
  • processor 605 is further configured to:
  • NSD file corresponding to the network element type of the network element is generated, and the NSD files corresponding to different network element types record different network parameters to be configured.
  • the network element type includes a first network element type and a second network element type
  • the network parameters to be configured recorded in the NSD file corresponding to the first network element type include static routing parameters between the SDN gateway and the external PE;
  • the network parameters to be configured recorded in the NSD file corresponding to the second network element type include static routing parameters between the SDN gateway and the external PE, the Border Gateway Protocol BGP routing parameters between the SDN gateway and the external PE, the SDN gateway and Static routing parameters between external VNFs, or BGP routing parameters between SDN gateways and VNFs.
  • transceiver 602 is further configured to: receive the virtual machine port Internet Protocol IP address information of the network element sent by the virtual network function manager VNFM after the network element is instantiated, and send the network element backhaul static state Route to SDN controller;
  • the processor 605 is further configured to generate a network element backhaul static route according to the virtual machine port IP address information when it is determined that load sharing is required according to the virtual machine port IP address information and the NSD.
  • the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.
  • the network parameters include at least one of the following parameters: route type, destination address, next hop address, and whether to enable link detection;
  • the network parameters include at least one of the following parameters: tenant, local subnet information, local autonomous system AS number, opposite IP address information, opposite AS number, and , Whether route suppression;
  • the network parameter includes at least one of the following parameters: tenant, local network segment information, and opposite network segment information.
  • the entity can implement each process implemented by NFVO in the method embodiment shown in FIG. 1. To avoid repetition, details are not described here.
  • the entity of this embodiment analyzes the network service description NSD file of the network element corresponding to the network element type, determines the network relationship and network configuration information of the network element; creates a network instance according to the network relationship; sends the network
  • the configuration information is sent to the SDN controller, and the network configuration information includes network parameters for the SDN controller to configure the network element.
  • the SDN controller is used to automatically configure the network to achieve the integration of NFV and SDN. Efficient configuration of meta-network parameters.
  • the entity when the entity is a software-defined network SDN, the entity includes a processor and a transceiver;
  • the transceiver 602 is configured to: receive network configuration information sent by the network function virtualization orchestrator NFVO after creating a network instance according to the networking relationship of the network element, the network configuration information including the network element configured by the SDN controller The network parameters of the network configuration information and the network relationship are obtained by NFVO analyzing the network service description NSD file corresponding to the network element type of the network element;
  • the processor 605 is configured to configure network parameters of the network element.
  • the transceiver 602 is further configured to receive, through the virtual infrastructure manager VIM, the network configuration information sent by the NFVO after the network instance is created according to the networking relationship of the network elements.
  • the network element type includes a first network element type and a second network element type
  • the network parameters to be configured recorded in the NSD file corresponding to the first network element type include static routing parameters between the SDN gateway and the external PE;
  • the network parameters to be configured recorded in the NSD file corresponding to the second network element type include static routing parameters between the SDN gateway and the external PE, the Border Gateway Protocol BGP routing parameters between the SDN gateway and the external PE, the SDN gateway and Static routing parameters between external VNFs, or BGP routing parameters between SDN gateways and VNFs.
  • transceiver 602 is also used for:
  • the network element backhaul static route is generated by the NFVO based on the virtual machine port IP address information when the NFVO determines that load sharing is required based on the virtual machine port Internet Protocol IP address information and the NSD, so The virtual machine port IP address information is obtained by the NFVO after the virtual network function manager VNFM completes the instantiation of the network element.
  • the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.
  • the network parameters include at least one of the following parameters: route type, destination address, next hop address, and whether to enable link detection;
  • the network parameters include at least one of the following parameters: tenant, local subnet information, local autonomous system AS number, opposite IP address information, opposite AS number, and , Whether route suppression;
  • the network parameter includes at least one of the following parameters: tenant, local network segment information, and opposite network segment information.
  • the entity can implement each process implemented by the SDN in the method embodiment shown in FIG. 2, and in order to avoid repetition, details are not repeated here.
  • the entity in this embodiment receives network configuration information sent by NFVO after creating a network instance based on the networking relationship of the network element, where the network configuration information includes network parameters used by the SDN controller to configure the network element, and The network configuration information and the networking relationship are obtained by NFVO analyzing the network service description NSD file corresponding to the network element type of the network element.
  • the NSD file of the network element is parsed by NFVO to obtain network configuration information, and the SDN controller 500 implements the automatic configuration of the network parameters of the network element according to the network configuration information, which improves the configuration efficiency of the network parameters of the network element.
  • bus architecture represented by bus 601
  • bus 601 can include any number of interconnected buses and bridges
  • bus 601 will include one or more processors represented by processor 605 and memory represented by memory 606
  • the various circuits are linked together.
  • the bus 601 can also link various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further description will be given herein.
  • the bus interface 604 provides an interface between the bus 601 and the transceiver 602.
  • the transceiver 602 may be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on the transmission medium.
  • the data processed by the processor 605 is transmitted on the wireless medium through the antenna 603, and further, the antenna 603 also receives the data and transmits the data to the processor 605.
  • the processor 605 is responsible for managing the bus 601 and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 606 may be used to store data used by the processor 605 when performing operations.
  • the processor 605 may be a CPU, ASIC, FPGA or CPLD.
  • an embodiment of the present disclosure further provides an electronic device, including a processor 605, a memory 606, a computer program stored on the memory 606 and running on the processor 605, and the computer program is executed by the processor 605
  • an electronic device including a processor 605, a memory 606, a computer program stored on the memory 606 and running on the processor 605, and the computer program is executed by the processor 605
  • the processes of any one of the network automated orchestration management method embodiments in FIG. 1 to FIG. 2 can be realized at a time, and the same technical effect can be achieved. In order to avoid repetition, details are not repeated here.
  • the embodiment of the present disclosure also provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the computer program is executed by a processor, the automatic network arrangement management shown in any one of FIGS. 1 to 2 is realized.
  • Each process of the method embodiment can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the computer-readable storage medium such as ROM, RAM, magnetic disk or optical disk, etc.
  • modules, units, sub-modules, sub-units, etc. can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (Digital Signal Processing, DSP), digital signal processing equipment ( DSP Device, DSPD), Programmable Logic Device (PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, Other electronic units or combinations thereof that perform the functions described in the present disclosure.
  • ASICs application specific integrated circuits
  • DSP Digital Signal Processing
  • DSP Device digital signal processing equipment
  • PLD Programmable Logic Device
  • Field-Programmable Gate Array Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • the technical solution of the present disclosure essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present disclosure.
  • a terminal which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开提供一种网络自动化编排管理方法、实体、控制器及电子设备，该网络自动化编排管理方法包括：NFVO解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息；根据所述组网关系创建网络实例；发送所述网络配置信息到SDN控制器，网络配置信息包括用于SDN控制器配置所述网元的网络参数。

Description

网络自动化编排管理方法、实体、控制器及电子设备
相关申请的交叉引用
本申请主张在2020年6月11日在中国提交的中国专利申请号No.202010530056.3的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种网络自动化编排管理方法、实体、控制器及电子设备。
背景技术
随着虚拟化技术的飞速发展，在通用的物理设备上，实现网络中专用的网元设备的功能的网络功能虚拟化(Network Function Virtualization，NFV)逐渐受到人们的重视。
在NFV系统中，网络功能虚拟化编排器(Network Function Virtualization Orchestrator，NFVO)作为业务编排的核心，用于进行NFV网络的生命周期管理，实现网络的快速部署等。
目前，NFVO在进行网元网络配置时，由于需要人工参与的原因，导致配置效率低。
发明内容
本公开实施例提供一种网络自动化编排管理方法、实体、控制器及电子设备，以解决进行网元网络配置时，配置效率低的问题。
为解决上述技术问题，本公开是这样实现的：
第一方面，本公开实施例提供了一种网络自动化编排管理方法，用于网络功能虚拟化编排器NFVO，包括：
解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息；
根据所述组网关系创建网络实例；
发送所述网络配置信息到软件定义网络SDN控制器，所述网络配置信息包括用于所述SDN控制器配置所述网元的网络参数。
第二方面，本公开实施例提供一种网络自动化编排管理方法，用于软件定义网络SDN控制器，包括：
接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得。
第三方面，本公开实施例提供一种NFVO实体，所述实体包括处理器和收发机；
所述处理器用于，解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息，并根据所述组网关系创建网络实例；
所述收发机，用于发送所述网络配置信息到软件定义网络SDN控制器，所述网络配置信息包括用于所述SDN控制器配置所述网元的网络参数。
第四方面，本公开实施例提供一种SDN控制器，所述控制器包括处理器和收发机；
所述收发机用于：接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得；
所述处理器，用于配置所述网元的网络参数。
第五方面，本公开实施例提供一种NFVO实体，包括：
解析模块，用于解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息；
创建模块，用于根据所述组网关系创建网络实例；
发送模块，用于发送所述网络配置信息到软件定义网络SDN控制器，所述网络配置信息包括用于所述SDN控制器配置所述网元的网络参数。
第六方面，本公开实施例提供一种SDN控制器，包括：
接收模块，用于接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得；
配置模块，用于配置所述网元的网络参数。
第七方面，本公开实施例提供一种电子设备，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如第一方面所述的网络自动化编排管理方法中的步骤，或者，所述计算机程序被所述处理器执行时实现如第二方面所述的网络自动化编排管理方法中的步骤。
第八方面，本公开实施例提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被所述处理器执行时实现如第一方面所述的网络自动化编排管理方法中的步骤，或者，所述计算机程序被所述处理器执行时实现如第二方面所述的网络自动化编排管理方法中的步骤，或者，所述计算机程序被所述处理器执行时实现如第三方面所述的网络自动化编排管理方法中的步骤。
本公开实施例中，通过预先配置不同类型的网元需要建立的网络关系及网络配置信息，并在解析确定这些网络关系及网络配置信息之后，通过SDN控制器进行自动的配置，实现了NFV和SDN的融合下的网元网络参数的高效配置。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本公开实施例提供的一种网络自动化编排管理方法的流程图之一；
图1a是本公开实施例提供的一种虚拟化技术架构的示意图；
图2是本公开实施例提供的一种网络自动化编排管理方法的流程图之二；
图3是本公开实施例提供的一种网络自动化编排管理方法的流程图之三；
图4是本公开实施例提供的一种NFVO实体的结构图；
图5是本公开实施例提供的一种SDN控制器的结构图；
图6是本公开实施例提供的另一种实体的结构图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
以下对本公开具体实施例进行进一步的详细说明。
参见图1，图1是本公开实施例提供的一种网络自动化编排管理方法的流程图，用于网络功能虚拟化编排器(network function virtualization orchestrator，NFVO)，如图1所示，所述网络自动化编排管理方法包括以下步骤：
步骤101、解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息。
网络服务描述(Network Service Description，NSD)文件与网元的网元类型对应，NFVO通过解析网元的与网元类型对应的NSD文件，可确定网元的组网关系和网络配置信息，其中，组网关系可包括网络、业务链路等等，网络配置信息包括用于软件定义网络(Software Defined Network，SDN)控制器配置所述网元的网络参数。
NSD文件可包括一个或多个网元信息，NFVO在读取并解析NSD文件确定网元需求后，NSD中会生成虚拟路由器(即vRouter)的配置需求，如vRouter下所挂网元信息、需要配置的网元负载分担路由信息、网元和网关之间动态路由配置信息等；同时NSD文件中会生成vRouter对外部网络路由器的动态路由配置需求、用户路由配置需求等。
步骤102、根据所述组网关系创建网络实例。
具体的，NFVO可基于NSD文件通过虚拟基础设施管理器(Virtualized  Infrastructure Manager，VIM)创建网络实例。
步骤103、发送所述网络配置信息到SDN控制器，使得SDN控制器可根据网络配置信息来配置网元的网络参数。
图1a所示为本申请提供的虚拟化技术架构，包括SDN控制器，虚拟基础设施管理器(Virtualized Infrastructure Manager，VIM)为NFV和SDN融合的关键组件，VIM北行对接NFV管理编排系统MANO，VIM南向对接SDN控制器，由SDN控制器纳管出口路由器等其他网络设备，进行网元网络配置和转发控制。
图1a中，NFVO解析NSD文件，确定所述网元的组网关系和网络配置信息，NFVO可基于所述NSD文件在VIM上创建网络实例，同时，NFVO将网络配置信息发送给VIM，由VIM通过OpenStack原生及扩展接口传给SDN控制器，使得SDN控制器可根据网络配置信息来配置网元的网络参数。
本实施例中，实现了NFV架构和SDN架构两个独立架构的联动。通过虚拟化技术(NFV)，电信网元功能以软件形式承载在统一资源池上形成电信云，而SDN技术则能通过SDN控制器实现网络路由的集中计算，并下发至网元，从而实现网络的智能调度。二者相互结合，相互补充，更大程度的实现了NFV网元网络功能软件化、灵活化、自动化。
同时，本实施例中，NFVO解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息；根据所述组网关系创建网络实例；发送所述网络配置信息到SDN控制器，网络配置信息包括用于SDN控制器配置所述网元的网络参数。通过预先配置不同类型的网元需要建立的网络关系及网络配置信息，并在解析确定这些网络关系及网络配置信息之后，通过SDN控制器进行自动的配置，实现了NFV和SDN的融合下的网元网络参数的高效配置。
在本申请一个实施例中，所述网络实例包括网元间网络、子网和虚拟路由器中的至少一个。
NFVO可基于所述NSD文件在VIM上创建网络实例，具体的，可包括如下步骤：
a使用Openstack社区接口Post/v2.0/subnets创建Network；
b.使用Openstack社区接口Post/v2.0/subnets创建Subnet；
c.使用VIM增强接口Post/v2.0/routers，PUT/v2.0/routers/{router_id}创建Router，可选配置原生静态路由；
d.用Openstck社区接口PUT/v2.0/routers/{router_id}/add_router_interface，将Subnet加入到Router。
根据NSD文件中对vRouter的配置需求，在c步骤创建vRouter，在c步骤对vRouter进行配置，另外，还可根据NSD文件中标识的不同的网元需求进行不同的配置操作(如下文介绍)来对vRouter进行配置。
配置信息包括但不限于在vRouter下挂载网元网络、配置网元负载分担路由信息、配置网元和网关之间动态路由配置信息等；同时配置外部网络路由器的动态路由、配置用户路由等。
在本申请一个实施例中，所述发送所述网络配置信息到SDN控制器具体为：
通过VIM发送所述网络配置信息到所述SDN控制器。
NFVO将网络配置信息发送给虚拟基础设施管理器(Virtualized Infrastructure Manager，VIM)，由VIM通过OpenStack原生及扩展接口传给SDN，使得SDN控制器可根据网络配置信息来配置网元的网络参数。
在本申请一个实施例中，在步骤101、解析网元的网络服务描述NSD文件，获取所述网元的组网关系和网络配置信息之前，还包括：
根据所述网元对应的虚拟网络功能VNF包中记录的南北向通信需求信息确定所述网元的网元类型；
生成与所述网元的网元类型对应的NSD文件，不同网元类型对应的NSD文件中记录有不同的待配置的网络参数。
南北向通信需求信息包括网元负载分担路由信息、链路检测需求、网元和网关之间动态路由配置需求、用户路由配置需求、网元是否共用vRouter等。
NFVO可根据网元对应的虚拟网络功能(Virtualised Network Function，VNF)包中记录的南北向通信需求信息，来确定网元的网元类型，以根据网元类型来生成对应的NSD文件。例如，可由操作员在NFVO上进行网络业务 (Network Service，NS)设计，NFVO基于NS生成NSD。可根据NSD文件中标识的不同的网元需求对网络参数进行不同的配置操作。
在本申请一个实施例中，在所述网元需要配置静态路由的情况下，网络参数包括如下参数中的至少一个：路由类型、目的地址、下一跳地址、是否启用链路检测；
或
在所述网元采用BGP动态路由协议的情况下，网络参数包括如下参数中的至少一个：租户、本端子网信息、本端AS号、对端IP地址信息、对端AS号，和，是否路由抑制；
或
在所述网元存在跨VPC互访需求的情况下，网络参数包括如下参数中的至少一个：租户、本端网段信息和对端网段信息。
在所述网元需要配置静态路由的情况下，例如，配置UE地址静态路由，则在Router上增量下发扩展静态路由。网络参数包括如下参数中的至少一个：路由类型、目的地址、下一跳地址、是否启用链路检测。
在所述网元采用边界网关协议(Border Gateway Protocol，BGP)动态路由协议的情况下，则在Router上分别下发Router、业务网元BGP对等体配置以及和外部PE设备的对等体配置，网络参数包括如下参数中的至少一个：租户、本端子网信息、本端AS号、对端IP地址信息、对端AS号和是否路由抑制等。
在所述网元存在跨私有网络(VirtualPrivateCloud，VPC)互访需求的情况下，则创建跨Router间的VPC Connecntion互联，网络参数包括如下参数中的至少一个：租户、本端网段信息和对端网段信息。
在本申请一个实施例中，所述网元类型包括第一网元类型和第二网元类型；
所述第一网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数；
所述第二网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数，SDN网关和外部PE之间的边界 网关协议BGP路由参数，SDN网关和外部VNF之间的静态路由参数，或，SDN网关和VNF之间的BGP路由参数。
第一网元类型可为主机型接口，第二网元类型可为路由型接口。第一网元类型和第二网元类型分别对应不同的网络通用模型和描述方式，第一网元类型的描述方式为：一个或多个虚拟NIC(virtual NICs，简称vNIC，其中，网络接口控制器(network interface controller，简称NIC))共享一个IP地址，对应主备方式；网络侧需配置的参数为：SDN网关和外部PE间静态路由。第二网元类型的描述方式为：多个VM共享该IP，通过一个或多个vNIC IP(负荷分担)到达该IP；网络侧需配置的参数为：SDN网关和外部PE间BGP或SDN网关和外部PE间静态路由；SDN网关和VNF间BGP或SDN网关和VNF间的静态路由。
NSD文件中需增加SDN网关和外部PE间BGP、SDN网关和外部PE间静态路由、SDN网关和VNF间BGP、SDN网关和VNF间的静态路由四类资源的描述。
其中，SDN网关和外部PE间BGP、SDN网关和VNF间BGP的描述需包含vRouter标识符、本端IP地址、本端AS号、对端IP地址、对端AS号等。
SDN网关和外部PE间静态路由的描述需包含vRouter标识符、目的IP地址、下一跳IP地址、路由类型、是否使能双向转发检测(Bidirectional Forwarding Detection，BFD)等。
SDN网关和VNF间的静态路由的描述需包含VNF外部网络对应的IP地址、是否负载分担。
所述第一网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数。所述第二网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数，SDN网关和外部PE之间的边界网关协议BGP路由参数，SDN网关和外部VNF之间的静态路由参数，或，SDN网关和VNF之间的BGP路由参数。
在本申请一个实施例中，发送所述网络配置信息到SDN之后，还包括：
接收虚拟网络功能管理器VNFM在网元实例化完成后，发送的所述网元 的虚拟机端口IP地址信息；
在根据所述虚拟机端口互联网协议IP地址信息和NSD判断需要负载分担的情况下，根据所述虚拟机端口IP地址信息生成网元回程静态路由；
发送所述网元回程静态路由到SDN控制器。
NFVO向虚拟网络功能管理器(英文：virtualized network function manager，VNFM)发起创建网元的申请，VNFM解析网元描述文件(Virtualised Network Function Descriptor，VNFD)，进行网元资源实例化。网元资源实例化完成后，VNFM将已配置好的虚拟机端口互联网协议地址(Internet Protocol Address，IP)信息发送给NFVO。
NFVO根据VNFM上报的虚拟机端口IP地址信息，生成网元回程静态路由，并下发给VIM，由VIM下发给SDN控制器，NFVO返回网络服务创建完成。其中，NFVO生成网元回程静态路由的方式，具体为：
在原有资源上报接口中，增加端口信息。端口信息包含端口IP地址、端口所在网元网络、端口实例的UUID。通过上报的端口信息中端口所在网元网络字段，及NSD中SDN网关和VNF间的静态路由的描述，来确定该端口是否进行负载分担及负载分担所对应的IP地址，如果需要配置负载分担，则通过接口上报的端口IP地址来确定端口的回程静态路由，也就是说，在根据所述虚拟机端口IP地址信息和NSD判断需要负载分担的情况下，NFVO根据所述虚拟机端口IP地址信息生成网元回程静态路由。
本申请提出的方法可应用在NFV和SDN融合场景中网络服务的实例化流程，从而实现NFV网元网络的自动化开通和配置，提高网元网络的配置效率。
参见图2，图2是本公开实施例提供的一种网络自动化编排管理方法的流程图，用于软件定义网络(Software Defined Network，SDN)控制器，如图2所示，所述网络自动化编排管理方法包括以下步骤：
步骤201、接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，其中，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得。
步骤202，配置所述网元的网络参数。
网络服务描述(Network Service Description，NSD)文件与网元的网元类型对应，NFVO通过解析网元的与网元类型对应的NSD文件，可确定网元的组网关系和网络配置信息，其中，组网关系可包括网络、业务链路等等，网络配置信息包括用于SDN控制器配置所述网元的网络参数。
NSD文件可包括一个或多个网元信息，NFVO在读取并解析网元需求后，NSD中会生成虚拟路由器(即vRouter)的配置需求，如vRouter下所挂网元信息、需要配置的网元负载分担路由信息、网元和网关之间动态路由配置信息等；同时NSD文件中会生成vRouter对外部网络路由器的动态路由配置需求、用户路由配置需求等。
NFVO可基于NSD文件通过虚拟基础设施管理器(Virtualized Infrastructure Manager，VIM)创建网络实例。
本实施例中，SDN接收NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，其中，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得；配置所述网元的网络参数。通过预先配置不同类型的网元需要建立的网络关系及网络配置信息，通过NFVO解析确定这些网络关系及网络配置信息，由SDN控制器根据网络配置信息来实现网元的网络参数的自动化配置，实现了NFV和SDN的融合下的网元网络参数的高效配置。
在本申请一个实施例中，所述接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息具体为：
通过虚拟基础设施管理器VIM接收NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息。
NFVO将网络配置信息发送给虚拟基础设施管理器(Virtualized Infrastructure Manager，VIM)，由VIM通过OpenStack原生及扩展接口传给SDN，使得SDN可根据网络配置信息来配置网元的网络参数。
在本申请一个实施例中，所述网元类型包括第一网元类型和第二网元类型；
所述第一网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数；
所述第二网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数，SDN网关和外部PE之间的边界网关协议BGP路由参数，SDN网关和外部VNF之间的静态路由参数，或，SDN网关和VNF之间的BGP路由参数。
具体的，不同网元类型对应的NSD文件中记录有不同的待配置的网络参数。第一网元类型可为主机型接口，第二网元类型可为路由型接口。第一网元类型和第二网元类型分别对应不同的网络通用模型和描述方式，第一网元类型的描述方式为：一个或多个虚拟NIC(virtual NICs，简称vNIC，其中，网络接口控制器(network interface controller，简称NIC))共享一个IP地址，对应主备方式；网络侧需配置的参数为：SDN网关和外部PE间静态路由。第二网元类型的描述方式为：多个VM共享该IP，通过一个或多个vNIC IP(负荷分担)到达该IP；网络侧需配置的参数为：SDN网关和外部PE间BGP或SDN网关和外部PE间静态路由；SDN网关和VNF间BGP或SDN网关和VNF间的静态路由。
NSD文件中需增加SDN网关和外部PE间BGP、SDN网关和外部PE间静态路由、SDN网关和VNF间BGP、SDN网关和VNF间的静态路由四类资源的描述。
其中，SDN网关和外部PE间BGP、SDN网关和VNF间BGP的描述需包含vRouter标识符、本端IP地址、本端AS号、对端IP地址、对端AS号等。
SDN网关和外部PE间静态路由的描述需包含vRouter标识符、目的IP地址、下一跳IP地址、路由类型、是否使能双向转发检测(Bidirectional Forwarding Detection，BFD)等。
SDN网关和VNF间的静态路由的描述需包含VNF外部网络对应的IP地址、是否负载分担。
所述第一网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数。所述第二网元类型对应的NSD文 件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数，SDN网关和外部PE之间的边界网关协议BGP路由参数，SDN网关和外部VNF之间的静态路由参数，或，SDN网关和VNF之间的BGP路由参数。
在本申请一个实施例中，在所述接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息之后，还包括：
接收网元回程静态路由，所述网元回程静态路由由所述NFVO在根据虚拟机端口互联网协议IP地址信息和NSD判断需要负载分担的情况下，根据所述虚拟机端口IP地址信息生成，所述虚拟机端口IP地址信息由所述NFVO在虚拟网络功能管理器VNFM完成网元实例化后获得。
NFVO向虚拟网络功能管理器(Virtualized Network Function Manager，VNFM)发起创建网元的申请，VNFM解析网元描述文件(Virtualised Network Function Descriptor，VNFD)，进行网元资源实例化。网元资源实例化完成后，VNFM将已配置好的虚拟机端口互联网协议地址(Internet Protocol Address，IP)信息发送给NFVO。
NFVO根据VNFM上报的虚拟机端口IP地址信息，生成网元回程静态路由，并下发给VIM，由VIM下发给SDN控制器，NFVO返回网络服务创建完成。
其中，NFVO生成网元回程静态路由的方式，具体为：
在原有资源上报接口中，增加端口信息。端口信息包含端口IP地址、端口所在网元网络、端口实例的UUID。通过上报的端口信息中端口所在网元网络字段，及NSD中SDN网关和VNF间的静态路由的描述，来确定该端口是否进行负载分担及负载分担所对应的IP地址，如果需要配置负载分担，则通过接口上报的端口IP地址来确定端口的回程静态路由，也就是说，在根据所述虚拟机端口IP地址信息和NSD判断需要负载分担的情况下，NFVO根据所述虚拟机端口IP地址信息生成网元回程静态路由，然后将网元回程静态路由发送给SDN。
本申请提出的方法可应用在NFV和SDN融合场景中网络服务的实例化流程，从而实现NFV网元网络的自动化开通和配置，提高网元网络的配置效率。
在本申请一个实施例中，所述网络实例包括网元间网络、子网和虚拟路由器中的至少一个。NFVO可基于所述NSD文件在VIM上创建网络实例，具体的，可包括如下步骤：
a使用Openstack社区接口Post/v2.0/subnets创建Network；
b.使用Openstack社区接口Post/v2.0/subnets创建Subnet；
c.使用VIM增强接口Post/v2.0/routers，PUT/v2.0/routers/{router_id}创建Router，可选配置原生静态路由；
d.用Openstck社区接口PUT/v2.0/routers/{router_id}/add_router_interface，将Subnet加入到Router；
根据NSD文件中对vRouter的配置需求，在c步骤创建vRouter，在c步骤对vRouter进行配置，另外，还可根据NSD文件中标识的不同的网元需求进行不同的配置操作(如下文介绍)来对vRouter进行配置。
配置信息包括但不限于在vRouter下挂载网元网络、配置网元负载分担路由信息、配置网元和网关之间动态路由配置信息等；同时配置外部网络路由器的动态路由、配置用户路由等。
在本申请一个实施例中，在所述网元需要配置静态路由的情况下，网络参数包括如下参数中的至少一个：路由类型、目的地址、下一跳地址和是否启用链路检测；
或，
在所述网元采用BGP动态路由协议的情况下，网络参数包括如下参数中的至少一个：租户、本端子网信息、本端自治系统AS号、对端IP地址信息、对端AS号，和，是否路由抑制；
或，
在所述网元存在跨私有网络VPC互访需求的情况下，网络参数包括如下参数中的至少一个：租户、本端网段信息和对端网段信息。
在所述网元需要配置静态路由的情况下，例如，配置UE地址静态路由，则在Router上增量下发扩展静态路由。网络参数包括如下参数中的至少一个：路由类型、目的地址、下一跳地址、是否启用链路检测。
在所述网元采用边界网关协议(Border Gateway Protocol，BGP)动态路由 协议的情况下，则在Router上分别下发Router、业务网元BGP对等体配置以及和外部PE设备的对等体配置，网络参数包括如下参数中的至少一个：租户、本端子网信息、本端AS号、对端IP地址信息、对端AS号和是否路由抑制等。
在所述网元存在跨私有网络(VirtualPrivateCloud，VPC)互访需求的情况下，则创建跨Router间的VPC Connecntion互联，网络参数包括如下参数中的至少一个：租户、本端网段信息和对端网段信息。
以下对本申请提供的网络自动化编排管理方法的详细过程进行举例说明。图3为本申请一实施例提供的网络自动化编排管理方法的流程图，如图3所示，网络自动化编排管理方法的步骤如下：
步骤11、NFVO接收上载的VNF网元包；
步骤12、NFVO从VNF包中读取网元南北向通信需求(包括网元负载分担路由信息、链路检测需求、网元和网关之间动态路由配置需求、用户路由配置需求、网元是否共用vRouter等)，进行NSD设计，生成网络服务描述文件NSD(NSD中包含一个或多个网元信息，在读取并解析网元需求后，NSD中会生成vRouter的配置需求，比如vRouter下所挂网元信息、需要配置的网元负载分担路由信息、网元和网关之间动态路由配置信息等；同时生成vRouter对外部网络路由器的动态路由配置需求、用户路由配置需求等)。
步骤13、根据选择的NSD并发起网络服务实例化流程；
步骤14、NFVO解析网络服务描述文件NSD，NSD中包含了本公开实施例增加的网元南北向路由信息、链路检测需求、用户路由配置需求等等；
步骤15、NFVO通过到VIM创建外部网络实例，网络实例包含网元间网络及子网、vrouter等；本步骤可包含如下多步：
使用Openstack社区接口Post/v2.0/subnets创建Network；
使用Openstack社区接口Post/v2.0/subnets创建Subnet；
使用VIM增强接口Post/v2.0/routers，PUT/v2.0/routers/{router_id}创建Router，可选配置原生静态路由；
使用Openstck社区接口PUT/v2.0/routers/{router_id}/add_router_interface，将Subnet加入到Router。
步骤16、NFVO下发网络配置参数给VIM，由VIM通过OpenStack原生及扩展接口传给SDN控制器；本步骤可根据NSD中标识的不同的网元需求进行不同的配置操作。
例如，如果网元需配置静态路由(例如需配置UE地址静态路由)，则在Router上增量下发扩展静态路由，接口中需包含路由类型、目的地址、下一跳地址、是否启用链路检测等；
如果网元采用了BGP动态路由协议，则在Router上分别下发Router和业务网元BGP对等体配置以及和外部PE设备的对等体配置，接口中需包含租户、本端子网信息、本端AS号、对端IP地址信息、对端AS号、是否路由抑制等；
如果网元间存在跨VPC互访需求，则创建跨Router间的VPC Connecntion互联，接口中需包含租户、本端网段信息、对端网段信息等。
步骤17、NFVO请求VNFM创建网元，VNFM解析网元描述文件VNFD，进行网元资源实例化。网元资源实例化完成后，VNFM将已配置好的虚拟机端口IP地址信息发送给NFVO。
步骤18、NFVO根据VNFM上报的IP地址信息，生成网元回程静态路由，并下发给VIM，由VIM下发给SDN控制器。
步骤19、NFVO返回网络服务创建完成。
针对步骤12中提到的网络服务描述文件NSD，本申请还提出了一种网元网络通用模型及描述方式。如表1所示，网元可包含两类接口，主机型接口和路由型接口，两类接口分别对应不同的网络通用模型和描述方式。
表1
Figure PCTCN2021099139-appb-000001
Figure PCTCN2021099139-appb-000002
网络服务描述文件NSD中需增加SDN网关和外部PE间BGP、SDN网关和外部PE间静态路由、SDN网关和VNF间BGP、SDN网关和VNF间的静态路由四类资源的描述。
SDN网关和外部PE间的BGP和SDN网关和VNF间BGP的描述需包含vRouter标识符、本端IP地址、本端AS号、对端IP地址、对端AS号等。
SDN网关和外部PE间静态路由的描述需包含vRouter标识符、目的IP地址、下一跳IP地址、路由类型、是否使能BFD等。
SDN网关和VNF间的静态路由的描述需包含VNF外部网络对应的IP地址、是否负载分担。
针对步骤16，本申请提出了一种回程静态路由的配置方式：在原有资源上报接口中，增加端口信息。端口信息包含端口IP地址、端口所在网元网络、端口实例的UUID。通过上报的端口信息中端口所在网元网络字段，及NSD中SDN网关和VNF间的静态路由的描述，来确定该端口是否进行负载分担及负载分担所对应的IP地址。如果需要配置负载分担，再通过接口上报的端口IP地址来确定端口的回程静态路由。
本申请提出的方法可应用在NFV和SDN融合场景中网络服务的实例化流程，从而实现NFV网元网络的自动化开通和配置，提高网元网络的配置效率。
NFVO、VNFM、VIM等可以单独部署，也可以是NFVO、VNFM、VIM部署于同一服务器。
参见图4，图4是本公开实施例提供的一种NFVO实体的结构示意图，如图4所示，NFVO实体400包括：
解析模块401，用于解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息；
创建模块402，用于根据所述组网关系创建网络实例；
发送模块403，用于发送所述网络配置信息到软件定义网络SDN控制器，所述网络配置信息包括用于所述SDN控制器配置所述网元的网络参数。
进一步的，所述发送模块403，还用于：
通过虚拟基础设施管理器VIM发送所述网络配置信息到所述SDN。
进一步的，NFVO实体400还包括：
确定模块，用于根据所述网元对应的虚拟网络功能VNF包中记录的南北向通信需求信息确定所述网元的网元类型；
第一生成模块，用于生成与所述网元的网元类型对应的NSD文件，不同网元类型对应的NSD文件中记录有不同的待配置的网络参数。
NFVO实体400，所述网元类型包括第一网元类型和第二网元类型；
所述第一网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数；
所述第二网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数，SDN网关和外部PE之间的边界网关协议BGP路由参数，SDN网关和外部VNF之间的静态路由参数，或，SDN网关和VNF之间的BGP路由参数。
进一步的，NFVO实体400还包括：
第一接收模块，用于接收虚拟网络功能管理器VNFM在网元实例化完成后，发送的所述网元的虚拟机端口互联网协议IP地址信息；
第二生成模块，用于在根据所述虚拟机端口IP地址信息和NSD判断需要负载分担的情况下，根据所述虚拟机端口IP地址信息生成网元回程静态路由；
第二发送模块，用于发送所述网元回程静态路由到SDN控制器。
进一步的，所述网络实例包括网元间网络、子网和虚拟路由器中的至少一个。
进一步的，在所述网元需要配置静态路由的情况下，网络参数包括如下参数中的至少一个：路由类型、目的地址、下一跳地址和是否启用链路检测；
或，
在所述网元采用BGP动态路由协议的情况下，网络参数包括如下参数中的至少一个：租户、本端子网信息、本端自治系统AS号、对端IP地址信息、对端AS号，和，是否路由抑制；
或，
在所述网元存在跨私有网络VPC互访需求的情况下，网络参数包括如下参数中的至少一个：租户、本端网段信息和对端网段信息。
NFVO实体400能够实现图1所示的方法实施例中NFVO实体实现的各个过程，为避免重复，这里不再赘述。
本公开实施例的NFVO实体400，解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息；根据所述组网关系创建网络实例；发送所述网络配置信息到SDN控制器，网络配置信息包括用于SDN控制器配置所述网元的网络参数。通过预先配置不同类型的网元需要建立的网络关系及网络配置信息，并在解析确定这些网络关系及网络配置信息之后，通过SDN控制器进行自动的配置，实现了NFV和SDN的融合下的网元网络参数的高效配置。
参见图5，图5是本公开实施例提供的一种SDN控制器的结构示意图，如图5所示，SDN控制器500包括：
接收模块501，用于接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得；
配置模块502，用于配置所述网元的网络参数。
进一步的，接收模块501用于：
通过虚拟基础设施管理器VIM接收NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息。
进一步的，所述网元类型包括第一网元类型和第二网元类型；
所述第一网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数；
所述第二网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数，SDN网关和外部PE之间的边界网关协议BGP路由参数，SDN网关和外部VNF之间的静态路由参数，或，SDN网关和VNF之间的BGP路由参数。
进一步的，SDN控制器500还包括：
第二接收模块，用于接收网元回程静态路由，所述网元回程静态路由由所述NFVO在根据虚拟机端口互联网协议IP地址信息和NSD判断需要负载分担的情况下，根据所述虚拟机端口IP地址信息生成，所述虚拟机端口IP地址信息由所述NFVO在虚拟网络功能管理器VNFM完成网元实例化后获得。
进一步的，所述网络实例包括网元间网络、子网和虚拟路由器中的至少一个。
进一步的，在所述网元需要配置静态路由的情况下，网络参数包括如下参数中的至少一个：路由类型、目的地址、下一跳地址和是否启用链路检测；
或，
在所述网元采用BGP动态路由协议的情况下，网络参数包括如下参数中的至少一个：租户、本端子网信息、本端自治系统AS号、对端IP地址信息、对端AS号，和，是否路由抑制；
或，
在所述网元存在跨私有网络VPC互访需求的情况下，网络参数包括如下参数中的至少一个：租户、本端网段信息和对端网段信息。
SDN控制器500能够实现图2所示的方法实施例中SDN控制器实现的各个过程，为避免重复，这里不再赘述。
本公开实施例的SDN控制器500，接收NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，其中，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得。通过NFVO解析网元的NSD文件获得网络配置信息，由SDN控制器500根据网络配置信息来实现网元的网络参数的自动化配置，提高了网元的网络参数的配置效率。
参见图6，本公开实施例还提供了一种实体，包括总线601、收发机602、天线603、总线接口604、处理器605和存储器606。
在本申请一个实施例中，所述实体为网络功能虚拟化编排器NFVO，所述实体包括处理器605和收发机602；
所述处理器605用于，解析网元的与网元类型对应的网络服务描述NSD 文件，确定所述网元的组网关系和网络配置信息，并根据所述组网关系创建网络实例；
所述收发机602，用于发送所述网络配置信息到软件定义网络SDN控制器，所述网络配置信息包括用于所述SDN控制器配置所述网元的网络参数。
进一步的，所述收发机602，还用于：
通过虚拟基础设施管理器VIM发送所述网络配置信息到所述SDN控制器。
进一步的，所述处理器605还用于：
根据所述网元对应的虚拟网络功能VNF包中记录的南北向通信需求信息确定所述网元的网元类型；
生成与所述网元的网元类型对应的NSD文件，不同网元类型对应的NSD文件中记录有不同的待配置的网络参数。
进一步的，所述网元类型包括第一网元类型和第二网元类型；
所述第一网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数；
所述第二网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数，SDN网关和外部PE之间的边界网关协议BGP路由参数，SDN网关和外部VNF之间的静态路由参数，或，SDN网关和VNF之间的BGP路由参数。
进一步的，所述收发机602，还用于：接收虚拟网络功能管理器VNFM在网元实例化完成后，发送的所述网元的虚拟机端口互联网协议IP地址信息，并发送网元回程静态路由到SDN控制器；
所述处理器605还用于，根据所述虚拟机端口IP地址信息和NSD判断需要负载分担的情况下，根据所述虚拟机端口IP地址信息生成网元回程静态路由。
进一步的，所述网络实例包括网元间网络、子网和虚拟路由器中的至少一个。
进一步的，在所述网元需要配置静态路由的情况下，网络参数包括如下参数中的至少一个：路由类型、目的地址、下一跳地址和是否启用链路检测；
或，
在所述网元采用BGP动态路由协议的情况下，网络参数包括如下参数中的至少一个：租户、本端子网信息、本端自治系统AS号、对端IP地址信息、对端AS号，和，是否路由抑制；
或，
在所述网元存在跨私有网络VPC互访需求的情况下，网络参数包括如下参数中的至少一个：租户、本端网段信息和对端网段信息。
实体能够实现图1所示的方法实施例中NFVO实现的各个过程，为避免重复，这里不再赘述。
本实施例的实体，解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息；根据所述组网关系创建网络实例；发送所述网络配置信息到SDN控制器，网络配置信息包括用于SDN控制器配置所述网元的网络参数。通过预先配置不同类型的网元需要建立的网络关系及网络配置信息，并在解析确定这些网络关系及网络配置信息之后，通过SDN控制器进行自动的配置，实现了NFV和SDN的融合下的网元网络参数的高效配置。
在本申请一个实施例中，所述实体为软件定义网络SDN时，所述实体包括处理器和收发机；
所述收发机602用于：接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得；
所述处理器605，用于配置所述网元的网络参数。
进一步的，所述收发机602还用于：通过虚拟基础设施管理器VIM接收NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息。
进一步的，所述网元类型包括第一网元类型和第二网元类型；
所述第一网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数；
所述第二网元类型对应的NSD文件中记录的待配置的网络参数包括 SDN网关和外部PE之间的静态路由参数，SDN网关和外部PE之间的边界网关协议BGP路由参数，SDN网关和外部VNF之间的静态路由参数，或，SDN网关和VNF之间的BGP路由参数。
进一步的，所述收发机602还用于：
接收网元回程静态路由，所述网元回程静态路由由所述NFVO在根据虚拟机端口互联网协议IP地址信息和NSD判断需要负载分担的情况下，根据所述虚拟机端口IP地址信息生成，所述虚拟机端口IP地址信息由所述NFVO在虚拟网络功能管理器VNFM完成网元实例化后获得。
进一步的，所述网络实例包括网元间网络、子网和虚拟路由器中的至少一个。
进一步的，在所述网元需要配置静态路由的情况下，网络参数包括如下参数中的至少一个：路由类型、目的地址、下一跳地址和是否启用链路检测；
或，
在所述网元采用BGP动态路由协议的情况下，网络参数包括如下参数中的至少一个：租户、本端子网信息、本端自治系统AS号、对端IP地址信息、对端AS号，和，是否路由抑制；
或，
在所述网元存在跨私有网络VPC互访需求的情况下，网络参数包括如下参数中的至少一个：租户、本端网段信息和对端网段信息。
实体能够实现图2所示的方法实施例中SDN实现的各个过程，为避免重复，这里不再赘述。
本实施例的实体，接收NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，其中，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得。通过NFVO解析网元的NSD文件获得网络配置信息，由SDN控制器500根据网络配置信息来实现网元的网络参数的自动化配置，提高了网元的网络参数的配置效率。
在图6中，总线架构(用总线601来代表)，总线601可以包括任意数量的互联的总线和桥，总线601将包括由处理器605代表的一个或多个处理器 和存储器606代表的存储器的各种电路链接在一起。总线601还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口604在总线601和收发机602之间提供接口。收发机602可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器605处理的数据通过天线603在无线介质上进行传输，进一步，天线603还接收数据并将数据传送给处理器605。
处理器605负责管理总线601和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器606可以被用于存储处理器605在执行操作时所使用的数据。
可选的，处理器605可以是CPU、ASIC、FPGA或CPLD。
可选的，本公开实施例还提供一种电子设备，包括处理器605，存储器606，存储在存储器606上并可在所述处理器605上运行的计算机程序，该计算机程序被处理器605执行时实现上述图1-图2中任一个网络自动化编排管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述图1-图2中任一个所示的网络自动化编排管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述的计算机可读存储介质，如ROM、RAM、磁碟或者光盘等。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，模块、单元、子模块、子单元等可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本公开各个实施例所述的方法。
上面结合附图对本公开的实施例进行了描述，但是本公开并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本公开的启示下，在不脱离本公开宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本公开的保护之内。

Claims (19)

  1. 一种网络自动化编排管理方法，用于网络功能虚拟化编排器NFVO，包括：
    解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息；
    根据所述组网关系创建网络实例；
    发送所述网络配置信息到软件定义网络SDN控制器，所述网络配置信息包括用于所述SDN控制器配置所述网元的网络参数。
  2. 根据权利要求1所述的网络自动化编排管理方法，其中，所述发送所述网络配置信息到SDN控制器具体为：
    通过虚拟基础设施管理器VIM发送所述网络配置信息到所述SDN控制器。
  3. 根据权利要求1所述的网络自动化编排管理方法，其中，在所述解析网元的网络服务描述NSD文件，获取所述网元的组网关系和网络配置信息之前，所述方法还包括：
    根据所述网元对应的虚拟网络功能VNF包中记录的南北向通信需求信息确定所述网元的网元类型；
    生成与所述网元的网元类型对应的NSD文件，不同网元类型对应的NSD文件中记录有不同的待配置的网络参数。
  4. 根据权利要求3所述的网络自动化编排管理方法，其中，所述网元类型包括第一网元类型和第二网元类型；
    所述第一网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数；
    所述第二网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数，SDN网关和外部PE之间的边界网关协议BGP路由参数，SDN网关和外部VNF之间的静态路由参数，或，SDN网关和VNF之间的BGP路由参数。
  5. 根据权利要求1-4中任意一项所述的网络自动化编排管理方法，其中， 在所述发送所述网络配置信息到SDN控制器之后，所述方法还包括：
    接收虚拟网络功能管理器VNFM在网元实例化完成后，发送的所述网元的虚拟机端口互联网协议IP地址信息；
    在根据虚拟机端口IP地址信息和NSD判断需要负载分担的情况下，根据所述虚拟机端口IP地址信息生成网元回程静态路由；
    发送所述网元回程静态路由到SDN控制器。
  6. 根据权利要求1-4中任意一项所述的网络自动化编排管理方法，其中，所述网络实例包括网元间网络、子网和虚拟路由器中的至少一个。
  7. 根据权利要求1-4中任意一项所述的网络自动化编排管理方法，其中：
    在所述网元需要配置静态路由的情况下，网络参数包括如下参数中的至少一个：路由类型、目的地址、下一跳地址和是否启用链路检测；
    或，
    在所述网元采用BGP动态路由协议的情况下，网络参数包括如下参数中的至少一个：租户、本端子网信息、本端自治系统AS号、对端IP地址信息、对端AS号，和，是否路由抑制；
    或，
    在所述网元存在跨私有网络VPC互访需求的情况下，网络参数包括如下参数中的至少一个：租户、本端网段信息和对端网段信息。
  8. 一种网络自动化编排管理方法，用于软件定义网络SDN控制器，包括：
    接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得；
    配置所述网元的网络参数。
  9. 根据权利要求8所述的网络自动化编排管理方法，其中，所述接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，具体为：
    通过虚拟基础设施管理器VIM接收NFVO在根据网元的组网关系创建网 络实例之后发送的网络配置信息。
  10. 根据权利要求8所述的网络自动化编排管理方法，其中，所述网元类型包括第一网元类型和第二网元类型；
    所述第一网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数；
    所述第二网元类型对应的NSD文件中记录的待配置的网络参数包括SDN网关和外部PE之间的静态路由参数，SDN网关和外部PE之间的边界网关协议BGP路由参数，SDN网关和外部VNF之间的静态路由参数，或，SDN网关和VNF之间的BGP路由参数。
  11. 根据权利要求8-10中任意一项所述的网络自动化编排管理方法，其中，在所述接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息之后，所述方法还包括：
    接收网元回程静态路由，所述网元回程静态路由由所述NFVO在根据虚拟机端口互联网协议IP地址信息和NSD判断需要负载分担的情况下，根据虚拟机端口IP地址信息生成，所述虚拟机端口IP地址信息由所述NFVO在虚拟网络功能管理器VNFM完成网元实例化后获得。
  12. 根据权利要求8-10中任意一项所述的网络自动化编排管理方法，其中，所述网络实例包括网元间网络、子网和虚拟路由器中的至少一个。
  13. 根据权利要求8-10中任意一项所述的网络自动化编排管理方法，其中：
    在所述网元需要配置静态路由的情况下，网络参数包括如下参数中的至少一个：路由类型、目的地址、下一跳地址和是否启用链路检测；
    或，
    在所述网元采用BGP动态路由协议的情况下，网络参数包括如下参数中的至少一个：租户、本端子网信息、本端自治系统AS号、对端IP地址信息、对端AS号，和，是否路由抑制；
    或，
    在所述网元存在跨私有网络VPC互访需求的情况下，网络参数包括如下参数中的至少一个：租户、本端网段信息和对端网段信息。
  14. 一种网络功能虚拟化编排器NFVO实体，其中，所述NFVO实体包括处理器和收发机；
    所述处理器用于，解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息，并根据所述组网关系创建网络实例；
    所述收发机，用于发送所述网络配置信息到软件定义网络SDN控制器，所述网络配置信息包括用于所述SDN控制器配置所述网元的网络参数。
  15. 一种软件定义网络SDN控制器，包括处理器和收发机；
    所述收发机用于：接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得；
    所述处理器，用于配置所述网元的网络参数。
  16. 一种网络功能虚拟化编排器NFVO实体，包括：
    解析模块，用于解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息；
    创建模块，用于根据所述组网关系创建网络实例；
    发送模块，用于发送所述网络配置信息到软件定义网络SDN控制器，所述网络配置信息包括用于所述SDN控制器配置所述网元的网络参数。
  17. 一种软件定义网络SDN控制器，包括：
    接收模块，用于接收网络功能虚拟化编排器NFVO在根据网元的组网关系创建网络实例之后发送的网络配置信息，所述网络配置信息包括用于所述SDN控制器配置网元的网络参数，所述网络配置信息和所述组网关系由NFVO解析网元的与网元类型对应的网络服务描述NSD文件获得；
    配置模块，用于配置所述网元的网络参数。
  18. 一种电子设备，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至7中任一项所述的网络自动化编排管理方法中的步骤，或者，所述计算机程序被所述处理器执行时实现如权利要求8至13中任一项所述的 网络自动化编排管理方法中的步骤。
  19. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至7中任一项所述的网络自动化编排管理方法中的步骤，或者，所述计算机程序被所述处理器执行时实现如权利要求8至13中任一项所述的网络自动化编排管理方法中的步骤。
PCT/CN2021/099139 2020-06-11 2021-06-09 网络自动化编排管理方法、实体、控制器及电子设备 WO2021249432A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010530056.3 2020-06-11
CN202010530056.3A CN113810206B (zh) 2020-06-11 2020-06-11 一种网络自动化编排管理方法、实体、控制器及电子设备

Publications (1)

Publication Number Publication Date
WO2021249432A1 true WO2021249432A1 (zh) 2021-12-16

Family

ID=78845369

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/099139 WO2021249432A1 (zh) 2020-06-11 2021-06-09 网络自动化编排管理方法、实体、控制器及电子设备

Country Status (2)

Country Link
CN (1) CN113810206B (zh)
WO (1) WO2021249432A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114422280A (zh) * 2021-12-31 2022-04-29 深信服科技股份有限公司 网络部署方法、装置、节点及存储介质
CN114928536A (zh) * 2022-05-16 2022-08-19 中国建设银行股份有限公司 自动化网络变更方法及装置
CN115277422A (zh) * 2022-07-21 2022-11-01 浪潮思科网络科技有限公司 一种sdn组网生成方法、装置、设备及介质
CN115277347A (zh) * 2022-07-19 2022-11-01 浪潮思科网络科技有限公司 一种基于sdn的实验室设备管理方法及设备
WO2023125943A1 (zh) * 2021-12-31 2023-07-06 中国移动通信有限公司研究院 一种网元配置方法、装置及通信设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN106533935A (zh) * 2015-09-14 2017-03-22 华为技术有限公司 一种在云计算系统中获取业务链信息的方法和装置
CN108011759A (zh) * 2017-12-05 2018-05-08 锐捷网络股份有限公司 一种vpn管理方法、装置及系统
US10469317B1 (en) * 2017-03-29 2019-11-05 Juniper Networks, Inc. Virtualized network function descriptors for virtualized network function configuration
CN110740053A (zh) * 2018-07-20 2020-01-31 中国移动通信集团浙江有限公司 业务编排方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108400998B (zh) * 2017-02-07 2020-03-20 华为技术有限公司 一种部署vnf的方法和系统
US10448242B2 (en) * 2017-12-29 2019-10-15 Comptel Oy Method and arrangement for on-boarding network service descriptions from various sources in a common service catalogue of NFV orchestration platform
CN107948006B (zh) * 2018-01-09 2021-04-16 重庆邮电大学 一种虚拟化网络功能的编排方法及装置
CN111221619B (zh) * 2018-11-27 2023-09-08 中国移动通信集团江西有限公司 一种业务开通和编排的方法、装置及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN106533935A (zh) * 2015-09-14 2017-03-22 华为技术有限公司 一种在云计算系统中获取业务链信息的方法和装置
US10469317B1 (en) * 2017-03-29 2019-11-05 Juniper Networks, Inc. Virtualized network function descriptors for virtualized network function configuration
CN108011759A (zh) * 2017-12-05 2018-05-08 锐捷网络股份有限公司 一种vpn管理方法、装置及系统
CN110740053A (zh) * 2018-07-20 2020-01-31 中国移动通信集团浙江有限公司 业务编排方法及装置

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114422280A (zh) * 2021-12-31 2022-04-29 深信服科技股份有限公司 网络部署方法、装置、节点及存储介质
WO2023125943A1 (zh) * 2021-12-31 2023-07-06 中国移动通信有限公司研究院 一种网元配置方法、装置及通信设备
CN114422280B (zh) * 2021-12-31 2023-11-07 深信服科技股份有限公司 网络部署方法、装置、节点及存储介质
CN114928536A (zh) * 2022-05-16 2022-08-19 中国建设银行股份有限公司 自动化网络变更方法及装置
CN114928536B (zh) * 2022-05-16 2024-04-30 中国建设银行股份有限公司 自动化网络变更方法及装置
CN115277347A (zh) * 2022-07-19 2022-11-01 浪潮思科网络科技有限公司 一种基于sdn的实验室设备管理方法及设备
CN115277347B (zh) * 2022-07-19 2024-05-14 浪潮思科网络科技有限公司 一种基于sdn的实验室设备管理方法及设备
CN115277422A (zh) * 2022-07-21 2022-11-01 浪潮思科网络科技有限公司 一种sdn组网生成方法、装置、设备及介质
CN115277422B (zh) * 2022-07-21 2024-04-16 浪潮思科网络科技有限公司 一种sdn组网生成方法、装置、设备及介质

Also Published As

Publication number Publication date
CN113810206A (zh) 2021-12-17
CN113810206B (zh) 2023-01-13

Similar Documents

Publication Publication Date Title
WO2021249432A1 (zh) 网络自动化编排管理方法、实体、控制器及电子设备
US10547463B2 (en) Multicast helper to link virtual extensible LANs
US11818647B2 (en) Containerized router with a generic data plane interface
US10834669B2 (en) Stateful network slice selection using replay of connection handshake
US11483762B2 (en) Virtual service networks
US11246087B2 (en) Stateful network slice selection using slice selector as connection termination proxy
US10686627B2 (en) Distributed virtual gateway appliance
US9304801B2 (en) Elastic enforcement layer for cloud security using SDN
CN109088820B (zh) 一种跨设备链路聚合方法、装置、计算装置和存储介质
CN110476453A (zh) 用于向客户提供网络切片的服务发放
CN111866053B (zh) 软件定义网络控制器、方法及计算机可读存储介质
CN111224821B (zh) 安全服务部署系统、方法及装置
AU2023210524A1 (en) Virtual service networks
WO2017162089A1 (zh) 网络服务的业务配置方法和装置
WO2019127418A1 (zh) 网络服务管理方法、相关装置及系统
US10594602B2 (en) Web services across virtual routing and forwarding
US9590855B2 (en) Configuration of transparent interconnection of lots of links (TRILL) protocol enabled device ports in edge virtual bridging (EVB) networks
US20240113969A1 (en) Evpn host routed bridging (hrb) and evpn cloud native data center
US20230093915A1 (en) Cloud router platform for sdn networks
WO2021078058A1 (zh) 资源调度方法、装置、设备及计算机可读存储介质
CN112187489B (zh) 基于软件定义网络的网络管理系统及方法
Jain OpenFlow, software defined networking (SDN) and network function virtualization (NFV)
EP4293978A1 (en) Hybrid data plane for a containerized router
US11108652B2 (en) Server assisted network discovery (SAND)
CN113132129A (zh) 网络管理方法、装置及系统、存储介质

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: 21821529

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21821529

Country of ref document: EP

Kind code of ref document: A1