A network slice isolation method, device, apparatus and storage medium

Abstract

The application discloses a network slice isolation method and device, equipment and storage medium, the method comprises the following steps: a corresponding Yang data model is constructed; a network slice request of a user is received, and a plurality of isolated network slices are created according to the network slice request and model information of the Yang data model; the network slice comprises a soft isolated network slice and a hard network isolated slice; according to the created network slice, a corresponding L3VPN service is generated for each network slice, the L3VPN service is mapped into the corresponding network slice, and a connectivity service is created in the current transmission network, so that communication between the end points of each network slice is realized, and the isolation of the network slice is completed. Through the application, soft and hard isolation of the network slice can be realized.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a network slicing isolation method, apparatus, device, and storage medium. Background Technology

[0002] Network slicing refers to dividing a physical network into multiple virtual networks, each network slice being architected and optimized for a specific application / service. In this context, Next Generation Mobile Networks (NGMNs) define two main concepts: Service Instance (SI) is an end-user service or business service implemented within a network slice; Network Slice Instance (NSI) is a complete, instantiated logical network that meets the specific characteristics required by the Service Instance.

[0003] Therefore, network slicing involves sharing network infrastructure across different service instances to meet network-specific needs. Network slicing can vary depending on the network operator's implementation, resource management, network characteristics, or the communication layer of the toolkit used to implement it. Some examples of network characteristics required by service instances include ultra-low latency or ultra-reliability, but there is currently no detailed and technical explanation in the existing technology of how to isolate network slices. Summary of the Invention

[0004] This invention provides a network slice isolation method, apparatus, device, 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 existing technology.

[0005] To address the aforementioned technical problems, embodiments of the present invention provide a network slicing isolation method, comprising:

[0006] Obtain preset endpoint information, client information, and service level protocol (SLP) for slice requests. Construct the corresponding Yang data model based on the endpoint information, client information, and SLP for slice requests. The endpoint information refers to the communication endpoint of the network slice to be created. The client information refers to the terminal of the client requesting to configure the network slice. The SLP includes the performance requirements, resource isolation level, optimization criteria, and node link characteristics of the network slice to be created.

[0007] The system receives network slice requests from users and creates several isolated network slices based on the network slice requests and the model information of the Yang data model. The network slice requests include the service type, performance indicators, and isolation requirements required for the network slices to be created. The network slices include soft-isolated network slices and hard-isolated network slices.

[0008] Based on 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 transport network to enable communication between the endpoints of each network slice and complete the isolation of the network slices.

[0009] As a preferred embodiment, the step of generating a corresponding L3VPN service for each network slice based on the created network slice, mapping the L3VPN service to the corresponding network slice, and creating a connectivity service in the current transport network to enable communication between the endpoints of each network slice and complete the isolation of the network slice includes:

[0010] Based on the created network slices, generate corresponding L3VPN services for each network slice, map the L3VPN services to the corresponding network slices, and verify the connectivity between the network slices.

[0011] When the connectivity verification between network slices passes, a connectivity service is created in the current transport network to enable communication between the endpoints of each network slice and to verify the service continuity between each network slice. Once the service continuity verification between each network slice passes, the isolation of the network slices is completed.

[0012] As a preferred embodiment, the step of generating corresponding L3VPN services for each network slice based on the created network slices, and mapping the L3VPN services to the corresponding network slices, includes:

[0013] Based on the network slice request, generate the corresponding L3VPN parameters, and based on the L3VPN parameters and the created network slice, generate the corresponding L3VPN service for each 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 embodiment, the creation of a connectivity service in the current transport network to enable communication between endpoints of each network slice includes:

[0016] The communication requirements between each network slice endpoint are determined based on the network slice request.

[0017] Based on 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. Based on 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 embodiments, 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, client information, and service level protocol (SLP) of slice requests, and construct the corresponding Yang data model based on the endpoint information, client information, and SLP of slice requests; wherein, the endpoint information is the communication endpoint of the network slice to be created; the client information is the terminal of the client requesting to configure the network slice; the SLP includes: the 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 network slice requests from users and create several isolated network slices based on the network slice requests and the model information of the Yang data model; wherein, the network slice request includes: the service type, performance indicators and isolation requirements required for the network slice to be created; the network slice includes: soft isolated network slices and hard isolated network slices;

