CN113810206A - A network automation orchestration management method, entity, controller and electronic device - Google Patents

Abstract

Translated fromChinese

本发明提供一种网络自动化编排管理方法、实体、控制器及电子设备，该网络自动化编排管理方法包括：NFVO解析网元的与网元类型对应的网络服务描述NSD文件，确定所述网元的组网关系和网络配置信息；根据所述组网关系创建网络实例；发送所述网络配置信息到SDN控制器，网络配置信息包括用于SDN控制器配置所述网元的网络参数。通过预先配置不同类型的网元需要建立的网络关系及网络配置信息，并在解析确定这些网络关系及网络配置信息之后，通过SDN控制器进行自动的配置，实现了NFV和SDN的融合下的网元网络参数的高效配置。

The present invention provides a method, entity, controller and electronic equipment for automatic network arrangement and management. The method for network automation arrangement and management includes: NFVO parses the network service description NSD file corresponding to the network element type of the network element, and determines the network element's network service description NSD file. networking relationship and network configuration information; creating a network instance according to the networking relationship; sending the network configuration information to the SDN controller, where the network configuration information includes network parameters for the SDN controller to configure the network element. By pre-configuring the network relationships and network configuration information that different types of network elements need to establish, and after analyzing and determining these network relationships and network configuration information, the SDN controller performs automatic configuration, realizing the network under the fusion of NFV and SDN. Efficient configuration of meta network parameters.

Description

Network automation arrangement management method, entity, controller and electronic equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a network automation arrangement management method, an entity, a controller, and an electronic device.

Background

With the rapid development of Virtualization technology, Network Function Virtualization (NFV) that implements functions of dedicated Network element devices in a Network on a general physical device has been receiving attention from people.

In the NFV system, a Network Function Virtualization Orchestrator (NFVO) is used as a core of service orchestration, and is used to perform life cycle management of an NFV Network, implement rapid deployment of the Network, and the like.

At present, when the NFVO performs network element network configuration, the configuration efficiency is low due to the need of manual participation.

Disclosure of Invention

The embodiment of the invention provides a network automation arrangement management method, an entity, a controller and electronic equipment, which aim to solve the problem of low configuration efficiency when network element network configuration is carried out.

In order to solve the technical problem, the invention is realized as follows:

in a first aspect, an embodiment of the present invention provides a network automation orchestration management method, used for a network function virtualization orchestrator NFVO, including:

analyzing a Network Service Description (NSD) file of a network element corresponding to the type of the network element, and determining networking relation and network configuration information of the network element;

creating a network instance according to the networking relationship;

sending the network configuration information to a Software Defined Network (SDN) controller, wherein the network configuration information comprises network parameters for the SDN controller to configure the network element.

In a second aspect, an embodiment of the present invention provides a network automation orchestration management method, for a software defined network SDN controller, including:

receiving network configuration information sent by a network function virtualization orchestrator NFVO after creating a network instance according to a networking relationship of a network element, wherein the network configuration information comprises network parameters used for the SDN controller to configure the network element, and the network configuration information and the networking relationship are obtained by analyzing a Network Service Description (NSD) file, corresponding to the network element type, of the network element by the NFVO.

In a third aspect, an embodiment of the present invention provides an NFVO entity, where the NFVO entity includes a processor and a transceiver;

the processor is used for analyzing a Network Service Description (NSD) file of a network element corresponding to the type of the network element, determining the networking relationship and the network configuration information of the network element, and creating a network instance according to the networking 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.

In a fourth aspect, an embodiment of the present invention provides an SDN controller, where the controller includes a processor and a transceiver;

the transceiver is configured to: receiving network configuration information sent by a network function virtualization orchestrator NFVO after a network instance is created according to a networking relationship of a network element, wherein the network configuration information comprises network parameters used for the SDN controller to configure the network element, and the network configuration information and the networking relationship are obtained by analyzing a Network Service Description (NSD) file, corresponding to the type of the network element, of the network element by the NFVO;

the processor is configured to configure a network parameter of the network element.

In a fifth aspect, an embodiment of the present invention provides an NFVO entity, including:

the analysis module is used for analyzing a Network Service Description (NSD) file of the network element corresponding to the type of the network element and determining the networking relationship and the network configuration information of the network element;

the creating module is used for creating a network instance according to the networking relation;

a sending module, 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.

In a sixth aspect, an embodiment of the present invention provides an SDN controller, including:

a receiving module, configured to receive network configuration information sent by a network function virtualization orchestrator NFVO after creating a network instance according to a networking relationship of a 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 analyzing, by the NFVO, a network service description NSD file of the network element, the network service description NSD file corresponding to a network element type;

and the configuration module is used for configuring the network parameters of the network element.

In a seventh aspect, an embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a computer program stored on the memory and being executable on the processor, where the computer program, when executed by the processor, implements the steps in the network automation orchestration management method according to the first aspect, or the computer program, when executed by the processor, implements the steps in the network automation orchestration management method according to the second aspect.

In an eighth aspect, the embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores thereon a computer program, and the computer program, when executed by the processor, implements the steps in the network automated arrangement management method according to the first aspect, or the computer program, when executed by the processor, implements the steps in the network automated arrangement management method according to the second aspect, or the computer program, when executed by the processor, implements the steps in the network automated arrangement management method according to the third aspect.

In the embodiment of the invention, the network relations and the network configuration information which need to be established by different types of network elements are configured in advance, and after the network relations and the network configuration information are analyzed and determined, the SDN controller is used for automatically configuring, so that the network element network parameters under the fusion of the NFV and the SDN are efficiently configured.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.

FIG. 1 is a flowchart of a method for managing network automation arrangement according to an embodiment of the present invention;

FIG. 1a is a diagram of a virtualization technology architecture according to an embodiment of the present invention;

FIG. 2 is a second flowchart of a network automation arrangement management method according to an embodiment of the present invention;

fig. 3 is a third flowchart of a network automation arrangement management method according to an embodiment of the present invention;

fig. 4 is a structural diagram of an NFVO entity provided in an embodiment of the present invention;

fig. 5 is a structural diagram of an SDN controller according to an embodiment of the present invention;

fig. 6 is a block diagram of another entity provided by an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Specific examples of the present invention will be described in further detail below.

