A SRv6 network slice configuration management method and system

Abstract

An SRv6 network slice configuration management method and system, relating to the field of communications, including: S1. The slice controller sends slice configuration data to the source node, the slice configuration data including Slice ID, slice bandwidth value and physical outbound interface information; S2. The source node encapsulates the Slice ID and slice bandwidth value into the service message through the slice identification extension header, and forwards it according to the slice sub-interface corresponding to the Slice ID; S3. The intermediate node forwards the service message and extracts the Slice ID and slice bandwidth value, adds the network node device ID and the physical outbound interface information to generate the slice information, and reports it to the slice controller; S4. The slice controller stores the previously received slice information to generate a configuration data summary table, analyzes the currently received slice information based on the configuration data summary table, and manages the slice configuration of the corresponding intermediate node. The present invention realizes automatic deployment of slices without manual operation, thereby improving management and maintenance efficiency.

Description

Technical Field

[0001] The present invention relates to the field of communications, and specifically to an SRv6 network slice configuration management method and system. Background Art

[0002] With the rapid development of 5G technology, 5G networks have been widely used in all walks of life. However, in 5G networks, different types of services in various vertical industries will have very different service requirements. There are huge differences in bandwidth, latency, reliability, security and mobility. Some industries have very stringent requirements on network transmission latency, jitter, security, etc., and cannot tolerate their services being affected by other services. In order to cope with the emerging differentiated business needs, network slicing technology came into being and became one of the key technologies of 5G.

[0003] SRv6 network slicing technology is to slice the SRv6 network into multiple logical networks with specific network functions, consisting of customized network topology and network resources on the same physical network, to meet the business function requirements of different network slice tenants, so that different network slice services can exclusively use the bandwidth of the logical network, thereby achieving secure isolation between services, ensuring service quality, and meeting differentiated business requirements. The SRv6 network slicing technology based on Slice ID introduces a globally unique Slice ID to identify network slices. Each Slice ID corresponds to a network slice. The Slice ID can identify the forwarding resource interface within the slice. In principle, the total bandwidth of the physical outbound interface on the network side is logically soft-sliced ​​into small-granularity logical sub-interfaces, and then a Slice ID and corresponding bandwidth value are assigned to each slice sub-interface. In the control plane, the SRv6 service path is calculated based on the Slice ID for service carrying. In the data plane, each forwarding node matches the slice resource interface forwarding service according to the Slice ID carried in the SRv6 HBH Header of the service message.

[0004] The SRv6 network slicing technology solution based on Slice ID requires configuring the same Slice ID and slice bandwidth value for the network-side egress of all nodes on the service path. The existing implementation method is to manually send slice configurations to each node, and the complete service path needs to be known in advance. Therefore, if there are many service flows that need to implement slicing functions, the manual operation method is very inconvenient and has low management and maintenance efficiency. Summary of the invention

[0005] In view of the defects existing in the prior art, the purpose of the present invention is to provide an SRv6 network slice configuration management method and system, which can realize automatic deployment of slices without manual operation and improve management and maintenance efficiency.

[0006] To achieve the above objectives, on the one hand, a SRv6 network slice configuration management method is adopted, comprising the steps of:

[0007] S1. The slice controller sends slice configuration data to the source node. The slice configuration data includes Slice ID, slice bandwidth value and physical outbound interface information.

[0008] S2. The source node encapsulates the Slice ID and the Slice bandwidth value into the service message through the Slice ID extension header, and forwards it according to the slice sub-interface corresponding to the Slice ID;

[0009] S3. The intermediate node forwards the service message; and extracts the Slice ID and the slice bandwidth value, plus the network node device ID and the physical outbound interface information to generate the slice information, and reports it to the slice controller;

[0010] S4. The slice controller stores the previously received slice information to generate a configuration data summary table, analyzes the currently received slice information based on the configuration data summary table, and manages the slice configuration of the corresponding intermediate node.

[0011] Preferably, in S2, the source node generates a corresponding slice forwarding table entry based on the Slice ID, the slice bandwidth value and the physical outbound interface information, and determines the slice sub-interface corresponding to the slice service;

[0012] The slice identification extension header is SRv6 HBH. The source node encapsulates the Slice ID and slice bandwidth value of the slice service into the SRv6 HBH, and then encapsulates the SRv6 HBH into the service message.

[0013] Preferably, S4 includes:

[0014] If the corresponding intermediate node has never sent down any slice configuration, the controller will send the acquired slice configuration data to the network node device.

