WO2018201787A1 - 虚拟网络创建方法、装置、设备及传送网络系统、存储介质 - Google Patents

虚拟网络创建方法、装置、设备及传送网络系统、存储介质 Download PDF

Info

Publication number
WO2018201787A1
WO2018201787A1 PCT/CN2018/077854 CN2018077854W WO2018201787A1 WO 2018201787 A1 WO2018201787 A1 WO 2018201787A1 CN 2018077854 W CN2018077854 W CN 2018077854W WO 2018201787 A1 WO2018201787 A1 WO 2018201787A1
Authority
WO
WIPO (PCT)
Prior art keywords
virtual
vnet
vnode
port
network
Prior art date
Application number
PCT/CN2018/077854
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 中兴通讯股份有限公司
Priority to EP18793863.4A priority Critical patent/EP3621243B1/en
Publication of WO2018201787A1 publication Critical patent/WO2018201787A1/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
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • 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/12—Discovery or management of network topologies

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a method and apparatus for creating a virtual network of a transport network based on a Software Defined Network (SDN), a virtual network creation device, a transport network system, and a computer storage medium.
  • SDN Software Defined Network
  • the transport network bears a large number of services. Its service type is very complex and the number of customers it serves is large.
  • the types of services include mobile backhaul, home broadband, Internet of Things IoT applications, industrial control. Applications such as mobile backhaul, home broadband, IoT applications, industrial control applications, etc.
  • an A-plane network and a B-plane network can be constructed to carry mobile backhaul services and government services, thereby implementing different services.
  • Physical network isolation a method of constructing multiple planar physical transport networks.
  • this method of constructing multiple planar physical transport networks has the problems of large investment and high cost, and resources between different plane transport networks cannot be coordinated and shared, resulting in low utilization of network resources.
  • a demand for a physical transport network virtualization slice is generated.
  • an operator's demand scenario for transport network slicing is to virtualize the same metropolitan area network into three different slicing networks, which are used for mobile backhaul, home customers, and enterprise customers, and these three virtual ones.
  • the slicing network is similar to three different platform physical networks, independent of each other, so that different business departments can manage and control separately.
  • VPN virtual private network
  • L2VPN Layer 2 VPN
  • L3VPN Layer 3 VPN
  • Embodiments of the present invention provide an SDN-based transport network virtual network creation method and apparatus, a virtual network creation device, and an SDN-based transport network system and a computer storage medium, which can effectively share physical network resources and improve resource utilization. In network operation and maintenance and business deployment.
  • a virtual network creation method including:
  • vNode Create a virtual network element (vNode) and a virtual port according to the virtual port parameters of the virtual network element; create a virtual link (vLink) between the virtual ports of the vNode according to the virtual port parameter; wherein the virtual network element and the virtual link form a virtual Network (vNet).
  • vNode virtual network element
  • vLink virtual link
  • a virtual network creation apparatus including: a vNode creation module, configured to create a virtual network element vNode and a virtual port according to virtual port parameters of the virtual network element; and a vLink creation module configured to A virtual link vLink is created between the virtual ports of the vNode according to the virtual port parameters; wherein the virtual network element and the virtual link form a virtual network vNet.
  • the virtual port includes: a virtual network node port vNNI and a virtual user network port vUNI.
  • the vLink creation module is configured to determine a tunnel creation requirement according to the virtual port parameter provided by the user, generate a tunnel creation command according to the requirements created by the tunnel, and send a tunnel creation command to the SDN controller, where the creation command includes the tunnel creation.
  • the requirement wherein the virtual port parameter includes at least one of the following: a port information, a routing policy, a routing constraint, and a protection mode of the vNNI of the AZ endpoint;
  • the transport network creation device further includes:
  • the virtual-physical resource mapping module is configured to create a mapping relationship between the vNode and the node, and create a mapping relationship between the vLink and the tunnel according to the tunnel ID returned by the SDN controller.
  • a transport network system including a vNet manager and an SDN controller, wherein the vNet manager is configured to create a virtual network element vNode and virtual according to virtual port parameters of the virtual network element.
  • a virtual link vLink is created between the virtual ports of the vNode according to the virtual port parameters; wherein the virtual network element and the virtual link form a virtual network vNet;
  • the SDN controller is configured to communicate with the vNet manager and assist the vNet manager Complete the creation of vNode and vLink.
  • the vNet manager accesses the SDN controller through the internal interface; in the case where the vNet manager is implemented independently of the SDN controller, the vNet manager passes the southbound interface module Access to the SDN controller.
  • the virtual port includes: a virtual network node port vNNI and a virtual user network port vUNI.
  • a virtual network creation device including: a memory and a processor, where the memory stores a computer program, and when the computer program is executed by the processor, the following steps are implemented:
  • the virtual port parameters of the virtual network element provided by the user create a vNode and a virtual port.
  • a vLink is created between the virtual ports of the vNode.
  • the virtual network element and the virtual link form a vNet.
  • a computer storage medium storing a computer program for performing the aforementioned virtual network creation method is provided.
  • the embodiment of the present invention has at least the following advantages:
  • the solution in the embodiment of the present invention can slice a physical network into a corresponding virtual network according to different service types or different tenants (for example, slice according to government enterprise customers, home customers, or eMBB services, uRLLC services, and mMTC services).
  • Each virtual transport network has characteristics similar to physical networks. For the services it carries, the virtual network that the service perceives is similar to the physical network, thus effectively meeting the needs of different types of services.
  • the embodiment of the present invention performs virtual network slicing on the basis of physical network resource sharing, thereby avoiding problems such as large investment, high cost, and low utilization rate caused by repeated network construction.
  • FIG. 1 is a flowchart of a method for creating a virtual network of a SDN-based transport network according to an embodiment of the present invention
  • FIG. 2 is a block diagram of a network element (Satellite) slice model according to an embodiment of the present invention
  • FIG. 3 is a block diagram of a link slice and virtual network (vNet) model in accordance with an embodiment of the present invention
  • FIG. 4 is a block diagram of a network architecture model based on network slicing according to an embodiment of the present invention
  • FIG. 5 is a block diagram of an SDN-based transport network virtual network creation apparatus according to an embodiment of the present invention.
  • FIG. 6 is a block diagram of a transport network system to which an SDN-based transport network virtual network creation device is applied, in accordance with an embodiment of the present invention
  • FIG. 7 is a signaling flowchart of a vNet creation process in an SDN-based transport network network tiling scheme according to an embodiment of the present invention
  • FIG. 8 is a signaling flowchart of a vNode creation process in an SDN-based transport network network tiling scheme according to an embodiment of the present invention
  • FIG. 9 is a signaling flowchart of a vLink creation process in an SDN-based transport network network tiling scheme according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of a network creation process according to an embodiment of the present invention.
  • SDN is a new type of network innovation architecture. Unlike traditional VPN technology, the core technology of SDN is to separate the control plane and forwarding plane of the network to achieve centralized control, thus achieving flexible control of network resources and services.
  • the embodiment of the present invention is a network virtualization using SDN technology, thereby establishing a virtual network based on a physical network, which is equivalent to implementing a network slice of the transport network.
  • a first embodiment of the present invention provides a virtual network creation method, and specifically provides a SDN-based transport network virtual network creation method. As shown in FIG. 1, the following specific steps are included:
  • Step S101 Create a virtual network element (vNode) and a virtual port according to virtual port parameters of the virtual network element.
  • the virtual port parameter is provided by a user.
  • Step S102 Create a virtual link (vLink) between the virtual ports of the vNode; wherein the virtual network element and the virtual link form a virtual network (vNet).
  • vLink virtual link
  • vNet virtual network
  • the above method according to an embodiment of the present invention may further include: creating a vNet;
  • the vNet can be created prior to the vNode and/or vLink. For example, you can create them in the following order: create vNet ⁇ create vNode ⁇ create vLink; or you can create them in the following order: create vNode ⁇ create vNet ⁇ create vLink.
  • the parameters of the vNet can be understood as characteristic parameters, including but not limited to: name, user information, and feature description.
  • vNet is created later than vNode and vLink.
  • the vNet creation should be completed with further reference to the vNode and vLink that have been created, specifically In the process of creation, it is necessary to refer to the vNet name and the included vNode list, wherein all virtual links vLink between the vNodes are automatically attributed to the vNet.
  • the vNet may be created according to the parameters of the vNet, and then the vNode and vLink that have been created are added to the vNet.
  • the virtual port includes: a virtual network node port (vNNI) and a virtual user network port (vUNI).
  • the network element (Node) is the core element of the network, and the vNode constitutes the vNet. From the network point of view, the ability of Node to externally present is mainly reflected by the network node port (NNI) and user network port (UNI) capabilities of the network element. Therefore, the process of creating a vNode based on a physical network element (Node) can be understood as a Node. Virtualization slicing, in order to achieve this goal, first to solve the virtualization of its ports, it can also be understood as the slicing of the port. As shown in Figure 2, the physical network element Node1 includes UNI and NNI ports.
  • the virtual network elements formed by Node1 are used to form different virtual networks vNet1 and vNet2 respectively. That is, the virtual network elements formed after Node1 slicing are in the corresponding vNet (vNet). 1 and vNet 2) are the virtual network element vNode1@vNet1 and the virtual network element vNode1@vNet2, respectively.
  • the virtual network element vNode1@vNet1 includes the sliced virtual ports vUNI1@UNI1 and vNNI1@NNI1
  • the virtual network element vNode1@vNet2 includes the sliced virtual ports vUNI2@UNI1 and vNNI2@NNI1.
  • the vUNI can identify and filter the traffic of the UNI ingress entering the vNet according to the corresponding configuration.
  • vNNI is used to subsequently create a link vLink between vNodes.
  • a vLink can be created between the vNNIs of the vNodes by establishing a virtual pipe or a tunnel according to the virtual port parameters provided by the user, thereby realizing the virtual network topology reconstruction.
  • the topology of the network can be established according to the needs of the user.
  • the topology of the virtual network is not limited to the physical network topology.
  • the tunnel creation requirements are determined according to the virtual port parameters provided by the user, the tunnel creation command is generated according to the requirements of the tunnel creation, and the tunnel creation command is sent to the SDN controller, and the creation command includes the tunnel creation.
  • the virtual port parameter includes at least one of: port information (including bandwidth information) of the vNNI of the AZ endpoint, routing policy (for example, shortest path or load balancing, etc.), and routing constraint (for example, a mandatory node, a mandatory Link, exclusion node, exclusion link, etc.), protection mode (including path protection or rerouting protection, etc.); according to the tunnel ID returned by the SDN controller, create a mapping relationship between the vLink and the tunnel and generate a vLink ID (ie, Complete mapping of virtual resources and physical resources).
  • port information including bandwidth information
  • routing policy for example, shortest path or load balancing, etc.
  • routing constraint for example, a mandatory node, a mandatory Link, exclusion node, exclusion link, etc.
  • protection mode including path protection or rerouting protection, etc.
  • the SDN controller calculates the tunnel route and the cross-connection (CrossConnection) configuration parameters (including the cross-nodes) according to the requirements of the tunnel creation included in the tunnel creation command.
  • the inbound and outbound parameters, etc. reserve bandwidth resources on the NNI, and send the cross-connection creation command to the network device (Network Element, NE for short).
  • the cross-connection creation command includes the configuration parameters of the cross-connection and the pre-configuration.
  • the information of the reserved bandwidth resource is configured to use the reserved bandwidth resource, create a cross-connection according to the configuration parameter of the cross-connection included in the cross-connection creation command, and send the created cross-connection ID to the SDN controller; After the NE completes the cross-connection creation (that is, the reserved resources have been allocated), the SDN controller creates an inclusion relationship between the tunnel and the cross-connection according to the parameters of the created cross-connection and the parameters of the cross-connection returned by the NE, and returns Tunnel ID.
  • Link is a key element that makes up the internal connections and network topology of the network.
  • vLink is a virtual link between vNodes through vNNI.
  • Link1 is a link between physical network elements Node1 and Node2
  • Link2 is a link between physical network elements Node2 and Node3.
  • a virtual link can be formed between the vNNIs by establishing a virtual pipe or a tunnel to form a virtual network topology to implement topology reconstruction of the virtual network.
  • vLink1 is a virtual link between vNode1 and vNode3
  • vLink2 is a virtual link between vNode1 and vNode2
  • vLink3 is a virtual link between vNode2 and vNode3.
  • vLink can be a Flex Ethernet pipe; for a packet device network element supporting Multi-Protocol Label Switching Transport Profile (MPLS-TP), vLink It can be an MPLS-TP Label Switching Path (LSP) tunnel.
  • MPLS-TP Multi-Protocol Label Switching Transport Profile
  • vLink can be an MPLS-TP Label Switching Path (LSP) tunnel.
  • OTN Optical Transport Network
  • ODUk Optical Path Data Unit
  • the SDN controller and the NE side After the vLink is successfully created, the SDN controller and the NE side generate the corresponding vLink, vLink ID (ID), and working path routing information, or further generate protection path routing information, and route the path along the working path and the protection path.
  • the bandwidth of the network node port NNI is reserved.
  • vNet1 can be considered to be composed of virtual network elements such as vNode1@vNet1 and vNode3@vNet1, and virtual links such as vLink1@vNet1;
  • vNet2 is composed of vNode1@vNet2.
  • Virtual network elements such as vNode2@vNet2 and vNode3@vNet2, and virtual links such as vLink2@vNet2 and vLink3@vNet2.
  • the virtual port parameter of the virtual network element includes at least one of the following: a vNode name, and an ID of the Node to which the vNode belongs (since the vNode is created by virtualizing the Node,
  • the Node can be understood as the host of the vNode, the ID of the vNet to which the vNode belongs, the port parameter of the vNNI included in the vNode, and the port parameter of the vUNI included in the vNode.
  • the port parameters of the vNNI include the network node port (NNI) to which the vNNI belongs.
  • the ID and vNNI allocation bandwidth; the port parameters of the vUNI include the ID of the user network port (UNI) to which each vUNI belongs and the allocated bandwidth of the vUNI.
  • the port parameters of the vNNI and the port parameters of the vUNI can be saved in the respective port attribute list.
  • the SDN controller is configured to create an object instance of the vNNI and the vUNI according to the virtual port parameter, and configured to reserve resources for the vNode, the vNNI, and the vUNI, and generate a port ID corresponding to the vNNI and the vUNI, where the vNNI and the vUNI are pre- When the resource is reserved, the SDN controller is configured to reserve bandwidth resources on the NNI and UNI to which the vNNI and the vUNI belong.
  • At least one of the following steps may be further performed: modifying the name of the created vNode, adding or deleting the vNNI and/or vUNI included in the vNode, and modifying the vNNI included in the vNode.
  • Port bandwidth modify the port bandwidth of the vUNI included in the vNode.
  • vNet services can be created based on the vNets that have been created, including but not limited to at least one of the following: L2VPN, L3VPN.
  • L2VPN Low-power Virtual Network
  • L3VPN Low-power Virtual Network
  • vNet creation step at least one of the following steps may be performed: generating a corresponding vNet ID, modifying a vNet name, adding or deleting a vNode included in the vNet.
  • the network architecture is divided into a physical network layer, a service layer, and a client layer according to layers.
  • a service layer Above the physical network layer is a service layer, that is, the service is directly loaded on the physical network.
  • the network layering model and method according to the embodiment of the present invention adds a virtual network layer after the slice between the service layer and the physical network layer.
  • the obtained network architecture is as shown in FIG. 4 . Referring to FIG. 4, after the tiling scheme proposed in the embodiment of the present invention is sliced, the obtained network architecture has the following features:
  • the virtual network layer is located between the service layer and the physical network layer, which decouples the service layer from the physical network layer, and the service layer does not need to perceive the physical network.
  • the virtual network formed by slicing has characteristics similar to physical networks.
  • the perceived virtual network is similar to the physical network.
  • slice is not dependent on business. Similar to a physical network, a virtual network is created before the service is created, and then the service is reloaded on the virtual network, and the service can be flexibly created and adjusted.
  • a virtual network creation apparatus is further provided, in particular, an SDN-based transport network virtual network creation apparatus is provided (the apparatus can create multiple virtual networks on a physical network basis, and thus can also It is understood as a device for network slicing of a transport network, as shown in FIG. 5, comprising:
  • the vNode creation module 51 is configured to create a virtual network element vNode and a virtual port according to the virtual port parameter of the virtual network element, where the virtual port parameter is provided by the user;
  • the vLink creation module 52 is configured to create a virtual link vLink between the virtual ports of the vNode according to the virtual port parameters; wherein the virtual network element and the virtual link form a virtual network vNet.
  • the transport network creation device In the process of creating a vNode, a virtual port, and a vLink, the transport network creation device according to an embodiment of the present invention needs to communicate with the SDN.
  • the transport network virtual network creation apparatus In the case where the transport network virtual network creation apparatus is embedded in the SDN controller according to an embodiment of the present invention, the apparatus accesses the SDN controller through the internal interface; in the case where the transport network virtual network creation apparatus is implemented independently of the SDN controller, The device will be connected to the SDN controller through the southbound interface module.
  • the above virtual ports include: a virtual network node port vNNI and a virtual user network port vUNI.
  • the vLink creation module 52 is configured to create a vLink between the vNNIs of the vNodes by establishing a virtual pipe or a tunnel according to the virtual port parameters provided by the user, to implement virtual network topology reconstruction.
  • the VLink creation module 52 is configured to determine a tunnel creation requirement according to the virtual port parameter provided by the user, generate a tunnel creation command according to the requirements created by the tunnel, and send a tunnel creation command to the SDN controller, where the creation command includes the tunnel creation.
  • the virtual port parameter includes at least one of the following: a port information of the vNNI of the AZ endpoint, a routing policy, a routing constraint, and a protection mode; and the transport network virtual network creating apparatus according to the embodiment of the present invention further includes:
  • the physical resource mapping module (not shown) is configured to create a mapping relationship between the vNode and the node, and create a mapping relationship between the vLink and the tunnel according to the tunnel ID returned by the SDN controller.
  • the vLink creation module 52 is configured to generate a vLink ID, and the virtual-physical resource mapping module can establish a mapping relationship between the vLink ID and the tunnel ID.
  • the foregoing SDN controller is configured to calculate a route of the tunnel and a configuration parameter of the cross-connection according to the requirements of the tunnel creation command included in the tunnel creation command, reserve the bandwidth resource on the NNI, and send the cross-connection creation command to the network device NE.
  • the cross-connection creation command includes the configuration parameters of the cross-connection and the information of the reserved bandwidth resources; the SDN controller is further configured to, according to the configuration parameters of the cross-connection and the ID of the cross-connection returned by the NE, in case the NE successfully creates the cross-connection Creating an inclusion relationship between the tunnel and the cross-connection and generating a tunnel ID; and, the NE is configured to create a cross-connection using the reserved bandwidth resource, according to the configuration parameters of the cross-connection included in the cross-connection creation command, and create the The cross-connected ID is sent to the SDN controller.
  • the virtual port parameter of the virtual network element includes at least one of the following:
  • the vNode name the ID of the node to which the vNode belongs, the ID of the vNet to which the vNode belongs, the port parameter of the vNNI included in the vNode, and the port parameter of the vUNI included in the vNode; wherein the port parameter of the vNNI includes the ID of the network node port NNI to which the vNNI belongs and the vNNI
  • the allocated bandwidth, the port parameters of the vUNI include the ID of the user network port UNI to which each vUNI belongs and the allocated bandwidth of the vUNI.
  • the vNode creation module 51 is configured to send the virtual port parameters of the virtual network element to the SDN controller; and configured to create an object instance of the vNode according to the port ID returned by the SDN controller and generate a vNode ID; wherein, the SDN control
  • the device is configured to create object instances of vNNI and vUNI based on virtual port parameters, and configured to reserve resources for vNodes, vNNIs, and vUNIs and generate port IDs corresponding to vNNIs and vUNIs, wherein when resources are reserved for vNNIs and vUNIs,
  • the SDN controller is configured to reserve bandwidth resources on the NNI and UNI to which the vNNI and the vUNI belong.
  • a transport network virtual network creation device is embedded in an SDN controller. At this time, the transport network virtual network creation device according to an embodiment of the present invention accesses the SDN controller through an internal interface. In another embodiment, the transport network virtual network creation apparatus according to the present invention is implemented independently of the SDN controller. At this time, the transport network virtual network creation apparatus according to the embodiment of the present invention accesses the SDN controller through the southbound interface module.
  • the transport network virtual network creation apparatus has the functions of resource mapping and lifecycle management, it is functionally completely independent of the SDN controller, such that when the transport network virtual according to the embodiment of the present invention is employed in the system When the network creates a device, it can avoid excessive improvement of the existing system and has good compatibility.
  • the foregoing transport network virtual network creating apparatus further includes: a vNet creating module configured to create a vNet;
  • the vNet creation module is configured to create a vNet based on the parameters of the vNet, and the vNode and/or vLink to be created when the vNode and/or vLink are created or after the creation is completed.
  • the vNet creation module is configured to create a vNet based on the vNet's parameters including the created vNode and vLink lists.
  • the vNode creation module 51, the vLink creation module 52, and the vNet creation module are set in the lifecycle management module, and the lifecycle management module is configured to perform at least one of the following functions: modifying the name of the created vNode, adding or deleting the vNode.
  • the included vNNI and/or vUNI modify the port bandwidth of the vNNI and vUNI included in the vNode, modify the port bandwidth of the vUNI included in the vNode, generate the corresponding vNet ID, modify the vNet name, add or delete the vNode included in the vNet.
  • the lifecycle management module is configured to perform at least one of the following functions: modifying the name of the created vNode, adding or deleting the vNNI and/or vUNI included in the vNode, modifying the port bandwidth of the vNNI included in the vNode, and modifying the vNode. Contains the port bandwidth of the vUNI, generates the corresponding vNet ID, modifies the vNet name, adds or removes the vNode included in the vNet.
  • the above apparatus according to an embodiment of the present invention may further include:
  • the northbound interface module is configured to provide a vNet control interface to an upper-layer controller or an application. Based on the vNet that has been created, multiple types of services can be created. These service types can include at least one of the following: L2VPN and L3VPN.
  • FIG. 6 is a block diagram of an SDN based transport network system in accordance with an embodiment of the present invention.
  • the system includes a vNet manager (corresponding to the previously described transport network virtual network creation device, which may also be referred to as a vNet hypervisor, ie, the vNet Hypervisor shown in FIG. 6) and an SDN controller.
  • vNet manager corresponding to the previously described transport network virtual network creation device, which may also be referred to as a vNet hypervisor, ie, the vNet Hypervisor shown in FIG. 6
  • the system shown includes a service control layer, a slice control layer (virtualization layer), and a physical network controller layer.
  • the SDN controller is located at the physical network control layer and is responsible for the control of the physical network.
  • the SDN controller can send commands to each network element (Network Element) to control the operations of each NE to complete the cross-connection.
  • the vNet hypervisor is located in the slice control layer (virtualization layer) and is responsible for slice control (virtualization) of the physical network.
  • the vNet Hypervisor includes: virtual-physical resource mapping, configured as a mapping between virtual resources and physical resources; vNet lifecycle management module (vNet lifecycle mgmt) configured as a virtual network vNet and its included vNodes , vLink and other virtual resource creation and lifecycle management, therefore, it can be understood that the vNet lifecycle management module includes the above vNode creation module, vLink creation module and vNet creation module, and these modules and other modules included in the vNet Hypervisor The function has been explained before, and will not be described here.
  • the vNet Hypervisor may further include a northbound interface module (NBI) configured to provide a control interface of the vNet to an upper layer controller or APP.
  • NBI northbound interface module
  • the vNet Hypervisor can be a standalone system on top of the SDN Controller or an internal component embedded in the SDN Controller. If the vNet Hypervisor is implemented as a standalone system on top of the SDN Controller, the vNet Hypervisor can access the underlying SDN Controller through the Southbound Interface Module (SBI).
  • SBI Southbound Interface Module
  • the SDN Controller (vNet) control of the vNet at the service control layer is similar to the control of the physical network.
  • An SDN Controller (vNet) instance or APP corresponds to a vNet control to achieve isolation of different vNet control planes.
  • the Administrator in Figure 6 is the administrator of the controller, responsible for issuing various configuration commands to the controller.
  • Each controller can have a unified Administrator or a separate Administrator.
  • Orchestrator it can also send configuration commands for network slicing to the controller.
  • the following administrator can also be replaced with Orchestrator.
  • the process of creating a vNet may specifically include the following steps:
  • the Administrator sends the command Create vNet to the vNet Hypervisor, including the following parameters: vNet name, included vNode list (vLink is automatically attributed to the vNet for all virtual links between vNodes);
  • vNet Hypervisor After the vNet Hypervisor successfully creates the vNet, it generates the corresponding vNetID and returns a vNet creation success response to the Administrator, and vNetID;
  • vNet is just a logical collection of vNodes and vLinks built on the vNet Hypervisor, so the SDN Controller and Network Element do not need to be aware of vNet.
  • the process of creating a vNode may specifically include the following steps:
  • the command contains the following parameters: vNode name, its own NodeID, its associated vNet ID, vNNI port and attribute list (including the NNI ID of each vNNI and the allocated bandwidth of vNNI), vUNI Port and attribute list (including the UNI ID of each vUNI and the allocated bandwidth of vUNI);
  • the vNet Hypervisor sends the command Create vPort request to the SDN Controller, including the following parameters: vNNI port and attribute list (including the NNI ID and vNNI allocation bandwidth of each vNNI), vUNI port and attribute list (including the UNI ID to which each vUNI belongs). And vUNI allocated bandwidth);
  • the SDN Controller creates vNNI and vUNI object instances, generates the corresponding vNNI ID and vUNI ID, and reserves bandwidth resources for vNNI and vUNI on the corresponding NNI and UNI.
  • the SDN Controller returns a vPort creation success response to the vNet Hypervisor, and the vNNI ID and vUNI ID.
  • the 4.vNet Hypervisor creates a vNode object instance (including the corresponding vNNI ID and vUNI ID), generates a vNodeID, and returns a vNode creation success response to the Administrator. And vNodeID.
  • the process of creating a vLink may specifically include the following steps:
  • administering sends the command Create vLink to the vNet Hypervisor, including the following parameters: AZ endpoint vNNI (vNNI contains bandwidth information), routing policy (such as shortest path or load balancing, etc.), routing constraints (such as mandatory nodes, mandatory chain) Road, etc.), protection mode (path 1+1/1:1 protection or rerouting protection, etc.);
  • routing policy such as shortest path or load balancing, etc.
  • routing constraints such as mandatory nodes, mandatory chain) Road, etc.
  • protection mode path 1+1/1:1 protection or rerouting protection, etc.
  • the vNet Hypervisor converts the vLink creation requirements into the requirements for creating a tunnel, and sends a command Create Tunnel Request to the SDN Controller with the same parameters as above;
  • the SDN Controller calculates the route of the tunnel, and routes the CrossConnection configuration parameters of the network element, and reserves bandwidth resources on the corresponding NNI port.
  • the specific CrossConnection parameters and Node configuration parameters depend on the tunnel type, for example, LSP Tunnel or ODUk Tunnel.
  • the SDN Controller sends a command Create CrossConnection to each Network Element
  • Each Network Element completes the Cross Connection creation and corresponding configuration and resource reservation, and returns a Cross Connection creation success response and a Cross Connection ID to the SDN Controller;
  • the SDN Controller creates the inclusion relationship between the tunnel and the Cross Connection, generates the tunnel ID, and returns the tunnel creation success response to the vNet Hypervisor, and the TunnelID.
  • the SDN Controller creates the inclusion relationship between the tunnel and the Cross Connection, generates the tunnel ID, and returns the tunnel creation success response to the vNet Hypervisor, and the TunnelID.
  • the SDN Controller creates the inclusion relationship between the tunnel and the Cross Connection, generates the tunnel ID, and returns the tunnel creation success response to the vNet Hypervisor, and the TunnelID.
  • vNet Hypervisor creates the vLink and tunnel containment relationship, generates the vLinkID, and returns the vLink to the Administrator. Create a successful response, and vLinkID.
  • FIG. 10 is a specific implementation flowchart of a network slicing process according to an embodiment of the present invention, including the following steps:
  • step S101 the administrator sends a command to the vNet Hypervisor to create a vNet instance.
  • the command parameter is
  • step S102 the administrator sends a command to the vNet Hypervisor to create vNode1@vNet1, and the command parameter is
  • step S103 the vNet Hypervisor sends a command to the SDN Controller to create vNNI1@NNI1 and vUNI1@UNI1.
  • the command parameters are:
  • step S105 the administrator sends a command to the vNet Hypervisor to create vNode3@vNet1, and the command parameter is
  • step S106 the vNet Hypervisor sends a command to the SDN Controller to create vNNI1@NNI1 and vUNI1@UNI1.
  • the command parameters are:
  • step S108 the administrator sends a command to the vNet Hypervisor to create vLink1@vNet1, and the command parameter is
  • step S109 the vNet Hypervisor converts the request for creating the vLink1@vNet1 into a command for creating the ODU2 pipe and sends it to the SDN Controller.
  • the command parameters are:
  • step S110 the SDN controller calculates the route of vLink1@vNet1 as Node1-Node2-Node3 based on the physical topology, and calculates the time slot intersection of the optical channel data unit ODU2 inside the Node2.
  • step S111 the SDN Controller sends an ODU2CrossConnection command to the network element Node2.
  • the solution in the embodiment of the present invention can slice a physical network into a corresponding virtual network according to different service types or different tenants (for example, according to a government enterprise client, a home customer, or an enhanced mobile broadband eMBB service, Ultra-high reliability and low-latency uRLLC services, large-scale Internet of Things mMTC services are sliced), each virtual transport network has similar physical network characteristics. For the services it carries, the virtual network that the service perceives is similar to the physical network, thus effectively meeting the needs of different types of services.
  • the embodiment of the present invention performs virtual network slicing on the basis of physical network resource sharing, thereby avoiding problems such as large investment, high cost, and low utilization rate caused by repeated network construction.
  • the foregoing SDN-based transport network virtual network creation method may be implemented by means of software plus a necessary general hardware platform, and may of course also be through hardware, but in many cases, the former is a better implementation.
  • the method of the embodiments of the present invention may be embodied in the form of a computer software product stored in a storage medium (such as a ROM/RAM, a magnetic disk, an optical disk), including a plurality of instructions.
  • a device (which may be a network device such as a base station) is caused to perform the method described in the embodiments of the present invention.
  • a virtual network creation device includes: a memory and a processor, wherein the memory stores a computer program executable on the processor, and the computer program is executed by the processor to implement the following steps: according to the virtual port parameter of the virtual network element provided by the user Create a vNode and a virtual port; create a vLink between the virtual ports of the vNode according to the virtual port parameters; wherein the virtual network element and the virtual link form a vNet.
  • the virtual ports include: vNNI and vUNI.
  • the step of creating a vLink between the virtual ports of the vNode specifically includes:
  • the step of creating a virtual link vLink between the virtual ports of the vNode according to the virtual port parameter specifically includes:
  • the tunnel creation request is determined according to the virtual port parameters provided by the user, the tunnel creation command is generated according to the requirements created by the tunnel, and the tunnel creation command is sent to the SDN controller, where the creation command includes the requirements for tunnel creation, where the virtual port parameter Including at least one of the following: port information, routing policy, routing constraint, and protection mode of the vNNI of the AZ endpoint;
  • the SDN controller is configured to calculate a route of the tunnel and a configuration parameter of the cross-connection according to the requirements of the tunnel creation request included in the tunnel creation command, reserve bandwidth resources on the NNI, and send a cross-connection creation command to the
  • the network device (NE) the cross-connection creation command includes the configuration parameters of the cross-connection and the information of the reserved bandwidth resources;
  • the SDN controller is further configured to configure the cross-connect configuration parameters and the NE when the NE successfully creates the cross-connection The ID of the returned cross-connection, creating an inclusion relationship between the tunnel and the cross-connection and generating a tunnel ID;
  • the NE is configured to create a cross-connection according to the reserved bandwidth resource, according to the configuration parameter of the cross-connection included in the cross-connection creation command, and send the created cross-connect ID to the SDN controller.
  • the virtual port parameter of the virtual network element includes at least one of the following:
  • the vNode name the ID of the node to which the vNode belongs, the ID of the vNet to which the vNode belongs, the port parameter of the vNNI included in the vNode, and the port parameter of the vUNI included in the vNode; wherein the port parameter of the vNNI includes the ID of the network node port NNI to which each vNNI belongs and vNNI allocates bandwidth.
  • the port parameters of the vUNI include the ID of the user network port UNI to which each vUNI belongs and the allocated bandwidth of the vUNI.
  • the step of creating a vNode and a virtual port according to the virtual port parameters of the virtual network element provided by the user includes:
  • the SDN controller is configured to create an object instance of the vNNI and the vUNI according to the virtual port parameter, and configured to reserve resources for the vNode, the vNNI, and the vUNI and generate a port ID corresponding to the vNNI and the vUNI, wherein the vNNI and the vUNI are pre- When the resource is reserved, the SDN controller is configured to reserve bandwidth resources on the NNI and UNI to which the vNNI and the vUNI belong.
  • the computer program is further executed by the processor to implement at least one of the following steps:
  • the vNet is created before the vNode and/or the vLink
  • the vNet is created according to the parameters of the vNet, and the created vNode and/or vLink are added to the vNet when the vNode and/or the vLink are created or after the creation is completed; or,
  • vNet is created later than vNode and vLink
  • vNet is created according to the vNet parameters including the created vNode and vLink list; or vNet is created according to the parameters of vNet, and then the created vNode and vLink are added to the created In the vNet.
  • the computer program is executed by the processor to implement the following steps:
  • the foregoing method according to the embodiment of the present invention further includes: creating a service based on the vNet that has been created, including but not limited to at least one of the following: L2VPN, L3VPN
  • a computer storage medium (which may be a ROM, a RAM, a hard disk, a detachable memory, etc.), wherein the storage medium stores a computer program for performing a network creation step,
  • the computer program has a code segment configured to perform the steps of: creating a virtual network element and a virtual port according to a virtual port parameter of the virtual network element; and creating a virtual link between the virtual ports of the virtual network element according to the virtual port parameter;
  • the virtual network element and the virtual link form a virtual network.
  • a computer program having a code segment configured to perform the following network creation steps: creating a virtual network element and a virtual port according to virtual port parameters of the virtual network element; A virtual link is created between the virtual ports of the virtual network element according to the virtual port parameters.
  • the virtual network element and the virtual link form a virtual network.
  • the embodiment of the invention performs virtual network slicing on the basis of physical network resource sharing, thereby avoiding the problems of large investment, high cost and low utilization rate caused by repeated network construction.
  • virtual network similar to the physical network, based on the independent virtualized network, you can create various services, such as L2VPN and L3VPN. This enables higher resource utilization and more flexible scheduling, allowing management, operation and maintenance, and service deployment. It is easier to solve the problems in the prior art.

