Network slice isolation method and device, equipment and storage medium

Abstract

The invention discloses a network slice isolation method, apparatus and device, and a storage medium. The method comprises the steps of constructing a corresponding Yang data model; receiving a network slicing request of a user, and creating a plurality of isolated network slices according to the network slicing request and the model information of the Yang data model; the network slices comprise soft isolation network slices and hard network isolation slices; and according to the created network slices, generating a corresponding L3VPN service for each network slice, mapping the L3VPN services to the corresponding network slices, and creating connectivity services in the current transmission network, so that communication between end points of the network slices is realized, and isolation of the network slices is completed. According to the invention, soft and hard isolation of the network slice can be realized.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a network slicing isolation method, device, equipment and storage medium. Background Art

[0002] Network slicing refers to dividing a physical network into multiple virtual networks, each of which is architected and optimized for specific applications / services. In this context, the Next Generation Mobile Network (NGMN) defines two main concepts: a service instance (SI) is an end-user service or business service implemented in a network slice; and a network slice instance (NSI) is a complete, instantiated logical network that meets the specific characteristics required by a service instance.

[0003] Therefore, network slicing is the sharing of network infrastructure between different service instances to meet network-specific requirements. Network slicing can be changed depending on the communication layer of the network operator implementing network slicing, resource management, network characteristics, or toolkits used to implement network slicing. Some examples of network characteristics required by service instances include ultra-low latency or ultra-reliability, etc., but there is currently no detailed and professional explanation of how to perform network slicing isolation in the existing technology. Summary of the invention

[0004] The present invention provides a network slice isolation method, device, equipment and storage medium to solve the technical problem that there is no detailed and professional explanation of how to perform network slice isolation in the current prior art.

[0005] In order to solve the above technical problems, an embodiment of the present invention provides a network slice isolation method, including:

[0006] Obtain preset endpoint information, customer information, and a service level agreement for slice requests, and construct a corresponding Yang data model according to the endpoint information, customer information, and the service level agreement for slice requests; wherein the endpoint information is the communication end point of the network slice to be created; the customer information is the terminal for the customer to request configuration of the network slice; the service level agreement includes: performance requirements, resource isolation level, optimization criteria, and node link characteristics of the network slice to be created;

[0007] Receive a network slice request from a user, and create a number of isolated network slices according to the network slice request and the model information of the Yang data model; wherein the network slice request includes: the service type, performance indicator and isolation requirement required for the network slice to be created; the network slice includes: soft isolated network slices and hard isolated network slices;

[0008] According to the created network slices, a corresponding L3VPN service is generated for each network slice, the L3VPN service is mapped to the corresponding network slice, and a connectivity service is created in the current transmission network to enable communication between the endpoints of each network slice, thereby completing the isolation of the network slices.

[0009] As a preferred solution, according to the created network slice, a corresponding L3VPN service is generated for each network slice, the L3VPN service is mapped to the corresponding network slice, and a connectivity service is created in the current transmission network to enable communication between endpoints of each network slice, thereby completing the isolation of the network slice, including:

[0010] Generate corresponding L3VPN services for each network slice according to the created network slices, map the L3VPN services to the corresponding network slices, and verify the connectivity between the network slices;

[0011] When the connectivity verification between each network slice is passed, a connectivity service is created in the current transmission network to enable communication between the endpoints of each network slice, and the business continuity between each network slice is verified. When the business continuity verification between each network slice is passed, the isolation of the network slice is completed.

[0012] As a preferred solution, generating a corresponding L3VPN service for each network slice according to the created network slice, and mapping the L3VPN service to the corresponding network slice includes:

[0013] Generate corresponding L3VPN parameters according to the network slice request, and generate corresponding L3VPN services for each network slice according to the L3VPN parameters and the created network slice;

[0014] Allocate resources for each L3VPN service and create a corresponding VRF instance, associate each VRF instance with a corresponding network slice, and map the L3VPN service to the corresponding network slice; wherein the resources include: bandwidth and virtual routers.

[0015] As a preferred solution, the creating a connectivity service in the current transport network to enable communication between endpoints of each network slice includes:

[0016] Determine the communication requirements between the network slice endpoints according to the network slice request;

[0017] According to the communication requirements and the preset API interface, a connectivity service is created in the current transmission network, and the optimal transmission path is calculated. According to the optimal transmission path, resources are allocated between the endpoints of each network slice, and physical connections are established between the endpoints to enable communication between the endpoints of each network slice.

[0018] Based on the above embodiment, another embodiment of the present invention provides a network slice isolation device, including: a Yang data model construction module, a network slice creation module and a network slice isolation module;

[0019] The Yang data model construction module is used to obtain preset endpoint information, customer information and a service level agreement for slice requests, and construct a corresponding Yang data model according to the endpoint information, customer information and the service level agreement for slice requests; wherein the endpoint information is the communication end point of the network slice to be created; the customer information is the terminal for the customer to request the configuration of the network slice; the service level agreement includes: performance requirements, resource isolation level, optimization criteria and node link characteristics of the network slice to be created;

[0020] The network slice creation module is used to receive a network slice request from a user, and create a plurality of isolated network slices according to the network slice request and the model information of the Yang data model; wherein the network slice request includes: the service type, performance index and isolation requirement required for the network slice to be created; the network slice includes: soft isolated network slice and hard isolated network slice;

[0021] The network slice isolation module is used to generate corresponding L3VPN services for each network slice according to the created network slices, map the L3VPN services to the corresponding network slices, and create connectivity services in the current transmission network to enable communication between the endpoints of each network slice, thereby completing the isolation of the network slices.

[0022] As a preferred solution, according to the created network slice, a corresponding L3VPN service is generated for each network slice, the L3VPN service is mapped to the corresponding network slice, and a connectivity service is created in the current transmission network to enable communication between endpoints of each network slice, thereby completing the isolation of the network slice, including:

[0023] Generate corresponding L3VPN services for each network slice according to the created network slices, map the L3VPN services to the corresponding network slices, and verify the connectivity between the network slices;

[0024] When the connectivity verification between each network slice is passed, a connectivity service is created in the current transmission network to enable communication between the endpoints of each network slice, and the business continuity between each network slice is verified. When the business continuity verification between each network slice is passed, the isolation of the network slice is completed.

[0025] As a preferred solution, generating a corresponding L3VPN service for each network slice according to the created network slice, and mapping the L3VPN service to the corresponding network slice includes:

[0026] Generate corresponding L3VPN parameters according to the network slice request, and generate corresponding L3VPN services for each network slice according to the L3VPN parameters and the created network slice;

[0027] Allocate resources for each L3VPN service and create a corresponding VRF instance, associate each VRF instance with a corresponding network slice, and map the L3VPN service to the corresponding network slice; wherein the resources include: bandwidth and virtual routers.

[0028] As a preferred solution, the creating a connectivity service in the current transport network to enable communication between endpoints of each network slice includes:

[0029] Determine the communication requirements between the network slice endpoints according to the network slice request;

[0030] According to the communication requirements and the preset API interface, a connectivity service is created in the current transmission network, and the optimal transmission path is calculated. According to the optimal transmission path, resources are allocated between the endpoints of each network slice, and physical connections are established between the endpoints to enable communication between the endpoints of each network slice.

[0031] Based on the above embodiments, another embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, and when the processor executes the computer program, the network slice isolation method described in the above embodiments of the invention is implemented.

[0032] Based on the above embodiments, another embodiment of the present invention provides a storage medium, which includes a stored computer program, wherein when the computer program is running, the device where the storage medium is located is controlled to execute the network slice isolation method described in the above invention embodiment.

[0033] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0034] The present invention provides a network slice isolation method, which obtains preset endpoint information, customer information and a service level agreement of a slice request, and constructs a corresponding Yang data model according to the endpoint information, customer information and the service level agreement of the slice request; wherein the endpoint information is the communication end point of the network slice to be created; the customer information is the terminal for the customer to request to configure the network slice; the service level agreement includes: performance requirements, resource isolation level, optimization criteria and node link characteristics of the network slice to be created; receiving a user's network slice request, and creating several isolated network slices according to the network slice request and the model information of the Yang data model; wherein the network slice request includes: service type, performance index and isolation requirements required for the network slice to be created; the network slice includes: soft isolated network slice and hard isolated network slice; according to the created network slice, a corresponding L3VPN service is generated for each network slice, the L3VPN service is mapped to the corresponding network slice, and a connectivity service is created in the current transmission network, so that the endpoints of each network slice can communicate with each other, and the isolation of the network slice is completed. Through the present invention, the soft and hard isolation of network slices can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 It is a flowchart of a network slice isolation method provided by an embodiment of the present invention;

[0036] Figure 2 It is a flowchart for realizing network slice isolation;

[0037] Figure 3 This is the overall architecture diagram of the iFUSIONN architecture;

[0038] Figure 4 It is a structural schematic diagram of a network slice isolation device provided by one embodiment of the present invention. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions in this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0040] Embodiment 1

[0041] Please refer to Figure 1 , is a flow chart of a network slice isolation method provided by an embodiment of the present invention, comprising the following specific steps:

[0042] S1. Obtain preset endpoint information, customer information, and a service level agreement for slice requests, and construct a corresponding Yang data model according to the endpoint information, customer information, and the service level agreement for slice requests; wherein the endpoint information is the communication end point of the network slice to be created; the customer information is the terminal for the customer to request the configuration of the network slice; the service level agreement includes: performance requirements, resource isolation level, optimization criteria, and node link characteristics of the network slice to be created;

[0043] The present invention provides a network slice isolation method, please refer to Figure 2 , a flow chart for realizing network slice isolation, including the following steps:

[0044] 1. Introduction to soft, hard and 5G network slicing:

[0045] 1. Network Slicing:

[0046] The concept of network slicing provides a framework that is widely applicable to various industries. One of the main factors driving network slicing is the implementation of the fifth generation (5G) network. Due to the need to integrate multiple services with different performance requirements such as high throughput, low latency, high reliability, high mobility and high security into a single physical network infrastructure, and provide a customized logical network for each service. Network slicing is a key technology to achieve the above goals. There are two main options for implementing network slicing: hard slicing and soft slicing, which will be described below.

[0047] 1) Soft network slicing:

[0048] Slicing corresponds to a lower level of isolation between services transported by the network. Soft slicing means sharing the physical infrastructure but creating logical segmentations between customers. Traditional IP network resource management (L3VPNs) are an example of soft slicing implementation in MPLS networks, because a VPN can be considered as a series of tunnels connecting customer sites, each site may have different Quality of Service (QoS) treatment, and all traffic to and from each site is internal to the customer. In the VPN service, the provider ensures that each customer's traffic is logically distinguished from the shared physical infrastructure according to the routing policy configuration of the entire network. In this sense, network slicing at the MPLS level can be achieved in the following ways:

[0049] Virtual Routing and Forwarding (VRF), which allows multiple routing environments to be implemented on a shared MPLS transport network.

[0050] Virtual Switching Interfaces (VSIs) enable multiple switching environments on the same shared infrastructure.

[0051] Each physical router is capable of hosting multiple VRFs and multiple VSIs (and their attached logical interfaces), effectively partitioning it into multiple routing and switching environments that can be assigned to different tenants / customers / services.

[0052] 2) Hard network slicing:

[0053] Although overlay MPLS tunnels may offer obvious advantages, there are also some disadvantages. Overlay tunnels established through data encapsulation cannot see or control the underlying physical network. As more and more tunnels are deployed on shared physical infrastructure, network congestion is bound to become a concern. Therefore, VRFs, VSIs, or optical data units (ODus) cannot be managed directly by their corresponding tenants because they belong to the same management domain represented by physical devices and need to be operated by network administrators. Due to the large number of tunnels and services in complex networks, QoS and traffic engineering policy management become critical tasks to ensure the correct SLAs are provided to customers.

