Network slice management method, network management system, and storage medium

Abstract

The present application provides a network slice management method, a network management system, and a storage medium. The network slice management method comprises: receiving network slice configuration data from a network element (S110); on the basis of an IGP process identifier of a target network slice configured by a user, screening, from the network slice configuration data, requirement data for deploying the target network slice (S120); and deploying the target network slice on the basis of the requirement data (S130).

Description

Network slicing management methods, network management systems, and storage media

[0001] Cross-references to related applications

[0002] This application is based on and claims priority to Chinese Patent Application No. 202411534900.4, filed on October 30, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a network slicing management method, a network management system, and a storage medium. Background Technology

[0004] Network slicing is a virtualization technique that creates "one physical network and multiple logical networks," which can meet the application needs of diverse business scenarios. For example, network slicing can provide customized network services on demand for autonomous driving and Ultra Reliable Low Latency Communication (RLLC) applications.

[0005] In related technologies, network slice data is typically configured via command-line interfaces on network elements within a transmission network. Users have management needs for creating, modifying, and deleting network slices. To facilitate this management, it's necessary to deploy network slices within the network management system used to manage network elements. However, currently, deploying network slices in the network management system mainly relies on manually specifying each link to add a slice, which is cumbersome and prone to errors. Summary of the Invention

[0006] This application provides a network slice management method, a network management system, and a storage medium.

[0007] In a first aspect, embodiments of this application provide a network slice management method, comprising: receiving network slice configuration data from a network element; filtering out deployment requirement data for the target network slice from the network slice configuration data based on the IGP process identifier of the target network slice configured by the user; and deploying the target network slice according to the requirement data.

[0008] Secondly, embodiments of this application also provide a network management system, which includes a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for implementing communication between the processor and the memory, wherein when the computer program is executed by the processor, it implements the steps of any of the network slice management methods provided in this specification.

[0009] Thirdly, embodiments of this application also provide a storage medium for computer-readable storage, wherein the storage medium stores one or more programs that can be executed by one or more processors to implement the steps of any of the network slice management methods provided in this application specification. Attached Figure Description

[0010] Figure 1 is a schematic diagram of the implementation environment of the network slice management method provided in the embodiments of this application;

[0011] Figure 2 is a schematic diagram of the architecture of the network management system provided in an embodiment of this application;

[0012] Figure 3 is a flowchart of a network slice management method provided in an embodiment of this application;

[0013] Figure 4 is a flowchart of the sub-steps of step S120 in Figure 3;

[0014] Figure 5 is a flowchart of the sub-steps of step S121 in Figure 4;

[0015] Figure 6 is a flowchart of the sub-steps of step S1212 in Figure 5;

[0016] Figure 7 is a flowchart of the sub-steps of step S122 in Figure 4;

[0017] Figure 8 is a schematic diagram of the visual configuration interface provided in an embodiment of this application;

[0018] Figure 9 is a flowchart illustrating a network slice management method provided in an embodiment of this application;

[0019] Figure 10 is a schematic diagram of the structure of a network management system provided in an embodiment of this application. Detailed Implementation

[0020] To make the objectives, technical methods, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0021] It should be noted that although the flowchart shows a logical order, in some cases, the steps shown or described may be performed in a different order than that shown in the flowchart. In the description of the specification, claims, and the foregoing drawings, "multiple" means two or more; "greater than," "less than," and "exceeding" are understood to exclude the stated number; "above," "below," and "within" are understood to include the stated number. The use of terms such as "first" and "second" is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly specifying the number of indicated technical features or their sequential relationship.

[0022] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, the simultaneous existence of A and B, or the existence of B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c can represent: the existence of a alone, the existence of b alone, the existence of c alone, the simultaneous existence of a and b, the simultaneous existence of a and c, the simultaneous existence of b and c, or the simultaneous existence of a, b, and c, where a, b, and c can be single or multiple.

[0023] With the development of network services, the number of network service scenarios is increasing. Different network service scenarios may have huge differences in their requirements for network services in terms of mobility, bandwidth, latency, reliability, security, operation and billing. For example, enhanced mobile broadband (eMBB) service scenarios such as 4K / 8K mobile video services require ultra-high bandwidth and ultra-high speed mobility, while ultra-reliable low-latency communication (uRLLC) service scenarios such as autonomous driving and remote control applications require ultra-low latency (<1ms) and high reliability. The requirements for network capabilities of each service scenario are very uneven.

[0024] Network slicing is an on-demand networking approach that allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Each network slice is logically isolated from the radio access network to the bearer network and then to the core network. Different network slices have different characteristics, enabling flexible allocation of network resources and flexible combination of network capabilities, providing on-demand customized network services for various business scenarios to adapt to a wide variety of business applications.