Landscapes

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

Abstract

本发明实施例公开了一种基于软件定义网络的传送网虚拟网络创建方法和装置及传送网络系统，其中，该方法包括：根据虚拟网元的虚拟端口参数创建虚拟网元和虚拟端口；根据虚拟端口参数，在虚拟网元的虚拟端口之间创建虚拟链路；其中，虚拟网元和虚拟链路组成虚拟网络。还公开一种虚拟网络创建装置、设备及传送网络系统、计算机存储介质。

Description

虚拟网络创建方法、装置、设备及传送网络系统、存储介质
相关申请的交叉引用
本申请基于申请号为201710308230.8、申请日为2017年5月04日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的内容在此以引入方式并入本申请。
技术领域
本发明涉及网络通信技术领域，尤其涉及一种基于软件定义网络(Software Defined Network，简称为SDN)的传送网虚拟网络创建方法和装置、虚拟网络创建设备以及传送网络系统、计算机存储介质。
背景技术
传送网作为整个通信网络的基础网络，承担着大量业务的传输，其业务类型非常复杂，所服务的客户数量众多，例如，业务的类型包括移动回传、家庭宽带、物联网IoT应用、工业控制应用等，所服务的客户包括移动回传、家庭宽带、IoT应用、工业控制应用等。当这些不同客户、不同类型的业务在同一物理传送网上传送时，由于物理网络资源完全共享，缺乏有效的隔离机制，因此带来了管理和控制的复杂性问题。
为了解决这个问题，有些运营商采取了建设多个平面物理传送网的方式，例如，可以建设A平面网络和B平面网络，分别用于承载移动回传业务和政企业务，从而实现不同业务的物理网络隔离。但是，这种建设多个平面物理传送网的方式存在投资大、成本高的问题，并且不同平面的传送网之间的资源不能协调和共享，导致网络资源利用率很低。
为了解决上述问题，产生了物理传送网虚拟化切片的需求。举例而言， 一个运营商，其传送网切片的需求场景就是将同一张城域网虚拟为三个不同的切片网络，分别用于移动回传、家庭客户、企业客户的承载，而这三个虚拟的切片网络类似三个不同平台物理网络，彼此独立，从而方便不同的业务部门分别进行管理和控制。
传统的虚拟专用网(VPN)技术，例如L2VPN(二层VPN)、L3VPN(三层VPN)实质上是在业务层建立的业务虚拟专网，直接与业务绑定，不能满足在物理网络层将一个物理传送网络切片成多个虚拟物理传送网的需求。
因此，传统的虚拟网络技术存在物理网共享不足、资源利用率低的问题。针对这些问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例在于提供一种基于SDN的传送网虚拟网络创建方法和装置、虚拟网络创建设备以及基于SDN的传送网络系统和计算机存储介质，能够有效共享物理网资源，提高资源利用率，有助于网络运维和业务部署。
根据本发明实施例的一个方面，提供了一种虚拟网络创建方法，包括：
根据虚拟网元的虚拟端口参数创建虚拟网元(vNode)和虚拟端口；根据虚拟端口参数，在vNode的虚拟端口之间创建虚拟链路(vLink)；其中，虚拟网元和虚拟链路组成虚拟网络(vNet)。
根据本发明实施例的另一方面，提供了一种虚拟网络创建装置，包括：vNode创建模块，配置为根据虚拟网元的虚拟端口参数创建虚拟网元vNode和虚拟端口；vLink创建模块，配置为根据虚拟端口参数，在vNode的虚拟端口之间创建虚拟链路vLink；其中，虚拟网元和虚拟链路组成虚拟网络vNet。
其中，上述虚拟端口包括：虚拟网络节点端口vNNI和虚拟用户网络端口vUNI。
此外，vLink创建模块配置为根据用户提供的虚拟端口参数确定隧道创建的需求，根据所述隧道创建的需求生成隧道创建命令，并将隧道创建命令发送至SDN控制器，创建命令中包含隧道创建的需求，其中，虚拟端口参数包括以下至少之一：A-Z端点的vNNI的端口信息、路由策略、路由约束、保护方式；
并且，根据本发明实施例的传送网网络创建装置还包括：
虚拟-物理资源映射模块，配置为创建vNode与Node的映射关系，以及根据SDN控制器返回的隧道ID，创建vLink与隧道之间的映射关系。
根据本发明实施例的再一方面，提供了一种传送网络系统，包括vNet管理器和SDN控制器；其中，vNet管理器，配置为根据虚拟网元的虚拟端口参数创建虚拟网元vNode和虚拟端口；根据虚拟端口参数，在vNode的虚拟端口之间创建虚拟链路vLink；其中，虚拟网元和虚拟链路组成虚拟网络vNet；SDN控制器配置为与vNet管理器通信，并协助vNet管理器完成vNode和vLink的创建。
其中，在vNet管理器嵌入在SDN控制器中的情况下，vNet管理器通过内部接口接入SDN控制器；在vNet管理器独立于SDN控制器实现的情况下，vNet管理器通过南向接口模块接入SDN控制器。
此外，虚拟端口包括：虚拟网络节点端口vNNI和虚拟用户网络端口vUNI。
根据本发明实施例的再一方面，提供了一种虚拟网络创建设备，包括：存储器及处理器，所述存储器存储有计算机程序，所述计算机程序被所述处理器执行时实现以下步骤：根据用户提供的虚拟网元的虚拟端口参数创建vNode和虚拟端口；根据虚拟端口参数，在vNode的虚拟端口之间创建vLink；其中，虚拟网元和虚拟链路组成vNet。
根据本发明实施例的再一方面，提供了一种计算机存储介质，存储有 计算机程序，所述计算机程序用于执行前述的虚拟网络创建方法。
采用上述技术方案，本发明实施例至少具有下列优点：
本发明实施例所述的方案能够根据承载不同业务类型或不同租户而将物理网络切片成相应的虚拟网络(例如，按照政企客户、家庭客户、或者eMBB业务、uRLLC业务、mMTC业务进行切片)，每一个虚拟传送网都具有类似物理网络的特征。对其承载的业务而言，业务感知到的虚拟网络和物理网络类似，从而有效满足不同类型业务需求。相对于建设不同的物理网络平面，本发明实施例在物理网络资源共享的基础上进行虚拟网络切片，避免了重复建网带来的投资大、成本高、利用率低等问题。不仅如此，和物理网络类似，基于彼此独立的切片虚拟网络，可以再创建需要的各种业务，例如L2VPN、L3VPN等，能够让资源利用率更高、调度更加灵活，让管理、运维以及业务部署更加容易，从而有效解决了现有技术中存在的问题。
附图说明
图1为本发明实施例的基于SDN的传送网虚拟网络创建方法的流程图；
图2是根据本发明实施例的网元(Node)切片模型的框图；
图3是根据本发明实施例的链路(Link)切片和虚拟网络(vNet)模型的框图；
图4是根据本发明实施例的基于网络切片的网络架构模型框图；
图5为本发明实施例的基于SDN的传送网虚拟网络创建装置的框图；
图6是根据本发明实施例的基于SDN的传送网虚拟网络创建装置所应用的传送网络系统的框图；
图7根据本发明实施例的基于SDN的传送网网络切片方案中vNet创建过程的信令流程图；
图8根据本发明实施例的基于SDN的传送网网络切片方案中vNode创建过程的信令流程图；
图9根据本发明实施例的基于SDN的传送网网络切片方案中vLink创建过程的信令流程图；
图10是根据本发明实施例的网络创建过程的流程图；
具体实施方式
为更进一步阐述本发明为达成预定目的所采取的技术手段及功效，以下结合附图及较佳实施例，对本发明进行详细说明如后。
SDN是一种新型网络创新架构，与传统的VPN技术不同，SDN的核心技术是将网络的控制平面和转发平面相分离，实现集中控制，从而实现网络资源和业务的灵活控制。本发明实施例正是利用SDN技术的网络虚拟化，从而在物理网络基础上建立虚拟网络，相当于实现传送网的网络切片。
本发明第一实施例，提供了一种虚拟网络创建方法、具体是提供一种基于SDN的传送网虚拟网络创建方法，如图1所示，包括以下具体步骤：
步骤S101，根据虚拟网元的虚拟端口参数创建虚拟网元(vNode)和虚拟端口；
其中，所述虚拟端口参数由用户提供。
步骤S102，在vNode的虚拟端口之间创建虚拟链路(vLink)；其中，虚拟网元和虚拟链路组成虚拟网络(vNet)。
根据本发明实施例的上述方法可以还包括：创建vNet；
在一个实施例中，vNet可以先于vNode和/或vLink创建。例如，可以按照如下顺序进行创建：创建vNet→创建vNode→创建vLink；或者，也可以按照如下顺序进行创建：创建vNode→创建vNet→创建vLink。在这种情况下，在创建vNet时，由于vNode和/或vLink还没有创建，所以可以先根据vNet的参数创建vNet，并在vNode和/或vLink创建时或创建完成后， 将创建的vNode和/或vLink加入vNet中。其中，vNet的参数可以理解为是特性参数，包括但不限于：名称、用户信息、特征描述。
在另一实施例中，vNet晚于vNode和vLink创建。在这种情况下，由于vNode和vLink已经预先创建完成，所以在创建vNet时，除了根据之前所描述的vNet的参数，还应进一步参照已经创建的vNode和vLink来完成vNet的创建，具体而言，在创建的过程中需要参照vNet名称、包含的vNode列表，其中，对于vNode之间的所有虚拟链路vLink自动归属于该vNet。或者，在本实施例中，也可以先根据vNet的参数创建vNet，之后再将已经创建的vNode和vLink加入到vNet中。
其中，上述虚拟端口包括：虚拟网络节点端口(vNNI)、以及虚拟用户网络端口(vUNI)。网元(Node)是构成网络的核心元素，vNode则构成vNet。从网络角度看，Node对外部呈现的能力主要体现为网元的网络节点端口(NNI)和用户网络端口(UNI)能力，因此，基于物理网元(Node)创建vNode的过程可以理解为是Node的虚拟化切片，为了实现该目的，首先要解决其端口的虚拟化，也可以理解为是对于端口的切片。如图2所示，物理网元Node1包含UNI、NNI端口，Node1切片后形成的虚拟网元分别用于组建不同的虚拟网络vNet1和vNet2，即Node1切片后形成的虚拟网元在对应vNet(vNet 1和vNet 2)中分别为虚拟网元vNode1@vNet1和虚拟网元vNode1@vNet2。虚拟网元vNode1@vNet1包含了切片后的虚拟端口vUNI1@UNI1和vNNI1@NNI1，虚拟网元vNode1@vNet2包含了切片后的虚拟端口vUNI2@UNI1和vNNI2@NNI1。
vUNI可以根据相应配置，对UNI入口(Ingress)进入vNet的业务流进行识别和过滤。vNNI用于后续创建vNode之间的链路vLink。
此外，在创建vLink的步骤中，可以根据用户提供的虚拟端口参数，通过建立虚拟管道或隧道(Tunnel)的方式在vNode的vNNI之间创建vLink， 实现虚拟网络拓扑重构。网络的拓扑可以根据用户的需求来建立，这种虚拟网络的拓扑并不局限于物理网络拓扑。不仅如此，在vLink创建步骤中，根据用户提供的虚拟端口参数确定隧道创建的需求，根据隧道创建的需求生成隧道创建命令，并将隧道创建命令发送至SDN控制器，创建命令中包含隧道创建的需求，其中，虚拟端口参数包括以下至少之一：A-Z端点的vNNI的端口信息(包括带宽信息)、路由策略(例如，最短路径或负载均衡等)、路由约束(例如，必经节点、必经链路、排斥节点、排斥链路等)、保护方式(包括路径保护或重路由保护等)；根据SDN控制器返回的隧道ID，创建vLink与隧道之间的映射关系并生成vLink ID(即，完成虚拟资源和物理资源的映射)。
在上述创建vLink的过程中，在收到创建命令后，SDN控制器将会根据隧道创建命令中包含的隧道创建的需求，计算隧道的路由以及交叉连接(CrossConnection)的配置参数(包括各个交叉节点的入端口和出端口等参数)，在NNI上预留带宽资源，并将交叉连接创建命令发送至网络设备(Network Element，简称为NE)，交叉连接创建命令中包含交叉连接的配置参数以及预留的带宽资源的信息；NE，配置为利用预留的带宽资源、根据交叉连接创建命令中所包含的交叉连接的配置参数创建交叉连接，并将创建的交叉连接的ID发送至SDN控制器；在NE完成交叉连接创建后(即，预留的资源已经分配)，SDN控制器根据创建的交叉连接的参数以及NE返回的交叉连接的参数，创建隧道与交叉连接之间的包含关系，并返回隧道ID。
Link是构成网络内部连接和网络拓扑的关键元素。vLink是vNode之间通过vNNI的虚拟链路。如图3所示，Link1是物理网元Node1和Node2之间的链路，Link2是物理网元Node2和Node3之间的链路。Node1、Node2、Node3虚拟化切片之后，可按需在其vNNI之间通过建立虚拟管道或隧道的 方法形成虚拟链路，以构成所需的虚拟网络拓扑，实现虚拟网络的拓扑重构。图3中，vLink1是vNode1和vNode3之间的虚拟链路，vLink2是vNode1和vNode2之间的虚拟链路，vLink3是vNode2和vNode3之间的虚拟链路。
vLink的具体实现技术取决于Node转发面技术。对于支持灵活以太网(Flex Ethernet)的分组设备网元，vLink可以是Flex Ethernet管道；对于支持多协议标签交换传送应用(MPLS-TP，Multi-Protocol Label Switching Transport Profile)的分组设备网元，vLink可以是MPLS-TP标签交换路径(LSP，Label Switching Path)隧道；对于支持光传送网(OTN，Optical Transport Network)的设备网元，vLink可以是光通路数据单元(ODUk)管道。本发明实施例提出的传送网虚拟网络创建模型(即，网络切片模型)和方法具有通用性，可适用于采用上述各种转发面技术的设备网元。
在vLink创建成功后，SDN控制器和网元侧生成相应的vLink、vLink标识(ID)、以及工作路径路由信息，或进一步生成保护路径路由信息，并在工作路径、保护路径沿路由上各Node的网络节点端口NNI上预留带宽资源。
由于vNet是vNode和vLink的集合，所以在图3所示框图中，可以认为vNet1由vNode1@vNet1和vNode3@vNet1等虚拟网元，及vLink1@vNet1等虚拟链路构成；vNet2由vNode1@vNet2、vNode2@vNet2和vNode3@vNet2等虚拟网元，及vLink2@vNet2、vLink3@vNet2等虚拟链路构成。
此外，在一个实施例中，针对vNode的创建，上述虚拟网元的虚拟端口参数包括以下至少之一：vNode名称、vNode所属Node的ID(由于vNode是通过对Node进行虚拟化创建得到的，所以可以将Node理解为vNode的宿主)、vNode所属的vNet的ID、vNode包含的vNNI的端口参数、vNode包含的vUNI的端口参数；其中，vNNI的端口参数包括各vNNI所属的网 络节点端口(NNI)的ID和vNNI的分配带宽；vUNI的端口参数包括各vUNI所属的用户网络端口(UNI)的ID和vUNI的分配带宽。vNNI的端口参数和vUNI的端口参数可以保存在各自的端口属性列表中。
此外，在创建vNode和虚拟端口的步骤中，
将虚拟网元的虚拟端口参数发送至SDN控制器；
根据SDN控制器返回的端口ID创建vNode的对象实例并生成vNode ID；
其中，SDN控制器配置为根据虚拟端口参数创建vNNI和vUNI的对象实例，以及配置为对vNode、vNNI和vUNI预留资源并生成与vNNI和vUNI对应的端口ID，其中，在对vNNI和vUNI预留资源时，SDN控制器配置为在vNNI、vUNI所属的NNI、UNI上预留带宽资源。
此外，在创建Node和虚拟端口的步骤之后，可以进一步执行以下步骤中的至少之一：修改已创建的vNode的名称、添加或删除vNode所包含的vNNI和/或vUNI、修改vNode所包含的vNNI的端口带宽、修改vNode所包含的vUNI的端口带宽。
此外，在完成vNet创建之后，可以基于已经创建的vNet创建业务，这些业务包括但不限于以下至少之一：L2VPN、L3VPN。其创建业务的过程和在物理网络上的创建过程一样。vNet的业务配置等特征和物理网络相同。
此外，在vNet创建步骤之后，可以执行以下步骤中的至少之一：生成相应的vNet ID、修改vNet名称、添加或删除vNet所包含的vNode。
对于传统的传送网而言，网络架构按层次分为物理网络层、业务层、客户层，物理网络层之上就是业务层，即业务是直接加载于物理网络之上的。而基于本发明实施例提出的网络切片模型和方法，在业务层和物理网络层之间增加了切片之后的虚拟网络层。采用根据本发明实施例的虚拟网络创建(切片)方案后，得到的网络架构如图4所示。参照图4可以看出， 根据本发明实施例提出的切片方案进行切片后，得到的网络架构具有以下特点：
(1)虚拟网络层位于业务层和物理网络层之间，实现了业务层与物理网络层的解耦，业务层不需要感知物理网络。
(2)切片形成的虚拟网络具有类似物理网络的特征。对业务层而言，其感知到的虚拟网络和物理网络类似。
(3)切片和业务解耦，切片不依赖于业务。和物理网络类似，虚拟网络的创建先于业务创建，然后业务再加载于虚拟网络之上，并且业务可灵活创建、调整。
(4)业务层的业务创建基于虚拟网络。基于vNet，可以进一步创建各种业务，如L2VPN、L3VPN等。
根据本发明的实施例，还提供了一种虚拟网络创建装置、具体是提供一种基于SDN的传送网虚拟网络创建装置(该装置能够在物理网络基础上，创建多个虚拟网络，因此也可以被理解为用于对传送网进行网络切片的装置)，如图5所示，包括：
vNode创建模块51，配置为根据虚拟网元的虚拟端口参数创建虚拟网元vNode和虚拟端口；其中，所述虚拟端口参数由用户提供；
vLink创建模块52，配置为根据虚拟端口参数，在vNode的虚拟端口之间创建虚拟链路vLink；其中，虚拟网元和虚拟链路组成虚拟网络vNet。
在创建vNode、虚拟端口以及vLink的过程中，根据本发明实施例传送网网络创建装置需要与SDN通信。当根据本发明实施例传送网虚拟网络创建装置嵌入在SDN控制器中的情况下，该装置通过内部接口接入SDN控制器；在传送网虚拟网络创建装置独立于SDN控制器实现的情况下，该装置将通过南向接口模块接入SDN控制器。
此外，上述虚拟端口包括：虚拟网络节点端口vNNI和虚拟用户网络端 口vUNI。
vLink创建模块52配置为根据用户提供的虚拟端口参数，通过建立虚拟管道或隧道的方式在vNode的vNNI之间创建vLink，实现虚拟网络拓扑重构；
并且，VLink创建模块52配置为根据用户提供的虚拟端口参数确定隧道创建的需求，根据所述隧道创建的需求生成隧道创建命令，并将隧道创建命令发送至SDN控制器，创建命令中包含隧道创建的需求，其中，虚拟端口参数包括以下至少之一：A-Z端点的vNNI的端口信息、路由策略、路由约束、保护方式；并且，根据本发明实施例的传送网虚拟网络创建装置还包括：虚拟-物理资源映射模块(未示出)，配置为创建vNode与Node的映射关系，以及根据SDN控制器返回的隧道ID，创建vLink与隧道之间的映射关系。具体而言，vLink创建模块52配置为生成vLink ID，虚拟-物理资源映射模块可以在vLink ID与隧道ID之间建立映射关系。
此外，上述SDN控制器配置为根据隧道创建命令中包含的隧道创建的需求计算隧道的路由以及交叉连接的配置参数，在NNI上预留带宽资源，并将交叉连接创建命令发送至网络设备NE，交叉连接创建命令中包含交叉连接的配置参数以及预留的带宽资源的信息；SDN控制器还配置为在NE成功创建交叉连接的情况下，根据交叉连接的配置参数以及NE返回的交叉连接的ID，创建隧道与交叉连接之间的包含关系并生成隧道ID；并且，NE配置为利用预留的带宽资源、根据交叉连接创建命令中所包含的交叉连接的配置参数创建交叉连接，并将创建的交叉连接的ID发送至SDN控制器。
此外，对于vNode创建的步骤，上述虚拟网元的虚拟端口参数包括以下至少之一：
vNode名称、vNode所属Node的ID、vNode所属vNet的ID、vNode包含的vNNI的端口参数、vNode包含的vUNI的端口参数；其中，vNNI 的端口参数包括各vNNI所属的网络节点端口NNI的ID和vNNI的分配带宽，vUNI的端口参数包括各vUNI所属的用户网络端口UNI的ID和vUNI的分配带宽。
在创建vNode时，vNode创建模块51配置为将虚拟网元的虚拟端口参数发送至SDN控制器；以及配置为根据SDN控制器返回的端口ID创建vNode的对象实例并生成vNode ID；其中，SDN控制器配置为根据虚拟端口参数创建vNNI和vUNI的对象实例，以及配置为对vNode、vNNI和vUNI预留资源并生成与vNNI和vUNI对应的端口ID，其中，在对vNNI和vUNI预留资源时，SDN控制器配置为在vNNI、vUNI所属的NNI、UNI上预留带宽资源。
在一个实施例中，根据本发明实施例的传送网虚拟网络创建装置嵌入在SDN控制器中，此时，根据本发明实施例的传送网虚拟网络创建装置通过内部接口接入SDN控制器。在另一实施例中，根据本发明的传送网虚拟网络创建装置独立于SDN控制器实现，此时，根据本发明实施例的传送网虚拟网络创建装置通过南向接口模块接入SDN控制器。
由于根据本发明实施例的传送网虚拟网络创建装置具有资源映射和生命周期管理的功能，所以其功能上与SDN控制器完全独立，这样，当在系统中采用根据本发明实施例的传送网虚拟网络创建装置时，能够避免对已有系统进行过多改进，具有良好的兼容性。
此外，根据本发明实施例的上述传送网虚拟网络创建装置还包括：vNet创建模块，配置为创建vNet；
其中，在vNet先于vNode和/或vLink创建的情况下，vNet创建模块配置为根据vNet的参数创建vNet，并在vNode和/或vLink创建时或创建完成后，将创建的vNode和/或vLink加入vNet中；或者
在vNet晚于vNode和vLink创建的情况下，vNet创建模块配置为根据 vNet的参数中包含已创建的vNode和vLink列表创建vNet。
此外，上述vNode创建模块51、vLink创建模块52以及vNet创建模块设置于生命周期管理模块中，生命周期管理模块配置为执行以下功能的至少之一：修改已创建的vNode的名称、添加或删除vNode所包含的vNNI和/或vUNI、修改vNode所包含的vNNI和vUNI的端口带宽、修改vNode所包含的vUNI的端口带宽、生成相应的vNet ID、修改vNet名称、添加或删除vNet所包含的vNode。其中，生命周期管理模块配置为执行以下功能的至少之一：修改已创建的vNode的名称、添加或删除vNode所包含的vNNI和/或vUNI、修改vNode所包含的vNNI的端口带宽、修改vNode所包含的vUNI的端口带宽、生成相应的vNet ID、修改vNet名称、添加或删除vNet所包含的vNode。
此外，在一个实施例中，根据本发明实施例的上述装置可以还包括：
北向接口模块，配置为向上层控制器或应用提供vNet的控制接口，基于已经创建的vNet，可以创建多种类型的业务，这些业务类型可以包括以下至少之一：L2VPN、L3VPN。
图6是根据本发明实施例的基于SDN的传送网络系统的框图。如图6所示，该系统包括vNet管理器(相当于之前描述的传送网虚拟网络创建装置，也可以称为vNet管理程序，即，图6中所示的vNet Hypervisor)和SDN控制器。从系统层面划分角度来看，其中所示的系统包括业务控制层、切片控制层(虚拟化层)以及物理网络控制器层。
继续参见图6，SDN控制器(SDN Controller)位于物理网络控制层，负责物理网络的控制，SDN控制器能够向各个网络设备(Network Element)发送命令，控制各个NE完成创建交叉连接等操作。vNet管理程序位于切片控制层(虚拟化层)中，负责对物理网络的切片控制(虚拟化)。vNet Hypervisor则包括：虚拟-物理资源映射模块(virtual-physical resource  mapping)，配置为虚拟资源和物理资源的映射；vNet生命周期管理模块(vNet lifecycle mgmt)，配置为虚拟网络vNet及其包含的vNode、vLink等虚拟资源的创建及生命周期管理，因此，可以理解为，vNet生命周期管理模块包含了上述的vNode创建模块、vLink创建模块以及vNet创建模块，这些模块以及vNet Hypervisor所包含的其他模块的功能之前已经说明，这里不再赘述。
另外，根据本发明实施例的vNet Hypervisor还可以包括北向接口模块(NBI)，配置为向上层的controller或APP提供vNet的控制接口。
在具体实现上，vNet Hypervisor可以是SDN Controller之上的独立系统，也可以是内嵌在SDN Controller中的内部组件。如果vNet Hypervisor作为SDN Controller之上的独立系统实现，vNet Hypervisor可以通过南向接口模块(SBI)接入下层的SDN Controller。
继续参见图6，因虚拟网络vNet和物理网络类似，因此在业务控制层的SDN Controller(vNet)对vNet的控制也类似对物理网络的控制。一个SDN Controller(vNet)实例或APP对应一个vNet的控制，以实现不同vNet控制面的隔离。
此外，图6中的Administrator是控制器的管理者，负责向控制器下发各种配置命令。各控制器可以有统一的Administrator，也可以有各自独立的Administrator。另外，如果有上层的Orchestrator(编排器)，其也可以向控制器下发网络切片的配置命令，下文中的Administrator也可替换为Orchestrator。
下面将以图6所示的系统为例，描述根据本发明实施例的各个创建过程。
如图7所示，创建vNet的过程具体可以包括以下步骤：
1.Administrator向vNet Hypervisor发送命令Create vNet，包括以下参 数：vNet名称、包含的vNode列表(对于vNode之间的所有虚拟链路vLink自动归属于该vNet)；
2.vNet Hypervisor创建vNet成功后，生成相应的vNetID，并向Administrator返回vNet创建成功应答，及vNetID；
在该过程中，vNet只是在vNet Hypervisor上建立的vNode和vLink的逻辑集合，因此SDN Controller和Network Element可不用感知vNet。
如图8所示，创建vNode的过程具体可以包括以下步骤：
1.Administrator向vNet Hypervisor发送命令Create vNode，该命令中包含以下参数：vNode名称、所属NodeID、所属vNet的ID、vNNI端口及属性列表(包括各vNNI所属的NNI ID和vNNI的分配带宽)、vUNI端口及属性列表(包括各vUNI所属的UNI ID和vUNI的分配带宽)；
2.vNet Hypervisor向SDN Controller发送命令Create vPort request，包含以下参数：vNNI端口及属性列表(包括各vNNI所属的NNI ID和vNNI的分配带宽)、vUNI端口及属性列表(包括各vUNI所属的UNI ID和vUNI的分配带宽)；
3.SDN Controller创建vNNI、vUNI对象实例，生成相应的vNNI ID、vUNI ID,并在相应的NNI、UNI上为vNNI、vUNI预留带宽资源。SDN Controller向vNet Hypervisor返回vPort创建成功应答，及vNNI ID、vUNI ID；4.vNet Hypervisor创建vNode对象实例(包含相应的vNNI ID和vUNI ID)，以及生成vNodeID，并向Administrator返回vNode创建成功应答，及vNodeID。
如图9所示，创建vLink的过程具体可以包括以下步骤：
1.Administrator向vNet Hypervisor发送命令Create vLink，包含以下参数：A-Z端点vNNI(vNNI中包含了带宽信息)、路由策略(如最短路径或负载均衡等)、路由约束(如必经节点、必经链路等)、保护方式(路径1+1/1:1 保护或重路由保护等)；
2.vNet Hypervisor将vLink的创建需求转换为创建Tunnel的需求，并向SDN Controller发送命令Create Tunnel Request，参数同上；
3.SDN Controller计算Tunnel的路由，及路由上网元的CrossConnection配置参数，并在相应NNI端口上预留带宽资源。具体的CrossConnection参数和Node配置参数，依赖于Tunnel类型，例如，LSP Tunnel或ODUk Tunnel等；
4.根据计算结果，SDN Controller向各Network Element发送命令Create CrossConnection；
5.各Network Element完成Cross Connection创建及相应的配置及资源预留，并向SDN Controller返回Cross Connection创建成功应答及Cross Connection ID；
6.SDN Controller创建Tunnel与Cross Connection的包含关系，生成Tunnel ID，并向vNet Hypervisor返回Tunnel创建成功应答，及TunnelID；7.vNet Hypervisor创建vLink与Tunnel的包含关系，生成vLinkID，并向Administrator返回vLink创建成功应答，及vLinkID。
图10是根据本发明实施例的网络切片过程的具体实现流程图，包括以下步骤：
步骤S101，管理者向vNet Hypervisor下发命令创建vNet实例。
命令参数为
Figure PCTCN2018077854-appb-000001
步骤S102，管理者向vNet Hypervisor下发命令，创建vNode1@vNet1， 命令参数为
Figure PCTCN2018077854-appb-000002
步骤S103，vNet Hypervisor向SDN Controller下发命令，创建vNNI1@NNI1、vUNI1@UNI1，命令参数为：
Figure PCTCN2018077854-appb-000003
Figure PCTCN2018077854-appb-000004
步骤S104，vNet Hypervisor收到SDN Controller成功应答后，生成vNode实例，返回vNodeID＝1。
步骤S105，管理者向vNet Hypervisor下发命令，创建vNode3@vNet1，命令参数为
Figure PCTCN2018077854-appb-000005
Figure PCTCN2018077854-appb-000006
步骤S106，vNet Hypervisor向SDN Controller下发命令，创建vNNI1@NNI1、vUNI1@UNI1，命令参数为:
Figure PCTCN2018077854-appb-000007
步骤S107，vNet Hypervisor收到SDN Controller成功应答后，生成vNode实例，返回vNodeID＝3。
步骤S108，管理者向vNet Hypervisor下发命令，创建vLink1@vNet1，命令参数为
Figure PCTCN2018077854-appb-000008
步骤S109，vNet Hypervisor将创建vLink1@vNet1的请求，转换为创建ODU2管道的命令，发给SDN Controller。
命令参数为:
Figure PCTCN2018077854-appb-000009
Figure PCTCN2018077854-appb-000010
步骤S110，SDN Controller基于物理拓扑计算vLink1@vNet1的路由为Node1-Node2-Node3，并计算出Node2内部的光通道数据单元ODU2时隙交叉。
步骤S111，SDN Controller向网元Node2下发创建ODU2CrossConnection命令。
步骤S112，Node2完成ODU2CrossConnection创建，生成CrossConnection＝1，并返回创建成功应答及CrossConnectionID＝1。
步骤S113，SDN Controller收到网元Node2成功应答后建立ODU2Tunnel与CrossConnection的包含关系，生成ODU2的TunnelID＝1,并向vNet Hypervisor返回Tunnel创建成功应答，及TunnelID＝1。
步骤S114，vNet Hypervisor创建vLink与Tunnel的包含关系，生成vLinkID＝1，并向Administrator返回vLink创建成功应答，及vLinkID＝1。
综上所述，本发明实施例所述的方案能够根据承载不同业务类型或不同租户而将物理网络切片成相应的虚拟网络(例如，按照政企客户、家庭客户、或者增强移动宽带eMBB业务、超高可靠性与低延时uRLLC业务、大规模物联网mMTC业务进行切片)，每一个虚拟传送网都具有类似物理网络的特征。对其承载的业务而言，业务感知到的虚拟网络和物理网络类似，从而有效满足不同类型业务需求。相对于建设不同的物理网络平面，本发明实施例在物理网络资源共享的基础上进行虚拟网络切片，避免了重复建网带来的投资大、成本高、利用率低等问题。不仅如此，和物理网络类似，基于彼此独立的切片虚拟网络，可以再创建需要的各种业务，例如 L2VPN、L3VPN等，能够让资源利用率更高、调度更加灵活，让管理、运维以及业务部署更加容易，从而有效解决了现有技术中存在的问题。
此外，根据本发明实施例的上述基于SDN的传送网虚拟网络创建方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明实施例的所述方法可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台设备(可以是基站等网络设备)执行本发明实施例所述的方法。
根据本发明的另一实施例，还提供了一种虚拟网络创建设备。该虚拟网络创建设备包括：存储器及处理器，其中存储器上存储有可在处理器上运行的计算机程序，该计算机程序被处理器执行时实现以下步骤：根据用户提供的虚拟网元的虚拟端口参数创建vNode和虚拟端口；根据虚拟端口参数，在vNode的虚拟端口之间创建vLink；其中，虚拟网元和虚拟链路组成vNet。
其中，上述虚拟端口包括：vNNI和vUNI。
此外，根据虚拟端口参数，在vNode的虚拟端口之间创建vLink的步骤具体包括：
根据用户提供的虚拟端口参数，在vNode的vNNI之间创建vLink，实现虚拟网络拓扑重构。
此外，根据虚拟端口参数，在vNode的虚拟端口之间创建虚拟链路vLink的步骤具体包括：
根据用户提供的虚拟端口参数确定隧道创建的需求，根据所述隧道创建的需求生成隧道创建命令，并将隧道创建命令发送至SDN控制器，创建命令中包含隧道创建的需求，其中，虚拟端口参数包括以下至少之一：A-Z端点的vNNI的端口信息、路由策略、路由约束、保护方式；
根据SDN控制器返回的隧道ID，创建vLink与隧道之间的映射关系并生成vLink ID。
在一个实施例中，上述SDN控制器配置为根据隧道创建命令中包含的隧道创建的需求计算隧道的路由以及交叉连接的配置参数，在NNI上预留带宽资源，并将交叉连接创建命令发送至网络设备(NE)，交叉连接创建命令中包含交叉连接的配置参数以及预留的带宽资源的信息；SDN控制器还配置为在NE成功创建交叉连接的情况下，根据交叉连接的配置参数以及NE返回的交叉连接的ID，创建隧道与交叉连接之间的包含关系并生成隧道ID；
并且，上述NE配置为利用预留的带宽资源、根据交叉连接创建命令中所包含的交叉连接的配置参数创建交叉连接，并将创建的交叉连接的ID发送至SDN控制器。
此外，上述虚拟网元的虚拟端口参数包括以下至少之一：
vNode名称、vNode所属Node的ID、vNode所属的vNet的ID、vNode包含的vNNI的端口参数、vNode包含的vUNI的端口参数；其中，vNNI的端口参数包括各vNNI所属的网络节点端口NNI的ID和vNNI的分配带宽，vUNI的端口参数包括各vUNI所属的用户网络端口UNI的ID和vUNI的分配带宽。
在一个实施例中，根据用户提供的虚拟网元的虚拟端口参数创建vNode和虚拟端口的步骤具体包括：
将虚拟网元的虚拟端口参数发送至SDN控制器；
根据SDN控制器返回的端口ID创建vNode的对象实例并生成vNode ID；
其中，SDN控制器配置为根据虚拟端口参数创建vNNI和vUNI的对象实例，以及配置为对vNode、vNNI和vUNI预留资源并生成与vNNI和vUNI 对应的端口ID，其中，在对vNNI和vUNI预留资源时，SDN控制器配置为在vNNI、vUNI所属的NNI、UNI上预留带宽资源。
此外，在根据用户提供的虚拟网元的虚拟端口参数创建虚拟网元vNode和虚拟端口之后，该计算机程序被处理器执行时还实现以下步骤中的至少之一：
修改已创建的vNode的名称、添加或删除vNode所包含的vNNI和/或vUNI、修改vNode所包含的vNNI和vUNI的端口带宽。
此外，该计算机程序被处理器执行时还实现以下步骤：创建vNet；
其中，在vNet先于vNode和/或vLink创建的情况下，则根据vNet的参数创建vNet，并在vNode和/或vLink创建时或创建完成后，将创建的vNode和/或vLink加入vNet中；或者，
在vNet晚于vNode和vLink创建的情况下，则根据vNet的参数中包含已创建的vNode和vLink列表创建vNet；或者，根据vNet的参数创建vNet，之后将已创建的vNode和vLink加入到创建的所述vNet中。
此外，在创建vNet之后，该计算机程序被处理器执行时还实现以下步骤：
生成相应的vNet ID、修改vNet名称、添加或删除vNet所包含的vNode。
此外，在创建vNet之后，根据本发明实施例的上述方法还包括：基于已经创建的vNet创建业务，这些业务包括但不限于以下至少之一：L2VPN、L3VPN
根据本发明的另一实施例，还提供了一种计算机存储介质(该存储介质可以是ROM、RAM、硬盘、可拆卸存储器等)，该存储介质中存储有用于进行网络创建步骤的计算机程序，该计算机程序具有被配置用于执行以下步骤的代码段：根据虚拟网元的虚拟端口参数创建虚拟网元和虚拟端口；根据虚拟端口参数，在虚拟网元的虚拟端口之间创建虚拟链路；其中，虚拟网元和虚拟链路组成虚拟网络。
根据本发明的另一实施例，还提供了一种计算机程序，该计算机程序具有被配置用于执行以下网络创建步骤的代码段：根据虚拟网元的虚拟端口参数创建虚拟网元和虚拟端口；根据虚拟端口参数，在虚拟网元的虚拟端口之间创建虚拟链路；其中，虚拟网元和虚拟链路组成虚拟网络。
通过具体实施方式的说明，应当可对本发明为达成预定目的所采取的技术手段及功效得以更加深入且具体的了解，然而所附图示仅是提供参考与说明之用，并非用来对本发明加以限制。
工业实用性
本发明实施例在物理网络资源共享的基础上进行虚拟网络切片，避免了重复建网带来的投资大、成本高、利用率低等问题。此外，和物理网络类似，基于彼此独立的切片虚拟网络，可以再创建需要的各种业务，例如L2VPN、L3VPN等，能够让资源利用率更高、调度更加灵活，让管理、运维以及业务部署更加容易，从而有效解决了现有技术中存在的问题。