[0015] Preferably, S4 includes:

[0016] If the corresponding intermediate node has issued a slice configuration, compare the newly obtained slice information with the issued slice information;

[0017] If the two slice IDs are the same, the physical outbound interfaces are the same, but the slice bandwidth values ​​are different, the slice bandwidth value is compared with the slice bandwidth value configured on the source node. If they are consistent, the updated slice configuration is sent to the network node device to update the slice bandwidth value; if they are inconsistent, an alarm message is generated;

[0018] If the two slice IDs are the same, the physical outbound interfaces are the same, and the slice bandwidth values ​​are the same, the current storage time of this entry in the configuration summary table is refreshed, and no other processing is performed.

[0019] Preferably, S4 includes:

[0020] If the corresponding intermediate node has issued a slice configuration, compare the newly obtained slice information with the issued slice information;

[0021] If the two Slice IDs are different but the physical output interfaces are the same, check whether the slice resources of the physical output interface exceed the limit. If not, send a new slice configuration to the network node device. If so, generate an alarm.

[0022] Preferably, S4 includes: if the controller finds that the current storage time of an entry in the configuration data table exceeds the default aging time, then the slice deletion configuration is sent down to the corresponding intermediate node.

[0023] Preferably, 1588 clock synchronization is implemented between the slice controller and all network nodes. In S3, the intermediate node periodically reports the slice information to the slice controller. The slice information is reported in the form of a message and carries 1588 timestamp data.

[0024] On the other hand, an SRv6 network slice configuration management system is provided, including a slice controller and a plurality of network node devices, the network node devices serving as source nodes or intermediate nodes; a bidirectional communication channel is established between the slice controller and all network node devices;

[0025] The slice controller is used to send slice configuration data to the source node. The slice configuration data includes Slice ID, slice bandwidth value and physical outbound interface information. It is also used to store previously received slice information to generate a configuration data summary table, analyze the currently received slice information based on the configuration data summary table, and manage the slice configuration of the corresponding intermediate node.

[0026] The source node encapsulates the Slice ID and the Slice bandwidth value into the service message through the Slice ID extension header, and forwards it according to the slice sub-interface corresponding to the Slice ID.

[0027] The intermediate node is used to forward the service message; it is also used to extract the Slice ID and slice bandwidth value, add the network node device ID and the physical output interface to generate slice information, and report it to the slice controller.

[0028] Preferably, the slice controller comprises:

[0029] A receiving and storing module, used to store the received slice information by entry and generate a configuration data summary table;

[0030] The control processing module is used to assign a unique Slice ID to the slice service; it is also used to obtain the network node device ID, Slice ID, slice bandwidth value and physical outbound interface information from the receiving storage module, and analyze it according to the configuration data summary table;

[0031] The configuration module manages the slice configuration of the corresponding intermediate node according to the analysis results of the control processing module, including issuing slice configuration, updating slice configuration, deleting slice configuration, or generating alarms.

[0032] Preferably, the network node device includes a configuration receiving module, a slice processing module and a reporting module;

[0033] The receiving module is configured to, when the network node device acts as a source node, generate a corresponding slice forwarding table entry based on the slice ID, the slice bandwidth value and the physical outbound interface information to determine the corresponding slice sub-interface;

[0034] The slice processing module is used to generate a slice identification extension header when the network node device acts as a source node, encapsulate the Slice ID and slice bandwidth value corresponding to the slice service, and encapsulate the slice identification extension header into the service message, and forward it from the corresponding slice sub-interface; when the network node device acts as an intermediate node, it is used to identify the slice identification extension header, keep the slice identification extension header unchanged and forward the service message; it is also used to extract the Slice ID and slice bandwidth value, add the network node device ID and the physical output interface to generate the slice information;

[0035] The reporting module is used to report the slice information to the slice controller when the network node device acts as an intermediate node.

[0036] Preferably, the network node device also serves as a host node, in which case the slice processing module is used to identify the slice identifier extension header, decapsulate it, restore the service message to the original message service, and forward it.

[0037] Preferably, the slice controller also includes a display module for viewing the network topology of the specified slice service and the current allocation of slice resources.

[0038] Preferably, a two-way communication channel is established between the slice controller and each network node device, the slice controller senses different network node devices through the node device ID, and deploys 1588 clock synchronization in the entire network;

[0039] The intermediate node periodically reports slice information to the slice controller and carries 1588 timestamp data.

[0040] One of the above technical solutions has the following beneficial effects:

[0041] The slice configuration of all network nodes is centrally managed by the slice controller. The configuration personnel only need to send the slice configuration to the source node through the slice controller. When the slice service is forwarded from the slice sub-interface through the source node, the slice identification extension header is encapsulated to carry the slice configuration data corresponding to this slice service. The intermediate node only needs to identify the slice identification extension header and report the slice information to the slice controller. The slice controller analyzes the currently received slice information and manages the slice configuration of the corresponding intermediate node. Automatic deployment of slices can be achieved without manual operation, thereby improving management and maintenance efficiency.

[0042] The controller stores the slice information received previously to generate a configuration data table, performs retrieval and conflict checks in the configuration data table, and generates processing results, that is, issuing slice configurations, updating slice configurations, deleting slice configurations, or generating alarms, to achieve further automatic management of slice configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 This is a flow chart of the SRv6 network slice configuration management method according to an embodiment of the present invention;

[0044] Figure 2 Schematic diagram of the SRv6 network slice message encapsulation format according to an embodiment of the present invention;

[0045] Figure 3 This is a schematic diagram of an SRv6 network slice configuration management system according to an embodiment of the present invention;

[0046] Figure 4 Schematic diagram of the internal modules of the slice controller in an embodiment of the present invention;

[0047] Figure 5 It is a schematic diagram of functional modules in a network node device in an embodiment of the present invention. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0049] like Figure 1 As shown, an embodiment of an SRv6 network slice configuration management method is provided, comprising the following steps:

[0050] S1. The slice controller sends slice configuration data to the source node. The slice configuration data includes Slice ID, slice bandwidth value and physical outbound interface information.

[0051] S2. The source node encapsulates the Slice ID and slice bandwidth value into the service message through the slice identification extension header, and forwards it according to the slice sub-interface corresponding to the Slice ID.

[0052] S3. The intermediate node forwards the service message; extracts the Slice ID and the slice bandwidth value, adds the network node device ID and the physical outbound interface information to generate the slice information, and reports it to the slice controller.

[0053] S4. The slice controller stores the previously received slice information to generate a configuration data summary table, analyzes the currently received slice information based on the configuration data summary table, and manages the slice configuration of the corresponding intermediate node.

[0054] In the above step S1, the slice controller can provide a user operation interface to receive the network node device ID, slice bandwidth value Bandwidth and physical output interface information of the source node input by the user. The controller allocates a unique Slice ID for this slice service in the entire network. The Slice ID, slice bandwidth value and physical output interface information are used as slice configuration data and are sent to the source node.

[0055] In the above step S2, after the source node receives the slice configuration data sent by the slice controller, the source node generates a corresponding slice forwarding table entry based on the Slice ID, slice bandwidth value and physical outbound interface information, and the slice forwarding table entry is used to determine the slice sub-interface corresponding to this slice service. When a slice service with network slicing requirements passes through the source node, the source node generates a slice identification extension header, encapsulates the Slice ID and slice bandwidth value corresponding to this slice service into the slice identification extension header, and then encapsulates the slice identification extension header into the service message, and then finds the corresponding slice sub-interface according to the Slice ID to forward the service message.

[0056] Preferably, the slice identifier extension header is SRv6 HBH (Hop-by-Hop Options Header, hop-by-hop options extension header), which is sent by the source node according to Figure 2 The format is generated, where Option Type = 10 is the slice identifier.

[0057] In the above step S3, when the slice service with the slice identifier extension header passes through the intermediate node of the network, the intermediate node recognizes the slice identifier in the slice service message, keeps the slice identifier extension header in the slice service message unchanged and forwards it. It also extracts the Slice ID and slice bandwidth value in the slice identifier extension header, adds the network node device ID and the physical outbound interface information to generate the slice information, and reports it to the slice controller.

[0058] Preferably, 1588 is deployed in the whole network, 1588 clock synchronization is implemented between the slice controller and all network nodes, and the intermediate node periodically reports the slice information to the slice controller. The slice information is reported in the form of a message (i.e., a slice information message) and carries 1588 timestamp data. In addition to reporting slice information in real time, the intermediate node can also report slice information periodically to avoid the controller receiving duplicate data. The intermediate node can implement duplicate filtering of data, reduce the amount of data received by the controller, and improve the intelligence of configuration management.

[0059] In the above step S4, the slice controller receives the slice information reported by each network node, stores it by entry, and generates a configuration data summary table. Then, the configuration data summary table is analyzed, including retrieval and conflict checking, to generate processing results, manage the slice configuration of the corresponding intermediate node, including issuing slice configuration, updating slice configuration, deleting slice configuration, or generating alarms.