[0021] The network slice isolation module is used to generate corresponding L3VPN services for each network slice based on the created network slices, map the L3VPN services to the corresponding network slices, and create connectivity services in the current transport network so that the endpoints of each network slice can communicate and complete the isolation of the network slices.

[0022] As a preferred embodiment, the step of generating a corresponding L3VPN service for each network slice based on the created network slice, mapping the L3VPN service to the corresponding network slice, and creating a connectivity service in the current transport network to enable communication between the endpoints of each network slice and complete the isolation of the network slice includes:

[0023] Based on the created network slices, generate corresponding L3VPN services for each network slice, map the L3VPN services to the corresponding network slices, and verify the connectivity between the network slices.

[0024] When the connectivity verification between network slices passes, a connectivity service is created in the current transport network to enable communication between the endpoints of each network slice and to verify the service continuity between each network slice. Once the service continuity verification between each network slice passes, the isolation of the network slices is completed.

[0025] As a preferred embodiment, the step of generating corresponding L3VPN services for each network slice based on the created network slices, and mapping the L3VPN services to the corresponding network slices, includes:

[0026] Based on the network slice request, generate the corresponding L3VPN parameters, and based on the L3VPN parameters and the created network slice, generate the corresponding L3VPN service for each 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 embodiment, the creation of a connectivity service in the current transport network to enable communication between endpoints of each network slice includes:

[0029] The communication requirements between each network slice endpoint are determined based on the network slice request.

[0030] Based on 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. Based on 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, the device including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor executes the computer program to implement the network slicing isolation method described in the above embodiments of the invention.

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

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

[0034] This invention provides a network slice isolation method. It obtains preset endpoint information, client information, and the service level protocol (SLP) of the slice request. Based on the endpoint information, client information, and SLP of the slice request, a corresponding Yang data model is constructed. The endpoint information refers to the communication endpoint of the network slice to be created. The client information refers to the terminal requesting network slice configuration. The SLP includes performance requirements, resource isolation level, optimization criteria, and node link characteristics of the network slice to be created. The method receives user network slice requests and creates several isolated network slices based on the network slice requests and the model information of the Yang data model. The network slice request includes the service type, performance indicators, and isolation requirements required for the network slice to be created. The network slices include soft-isolated network slices and hard-isolated network slices. Based on 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 transport network to enable communication between the endpoints of each network slice, thus completing the isolation of the network slices. This invention achieves both soft and hard isolation of network slices. Attached Figure Description

[0035] Figure 1 This is a schematic flowchart of a network slicing isolation method provided in an embodiment of the present invention;

[0036] Figure 2 This is a flowchart illustrating the process of implementing network slicing isolation;

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

[0038] Figure 4 This is a schematic diagram of a network slicing isolation device provided in an embodiment of the present invention. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0040] Example 1

[0041] Please refer to Figure 1 The following is a flowchart illustrating a network slicing isolation method according to an embodiment of the present invention, including the following specific steps:

[0042] S1. Obtain preset endpoint information, client information, and service level protocol (SLP) for slice requests. Construct the corresponding Yang data model based on the endpoint information, client information, and SLP for slice requests. The endpoint information is the communication endpoint of the network slice to be created. The client information is the terminal of the client requesting to configure the network slice. The SLP includes: the performance requirements, resource isolation level, optimization criteria, and node link characteristics of the network slice to be created.

[0043] This invention provides a network slicing isolation method, please refer to... Figure 2 The flowchart for implementing network slicing isolation includes the following steps:

[0044] I. Introduction to Software, Hardware, and 5G Network Slicing:

[0045] 1. Network slicing:

[0046] The concept of network slicing provides a framework widely applicable across various industries. One of the main drivers behind network slicing is the realization of fifth-generation (5G) networks. This necessitates integrating multiple services with varying performance requirements—such as high throughput, low latency, high reliability, high mobility, and high security—into a single physical network infrastructure, providing a customized logical network for each service. Network slicing is a key technology for achieving these 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 over a network. Soft slicing means sharing the physical infrastructure but creating logical segments between customers. Traditional IP Network Resource Management (L3VPNs) is an example of soft slicing implementation in MPLS networks because a VPN can be thought of as a series of tunnels connecting customer sites, each potentially with different Quality of Service (QoS) handling, and all traffic going in and out of each site is internal to the customer. In VPN services, the provider configures routing policies across the entire network to ensure that each customer's traffic is logically separated from the shared physical infrastructure. In this sense, MPLS-level network slicing can be implemented as follows:

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

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