Claims (20)

  1. 一种虚拟网络创建方法，所述方法包括：
    根据虚拟网元的虚拟端口参数创建虚拟网元vNode和虚拟端口；
    根据所述虚拟端口参数，在所述vNode的虚拟端口之间创建虚拟链路vLink；其中，所述虚拟网元和所述虚拟链路组成虚拟网络vNet。
  2. 根据权利要求1所述的虚拟网络创建方法，其中，所述虚拟端口包括：虚拟网络节点端口vNNI和虚拟用户网络端口vUNI。
  3. 根据权利要求2所述的虚拟网络创建方法，其中，根据所述虚拟端口参数，在所述vNode的虚拟端口之间创建vLink包括：
    根据所述虚拟端口参数，在所述vNode的vNNI之间创建所述vLink。
  4. 根据权利要求2所述的虚拟网络创建方法，其中，根据所述虚拟端口参数，在所述vNode的虚拟端口之间创建虚拟链路vLink包括：
    根据用户提供的所述虚拟端口参数确定隧道创建的需求，根据所述隧道创建的需求生成隧道创建命令，并将所述隧道创建命令发送至SDN控制器，其中，所述虚拟端口参数包括以下至少之一：A-Z端点的vNNI的端口信息、路由策略、路由约束、保护方式；
    根据所述SDN控制器返回的隧道标识ID，创建vLink与隧道之间的映射关系并生成vLink ID。
  5. 根据权利要求4所述的虚拟网络创建方法，其中，所述SDN控制器，配置为根据所述隧道创建命令中包含的所述隧道创建的需求，计算隧道的路由以及交叉连接的配置参数，在网络节点端口NNI上预留带宽资源，并将交叉连接创建命令发送至网络设备NE，所述交叉连接创建命令中包含所述交叉连接的配置参数以及预留的带宽资源的信息；
    所述SDN控制器，还配置为在所述NE成功创建交叉连接的情况下，根据所述交叉连接的配置参数以及所述NE返回的交叉连接的ID，创建隧 道与所述交叉连接之间的包含关系并生成隧道ID；
    所述NE，配置为利用预留的所述带宽资源、根据所述交叉连接创建命令中所包含的所述交叉连接的配置参数创建交叉连接，并将创建的交叉连接的ID发送至所述SDN控制器。
  6. 根据权利要求2所述的虚拟网络创建方法，其中，所述虚拟网元的虚拟端口参数包括以下至少之一：
    vNode名称、vNode所属Node的ID、vNode所属的vNet的ID、vNode包含的vNNI的端口参数、vNode包含的vUNI的端口参数；其中，vNNI的端口参数包括各vNNI所属的网络节点端口NNI的ID和vNNI的分配带宽，vUNI的端口参数包括各vUNI所属的用户网络端口UNI的ID和vUNI的分配带宽。
  7. 根据权利要求6所述的虚拟网络创建方法，其中，所述根据虚拟网元的虚拟端口参数创建虚拟网元vNode和虚拟端口包括：
    将所述虚拟网元的虚拟端口参数发送至SDN控制器；
    根据所述SDN控制器返回的端口ID创建所述vNode的对象实例并生成vNode ID；
    其中，所述SDN控制器，配置为根据所述虚拟端口参数创建所述vNNI和所述vUNI的对象实例，以及配置为对所述vNode、所述vNNI和所述vUNI预留资源并生成与所述vNNI和所述vUNI对应的所述端口ID，其中，在对所述vNNI和所述vUNI预留资源时，所述SDN控制器，配置为在所述vNNI、所述vUNI所属的NNI、UNI上预留带宽资源。
  8. 根据权利要求2所述的虚拟网络创建方法，其中，在根据虚拟网元的虚拟端口参数创建虚拟网元vNode和虚拟端口之后，所述方法还包括以下步骤中的至少之一：
    修改已创建的vNode的名称、添加或删除vNode所包含的vNNI和/或 vUNI、修改vNode所包含的vNNI和vUNI的端口带宽。
  9. 根据权利要求1所述的虚拟网络创建方法，其中，所述方法还包括：
    创建vNet；
    其中，在所述vNet先于所述vNode和/或所述vLink创建的情况下，则根据vNet的参数创建vNet，并在vNode和/或vLink创建时或创建完成后，将创建的所述vNode和/或所述vLink加入所述vNet中；或者
    在所述vNet晚于所述vNode和所述vLink创建的情况下，则根据vNet的参数、以及已创建的所述vNode和所述vLink列表创建所述vNet；或者，根据vNet的参数创建vNet，之后将已创建的所述vNode和所述vLink加入到创建的所述vNet中。
  10. 根据权利要求9所述的虚拟网络创建方法，其中，在创建vNet之后，所述方法还包括：基于创建的所述vNet创建业务，所述业务包括以下至少之一：二层虚拟专用网L2VPN、三层虚拟专用网L3VPN。
  11. 根据权利要求1所述的虚拟网络创建方法，其中，在创建vNet之后，所述方法还包括：
    生成相应的vNet ID、修改vNet名称、添加或删除vNet所包含的vNode。
  12. 根据权利要求1至11任一项所述的虚拟网络创建方法，所述虚拟链路vLink为灵活以太网管道、多协议标签交换传送应用MPLS-TP标签交换路径LSP隧道、和光通路数据单元ODUk管道中的至少一种。
  13. 一种虚拟网络创建装置，所述装置包括：
    vNode创建模块，配置为根据虚拟网元的虚拟端口参数创建虚拟网元vNode和虚拟端口；
    vLink创建模块，配置为根据所述虚拟端口参数，在所述vNode的虚拟端口之间创建虚拟链路vLink；其中，所述虚拟网元和所述虚拟链路组成虚拟网络vNet。
  14. 根据权利要求13所述的虚拟网络创建装置，其中，所述虚拟端口包括：虚拟网络节点端口vNNI和虚拟用户网络端口vUNI。
  15. 根据权利要求13或14所述的虚拟网络创建装置，其中，所述vLink创建模块，配置为根据用户提供的所述虚拟端口参数确定隧道创建的需求，根据所述隧道创建的需求生成隧道创建命令，并将所述隧道创建命令发送至SDN控制器，其中，所述虚拟端口参数包括以下至少之一：A-Z端点的vNNI的端口信息、路由策略、路由约束、保护方式；
    并且，所述传送网虚拟网络创建装置还包括：
    虚拟-物理资源映射模块，配置为创建vNode与Node的映射关系，以及根据所述SDN控制器返回的隧道ID，创建vLink与隧道之间的映射关系。
  16. 一种传送网络系统，包括vNet管理器和SDN控制器；其中，
    所述vNet管理器，配置为根据虚拟网元的虚拟端口参数创建虚拟网元vNode和虚拟端口；根据所述虚拟端口参数，在所述vNode的虚拟端口之间创建虚拟链路vLink；其中，所述虚拟网元和所述虚拟链路组成虚拟网络vNet；
    所述SDN控制器，配置为与所述vNet管理器通信，并协助所述vNet管理器完成vNode和vLink的创建。
  17. 根据权利要求16所述的传送网络系统，其中，
    在所述vNet管理器嵌入在所述SDN控制器中的情况下，所述vNet管理器通过内部接口接入所述SDN控制器；
    在所述vNet管理器独立于所述SDN控制器实现的情况下，所述vNet管理器通过南向接口模块接入所述SDN控制器。
  18. 根据权利要求16所述的传送网络系统，其中，所述虚拟端口包括：虚拟网络节点端口vNNI和虚拟用户网络端口vUNI。
  19. 一种虚拟网络创建设备，包括：存储器及处理器，所述存储器存 储有计算机程序，所述计算机程序被所述处理器执行时实现根据权利要求1至12中任一项所述的步骤。
  20. 一种计算机存储介质，存储有计算机程序，所述计算机程序用于执行权利要求1至12任一项所述的虚拟网络创建方法。