[0025] The following situations may exist in current online services:

[0026] Scenario 1: In the transmission network, the slice-related data of the network element device is configured through the command line of the network element device, but the slice object is not deployed in the network management system. In this case, it is inconvenient for users to manage from the perspective of network slice, and it is inconvenient for users to view the global information of the network slice, such as network slice alarms, services on the network slice, etc. The creation, deletion, modification and query of resources within the slice cannot be operated in a graphical user interface, which is inconvenient for users to operate and maintain.

[0027] Scenario 2: Due to upgrades, failures, or other reasons, the slice object data in the network management system is lost. It is desirable to recover the slice object data in the network management system from the network data of the physical network. In this case, it is necessary to manually select links one by one to add them to the slice. The manual operation is cumbersome and inefficient. When the slice scale is large, it is easy to make mistakes.

[0028] Scenario 3: Some configurations of slices affecting network elements in the network were modified through command line or other means, resulting in inconsistencies between the slice information in the network management system and the actual network. It is desired to correct the slice data based on the actual network. In this case, users need to manually compare and find the inconsistent data, and then manually select links to add to the slice, which is difficult to operate.

[0029] The main objective of this application is to provide a network slice management method, a network management system, and a storage medium, aiming to solve the technical problems of cumbersome and error-prone operation in deploying network slices in the network management system in related technologies. This application creates an Interior Gateway Protocol (IGP) process and establishes a correspondence between the IGP process and network slices. Different network slices correspond to different IGP processes. The slice configuration data of network elements is associated with the corresponding IGP process, enabling the network management system to automatically discover slices in the transmission network based on the IGP process, and then receive network slice configuration data from the network elements involved in the IGP process. The network management system filters the deployment requirement data of the target network slice from the network slice configuration data according to the IGP process identifier of the target network slice configured by the user, and deploys the target network slice according to the requirement data. In this way, by using the IGP process identifier of the target network slice as a basis, the required data for deploying the target network slice can be quickly and accurately filtered from the network slice configuration data of the network element. This enables the target network slice to be deployed in the network management system in a timely manner based on the required data, improving the convenience, efficiency and accuracy of deploying network slices in the network management system. This allows the network management system to correctly manage and schedule network slices, while also facilitating users to manage network slices in the transport network and ensuring the quality of service of the network slices.

[0030] Please refer to Figure 1, which is a schematic diagram of the implementation environment of the network slice management method provided in this application embodiment. As shown in Figure 1, the implementation environment of this application embodiment includes a network management system and a transmission network. The network management system is used to manage the transmission network, which includes multiple network elements, such as network element 1 to network element 7 shown in Figure 1. Links for transmission services are formed between the multiple network elements. By flexibly combining the links, link resources that meet the needs of different slice services can be formed.

[0031] It should be noted that Flexible Ethernet (FlexE) divides the bandwidth of each physical interface into multiple fixed-size slots, each carrying a certain amount of bandwidth (e.g., 5Gbps). These slots can be used by different FlexE clients, thus enabling fine-grained control over bandwidth. Utilizing these characteristics of FlexE, multiple logical network slices can be virtualized on the same physical network. Each slice can have its own bandwidth, latency, and quality of service requirements, thereby meeting the needs of different services.

[0032] Please refer to Figure 2, which is a schematic diagram of the architecture of the network management system provided in the embodiment of this application. As shown in Figure 2, the network management system includes a network management server, a network management database, and a network management interface.

[0033] The network management server can communicate with the network element and receive the slice configuration data uploaded by the network element. In one embodiment, both the network management server and the network element can be equipped with a Network Configuration Protocol (NETCONF) interface, and the network management server and the network element can communicate and connect through the NETCONF interface.

[0034] The network management database is used to store network slice configuration data. After receiving the slice configuration data uploaded by the network element, the network management server sends the slice configuration data to the network management database for storage.

[0035] The network management interface provides a visual configuration interface. Users (such as network administrators) can log in to the network management interface through a client, access the visual configuration interface from the main page, and configure the IGP process identifier. This IGP process identifier serves as the basis for the network management system to automatically discover network slices. The client can take various forms, including but not limited to user equipment (UE), terminals, and terminal equipment. The client sends the user's operations in the visual configuration interface to the network management server, enabling the network management server to obtain the IGP process identifier information of the target network slice based on the user's configuration operations. Based on the target network slice's IGP process identifier, the server filters the network slice configuration data uploaded by network elements to select the deployment requirements for the target network slice, and then deploys the target network slice according to the requirements.