[0054] The solution to this limitation and the way to move the network industry to a more automated scenario is hard slicing. Hard slicing refers to the provision of dedicated resources for a specific network slice instance. For example, data plane resources are provided by allocating time domain multiplexing resources (such as Flex Ethernet Channel) or as services such as MPLS hard pipes, route diversity (disjoint paths), wavelength selection, etc.

[0055] Disaggregated routers are an example of hard slicing. The data plane runs inside the physical device and the control plane runs outside the device in a remote cloud or server. This removes the 1:1 relationship between the physical device and the routing logic, allowing multiple virtual routers to be supported on a single physical network device. Each of these virtual routers is a full-fledged router capable of hosting multiple VRFs and VSIs or being managed independently of other virtual routers running on the same device. As a result, virtual routers are administratively decoupled from each other, meaning that separate virtual routers can be assigned to different tenants, each of which can directly manage the virtual routers without the need for intervention by the operator who owns the physical network. Network slicing at the IP transport level can be accomplished by grouping multiple virtual routers running on a shared physical network infrastructure into a common virtual infrastructure under their separate management domains. Virtual routers under the same management domain are called hard network slices, so different hard slices can be assigned to different tenants.

[0056] 3) 5G network slicing

[0057] 5G must enable network operators to ensure that the same network can meet the heterogeneous needs of different types of applications. To effectively implement these needs and determine how to allocate network resources, service providers must integrate technologies such as software-defined networking (SDN), network function virtualization (NFV), and machine learning (ML) with a layered transport architecture. According to the 5G definition, this architecture has three main components:

[0058] Radio Access Network (RAN): It covers everything related to the air interface between user elements and base stations. RAN interfaces and interconnections are specified by the 3GPPP Architecture Working Group.

[0059] Mobile Core (MC): Its core role is to act as a gateway for user traffic to and from the Internet. The Mobile Core consists of a set of Network Functions (NFs) responsible for managing user mobility, access authentication, access authorization, location service management, registration, and establishing per-user tunnels between base stations for different traffic types.

[0060] The backhaul network is the network that connects the RAN and the MC. It is not part of the 5G specification, so it is up to each network operator to decide how to implement it. It requires features such as QoS management, synchronization, and protocol stacks such as IP / MPLS or segment routing.

[0061] Network slicing functionality needs to be available in all components of a 5G cellular network (RAN, MC, backhaul network) to ensure differentiated treatment of packets in the network. Therefore, the 5G working group has specified a set of standard network slices, called Standardized Slice Types (SSTs), to determine how resources are allocated on the RAN and MC.

[0062] 5G specifies two network slicing mechanisms. The first is based on QoS technology and is called soft network slicing by dynamically allocating available network resources to different classes of traffic. The second leverages 5G's software-based, cloud-based architecture and component disaggregation to achieve slicing through 5G component virtualization and replication. This second approach is called hard network slicing.

[0063] 2. Proposed Architecture

[0064] iFUSION architecture is an architecture defined by Telefonica to enhance network automation and programmability in service provider environments. Figure 3, which is a schematic diagram of the overall architecture of the iFUSIONN architecture. iFUSION is a two-layer control architecture with specific domain controllers for each technology area (IP / MPLS, microwave and optical) at the bottom, and a software-defined transport network controller (SDTN controller) handling multi-layer and multi-domain transport network resources. The domain controller communicates directly with the network elements, and the SDTN controller communicates directly with the OSS / BSS system. In addition to the functional block definition, iFUSION also includes the use of: (1) standard interfaces based on RESTCONF / YANG for communication between control components and NETCONF / YANG to configure network elements; (2) YANG data models based on the latest versions of standard development organizations (SDOs): IETF, ONF and OpenConfig

[0065] Figure 3 The network scheme of the iFUSION architecture is presented, including the components and the relationships between them. Each structural pillar in the architecture is defined below, including their role in network slicing:

[0066] 1) Software-defined transport network controller:

[0067] The Software Defined Transport Network (SDTN) Controller is a functional module with the following features: It is the main entry point from the Operation Support System (OSS) / Business Support System (BSS) system to the network. It is responsible for coordinating / providing services through multiple domains and layers. It has a topological view of the multi-layer / multi-domain network. The SDTN controller can segment the requirements based on technical needs. In this process, the SDTN controller can add / allocate logical resources for use by the network when the business is implemented. The SDTN controller has two RESTCONF interfaces, one for handling the requirements of the OSS / BSS system and the other for sending specific requests to the domain controller.

[0068] 2) Network Slice Controller:

[0069] The Network Slice Controller (NSC) implements transport network slices in the underlying transport infrastructure and manages and controls the status of resources and topology associated with them. The NSC receives transport network slice requests from the Operation Support System and Business Support System (OSS / BSS). The NSC runs the internal workflows for transport network slice lifecycle management and interacts with the underlying IP and optical domain controllers through the RESTCONF client. The Network Slice Controller provides the ability to create / modify / delete, monitor and optimize network slices in a multi-domain, multi-technology and multi-vendor environment. It has two main functions:

[0070] Mapping: The NSC must map network slice requests to the underlying technology-specific infrastructure. It therefore maintains a mapping record from user requests to slice instantiations to allow subsequent control functions such as modification or deletion.

[0071] Implementation: The NSC shall implement the network slice request to the domain controller using its SBI interface in a physical or logical connection through VPNs or various tunneling technologies (such as segment routing, MPLS, etc.).

[0072] 3) Network domain controller:

[0073] The network domain controller (SDN controller) is responsible for managing network elements (network domains). It has a standard southbound interface for communicating with network elements. The domain controller SBI relies on the use of the Network Configuration Protocol (NETCONF) to interact with network elements of the underlying technology. The SDN controller also has a northbound interface to communicate with the SDTN controller or OSS / BSS system via RESTCONF.

[0074] 4) Yang model of network controller:

[0075] As mentioned before, the three control elements: SDTN controller, network slice controller and network domain controller, have standard SBI and NBI interfaces for communication between them and with the network or OSS / BSS systems. The standard interface consists of the protocol for selecting the data to be transmitted and the YANG data model that defines how the messages are formed. The YANG data model includes service level agreements for endpoints, customer information and slice requests. In a sense, the YANG modeling activity has gained significant relevance across standardization entities. By 2019, the number of YANG models correctly extracted from IETF drafts was 283, 214 in the Broadband Forum and 137 in Openconfig; similarly, other organizations such as MEF, 3GPP or ONF have also produced YANG data models to describe technologies, protocols or connectivity services. Therefore, from the perspective of architecture definition, it becomes a fundamental task to browse the large number of available YANGs and select the appropriate data model package to define the interface of each functional block.

[0076] 3. Instantiation of network slices in SDN transport networks:

[0077] OSS / BSS systems can request the deployment of new network slices with certain transport characteristics. Each network slice must be isolated from any other network slice or different services delivered to a specific customer, and naturally, other network slices or services must not negatively impact the delivery of the requested transport network slice.

[0078] To provide this isolation and instantiate shards in the network, there are a number of implementation options, ranging from softer isolation levels to the hardest isolation level, as follows:

[0079] No isolation, meaning that slices are not separated. Logical isolation, where slices are logically separated, with only a certain degree of isolation enforced through QoS mechanisms. Service isolation, where virtual resources and NFs are shared. Process isolation, where slices include process and thread isolation. Virtual resource isolation, where slices have dedicated virtual resources. Network function isolation, where a network function (NF) is dedicated to a single network slice. Physical isolation, where slices are completely physically separated, e.g., in different locations. Physical network isolation, where slices contain physically separated links.

[0080] Since the isolation level is an important constraint to be considered in network slicing implementation, the selected network infrastructure and the selected control elements will generate different sets of functions in the network slice controller. Several possibilities are described below from the perspective of mapping and implementation tasks of the network slice controller:

[0081] 1) Network slice controller as part of the hierarchical controller:

[0082] When the network slice controller is a hierarchical SDN controller module, the network slice controller (NSC) and the hierarchical network controller should share the same internal data and the same network boundary interface (NBI). Therefore, in order to handle the customer's view, the hierarchical SDN module must be able to:

[0083] Mapping: Customer requests received using NCS must be processed by NCS. The mapping process maps the network slice SLAs selected by the customer to the available routing policies and forwarding policies. Implementation: Create the necessary network requests. The implementation of the slice can be translated into one or more LXNM network requests. Therefore, NCS must have a complete view of the network to map the orders and distribute them across domains. The implementation should include the extension / selection of forwarding policies, routing policies, VPN policies, and underlying transport priorities.

[0084] To maintain data consistency between control planes, the network-slice-id used must be directly mapped to the transport-instance-id at the VPN-Node level.

[0085] 2) Network slice controller as an independent controller:

[0086] When the network slice controller is a standalone controller module, the NSC should perform the same two tasks as described previously:

[0087] Mapping: Handles customer requests. Customer requests can be sent using [draft-liu-tea-transport-networkslice-yang-01]. This draft allows topology mapping of slice requests. Implementation: Creates the necessary network requests. The implementation of the slice will be translated into an LXNM network request. Since the NCS has a topological view of the network, the implementation includes the customer's traffic engineering transport preferences and policies.

[0088] 3) Network slice controller at domain controller level:

[0089] The network slice controller can be at the same level as the network domain controller. The SDTN controller handles slice requests, which can be implemented by the NSC communicating directly with the network elements. The SDTN controller should create a unified view of the network, including each transport domain and network slice. Mapping: The SDTN will handle customer requests. Customer requests can be sent using [draft-liu-tea-transport-networkslice-yang-01]. This draft allows topology mapping for slice requests. Implementation: Implementation can be done by creating policies directly on the network elements through the NCS controller applying service logic. The SDTN should handle shared resource management between domains.

[0090] 4) Network slice controller as part of domain controller:

[0091] When the network slice controller is part of the domain controller, the OSS / BSS system handles the slice request and introduces the network abstraction layer. At the network level, the NBI and SBI of the SDN controller will use the same device data model. Direct conversion will reduce the service logic implemented at the SDN controller level, grouping mapping and conversion into a single task. Mapping and implementation: Mapping and implementation can be done by the domain controller applying service logic to create policies directly on the network element. The network slice controller is used to receive all service requests. In order to interact with the transport domain, there are two controllers, one IP and one optical.

[0092] 4. Steps to achieve isolation:

[0093] 1. Define the Yang data model, which includes endpoints, customer information, and service level agreements for slice requests.

[0094] Among them, endpoint refers to the communication end point defined in the network slice service, which represents the interface of the user device, server or router that actually transmits data in the network. In our design, the endpoint information will be mapped to a specific VRF instance in the virtual router so that different network traffic can be processed independently through these VRFs. In fact, each virtual router can be configured with multiple VRFs. VRF is a virtualization technology that can create multiple virtual routing tables on the same physical router. Traffic from different customers or services can be processed independently on the same device without interfering with each other. Customer information includes: the device or application that the customer requests configuration or status data, that is, the identifier; configurable settings of the device or system, such as the IP address and subnet mask of the network router, which contain specific functions or business requirements; traffic, connection status, etc. of the network device, to monitor device performance, troubleshoot or optimize configuration; for more specific definitions, see: The service level agreement for slice requests includes: 1) Performance requirements: Delay tolerance: defines the maximum delay that the network slice can accept; Periodicity: specifies the periodic requirements of the service, such as the frequency of data transmission; 2) Resource isolation level: determines the resource isolation requirements of the network slice to prevent resource interference between different slices. 3) Optimization criteria: define the goals of the slice in network performance optimization, such as maximizing throughput or minimizing latency. 4) Node and link characteristics: specify specific computing and storage resources.