Referring to fig. 1, fig. 1 is a flowchart of a network automation orchestration management method according to an embodiment of the present invention, which is used for a Network Function Virtualization Orchestrator (NFVO), and as shown in fig. 1, the network automation orchestration management method includes the following steps:

step 101, analyzing a Network Service Description (NSD) file of a network element corresponding to the type of the network element, and determining the networking relationship and the network configuration information of the network element.

A Network Service Description (NSD) file corresponds to a Network element type of a Network element, and the NFVO may determine a networking relationship and Network configuration information of the Network element by parsing the NSD file corresponding to the Network element type of the Network element, where the networking relationship may include a Network, a Service link, and the like, and the Network configuration information includes a Network parameter for configuring the Network element by a Software Defined Network (SDN) controller.

The NSD file may include one or more network element information, and after the NFVO reads and analyzes the NSD file to determine the network element requirement, the NFVO may generate a configuration requirement of a virtual router (i.e., a vruter) in the NSD, such as network element information hung under the vruter, network element load sharing routing information that needs to be configured, dynamic routing configuration information between a network element and a gateway, and the like; and meanwhile, the NSD file generates dynamic routing configuration requirements of the vRouter on an external network router, user routing configuration requirements and the like.

And 102, creating a network instance according to the networking relation.

Specifically, NFVO may create a network instance based on the NSD file through a Virtual Infrastructure Manager (VIM).

Step 103, sending the network configuration information to the SDN controller, so that the SDN controller may configure network parameters of the network element according to the network configuration information.

Fig. 1a shows a virtualization technology architecture provided by the present application, which includes an SDN controller, a Virtual Infrastructure Manager (VIM) being a key component for NFV and SDN fusion, a VIM northbound docking NFV management and orchestration system MANO, a VIM southbound docking SDN controller, and an SDN controller hosting an egress router and other network devices for network element network configuration and forwarding control.

In fig. 1a, the NFVO parses the NSD file, determines the networking relationship and the network configuration information of the network element, and the NFVO may create a network instance on the VIM based on the NSD file, and meanwhile, the NFVO sends the network configuration information to the VIM, and the VIM transmits the network configuration information to the SDN controller through the OpenStack native and extended interface, so that the SDN controller may configure the network parameters of the network element according to the network configuration information.

In the embodiment, linkage of two independent architectures, namely an NFV architecture and an SDN architecture, is realized. Through a virtualization technology (NFV), telecommunication network element functions are loaded on a uniform resource pool in a software form to form a telecommunication cloud, and an SDN technology can realize centralized calculation of network routes through an SDN controller and issue the network routes to network elements, so that intelligent scheduling of the network is realized. The NFV network element and the NFV network element are combined and supplemented with each other, and the network function software, the flexibility and the automation of the NFV network element are realized to a greater extent.

Meanwhile, in this embodiment, the NFVO parses a network service description, NSD, file of the network element corresponding to the type of the network element, and determines a networking relationship and network configuration information of the network element; creating a network instance according to the networking relationship; sending the network configuration information to an SDN controller, wherein the network configuration information comprises network parameters for the SDN controller to configure the network element. By pre-configuring network relationships and network configuration information which need to be established by different types of network elements, and after analyzing and determining the network relationships and the network configuration information, automatically configuring through an SDN controller, the network element network parameters under the fusion of NFV and SDN are efficiently configured.

In one embodiment of the present application, the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.

The NFVO may create a network instance on the VIM based on the NSD file, which may specifically include the following steps:

a, establishing a Network by using an Openstack community interface Post/v 2.0/subnet;

b. creating a Subnet by using an Openstack community interface Post/v 2.0/subnets;

c. using VIM enhanced interfaces Post/v2.0/routers, PUT/v2.0/routers/{ Router _ id } to create routers, and optionally configuring a native static route;

d. and adding the Subnet to the Router by using an Opensck community interface PUT/v2.0/routers/{ Router _ id }/add _ Router _ interface.

And according to the configuration requirement for the vruter in the NSD file, establishing the vruter in the step c, configuring the vruter in the step c, and in addition, performing different configuration operations (as described below) according to different network element requirements identified in the NSD file to configure the vruter.

The configuration information includes, but is not limited to, network element network mounting under the router, network element load sharing routing information configuring, dynamic routing configuration information between the network element and the gateway configuring, and the like; and meanwhile, configuring dynamic routing of an external network router, configuring user routing and the like.

In an embodiment of the present application, the sending the network configuration information to the SDN controller specifically includes:

sending, by the VIM, the network configuration information to the SDN controller.

The NFVO sends the network configuration information to a Virtual Infrastructure Manager (VIM), which is passed to the SDN through an OpenStack native and extended interface, so that the SDN controller may configure network parameters of the network element according to the network configuration information.

In an embodiment of the present application, before analyzing, instep 101, a network service description NSD file of a network element and acquiring a networking relationship and network configuration information of the network element, the method further includes:

determining the network element type of the network element according to the north-south communication demand information recorded in the virtual network function VNF packet corresponding to the network element;

and generating NSD files corresponding to the network element types of the network elements, wherein different to-be-configured network parameters are recorded in the NSD files corresponding to different network element types.

The north-south communication requirement information comprises network element load sharing routing information, link detection requirements, dynamic routing configuration requirements between the network elements and the gateway, user routing configuration requirements, whether the network elements share a router and the like.

The NFVO may determine a Network element type of the Network element according to the north-south communication demand information recorded in a Virtual Network Function (VNF) packet corresponding to the Network element, so as to generate a corresponding NSD file according to the Network element type. For example, Network Service (NS) design may be performed by an operator on an NFVO, which generates an NSD based on the NS. Different configuration operations can be performed on the network parameters according to different network element requirements identified in the NSD file.

In an embodiment of the present application, in a case that the network element needs to configure a static route, the network parameter includes at least one of the following parameters: routing type, destination address, next hop address, whether to enable link detection;

or

Under the condition that the network element adopts a BGP dynamic routing protocol, the network parameters comprise at least one of the following parameters: the tenant, home subnet information, home AS number, opposite terminal IP address information, opposite terminal AS number, and whether routing is inhibited;

or