[0060] Based on the above step S4, embodiments of different processing results are provided.

[0061] If the slice controller searches the configuration data table and finds that the corresponding intermediate node has never sent down any slice configuration, the controller will send the acquired slice configuration data to the network node device serving as the intermediate node.

[0062] If the slice controller searches the configuration data table and the corresponding intermediate node has issued a slice configuration, a conflict check is performed to compare the newly obtained slice information with the issued slice information. The comparison process is as follows:

[0063] If the two slice IDs are the same, the physical outbound interfaces are the same, but the slice bandwidth values ​​are different, the slice bandwidth value is compared with the slice bandwidth value configured on the source node. If they are consistent, the updated slice configuration is sent to the network node device to update the slice bandwidth value; if they are inconsistent, it may be an illegal message or attack message on the network, and an alarm should be generated at this time. When the user needs to adjust the slice bandwidth of a specific service, the source node is manually updated through the controller, and the update is automatic.

[0064] If the two slice IDs are the same, the physical outbound interfaces are the same, and the slice bandwidth values ​​are the same, the current storage time of this entry in the configuration summary table is refreshed, and no other processing is performed.

[0065] If the Slice IDs of the two are different but the physical output interfaces are the same, check whether the slice resources of the physical output interface exceed the limit. If not, send a new slice configuration to the network node device of the intermediate node. If so, generate an alarm message.

[0066] If the controller finds that the current storage time of an entry in the configuration data master table exceeds the default aging time, it sends the slice deletion configuration to the network node device of the intermediate node.

[0067] When a slice service with a slice identifier extension header passes through a destination node, the destination node identifies the slice identifier, decapsulates the slice identifier extension header, restores the service message to the original message service, and forwards it.