[0051] Each physical router can host multiple VRFs and multiple VSIs (as well as their attached logical interfaces), effectively dividing them into multiple routing and switching environments that can be assigned to different tenants / customers / services.

[0052] 2) Hard network slicing:

[0053] While overlay MPLS tunnels may offer significant advantages, they also present several drawbacks. Overlay tunnels established through data encapsulation cannot see or control the underlying physical network. As more tunnels are deployed on shared physical infrastructure, network congestion inevitably becomes a concern. Therefore, VRFs, VSIs, or Optical Data Units (ODus) cannot be directly managed by their respective tenants, as they belong to the same management domain represented by physical devices and require operation by the network administrator. Due to the large number of tunnels and services in complex networks, QoS and traffic engineering policy management become critical tasks for ensuring the correct SLA is delivered to customers.

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

[0055] Decomposed routers are an example of hard slicing. The data plane runs inside the physical device, while the control plane runs on a remote cloud or server outside the device. This decouples the physical device from 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 managed independently of other virtual routers running on the same device. Therefore, the management of virtual routers is decoupled, meaning individual virtual routers can be assigned to different tenants, each of whom can directly manage the virtual routers without intervention from the operator owning the physical network. IP transport-level network slicing can be accomplished by grouping multiple virtual routers running on a shared physical network infrastructure into a shared virtual infrastructure under separate management domains. Virtual routers under the same management domain are called hard network slices, and 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 meet these needs and determine how to allocate network resources, service providers must integrate technologies such as Software-Defined Networking (SDN), Network Functions 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): This encompasses 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 function is to act as a gateway for user traffic entering and leaving 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 connecting the RAN and 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 functions such as QoS management, synchronization, and protocol stacks such as IP / MPLS or segment routing.

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

[0062] 5G specifies two network slicing mechanisms. The first, based on QoS technology, dynamically allocates available network resources to different categories of traffic; this is known as soft network slicing. The second utilizes 5G's software-based, cloud-based architecture and component de-aggregation, achieving slicing through 5G component virtualization and replication. This second method is known as hard network slicing.

[0063] II. Proposed System Architecture:

[0064] The iFUSION architecture is an architecture defined by Telefonica to enhance network automation and programmability in service provider environments. Please refer to [link / reference]. Figure 3This 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 optics) located at the bottom, and a software-defined transport network controller (SDTN controller) handling multi-layer and multi-domain transport network resources. The domain controllers communicate directly with network elements, and the SDTN controller communicates directly with the OSS / BSS system. In addition to function block definitions, iFUSION also includes the use of: (1) a standard interface based on RESTCONF / YANG for communication between control components and NETCONF / YANG to configure network elements; (2) the latest version of the YANG data model based on Standards Development Organizations (SDOs): IETF, ONF, and OpenConfig.

[0065] Figure 3 This demonstrates the iFUSION architecture's network scheme, including the components and their relationships. The following defines each structural pillar in the architecture, 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 functions: It is the main entry point from the Operations Support System (OSS) / Business Support System (BSS) to the network. It is responsible for coordinating / providing services across multiple domains and layers. It has a topology view of the multi-layer / multi-domain network. The SDTN controller can segment requirements according to technical needs. In this process, the SDTN controller can add / allocate logical resources for network use during service implementation. The SDTN controller has two RESTCONF interfaces: one for handling requirements from 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 within the underlying transport infrastructure, managing and controlling the status of associated resources and topology. The NSC receives transport network slice requests from Operations Support Systems (OSS / BSS). The NSC runs an internal workflow for transport network slice lifecycle management and interacts with the underlying IP and optical domain controllers via a RESTCONF client. The Network Slice Controller provides the ability to create / modify / delete, monitor, and optimize network slices in multi-domain, multi-technology, and multi-vendor environments. It has two main functions:

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

[0071] Implementation: The NSC should use its SBI interface to make network slice requests to the domain controller via VPNs or various tunneling technologies (such as segment routing, MPLS, etc.) over a physical or logical connection.

[0072] 3) Network Domain Controller:

[0073] The SDN controller manages network elements (network domains). It has a standard southbound interface for communicating with network elements. The SDN controller relies on the Network Configuration Protocol (NETCONF) to interact with network elements using the underlying technology. The SDN controller also has a northbound interface that communicates with the SDTN controller or OSS / BSS system via RESTCONF.