In the case that the network element has a cross-VPC inter-access requirement, the network parameter comprises at least one of the following parameters: the network segment information of the tenant, the local terminal and the opposite terminal.

And under the condition that the network element needs to configure the static route, for example, the static route of the address of the UE is configured, incrementally issuing the extended static route on the Router. The network parameters include at least one of the following parameters: route type, destination address, next hop address, whether link detection is enabled.

Under the condition that the network element adopts a Border Gateway Protocol (BGP) dynamic routing Protocol, issuing Router, service network element BGP peer configuration and peer configuration of external PE equipment on the Router, respectively, where the network parameters include at least one of the following parameters: the tenant, home subnet information, home AS number, opposite terminal IP address information, opposite terminal AS number, whether to route inhibition, etc.

In the case that the network element has a cross private network (VPC) inter-access requirement, creating a VPC connectivity interconnection between routers, wherein the network parameters include at least one of the following parameters: the network segment information of the tenant, the local terminal and the opposite terminal.

In an embodiment of the present application, 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 comprise 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, border gateway protocol BGP routing parameters between the SDN gateway and the external PE, static routing parameters between the SDN gateway and the external VNF, or BGP routing parameters between the SDN gateway and the VNF.

The first network element type may be a host-type interface and the second network element type may be a routing-type interface. The first network element type and the second network element type respectively correspond to different network general models and description modes, and the description mode of the first network element type is as follows: one or more virtual NICs (virtual NICs, abbreviated as vnics), where a Network Interface Controller (NIC) shares an IP address, corresponding to a master/slave mode; the parameters to be configured at the network side are as follows: static routing between the SDN gateway and external PEs. The description mode of the second network element type is as follows: multiple VMs share the IP, which is reached through one or more vNIC IPs (load sharing); the parameters to be configured at the network side are as follows: BGP between the SDN gateway and external PE or static routing between the SDN gateway and the external PE; BGP between SDN gateway and VNF or static route between SDN gateway and VNF.

Descriptions of four types of resources, namely BGP between an SDN gateway and external PEs, static routing between the SDN gateway and the external PEs, BGP between the SDN gateway and VNFs, and static routing between the SDN gateway and VNFs, need to be added to the NSD file.

The description of the BGP between the SDN gateway and the external PE, and the BGP between the SDN gateway and the VNF includes a vruter identifier, a home terminal IP address, a home terminal AS number, an opposite terminal IP address, an opposite terminal AS number, and the like.

Description of a static route between an SDN gateway and an external PE needs to include a vruter identifier, a destination IP address, a next hop IP address, a route type, whether Bidirectional Forwarding Detection (BFD) is enabled, and the like.

Description of a static route between the SDN gateway and the VNF needs to include an IP address corresponding to a network outside the VNF, and whether load sharing is performed.

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, border gateway protocol BGP routing parameters between the SDN gateway and the external PE, static routing parameters between the SDN gateway and the external VNF, or BGP routing parameters between the SDN gateway and the VNF.

In an embodiment of the present application, after sending the network configuration information to the SDN, the method further includes:

receiving IP address information of a virtual machine port of a network element, which is sent by a VNFM after the network element instantiation is completed;

under the condition that the load sharing is judged to be needed according to the virtual machine port Internet Protocol (IP) address information and the NSD, generating a network element return static route according to the virtual machine port IP address information;

and sending the network element backhaul static route to an SDN controller.

NFVO initiates an application for creating a Network element to a Virtual Network Function Manager (VNFM), and the VNFM parses a Network element description file (VNFD) to instantiate a Network element resource. After the network element resource instantiation is completed, the VNFM sends the configured virtual machine port Internet Protocol Address (IP) information to the NFVO.

And the NFVO generates a network element return static route according to the IP address information of the virtual machine port reported by the VNFM, issues the route to the VIM, issues the route to the SDN controller, and returns to complete network service creation. The method for generating the network element backhaul static route by the NFVO specifically includes:

and adding port information in the original resource reporting interface. The port information comprises the IP address of the port, the network element network where the port is located and the UUID of the port instance. Determining whether the port performs load sharing and an IP address corresponding to the load sharing through a network element network field where the port is located in the reported port information and description of a static route between an SDN gateway and a VNF in the NSD, and if the load sharing needs to be configured, determining a backhaul static route of the port through the port IP address reported by the interface, that is, under the condition that the load sharing needs to be determined according to the virtual machine port IP address information and the NSD, the NFVO generates the network element backhaul static route according to the virtual machine port IP address information.

The method provided by the application can be applied to the instantiation process of the network service in the fusion scene of the NFV and the SDN, so that the automatic opening and configuration of the NFV network element network are realized, and the configuration efficiency of the network element network is improved.

Referring to fig. 2, fig. 2 is a flowchart of a Network automation orchestration management method according to an embodiment of the present invention, where the method is used for a Software Defined Network (SDN) controller, and as shown in fig. 2, the Network automation orchestration management method includes the following steps:

step 201, receiving network configuration information sent by a network function virtualization orchestrator NFVO after creating a network instance according to a networking relationship of a network element, wherein the network configuration information includes network parameters for the SDN controller to configure the network element, and the network configuration information and the networking relationship are obtained by analyzing a network service description NSD file, corresponding to a network element type, of the network element by the NFVO.

Step 202, configuring network parameters of the network element.

A Network Service Description (NSD) file corresponds to a Network element type of a Network element, and the NFVO may determine a networking relationship and Network configuration information of the Network element by analyzing the NSD file of the Network element corresponding to the Network element type, where the networking relationship may include a Network, a Service link, and the like, and the Network configuration information includes a Network parameter for configuring the Network element by the SDN controller.

The NSD file may include one or more network element information, and after the NFVO reads and analyzes the network element requirement, the NFVO may generate a configuration requirement of a virtual router (i.e., a vRouter) in the NSD, such as network element information hung under the vRouter, network element load sharing routing information that needs to be configured, dynamic routing configuration information between a network element and a gateway, and the like; and meanwhile, the NSD file generates dynamic routing configuration requirements of the vRouter on an external network router, user routing configuration requirements and the like.

NFVO may create a network instance based on the NSD file through a Virtual Infrastructure Manager (VIM).