[0095] The iFusion architecture proposed in this invention is enhanced to manage services and resources by using information models. These information models capture management entities defined in terms of attributes and supported operations. Therefore, a set of Yang data models have been defined to implement network slicing between control entities.

[0096] The iFusion architecture enhances how to implement service and resource management: the iFusion architecture has a unified management platform, a comprehensive view (integrating different IP layers, different domains, etc.), and can perform network slicing management and other aspects of enhanced management, which are reflected in: 1) unified modeling language; 2) object model (abstracting management entities into objects, which have attributes such as name and type and supporting operations such as configuration and control); 3) definition of attributes and supporting operations; 4) YANG data model for structured and standardized representation.

[0097] How to capture the definition of management entities: YANG is a data modeling language used to model configuration data, state data, remote procedure calls, and notifications used by network configuration management protocols (such as RESTCONF). YANG describes data structures, data integrity constraints, and data operations to form a YANG model.

[0098] Model structure: 1) Define the entities, attributes, and relationships required for network slicing 2) Divide the hierarchical structure of the data model and define the relationship between each entity. 3) Use the Yang language to define the syntax and semantics of the data model, including elements such as modules, containers, lists, and leaves.

[0099] How to build the Yang data model: Model input and output: 1) Input: Based on the needs of network slicing, input the configuration parameters, resource requirements, service requirements and other information of the network slice. 2) Output: Generate network slice configuration information that conforms to the definition of the Yang data model, including the attributes and configuration of each entity.

[0100] Model training process: 1) Collect network slice requirements and constraints, including service types, resource requirements, QoS requirements, etc. 2) Design the structure and attributes of the Yang data model according to the requirements to ensure that the requirements of the network slice can be accurately captured. 3) Use appropriate tools and editors to write Yang model files 4) Verify the correctness and completeness of the data model

[0101] How to implement network slicing: 1) Configuration management entity; 2) Resource allocation and scheduling; 3) Real-time monitoring and optimization; 4) Ensure security and isolation.

[0102] S2. Receive a network slice request from a user, and create a number of isolated network slices according to the network slice request and the model information of the Yang data model; wherein the network slice request includes: the service type, performance index and isolation requirement required for the network slice to be created; the network slice includes: soft isolated network slice and hard isolated network slice;

[0103] 2. Create multiple isolated network slices based on the defined Yang data model information, where the SDTN controller will accept network slice services and convert them into specific domain requests, including L3VPN services and connectivity requests.

[0104] Among them, the user sends a slice request: the SDTN controller receives the user's network slice request to create an isolated network slice. That is, the user sends a network slice request to the SDTN controller, including the required service type, performance indicators and isolation requirements.

[0105] Translate Request: The SDTN controller parses the parameters in the request to determine the specific requirements of each slice. The SDTN controller translates the network slice service request into a specific domain request.

[0106] Use of YANG data model: Through the YANG data model, the controller can represent and manage the properties and structure of network slices. The YANG model defines various properties of network slices. The controller uses this model to interact with the IP domain controller to create L3VPN services.

[0107] L3VPN service creation: Each network slice request requires the creation of an L3VPN (Layer 3 Virtual Private Network) service. Each L3VPN service is mapped to a specific network slice and has its own dedicated L3VPN service. The endpoints defined in the request will be mapped to virtual routers and forwarding instances (VRFs), allowing each network slice to manage its traffic and resources independently.

[0108] That is to say, through the SDTN controller, users can request multiple isolated network slices. The creation of each slice involves the setting of L3VPN services to ensure that each slice has independent traffic management and resource allocation. Therefore, the YANG data model is used to ensure that all requests and settings comply with standards and protocols.

[0109] S3. Based on the created network slices, generate corresponding L3VPN services for each network slice, map the L3VPN services to the corresponding network slices, and create connectivity services in the current transmission network to enable communication between the endpoints of each network slice, thereby completing the isolation of the network slices.

[0110] Preferably, generating a corresponding L3VPN service for each network slice according to the created network slice, and mapping the L3VPN service to the corresponding network slice, includes: generating corresponding L3VPN parameters according to the network slice request, and generating corresponding L3VPN services for each network slice according to the L3VPN parameters and the created network slice; allocating resources for each L3VPN service and creating a corresponding VRF instance, associating each VRF instance with the corresponding network slice, and mapping the L3VPN service to the corresponding network slice; wherein the resources include: bandwidth and virtual routers.

[0111] Preferably, the creation of a connectivity service in the current transmission network to enable communication between endpoints of each network slice includes: determining the communication requirements between endpoints of each network slice based on the network slice request; creating a connectivity service in the current transmission network based on the communication requirements and a preset API interface, and calculating an optimal transmission path, allocating resources between endpoints of each network slice based on the optimal transmission path, and establishing a physical connection between endpoints to enable communication between endpoints of each network slice.

[0112] Preferably, according to the created network slices, a corresponding L3VPN service is generated for each network slice, the L3VPN service is mapped to the corresponding network slice, and a connectivity service is created in the current transmission network to enable communication between the endpoints of each network slice and complete the isolation of the network slices, including: according to the created network slices, a corresponding L3VPN service is generated for each network slice, the L3VPN service is mapped to the corresponding network slice, and the connectivity between the network slices is verified; when the connectivity between the network slices is verified, a connectivity service is created in the current transmission network to enable communication between the endpoints of the network slices, and the service continuity between the network slices is verified. When the service continuity between the network slices is verified, the isolation of the network slices is completed.