[0074] 4) Yang model of network controller:

[0075] As previously mentioned, the three control elements—SDTN controller, network slice controller, and network domain controller—have standard SBI and NBI interfaces for communication between themselves and with the network or OSS / BSS system. The standard interface consists of a YANG data model that selects the protocol for transmitting data and defines how messages are formed. The YANG data model includes the service level protocol for endpoints, client information, and slice requests. In a sense, YANG modeling activities have gained significant relevance across standardization entities. By 2019, 283 YANG models had been correctly extracted from IETF drafts, 214 from the Broadband Forum, and 137 from 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 an architecture definition perspective, navigating the large number of available YANGs and selecting the appropriate data model package to define the interface for each functional block becomes a fundamental task.

[0076] III. 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 service delivered to a specific customer, and naturally, other network slices or services must not negatively affect the delivery of the requested transport network slice.

[0078] To provide this isolation and instantiate slices in the network, there are several implementation options, ranging from softer to hardest isolation levels, as follows:

[0079] No isolation means the slices are not separated. Logical isolation means the slices are logically separated, with only a certain degree of isolation implemented through QoS mechanisms. Service isolation means virtual resources and NFs are shared. Process isolation means the slice includes process and thread isolation. Virtual resource isolation means the slice has dedicated virtual resources. Network function isolation means network functions (NFs) are dedicated to a single network slice. Physical isolation means the slices are physically completely separated, for example, in different locations. Physical network isolation means the slice contains physically separate links.

[0080] Since isolation level is a crucial constraint to consider in network slicing implementation, the chosen network infrastructure and control elements will generate different function sets in the network slice controller. The following describes several possibilities from the perspective of mapping and implementation tasks in the network slice controller:

[0081] 1) The network slice controller is 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 client's view, the hierarchical SDN module must be able to:

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

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

[0085] 2) The network slice controller acts as a standalone controller:

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

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

[0088] 3) Domain controller-level network slice controller:

[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 NCS communicating directly with network elements. The SDTN controller should create a unified network view, including each transport domain and network slice. Mapping: The SDTN will handle client requests. Client requests can be sent using [draft-liu-tea-transport-networkslice-yang-01]. This draft allows topology mapping for slice requests. Implementation: Implementation can be accomplished by creating policies directly on network elements through the NCS controller's application service logic. The SDTN should handle shared resource management between domains.

[0090] 4) The network slice controller is part of the domain controller:

[0091] When the network slice controller is part of a domain controller, the OSS / BSS system handles slice requests and introduces a network abstraction layer. At the network layer, the NBI and SBI of the SDN controller will use the same device data model. Direct translation reduces the service logic implemented at the SDN controller level, grouping mapping and translation into single tasks. Mapping and implementation: Mapping and implementation can be accomplished by the domain controller applying service logic to create policies directly on the network elements. The network slice controller receives all service requests and, for interaction with the transport domain, has two controllers: one IP and one optical.

[0092] IV. Steps to achieve isolation:

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

[0094] In this context, an endpoint refers to the communication endpoint defined in the network slicing service, representing the interface of the user device, server, or router that actually transmits data in the network. In our design, endpoint information is mapped to specific VRF instances within a virtual router, allowing different network traffic to be handled independently through these VRFs. In fact, each virtual router can be configured with multiple VRFs. VRF is a virtualization technology that allows multiple virtual routing tables to be created on the same physical router. Traffic from different clients or services can be processed independently on the same device without interfering with each other. Client information includes: the device or application requesting configuration or status data, i.e., the identifier; configurable settings of the device or system, such as the IP address and subnet mask of the network router, which contain specific functional or business requirements; network device traffic and connection status, enabling monitoring of device performance, troubleshooting, or configuration optimization; for more detailed definitions, see: The Service Level Agreement for Slicing Requests includes: 1) Performance Requirements: Latency Tolerance: Defines the maximum acceptable latency for a network slice; Periodicity: Specifies the periodic requirements of the service, such as data transmission frequency; 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 objectives of the slice for 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 enhances the management of services and resources through the use of information models. These information models capture management entities defined in terms of attributes and supported operations. Therefore, a set of Yang data models has been defined to implement network slicing among control entities.