[0036] The network management interface also provides an auto-discovery interface, where network slice information discovered by the network management system is displayed.

[0037] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0038] Please refer to Figure 3, which is a flowchart of a network slice management method provided in an embodiment of this application. The network slice management method can be applied to a network management system, including but not limited to steps S110 to S130.

[0039] Step S110: Receive network slice configuration data from the network element.

[0040] It should be noted that, in this embodiment of the application, network slicing is first configured on the network element through the command line of the network element to form network slice configuration data. The network slice configuration data is associated with the IGP process so that the network slice configuration data of the network element can be uploaded to the network management system by the IGP process.

[0041] It should be noted that the network slices and IGP processes in this application embodiment have a one-to-one correspondence. By associating the IP address prefix and link resources corresponding to the slice with the IGP process, the IP address prefix is ​​only reachable in a single IGP process. This enables traffic with different prefixes addressing the same node to follow different topologies and paths, thus meeting the requirements for topology and link resource isolation between network slices.

[0042] In one implementation, the network slice configuration data may include at least one of the following:

[0043] Network element identifier (ID) is used to uniquely identify network elements in the transmission network;

[0044] The IGP process identifier is used to uniquely identify the IGP process. Specifically, it can be the instance number of the IGP process. In this embodiment, the IGP process and the network slice have a corresponding relationship.

[0045] The FlexE Client identifier defines the concepts of Client and Group. A FlexE Group consists of one or more physical interfaces (PHYs). The FlexE Client represents the client's Ethernet flow information, which is mapped to the PHY. Its rate may not be equal to the PHY rate. The FlexE Client Ethernet flow information can be mapped to the FlexE Group or demapped from the FlexE Group through time slot configuration.

[0046] Layer 3 interface information includes the identifier of the Layer 3 interface. The Layer 3 interface is the interface that supports sending and receiving data packets for Layer 2 and Layer 3 services. It is bound to the port of the network element or the FlexE Client and has a corresponding relationship with the FlexE Client.

[0047] The IP address prefix can specifically be the prefix of the IPv4 / IPv6 address of a network element.

[0048] In one implementation, network slice configuration data is used to indicate at least one of the following correspondences: the correspondence between network elements (network element IP address prefix information) and IGP processes, the correspondence between Layer 3 interfaces under a network element and IGP processes, and the correspondence between Layer 3 interfaces and FlexE Clients. Based on the above correspondence information, the network management system can determine the correspondence between network slices and network elements, Layer 3 interfaces, or FlexE Clients.

[0049] It should be noted that the correspondence between the Layer 3 interface and the IGP process, and / or the correspondence between the Layer 3 interface and the FlexE Client, can also be reported to the network management system through other channels between the network element and the network management system, such as through Border Gateway Protocol-Link State (BGP-LS).

[0050] As one embodiment, the IGP process can specifically be an Intermediate System to Intermediate System (ISIS) process. The IGP ISIS process is associated with the network slice configuration information of network elements. By discovering the IGP ISIS process, the network management system can obtain the network slice configuration information of network elements. Of course, besides the IGP ISIS process, other types of IGP processes can also be used to associate the network slice configuration information of network elements. This application embodiment does not impose excessive restrictions on the specific type of IGP process.

[0051] It should be noted that the network management system can receive network slice configuration data of all network elements in the transmission network, and organize and obtain the network slice configuration data of all network elements involved in the network slice according to the IGP process identifier corresponding to the network slice.

[0052] Step S120: Based on the IGP process identifier of the target network slice configured by the user, filter out the requirement data for deploying the target network slice from the network slice configuration data.

[0053] It should be noted that users can configure the IGP process identifier of the target network slice through the network management interface (visual configuration interface) of the network management system. This IGP process identifier is used to provide a basis for the network management system to automatically discover the target network slice. After receiving the IGP process identifier configured by the user through the network management interface, the network management system filters out the requirement data for deploying the target network slice from the network slice configuration data from the network elements.

[0054] It should be noted that users can configure the IGP process identifiers of multiple target network slices at once in the network management interface. The network management system can discover multiple target network slices in parallel and filter the required data for deploying each target network slice from the network slice configuration data from the network elements.

[0055] Step S130: Deploy the target network slice according to the requirement data.

[0056] After the network management system selects the target network slice requirement data from the network slice configuration data from the network elements, it deploys the target network slice according to the requirement data, including: creating the target network slice in the network management system, or updating the target network slice in the network management system.