[0113] 3. For L3VPN services, the endpoints defined in the slice request are mapped to the virtual routing and forwarding (VRF), and an L3VPN service is created for each network slice to ensure that each L3VPN service will be mapped to a single network slice, achieving soft and hard isolation between multiple slices at the network level.

[0114] To request standards-based and model-driven isolated network slice usage, the SDTN controller will receive network slice services and convert them into specific per-domain requests as follows:

[0115] (a) Create L3VPN service: In this part, each network slice request needs to create an L3VPN service; therefore, each L3VPN service will be mapped to a single network slice. The endpoints defined in the slice request will be mapped to the virtual router and forwarding (VRFs) instances on the virtual router. The Yang data model used by SDTN to request L3VPN services from the IP domain controller is L3NM.

[0116] How to create L3VPN service: L3VPN is a layer 3 virtual private network, which is a network service that provides layer 3 isolation and reachability in the service provider network and is an IP network resource management measure.

[0117] Through the following steps, you can create an independent L3VPN service for each network slice request in the iFusion architecture. Creation steps: 1) Receive network slice request; 2) Define L3VPN parameters; 3) Allocate resources (such as bandwidth, configure virtual routers, etc.); 4) Create VRF instances (configure an independent VRF instance for each L3VPN service); 5) Configure routing policies; 6) Connect endpoints (endpoints in slice requests are mapped to corresponding VRF instances); 7) Check configuration; 8) Enable L3VPN services; 9) Monitor and manage

[0118] How to map L3VPN services to a single network slice: Configure an independent VRF instance for each L3VPN service, and associate each VRF instance with the corresponding network slice to ensure that each network slice has a corresponding L3VPN service. That is, ensure that each network slice request is mapped to a single L3VPN service, thereby achieving a one-to-one correspondence between network slices and L3VPN services. Function: Realize isolation and independence between network slices, ensure service quality, and improve network management efficiency.

[0119] 4. For network connectivity, create new connectivity services in the transport network to enable cross-layer communication between network slice endpoints.

[0120] (b) DWDM connectivity: New connectivity services are created in the transport network using T-API, enabling L2-L1 communication between network slice endpoints.

[0121] How to create a new connectivity service in the transport network: Operations: 1) Determine requirements (bandwidth, reliability, etc.); 2) Use T-API (use this interface for communication); 3) Define connectivity services (requirements for bandwidth, starting endpoints, etc.); 4) Calculate the optimal transmission path; 5) Allocate resources; 6) Establish physical connections between endpoints; 7) Verify and monitor (ensure connection correctness and monitor in real time)

[0122] The reasons why L2-L1 communication between network slice endpoints is possible: 1) The physical connection created enables cross-layer data transmission (L2 (data link layer)-L1 (physical layer) communication); 2) Through T-API, flexible configuration and efficient utilization of transmission network resources can be achieved, providing more flexible and adaptive support for L2-L1 communication; 3) New connectivity services are created to help form independent communication channels between different network slices and achieve isolation between slices.

[0123] 5. After creating isolated network slices, verify the IP connectivity between network slices to ensure correct transmission of data packets.

[0124] 6. Verify the continuity of network slicing services to ensure the normal status of system services.

[0125] 7. After the IP connectivity and business continuity tests are passed, the isolated network slice is successfully created and the system service status is normal, which can ensure the reliability of service and data packet transmission and business continuity, and realize the isolation of network soft and hard slices of 5G network

[0126] Adding and destroying prefixes: This part expects to verify IP connectivity between network slices. Spirent testers announce a set of 5k IP prefixes through the previously created network slice. The testers then conduct automatic IP reachability testing and CLI route redistribution verification. Once route propagation is verified, the test team stops the announcement of all Spirent prefixes and conducts a new automatic connectivity test.

[0127] After end-to-end service creation and control and data plane verification, we rebooted the device to verify service continuity after a simulated power failure. We verified that all traffic was flowing again between network slices after the recovery was complete.

[0128] 1. Add 5k IP prefix corresponding operation: respond to the user's 5k IP prefix addition request, that is, update the routing table: add these new IP prefixes to the routing table. 2) Update network configuration: according to the new IP prefix, update the configuration of network devices to ensure that the data packet can be correctly routed to the destination.

[0129] 2. Operations corresponding to the IP reachability test: Verify the connectivity of the newly added IP prefix to ensure that the data packet can be transmitted correctly. 1) Test data packet generation (including some target IP address and identification information); 2) Routing table query; 3) Data packet transmission; 4) Data packet reception; 5) Response data packet transmission (after the target device receives it, it will process and generate a response data packet and return it to the sending device along the opposite path); 6) Response data packet reception and analysis (analyze to understand whether the target device receives and responds normally); 7) Connectivity test (based on the previous step, determine whether there is good connectivity between the sending and target devices).

[0130] 3. CLI route redistribution verification corresponding operation: The system redistributes routes based on the newly added prefix to ensure that the routing information in the network is up to date.

[0131] 1) Verify routing information updates (ensure that new routing information is updated to network devices); 2) Update routing tables; 3) Notify network devices (synchronize new routing information to relevant network devices); 4) Trigger routing protocol updates (prompt each device in the network to update its routing table and adjust routing paths accordingly); 5) Verify routing propagation (ensure the integrity and correctness of the new routing configuration); 6) Packet forwarding test (ensure that network devices correctly forward packets according to the new routing information)

[0132] 4. Stop the announcement of the Spirent prefix and the corresponding operation: respond to the tester's operation and maintain the normal operation and connectivity of the network.

[0133] 1) Routing table update (update the local routing table and delete the routing information related to these prefixes. In this way, the system will no longer route traffic to the network devices associated with these prefixes); 2) Routing protocol notification (notify the relevant network devices to tell them to stop using these prefixes); 3) Routing information synchronization; 4) Verify routing updates (make sure they have been updated); 5) Traffic adjustment.