[0096] Specifically, how does the iFusion architecture enhance service and resource management? The iFusion architecture features a unified management platform, a comprehensive view (integrating different IP layers, different domains, etc.), and network slice management capabilities, which are specifically enhanced in the following ways: 1) Unified modeling language; 2) Object model (abstracting management entities into objects, which have attributes such as name and type, and support operations such as configuration and control); 3) Attribute and support operation definitions; 4) YANG data model for structured and standardized representation.

[0097] Specifically, how does a model capture the definition of a management entity? 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). By describing data structures, data integrity constraints, and data operations using YANG, YANG models are formed.

[0098] Model Structure: 1) Define the entities, attributes, and relationships required for network slicing; 2) Divide the data model into hierarchical structures and define the relationships between entities; 3) Define the syntax and semantics of the data model using Yang language, including elements such as modules, containers, lists, and leaves.

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

[0100] The model training process includes: 1) Collecting network slice requirements and constraints, including service type, resource requirements, QoS requirements, etc. 2) Designing the structure and attributes of the Yang data model based on these requirements to ensure accurate capture of network slice needs. 3) Writing the Yang model file using appropriate tools and an editor. 4) Verifying the correctness and completeness of the data model.

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

[0102] S2. Receive a user's network slice request, and create several isolated network slices based on the network slice request and the model information of the Yang data model; wherein, the network slice request includes: the service type, performance indicators, and isolation requirements required for the network slice to be created; the network slice includes: soft isolated network slices and hard isolated network slices;

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

[0104] In this process, the user issues a network slice request: the SDTN controller receives the user's network slice request and creates isolated network slices. That is, the user sends a network slice request to the SDTN controller, including the required service type, performance metrics, and isolation requirements.

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

[0106] Using the YANG data model: The YANG data model allows the controller to represent and manage the attributes and structure of network slices. The YANG model defines various attributes of network slices. The controller uses this model to interact with the IP domain controller, thereby enabling the creation of 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 maps to a specific network slice and has its own dedicated L3VPN service. The endpoints defined in the request are mapped to Virtual Routers and Forwarding Instances (VRFs), allowing each network slice to independently manage its traffic and resources.

[0108] In other words, through the SDTN controller, users can request multiple isolated network slices. The creation of each slice involves the configuration of the L3VPN service, ensuring that each slice has independent traffic management and resource allocation. Therefore, the YANG data model is used to ensure that all requests and configurations 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 transport network to enable communication between the endpoints of each network slice and complete the isolation of the network slices.

[0110] Preferably, the step of generating a corresponding L3VPN service for each network slice based on the created network slice, and mapping the L3VPN service to the corresponding network slice, includes: generating corresponding L3VPN parameters based on the network slice request, and generating a corresponding L3VPN service for each network slice based on 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 step of creating a connectivity service in the current transmission network to enable communication between the endpoints of each network slice includes: determining the communication requirements between the 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, calculating the optimal transmission path, allocating resources between the endpoints of each network slice based on the optimal transmission path, and establishing physical connections between the endpoints to enable communication between the endpoints of each network slice.

[0112] Preferably, the step of generating a corresponding L3VPN service for each network slice based on the created network slice, mapping the L3VPN service to the corresponding network slice, and creating a connectivity service in the current transport network to enable communication between the endpoints of each network slice and complete the isolation of the network slice includes: generating a corresponding L3VPN service for each network slice based on the created network slice, mapping the L3VPN service to the corresponding network slice, and verifying the connectivity between each network slice; when the connectivity verification between each network slice passes, creating a connectivity service in the current transport network to enable communication between the endpoints of each network slice, and verifying the service continuity between each network slice; after the service continuity verification between each network slice passes, the isolation of the network slice is completed.

[0113] 3. For L3VPN services, the endpoints defined in the slice request are mapped to Virtual Routers and Forwarders (VRFs), and an L3VPN service is created for each network slice. This ensures that each L3VPN service is mapped to a single network slice, achieving hardware and software isolation between multiple slices at the network layer.

[0114] To request the use of isolated network slices based on standards and model-driven approaches, the SDTN controller will receive network slice requests and translate them into specific per-domain requests, as follows:

[0115] (a) Creating an L3VPN Service: In this section, each network slice request requires the creation of 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 Virtual Router and Forwarder (VRF) instances on the virtual router. The Yang data model used by the SDTN to request L3VPN services from the IP domain controller is L3NM.