In this embodiment, an SDN receives network configuration information sent by an NFVO after a network instance is created according to a networking relationship of a 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 an NFVO parsing a network service description NSD file corresponding to a network element type of the network element; and configuring the network parameters of the network element. Network relations and network configuration information which need to be established by different types of network elements are configured in advance, the network relations and the network configuration information are analyzed and determined through the NFVO, the SDN controller realizes automatic configuration of network parameters of the network elements according to the network configuration information, and efficient configuration of network element network parameters under the fusion of the NFV and the SDN is realized.

In an embodiment of the present application, the receiving network configuration information sent by the network function virtualization orchestrator NFVO after creating the network instance according to the networking relationship of the network element specifically is:

and receiving network configuration information sent by the NFVO after the network instance is created according to the networking relationship of the network elements through a VIM (virtual infrastructure manager).

The NFVO sends the network configuration information to a Virtual Infrastructure Manager (VIM), which is passed to the SDN through an OpenStack native and extended interface, so that the SDN can configure network parameters of the network element according to the network configuration information.

In an embodiment of the present application, 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 comprise 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, border gateway protocol BGP routing parameters between the SDN gateway and the external PE, static routing parameters between the SDN gateway and the external VNF, or BGP routing parameters between the SDN gateway and the VNF.

Specifically, different network parameters to be configured are recorded in NSD files corresponding to different network element types. The first network element type may be a host-type interface and the second network element type may be a routing-type interface. The first network element type and the second network element type respectively correspond to different network general models and description modes, and the description mode of the first network element type is as follows: one or more virtual NICs (virtual NICs, abbreviated as vnics), where a Network Interface Controller (NIC) shares an IP address, corresponding to a master/slave mode; the parameters to be configured at the network side are as follows: static routing between the SDN gateway and external PEs. The description mode of the second network element type is as follows: multiple VMs share the IP, which is reached through one or more vNIC IPs (load sharing); the parameters to be configured at the network side are as follows: BGP between the SDN gateway and external PE or static routing between the SDN gateway and the external PE; BGP between SDN gateway and VNF or static route between SDN gateway and VNF.

Descriptions of four types of resources, namely BGP between an SDN gateway and external PEs, static routing between the SDN gateway and the external PEs, BGP between the SDN gateway and VNFs, and static routing between the SDN gateway and VNFs, need to be added to the NSD file.

The description of the BGP between the SDN gateway and the external PE, and the BGP between the SDN gateway and the VNF includes a vruter identifier, a home terminal IP address, a home terminal AS number, an opposite terminal IP address, an opposite terminal AS number, and the like.

Description of a static route between an SDN gateway and an external PE needs to include a vruter identifier, a destination IP address, a next hop IP address, a route type, whether Bidirectional Forwarding Detection (BFD) is enabled, and the like.

Description of a static route between the SDN gateway and the VNF needs to include an IP address corresponding to a network outside the VNF, and whether load sharing is performed.

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, border gateway protocol BGP routing parameters between the SDN gateway and the external PE, static routing parameters between the SDN gateway and the external VNF, or BGP routing parameters between the SDN gateway and the VNF.

In an embodiment of the present application, after receiving the network configuration information sent by the network function virtualization orchestrator NFVO after creating the network instance according to the networking relationship of the network element, the method further includes:

receiving a network element backhaul static route, wherein the network element backhaul static route is generated by the NFVO according to the virtual machine port IP address information when the NFVO judges that load sharing is required according to the virtual machine port internet protocol IP address information and the NSD, and the virtual machine port IP address information is obtained by the NFVO after a virtual network function manager VNFM completes network element instantiation.

NFVO initiates an application for creating a Network element to a Virtual Network Function Manager (VNFM), and the VNFM parses a Network element description file (VNFD) to instantiate a Network element resource. After the network element resource instantiation is completed, the VNFM sends the configured virtual machine port Internet Protocol Address (IP) information to the NFVO.

And the NFVO generates a network element return static route according to the IP address information of the virtual machine port reported by the VNFM, issues the route to the VIM, issues the route to the SDN controller, and returns to complete network service creation.

The method for generating the network element backhaul static route by the NFVO specifically includes:

and adding port information in the original resource reporting interface. The port information comprises the IP address of the port, the network element network where the port is located and the UUID of the port instance. Determining whether the port performs load sharing and an IP address corresponding to the load sharing through a network element network field where the port is located in the reported port information and description of a static route between an SDN gateway and a VNF in the NSD, if the load sharing needs to be configured, determining a backhaul static route of the port through the port IP address reported by the interface, that is, under the condition that the load sharing needs to be determined according to the virtual machine port IP address information and the NSD, the NFVO generates a network element backhaul static route according to the virtual machine port IP address information, and then sends the network element backhaul static route to the SDN.

The method provided by the application can be applied to the instantiation process of the network service in the fusion scene of the NFV and the SDN, so that the automatic opening and configuration of the NFV network element network are realized, and the configuration efficiency of the network element network is improved.

In one embodiment of the present application, the network instance includes at least one of an inter-network element network, a subnet, and a virtual router. The NFVO may create a network instance on the VIM based on the NSD file, which may specifically include the following steps:

a, establishing a Network by using an Openstack community interface Post/v 2.0/subnet;

b. creating a Subnet by using an Openstack community interface Post/v 2.0/subnets;

c. using VIM enhanced interfaces Post/v2.0/routers, PUT/v2.0/routers/{ Router _ id } to create routers, and optionally configuring a native static route;

d. adding the Subnet to the Router by using an Opensck community interface PUT/v2.0/routers/{ Router _ id }/add _ Router _ interface;

and according to the configuration requirement for the vruter in the NSD file, establishing the vruter in the step c, configuring the vruter in the step c, and in addition, performing different configuration operations (as described below) according to different network element requirements identified in the NSD file to configure the vruter.

The configuration information includes, but is not limited to, network element network mounting under the router, network element load sharing routing information configuring, dynamic routing configuration information between the network element and the gateway configuring, and the like; and meanwhile, configuring dynamic routing of an external network router, configuring user routing and the like.

In an embodiment of the present application, in a case that the network element needs to configure a static route, the network parameter includes at least one of the following parameters: routing type, destination address, next hop address and whether to enable link detection;

or the like, or, alternatively,