[0134] 5. Perform the following operations for the new automatic connection test: 1) update the routing table (ensure that the latest connection path and destination address routing information are included); 2) configure the service instance (the service instances may need to be reconfigured inside the computer to ensure that they can correctly respond to new connection requests and process traffic); 3) adjust the data plane (ensure that data packets can flow correctly between network slices along the new connection path and reach the target service instance); 4) start the connection test (the system detects the network connection status to ensure that the communication between network slices is normal); 5) performance monitoring;

[0135] 3) Equipment recovery test: This part verifies the continuity of network slice services. The team manually restarted all DCSGs. Once the equipment is back online, the service status is checked by measuring the service recovery time.

[0136] How to check the service status by measuring the service recovery time: 1) Device restart and service recovery (start all DCSGs so that related services can resume operation after the device is back online); 2) Monitor service status (monitor the service's operating status, response time, and the service's ability to handle requests, etc.); 3) Measure service recovery time (start from the time the device is back online until the service is fully restored to normal operation. This time period is usually used to evaluate service reliability and business continuity); 4) Record recovery time; 5) Status check (including checking whether the service has been started, whether the response time is normal, and whether the service can handle traffic normally); 6) Result analysis

[0137] 1) Measuring service recovery time can help the test team evaluate the continuity of network slicing services. Shorter service recovery time usually means shorter service interruption and higher continuity; 2) By checking the service recovery time, the team can promptly detect any service interruption or delay, so as to take necessary measures to ensure the reliability and stability of network slicing services.

[0138] Embodiment 2

[0139] Please refer to Figure 4 , is a structural schematic diagram of a network slice isolation device provided by an embodiment of the present invention, the device comprising: a Yang data model construction module, a network slice creation module and a network slice isolation module;

[0140] The Yang data model construction module is used to obtain preset endpoint information, customer information and a service level agreement for slice requests, and construct a corresponding Yang data model according to the endpoint information, customer information and the service level agreement for slice requests; wherein the endpoint information is the communication end point of the network slice to be created; the customer information is the terminal for the customer to request the configuration of the network slice; the service level agreement includes: performance requirements, resource isolation level, optimization criteria and node link characteristics of the network slice to be created;

[0141] The network slice creation module is used to receive a network slice request from a user, and create a plurality of isolated network slices according to the network slice request and the model information of the Yang data model; wherein the network slice request includes: the service type, performance index and isolation requirement required for the network slice to be created; the network slice includes: soft isolated network slice and hard isolated network slice;

[0142] The network slice isolation module is used to generate corresponding L3VPN services for each network slice according to the created network slices, map the L3VPN services to the corresponding network slices, and create connectivity services in the current transmission network to enable communication between the endpoints of each network slice, thereby completing the isolation of the network slices.

[0143] Preferably, according to the created network slices, a corresponding L3VPN service is generated for each network slice, the L3VPN service is mapped to the corresponding network slice, and a connectivity service is created in the current transmission network to enable communication between the endpoints of each network slice and complete the isolation of the network slices, including: according to the created network slices, a corresponding L3VPN service is generated for each network slice, the L3VPN service is mapped to the corresponding network slice, and the connectivity between the network slices is verified; when the connectivity between the network slices is verified, a connectivity service is created in the current transmission network to enable communication between the endpoints of the network slices, and the service continuity between the network slices is verified. When the service continuity between the network slices is verified, the isolation of the network slices is completed.

[0144] Preferably, generating a corresponding L3VPN service for each network slice according to the created network slice, and mapping the L3VPN service to the corresponding network slice, includes: generating corresponding L3VPN parameters according to the network slice request, and generating corresponding L3VPN services for each network slice according to the L3VPN parameters and the created network slice; allocating resources for each L3VPN service and creating a corresponding VRF instance, associating each VRF instance with the corresponding network slice, and mapping the L3VPN service to the corresponding network slice; wherein the resources include: bandwidth and virtual routers.

[0145] Preferably, the creation of a connectivity service in the current transmission network to enable communication between endpoints of each network slice includes: determining the communication requirements between endpoints of each network slice based on the network slice request; creating a connectivity service in the current transmission network based on the communication requirements and a preset API interface, and calculating an optimal transmission path, allocating resources between endpoints of each network slice based on the optimal transmission path, and establishing a physical connection between endpoints to enable communication between endpoints of each network slice.

[0146] It should be noted that the device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the accompanying drawings of the device embodiments provided by the present invention, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines. A person of ordinary skill in the art may understand and implement it without paying any creative effort.

[0147] Those skilled in the art can clearly understand that, for the sake of convenience and brevity, the specific working process of the device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0148] Embodiment 3

[0149] Accordingly, an embodiment of the present invention provides an electronic device, comprising a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor implements the network slice isolation method described in the above-mentioned embodiment of the invention when executing the computer program.

[0150] The electronic device may be a computing device such as a desktop computer, a notebook, a palm computer, a cloud server, etc. The device may include, but is not limited to, a processor and a memory.

[0151] The processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of the device, and various interfaces and lines are used to connect various parts of the entire device.

[0152] Embodiment 4

[0153] Accordingly, an embodiment of the present invention provides a storage medium, which includes a stored computer program, wherein when the computer program is running, the device where the storage medium is located is controlled to execute the network slice isolation method described in the above-mentioned embodiment of the invention.

[0154] The memory can be used to store the computer program, and the processor realizes various functions of the device by running or executing the computer program stored in the memory and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application required for a function, etc.; the data storage area can store data created according to the use of the mobile phone, etc. In addition, the memory can include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (FlashCard), at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0155] The storage medium is a computer-readable storage medium, and the computer program is stored in the computer-readable storage medium. When the computer program is executed by the processor, the steps of each method embodiment described above can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0156] The above is a preferred embodiment of the present invention. It should be pointed out that a person skilled in the art can make several improvements and modifications without departing from the principle of the present invention. These improvements and modifications are also considered to be within the scope of protection of the present invention.