[0068] like Figure 3 As shown, an SRv6 network slice configuration management system is provided, which can be used to implement the above management method. The management system includes a slice controller and multiple network node devices. After the system is initialized, a two-way communication channel is normally established between the slice controller and all network node devices in the entire network. The configuration channel ( Figure 3 The solid arrow in the middle) and the Telemetry reporting channel ( Figure 3 The slice controller senses different network node devices through the network node device ID, and can also deploy 1588 time synchronization in the whole network system to synchronize the 1588 time between each network node device, so that the service flow can be connected normally. The network node device can be used as a source node, an intermediate node, or a sink node.

[0069] In the management system, the slice controller provides a user operation interface. Figure 3 Data represents user data, receiving the network node device ID, slice bandwidth value and physical outbound interface information of the source node input by the user, and the slice controller is used to send slice configuration data ( Figure 3 The slice controller is also used to store previously received slice information and generate a configuration data summary table, analyze the currently received slice information based on the configuration data summary table, and manage the slice configuration of the corresponding intermediate node.

[0070] The source node identifies the extended header through the slice ( Figure 3 The Slice ID and the slice bandwidth value are encapsulated into the service message, and the message is forwarded according to the slice sub-interface corresponding to the Slice ID.

[0071] The intermediate node is used to forward service messages; it is also used to extract the Slice ID and slice bandwidth value, plus the network node device ID and physical outbound interface to generate slice information ( Figure 3 The data is represented by D in the figure) and reported to the slice controller in the form of a message.

[0072] like Figure 4 As shown, an internal module embodiment of a slice controller is provided. The slice controller includes a receiving storage module, a control processing module and a configuration module.

[0073] The receiving storage module is used to extract the slice information from the slice information message and store it by entry to generate a configuration data summary table.

[0074] The control processing module receives slice configuration data through the user operation interface, is used to assign a unique Slice ID to the slice service, and notifies the configuration module to send the slice configuration data of this slice service to the source node (such as a→b→c); it is also used to obtain the network node device ID, Slice ID, slice bandwidth value and physical output interface information from the receiving storage module, and analyze it according to the configuration data summary table (including retrieval and conflict check), and can also obtain 1588 timestamp data (such as d→e→b→c).

[0075] The configuration module manages the slice configuration of the corresponding intermediate node according to the analysis results of the control processing module, including issuing slice configuration, updating slice configuration, deleting slice configuration, or generating alarms.

[0076] Furthermore, the slice controller may also include a display module for viewing the network topology of the specified slice service and the current allocation of slice resources to achieve system visualization.

[0077] In this embodiment, if the control processing module searches the configuration data table and finds that the corresponding intermediate node has never issued any slice configuration, then the acquired slice configuration data is notified to the configuration module to be issued to the network node device serving as the intermediate node.

[0078] If the control processing module searches the configuration data table and finds that the corresponding intermediate node has issued a slice configuration, it will further perform a conflict check to compare the newly obtained slice information with the issued slice information. The comparison process is as follows:

[0079] If the two slice IDs are the same, the physical outbound interfaces are the same, but the slice bandwidth values ​​are different, the slice bandwidth value is compared with the slice bandwidth value configured on the source node. If they are consistent, the configuration module is notified to send the updated slice configuration to the network node device and update the slice bandwidth value. If they are inconsistent, it may be an illegal message or attack message on the network, and an alarm should be generated at this time. When the user needs to adjust the slice bandwidth of a specific service, the source node is manually updated through the controller, and the update is automatic.

[0080] If the two slice IDs are the same, the physical outbound interfaces are the same, and the slice bandwidth values ​​are the same, the current storage time of this entry in the configuration summary table is refreshed, and no other processing is performed.

[0081] If the Slice IDs of the two are different but the physical output interfaces are the same, check whether the slice resources of the physical output interface exceed the limit. If not, notify the configuration module to send a new slice configuration to the network node device of the intermediate node. If it does, generate an alarm message.

[0082] If the controller finds that the current storage time of an entry in the configuration data table exceeds the default aging time, it notifies the configuration module to send the slice deletion configuration to the network node device of the intermediate node.

[0083] like Figure 5 As shown, an embodiment of a functional module in a network node device is provided, and the network node device includes a configuration receiving module, a slice processing module and a reporting module.

[0084] When the configuration receiving module is used as a source node in the network node device, it is used to generate a corresponding slice forwarding table entry based on the Slice ID, slice bandwidth value and physical outbound interface information. The slice forwarding table entry is used to determine the slice sub-interface corresponding to the slice service to forward the service message (such as g→h).

[0085] When the network node device acts as a source node, the slice processing module is used to generate a slice identification extension header, such as SRv6 HBH, encapsulate the Slice ID and slice bandwidth value corresponding to the slice service into the slice identification extension header, and then find the corresponding sub-interface according to the Slice ID to forward the service message (such as g→h). When the network node device acts as an intermediate node, the slice processing module is used to identify the slice identification extension header in the slice service message, keep the slice identification extension header unchanged and forward it (as shown in the figure k→l→m→n); it is also used to extract the Slice ID and slice bandwidth value, as well as the network node device ID and the physical output interface to generate slice information, and send it to the reporting module. The reporting module is used to report the slice information to the slice controller when the network node device acts as an intermediate node (as shown in the figure k→l→i→j).

[0086] When the network node device acts as a host node, the slice processing module is used to identify the slice identification extension header, decapsulate it, restore the service message to the original message service and forward it.

[0087] The above are merely embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention are included in the scope of the claims of the present invention to be approved.

Claims

1. A SRv6 network slice configuration management method, characterized in that: Includes steps: S1. The slice controller sends slice configuration data to the source node. The slice configuration data includes SliceID, slice bandwidth value and physical outbound interface information. S2. The source node encapsulates the Slice ID and the Slice bandwidth value into the service message through the Slice ID extension header, and forwards it according to the slice sub-interface corresponding to the Slice ID; S3. The intermediate node forwards the service message; and extracts the Slice ID and the slice bandwidth value, plus the network node device ID and the physical outbound interface information to generate the slice information, and reports it to the slice controller; S4. The slice controller stores the previously received slice information to generate a configuration data summary table, analyzes the currently received slice information based on the configuration data summary table, and manages the slice configuration of the corresponding intermediate node.

2. The SRv6 network slice configuration management method according to claim 1, characterized in that: In S2, the source node generates a corresponding slice forwarding table entry based on the slice ID, slice bandwidth value and physical outbound interface information, and determines the slice sub-interface corresponding to the slice service; The slice identification extension header is SRv6 HBH. The source node encapsulates the Slice ID and slice bandwidth value of the slice service into the SRv6 HBH, and then encapsulates the SRv6 HBH into the service message.

3. The SRv6 network slice configuration management method according to claim 1, characterized in that: The S4 includes: If the corresponding intermediate node has never sent down any slice configuration, the controller will send the acquired slice configuration data to the network node device.

4. The SRv6 network slice configuration management method according to claim 1, characterized in that: The S4 includes: If the corresponding intermediate node has issued a slice configuration, compare the newly obtained slice information with the issued slice information; If the two slice IDs are the same, the physical outbound interfaces are the same, but the slice bandwidth values ​​are different, the slice bandwidth value is compared with the slice bandwidth value configured on the source node. If they are consistent, the updated slice configuration is sent to the network node device to update the slice bandwidth value; if they are inconsistent, an alarm message is generated; If the two slice IDs are the same, the physical outbound interfaces are the same, and the slice bandwidth values ​​are the same, the current storage time of this entry in the configuration summary table is refreshed, and no other processing is performed.

5. The SRv6 network slice configuration management method according to claim 1, characterized in that: The S4 includes: If the corresponding intermediate node has issued a slice configuration, compare the newly obtained slice information with the issued slice information; If the two Slice IDs are different but the physical output interfaces are the same, check whether the slice resources of the physical output interface exceed the limit. If not, send a new slice configuration to the network node device. If so, generate an alarm.

6. The SRv6 network slice configuration management method according to claim 1, characterized in that: The S4 includes: if the controller finds that the current storage time of an entry in the configuration data master table exceeds the default aging time, it sends the slice deletion configuration to the corresponding intermediate node.

7. The SRv6 network slice configuration management method according to claim 1, characterized in that: 1588 clock synchronization is implemented between the slice controller and all network nodes. In S3, the intermediate node periodically reports the slice information to the slice controller. The slice information is reported in the form of a message and carries 1588 timestamp data.

8. An SRv6 network slice configuration management system, characterized in that: It includes a slice controller and multiple network node devices, and the network node devices serve as source nodes or intermediate nodes; a two-way communication channel is established between the slice controller and all network node devices; The slice controller is used to send slice configuration data to the source node. The slice configuration data includes the slice ID, slice bandwidth value, and physical outbound interface information. It is also used to store previously received slice information to generate a configuration data summary table, analyze the currently received slice information based on the configuration data summary table, and manage the slice configuration of the corresponding intermediate node; The source node encapsulates the Slice ID and the Slice bandwidth value into the service message through the Slice ID extension header, and forwards it according to the slice sub-interface corresponding to the Slice ID. The intermediate node is used to forward the service message; it is also used to extract the Slice ID and slice bandwidth value, add the network node device ID and the physical output interface to generate slice information, and report it to the slice controller.

9. The SRv6 network slice configuration management system according to claim 8, characterized in that: The slice controller comprises: A receiving and storing module, used to store the received slice information by entry and generate a configuration data summary table; The control processing module is used to assign a unique Slice ID to the slice service; it is also used to obtain the network node device ID, Slice ID, slice bandwidth value and physical outbound interface information from the receiving storage module, and analyze it according to the configuration data summary table; The configuration module manages the slice configuration of the corresponding intermediate node according to the analysis results of the control processing module, including issuing slice configuration, updating slice configuration, deleting slice configuration, or generating alarms.

10. The SRv6 network slice configuration management system according to claim 8, characterized in that: The network node device includes a configuration receiving module, a slice processing module and a reporting module; The receiving module is configured to, when the network node device acts as a source node, generate a corresponding slice forwarding table entry based on the slice ID, the slice bandwidth value and the physical outbound interface information to determine the corresponding slice sub-interface; The slice processing module is used to, when the network node device acts as a source node, generate a slice identification extension header, encapsulate the Slice ID and slice bandwidth value corresponding to the slice service, and encapsulate the slice identification extension header into the service message, and forward it from the corresponding slice sub-interface; When the network node device acts as an intermediate node, it is used to identify the slice identifier extension header and forward the service message without changing the slice identifier extension header. It is also used to extract the slice ID and slice bandwidth value, add the network node device ID and the physical outbound interface to generate the slice information. The reporting module is used to report the slice information to the slice controller when the network node device acts as an intermediate node.

11. The SRv6 network slice configuration management system according to claim 10, characterized in that: The network node device also serves as a host node. At this time, the slice processing module is used to identify the slice identification extension header, decapsulate it, restore the service message to the original message service and forward it.

12. The SRv6 network slice configuration management system according to claim 8, characterized in that: The slice controller also includes a display module for viewing the network topology of the specified slice service and the allocation of current slice resources.

13. The SRv6 network slice configuration management system according to claim 8, characterized in that: A two-way communication channel is established between the slice controller and each network node device. The slice controller senses different network node devices through the node device ID and deploys 1588 clock synchronization in the entire network; The intermediate node periodically reports slice information to the slice controller and carries 1588 timestamp data.

Images