[0057] In this embodiment, the network management system receives network slice configuration data from network elements and IGP process identifiers of one or more target network slices configured by the user. Based on the IGP process identifiers of the target network slices configured by the user, the network management system filters out the deployment requirement data for the target network slices from the network slice configuration data. Next, the network management system deploys the target network slices based on the requirement data. In this way, by using the IGP process identifiers of the target network slices as a basis, the deployment requirement data for the target network slices can be quickly and accurately filtered from the network slice configuration data of the network elements. This allows for timely deployment of target network slices in the network management system based on the requirement data, improving the convenience, efficiency, and accuracy of network slice deployment in the network management system. This enables the network management system to correctly manage and schedule network slices, ensuring the quality of service of the network slices.

[0058] It should be noted that, in this embodiment of the application, the user first configures the network slice configuration data in the transport network via the command line of the network element. The network slice configuration data on the network element is configured in a way that is associated with the IGP process, so that the network management system can automatically discover slices based on the IGP process. The rules for deploying slices in the transport network and the rules for the network management system to automatically discover slices need to be consistent.

[0059] In one embodiment, step S120 can be implemented by steps S121 to S122 as shown in FIG4:

[0060] Step S121: Based on the IGP process identifier, filter out the target links of the target network slice from the network slice configuration data;

[0061] Step S122: Determine the required data based on the target link.

[0062] It should be noted that network slicing consists of virtual links (Vlinks), which map to actual resource links. For FlexE slices, the actual resource mapped by the Vlink is a FlexE Channel link. A FlexE Channel combines the characteristics of FlexE sub-pipes and physical layer time slot cross-connection, enabling the construction of end-to-end rigid FlexE channels across network elements on the transport network. Intermediate nodes do not need to parse service packets, forming strict physical layer service isolation. The endpoints at both ends of the FlexEChannel (referred to as endpoint A and endpoint Z, respectively) correspond to the FlexE Clients of the network elements. The network management system can discover FlexE Channels in the transport network through end-to-end (E2E) service detection.

[0063] In one embodiment, when the network management system executes step S121, it first filters out target network slice configuration data that matches the IGP process identifier of the target network slice (such as the instance number of the IGP ISIS process) from the network slice configuration data, based on the IGP process identifier of the target network slice specified by the user. This target network slice configuration data includes all network elements involved in the target network slice and the Layer 3 interface information of each network element. Based on the FlexE Client of the service layer interface corresponding to the Layer 3 interface involved in the target network slice, the FlexE Client corresponding to the target network slice can be determined. Based on the correspondence between the FlexE Channel and the FlexE Client of the network element, the FlexE Channel corresponding to the target slice is determined, and the FlexE Channel is used as the target link corresponding to the target slice. Based on the target link, the required data for deploying the target network slice is determined.

[0064] It should be noted that different network slices correspond to different IGP process identifiers, Layer 3 interfaces, and FlexE Clients.

[0065] As one implementation, the network management system automatically discovers all FlexE Channels in the transport network via E2E. It iterates through each FlexE Channel, determining the Layer 3 interfaces corresponding to both ends of the FlexE Channel. If the Layer 3 interfaces at both ends of the FlexE Channel are within the range of Layer 3 interfaces corresponding to the target network slice, it indicates that the FlexE Channel belongs to the physical resource mapped by the target network slice. Then, based on the correspondence between the FlexE Channel and Vlinks, the Vlink corresponding to the network slice is obtained, and this Vlink can be used as the deployment requirement data for the network slice. If the Layer 3 interfaces at both ends of the FlexE Channel are not within the range of Layer 3 interfaces corresponding to the target network slice, it indicates that the FlexE Channel does not belong to the physical resource mapped by the target network slice.

[0066] In one embodiment, the network slice configuration data includes first slice configuration data related to network elements and second slice configuration data related to links. Step S121 can be implemented through steps S1211 to S1212 as shown in FIG5:

[0067] Step S1211: Filter out the network elements configured with IGP process identifiers from the first slice configuration data, and use the filtered network elements as target network elements;

[0068] Step S1212: Based on the target network element, filter out the target link from the second slice configuration data.

[0069] In one embodiment, the first slice configuration data is used to indicate the network element information corresponding to the IGP process identifier. When the network management system executes step S1211, it can determine all network elements with target network slices configured with the IGP process identifier based on the first slice configuration data.

[0070] The second slice configuration data is used to indicate the link-related information corresponding to the network element. When the network management system executes step S1212, it can select the target link corresponding to the target network slice from the candidate links corresponding to the target network element. The selection criteria can be that both the A endpoint and the Z endpoint of the target link belong to the target network element selected in step S1211.

[0071] In one embodiment, step S1212 can be implemented by steps S1212a to S1212b as shown in FIG6:

[0072] Step S1212a: Extract the FlexEClient, a flexible Ethernet client for the target network element, from the first slice configuration data.

[0073] Step S1212b: Based on FlexEClient, filter out the target link from the second slice configuration data.

[0074] In one embodiment, the network management system can determine the Layer 3 interface on the target network element corresponding to the IGP process identifier of the target network slice based on the correspondence between the IGP process identifier, network element and Layer 3 interface, and then determine the corresponding FlexEClient based on the Layer 3 interface. Based on the determined FlexEClient, multiple candidate links (candidate FlexE Channels) can be obtained, and then the target link (target FlexE Channel) corresponding to the target network slice can be selected from the candidate links.

[0075] In one embodiment, for step S1212b, links configured with FlexEClient can be filtered from the second slice configuration data, and the filtered links can be used as target links.

[0076] In one implementation, the target Layer 3 interface corresponding to the IGP process identifier of the target network slice on the target network element can be determined first. Then, the corresponding target FlexEClient can be determined according to the target Layer 3 interface. Based on the target FlexE Client, the FlexE Channel with the endpoints of the two ends as the target FlexE Client can be selected from the candidate FlexE Channels as the target link.

[0077] In one embodiment, step S122 can be implemented by steps S1221, S1222a, and S1222b as shown in FIG7:

[0078] Step S1221: Determine the category of the target network slice based on the target link;

[0079] Step S1222a: If the target network slice is a newly created slice, generate new virtual link (Vlink) data based on the target link, and use the new Vlink data as the requirement data.

[0080] Step S1222b: If the target network slice is of the slice type to be updated, update the Vlink data of the target network slice according to the target link, and use the updated Vlink data as the required data.

[0081] In one embodiment, when performing step S1221, it can be first determined whether the target link is configured with a slice ID; if the target link is not configured with a slice ID, the target network slice is determined to be a newly created slice; if the target link is configured with a slice ID, the target network slice is determined to be a slice to be updated.

[0082] As one embodiment, a FlexE Channel information table is set up in the network management system. This table records the ID of the FlexE Channel, the FlexEClient on the A-side, the FlexEClient on the Z-side, and the corresponding slice ID discovered by the network management system through E2E services. If the slice ID corresponding to the FlexE Channel is empty, it indicates that the slice corresponding to the FlexE Channel is a newly created slice. For a newly created slice, the Vkink data for creating the new slice is created based on the FlexE Channel, and the slice ID of the new slice is written into the FlexE Channel information table.

[0083] As one embodiment, a Vlink information table is set up in the network management system. This network slice index table records the Vkink ID, physical resource ID, and slice ID corresponding to the network slice, where the physical resource ID is the FlexE Channel ID. For newly created slices that are only configured on network elements but not deployed in the network management system, when the network management system automatically discovers the newly created slice based on the IGP process identifier, it determines the physical resource FlexE Channel corresponding to the newly created slice, then determines the Vlink with the FlexE Channel as the physical resource, generates the Vlink ID corresponding to the Vlink, and writes the FlexE Channel ID, Vkink ID, and slice ID corresponding to the newly created slice into the Vlink information table. For slices that have been deployed in the network management system and are awaiting updates, when the network management system automatically discovers the slice to be updated based on the IGP process identifier, it determines the physical resource FlexE Channel corresponding to the slice to be updated, and can find the corresponding Vkink ID and slice ID in the Vlink information table based on the FlexE Channel ID. The Vkink data corresponding to the slice to be updated is updated based on the bandwidth information of the FlexE Channel. The Vkink ID can be used to index the Vkink data.

[0084] It should be noted that the Vkink data of the newly created slice or the updated Vkink data of the slice to be updated can be stored in the network management database.

[0085] In one embodiment, before step S120, the following steps may be included: obtaining the slice name of the target network slice configured by the user in the visual configuration interface; and executing the IGP process configuration function in the visual configuration interface according to the slice name to obtain the IGP process identifier.

[0086] Understandably, users can configure the slice name of the target network slice in the visual configuration interface provided by the network management system. The network management system determines the corresponding IGP process based on the slice name configured by the user and displays the identifier of the IGP process in the visual configuration interface.

[0087] It should be noted that users can specify multiple slice names in the visual configuration interface. Each slice name corresponds to a target network slice, and each target network slice has a different IGP process identifier. The network management system initiates an automatic slice discovery process based on the IGP process identifier corresponding to the target network slice configured by the user. After discovering the slice, it performs creation or update operations on the slice.