Claims

1. A network slice isolation method, characterized in that: include: Obtain preset endpoint information, customer information, and a service level agreement for slice requests, and construct a corresponding Yang data model according to the endpoint information, customer information, and the service level agreement for slice requests; wherein the endpoint information is the communication end point of the network slice to be created; the customer information is the terminal for the customer to request configuration of the network slice; the service level agreement includes: performance requirements, resource isolation level, optimization criteria, and node link characteristics of the network slice to be created; Receive a network slice request from a user, and create a number of isolated network slices according to the network slice request and the model information of the Yang data model; wherein the network slice request includes: the service type, performance indicator and isolation requirement required for the network slice to be created; the network slice includes: soft isolated network slices and hard isolated network slices; According to the created network slices, a corresponding L3VPN service is generated for each network slice, the L3VPN service is mapped to the corresponding network slice, and a connectivity service is created in the current transmission network to enable communication between the endpoints of each network slice, thereby completing the isolation of the network slices.

2. The network slice isolation method according to claim 1, characterized in that: The generating a corresponding L3VPN service for each network slice according to the created network slice, mapping the L3VPN service to the corresponding network slice, and creating a connectivity service in the current transport network so that the endpoints of each network slice can communicate with each other and the isolation of the network slice is completed, including: Generate corresponding L3VPN services for each network slice according to the created network slices, map the L3VPN services to the corresponding network slices, and verify the connectivity between the network slices; When the connectivity verification between each network slice is passed, a connectivity service is created in the current transmission network to enable communication between the endpoints of each network slice, and the business continuity between each network slice is verified. When the business continuity verification between each network slice is passed, the isolation of the network slice is completed.

3. The network slice isolation method according to claim 1, characterized in that: The generating a corresponding L3VPN service for each network slice according to the created network slice, and mapping the L3VPN service to the corresponding network slice, includes: Generate corresponding L3VPN parameters according to the network slice request, and generate corresponding L3VPN services for each network slice according to the L3VPN parameters and the created network slice; Allocate resources for each L3VPN service and create a corresponding VRF instance, associate each VRF instance with a corresponding network slice, and map the L3VPN service to the corresponding network slice; wherein the resources include: bandwidth and virtual routers.

4. The network slice isolation method according to claim 1, characterized in that: The creating a connectivity service in the current transport network to enable communication between endpoints of each network slice includes: Determine the communication requirements between the network slice endpoints according to the network slice request; According to the communication requirements and the preset API interface, a connectivity service is created in the current transmission network, and the optimal transmission path is calculated. According to the optimal transmission path, resources are allocated between the endpoints of each network slice, and physical connections are established between the endpoints to enable communication between the endpoints of each network slice.

5. A network slice isolation device, characterized in that: include: Yang data model building module, network slice creation module, and network slice isolation module; The Yang data model construction module is used to obtain preset endpoint information, customer information and a service level agreement for slice requests, and construct a corresponding Yang data model according to the endpoint information, customer information and the service level agreement for slice requests; wherein the endpoint information is the communication end point of the network slice to be created; the customer information is the terminal for the customer to request the configuration of the network slice; the service level agreement includes: performance requirements, resource isolation level, optimization criteria and node link characteristics of the network slice to be created; The network slice creation module is used to receive a network slice request from a user, and create a plurality of isolated network slices according to the network slice request and the model information of the Yang data model; wherein the network slice request includes: the service type, performance index and isolation requirement required for the network slice to be created; the network slice includes: soft isolated network slice and hard isolated network slice; The network slice isolation module is used to generate corresponding L3VPN services for each network slice according to the created network slices, map the L3VPN services to the corresponding network slices, and create connectivity services in the current transmission network to enable communication between the endpoints of each network slice, thereby completing the isolation of the network slices.

6. The network slice isolation device according to claim 5, characterized in that: The generating a corresponding L3VPN service for each network slice according to the created network slice, mapping the L3VPN service to the corresponding network slice, and creating a connectivity service in the current transport network so that the endpoints of each network slice can communicate with each other and the isolation of the network slice is completed, including: Generate corresponding L3VPN services for each network slice according to the created network slices, map the L3VPN services to the corresponding network slices, and verify the connectivity between the network slices; When the connectivity verification between each network slice is passed, a connectivity service is created in the current transmission network to enable communication between the endpoints of each network slice, and the business continuity between each network slice is verified. When the business continuity verification between each network slice is passed, the isolation of the network slice is completed.

7. The network slice isolation device according to claim 5, characterized in that: The generating a corresponding L3VPN service for each network slice according to the created network slice, and mapping the L3VPN service to the corresponding network slice, includes: Generate corresponding L3VPN parameters according to the network slice request, and generate corresponding L3VPN services for each network slice according to the L3VPN parameters and the created network slice; Allocate resources for each L3VPN service and create a corresponding VRF instance, associate each VRF instance with a corresponding network slice, and map the L3VPN service to the corresponding network slice; wherein the resources include: bandwidth and virtual routers.

8. The network slice isolation device according to claim 5, characterized in that: The creating a connectivity service in the current transport network to enable communication between endpoints of each network slice includes: Determine the communication requirements between the network slice endpoints according to the network slice request; According to the communication requirements and the preset API interface, a connectivity service is created in the current transmission network, and the optimal transmission path is calculated. According to the optimal transmission path, resources are allocated between the endpoints of each network slice, and physical connections are established between the endpoints to enable communication between the endpoints of each network slice.

9. An electronic device, characterized in that: It includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, and when the processor executes the computer program, it implements the network slice isolation method as described in any one of claims 1 to 4.

10. A storage medium, characterized in that: The storage medium includes a stored computer program, wherein, when the computer program is running, the device where the storage medium is located is controlled to execute the network slice isolation method as described in any one of claims 1 to 4.

Images