[0116] How to create an L3VPN service: L3VPN, or Layer 3 Virtual Private Network, is a network service that provides Layer 3 isolation and reachability within a service provider's network. It is an IP network resource management measure.

[0117] The following steps allow you to create a separate L3VPN service for each network slice request in the iFusion architecture. Creation steps: 1) Receive the network slice request; 2) Define L3VPN parameters; 3) Allocate resources (e.g., bandwidth, configure virtual routers); 4) Create a VRF instance (configure a separate VRF instance for each L3VPN service); 5) Configure routing policies; 6) Connect endpoints (map the endpoints in the slice request to the corresponding VRF instance); 7) Check the configuration; 8) Enable the L3VPN service; 9) Monitor and manage.

[0118] Specifically, L3VPN services are mapped to individual network slices by configuring an independent VRF instance for each L3VPN service. Each VRF instance is associated with a corresponding network slice, ensuring that each network slice has a corresponding L3VPN service. This ensures that every network slice request is mapped to a single L3VPN service, thus achieving a one-to-one correspondence between network slices and L3VPN services. The purpose is to achieve 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: Using T-API to create new connectivity services in the transport network, enabling L2-L1 communication between network slice endpoints.

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

[0122] The reasons why L2-L1 communication between network slice endpoints becomes possible are: 1) The created physical connection 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 have been created, which can help different network slices form independent communication channels and achieve isolation between slices.

[0123] 5. After creating isolated network slices, verify the IP connectivity between network slices to ensure that data packets are transmitted correctly.

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

[0125] 7. After passing IP connectivity and service continuity tests, the isolated network slice is successfully created and the system service status is normal, ensuring the reliability of service and data packet transmission and the continuity of services, thus realizing the isolation of 5G network hardware and software slices.

[0126] Adding and Destroying Prefixes: This section aims to verify IP connectivity between network slices. Spirent testers announced a set of 5k IP prefixes using previously created network slices. The testers then performed automated IP reachability tests and CLI route reassignment verification. Once route propagation was verified, the testing team stopped all Spirent prefix announcements and began new automated connectivity tests.

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

[0128] 1. Operations corresponding to adding 5k IP prefixes: In response to the user's request to add 5k IP prefixes, update the routing table: add these new IP prefixes to the routing table. 2) Update network configuration: Based on the new IP prefixes, update the network device configuration to ensure that data packets can be correctly routed to their destination.

[0129] 2. IP reachability test operations: Verify the connectivity of the newly added IP prefix to ensure that data packets can be transmitted correctly. 1) Test packet generation (including some target IP address and identification information); 2) Routing table lookup; 3) Data packet transmission; 4) Data packet reception; 5) Response data packet transmission (after the target device receives the packet, it processes it and generates a response data packet, which is then returned to the sending device along the reverse path); 6) Response data packet reception and analysis (analyze 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 reassignment verification operation: The system reassigns routes based on the newly added prefix to ensure that the routing information in the network is up-to-date.

[0131] 1) Verify route information updates (ensure new route information has been updated in network devices); 2) Update routing tables; 3) Notify network devices (synchronize new route information to relevant network devices); 4) Trigger routing protocol updates (cause each device in the network to update its routing table and adjust the routing path accordingly); 5) Verify route propagation (ensure the integrity and correctness of the new route configuration); 6) Perform packet forwarding tests (ensure network devices correctly forward packets according to the new route information).

[0132] 4. Actions corresponding to the announcement to stop the Spirent prefix: Respond to the actions of testers and maintain the normal operation and connectivity of the network.

[0133] 1) Routing table update (updates the local routing table, deleting routing information associated with these prefixes. This prevents the system from routing traffic to network devices associated with these prefixes); 2) Routing protocol notification (notifies relevant network devices to stop using these prefixes); 3) Routing information synchronization; 4) Verify route updates (ensure updates have been performed); 5) Traffic adjustment.

[0134] 5. Operations corresponding to the new automatic connection test: 1) Routing table update (ensuring that the routing information includes the latest connection path and destination address); 2) Service instance configuration (the computer may need to reconfigure service instances internally to ensure that they can correctly respond to new connection requests and process traffic); 3) Data plane adjustment (ensuring that data packets can correctly flow between network slices according to the new connection path and reach the target service instance); 4) Connection test initiation (the system detects network connectivity to ensure normal communication between network slices); 5) Performance monitoring;