PCT/CN2018/077854 2017-05-04 2018-03-02 虚拟网络创建方法、装置、设备及传送网络系统、存储介质 WO2018201787A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP18793863.4A EP3621243B1 (en) 2017-05-04 2018-03-02 Virtual network creation method, apparatus and transport network system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710308230.8A CN108809794B (zh) 2017-05-04 2017-05-04 基于sdn的传送网虚拟网络创建方法和装置及传送网络系统
CN201710308230.8 2017-05-04

Publications (1)

Publication Number Publication Date
WO2018201787A1 true WO2018201787A1 (zh) 2018-11-08

Family

ID=64016404

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077854 WO2018201787A1 (zh) 2017-05-04 2018-03-02 虚拟网络创建方法、装置、设备及传送网络系统、存储介质

Country Status (3)

Country Link
EP (1) EP3621243B1 (zh)
CN (1) CN108809794B (zh)
WO (1) WO2018201787A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112804687A (zh) * 2019-11-14 2021-05-14 华为技术有限公司 一种资源分配方法、装置、系统及存储介质
CN114157932A (zh) * 2021-11-23 2022-03-08 中国联合网络通信集团有限公司 接入网络处理方法、装置、电子设备及存储介质
EP3886493A4 (en) * 2018-11-23 2022-08-17 ZTE Corporation METHOD AND DEVICE FOR IMPLEMENTING NETWORK SLICING AND CONTROL DEVICE

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021031986A1 (zh) * 2019-08-21 2021-02-25 烽火通信科技股份有限公司 一种承载网络快速切片的方法
CN112422310B (zh) * 2019-08-21 2022-01-11 烽火通信科技股份有限公司 一种承载网络快速切片的方法
CN111416747B (zh) * 2020-03-27 2021-11-19 鹏城实验室 一种网络分片控制方法及网络分片系统
CN113783738A (zh) * 2021-09-28 2021-12-10 浙江大学 一种高可扩展性的sdn北向接口实现方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103368764A (zh) * 2012-04-10 2013-10-23 中兴通讯股份有限公司 一种虚拟网络的实现方法及网络管理系统
CN103430498A (zh) * 2013-02-06 2013-12-04 华为技术有限公司 一种网络虚拟化的数据传输的方法、设备和路由系统
CN103746925A (zh) * 2013-12-13 2014-04-23 北京邮电大学 一种FiWi融合网络以及基于FiWi融合网络的通信方法
US20140301192A1 (en) * 2013-04-05 2014-10-09 Futurewei Technologies, Inc. Software Defined Networking (SDN) Controller Orchestration and Network Virtualization for Data Center Interconnection
CN105763356A (zh) * 2014-12-19 2016-07-13 中兴通讯股份有限公司 一种资源虚拟化处理的方法、装置及控制器

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103051565B (zh) * 2013-01-04 2018-01-05 中兴通讯股份有限公司 一种等级软件定义网络控制器的架构系统及实现方法
US9356871B2 (en) * 2013-03-15 2016-05-31 Cisco Technology, Inc. Programmable management engine for networks
CN103269282A (zh) * 2013-04-25 2013-08-28 杭州华三通信技术有限公司 网络配置自动部署方法和装置
CN104363159B (zh) * 2014-07-02 2018-04-06 北京邮电大学 一种基于软件定义网络的开放虚拟网络构建系统和方法
US10015115B2 (en) * 2015-06-01 2018-07-03 Ciena Corporation Software defined networking service control systems and methods of remote services
US10084657B2 (en) * 2015-06-29 2018-09-25 Ca, Inc. Normalized software-defined networking interface
CN105827665A (zh) * 2016-06-06 2016-08-03 南开大学 一种sdn网络控制器与交换机之间的流表消息敏感数据加密方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103368764A (zh) * 2012-04-10 2013-10-23 中兴通讯股份有限公司 一种虚拟网络的实现方法及网络管理系统
CN103430498A (zh) * 2013-02-06 2013-12-04 华为技术有限公司 一种网络虚拟化的数据传输的方法、设备和路由系统
US20140301192A1 (en) * 2013-04-05 2014-10-09 Futurewei Technologies, Inc. Software Defined Networking (SDN) Controller Orchestration and Network Virtualization for Data Center Interconnection
CN103746925A (zh) * 2013-12-13 2014-04-23 北京邮电大学 一种FiWi融合网络以及基于FiWi融合网络的通信方法
CN105763356A (zh) * 2014-12-19 2016-07-13 中兴通讯股份有限公司 一种资源虚拟化处理的方法、装置及控制器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3621243A4 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3886493A4 (en) * 2018-11-23 2022-08-17 ZTE Corporation METHOD AND DEVICE FOR IMPLEMENTING NETWORK SLICING AND CONTROL DEVICE
CN112804687A (zh) * 2019-11-14 2021-05-14 华为技术有限公司 一种资源分配方法、装置、系统及存储介质
US11558784B2 (en) 2019-11-14 2023-01-17 Huawei Technologies Co., Ltd. Resource allocation method, apparatus, and system, and storage medium
CN112804687B (zh) * 2019-11-14 2023-04-11 华为技术有限公司 一种资源分配方法、装置、系统及存储介质
CN114157932A (zh) * 2021-11-23 2022-03-08 中国联合网络通信集团有限公司 接入网络处理方法、装置、电子设备及存储介质
CN114157932B (zh) * 2021-11-23 2023-06-02 中国联合网络通信集团有限公司 接入网络处理方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN108809794A (zh) 2018-11-13
EP3621243B1 (en) 2023-06-28
EP3621243A1 (en) 2020-03-11
CN108809794B (zh) 2021-10-29
EP3621243A4 (en) 2021-01-27