under the condition that the network element adopts a BGP dynamic routing protocol, the network parameters comprise at least one of the following parameters: the tenant, home terminal subnet information, home terminal autonomous system AS number, opposite terminal IP address information, opposite terminal AS number, and whether routing inhibition exists;

or the like, or, alternatively,

in case that the network element has a cross-private network VPC mutual access requirement, the network parameter comprises at least one of the following parameters: the network segment information of the tenant, the local terminal and the opposite terminal.

And under the condition that the network element needs to configure the static route, for example, the static route of the address of the UE is configured, incrementally issuing the extended static route on the Router. The network parameters include at least one of the following parameters: route type, destination address, next hop address, whether link detection is enabled.

Under the condition that the network element adopts a Border Gateway Protocol (BGP) dynamic routing Protocol, issuing Router, service network element BGP peer configuration and peer configuration of external PE equipment on the Router, respectively, where the network parameters include at least one of the following parameters: the tenant, home subnet information, home AS number, opposite terminal IP address information, opposite terminal AS number, whether to route inhibition, etc.

In the case that the network element has a cross private network (VPC) inter-access requirement, creating a VPC connectivity interconnection between routers, wherein the network parameters include at least one of the following parameters: the network segment information of the tenant, the local terminal and the opposite terminal.

The following is an example of a detailed process of the network automation arrangement management method provided by the present application. Fig. 3 is a flowchart of a network automation arrangement management method according to an embodiment of the present application, and as shown in fig. 3, the network automation arrangement management method includes the following steps:

step 11, the NFVO receives the uploaded VNF network element package;

step 12, the NFVO reads the network element north-south communication requirements (including the network element load sharing routing information, the link detection requirements, the dynamic routing configuration requirements between the network element and the gateway, the user routing configuration requirements, whether the network element shares the vruter, etc.) from the VNF package, performs NSD design, generates a network service description file NSD (the NSD includes one or more network element information, and after reading and analyzing the network element requirements, the NSD generates the configuration requirements of the vruter, such as the network element information hung under the vruter, the network element load sharing routing information needed to be configured, the dynamic routing configuration information between the network element and the gateway, etc., and simultaneously generates the dynamic routing configuration requirements of the vruter on the external network router, the user routing configuration requirements, etc.).

Step 13, initiating a network service instantiation process according to the selected NSD;

step 14, the NFVO parses a network service description file NSD, where the NSD includes network element north-south routing information, link detection requirements, user routing configuration requirements, and the like added in the embodiment of the present invention;

step 15, the NFVO creates an external network instance through the VIM, wherein the network instance comprises a network and a subnet among network elements, a vrouter and the like; the present step may comprise the following steps:

using an Openstack community interface Post/v2.0/subnet to create a Network;

creating a Subnet by using an Openstack community interface Post/v 2.0/subnets;

using VIM enhanced interfaces Post/v2.0/routers, PUT/v2.0/routers/{ Router _ id } to create routers, and optionally configuring a native static route;

the Subnet is added to the Router by using Opensck community interface PUT/v2.0/routers/{ Router _ id }/add _ Router _ interface.

Step 16, the NFVO issues network configuration parameters to the VIM, and the network configuration parameters are transmitted to the SDN controller by the VIM through the OpenStack native and extended interfaces; in this step, different configuration operations can be performed according to different network element requirements identified in the NSD.

For example, if the network element needs to configure a static route (for example, a UE address static route needs to be configured), an extended static route is issued on the Router in an incremental manner, and an interface needs to include a route type, a destination address, a next hop address, whether to enable link detection, and the like;

if the network element adopts a BGP dynamic routing protocol, respectively issuing Router and BGP peer configuration of a service network element and peer configuration of external PE equipment on the Router, wherein interfaces need to contain tenants, local terminal subnet information, local terminal AS numbers, opposite terminal IP address information, opposite terminal AS numbers, whether routing inhibition is required and the like;

if cross-VPC mutual access requirements exist among network elements, cross-Router VPC Connection interconnection is established, and interfaces need to contain tenants, local end network segment information, opposite end network segment information and the like.

And step 17, the NFVO requests the VNFM to create a network element, and the VNFM analyzes the network element description file VNFD and instantiates network element resources. And after the network element resource instantiation is completed, the VNFM sends the configured IP address information of the virtual machine port to the NFVO.

And step 18, the NFVO generates a network element return static route according to the IP address information reported by the VNFM, and sends the route to the VIM, and the VIM sends the route to the SDN controller.

Step 19, the NFVO returns the web service creation complete.

Aiming at the network service description file NSD mentioned in thestep 12, the application also provides a network element network general model and a description mode. As shown in table 1, the network element may include two types of interfaces, a host type interface and a routing type interface, where the two types of interfaces respectively correspond to different network general models and description modes.

TABLE 1

Four kinds of resource descriptions of BGP between an SDN gateway and an external PE, static routing between the SDN gateway and the external PE, BGP between the SDN gateway and a VNF, and static routing between the SDN gateway and the VNF are required to be added in the network service description file NSD.

The description of the BGP between the SDN gateway and the external PE and the BGP between the SDN gateway and the VNF need to include a vRouter identifier, a home IP address, a home AS number, an opposite IP address, an opposite AS number, and the like.

The description of the static route between the SDN gateway and the external PE needs to include a vruter identifier, a destination IP address, a next hop IP address, a route type, whether BFD is enabled, and the like.

Description of a static route between the SDN gateway and the VNF needs to include an IP address corresponding to a network outside the VNF, and whether load sharing is performed.

To step 16, the present application provides a backhaul static routing configuration method: and adding port information in the original resource reporting interface. The port information comprises the IP address of the port, the network element network where the port is located and the UUID of the port instance. And determining whether the port performs load sharing and an IP address corresponding to the load sharing through a network element network field where the port is located in the reported port information and the description of a static route between an SDN gateway and a VNF in the NSD. And if the load sharing needs to be configured, determining the backhaul static route of the port through the port IP address reported by the interface.

The method provided by the application can be applied to the instantiation process of the network service in the fusion scene of the NFV and the SDN, so that the automatic opening and configuration of the NFV network element network are realized, and the configuration efficiency of the network element network is improved.

The NFVO, VNFM, VIM, etc. may be deployed individually, or the NFVO, VNFM, VIM may be deployed in the same server.