[0088] It should be noted that this application embodiment uses slice data on network element devices in the transmission network as the basis. By determining the criteria for automatic slice discovery, and using the IGP multi-process in transmission network technology as the basis for automatic slice discovery, it supports manually specifying the IGP process for a slice in the network management system. Network data in the network is uploaded to the network management system, which analyzes the data and automatically discovers new slices or updates existing slices. This application embodiment supports the simultaneous and parallel discovery of multiple slices. This application embodiment allows users to easily, efficiently, and correctly create slices in the network management system, facilitating the management of network slices in the transmission network.

[0089] The network management system automatically discovers newly created or pending network slices. Users can easily deploy slices within the system, avoiding tedious manual operations and improving the efficiency and accuracy of slice activation. After deploying network slices, users can conveniently manage them from a network slice perspective, viewing overall information such as alarms and services running on the slices. A visual user interface facilitates the creation, deletion, modification, and querying of slice resources, simplifying network slice operation and maintenance.

[0090] It should be noted that, in this embodiment of the application, for automatically discovered new slices, after the slice and its corresponding Vlink are created, the slice and Vlink data are stored in the database and a slice creation notification is issued. For automatically discovered and updated existing slices, after the automatic discovery of the slice is completed, the Vlink data is stored in the database and a Vlink add, delete, or modify notification is issued.

[0091] The following examples illustrate in detail the network slice management method provided in the embodiments of this application.

[0092] Assume that the transport network is configured with FlexE slice 1 and FlexE slice 2. Slice 1 has a slice ID of 1 and IGP ISIS process numbers of 100 and 101. Slice 2 has a slice ID of 2 and IGP ISIS process numbers of 200 and 201.

[0093] It should be noted that FlexE slices correspond to IGP ISIS multiple processes. For example, the IGP ISIS process for the access ring is 101, and the IGP ISIS process for the aggregation ring is 100. There is a one-to-one correspondence between slices and IGP processes.

[0094] Users can specify the target network slices that the network management system needs to discover through the visual configuration interface shown in Figure 8. Specifically, users can select or create a new slice name in the visual configuration interface. For slices already existing in the network management system, the visual configuration interface automatically displays the IGP process identifier corresponding to that slice name. For example, if the user specifies slice 1, the visual configuration interface will automatically display the IGP process identifier corresponding to FlexE slice 1.

[0095] It should be noted that users can specify multiple target network slices that need to be discovered by the network management system through the visual configuration interface shown in Figure 8. Specifically, more target network slices can be added by using the "Add Slice" button on the interface.

[0096] After clicking the "Start Discovery" button in the visual configuration interface shown in Figure 8, the user submits the slice name and IGP process identifier corresponding to the specified target network slice to the network management system.

[0097] The network management system receives network slice configuration data uploaded by network elements in the transmission network. Based on the IGP process identifier corresponding to the target network slice specified by the user, it filters the relevant data of the target network slice from the network slice configuration data. The relevant data of the target network slice includes the network slice configuration data of all network elements involved in the target network slice. Assuming the target network slice specified by the user is slice 1, and the network elements involved in slice 1 include network element 1 and network element 2, the network slice configuration data uploaded by network element 1 can be seen in Table 1 below, and the network slice configuration data uploaded by network element 2 can be seen in Table 2 below.

[0098] Table 1 Network Slicing Configuration Data for Network Element 1

[0099] Table 2 Network Slicing Configuration Data for Network Element 2

[0100] The network management system automatically discovers FlexE Channel links across the entire network based on E2E services in the transport network. Assuming FlexE Channel1 and FlexE Channel2 are discovered, the information for FlexE Channel1 is shown in Table 3 below, and the information for FlexE Channel2 is shown in Table 4 below.

[0101] Table 3 Information on FlexE Channel 1

[0102] Table 4 Information on FlexE Channel 2

[0103] The network management system determines multiple candidate FlexE Channels based on all Layer 3 interfaces and FlexE Clients corresponding to Layer 3 interfaces in slice 1. Then, it selects the target FlexE Channel corresponding to the target network slice from the candidate links. The determination of the target FlexE Channel is based on the fact that the FlexE Clients at both ends of the FlexE Channel correspond to the ISIS process number of slice 1. In this example, based on the fact that the ISIS process number corresponding to slice 1 is "100", and the fact that the ISIS process number "100" corresponds to the FlexE Client 1 corresponding to Layer 3 interface 1 of network element 1 and the FlexE Client 1 corresponding to Layer 3 interface 1 of network element 2, FlexE Channel 1 is determined to be the target link corresponding to slice 1.

