WO2020103902A1 - 实现网络切片的方法、装置和控制器 - Google Patents

实现网络切片的方法、装置和控制器

Info

Publication number
WO2020103902A1
WO2020103902A1 PCT/CN2019/119933 CN2019119933W WO2020103902A1 WO 2020103902 A1 WO2020103902 A1 WO 2020103902A1 CN 2019119933 W CN2019119933 W CN 2019119933W WO 2020103902 A1 WO2020103902 A1 WO 2020103902A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
virtual
tunnel
slicing
layer
Prior art date
Application number
PCT/CN2019/119933
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 KR1020217017771A priority Critical patent/KR102653760B1/ko
Priority to EP19886839.0A priority patent/EP3886493A4/en
Publication of WO2020103902A1 publication Critical patent/WO2020103902A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/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/12—Discovery or management of network topologies
    • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • This disclosure relates to, but is not limited to, the field of communications.
  • the bearer network network slicing can slice the physical network into corresponding virtual networks (for example, according to government and enterprise customers, household customers, and 5G eMBB (Enhance Mobile Broadband, enhanced mobile broadband) services, uRLLC ( Ultra Reliable & Low Latency Communication, ultra-reliable and low-latency communication) services, and mMTC (massive Machine Type of Communication) services, to meet the needs of different types of services.
  • virtual networks for example, according to government and enterprise customers, household customers, and 5G eMBB (Enhance Mobile Broadband, enhanced mobile broadband) services, uRLLC ( Ultra Reliable & Low Latency Communication, ultra-reliable and low-latency communication) services, and mMTC (massive Machine Type of Communication) services, to meet the needs of different types of services.
  • network slicing can achieve the sharing of physical network resources, avoid repeated construction, and greatly reduce the cost of network construction. And resource scheduling is more flexible, easy to manage, operation and maintenance and business deployment.
  • the network architecture is divided into a physical network layer, a business layer, and a client layer according to layers.
  • the physical network layer is the business layer, that is, the business is directly loaded on the physical network.
  • a virtual network layer after slicing is added between the business layer and the physical network layer.
  • the network architecture based on network slicing is shown in FIG. 1.
  • the virtual network layer (slicing layer) is located between the business layer and the physical network layer, which realizes the decoupling of the business layer and the physical network layer.
  • the business layer does not need to be aware of the physical network. For the business layer, the perceived virtual network is similar to the physical network.
  • the creation of slices is prior to the creation of business, and then the business is loaded on the slice, and the business can be flexibly created and adjusted. Based on vNet, you can further create various services, such as L2VPN (Layer 2 Virtual Private Networks, Layer 2 Virtual Private Network), L3VPN (Layer 3 Virtual Private Networks, Layer 3 Virtual Private Network), etc.
  • L2VPN Layer 2 Virtual Private Networks, Layer 2 Virtual Private Network
  • L3VPN Layer 3 Virtual Private Networks, Layer 3 Virtual Private Network
  • Each slice can meet the needs of its own business, and can be independently monitored and managed to provide resource isolation between slices.
  • a network slice vNet contains virtual nodes (vNode) and virtual links (vLink).
  • Figure 2 describes a method for implementing network slicing based on physical ports. As shown in Fig. 2, the solid line port and the dotted port respectively represent different slices, and two different network slices are created through resource virtualization.
  • vNet1 The abstraction of the network cannot be fully realized. For example, users of vNet1 only need to care about four PE (Provider Edge) nodes, and do not need to be aware of intermediate P nodes, but port-based slicing does not have the ability to abstract the network. Only the complete topology can be presented to slice users.
  • PE Provide Edge
  • An embodiment of the present disclosure provides a method for implementing network slicing, which creates one or more nested network slicing layers between a physical network layer and a business layer, where each network in the network slicing layer is created by Slicing: creating multiple virtual network elements; creating a virtual link between virtual network elements based on a tunnel; establishing an inclusion relationship between the network slice and the virtual network elements and virtual links.
  • An embodiment of the present disclosure also provides an apparatus for implementing network slicing, including: a network element creation module for creating multiple virtual network elements; a link creation module for creating a virtual link between virtual network elements based on a tunnel Road; slice creation module, used to establish the inclusion relationship between the network slice and the virtual network element and virtual link.
  • An embodiment of the present disclosure also provides a controller, including a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor implements the program to implement the method for implementing network slicing.
  • Embodiments of the present disclosure also provide a computer-readable storage medium that stores computer-executable instructions, which are used to execute the method for implementing network slicing when executed by a processor.
  • Figure 1 is a schematic diagram of a network architecture model based on network slicing
  • Fig. 2 is a schematic diagram of a network slice model based on physical ports
  • FIG. 3 is a flowchart of a method for implementing network slicing according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of a model for establishing a network slice through a tunnel according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of establishing a network slice through a tunnel mechanism according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of label distribution and service encapsulation of an LSP tunnel when a slice vNet2 is formed in an embodiment of the present disclosure
  • FIG. 7 is a network architecture model based on nested network slices according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of implementation of a tunnel-based nested network slice according to an embodiment of the present disclosure
  • FIG. 9 is a schematic diagram of LSP label distribution and service encapsulation when a network nesting slice is formed based on a double-layer LSP tunnel and vNet2.1 is formed according to an embodiment of the present disclosure
  • FIG. 10 is a schematic diagram of label distribution and service encapsulation of LSP tunnel nesting when a slice vNet2.2 is formed according to an embodiment of the present disclosure
  • FIG. 11 is a schematic diagram of nested slice vNet2.1 service frame encapsulation based on an LSP + SR tunnel according to an embodiment of the present disclosure
  • FIG. 12 is a schematic diagram of end-to-end service forwarding of a FlexE tunnel
  • 13 is a schematic diagram of single node FlexE forwarding
  • FIG. 14 is a schematic diagram of encapsulation of nested slice vNet2.1 service frames based on FlexE tunnel + LSP tunnel according to an embodiment of the present disclosure
  • 15 is a schematic diagram of end-to-end service forwarding of an ODUk tunnel
  • 16 is a schematic diagram of single node ODUk mapping cross
  • 17 is a schematic diagram of nested slice vNet2.1 service frame encapsulation based on ODUk tunnel + LSP tunnel according to an embodiment of the present disclosure
  • FIG. 18 is a schematic diagram of a nested network slice usage scenario according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic diagram of a nested network slice creation example of an application example of the present disclosure.
  • FIG. 20 is a schematic diagram of an apparatus for implementing network slicing according to an embodiment of the present disclosure
  • 21 is a schematic diagram of a controller of an embodiment of the present disclosure.
  • Embodiments of the present disclosure provide a method for implementing network slicing and nested slicing based on tunnel technology, which can be applied to a bearer network based on technologies such as PTN (Packet Transport, Network) and routers.
  • PTN Packet Transport, Network
  • a virtual link connecting the virtual network elements is created, and then the virtual nodes and the virtual link are managed together to form a network slice or nested slice.
  • the upper layer system can create respective services on the network slice or nested slice.
  • the method for implementing network slicing in an embodiment of the present disclosure creates one or more nested network slicing layers between the physical network layer and the service layer, where the network can be created through the following steps 101 to 103 Each network slice in the slice layer.
  • step 101 multiple virtual network elements are created.
  • the virtual network element may also be called a virtual node.
  • the virtual network element and the virtual port of the virtual network element are created according to the characteristic parameters of the virtual network element and the virtual port.
  • the virtual port of the virtual network element includes a virtual user side port and a virtual network side port.
  • the virtual network side port is an endpoint of a virtual link and an endpoint of a tunnel.
  • step 102 a virtual link between virtual network elements is created based on a tunnel.
  • a tunnel is created as a virtual link.
  • the route of the virtual link is calculated according to the port parameters of the virtual link and the network topology relationship, and a tunnel is created as the virtual link.
  • the tunnel may include at least one of the following: LSP (Label Switched Path, tunnel), FlexE (Flex Ethernet) tunnel, SR (Segment Routing) tunnel, ODUk (Optical channel Data Unit, optical channel data unit) tunnel.
  • LSP Label Switched Path, tunnel
  • FlexE Flexible Ethernet
  • SR Segment Routing
  • ODUk Optical channel Data Unit, optical channel data unit
  • an LSP tunnel is created as a virtual link.
  • the first network slicing layer is implemented based on at least one of the LSP tunnel, FlexE tunnel, and ODUk tunnel, and the second layer
  • the network slice layer is based on LSP tunnel or SR tunnel.
  • step 103 the inclusion relationship between the network slice and the virtual network element and virtual link is established.
  • the network slicing layers are sequentially created from bottom to top.
  • the upper network slice layer is created based on the lower network topology.
  • the embodiments of the present disclosure can be implemented by a controller, for example, by an SDN (Software Defined Network, Software Defined Network) controller, where SDN is an open network innovation architecture that is separated and unified by the control plane and forwarding plane of the network Centralized control of the network to achieve flexible allocation and scheduling of network resources.
  • SDN Software Defined Network, Software Defined Network
  • Network virtualization based on SDN technology provides a very good technical platform for implementing bearer network slicing.
  • the tunnel technology of the embodiment of the present disclosure creates a virtual link, abstracts the actual physical network through the virtual link, shields forwarding information of intermediate nodes, and realizes the isolation and mapping of physical resources and logical resources. Users who use slicing do not need to perceive the status of the actual network, but only need to care about the constructed slicing network.
  • the embodiment of the present disclosure implements network slicing based on tunnel technology, which can realize the topology abstraction capability in the network slicing architecture, and has no high requirements on physical port resources, and can be widely applied to bearer networks based on technologies such as PTN and routers, as well as future 5G Bearer network.
  • vNet1 which includes virtual Nodes vN1.1, vN3.1, vN4.1, and vN6.1
  • vNet2 which includes virtual nodes vN1.2, vN3.2, and vN6.2
  • the end-to-end tunnel abstracts the actual physical network, shields the forwarding information of intermediate nodes, and realizes the isolation and mapping of physical and logical resources. Users who use slicing do not need to perceive the state of the physical network and directly create services on the slicing network.
  • FIG. 5 it is a schematic diagram of establishing a network slice through a tunnel mechanism, where Node1, Node2, Node3, Node4 are some network elements in the physical network (pNET), PortA, PortB, PortC, PortD, PortE, PortF are physical ports , Link1, Link2, Link3 are physical links.
  • Node1, Node2, Node3, Node4 are some network elements in the physical network (pNET)
  • PortA, PortB, PortC, PortD, PortE, PortF are physical ports
  • Link1, Link2, Link3 are physical links.
  • a virtual network element vNode is created: a virtual network element vNode1 @ vNet2, vNode2 @ vNet2, vNode4 @ vNet2, and a virtual port vPort (vNNI): vPortA1, vPortB1 are created according to the characteristic parameters such as the virtual network element and virtual port provided by the user , VPortC1, vPortF1.
  • the virtual port vPort (vNNI) is the endpoint of the virtual link vLink and the endpoint of the tunnel.
  • a virtual link vLink is created: a virtual link vLink is created according to the characteristics of the port of the virtual link provided by the user. Among them, a tunnel is created between Node2 and Node4 as a virtual link vLink3 of vNode2 and vNode4, and a normal tunnel forwarding is performed in the intermediate Node3 node, and vNet2 does not need to be aware of the Node3 node. In addition, a tunnel is created between Node1 and Node2 as a virtual link vLink2 of vNode1 and vNode2.
  • step 203 the virtual network is created, and based on the virtual network element and virtual link set created in the previous step, the creation of the virtual network vNet2 is completed.
  • FIG. 6 shows the network slicing based on LSP tunnel, LSP label distribution and service encapsulation when vNet2 is formed.
  • vLink2 @ vNet2 in vNet2 corresponds to the LSP tunnel through PortA-PortB in the physical network;
  • vLink3 @ vNet2 corresponds to the LSP tunnel through PortC-PortD-PortE-PortF in the physical network, and vNet2 to Port3 and PortE of Node3 and Node3 Not aware.
  • the LSP labels of each node are exchanged and changed.
  • FIG 7 it is a network architecture model based on nested network slices.
  • the slice is virtualized to generate sub-slices vNet1.1, vNet1.2 .... vNet1.x, and a slice network layer 2 is added to the entire network architecture. It can also be called a sub-slice layer. Services are loaded on sub-slices, without the need to perceive the underlying physical network layer and slice layer.
  • the slicing layer and sub-slicing layer can be dynamically created according to the characteristics of customer needs, implementing their own life cycle control and independent management and operation, so that the entire network has good flexibility and flexibility, while achieving resource sharing, meeting the isolation between slices demand.
  • Figure 8 describes the implementation method of tunnel-based nested network slicing (vNet2 slicing has been created on the basis of Figure 5).
  • vNet2 tunnel-based nested network slicing
  • vNode1, vNode2, and vNode4 are some network elements in this network, vPortA1, vPortB1, vPortC1 2.
  • vPortF1 can be regarded as a "physical port" (virtual), and the links of vPortA1-vPortB1 and vPortC1-vPortF1 generated in Figure 5 can be regarded as "physical links" (virtual).
  • step 301 create a virtual network element vNode: create virtual network elements vNode1.1, vNode4.1, and virtual ports vPort (vNNI): vPortA1.1, vPortF1.1 according to user-provided virtual network element and virtual port and other characteristic parameters .
  • the virtual port vPort (vNNI) is the endpoint of the virtual link vLink and the endpoint of the tunnel.
  • a virtual link vLink is created: a virtual link vLink is created according to the characteristics of the port of the virtual link provided by the user. Among them, a tunnel is created between vNode1 and vNode4 as the virtual link vLink2.1 of vNode1.1 and vNode4.1, and ordinary tunnel forwarding is performed in the intermediate vNode2 node. VNet2.1 does not need to be aware of the vNode2 node.
  • step 303 a virtual network is created. Based on the virtual network element and virtual link set created in the previous step, the creation of the virtual network vNet2.1 is completed.
  • the tunnel in FIG. 8 may use the LSP tunnel mechanism. This method is implemented by assigning the inbound and outbound labels on each node.
  • Figure 9 shows the LSP label distribution and service encapsulation when the network nesting slice and vNet2.1 are formed based on the double-layer LSP tunnel.
  • vLink2.1 in vNet2.1 corresponds to the LSP tunnel through the ports vPortA1-vPortB1-vPortC1-vPortF1 in the vNet2 network.
  • the outer label corresponds to the first slice and the inner label corresponds to the second slice.
  • the nested slice network is expressed with two layers of labels.
  • vNet2 the LSP label of each vNode node will be exchanged and changed.
  • vNet2.1 is not aware of vNode2 and vNode2 ports.
  • vLink2.1 in vNet2.1 corresponds to the LSP tunnel through the port vPortA1-vPortB1-vPortC1-vPortF1 in the vNet2 network (as shown in Figure 8).
  • the tunnel is labeled LSP X1 , X2 to mark (the upper part of Figure 9).
  • the LSP tunnel in the vNet2 network is established on the links of virtual vLink2 (vPortA1-vPortB1) and vLink3 (vPortC1-vPortF1).
  • the virtual vPortA1-vPortB1 link in vNet2 corresponds to the LSP tunnel through PortA-PortB in the physical network
  • the virtual vPortC1-vPortF1 link corresponds to PortC-PortD-PortE in the physical network.
  • -The LSP tunnel of PortF, and the LSP tunnel through PortA-PortB is marked with the L1 label (as shown in FIG. 6); the LSP tunnel through PortC-PortD-PortE-PortF is labeled with the L2 and L3 Marked.
  • X1 and X2 labels representing vLink2.1 in the sub-slice are first marked, and then labels L1, L2 and L3 representing vLink2 and vLink3 in the first slice.
  • vNet2 does not perceive the Node3 node and its ports PortD and PortE. Therefore, the inner label X2 formed based on the vNet2 slice again is transparently transmitted at the Node3 node and its ports PortD and PortE. In this way, the nesting of LSP tags is achieved through the nesting of two levels of nested slicing services.
  • Figure 10 shows the LSP label distribution and service encapsulation when the network nesting slice and vNet2.2 are formed based on the double-layer LSP tunnel.
  • vLink2.2 in vNet2.2 corresponds to the LSP tunnel through the ports vPortA1-vPortB1 in the vNet2 network;
  • vLink2.3 corresponds to the LSP tunnel through the ports vPortC1-vPortF1 in the vNet2 network.
  • the outer label corresponds to the first slice
  • the inner label corresponds to the second slice
  • the nested slice network vNet2.2 is expressed with two layers of labels.
  • vNet2 does not perceive the Node3 node and its ports PortD and PortE, so the inner label Y2 formed based on the vNet2 slice again is transparently transmitted at the Node3 node and its ports PortD and PortE.
  • the method of nesting slices may be nesting of soft slices, hard slices, or a combination of hard slices and soft slices.
  • a double-layer LSP tunnel is a way to nest soft slices.
  • LSP + SR-based tunneling is also one of the soft-slicing nesting methods. As shown in Figure 11, when LSP + SR-based nesting slicing is used, the vNet2.1 service frame encapsulation is sliced. SR provides a tunnel implementation mechanism based on source routing. The segment identifier (Segment ID) is used to identify the node or link that needs to be traversed on the SR tunnel.
  • the SR forwarding method is compatible with the LSP label forwarding method, because the SR label represents the node or link, and has nothing to do with the service, so the intermediate node is not aware of the service, so the processing capacity requirements of the intermediate node are reduced, so that the device can handle A larger number of services to meet the needs of the Internet of Everything in the 5G era.
  • the outer LSP labels L1, L2, and L3 in Figure 11 represent the LSP tunnel corresponding to the virtual link of the first slice vNet2, and the inner SR label 1 and SR label 2 represent the SR corresponding to the second slice vNet2.1 virtual link. tunnel.
  • the nesting of slices can also be achieved through the hard slice + LSP tunnel based on FlexE Tunnel.
  • client layer services are mapped to FlexE Clients at the source node, and client layer services are unmapped from FlexE Clients at the destination node.
  • client site A customer site A
  • NE4 unmap from FlexE tunnel on the line side to the customer interface of data center 2 (data center 2).
  • the FlexE Client layer receives services and multiplexes into the FlexE Tunnel, it inserts OAM (Operation Administration and Maintenance) as needed, extracts OAM from the FlexE Tunnel, demultiplexes the service and sends it; OAM insertion and extraction , Client-level business is not aware.
  • OAM Operaation Administration and Maintenance
  • the intermediate nodes of the FlexE tunnel network are exchanged based on the FlexE Client.
  • the single-node forwarding model of its service is shown in Figure 13.
  • the general Ethernet forwarding will be processed to the MAC (Media Access Control) layer, and the L2 forwarding of the service will be realized through Packet Switch.
  • FlexE forwarding is performed at the shim layer (gasket layer) of FlexE.
  • L1 forwarding of services is realized through FlexE cross connection (FlexE cross connection), thereby providing end-to-end Ethernet slice connection for the source and sink nodes in the network, and has Features such as low latency, transparent transmission, and hard isolation.
  • the FlexE tunnel can be point-to-point single-hop, as shown in FlexE tunnel1 in Figure 12; the FlexE tunnel can also be a multi-hop tunnel that spans intermediate network elements, as shown in FlexE tunnel2 in Figure 12.
  • the multi-hop FlexE tunnel2's intermediate network elements NE2 and NE3 directly cross the FlexE layer of services, shielding higher-level service processing, making the carried services have the characteristics of one-hop direct transmission, and realize ultra-low latency service forwarding .
  • Hard slices based on FlexE Tunnel + nested slices of LSP tunnels The first slice is realized by the FlexE tunnel.
  • the method of establishing network slices through the FlexE Tunnel mechanism is shown in Figure 5.
  • the slice establishment also includes virtual network element vNode and virtual link
  • the creation of vLink, as mentioned above, only corresponds to vLink2 and vLink3 at this time is FlexE tunnel.
  • the second nested slice still uses the LSP tunnel shown in Figure 8, and the creation method is the same as described above.
  • Figure 14 shows the label distribution and service encapsulation formed by vNet2.1 when the network nesting slicing based on the FlexE tunnel + LSP tunnel is used.
  • the nested slicing network is expressed with two layers of encapsulation and labels.
  • the outer FlexE package corresponds to the first slice.
  • the physical tunnel corresponding to vlink2 @ vNet2 in vNet2 is implemented by FlexE package 1
  • the physical tunnel corresponding to vlink3 @ vNet2 in vNet2 is implemented by FlexE package 2.
  • FlexE package 2 In a specific FelxE tunnel, its FlexE encapsulation remains unchanged, and the route of the tunnel is set by the network management or calculated by the controller according to the protocol.
  • the inner label in FIG. 14 corresponds to the second slice.
  • vLink2.1 in vNet2.1 corresponds to the LSP tunnel through the ports vPortA1-vPortB1-vPortC1-vPortF1 in the vNet2 network.
  • ODUk Tunnel can also implement hard slicing, and ODUk Tunnel + LSP tunnel can be used to achieve nesting of slices.
  • the client layer services are mapped and encapsulated into ODUk at the source node, and multiplexed to the OTN line side.
  • the client layer services are unmapped from ODUk.
  • the service service A is mapped to ODUk and It is multiplexed to the line side of NE1, and the service is demapped from the ODUk on the line side to the customer interface of data center2 in NE4.
  • the intermediate nodes of the ODUk tunnel are exchanged based on ODUk.
  • the single-node forwarding model of their services is shown in Figure 16.
  • ODUk crossovers L1 forwarding of services is implemented through ODUk crossovers, thereby providing end-to-end connections for source and sink node services in the network. Extension, transparent transmission, hard isolation, etc.
  • the ODUk tunnel can be point-to-point single-hop, as shown in Figure 15 ODUk tunnel1; ODUk tunnel can also be a multi-hop tunnel across the intermediate network elements, as shown in Figure 15 ODUk tunnel2.
  • the NE2 and NE3 of the multi-hop ODUk tunnel2 intermediary network directly perform ODUk crossover on services.
  • the first slicing is achieved through the ODUk tunneling method.
  • the specific method of establishing network slicing through the ODUk Tunnel mechanism is shown in Figure 5.
  • the slicing establishment also includes virtual network element vNode and virtual chain
  • the creation of the road vLink is as detailed above, but at this time the corresponding to vLink2 and vLink3 is the ODUk tunnel.
  • the second nested slice still uses the LSP tunnel shown in Figure 8, and the creation method is the same as described above.
  • Figure 17 shows the label distribution and service encapsulation formed by vNet2.1 when performing network nested slicing based on the ODUk Tunnel + LSP tunnel.
  • the nested slicing network is expressed with two layers of encapsulation and labels.
  • the outer ODUk package corresponds to the first slice.
  • the physical tunnel corresponding to vlink2 @ vNet2 in vNet2 is implemented by ODUk package 1
  • the physical tunnel corresponding to vlink3 @ vNet2 in vNet2 is implemented by ODUk package 2.
  • ODUk package 2 In a specific ODUk tunnel, its encapsulation remains unchanged, and the route of the tunnel is set by the network management.
  • the inner label in Figure 15 corresponds to the second slice.
  • vLink2.1 in vNet2.1 corresponds to the LSP tunnel in the vNet2 network through ports vPortA1-vPortB1-vPortC1-vPortF1.
  • the first layer of hard slicing is convenient for dividing and managing the hardware resources of the device, and it is easier to meet the business in time. Requirements for extension, isolation, etc.
  • the first layer uses LSP tunnel-based slicing, which has low hardware requirements, better service reuse, and more flexible deployment. You can choose a suitable nesting slicing scheme according to different customer needs. From the perspective of resource management and slicing effect, it is recommended to use hard slicing at the first layer.
  • nested network slicing is implemented through nested tunnels.
  • layers of slicing can carry various services such as L2VPN and L3VPN.
  • L2VPN L2VPN
  • L3VPN L3VPN
  • you want to directly carry the L2VPN service on vNet2 in Figure 5 then you need to establish an LSP tunnel for the L2VPN service on vNet2.
  • the tunnel is the same as the label and service encapsulation in Figure 9.
  • Figure 18 describes one of the application scenarios where the bearer network implements nested slicing.
  • a single physical network is virtualized into a guest slicing, a wireless slicing, a home-wide slicing, etc. as needed.
  • These slices are independently managed and operated by the corresponding virtual operator, and can be sliced again according to customer needs.
  • the virtual operator A can slice the customer slicing network into banking business sub-slicing, government business sub-slicing, and enterprise business sub-slicing according to its own business needs. Each sub-slice can be dynamically created and independently maintained.
  • the resources of the bearer network and the independent operation and maintenance of the slices are realized by slicing and sub-slicing.
  • the first part is to create a network slice vNet1 based on the physical network.
  • the physical network contains N1, N2, N3, N4, N5, N6 and other physical network elements. Proceed as follows:
  • VNet1 needs to contain four virtual nodes: vN1.1, vN3.1, vN4.1, and vN6.1.
  • the virtual node includes the corresponding virtual user-side port vUNI and the virtual network-side port vNNI, where the virtual network-side port vNNI is the endpoint of MPLS-TP LSP1.
  • the controller calculates the route of vLink1 as N1-N2-N3 based on the physical network topology relationship, and calculates the label exchange inside the N2 node as MPLS-TP LSP.
  • the controller creates an N1-N2-N3 MPLS-TP LSP tunnel as a vLink between the nodes vN1.1 and vN3.1 to complete the creation of the virtual link.
  • the controller completes the vNet1 instance and establishes the inclusion relationship between vNet1 and the corresponding virtual node and virtual link.
  • step (4) the controller (or network manager) calculates It is the routing of the ODUk tunnel, SR tunnel, and FlexE tunnel tunnel.
  • step (5) the controller creates (or configures the network management) ODUk tunnel, SR tunnel, and FlexE tunnel tunnel.
  • the second part is to create a nested network slice vNet1.1 based on the virtual network vNet1.
  • vNet1.1 There are four network elements vN1.1, vN3.1, vN4.1, vN6.1 and so on. Proceed as follows:
  • vNet1.1 needs to contain three virtual nodes: vN1.1.1, vN3.1.1, and vN4.1.1.
  • the controller creates a vN4.1-vN6.1-vN3.1 MPLS-TP LSP1.3 tunnel as a vLink between the nodes vN4.1.1 and vN3.1.1 to complete the creation of the virtual link.
  • the controller completes the vNet1.1 instance and establishes the inclusion relationship between vNet1.1 and the corresponding virtual node and virtual link.
  • step (d) the controller calculates the SR tunnel source routing label, and in step (e), the controller creates (or configures the network management) SR tunnel.
  • an embodiment of the present disclosure also provides an apparatus for implementing network slicing, including: a network element creation module 41 configured to create multiple virtual network elements; a link creation module 42 configured to create based on a tunnel A virtual link between virtual network elements; the slice creation module 43 is configured to establish the inclusion relationship between the network slice and the virtual network element and the virtual link.
  • the embodiment of the present disclosure implements network slicing based on tunnel technology, which can realize the topology abstraction capability in the network slicing architecture, and has no high requirements on physical port resources, and can be widely applied to bearer networks based on technologies such as PTN and routers, as well as future 5G Bearer network.
  • the network element creation module 41 is configured to create the virtual network element and the virtual port of the virtual network element according to the characteristic parameters of the virtual network element and the virtual port.
  • the virtual ports of the virtual network element include virtual user-side ports and virtual network-side ports.
  • the link creation module 42 is configured to create a tunnel as a virtual link according to the port parameters of the virtual link.
  • the link creation module 42 is configured to calculate the route of the virtual link based on the port parameters of the virtual link and the network topology, and create a tunnel as the virtual link.
  • the slice creation module 43 is configured to complete the creation of network slices based on the created virtual network element and virtual link set.
  • a virtual link vLink between virtual network elements is established through a tunnel (eg, LSP, etc.) on the forwarding plane to form a sliced network, and the nesting of slices is realized through recursion of tunnels and node virtualization.
  • the virtual transport network based on slicing is similar to the physical network, and can carry various services, such as L2VPN and L3VPN.
  • an embodiment of the present disclosure also provides a controller, including a memory 51, a processor 52, and a computer program 53 stored on the memory 51 and executable on the processor 52.
  • the processor 53 executes The method of implementing network slicing is realized when the program is described.
  • the controller may be an SDN controller.
  • Embodiments of the present disclosure also provide a computer-readable storage medium that stores computer-executable instructions, which are used to execute the method for implementing network slicing when executed by a processor.
  • the above storage medium may include, but is not limited to: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc.
  • ROM read-only memory
  • RAM random access memory
  • mobile hard disk magnetic disk or optical disk, etc.
  • computer storage media includes both volatile and nonvolatile implemented in any method or technology for storing information such as computer readable instructions, data structures, program modules, or other data Sex, removable and non-removable media.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or may Any other medium for storing desired information and accessible by a computer.
  • the communication medium generally contains computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .

Landscapes

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

Abstract

提供了一种实现网络切片的方法、装置和控制器，所述方法包括：在物理网络层和业务层之间创建一层或多层嵌套的网络切片层，其中，通过如下方式创建网络切片层中的每个网络切片：创建多个虚拟网元；基于隧道的方式创建虚拟网元之间的虚拟链路；建立网络切片与所述虚拟网元和虚拟链路的包含关系。

Description

实现网络切片的方法、装置和控制器 技术领域
本公开涉及但不限于通信领域。
背景技术
伴随通信技术的发展，运营商业务呈现出多场景、差异化的特点，需要通过切片的方式在同一张物理网络上对不同类型业务构建独立的端到端逻辑网络。网络虚拟化的本质是资源的共享，将物理网络资源池化，达到资源任意分割或者合并的目的，用于构建满足上层服务需求的虚拟网络。承载网网络切片是利用虚拟化技术在一个共享的物理网络资源之上创建多个虚拟网络(vNet)，或称为网络切片(Network Slice),同时为每个虚拟网络(vNet)提供独立部署及管理。
承载网网络切片可以根据承载业务不同类型或不同租户而将物理网络切片成相应的虚拟网络(例如按照政企客户、家庭客户、以及5G的eMBB(Enhance Mobile Broadband，增强移动宽带)业务、uRLLC(Ultra Reliable &Low Latency Communication，超高可靠与低延迟的通信)业务、mMTC(massive Machine Type of Communication，海量机器类通信)业务进行切片)，从而满足不同类型业务需求。相对于建设不同的物理网络平面，网络切片可实现物理网络资源的共享，避免重复建设，大幅降低建网成本。并且资源调度更加灵活，易于管理、运维及业务部署。
对于传统的承载网而言，网络架构按层次分为物理网络层、业务层、客户层，物理网络层之上就是业务层，即业务是直接加载于物理网络之上的。而基于网络切片模型和方法，在业务层和物理网络层之间增加了切片之后的虚拟网络层，基于网络切片的网络架构如图1所示。
虚拟网络层(切片层)位于业务层和物理网络层之间，实现了业务层与物理网络层的解耦，业务层不需要感知物理网络。对业务层 而言，其感知到的虚拟网络和物理网络类似。切片的创建先于业务创建，然后业务再加载于切片之上，并且业务可灵活创建、调整。基于vNet，可以进一步创建各种业务，如L2VPN(Layer 2 Virtual Private Networks，二层虚拟专用网)、L3VPN(Layer 3 Virtual Private Networks，三层虚拟专用网)等。各个切片能满足各自业务的需求，并可以独立监控管理，提供切片之间资源隔离。
类似物理网络包含节点和链路一样，一个网络切片vNet包含虚拟节点(vNode)和虚拟链路(vLink)。图2描述了一种基于物理端口实现网络切片的方法。如图2所示，实线端口和虚线端口分别代表不同的切片，通过资源虚拟化创建出两个不同的网络切片。
但是，基于物理端口的切片具有以下缺陷：
1、需要多组物理端口，不同的切片通过物理端口进行隔离，对端口资源有较高的要求。
2、无法完全实现网络的抽象，如vNet1的用户其实只需要关心四个PE(Provider Edge，提供商边缘设备)节点，无需感知中间P节点，但基于端口的切片不具备对网络的抽象能力，只能将完整的拓扑呈现给切片用户。
发明内容
本公开实施例提供了一种实现网络切片的方法，在物理网络层和业务层之间创建一层或多层嵌套的网络切片层，其中，通过如下方式创建网络切片层中的每个网络切片：创建多个虚拟网元；基于隧道的方式创建虚拟网元之间的虚拟链路；建立网络切片与所述虚拟网元和虚拟链路的包含关系。
本公开实施例还提供一种实现网络切片的装置，包括：网元创建模块，用于创建多个虚拟网元；链路创建模块，用于基于隧道的方式创建虚拟网元之间的虚拟链路；切片创建模块，用于建立网络切片与所述虚拟网元和虚拟链路的包含关系。
本公开实施例还提供一种控制器，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述 程序时实现所述实现网络切片的方法。
本公开实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令由处理器执行时用于执行所述实现网络切片的方法。
附图说明
附图用来提供对本公开技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本公开的技术方案，并不构成对本公开技术方案的限制。
图1是基于网络切片的网络架构模型的示意图；
图2是基于物理端口的网络切片模型的示意图；
图3是本公开实施例的实现网络切片的方法的流程图；
图4是本公开实施例的通过隧道建立网络切片的模型的示意图；
图5是本公开实施例的通过隧道机制建立网络切片的示意图；
图6是本公开实施例中，切片vNet2形成时的LSP隧道的标签分配和业务封装示意图；
图7是本公开实施例的基于嵌套网络切片的网络架构模型；
图8是本公开实施例的基于隧道的嵌套网络切片的实现示意图；
图9是本公开实施例的基于双层LSP隧道进行网络嵌套切片及vNet2.1形成时的LSP标签分配和业务封装示意图；
图10是本公开实施例的切片vNet2.2形成时的LSP隧道嵌套的标签分配和业务封装示意图；
图11是本公开实施例的基于LSP+SR隧道的嵌套切片vNet2.1业务帧封装示意图；
图12是FlexE隧道端到端业务转发示意图；
图13是单节点FlexE转发示意图；
图14是本公开实施例的基于FlexE隧道+LSP隧道的嵌套切片vNet2.1业务帧封装示意图；
图15是ODUk隧道端到端业务转发示意图；
图16是单节点ODUk映射交叉示意图；
图17是本公开实施例的基于ODUk隧道+LSP隧道的嵌套切片vNet2.1业务帧封装示意图；
图18是本公开实施例的嵌套的网络切片使用场景示意图；
图19是本公开应用实例的嵌套的网络切片创建实例示意图；
图20是本公开实施例的实现网络切片的装置的示意图；
图21是本公开实施例的控制器的示意图。
具体实施方式
下文中将结合附图对本公开的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本公开实施例提供一种基于隧道技术实现网络切片和嵌套切片的方法，可以适用于基于PTN(Packet Transport Network，分组传送网)、路由器等技术的承载网。通过隧道创建出连接虚拟网元的虚拟链路，再将虚拟节点和虚拟链路统一管理形成网络切片或嵌套切片，上层系统可以在网络切片或嵌套切片上创建各自的业务。
如图3所示，本公开实施例的实现网络切片的方法，在物理网络层和业务层之间创建一层或多层嵌套的网络切片层，其中，可以通过如下步骤101至103创建网络切片层中的每个网络切片。
在步骤101，创建多个虚拟网元。
其中，虚拟网元也可称为虚拟节点。
在一实施例中，根据虚拟网元和虚拟端口的特性参数，创建所述虚拟网元以及所述虚拟网元的虚拟端口。
其中，所述虚拟网元的虚拟端口包括虚拟用户侧端口和虚拟网络侧端口。
所述虚拟网络侧端口是虚拟链路的端点，也是隧道的端点。
在步骤102，基于隧道的方式创建虚拟网元之间的虚拟链路。
其中，在一实施例中，根据所述虚拟链路的端口参数，创建隧道作为虚拟链路。
在一实施例中，根据所述虚拟链路的端口参数和网络拓扑关系计算虚拟链路的路由，创建隧道作为虚拟链路。
其中，所述隧道可以包括如下至少之一：LSP(Label Switched Path，标签交换路径)隧道(tunnel)、FlexE(Flex Ethernet，灵活以太网)隧道、SR(Segment Routing，分段路由)隧道、ODUk(Optical channel Data Unit，光通路数据单元)隧道。
例如，通过分配虚拟链路上每个虚拟网元的入向标签和出向标签，创建LSP隧道作为虚拟链路。
其中，采用LSP隧道、SR隧道方式的切片对硬件资源要求低、带宽复用效果好、部署灵活，基于FlexE隧道、ODUk隧道的切片具有低时延、透明、隔离等优势。
在一实施例中，在物理网络层和业务层之间创建两层嵌套的网络切片层时，首层的网络切片层基于LSP隧道、FlexE隧道和ODUk隧道中的至少之一实现，次层的网络切片层基于LSP隧道或SR隧道实现。
在步骤103，建立网络切片与所述虚拟网元和虚拟链路的包含关系。
基于创建的虚拟网元和虚拟链路集合，完成创建网络切片。
在一实施例中，在物理网络层和业务层之间创建多层嵌套的网络切片层时，从下至上依次创建所述网络切片层。
其中，上层的网络切片层基于下层网络拓扑创建。
本公开实施例可以由控制器实现，例如通过SDN(Software Defined Network，软件定义网络)控制器实现，其中，SDN是一种开放的网络创新架构，通过网络的控制平面和转发平面相分离，统一的集中控制，实现网络资源的灵活分配调度。基于SDN技术的网络虚拟化为实现承载网络切片提供了非常好的技术平台。
本公开实施例的隧道技术创建虚拟的链路，通过虚拟链路将实际的物理网络进行抽象，屏蔽中间节点的转发信息，实现物理资源和 逻辑资源的隔离和映射。使用切片的用户无需感知实际网络的状态，只需关心已构建好的切片网络。
本公开实施例基于隧道技术实现网络切片，可以实现网络切片架构中的拓扑抽象能力，而且对物理端口资源没有较高要求，可广泛应用到基于PTN、路由器等技术的承载网，以及未来的5G承载网络。
如图4所示，为通过隧道建立网络切片的模型，在物理网络(其含有N1、N2、N3、N4、N5、N6等物理网元)基础上虚拟出两个切片网络vNet1(其包括虚拟节点vN1.1、vN3.1、vN4.1和vN6.1)和vNet2(其包括虚拟节点vN1.2、vN3.2和vN6.2)。端到端的隧道将实际的物理网络进行抽象，屏蔽了中间节点的转发信息，实现物理资源和逻辑资源的隔离和映射。使用切片的用户无需感知物理网络的状态，直接在切片网络上创建业务。
如图5所示，为通过隧道机制建立网络切片的示意图，其中Node1、Node2、Node3、Node4是物理网络(pNET)中的部分网元，PortA、PortB、PortC、PortD、PortE、PortF是物理端口，Link1、Link2、Link3是物理链路。以vNet2的创建为例，包括以下步骤201至203。
在步骤201，创建虚拟网元vNode：根据用户提供的虚拟网元和虚拟端口等特性参数创建虚拟网元vNode1@vNet2、vNode2@vNet2、vNode4@vNet2，及虚拟端口vPort(vNNI)：vPortA1、vPortB1、vPortC1、vPortF1。其中虚拟端口vPort(vNNI)是虚拟链路vLink的端点，也是隧道的端点。
在步骤202，创建虚拟链路vLink：根据用户提供的虚拟链路的端口等特性创建虚拟链路vLink。其中Node2与Node4之间创建了一条隧道作为vNode2与vNode4的虚拟链路vLink3，在中间Node3节点进行普通的隧道转发，而vNet2无需感知Node3节点。此外，在Node1与Node2之间创建一条隧道作为vNode1与vNode2的虚拟链路vLink2。
在步骤203，虚拟网络创建，基于前面步骤创建的虚拟网元和虚拟链路集合，完成创建虚拟网络vNet2。
通过对网络中的各节点(网元)分配相应的入向标签、出向标 签，这些节点的标签形成一条路径，就是LSP隧道。图6展示了基于LSP隧道进行网络切片，vNet2形成时的LSP标签分配和业务封装。vNet2中的vLink2@vNet2对应物理网路中经过端口PortA-PortB的LSP隧道；vLink3@vNet2对应物理网络中经过端口PortC-PortD-PortE-PortF的LSP隧道，vNet2对Node3和Node3的端口PortD、PortE不感知。物理网络中，每个节点的LSP标签会进行交换而发生变化。
如图7所示，为基于嵌套网络切片的网络架构模型。基于图1，在生成切片网络vNet1后，对此切片再进行虚拟化，生成子切片vNet1.1、vNet1.2....vNet1.x，在整个网络架构中增加了一个切片网络层2，也可称为子切片层。业务加载于子切片之上，不需感知下面的物理网络层和切片层。切片层和子切片层可以按照客户需求特性动态创建，实施各自的生命周期控制和独立的管理运营，从而使得整个网络具有很好的灵活性、弹性，在实现资源共享的同时，满足切片间的隔离需求。
图8描述基于隧道的嵌套网络切片的实现方法(在图5的基础上已经创建了vNet2切片)，在vNet2中，vNode1、vNode2、vNode4是此网络中的部分网元，vPortA1、vPortB1、vPortC1、vPortF1可当成“物理端口”看待(虚拟的)，可将图5中生成的vPortA1-vPortB1，vPortC1-vPortF1的链路看成“物理链路”(虚拟的)，基于这些链路，再分别建立经过端口vPortA1-vPortB1的隧道、经过端口vPortC1-vPortF1的隧道、经过端口vPortA1-vPortB1-vPortC1-vPortF1的隧道，以再次进行网络的虚拟化切片。
以子切片vNet2.1的创建为例，包括以下步骤301至303。
在步骤301，创建虚拟网元vNode：根据用户提供的虚拟网元和虚拟端口等特性参数创建虚拟网元vNode1.1、vNode4.1，及虚拟端口vPort(vNNI)：vPortA1.1、vPortF1.1。其中虚拟端口vPort(vNNI)是虚拟链路vLink的端点，也是隧道的端点。
在步骤302，创建虚拟链路vLink：根据用户提供的虚拟链路的端口等特性创建虚拟链路vLink。其中vNode1与vNode4之间创建了一条隧道作为vNode1.1与vNode4.1的虚拟链路vLink2.1，在中间vNode2节点进行普通的隧道转发，vNet2.1无需感知vNode2节点。
在步骤303，虚拟网络创建，基于前面步骤创建的虚拟网元和虚拟链路集合，完成创建虚拟网络vNet2.1。
按照同样步骤，可以创建子切片vNet2.2。
图8中的隧道可以采用LSP隧道的机制，此方式是通过各节点上的入向标签、出向标签的分配来实现的。图9展示了基于双层LSP隧道进行网络嵌套切片及vNet2.1形成时的LSP标签分配和业务封装。vNet2.1中的vLink2.1对应vNet2网络中经过端口vPortA1-vPortB1-vPortC1-vPortF1的LSP隧道。在报文封装中，外层标签对应着首次切片，内层标签对应着第二次切片，用两层标签表述了嵌套的切片网络。对于vNet2，每个vNode节点的LSP标签会进行交换而发生变化。而vNet2.1对vNode2及vNode2的端口也是不感知的。
从业务转发看，对vNet2.1而言，vNet2.1中的vLink2.1对应vNet2网络中经过端口vPortA1-vPortB1-vPortC1-vPortF1的LSP隧道(如图8所示)，该隧道以LSP标签X1、X2来标示(图9上部)。而vNet2网络中的这条LSP隧道是建立在虚拟vLink2(vPortA1-vPortB1)、vLink3(vPortC1-vPortF1)的链路上。如图5所示，vNet2中的虚拟vPortA1-vPortB1链路对应着物理网络中经过端口PortA-PortB的这个LSP隧道，虚拟的vPortC1-vPortF1的链路对应着物理网络中经过端口PortC-PortD-PortE-PortF的这个LSP隧道，而经过PortA-PortB的这个LSP隧道是以L1标签来标示的(如图6所示)；经过PortC-PortD-PortE-PortF的这个LSP隧道是以L2、L3标签来标示的。因而业务转发时，先打上代表子切片中vLink2.1的X1、X2标签，接着打上代表首切片中vLink2、vLink3的标签L1、L2、L3。vNet2不感知Node3节点及其端口PortD和PortE，因而基于vNet2再次切片形成的内层标签X2，在Node3节点及其端 口PortD和PortE是透明传送的。这样通过两层的LSP标签嵌套，实现了嵌套切片业务的转发。
图10展示了基于双层LSP隧道进行网络嵌套切片及vNet2.2形成时的LSP标签分配和业务封装。vNet2.2中的vLink2.2对应vNet2网络中经过端口vPortA1-vPortB1的LSP隧道；vLink2.3对应vNet2网络中经过端口vPortC1-vPortF1的LSP隧道。在报文封装中，外层标签对应着首次切片，内层标签对应着第二次切片，用两层标签表述了嵌套的切片网络vNet2.2。vNet2不感知Node3节点及其端口PortD和PortE，因而基于vNet2再次切片形成的内层标签Y2，在Node3节点及其端口PortD和PortE是透明传送的。
切片嵌套的方式可以采用软切片嵌套、硬切片嵌套或硬切片+软切片结合的嵌套方式。双层LSP隧道是软切片嵌套的一种方式。另外，基于LSP+SR隧道也是软切片嵌套的方式之一，如图11所示，展示了基于LSP+SR的嵌套切片时，切片vNet2.1的业务帧封装。SR提供了一种基于源路由的隧道实现机制。段标识符(Segment ID)用于标识SR隧道上需要经过的节点或者链路，只需在源节点将段标识符列表(Segment List)封装到报文头中，设备即可根据报文头中的SR标签栈代表的路径信息进行转发。SR的转发方式和LSP的标签转发方式兼容，因为SR的标签是代表节点或者链路的，和业务无关，因而中间节点对业务不感知，因而对中间节点的处理能力要求降低，从而设备能处理更大的业务数量，满足5G时代的万物互联的需求。
基于LSP+SR嵌套切片时，先按照图5的方式基于LSP隧道，将物理网络切分为vNet1和vNet2，实现网络的第一次切片。再参考图8进行嵌套切片，只是此时建立SR隧道作为虚拟网络vNet2.1、vNet2.2中的网元间的vLink，以将vNet2切分为vNet2.1和vNet2.2。SR隧道标签有push、next、continue等操作，可以完成标签的弹出、压入及透传。图11中的外层LSP标签L1、L2、L3代表首次切片vNet2的虚拟链路对应的LSP隧道，内层的SR标签1、SR标签2代表第二次切片vNet2.1虚拟链路对应的SR隧道。
切片的嵌套也可以通过基于FlexE Tunnel的硬切片+LSP隧道的 方式来实现。FlexE隧道机制下，客户层业务在源节点映射到FlexE Client，在目的节点从FlexE Client中解映射客户层业务，如图12中的client site A(客户站点A)映射到NE1的线路侧FlexE tunnel，在NE4中从线路侧的FlexE tunnel中解映射到data center2(数据中心2)的客户接口上。同时，在FlexE Client客户层接收业务并复用进入FlexE Tunnel时按需插入OAM(Operation Administration and Maintenance，操作维护管理)，从FlexE Tunnel提取OAM后解复用业务并发送；OAM的插入和提取过程，客户层业务无感知。
FlexE隧道的网络中间节点基于FlexE Client进行交换，其业务的单节点转发模型见图13。一般的以太网转发，会处理到MAC(Media Access Control，媒体访问控制)层，通过分组交换(Packet Switch)实现业务的L2转发。而FlexE转发是在FlexE的shim层(垫片层)进行，通过FlexE cross connection(FlexE交叉连接)实现业务的L1转发，从而为网络中的源宿节点提供端到端的以太网切片连接，并具有低时延、透明传输、硬隔离等特征。FlexE隧道可以是点对点单跳的，如图12中的FlexE tunnel1；FlexE隧道也可是跨越中间网元的多跳的隧道，如图12中的FlexE tunnel2。多跳的FlexE tunnel2的中间网元NE2和NE3，对业务直接进行FlexE层交叉，屏蔽了更高层次的业务处理，使得承载的业务具有类似一跳直达的特性，实现超低时延的业务转发。
基于FlexE Tunnel的硬切片+LSP隧道的嵌套切片，首次切片通过FlexE隧道方式来实现，通过FlexE Tunnel机制建立网络切片的方法如图5所示，切片建立也是包括虚拟网元vNode和虚拟链路vLink的创建，如前文所述，只是此时与vLink2、vLink3对应的是FlexE tunnel。第二次的嵌套切片仍采用图8所示的LSP隧道方式，创建方法同前文所述。
图14展示了基于FlexE隧道+LSP隧道进行网络嵌套切片时，vNet2.1形成的标签分配和业务封装，用两层的封装和标签表述了嵌套的切片网络。外层的FlexE封装对应着首次切片，如图5所示，vNet2中的vlink2@vNet2对应的物理隧道由FlexE封装1实现，vNet2中 的vlink3@vNet2对应的物理隧道由FlexE封装2实现。在特定的FelxE隧道中，其FlexE封装保持不变，隧道的路由由网管设定，或者由控制器根据协议来计算完成。图14的内层标签对应着第二次切片，如图8所示，vNet2.1中的vLink2.1对应vNet2网络中经过端口vPortA1-vPortB1-vPortC1-vPortF1的LSP隧道。
此外，基于ODUk Tunnel也可以实现硬切片，可以采用ODUk Tunnel+LSP隧道的方式实现切片的嵌套。ODUk隧道机制下，客户层业务在源节点映射并封装到ODUk，并复用到OTN线路侧，在目的节点从ODUk中解映射客户层业务，如图15中的业务service A映射到到ODUk并复用到NE1的线路侧，在NE4中从线路侧的ODUk中解映射业务到data center2的客户接口上。ODUk隧道的网络中间节点基于ODUk进行交换，其业务的单节点转发模型见图16，通过ODUk的交叉实现业务的L1转发，从而为网络中的源宿节点业务提供端到端的连接，具有低时延、透明传输、硬隔离等特征。ODUk隧道可以是点对点单跳的，如图15中的ODUk tunnel1；ODUk隧道也可是跨越中间网元的多跳的隧道，如图15中的ODUk tunnel2。多跳的ODUk tunnel2的中间网元NE2和NE3，对业务直接进行ODUk交叉。
基于ODUk Tunnel的硬切片+LSP隧道的嵌套切片，首次切片通过ODUk隧道方式来实现，通过ODUk Tunnel机制建立网络切片的具体方法如图5所示，切片建立也是包括虚拟网元vNode和虚拟链路vLink的创建，详细如前文所述，只是此时与vLink2、vLink3对应的是ODUk tunnel。第二次的嵌套切片仍采用图8所示的LSP隧道方式，创建方法同前文所述。
图17展示了基于ODUk Tunnel+LSP隧道进行网络嵌套切片时，vNet2.1形成的标签分配和业务封装，用两层的封装和标签表述了嵌套的切片网络。外层的ODUk封装对应着首次切片，如图5所示，vNet2中的vlink2@vNet2对应的物理隧道由ODUk封装1实现，vNet2中的vlink3@vNet2对应的物理隧道由ODUk封装2实现。在特定的ODUk隧道中，其封装保持不变，隧道的路由由网管设定。图15的内层标签对应着第二次切片，如图8所示，vNet2.1中的vLink2.1对应 vNet2网络中经过端口vPortA1-vPortB1-vPortC1-vPortF1的LSP隧道。
对比硬切片(FlexE隧道、ODUk隧道)+LSP隧道的嵌套的方式以及双层LSP隧道嵌套的方式，首层硬切片方便对设备的硬件资源进行切分和管理，更容易满足业务在时延、隔离等方面的要求。而首层采用基于LSP隧道的切片，对设备硬件要求低，业务复用效果更好，部署更加灵活。可以根据不同的客户需求来选择合适的嵌套切片的方案，从资源管理和切片效果看，建议首层采用硬切片的方式。另外，从切片嵌套的架构看，切片的层数没有限制，但切片层数增加，需要设备更强大的资源、能力支撑，同时也会增加切片在管理、运维方面的难度，也可能对客户的使用造成不便，可根据客户的需求、设备能力等因素来选择合适的切片的层数。一般情况下，建议采用两层隧道的嵌套切片。
以上通过嵌套的隧道实现嵌套的网络切片，无论哪一层切片都具有类似物理网络的特征，可承载各类L2VPN、L3VPN等业务。例如，如果要在图5中的vNet2上直接承载L2VPN业务，则要在vNet2上再建立L2VPN业务的LSP隧道，这时也同样需要标签嵌套，只不过这时的内层标签是表示业务的隧道，而在形式上和图9的标签及业务封装方式一样。
图18描述了承载网络实施嵌套切片的应用场景之一，单个物理网络按照需要虚拟化为集客切片、无线切片、家宽切片等。这些切片由相应的虚拟运营商进行独立管理和运维，并可以按照客户需要进行再次切片。如虚拟运营商A根据自身业务需求，可以将集客切片网络再次切片为银行业务子切片、政府业务子切片、企业业务子切片等。各个子切片可以动态创建、独立运维。在同一张物理网络上通过切片、子切片的方式实现承载网络的资源共享和切片的独立运维。
下面通过应用实例介绍本申请在承载网络中通过LSP等隧道机制创建嵌套的网络切片的实现方式，如图19所示。
第一部分、基于物理网络创建网络切片vNet1，物理网络中含有N1、N2、N3、N4、N5、N6等物理网元。步骤如下：
(1)管理者发起vNet1创建，vNet1需要包含vN1.1、vN3.1、vN4.1、vN6.1四个虚拟节点。
(2)创建vN1.1虚拟节点，虚拟节点包含相应的虚拟用户侧端口vUNI及虚拟网络侧端口vNNI，其中虚拟网络侧端口vNNI为MPLS-TP LSP1的端点。
(3)同样的步骤创建vN3.1、vN4.1、vN6.1虚拟节点。
(4)创建vN1.1与vN3.1的虚拟链路vLink1，控制器基于物理网络拓扑关系计算vLink1的路由为N1-N2-N3，并计算出N2节点内部为MPLS-TP LSP的标签交换。
(5)控制器创建一条N1-N2-N3的MPLS-TP LSP隧道作为节点vN1.1和vN3.1间的vLink，完成虚拟链路的创建。
(6)重复(4)和(5)步骤，创建节点vN1.1-vN4.1、vN3.1-vN6.1、vN4.1-vN6.1之间的vLink。
(7)控制器完成vNet1实例，建立vNet1与相应虚拟节点和虚拟链路的包含关系。
基于物理网络创建网络切片vNet1，也可以采用其他隧道技术，如ODUk隧道、SR隧道、FlexE tunnel隧道等，其步骤和上述方法一样，只是在第(4)步骤时，控制器(或者网管)计算的是ODUk隧道、SR隧道、FlexE tunnel隧道的路由，第(5)步骤时控制器创建(或者网管配置)的是ODUk隧道、SR隧道、FlexE tunnel隧道。
第二部分、基于虚拟网络vNet1创建嵌套的网络切片vNet1.1，vNet1中创建有vN1.1、vN3.1、vN4.1、vN6.1等四个网元。步骤如下：
(a)管理者发起vNet1.1创建，vNet1.1需要包含vN1.1.1、vN3.1.1、vN4.1.1三个虚拟节点。
(b)创建vN1.1.1虚拟节点，虚拟节点包含相应的虚拟用户侧端口vUNI及虚拟网络侧端口vNNI，其中虚拟网络侧端口vNNI为MPLS-TP LSP1.1的端点。
(c)同样的步骤创建vN3.1.1、vN4.1.1虚拟节点。
(d)创建节点vN3.1.1、vN4.1.1之间的虚拟链路vLink1.3，控制器基于网络拓扑关系计算vLink1的路由为vN4.1-vN6.1-vN3.1，并计算出vN6.1节点内部为MPLS-TP LSP的标签交换。
(e)控制器创建一条vN4.1-vN6.1-vN3.1的MPLS-TP LSP1.3隧道作为节点vN4.1.1和vN3.1.1间的vLink，完成虚拟链路的创建。
(f)重复(d)和(e)步骤，创建节点vN1.1.1-vN4.1.1、vN1.1.1-vN3.1.1之间的vLink。
(g)控制器完成vNet1.1实例，建立vNet1.1与相应虚拟节点和虚拟链路的包含关系。
基于虚拟网络vNet1创建嵌套的网络切片vNet1.1，也可以采用其他隧道技术，如SR隧道。其步骤和上述方法一样，只是在第(d)步骤时，控制器计算的是SR隧道源路由标签，第(e)步骤时控制器创建(或者网管配置)的是SR隧道。
如图20所示，本公开实施例还提供一种实现网络切片的装置，包括：网元创建模块41，配置为创建多个虚拟网元；链路创建模块42，配置为基于隧道的方式创建虚拟网元之间的虚拟链路；切片创建模块43，配置为建立网络切片与所述虚拟网元和虚拟链路的包含关系。
本公开实施例基于隧道技术实现网络切片，可以实现网络切片架构中的拓扑抽象能力，而且对物理端口资源没有较高要求，可广泛应用到基于PTN、路由器等技术的承载网，以及未来的5G承载网络。
在一实施例中，所述网元创建模块41，配置为根据虚拟网元和虚拟端口的特性参数，创建所述虚拟网元以及所述虚拟网元的虚拟端口。
在一实施例中，所述虚拟网元的虚拟端口包括虚拟用户侧端口和虚拟网络侧端口。
在一实施例中，所述链路创建模块42，配置为根据所述虚拟链路的端口参数，创建隧道作为虚拟链路。
在一实施例中，所述链路创建模块42，配置为根据所述虚拟链 路的端口参数和网络拓扑关系计算虚拟链路的路由，创建隧道作为虚拟链路。
在一实施例中，切片创建模块43，配置为基于创建的虚拟网元和虚拟链路集合，完成创建网络切片。
本公开实施例通过转发面的隧道(如LSP等)的方式建立虚拟网元之间的虚拟链路vLink，形成切片的网络，通过隧道及节点虚拟化的递归实现切片的嵌套。基于切片后的虚拟传送网和物理网络类似，可以承载各种业务，例如L2VPN、L3VPN等。
如图21所示，本公开实施例还提供一种控制器，包括存储器51、处理器52及存储在存储器51上并可在处理器52上运行的计算机程序53，所述处理器53执行所述程序时实现所述实现网络切片的方法。
所述控制器可以为SDN控制器。
本公开实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令由处理器执行时用于执行所述实现网络切片的方法。
在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、 可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。

Claims (11)

  1. 一种实现网络切片的方法，在物理网络层和业务层之间创建一层或多层嵌套的网络切片层，其中，通过如下步骤创建网络切片层中的每个网络切片：
    创建多个虚拟网元；
    基于隧道的方式创建虚拟网元之间的虚拟链路；
    建立网络切片与所述虚拟网元和虚拟链路的包含关系。
  2. 如权利要求1所述的方法，其中，所述创建多个虚拟网元包括：
    根据虚拟网元和虚拟端口的特性参数，创建所述虚拟网元以及所述虚拟网元的虚拟端口。
  3. 如权利要求2所述的方法，其中，所述虚拟网元的虚拟端口包括虚拟用户侧端口和虚拟网络侧端口。
  4. 如权利要求1所述的方法，其中，所述基于隧道的方式创建虚拟网元之间的虚拟链路，包括：
    根据所述虚拟链路的端口参数，创建隧道作为虚拟链路。
  5. 如权利要求4所述的方法，其中，所述根据所述虚拟链路的端口参数，创建隧道作为虚拟链路，包括：
    根据所述虚拟链路的端口参数和网络拓扑关系计算虚拟链路的路由，创建隧道作为虚拟链路。
  6. 如权利要求1～5中任意一项所述的方法，其中，所述隧道包括如下至少之一：
    标签交换路径隧道、灵活以太网隧道、分段路由隧道、光通路数据单元隧道。
  7. 如权利要求1所述的方法，其中，在物理网络层和业务层之间创建多层嵌套的网络切片层时，从下至上依次创建所述网络切片层。
  8. 如权利要求6所述的方法，其中，在物理网络层和业务层之间创建两层嵌套的网络切片层时，首层的网络切片层基于标签交换路径隧道、灵活以太网隧道和光通路数据单元隧道中的至少之一实现，次层的网络切片层基于标签交换路径隧道或分段路由隧道实现。
  9. 一种实现网络切片的装置，包括：
    网元创建模块，配置为创建多个虚拟网元；
    链路创建模块，配置为基于隧道的方式创建虚拟网元之间的虚拟链路；
    切片创建模块，配置为建立网络切片与所述虚拟网元和虚拟链路的包含关系。
  10. 一种控制器，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现如权利要求1～8中任意一项所述实现网络切片的方法。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令由处理器执行时用于执行权利要求1～8中任意一项所述实现网络切片的方法。
PCT/CN2019/119933 2018-11-23 2019-11-21 实现网络切片的方法、装置和控制器 WO2020103902A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
KR1020217017771A KR102653760B1 (ko) 2018-11-23 2019-11-21 네트워크 슬라이싱 구현 방법, 장치 및 컨트롤러
EP19886839.0A EP3886493A4 (en) 2018-11-23 2019-11-21 METHOD AND DEVICE FOR IMPLEMENTING NETWORK SLICING AND CONTROL DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811409431.8A CN111225419B (zh) 2018-11-23 2018-11-23 一种实现网络切片的方法、装置和控制器
CN201811409431.8 2018-11-23

Publications (1)

Publication Number Publication Date
WO2020103902A1 true WO2020103902A1 (zh) 2020-05-28

Family

ID=70774284

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/119933 WO2020103902A1 (zh) 2018-11-23 2019-11-21 实现网络切片的方法、装置和控制器

Country Status (4)

Country Link
EP (1) EP3886493A4 (zh)
KR (1) KR102653760B1 (zh)
CN (1) CN111225419B (zh)
WO (1) WO2020103902A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112291147A (zh) * 2020-10-15 2021-01-29 北京直真科技股份有限公司 一种5g业务动态智能sr隧道应用方法
CN112671650A (zh) * 2020-12-28 2021-04-16 网络通信与安全紫金山实验室 Sd-wan场景下的端到端sr控制方法、系统和可读存储介质
CN113014419A (zh) * 2021-02-01 2021-06-22 中盈优创资讯科技有限公司 一种5g承载子网切片自动开通方法及装置
WO2022110992A1 (zh) * 2020-11-27 2022-06-02 中兴通讯股份有限公司 网络切片管理方法、控制器及计算机可读存储介质
US20220182338A1 (en) * 2019-10-17 2022-06-09 Charter Communications Operating, Llc Method and apparatus for transporting data traffic using classifications
WO2023169285A1 (zh) * 2022-03-07 2023-09-14 华为技术有限公司 通信方法、装置、网络设备及系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115277548A (zh) * 2021-04-30 2022-11-01 中国移动通信有限公司研究院 一种传输方法、装置及存储介质
CN117480168A (zh) 2021-07-07 2024-01-30 株式会社Lg化学 化合物及包含其的有机发光器件

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103248572A (zh) * 2012-02-13 2013-08-14 上海贝尔股份有限公司 建立基于接入基础设施网络的虚拟链路的方法和装置
US20140301192A1 (en) * 2013-04-05 2014-10-09 Futurewei Technologies, Inc. Software Defined Networking (SDN) Controller Orchestration and Network Virtualization for Data Center Interconnection
WO2016095493A1 (zh) * 2014-12-19 2016-06-23 中兴通讯股份有限公司 一种资源虚拟化处理的方法、装置及控制器
CN108616386A (zh) * 2018-03-29 2018-10-02 西安交通大学 一种sdn虚拟网络环境的构建方法及sdn虚拟网络环境
CN108809794A (zh) * 2017-05-04 2018-11-13 中兴通讯股份有限公司 基于sdn的传送网虚拟网络创建方法和装置及传送网络系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10644955B2 (en) * 2015-08-21 2020-05-05 Huawei Technologies Co., Ltd. Method and apparatus for network slicing
WO2018076359A1 (zh) * 2016-10-31 2018-05-03 华为技术有限公司 管理网络切片的方法、装置和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103248572A (zh) * 2012-02-13 2013-08-14 上海贝尔股份有限公司 建立基于接入基础设施网络的虚拟链路的方法和装置
US20140301192A1 (en) * 2013-04-05 2014-10-09 Futurewei Technologies, Inc. Software Defined Networking (SDN) Controller Orchestration and Network Virtualization for Data Center Interconnection
WO2016095493A1 (zh) * 2014-12-19 2016-06-23 中兴通讯股份有限公司 一种资源虚拟化处理的方法、装置及控制器
CN108809794A (zh) * 2017-05-04 2018-11-13 中兴通讯股份有限公司 基于sdn的传送网虚拟网络创建方法和装置及传送网络系统
CN108616386A (zh) * 2018-03-29 2018-10-02 西安交通大学 一种sdn虚拟网络环境的构建方法及sdn虚拟网络环境

Non-Patent Citations (1)

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

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220182338A1 (en) * 2019-10-17 2022-06-09 Charter Communications Operating, Llc Method and apparatus for transporting data traffic using classifications
US12081459B2 (en) * 2019-10-17 2024-09-03 Charter Communications Operating, Llc Method and apparatus for transporting data traffic using classifications
CN112291147A (zh) * 2020-10-15 2021-01-29 北京直真科技股份有限公司 一种5g业务动态智能sr隧道应用方法
WO2022110992A1 (zh) * 2020-11-27 2022-06-02 中兴通讯股份有限公司 网络切片管理方法、控制器及计算机可读存储介质
CN112671650A (zh) * 2020-12-28 2021-04-16 网络通信与安全紫金山实验室 Sd-wan场景下的端到端sr控制方法、系统和可读存储介质
CN112671650B (zh) * 2020-12-28 2022-07-22 网络通信与安全紫金山实验室 Sd-wan场景下的端到端sr控制方法、系统和可读存储介质
CN113014419A (zh) * 2021-02-01 2021-06-22 中盈优创资讯科技有限公司 一种5g承载子网切片自动开通方法及装置
WO2023169285A1 (zh) * 2022-03-07 2023-09-14 华为技术有限公司 通信方法、装置、网络设备及系统

Also Published As

Publication number Publication date
KR102653760B1 (ko) 2024-04-01
CN111225419B (zh) 2023-04-18
CN111225419A (zh) 2020-06-02
KR20210089233A (ko) 2021-07-15
EP3886493A4 (en) 2022-08-17
EP3886493A1 (en) 2021-09-29

Similar Documents

Publication Publication Date Title
WO2020103902A1 (zh) 实现网络切片的方法、装置和控制器
US8456984B2 (en) Virtualized shared protection capacity
US8531969B2 (en) Path computation systems and methods for heterogeneous multi-domain networks
CN107852365B (zh) 用于动态vpn策略模型的方法和装置
CN107637031B (zh) 用于网络业务的路径计算单元中央控制器
Bitar et al. Technologies and protocols for data center and cloud networking
CN111492627B (zh) 为不同应用建立不同隧道的基于控制器的服务策略映射
ES2835326T3 (es) Controlador de múltiples dominios, controlador de dominio único y sistema y método de red óptica definida por software
US10003867B2 (en) Disjoint path computation systems and methods in optical networks
US10263848B2 (en) Compiler for and method for software defined networks
US8942256B1 (en) Advertising with a layer three routing protocol constituent link attributes of a layer two bundle
US8553707B2 (en) Administrative boundaries in single or multiple domain optical networks
US9559944B2 (en) Method and related apparatus for establishing link-diverse traffic paths in a telecommunications network
US10205523B2 (en) Designing and configuring packet optical networks
US8787394B2 (en) Separate ethernet forwarding and control plane systems and methods with interior gateway route reflector for a link state routing system
US10097306B1 (en) Path computation systems and methods in control plane based networks for photonic layer topologies
EP2549689A2 (en) Hybrid packet-optical private network systems and methods
EP1585263A1 (en) System and method for managing communications in an access network
US10097909B2 (en) Systems, apparatus, and methods for segment routing of optical signals
WO2018233580A1 (zh) 一种网络中建立转发路径的方法、控制器及系统
CN112333076B (zh) 通过FlexE通道承载VXLAN业务的方法及装置
US20200274739A1 (en) Methods, Nodes and Computer Readable Media for Tunnel Establishment Per Slice
CN112436990A (zh) 一种数据转发方法、设备以及计算机可读存储介质
Zhu et al. Ethernet-over-SONET (EoS) over WDM in optical wide-area networks (WANs): benefits and challenges
Taniguchi Dynamic network service control and management techniques across multi-provider networks.

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

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

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019886839

Country of ref document: EP

Effective date: 20210623