[0135] 3) Device Recovery Testing: This part verifies the continuity of network slice services. The team manually restarted all DCSGs. Once the devices were back online, the service status was checked by measuring service recovery time.

[0136] Specifically, how to check service status by measuring service recovery time: 1) Device restart and service recovery (start all DCSGs so that relevant services begin to resume operation after the device is back online); 2) Monitor service status (monitor service operation status, response time, and service request processing capabilities, etc.); 3) Measure service recovery time (start timing from device back online until the service is fully restored to normal operation. This time period is usually used to assess service reliability and business continuity); 4) Record recovery time; 5) Status checks (including checking whether the service has started, whether the response time is normal, and whether the service can handle traffic normally); 6) Result analysis.

[0137] 1) Measuring service recovery time helps the testing team assess the continuity of network slicing services. Shorter service recovery times generally mean less service interruption and higher continuity; 2) By checking service recovery times, the team can promptly identify any service interruptions or delays, thereby taking necessary measures to ensure the reliability and stability of network slicing services.

[0138] Example 2

[0139] Please refer to Figure 4 This is a schematic diagram of a network slice isolation device provided in an embodiment of the present invention. The device includes: 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, client information, and service level protocol (SLP) of slice requests, and construct the corresponding Yang data model based on the endpoint information, client information, and SLP of slice requests; wherein, the endpoint information is the communication endpoint of the network slice to be created; the client information is the terminal of the client requesting to configure the network slice; the SLP includes: the 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 network slice requests from users and create several isolated network slices based on the network slice requests and the model information of the Yang data model; wherein, the network slice request includes: the service type, performance indicators and isolation requirements required for the network slice to be created; the network slice includes: soft isolated network slices and hard isolated network slices;

[0142] The network slice isolation module is used to generate corresponding L3VPN services for each network slice based on the created network slices, map the L3VPN services to the corresponding network slices, and create connectivity services in the current transport network so that the endpoints of each network slice can communicate and complete the isolation of the network slices.

[0143] Preferably, the step of generating a corresponding L3VPN service for each network slice based on the created network slice, mapping the L3VPN service to the corresponding network slice, and creating a connectivity service in the current transport network to enable communication between the endpoints of each network slice and complete the isolation of the network slice includes: generating a corresponding L3VPN service for each network slice based on the created network slice, mapping the L3VPN service to the corresponding network slice, and verifying the connectivity between each network slice; when the connectivity verification between each network slice passes, creating a connectivity service in the current transport network to enable communication between the endpoints of each network slice, and verifying the service continuity between each network slice; after the service continuity verification between each network slice passes, the isolation of the network slice is completed.

[0144] Preferably, the step of generating a corresponding L3VPN service for each network slice based on the created network slice, and mapping the L3VPN service to the corresponding network slice, includes: generating corresponding L3VPN parameters based on the network slice request, and generating a corresponding L3VPN service for each network slice based on 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 step of creating a connectivity service in the current transmission network to enable communication between the endpoints of each network slice includes: determining the communication requirements between the 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, calculating the optimal transmission path, allocating resources between the endpoints of each network slice based on the optimal transmission path, and establishing physical connections between the endpoints to enable communication between the endpoints of each network slice.

[0146] It should be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, in the accompanying drawings of the device embodiments provided by this invention, the connection relationships between modules indicate that they have communication connections, which can be specifically implemented as one or more communication buses or signal lines. Those skilled in the art can understand and implement this without any creative effort.

[0147] Those skilled in the art will clearly understand that, for convenience and simplicity, the specific working process of the device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0148] Example 3

[0149] Accordingly, embodiments of the present invention provide an electronic device, the device including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor executes the computer program to implement the network slicing isolation method described in the above embodiments of the invention.

[0150] The electronic device may be a desktop computer, laptop, handheld computer, or cloud server, etc. The device may include, but is not limited to, a processor and a memory.

[0151] The processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor. The processor is the control center of the device, connecting various parts of the device via various interfaces and lines.

[0152] Example 4

[0153] Accordingly, embodiments of the present invention provide a storage medium, the storage medium including a stored computer program, wherein, when the computer program is running, it controls the device where the storage medium is located to execute the network slicing isolation method described in the above embodiments of the invention.

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

[0155] The storage medium is a computer-readable storage medium, and the computer program is stored in the computer-readable storage medium. When executed by a processor, the computer program can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0156] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications are also considered to be within the scope of protection of the present invention.