[0104] After determining the FlexE Channel 1 corresponding to slice 1, it is confirmed whether FlexE Channel 1 has a corresponding slice ID value. In one embodiment, it can be determined whether the network management system records the slice ID value corresponding to FlexE Channel 1. If the recorded slice ID value corresponding to FlexE Channel 1 is empty, it indicates that the category of slice 1 is a newly created slice. The Vlink with FlexE Channel 1 as the physical resource is determined, as shown in Table 5 below, which is the Vlink information table corresponding to slice 1.

[0105] Table 5 shows the Vlink information corresponding to slice 1.

[0106] If the slice ID value corresponding to FlexE Channel1 recorded by the network management system is not empty, it is necessary to further verify whether the recorded slice ID value corresponding to FlexE Channel1 is consistent with the slice ID of slice 1 automatically discovered this time. If they are inconsistent, the data of this FlexE Channel1 is abnormal data, and the abnormal data is written to the operation log. It should be noted that the slice ID of slice 1 can be determined according to a preset mapping rule, such as based on the name of slice 1.

[0107] If the slice ID value corresponding to the recorded FlexE Channel1 is consistent with the slice ID of the automatically discovered slice 1, it is necessary to further confirm whether slice 1 is a FlexE slice. If it is not a FlexE slice, automatic slice discovery by IGP ISIS process is not supported, and it is considered abnormal data. The abnormal data will be written to the operation log.

[0108] If slice 1 is confirmed to be a FlexE slice, it means that slice 1 is a slice to be updated. Determine the Vlink ID corresponding to slice 1 based on the ID of FlexE Channel 1, and update the Vlink data corresponding to the Vlink ID based on the bandwidth and other information of FlexE Channel 1.

[0109] It should be noted that if the network management system finds that the Vlink corresponding to the slice has not been processed after the slice is created or updated, then the Vlink can be regarded as a redundant Vlink. The real resource corresponding to the Vlink is no longer on the slice. The Vlink needs to be deleted and the association between the Vlink and the real resource needs to be removed, but the real resource FlexEChannel corresponding to the Vlink should not be deleted.

[0110] Please refer to Figure 9, which is a flowchart illustrating a network slice management method provided in an embodiment of this application. As shown in Figure 9, the method includes the following steps:

[0111] S1: Receive the target slice ID specified by the user and the target IGP identifier corresponding to the target slice ID;

[0112] S2: Based on the target IGP identifier, select multiple target network elements from the network elements of the entire network, determine the Layer 3 interface corresponding to the target IGP identifier in each target network element, and obtain the FlexE Client corresponding to the service layer interface of the Layer 3 interface.

[0113] S3: Traverse the entire network's FlexE Channel;

[0114] S4: Confirm whether the FlexE Channel being traversed is the target FlexE Channel. The confirmation is based on the correspondence between the FlexE Clients at both ends of the target FlexE Channel and the target IGP identifier. If yes, jump to S5; otherwise, return to step S3 to traverse the next FlexE Channel.

[0115] S5: Confirm whether the target FlexE Channel has a corresponding slice ID. If not, proceed to S6; if yes, proceed to S7.

[0116] S6: Create the Vlink corresponding to the target slice ID based on the target FlexE Channel, and then jump to S10;

[0117] S7: Determine whether the slice ID corresponding to the target FlexE Channel is consistent with the target slice ID. If not, return to step S3 to traverse the next FlexE Channel. If yes, jump to S8.

[0118] S8: Confirm whether the slice corresponding to the target slice ID is a FlexE slice. If not, return to step S3 to traverse the next FlexE Channel. If yes, jump to S9.

[0119] S9: Update the Vlink corresponding to the target slice ID according to the target FlexE Channel, and jump to S10;

[0120] S10: Confirm whether the traversal is complete. If not, return to step S3 to traverse the next FlexE Channel. If yes, jump to step S11.

[0121] S11: Complete the creation or update of the Vlink corresponding to the target slice ID, and delete the unprocessed Vlink corresponding to the slice corresponding to the target slice ID.

[0122] This application embodiment also provides a network management system, as shown in FIG10, the network management system 1400 includes:

[0123] One or more processors 1410;

[0124] The memory 1420 stores one or more programs that, when executed by one or more processors 1410, enable the one or more processors 1410 to implement the network slice management method provided in any embodiment of this application.

[0125] Memory 1420, as a non-transitory network system, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory 1420 may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 1420 may include remotely located memories 1420 relative to processor 1410, which can be connected to processor 1410 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0126] The memory 1420 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1420 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1420 and is called and executed by the processor 1410.

[0127] The processor 1410 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0128] In some embodiments, the network management system further includes:

[0129] Input / output interfaces are used to implement information input and output;

[0130] The communication interface is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0131] The bus transmits information between various components of the device (such as processor 1410, memory 1420, input / output interfaces, and communication interfaces);

[0132] The processor 1410, memory 1420, input / output interface, and communication interface can communicate with each other within the device via a bus.

[0133] An embodiment of this application also provides a storage medium for computer-readable storage, which stores one or more programs that can be executed by one or more processors to implement the network slice management method provided in any embodiment of this application.

[0134] An embodiment of this application also provides a computer program product, including a computer program or computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the computer device to perform a network slicing management method that implements any embodiment of this application.

[0135] This application provides a network slice management method, a network management system, and a storage medium. The network slice management method receives network slice configuration data from network elements; filters the deployment requirement data of the target network slice from the network slice configuration data based on the IGP process identifier of the target network slice configured by the user; and deploys the target network slice according to the requirement data. Thus, by using the IGP process identifier of the target network slice as a basis, the deployment requirement data of the target network slice can be quickly and accurately filtered from the network slice configuration data of the network elements. This enables timely deployment of the target network slice in the network management system based on the requirement data, improving the convenience, efficiency, and accuracy of network slice deployment in the network management system. This allows the network management system to correctly manage and schedule network slices, ensuring the quality of service of the network slices.

[0136] The system architecture and application scenarios described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. Those skilled in the art will understand that as system architectures evolve and new application scenarios emerge, the technical solutions provided in this application are also applicable to similar technical problems.

[0137] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0138] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0139] The above description, with reference to the accompanying drawings, illustrates some embodiments of this application, but does not limit the scope of this application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of this application shall be within the scope of this application.

Claims

1. A method for managing network slices, the method being applied to a network management system, comprising: Receive network slicing configuration data from network elements; Based on the Internal Gateway Protocol (IGP) process identifier of the target network slice configured by the user, the required data for deploying the target network slice is filtered from the network slice configuration data. Deploy the target network slice based on the stated requirements data.

2. The network slice management method according to claim 1, wherein, The step of filtering the required data for deploying the target network slice from the network slice configuration data based on the IGP process identifier of the target network slice configured by the user includes: Based on the IGP process identifier, the target link of the target network slice is selected from the network slice configuration data; The required data is determined based on the target link.

3. The network slice management method according to claim 2, wherein, The network slice configuration data includes first slice configuration data related to the network element and second slice configuration data related to the link. The step of filtering the target link of the target network slice from the network slice configuration data based on the IGP process identifier includes: The network elements configured with the IGP process identifier are selected from the first slice configuration data, and the selected network elements are used as target network elements. The target link is selected from the second slice configuration data based on the target network element.

4. The network slice management method according to claim 3, wherein, The step of filtering the target link from the second slice configuration data based on the target network element includes: Extract the FlexEClient, a flexible Ethernet client for the target network element, from the first slice configuration data; The target link is selected from the second slice configuration data based on the FlexEClient.

5. The network slice management method according to claim 4, wherein, The step of filtering the target link from the second slice configuration data according to the FlexEClient includes: The links configured with the FlexEClient are filtered out from the second slice configuration data, and the filtered links are used as target links.

6. The network slice management method according to claim 2, wherein, Determining the required data based on the target link includes: Based on the target link, determine the category of the target network slice; If the target network slice is a newly created slice, new virtual link (Vlink) data is generated based on the target link, and the new Vlink data is used as the demand data. If the target network slice is of the slice category to be updated, the Vlink data of the target network slice is updated according to the target link, and the updated Vlink data is used as the required data.

7. The network slice management method according to claim 6, wherein, Determining the category of the target network slice based on the target link includes: Determine whether the target link is configured with a slice ID; If the target link does not have the slice ID configured, the target network slice is determined to be a newly created slice; If the target link is configured with the slice ID, the target network slice is determined to be a slice to be updated.

8. The network slice management method according to claim 1, wherein, Before filtering the network slice configuration data to determine the deployment requirements for the target network slice based on the IGP process identifier of the target network slice configured by the user, the method further includes: Obtain the slice name of the target network slice configured by the user in the visual configuration interface; Based on the slice name, the IGP process configuration function is executed in the visual configuration interface to obtain the IGP process identifier.

9. A network management system, the network management system comprising a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for implementing connection communication between the processor and the memory, wherein the computer program, when executed by the processor, implements the steps of the network slice management method as described in any one of claims 1 to 8.

10. A storage medium for computer-readable storage, the storage medium storing one or more programs that can be executed by one or more processors to implement the steps of the network slice management method according to any one of claims 1 to 8.

Images