Similar Documents

Publication Publication Date Title
WO2018201787A1 (zh) 虚拟网络创建方法、装置、设备及传送网络系统、存储介质
US11082262B2 (en) Flow entry generating method and apparatus
CN106936857B (zh) 一种混合云的连接管理方法、sdn控制器及混合云系统
RU2595540C9 (ru) Базовые контроллеры для преобразования универсальных потоков
EP2989749B1 (en) Network resource monitoring
CN103477612B (zh) 经扩展以连接网络层级的云服务控制和管理架构
CN102884763B (zh) 跨数据中心的虚拟机迁移方法、服务控制网关及系统
KR102653760B1 (ko) 네트워크 슬라이싱 구현 방법, 장치 및 컨트롤러
US20140279862A1 (en) Network controller with integrated resource management capability
US20150036480A1 (en) Policy-driven automatic redundant fabric placement mechanism for virtual data centers
WO2018000890A1 (zh) 用于实现组合虚拟专用网vpn的方法与装置
KR102237299B1 (ko) 트래픽 엔지니어링 서비스 매핑
WO2007134551A1 (fr) Procédé et dispositif noeud de réservation de ressources de réseau
US20130297752A1 (en) Provisioning network segments based on tenant identity
WO2016095493A1 (zh) 一种资源虚拟化处理的方法、装置及控制器
KR20120039912A (ko) 다계층 네트워크에서의 계층간 경로 설정 방법 및 시스템
WO2017162030A1 (zh) 一种虚拟网络的生成方法和装置
CN113206776A (zh) 混合云网络连接方法、系统及控制器
CN110336730A (zh) 一种网络系统及数据传输方法
WO2013174096A1 (zh) 一种云计算虚拟机迁移的方法、设备及系统
WO2018036521A1 (zh) 资源调整方法、装置及系统
CN114513447A (zh) Sd-wan业务发放系统、方法、装置和网络设备
US9344487B2 (en) Method for networking cPaaS components for application on-boarding
CN113068083B (zh) 一种建立连接的方法、装置、设备及计算机可读存储介质
Vilalta et al. Experimental validation of resource allocation in transport network slicing using the ADRENALINE testbed

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018793863

Country of ref document: EP

Effective date: 20191204