Referring to fig. 4, fig. 4 is a schematic structural diagram of an NFVO entity provided in an embodiment of the present invention, and as shown in fig. 4, anNFVO entity 400 includes:

theanalysis module 401 is configured to analyze a network service description NSD file of a network element, which corresponds to a network element type, and determine a networking relationship and network configuration information of the network element;

a creatingmodule 402, configured to create a network instance according to the networking relationship;

a sendingmodule 403, 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.

Further, the sendingmodule 403 is further configured to:

sending, by a Virtual Infrastructure Manager (VIM), the network configuration information to the SDN.

Further,NFVO entity 400 further includes:

a determining module, configured to determine a network element type of the network element according to the north-south communication demand information recorded in the virtual network function VNF packet corresponding to the network element;

the first generating module is configured to generate an NSD file corresponding to a network element type of the network element, where different to-be-configured network parameters are recorded in the NSD file corresponding to different network element types.

AnNFVO entity 400, where the network element types include 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 comprise 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, border gateway protocol BGP routing parameters between the SDN gateway and the external PE, static routing parameters between the SDN gateway and the external VNF, or BGP routing parameters between the SDN gateway and the VNF.

Further,NFVO entity 400 further includes:

the network element instantiation processing module is used for receiving network element instantiation information of a virtual machine port of a network element, and sending the network element instantiation information to a virtual network function manager VNFM;

a second generating module, 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;

and a second sending module, configured to send the backhaul static route of the network element to an SDN controller.

Further, the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.

Further, in a case that the network element needs to configure a static route, the network parameter includes at least one of the following parameters: routing type, destination address, next hop address and whether to enable link detection;

or the like, or, alternatively,

under the condition that the network element adopts a BGP dynamic routing protocol, the network parameters comprise at least one of the following parameters: the tenant, home terminal subnet information, home terminal autonomous system AS number, opposite terminal IP address information, opposite terminal AS number, and whether routing inhibition exists;

or the like, or, alternatively,

in case that the network element has a cross-private network VPC mutual access requirement, the network parameter comprises at least one of the following parameters: the network segment information of the tenant, the local terminal and the opposite terminal.

TheNFVO entity 400 can implement each process implemented by the NFVO entity in the method embodiment shown in fig. 1, and is not described herein again to avoid repetition.

TheNFVO entity 400 of the embodiment of the present invention parses a network service description NSD file of a network element corresponding to a network element type, and determines a networking relationship and network configuration information of the network element; creating a network instance according to the networking relationship; sending the network configuration information to an SDN controller, wherein the network configuration information comprises network parameters for the SDN controller to configure the network element. By pre-configuring network relationships and network configuration information which need to be established by different types of network elements, and after analyzing and determining the network relationships and the network configuration information, automatically configuring through an SDN controller, the network element network parameters under the fusion of NFV and SDN are efficiently configured.

Referring to fig. 5, fig. 5 is a schematic structural diagram of an SDN controller according to an embodiment of the present invention, and as shown in fig. 5, theSDN controller 500 includes:

areceiving module 501, configured to receive network configuration information sent by a network function virtualization orchestrator NFVO after creating a network instance according to a networking relationship of a 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 analyzing, by the NFVO, a network service description NSD file of the network element, where the network service description NSD file corresponds to a network element type;

aconfiguring module 502, configured to configure network parameters of the network element.

Further, the receivingmodule 501 is configured to:

and receiving network configuration information sent by the NFVO after the network instance is created according to the networking relationship of the network elements through a VIM (virtual infrastructure manager).

Further, 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 comprise 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, border gateway protocol BGP routing parameters between the SDN gateway and the external PE, static routing parameters between the SDN gateway and the external VNF, or BGP routing parameters between the SDN gateway and the VNF.

Further, theSDN controller 500 further includes:

a second receiving module, configured to receive a network element backhaul static route, where the network element backhaul static route is generated by the NFVO according to the virtual machine port IP address information when it is determined that load sharing is required according to the virtual machine port internet protocol IP address information and the NSD, and the virtual machine port IP address information is obtained by the NFVO after a virtual network function manager VNFM completes network element instantiation.

Further, the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.

Further, in a case that the network element needs to configure a static route, the network parameter includes at least one of the following parameters: routing type, destination address, next hop address and whether to enable link detection;

or the like, or, alternatively,

under the condition that the network element adopts a BGP dynamic routing protocol, the network parameters comprise at least one of the following parameters: the tenant, home terminal subnet information, home terminal autonomous system AS number, opposite terminal IP address information, opposite terminal AS number, and whether routing inhibition exists;

or the like, or, alternatively,

in case that the network element has a cross-private network VPC mutual access requirement, the network parameter comprises at least one of the following parameters: the network segment information of the tenant, the local terminal and the opposite terminal.

TheSDN controller 500 can implement each process implemented by the SDN controller in the method embodiment shown in fig. 2, and is not described here again to avoid repetition.

TheSDN controller 500 according to the embodiment of the present invention receives network configuration information sent by an NFVO after creating a network instance according to a networking relationship of a 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 an NFVO parsing a network service description NSD file of the network element corresponding to a network element type. The network configuration information is obtained by analyzing the NSD file of the network element through the NFVO, and theSDN controller 500 realizes automatic configuration of the network parameters of the network element according to the network configuration information, so that the configuration efficiency of the network parameters of the network element is improved.

Referring to fig. 6, an embodiment of the present invention further provides an entity including abus 601, atransceiver 602, anantenna 603, abus interface 604, aprocessor 605, and amemory 606.

In one embodiment of the present application, the entity is a network function virtualization orchestrator NFVO, and the entity includes aprocessor 605 and atransceiver 602;

theprocessor 605 is configured to analyze a Network Service Description (NSD) file of a network element corresponding to a network element type, determine a networking relationship and network configuration information of the network element, and create a network instance according to the networking relationship;

thetransceiver 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.

Further, thetransceiver 602 is further configured to:

sending, by a Virtual Infrastructure Manager (VIM), the network configuration information to the SDN controller.

Further, theprocessor 605 is further configured to:

determining the network element type of the network element according to the north-south communication demand information recorded in the virtual network function VNF packet corresponding to the network element;