Claims

1. A network slicing isolation method, characterized in that, include: Obtain preset endpoint information, client information, and service level protocol (SLP) for slice requests. Construct the corresponding Yang data model based on the endpoint information, client information, and SLP for slice requests. The endpoint information refers to the communication endpoint of the network slice to be created. The client information refers to the terminal of the client requesting to configure the network slice. The SLP includes the performance requirements, resource isolation level, optimization criteria, and node link characteristics of the network slice to be created. The system receives network slice requests from users and creates several isolated network slices based on the network slice requests and the model information of the Yang data model. The network slice requests include the service type, performance indicators, and isolation requirements required for the network slices to be created. The network slices include soft-isolated network slices and hard-isolated network slices. Based on 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 transport network to enable communication between the endpoints of each network slice and complete the isolation of the network slices.

2. The network slicing isolation method as described in claim 1, characterized in that, The step of generating corresponding L3VPN services for each network slice based on the created network slices, mapping the L3VPN services to the corresponding network slices, and creating connectivity services in the current transport network to enable communication between endpoints of each network slice and complete network slice isolation includes: Based on the created network slices, generate corresponding L3VPN services for each network slice, map the L3VPN services to the corresponding network slices, and verify the connectivity between the network slices. When the connectivity verification between network slices passes, a connectivity service is created in the current transport network to enable communication between the endpoints of each network slice and to verify the service continuity between each network slice. Once the service continuity verification between each network slice passes, the isolation of the network slices is completed.

3. The network slicing isolation method as described in claim 1, characterized in that, The step of generating corresponding L3VPN services for each network slice based on the created network slices, and mapping the L3VPN services to the corresponding network slices, includes: Based on the network slice request, generate the corresponding L3VPN parameters, and based on the L3VPN parameters and the created network slice, generate the corresponding L3VPN service for each 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 slicing isolation method as described in claim 1, characterized in that, The step of creating a connectivity service in the current transport network to enable communication between endpoints of various network slices includes: The communication requirements between each network slice endpoint are determined based on the network slice request. Based on 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. Based on 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 slicing 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, client information, and service level protocol (SLP) of slice requests, and construct the corresponding Yang data model based on the endpoint information, client information, and SLP of slice requests; wherein, the endpoint information is the communication endpoint of the network slice to be created; the client information is the terminal of the client requesting to configure the network slice; the SLP includes: the 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 network slice requests from users and create several isolated network slices based on the network slice requests and the model information of the Yang data model; wherein, the network slice request includes: the service type, performance indicators and isolation requirements required for the network slice to be created; the network slice includes: soft isolated network slices and hard isolated network slices; The network slice isolation module is used to generate corresponding L3VPN services for each network slice based on the created network slices, map the L3VPN services to the corresponding network slices, and create connectivity services in the current transport network so that the endpoints of each network slice can communicate and complete the isolation of the network slices.

6. The network slicing isolation device as described in claim 5, characterized in that, The step of generating corresponding L3VPN services for each network slice based on the created network slices, mapping the L3VPN services to the corresponding network slices, and creating connectivity services in the current transport network to enable communication between endpoints of each network slice and complete network slice isolation includes: Based on the created network slices, generate corresponding L3VPN services for each network slice, map the L3VPN services to the corresponding network slices, and verify the connectivity between the network slices. When the connectivity verification between network slices passes, a connectivity service is created in the current transport network to enable communication between the endpoints of each network slice and to verify the service continuity between each network slice. Once the service continuity verification between each network slice passes, the isolation of the network slices is completed.

7. The network slicing isolation device as described in claim 5, characterized in that, The step of generating corresponding L3VPN services for each network slice based on the created network slices, and mapping the L3VPN services to the corresponding network slices, includes: Based on the network slice request, generate the corresponding L3VPN parameters, and based on the L3VPN parameters and the created network slice, generate the corresponding L3VPN service for each 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 slicing isolation device as described in claim 5, characterized in that, The step of creating a connectivity service in the current transport network to enable communication between endpoints of various network slices includes: The communication requirements between each network slice endpoint are determined based on the network slice request. Based on 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. Based on 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, wherein the processor, when executing the computer program, implements the network slicing 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 executed, it controls the device where the storage medium is located to perform the network slicing isolation method as described in any one of claims 1 to 4.

Images