and generating NSD files corresponding to the network element types of the network elements, wherein different to-be-configured network parameters are recorded in the NSD files corresponding to different network element types.

Further, 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 comprise 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, border gateway protocol BGP routing parameters between the SDN gateway and the external PE, static routing parameters between the SDN gateway and the external VNF, or BGP routing parameters between the SDN gateway and the VNF.

Further, thetransceiver 602 is further configured to: receiving virtual machine port Internet Protocol (IP) address information of a network element sent by a Virtual Network Function Manager (VNFM) after the network element is instantiated, and sending a network element return static route to an SDN controller;

theprocessor 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.

Further, the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.

Further, in a case that the network element needs to configure a static route, the network parameter includes at least one of the following parameters: routing type, destination address, next hop address and whether to enable link detection;

or the like, or, alternatively,

under the condition that the network element adopts a BGP dynamic routing protocol, the network parameters comprise at least one of the following parameters: the tenant, home terminal subnet information, home terminal autonomous system AS number, opposite terminal IP address information, opposite terminal AS number, and whether routing inhibition exists;

or the like, or, alternatively,

in case that the network element has a cross-private network VPC mutual access requirement, the network parameter comprises at least one of the following parameters: the network segment information of the tenant, the local terminal and the opposite terminal.

The entity can implement each process implemented by the NFVO in the method embodiment shown in fig. 1, and is not described here again to avoid repetition.

The entity of this embodiment parses a network service description NSD file of a network element corresponding to a network element type, and determines a networking relationship and network configuration information of the network element; creating a network instance according to the networking relationship; sending the network configuration information to an SDN controller, wherein the network configuration information comprises network parameters for the SDN controller to configure the network element. By pre-configuring network relationships and network configuration information which need to be established by different types of network elements, and after analyzing and determining the network relationships and the network configuration information, automatically configuring through an SDN controller, the network element network parameters under the fusion of NFV and SDN are efficiently configured.

In one embodiment of the present application, when the entity is a software defined network SDN, the entity comprises a processor and a transceiver;

thetransceiver 602 is configured to: receiving network configuration information sent by a network function virtualization orchestrator NFVO after a network instance is created according to a networking relationship of a network element, wherein the network configuration information comprises network parameters used for the SDN controller to configure the network element, and the network configuration information and the networking relationship are obtained by analyzing a Network Service Description (NSD) file, corresponding to the type of the network element, of the network element by the NFVO;

theprocessor 605 is configured to configure a network parameter of the network element.

Further, thetransceiver 602 is further configured to: and receiving network configuration information sent by the NFVO after the network instance is created according to the networking relationship of the network elements through a VIM (virtual infrastructure manager).

Further, 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 comprise 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, border gateway protocol BGP routing parameters between the SDN gateway and the external PE, static routing parameters between the SDN gateway and the external VNF, or BGP routing parameters between the SDN gateway and the VNF.

Further, thetransceiver 602 is further configured to:

receiving a network element backhaul static route, wherein the network element backhaul static route is generated by the NFVO according to the virtual machine port IP address information when the NFVO judges that load sharing is required according to the virtual machine port internet protocol IP address information and the NSD, and the virtual machine port IP address information is obtained by the NFVO after a virtual network function manager VNFM completes network element instantiation.

Further, the network instance includes at least one of an inter-network element network, a subnet, and a virtual router.

Further, in a case that the network element needs to configure a static route, the network parameter includes at least one of the following parameters: routing type, destination address, next hop address and whether to enable link detection;

or the like, or, alternatively,

under the condition that the network element adopts a BGP dynamic routing protocol, the network parameters comprise at least one of the following parameters: the tenant, home terminal subnet information, home terminal autonomous system AS number, opposite terminal IP address information, opposite terminal AS number, and whether routing inhibition exists;

or the like, or, alternatively,

in case that the network element has a cross-private network VPC mutual access requirement, the network parameter comprises at least one of the following parameters: the network segment information of the tenant, the local terminal and the opposite terminal.

The entity can implement each process implemented by the SDN in the method embodiment shown in fig. 2, and is not described here again to avoid repetition.

The entity of this embodiment receives network configuration information sent by the NFVO after creating a network instance according to a networking relationship of a 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 the NFVO analyzing a network service description NSD file, corresponding to a network element type, of the network element. The network configuration information is obtained by analyzing the NSD file of the network element through the NFVO, and theSDN controller 500 realizes automatic configuration of the network parameters of the network element according to the network configuration information, so that the configuration efficiency of the network parameters of the network element is improved.

In fig. 6, a bus architecture (represented by bus 601), wherebus 601 may include any number of interconnected buses and bridges, wherebus 601 links together various circuits including one or more processors, represented byprocessor 605, and memory, represented bymemory 606. Thebus 601 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. Abus interface 604 provides an interface between thebus 601 and thetransceiver 602. Thetransceiver 602 may be one element or may be multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by theprocessor 605 is transmitted over a wireless medium via theantenna 603, and further, theantenna 603 receives the data and transmits the data to theprocessor 605.

Theprocessor 605 is responsible for managing thebus 601 and general processing, and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. Andmemory 606 may be used to store data used byprocessor 605 in performing operations.

Alternatively,processor 605 may be a CPU, ASIC, FPGA or CPLD.

Preferably, an embodiment of the present invention further provides an electronic device, which includes aprocessor 605, amemory 606, and a computer program stored in thememory 606 and capable of running on theprocessor 605, where the computer program, when executed by theprocessor 605, implements each process of any one of the foregoing network automation arrangement management method embodiments in fig. 1-2, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the network automation arrangement management method embodiment shown in any one of fig. 1 to fig. 2, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The computer readable storage medium is, for example, ROM, RAM, magnetic disk or optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims (19)

1. A network automation arrangement management method is used for a network function virtualization orchestrator NFVO, and is characterized by comprising the following steps:

analyzing a Network Service Description (NSD) file of a network element corresponding to the type of the network element, and determining networking relation and network configuration information of the network element;

creating a network instance according to the networking relationship;

sending the network configuration information to a Software Defined Network (SDN) controller, wherein the network configuration information comprises network parameters for the SDN controller to configure the network element.

2. The method according to claim 1, wherein the sending the network configuration information to an SDN controller is specifically:

sending, by a Virtual Infrastructure Manager (VIM), the network configuration information to the SDN controller.

3. The method according to claim 1, wherein before parsing the Network Service Description (NSD) file of the network element and obtaining the networking relationship and the network configuration information of the network element, the method further comprises:

determining the network element type of the network element according to the north-south communication demand information recorded in the virtual network function VNF packet corresponding to the network element;

and generating NSD files corresponding to the network element types of the network elements, wherein different to-be-configured network parameters are recorded in the NSD files corresponding to different network element types.

4. The method of claim 3, wherein the network element types comprise 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 comprise 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, border gateway protocol BGP routing parameters between the SDN gateway and the external PE, static routing parameters between the SDN gateway and the external VNF, or BGP routing parameters between the SDN gateway and the VNF.

5. The method of network automated orchestration management according to any one of claims 1-4, further comprising, after the sending the network configuration information to an SDN controller:

receiving virtual machine port Internet Protocol (IP) address information of a network element, which is sent by a VNFM after the network element instantiation is completed;

under the condition that load sharing is judged to be needed according to the IP address information of the virtual machine port and NSD, generating a network element return static route according to the IP address information of the virtual machine port;

and sending the network element backhaul static route to an SDN controller.

6. The method of automated orchestration management according to any of claims 1-4, wherein the network instance comprises at least one of an inter-network element network, a subnet, and a virtual router.

7. The network automated orchestration management method according to any one of claims 1-4, wherein:

in case that the network element needs to configure a static route, the network parameter includes at least one of the following parameters: routing type, destination address, next hop address and whether to enable link detection;

or the like, or, alternatively,

under the condition that the network element adopts a BGP dynamic routing protocol, the network parameters comprise at least one of the following parameters: the tenant, home terminal subnet information, home terminal autonomous system AS number, opposite terminal IP address information, opposite terminal AS number, and whether routing inhibition exists;

or the like, or, alternatively,

in case that the network element has a cross-private network VPC mutual access requirement, the network parameter comprises at least one of the following parameters: the network segment information of the tenant, the local terminal and the opposite terminal.

8. A network automation arrangement management method is used for a Software Defined Network (SDN) controller and is characterized by comprising the following steps:

receiving network configuration information sent by a network function virtualization orchestrator NFVO after a network instance is created according to a networking relationship of a network element, wherein the network configuration information comprises network parameters used for the SDN controller to configure the network element, and the network configuration information and the networking relationship are obtained by analyzing a Network Service Description (NSD) file, corresponding to the type of the network element, of the network element by the NFVO;

and configuring the network parameters of the network element.

9. The method according to claim 8, wherein the receiving network configuration information sent by the network function virtualization orchestrator NFVO after creating the network instance according to the networking relationship of the network element specifically includes:

and receiving network configuration information sent by the NFVO after the network instance is created according to the networking relationship of the network elements through a VIM (virtual infrastructure manager).

10. The method of claim 8, wherein the network element types comprise 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 comprise 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, border gateway protocol BGP routing parameters between the SDN gateway and the external PE, static routing parameters between the SDN gateway and the external VNF, or BGP routing parameters between the SDN gateway and the VNF.

11. The network automation orchestration management method according to any one of claims 8-10, further comprising, after receiving the network configuration information sent by the network function virtualization orchestrator NFVO after creating a network instance according to a networking relationship of a network element:

receiving a network element backhaul static route, wherein the network element backhaul static route is generated by the NFVO according to virtual machine port IP address information obtained by the NFVO after network element instantiation is completed by a virtual network function manager VNFM under the condition that the NFVO judges that load sharing is required according to the virtual machine port internet protocol IP address information and the NSD.

12. The method of any of claims 8-10, wherein the network instance comprises at least one of an inter-network element network, a subnet, and a virtual router.

13. A network automated orchestration management method according to any one of claims 8-10, wherein:

in case that the network element needs to configure a static route, the network parameter includes at least one of the following parameters: routing type, destination address, next hop address and whether to enable link detection;

or the like, or, alternatively,

under the condition that the network element adopts a BGP dynamic routing protocol, the network parameters comprise at least one of the following parameters: the tenant, home terminal subnet information, home terminal autonomous system AS number, opposite terminal IP address information, opposite terminal AS number, and whether routing inhibition exists;

or the like, or, alternatively,

in case that the network element has a cross-private network VPC mutual access requirement, the network parameter comprises at least one of the following parameters: the network segment information of the tenant, the local terminal and the opposite terminal.

14. An NFVO entity, wherein the NFVO entity comprises a processor and a transceiver;

the processor is used for analyzing a Network Service Description (NSD) file of a network element corresponding to the type of the network element, determining the networking relationship and the network configuration information of the network element, and creating a network instance according to the networking 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.

15. An SDN controller, the SDN controller comprising a processor and a transceiver;

the transceiver is configured to: receiving network configuration information sent by a network function virtualization orchestrator NFVO after a network instance is created according to a networking relationship of a network element, wherein the network configuration information comprises network parameters used for the SDN controller to configure the network element, and the network configuration information and the networking relationship are obtained by analyzing a Network Service Description (NSD) file, corresponding to the type of the network element, of the network element by the NFVO;

the processor is configured to configure a network parameter of the network element.

16. An NFVO entity, comprising:

the analysis module is used for analyzing a Network Service Description (NSD) file of the network element corresponding to the type of the network element and determining the networking relationship and the network configuration information of the network element;

the creating module is used for creating a network instance according to the networking relation;

a sending module, 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.

17. An SDN controller, comprising:

a receiving module, configured to receive network configuration information sent by a network function virtualization orchestrator NFVO after creating a network instance according to a networking relationship of a 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 analyzing, by the NFVO, a network service description NSD file of the network element, the network service description NSD file corresponding to a network element type;

and the configuration module is used for configuring the network parameters of the network element.

18. An electronic device comprising a processor, a memory, and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps in a network automated orchestration management method according to any one of claims 1 to 7, or the computer program, when executed by the processor, implementing the steps in a network automated orchestration management method according to any one of claims 8 to 13.

19. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the network automated orchestration management method according to any one of claims 1 to 7, or which, when being executed by the processor, carries out the steps of the network automated orchestration management method according to any one of claims 8 to 13.

Images