Slice resource coordination method, apparatus, system, electronic device, and storage medium

Abstract

This invention provides a method, apparatus, system, electronic device, and storage medium for slice resource coordination, relating to the field of communication technology. The method includes: a slice controller distributing configuration information, resource load thresholds, and forwarding decision rules for each SRv6 slice to each node; a head node receiving a service forwarding request, collecting the first real-time resource status data of its slice, encapsulating the slice identifier, the first real-time resource status data, and the collection timestamp into a TLV field and embedding it into the message's SRH header, and forwarding the message to an intermediate node; an intermediate node receiving the message and parsing the TLV field, determining the slice load status based on the first real-time resource status data, the slice's second real-time resource status data at the intermediate node, and the resource load threshold, and adjusting the message forwarding path according to the forwarding decision rules; and a tail node receiving the message and parsing the TLV field, adjusting the slice service quality based on the end-to-end resource status data. This invention achieves resource coordination between slices.

Description

Technical Field

[0001] This invention relates to the field of communication technology, specifically to a method, apparatus, system, electronic device, and storage medium for collaborative resource slicing. Background Technology

[0002] With the rapid development of 5G mobile communication, industrial internet, and cloud-network convergence technologies, network slicing, as a core technology for achieving flexible isolation and differentiated services of network resources, has been widely applied in critical business scenarios with high requirements for network quality and security, such as government, industry, and power. Among them, network slicing technology based on segment routing IPv6 (SRv6) has become a core technology for building next-generation bearer networks due to its flexible path programming capabilities and good scalability.

[0003] In related technologies, SRv6 slicing networks typically employ independent resource allocation and path configuration strategies, with the slice controller pre-allocating forwarding paths and resource quotas to each slice using a static configuration method. However, in this approach, slice resources are allocated independently, lacking coordinated scheduling. Intermediate nodes cannot make rapid decisions based on global and local real-time load, resulting in delayed path adjustments. Furthermore, tail nodes cannot dynamically adapt slice service quality based on the overall link resource status, easily leading to uneven network resource utilization and local node congestion, thus making it difficult to guarantee service transmission quality and overall network efficiency. Summary of the Invention

[0004] The present invention aims to provide a method, apparatus, system, electronic device and storage medium for slice resource coordination, so as to at least solve the problems of lack of coordinated scheduling of slice resources, delayed path adjustment, uneven utilization of network resources and local node congestion in the prior art, which make it difficult to guarantee the quality of service transmission and the overall efficiency of the network.

[0005] The technical solution of the present invention to solve the above-mentioned technical problems is as follows: This invention provides a method for collaborative management of sliced ​​resources, comprising: The slice controller distributes the slice configuration information, resource load thresholds, and forwarding decision rules of each SRv6 slice to the head node, intermediate nodes, and tail node. When the head node receives a service forwarding request, it collects the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs, encapsulates the slice identifier, the first real-time resource status data and its collection timestamp into a TLV field and embeds it into the SRH header of the SRv6 message, and forwards the SRv6 message to the intermediate node. The intermediate node receives the SRv6 packet and parses the TLV field. Based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node, and the resource load threshold, it determines the slice load status and adjusts the forwarding path of the SRv6 packet based on the slice load status and the forwarding decision rule. The tail node receives the SRv6 message and parses the TLV field, and adjusts the quality of service of the SRv6 slice based on the end-to-end resource status data.

[0006] The technical solution provided by this invention brings at least the following beneficial effects: In the slice resource coordination method provided by this invention, the head node uses the extensible TLV field of the SRH header of the SRv6 packet to carry resource status information. This eliminates the need to modify a large number of network devices and enables slice coordination under the existing SRv6 architecture, demonstrating scalability and practicality. By encapsulating the real-time resource status of the slice in the TLV field of the SRv6 packet, intermediate nodes can quickly make decisions and dynamically adjust forwarding paths based on global and local load, breaking the limitations of independent slice resource allocation and lack of coordination. This reduces local node congestion and makes resource allocation more balanced. Intermediate nodes can directly make local decisions based on the real-time resource status in the SRv6 packet, without relying on centralized and repeated calculations by the controller. This allows for rapid switching of forwarding paths based on slice load, improving path adjustment lag issues. The tail node can dynamically adjust the quality of service (QoS) strategy based on the full-link resource status of the entire link, rather than using a fixed configuration. This adapts to real-time network conditions and ensures service transmission quality even during node congestion or resource fluctuations.

[0007] Based on the above technical solution, the present invention can be further improved as follows.

[0008] Furthermore, the method also includes: the tail node summarizing the end-to-end resource status data and reporting it to the slice controller; the slice controller performing global optimization and adjustment of the slice configuration information and resource load threshold of each SRv6 slice based on the end-to-end resource status data.

[0009] The beneficial effects of this scheme are as follows: By reporting end-to-end resource status data through tail nodes, the slice controller can dynamically optimize slice configuration and resource thresholds based on the real-time load of the entire network. This achieves a combination of centralized global control and distributed real-time decision-making, which not only avoids the problem of poor resource adaptability caused by static configuration, but also further balances resource allocation and prevents congestion from the perspective of the entire network, continuously improving the overall network operating efficiency and service transmission stability.

[0010] Furthermore, the first real-time resource status data and the second real-time resource status data include bandwidth utilization, CPU utilization, and cache utilization; the slice configuration information includes the slice identifier and SID list, the SID list includes a default SID list and a backup SID list, the default SID list corresponds to the default forwarding path of the SRv6 packet, and the backup SID list corresponds to the backup forwarding path of the SRv6 packet.

[0011] The beneficial effects of this scheme are as follows: By using multi-dimensional resource status data including bandwidth utilization, CPU utilization, and cache utilization, the true load level of nodes can be comprehensively and accurately reflected, avoiding scheduling misjudgments caused by inaccurate judgment of a single indicator; by setting a default SID list and a backup SID list, backup forwarding paths can be provided to intermediate nodes when they perceive node congestion, thereby achieving flexible scheduling of forwarding paths.

[0012] Furthermore, the step of determining the slice load status based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node, and the resource load threshold includes: verifying the timeliness of the first real-time resource status data based on the collection timestamp; when the first real-time resource status data passes the timeliness verification, determining the comprehensive load based on the first real-time resource status data and the second real-time resource status data; and determining the slice load status based on the comprehensive load and the resource load threshold.

[0013] The beneficial effects of this scheme are as follows: By verifying the timeliness of the first real-time resource status data collection timestamp, the use of invalid resource data for scheduling decisions can be avoided, ensuring the real-time and accuracy of load judgment; after the timeliness verification is passed, the slice load status can be judged based on the comprehensive load and resource load threshold, which can effectively improve the identification accuracy of slice load and further improve the reliability of slice resource scheduling.

[0014] Furthermore, the timeliness verification of the first real-time resource status data based on the collection timestamp includes: determining whether the time difference between the collection timestamp and the current time is greater than a preset threshold; if the time difference is greater than the preset threshold, the first real-time resource status data is determined to have failed the timeliness verification, the SRv6 message is discarded, and a packet loss alarm is sent to the slice controller; otherwise, the first real-time resource status data is determined to have passed the timeliness verification.

[0015] The beneficial effects of adopting the above scheme are as follows: By judging the timeout of the collection timestamp of resource status data, expired and invalid status information can be effectively filtered out, avoiding incorrect path switching and load scheduling caused by outdated data; when the data times out, the packet is actively discarded and an alarm is reported to the controller, which can reduce the forwarding of invalid packets and save network bandwidth and node processing resources.

[0016] Furthermore, determining the slice load status based on the overall load and the resource load threshold includes: comparing the overall load with its corresponding resource load threshold; if the overall load corresponding to any type of resource is greater than its corresponding resource load threshold, the slice load status is determined to be overloaded, otherwise it is normal.

[0017] The beneficial effects of adopting the above scheme are as follows: By comparing the overall load with the corresponding resource load thresholds item by item, the overall load is determined as soon as any type of resource is overloaded. This can sensitively and timely identify node resource bottlenecks and avoid scheduling delays caused by congestion due to the depletion of a single resource. By adopting a multi-dimensional judgment method, the accuracy of load status identification can be improved, ensuring that path adjustment can be triggered when any resource such as bandwidth, CPU, or cache is under pressure. This effectively prevents local node congestion and ensures stable transmission of slice services.

[0018] Furthermore, adjusting the forwarding path of the SRv6 packet based on the slice load status and the forwarding decision rule includes: if the slice load status is normal, forwarding the SRv6 packet to the next-hop node according to the default forwarding path based on the default SID list; if the slice load status is overloaded, switching the current forwarding path to the backup forwarding path, and forwarding the SRv6 packet to the next-hop node based on the backup SID list.

[0019] The beneficial effects of adopting the above scheme are as follows: Based on the slice load status, the forwarding path can be flexibly selected. Under normal conditions, the default SID list is used to maintain regular forwarding. Under overload conditions, it automatically switches to the backup path corresponding to the backup SID list. It can achieve local fast path switching without relying on centralized control of the controller, effectively avoid congested nodes, reduce service latency and packet loss, and ensure the stability of service transmission.

[0020] Furthermore, adjusting the QoS of the SRv6 slice based on end-to-end resource status data includes: verifying the legality and completeness of the TLV field; if the verification passes, identifying the end-to-end resource load status of the SRv6 slice based on the end-to-end resource status data, and dynamically adjusting the QoS processing strategy of the SRv6 slice based on the end-to-end resource load status, wherein the QoS processing strategy includes at least one of service scheduling priority adjustment, bandwidth allocation ratio adjustment, cache scheduling mode adjustment, and service latency guarantee level adjustment; if the verification fails, discarding the SRv6 packet and sending a packet loss alarm to the slice controller.

[0021] The beneficial effects of adopting the above scheme are as follows: By verifying the legality and integrity of the TLV field of SRv6 packets, abnormal data can be effectively avoided from interfering with QoS decisions, ensuring the security and reliability of scheduling; after successful verification, QoS policies such as service priority, bandwidth allocation, cache scheduling, and latency guarantee can be dynamically adjusted based on the full-link resource status, which can accurately adapt the quality of service according to the actual network load, realize the priority guarantee of high-priority services, and improve resource utilization efficiency and service experience; if the verification fails, the packet is directly discarded and an alarm is reported, which can reduce the occupation of node resources by invalid packets and further improve the stability of the sliced ​​network.

[0022] Correspondingly, the present invention also provides a slice resource collaboration device, comprising: The pre-configuration module is used by the slice controller to distribute the slice configuration information, resource load thresholds and forwarding decision rules of each SRv6 slice to the head node, intermediate node and tail node; The message generation module is used to collect the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs when the head node receives the service forwarding request, encapsulate the slice identifier, the first real-time resource status data and its collection timestamp into a TLV field and embed it into the SRH header of the SRv6 message, and forward the SRv6 message to the intermediate node. The resource coordination module is used for the intermediate node to receive the SRv6 packet and parse the TLV field, determine the slice load status based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node and the resource load threshold, and adjust the forwarding path of the SRv6 packet based on the slice load status and the forwarding decision rule. The message receiving module is used by the tail node to receive the SRv6 message and parse the TLV field, and adjust the quality of service of the SRv6 slice based on the end-to-end resource status data.

[0023] Furthermore, the device also includes a global optimization module; the global optimization module is used for: the tail node to summarize the end-to-end resource status data and report it to the slice controller; the slice controller to perform global optimization and adjustment on the slice configuration information and resource load threshold of each SRv6 slice based on the end-to-end resource status data.

[0024] This invention also provides a slice resource collaboration system, the system comprising a controller layer, a head node layer, an intermediate node layer, and a tail node layer; wherein: The controller layer is equipped with a slice controller, which is used to distribute the slice configuration information, resource load threshold and forwarding decision rules of each SRv6 slice to the head node, intermediate node and tail node. The head node layer is deployed with a head node. When a service forwarding request is received, the head node is used to collect the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs, encapsulate the slice identifier, the first real-time resource status data and its collection timestamp into a TLV field and embed it into the SRH header of the SRv6 message, and forward the SRv6 message to the intermediate node. The intermediate node layer is deployed with at least one intermediate node. The intermediate node is used to receive the SRv6 packet and parse the TLV field, determine the slice load status based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node and the resource load threshold, and adjust the forwarding path of the SRv6 packet based on the slice load status and the forwarding decision rule. The tail node layer is deployed with tail nodes, which are used to receive the SRv6 messages and parse the TLV field, and adjust the quality of service of the SRv6 slice based on the end-to-end resource status data.

[0025] Furthermore, the tail node is also used to summarize the end-to-end resource status data and report it to the slice controller; the slice controller is also used to globally optimize and adjust the slice configuration information and resource load threshold of each SRv6 slice based on the end-to-end resource status data.

[0026] The present invention also provides an electronic device, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the instructions to implement the above-described slice resource collaboration method.

[0027] The present invention also provides a computer-readable storage medium having a computer program stored thereon, characterized in that the computer program, when executed by a processor, implements the above-described slice resource collaboration method. Attached Figure Description

[0028] Figure 1 This is a flowchart illustrating a method for collaborative resource slicing provided by the present invention. Figure 2 This is a schematic diagram of the TLV field structure in a slice resource collaboration method provided by the present invention; Figure 3 A schematic block diagram of a slice resource collaboration device provided by the present invention; Figure 4 A schematic block diagram of a slice resource collaboration system provided by the present invention; Figure 5 This is a schematic diagram of an electronic device provided by the present invention. Detailed Implementation

[0029] The principles and features of the present invention are described below. The examples given are only for explaining the present invention and are not intended to limit the scope of the present invention.

[0030] In related technologies, SRv6 slicing networks typically employ independent resource allocation and path configuration strategies. The slice controller pre-allocates forwarding paths and resource quotas to each slice in a static configuration manner. This results in problems such as a lack of coordinated scheduling of slice resources, delayed path adjustment, uneven utilization of network resources, and local node congestion, making it difficult to guarantee service transmission quality and overall network efficiency.

[0031] To address the aforementioned problems, this invention proposes a method, apparatus, system, electronic device, and computer-readable storage medium for collaborative resource slicing. The technical solutions of the embodiments of this disclosure are described in detail below: In one embodiment of the present invention, a method for collaborative use of sliced ​​resources is provided. (See reference...) Figure 1 As shown, the slice resource collaboration method specifically includes the following steps: S110: The slice controller distributes the slice configuration information, resource load thresholds and forwarding decision rules of each SRv6 slice to the head node, intermediate node and tail node; S120: When the head node receives a service forwarding request, it collects the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs, encapsulates the slice identifier, the first real-time resource status data and its collection timestamp into a TLV field and embeds it into the SRH header of the SRv6 message, and forwards the SRv6 message to the intermediate node. S130: The intermediate node receives the SRv6 message and parses the TLV field. Based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice in the intermediate node and the resource load threshold, it determines the slice load status and adjusts the forwarding path of the SRv6 message based on the slice load status and forwarding decision rules. S140: The tail node receives SRv6 messages and parses the TLV field, and adjusts the quality of service of SRv6 slices based on the end-to-end resource status data.

[0032] In the slice resource coordination method provided in the above embodiments, the head node uses the extensible TLV field of the SRH header of the SRv6 packet to carry resource status information. Without modifying a large number of network devices, slice coordination can be achieved under the existing SRv6 architecture, which has scalability and practicality. By encapsulating the real-time resource status of the slice in the TLV field of the SRv6 packet, the intermediate node can make quick decisions and dynamically adjust the forwarding path based on global and local load. This breaks the limitations of independent allocation of slice resources and lack of coordination, reduces local node congestion, and makes resource allocation more balanced. The intermediate node can make local decisions directly based on the real-time resource status in the SRv6 packet without relying on the controller to perform repeated calculations. It can quickly switch forwarding paths according to slice load and improve the problem of path adjustment lag. The tail node can dynamically adjust the quality of service policy according to the full link resource status of the entire link, instead of using a fixed configuration. It can adapt to the real-time network conditions and ensure the quality of service transmission even when there is node congestion or resource fluctuations.

[0033] The above steps will now be described in more detail in another embodiment.

[0034] In S110, the slice controller distributes the slice configuration information, resource load thresholds, and forwarding decision rules of each SRv6 slice to the head node, intermediate nodes, and tail node.

[0035] The aforementioned slice controller is a centralized control unit in the SRv6 slice network that manages SRv6 slices in a unified manner, and is responsible for resource allocation, policy distribution and status monitoring.

[0036] The aforementioned SRv6 slices are logically isolated networks built on segment routing IPv6 technology. They identify forwarding paths through a SID list, providing independent bandwidth, latency, and reliability guarantees for specific services, and achieving flexible isolation and differentiated services for network resources.

[0037] The aforementioned slice configuration information consists of basic configuration parameters used to identify and forward SRv6 slices. This slice configuration information includes at least a list of slice identifiers (Slice IDs) and segment identifiers (SIDs) for the corresponding SRv6 slice. The slice identifier distinguishes different SRv6 slices, and the SID list is a set of path identifiers composed of a series of SRv6 segment identifiers arranged in forwarding order, used to guide SRv6 packets to be forwarded along a specified path. For example, this embodiment includes a default SID list and a backup SID list. The default SID list corresponds to the default forwarding path for SRv6 packets, and the backup SID list corresponds to the backup forwarding paths for SRv6 packets.

[0038] The resource load thresholds mentioned above are pre-configured upper limits for resource usage in SRv6 slices, used to determine whether a node is in an overloaded state.

[0039] The aforementioned forwarding decision rule is the execution logic for intermediate nodes to select a forwarding path based on the slice load status. For example, this forwarding decision rule can be: forwarding along the default path when the load is normal, and switching to the backup path when the load is overloaded.

[0040] The aforementioned head node is the entry point in the SRv6 forwarding path, responsible for receiving service flows, generating SRv6 packets, encapsulating resource status information, and initiating packet forwarding.

[0041] The aforementioned intermediate nodes are forwarding processing nodes in the SRv6 forwarding path, responsible for parsing packets, determining slice load, and performing path switching.

[0042] The aforementioned tail node is the end node of the SRv6 forwarding path, responsible for receiving packets, parsing the entire link resource status, and dynamically adjusting the slice service quality (QoS).

[0043] In one specific implementation of this embodiment, the slice controller can distribute the slice configuration information, resource load threshold, and forwarding decision rules of each SRv6 slice to the head node, intermediate nodes, and tail node as follows: S1: Based on the differentiated needs of target business scenarios such as government affairs and industrial internet, the slice controller independently generates three core parameters for each SRv6 slice: slice configuration information, resource load threshold, and forwarding decision rules. S2: The slice controller encapsulates the three types of core parameters generated according to the configuration data specifications of the industry standard protocol, forming a structured configuration distribution message, and distributes the encapsulated configuration message to the head node, all intermediate nodes, and tail node through the control link; S3: The head node, intermediate node, and tail node receive configuration messages and verify the legality, integrity, and version consistency of the messages. If the verification fails, the node sends a configuration anomaly alarm to the slice controller, and the controller reissues the corresponding configuration. S4: After each node verifies the configuration message, it stores the slice configuration information, resource load threshold and forwarding decision rules in the local dedicated configuration library, and sends a configuration activation confirmation message to the slice controller. S5: The slice controller receives configuration activation feedback from all nodes and verifies whether all nodes have completed configuration activation. If there are nodes that have not provided feedback or whose configuration has failed, the controller triggers a re-deployment mechanism until the configuration of all nodes in the entire network has taken effect.

[0044] This embodiment realizes the pre-configuration stage of SRv6 slice resource collaboration through the above process. The slice controller uniformly distributes standardized slice configuration information, resource load thresholds and forwarding decision rules to all links, laying a unified and executable rule foundation for subsequent distributed local decision-making, dynamic path adjustment and QoS adaptation.

[0045] In S120, when the head node receives a service forwarding request, it collects the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs, encapsulates the slice identifier, the first real-time resource status data and its collection timestamp into a TLV field and embeds it into the SRH header of the SRv6 message, and forwards the SRv6 message to the intermediate node.

[0046] The aforementioned service forwarding request is a service request initiated by the service end that requires data transmission through the corresponding SRv6 slice. It is a trigger signal that triggers the head node to perform resource acquisition, message encapsulation, and forwarding actions. For example, this service forwarding request can be the actual business data transmission needs in scenarios such as government affairs and industrial internet, such as a programmable logic controller (PLC) control signal transmission request.

[0047] The aforementioned first real-time resource status data refers to the multi-dimensional core resource usage status data of the SRv6 slice to which the received service forwarding request belongs, collected in real time by the head node. It directly reflects the resource load of the slice on the head node side. Specifically, this first real-time resource status data may include three core indicators: bandwidth utilization, CPU utilization, and cache utilization. Correspondingly, the aforementioned resource load thresholds may include bandwidth utilization thresholds, CPU utilization thresholds, and cache utilization thresholds.

[0048] The aforementioned collection timestamp is a precise time identifier for the first real-time resource status data collected by the head node. It is used to characterize the generation time of the resource data and provides a basis for subsequent intermediate and tail nodes to verify the timeliness of the resource data, ensuring that the entire link executes scheduling decisions based on effective and real-time resource data.

[0049] The aforementioned SRH header, or Segment Routing Header (SRH), is a standard header component of SRv6 packets, containing information such as the segment identifier required for slice forwarding.

[0050] The aforementioned TLV field is the real-time status TLV field of the slice resource introduced in this embodiment through the extension of the Optional TLV area in the SRH header of the SRv6 standard protocol (RFC9800). Specifically, as shown... Figure 2 As shown, this TLV field is a 20-byte fixed-length structured field, which is the core carrier of slice identifier, first real-time resource status data, and collection timestamp. Its field definition is shown in Table 1 below: Table 1: This embodiment introduces a slice resource real-time status TLV field into the SRH header Optional TLV area of ​​the SRv6 standard protocol, which enables the native carrying of multi-dimensional resource status in SRv6 messages without the need for additional dedicated signaling channels.

[0051] In one specific implementation of this embodiment, when the head node receives a service forwarding request, it collects the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs, encapsulates the slice identifier, the first real-time resource status data, and its collection timestamp into a TLV field, embeds it into the SRH header of the SRv6 message, and forwards the SRv6 message to the intermediate node as follows: S1: Receive service forwarding requests, and based on the service identification information in the request, match the Slice ID stored in the local configuration library to identify the SRv6 slice to which the service forwarding request belongs, ensuring that subsequent resource collection and packet encapsulation are only performed on the SRv6 slice to which it belongs. S2: For the identified SRv6 slice, collect the first real-time resource status data of that slice on its own node in real time and generate a precise collection timestamp, and uniquely bind the collection timestamp with the collected first real-time resource status data. Among them, the collection indicators of the first real-time resource status data need to cover three core dimensions: bandwidth utilization, CPU utilization, and cache utilization.

[0052] S3: Encapsulate the Slice ID of the identified SRv6 slice and the first real-time resource status data bound to the acquisition timestamp according to the above-mentioned preset TLV field standard format to generate a 20-byte fixed-length slice resource real-time status TLV field. S4: Based on the SRv6 standard protocol specification, a basic SRv6 message framework is built, which includes the IPv6 header and service data payload. The encapsulated slice resource real-time status TLV field is embedded into the Optional TLV extension area of ​​the SRH header of the SRv6 message to form a complete SRv6 message, realizing the native binding of slice resource status data and service messages. S5: Based on the default SID list of identified SRv6 slices pre-stored in the local configuration library, determine the next-hop intermediate node for packet forwarding, and send the assembled SRv6 packet to the corresponding intermediate node through the forwarding port.

[0053] This embodiment realizes the packet encapsulation and forwarding initiation stage of SRv6 slice resource collaboration through the above process. The head node completes real-time acquisition of slice resources, TLV field encapsulation and SRv6 packet forwarding based on the service forwarding request, realizing the native binding of resource status and service packets. It can provide real-time and accurate resource data support for end-to-end distributed collaborative decision-making, while conforming to the SRv6 standard protocol architecture and taking into account both real-time performance and compatibility.

[0054] In S130, the intermediate node receives SRv6 packets and parses the TLV field. Based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice in the intermediate node, and the resource load threshold, it determines the slice load status and adjusts the forwarding path of the SRv6 packets based on the slice load status and forwarding decision rules.

[0055] The aforementioned second real-time resource status data is the multi-dimensional core resource usage status data of the SRv6 slice to which the received SRv6 message belongs, collected in real time by the intermediate node. It is a direct reflection of the resource load of the slice on the intermediate node side. The collection dimensions of this second real-time resource status data are consistent with the first real-time resource status data of the head node, both including three core indicators: bandwidth utilization, CPU utilization, and cache utilization. The collection accuracy and data format also match the pre-configured resource load threshold. It can be combined with the first real-time resource status data of the head node to complete the comprehensive judgment of the slice load.

[0056] The above-mentioned slice load status is the result of the intermediate node's judgment on the resource usage status of the SRv6 slice in the current forwarding link, based on the first real-time resource status data, the second real-time resource status data, and the pre-configured resource load threshold. It includes two categories: normal status and overload status.

[0057] Preferably, in the embodiment, the above-mentioned determination of slice load status based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node, and the resource load threshold can be implemented by the following method: verifying the timeliness of the first real-time resource status data based on the collection timestamp; when the first real-time resource status data passes the timeliness verification, determining the comprehensive load based on the first real-time resource status data and the second real-time resource status data; and determining the slice load status based on the comprehensive load and the resource load threshold.

[0058] The aforementioned timeliness verification is a check action performed by the intermediate node to determine whether the first real-time resource status data forwarded by the head node is within the valid time range. Its purpose is to filter out expired and invalid resource data and avoid making incorrect load judgments and forwarding decisions based on outdated data.

[0059] Furthermore, the above-mentioned timeliness verification of the first real-time resource status data based on the collection timestamp can be implemented by the following method: determine whether the time difference between the collection timestamp and the current time is greater than a preset threshold; if the time difference is greater than the preset threshold, it is determined that the first real-time resource status data has failed the timeliness verification, the SRv6 message is discarded, and a packet loss alarm is sent to the slice controller; otherwise, it is determined that the first real-time resource status data has passed the timeliness verification.

[0060] The aforementioned comprehensive load is the slice load data obtained by integrating the first real-time resource status data that has passed timeliness verification and the second real-time resource status data collected by the intermediate node according to the same resource dimension. It can be used to reflect the overall resource utilization level of the link segment from the head node to the intermediate node. The calculation dimension must be consistent with the resource collection dimension, that is, a corresponding comprehensive load needs to be calculated for bandwidth utilization, CPU utilization, and cache utilization respectively.

[0061] For example, the aforementioned overall load can be determined by the following method: For each resource acquisition dimension, calculate the average of the corresponding first real-time resource status data and second real-time resource status data, and record it as the overall load under that resource acquisition dimension. Taking CPU utilization as an example, assuming the CPU utilization rate collected by the head node is 32.50% and the local CPU utilization rate collected by the intermediate node is 40%, then the overall load corresponding to the CPU utilization rate = (32.50% + 40%) / 2 = 36.25%.

[0062] Furthermore, the above-mentioned determination of slice load status based on comprehensive load and resource load threshold can be implemented in the following way: compare the comprehensive load with its corresponding resource load threshold; if the comprehensive load corresponding to any type of resource is greater than its corresponding resource load threshold, the slice load status is determined to be overloaded; otherwise, it is normal. That is, if the comprehensive load of any resource type among bandwidth utilization, CPU utilization, and cache utilization is greater than its resource load threshold, the slice load status is determined to be overloaded.

[0063] Preferably, the above-mentioned adjustment of the forwarding path of SRv6 packets based on slice load status and forwarding decision rules can be implemented by the following method: if the slice load status is normal, the SRv6 packets are forwarded to the next hop node according to the default forwarding path based on the default SID list; if the slice load status is overloaded, the current forwarding path is switched to the backup forwarding path, and the SRv6 packets are forwarded to the next hop node based on the backup SID list.

[0064] In one specific implementation of this embodiment, the intermediate node receives SRv6 packets and parses the TLV field. Based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node, and the resource load threshold, it determines the slice load status. The complete implementation process of adjusting the forwarding path of the SRv6 packet based on the slice load status and forwarding decision rules is as follows: S1: Receive SRv6 messages and parse the TLV field, extract the collection timestamp and its bound first real-time resource status data (bandwidth utilization, CPU utilization and cache utilization) from the TLV field. S2: Obtain the current system time in seconds, calculate the time difference between the collected timestamp and the current time, and compare the time difference with a preset threshold (set to 1 second in this specific implementation). If the time difference is greater than 1 second, continue to execute S3; if the time difference is less than or equal to 1 second, continue to execute S4. S3: If the first real-time resource status data is determined to be invalid, the SRv6 message is immediately discarded, and a packet loss and data failure alarm is sent to the slice controller. The process is terminated. S4: Determine that the first real-time resource status data has passed the timeliness verification, and continue to execute S5; S5: For the SRv6 slice to which the SRv6 message belongs, collect the second real-time resource status data (bandwidth utilization, CPU utilization and cache utilization) of the SRv6 slice on its own node in real time, and the collection accuracy and data format are consistent with the first real-time resource status data. S6: Integrate the first real-time resource status data that has passed the timeliness verification with the second real-time resource status data collected locally according to the same resource dimension, and calculate the comprehensive load according to the average value of the three dimensions of bandwidth, CPU and cache respectively. The calculation formula is: Comprehensive load of a certain dimension = (utilization rate of the head node in this dimension + utilization rate of the intermediate node in this dimension) / 2. S7: Compare the overall load of each dimension with the pre-configured corresponding resource load thresholds item by item. If the overall load of all dimensions does not exceed the corresponding resource load threshold, the slice load status is determined to be normal and continue to S8; if the overall load of any dimension exceeds the corresponding resource load threshold, the slice load status is determined to be overloaded and continue to S9. S8: Retrieve the forwarding decision rules pre-stored in the local configuration library that are bound to the slice identifier of the SRv6 slice. Based on the matching result of the load status and the forwarding decision rules (forwarding along the default path), retrieve the default SID list of the SRv6 slice and use the default SID list as a routing guide to send the SRv6 packet to the next hop node through the local forwarding port. S9: Retrieve the forwarding decision rules pre-stored in the local configuration library that are bound to the slice identifier of the SRv6 slice. Based on the matching result of the load status and the forwarding decision rules (switching to the alternative path forwarding), retrieve the alternative SID list of the SRv6 slice, and use the alternative SID list as a routing guide to send the SRv6 packet to the next hop node through the local forwarding port.

[0065] This embodiment achieves local decision-making and forwarding execution for SRv6 slice resource coordination through the above process. The intermediate node completes SRv6 packet parsing, resource data verification, load status determination, and dynamic adjustment of the forwarding path, realizing local dynamic coordination of resource status and forwarding decisions, eliminating reliance on real-time commands from the slice controller. Simultaneously, congestion avoidance is achieved through multi-dimensional load assessment and precise path adjustment, ensuring low latency and high stability for end-to-end slice service transmission.

[0066] In S140, the tail node receives SRv6 messages and parses the TLV field, adjusting the quality of service of the SRv6 slice based on the end-to-end resource status data.

[0067] The above-mentioned end-to-end resource status data is a multi-dimensional resource usage status data set covering the head node, intermediate nodes and tail node of the entire forwarding link, which intuitively reflects the resource load level of SRv6 slices across the entire link.

[0068] Preferably, the above-mentioned adjustment of the QoS of SRv6 slices based on end-link resource status data can be achieved by the following method: verifying the legality and integrity of the TLV field; if the verification is successful, identifying the end-link resource load status of the SRv6 slice based on the end-link resource status data, and dynamically adjusting the QoS processing strategy of the SRv6 slice based on the end-link resource load status. The QoS processing strategy includes at least one of service scheduling priority adjustment, bandwidth allocation ratio adjustment, cache scheduling mode adjustment, and service latency guarantee level adjustment; if the verification fails, discarding the SRv6 packet and sending a packet loss alarm to the slice controller.

[0069] In one specific implementation of this embodiment, the tail node receives the SRv6 message and parses the TLV field. The complete execution process for adjusting the service quality of the SRv6 slice based on the end-to-end resource status data can be as follows: S1: Receive the SRv6 message forwarded by the intermediate node and verify the validity, integrity, and timeliness of the TLV field through triple checks. If the TLV field fails the check, proceed to S2; if the TLV field passes the check, proceed to S3. S2: Discard the SRv6 message and send a packet loss and TLV field anomaly alarm to the slice controller, and terminate the process; S3: Perform a complete parsing of the TLV field to extract the slice identifier, collection timestamp, and the first real-time resource status data of the head node (bandwidth utilization, CPU utilization, cache utilization). S4: For the SRv6 slice corresponding to the parsed slice identifier, collect multi-dimensional resource status data (bandwidth utilization, CPU utilization, cache utilization) of the SRv6 slice on its own node in real time, and the collection accuracy and data format are consistent with those of the head node and intermediate nodes. S5: Integrate the first real-time resource status data of the head node obtained by parsing with the local multi-dimensional resource status data of the tail node collected by itself, and combine it with the message forwarding path information transmitted by the intermediate node to form a full-link resource status data set covering the head node, intermediate node and tail node. S6: Retrieve the preset QoS requirements of the slice service bound to the slice identifier of the SRv6 slice in the local configuration library, and clarify the core service quality indicators and priorities of the slice; S7: Based on the overall link resource load level and the pre-set QoS requirements of the slice, the QoS processing strategy is dynamically adapted accordingly. Details are as follows: S71: In scenarios where the overall resource load is low (the resource utilization of each node is far below the threshold), a high-performance optimization strategy is launched to improve the service processing priority of the SRv6 slice: enable high-speed caching mode, store the service load in the low-latency cache area to reduce data processing latency; improve the forwarding scheduling priority of slice packets to reduce queue waiting time; release redundant cache resources to improve service throughput and further reduce latency jitter. S72: In scenarios where the end-to-end resource load is high or close to the threshold, activate the stability guarantee optimization strategy to ensure that core QoS indicators meet the standards: enable dedicated cache isolation, allocate a fixed cache quota to this SRv6 slice to avoid competing for resources with other slices; adopt a low jitter scheduling algorithm to limit the queue forwarding latency of slice packets and ensure that core indicators (such as latency and packet loss rate) meet the preset requirements; reduce the processing priority of non-core services and tilt resources toward the core services of this SRv6 slice.

[0070] In addition, this embodiment can also use the following method to achieve global optimization: the tail node summarizes the full-link resource status data and reports it to the slice controller; the slice controller performs global optimization and adjustment on the slice configuration information and resource load threshold of each SRv6 slice based on the full-link resource status data.

[0071] This embodiment achieves the final closed-loop link of SRv6 slice resource coordination through the above process. The tail node obtains the resource data of the head node by parsing the TLV field and integrates its own collected information to form full-link resource status data. Based on this, the slice QoS strategy is dynamically adjusted, which not only achieves accurate adaptation between network resource fluctuations and service quality, ensuring that the core QoS indicators of highly sensitive services are stably met, but also eliminates the dependence on real-time commands from the controller by relying on local QoS optimization, which greatly reduces the control plane interaction overhead. At the same time, by reporting full-link resource and operation and maintenance data to the slice controller, a global collaborative closed loop from collection, scheduling, adaptation to feedback is constructed, which improves the overall network resource utilization.

[0072] Below, taking the PLC control signal scenario in the industrial internet context as an example, the execution flow of the above-mentioned slice resource collaboration method will be described in detail in a specific embodiment: In this specific embodiment, the network architecture of the above-mentioned dedicated SRv6 slice test network for industrial internet scenarios includes one slice controller, one head node, two intermediate nodes and one tail node; a dedicated SRv6 slice for industrial control is deployed separately in the network, with slice ID=0x00000005, to achieve logical isolation between industrial control services and other network services.

[0073] The aforementioned SRv6 slice 0x00000005 is used to carry PLC control signal transmission services. Its core performance requirements are: bandwidth requirement of 50Mbps, end-to-end transmission latency ≤10ms, latency jitter ≤5ms, and slice resource utilization rate ≥80%, in order to ensure the real-time performance and stability of industrial production instructions.

[0074] The pre-configured parameters of the slice controller are as follows: Resource load thresholds: CPU utilization threshold ≥75%, bandwidth utilization threshold ≥80%, cache utilization threshold ≥85%; Forwarding path configuration: The default forwarding path is fc00:5::1→fc00:5::2→fc00:5::5, and the backup forwarding path is fc00:5::1→fc00:5::3→fc00:5::5; Pre-set threshold for TLV timeliness verification: The timeliness of resource data collected by the head node is ≤1 second, and expired data is discarded directly.

[0075] In this specific embodiment, slice resource collaboration mainly includes four stages: slice controller pre-configuration, head node resource acquisition and TLV encapsulation, intermediate node forwarding, and tail node verification and reporting. Specifically: S1: Slice controller pre-configuration stage, specifically implemented as follows: The slice controller, based on the NETCONF standardized protocol, distributes slice configuration parameters globally to the head node, intermediate nodes, and tail node, specifically including: Basic slice parameters: Slice ID=0x00000005, primary and backup SID list, slice resource quota (CPU usage 60%, bandwidth 50Mbps, cache 250MB); Forwarding decision rules: When a slice is determined to be in an overload state, it will automatically switch to the backup path for forwarding and strictly enforce the TLV data timeliness verification rules.

[0076] S2: Head node resource acquisition and TLV encapsulation stage, specifically implemented as follows: S21: Real-time resource acquisition: After receiving the PLC control signal transmission request, the head node acquires local real-time resource status data for the industrial control slice with Slice ID=0x00000005: bandwidth utilization 45.20%, CPU utilization 32.50%, cache utilization 28.30%, and synchronously generates an acquisition timestamp of 6719 seconds. S22: TLV field encapsulation: Encapsulate the real-time status TLV field of the slice resource according to the preset 20-byte fixed format, and generate the corresponding byte stream: 07 14 00 00 00 05 42 34 66 66 42 0A 66 66 41 E1 99 9A 1A 3F; S23: SRv6 message assembly: Construct a standard IPv6 header (source address 2001:db8:1::1, destination address 2001:db8:5::1), embed the encapsulated TLV field into the SRH header extension area, and assemble it into a complete SRv6 message with a total length of 1080 bytes, along with a 1024-byte PLC control signal payload.

[0077] S3: Intermediate node forwarding phase, implemented as follows: S31: Normal Scenario: After receiving the SRv6 message, the first intermediate node (fc00:5::2) parses the TLV field to extract the header node resource data and timestamp, and the timeliness verification passes; the local slice CPU utilization rate is collected to be 40%, and the comprehensive CPU load is calculated to be (32.50%+40%) / 2=36.25%, which is lower than the preset CPU threshold of 75%. The slice is determined to be in a normal load state. The SRv6 message is forwarded to the second intermediate node according to the default forwarding path, and finally transmitted to the tail node. The service latency is 8ms, which meets the indicator requirements.

[0078] S32: Overload Scenario: After 10 minutes of operation, the first intermediate node is affected by other slice services, and the local industrial control slice CPU utilization rate rises to 90%. The head node fluctuates slightly with the service load, and the real-time updated slice CPU utilization rate is 60%. For the SRv6 message received by the first intermediate node after the update, the CPU-dimensional comprehensive load is calculated as (90%+60%) / 2=75%, which reaches the preset CPU threshold of 75%, and the slice is determined to be in an overload state. According to the pre-configured forwarding decision rules, the intermediate node immediately switches to the backup path (fc00:5::3). The local slice CPU utilization rate of the backup intermediate node is only 25%, and the calculated comprehensive load is (60%+25%) / 2=42.5%, which is lower than the preset threshold. This path switch takes 45ms, and the service transmission latency is stably maintained at 8ms with no obvious jitter, ensuring uninterrupted transmission of PLC control signals.

[0079] S4: Tail node verification and reporting, implemented as follows: S41: TLV validity verification: The tail node receives the SRv6 message and parses the TLV field, verifies that Type=0x07 and SliceID=0x00000005, the data format is compliant and the timeliness meets the standard, and the verification passes; S42: QoS Dynamic Adaptation: After evaluation, the resource load of the entire link slice is low. The tail node enables the high-speed cache optimization mode, and the PLC instruction processing latency is reduced from 3ms to 1.5ms, further improving the service response speed. S43: Data aggregation and reporting: The tail node aggregates the resource data and service transmission indicators of all nodes in the entire link and reports them to the slice controller every 30 seconds. After receiving the data, the controller determines that the current resource allocation is reasonable and the scheduling strategy is effective, without needing to perform global parameter adjustments.

[0080] This specific embodiment achieves dynamic resource perception and intelligent path scheduling of industrial control slices through the above process. The transmission delay of PLC control signals is stably controlled within 8ms, the delay jitter is less than 2ms, and there is no packet loss or interruption throughout the process, which fully meets the stringent business requirements of industrial Internet scenarios and improves the overall utilization rate of network resources.

[0081] Correspondingly, the present invention also provides a slice resource collaboration device, see reference. Figure 3 As shown, the slice resource coordination device 300 may include a pre-configuration module 310, a message generation module 320, a resource coordination module 330, and a message receiving module 340. Wherein: The pre-configuration module 310 can be used by the slice controller to distribute the slice configuration information, resource load threshold and forwarding decision rules of each SRv6 slice to the head node, intermediate node and tail node; The message generation module 320 can be used by the head node to collect the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs when it receives a service forwarding request, encapsulate the slice identifier, the first real-time resource status data and its collection timestamp into a TLV field and embed it into the SRH header of the SRv6 message, and forward the SRv6 message to the intermediate node. The resource coordination module 330 can be used to receive SRv6 packets and parse the TLV field in the intermediate node, determine the slice load status based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice in the intermediate node and the resource load threshold, and adjust the forwarding path of the SRv6 packet based on the slice load status and forwarding decision rules. The message receiving module 340 can be used by the tail node to receive SRv6 messages and parse the TLV field, and adjust the quality of service of SRv6 slices based on the end-link resource status data.

[0082] In one implementation of this embodiment, the above-mentioned device further includes a global optimization module; the global optimization module is used for: the tail node to summarize the full-link resource status data and report it to the slice controller; the slice controller to perform global optimization and adjustment on the slice configuration information and resource load threshold of each SRv6 slice based on the full-link resource status data.

[0083] In one implementation of this embodiment, the first real-time resource status data and the second real-time resource status data include bandwidth utilization, CPU utilization, and cache utilization; the slice configuration information includes slice identifiers and a SID list, the SID list includes a default SID list and a backup SID list, the default SID list corresponds to the default forwarding path of SRv6 packets, and the backup SID list corresponds to the backup forwarding path of SRv6 packets.

[0084] In one implementation of this embodiment, the resource coordination module 330 performs the following method to determine the slice load status based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node, and the resource load threshold: verifying the timeliness of the first real-time resource status data based on the collection timestamp; when the first real-time resource status data passes the timeliness verification, determining the comprehensive load based on the first real-time resource status data and the second real-time resource status data; and determining the slice load status based on the comprehensive load and the resource load threshold.

[0085] In one implementation of this embodiment, the resource coordination module 330 performs the timeliness verification of the first real-time resource status data based on the collection timestamp by executing the following method: determining whether the time difference between the collection timestamp and the current time is greater than a preset threshold; if the time difference is greater than the preset threshold, it is determined that the first real-time resource status data has failed the timeliness verification, the SRv6 message is discarded, and a packet loss alarm is sent to the slice controller; otherwise, it is determined that the first real-time resource status data has passed the timeliness verification.

[0086] In one implementation of this embodiment, the resource coordination module 330 determines the slice load status based on the overall load and resource load threshold by performing the following method: comparing the overall load and its corresponding resource load threshold; if the overall load corresponding to any type of resource is greater than its corresponding resource load threshold, the slice load status is determined to be overloaded, otherwise it is normal.

[0087] In one implementation of this embodiment, the resource coordination module 330 adjusts the forwarding path of SRv6 packets based on slice load status and forwarding decision rules by executing the following method: if the slice load status is normal, the SRv6 packets are forwarded to the next-hop node according to the default forwarding path based on the default SID list; if the slice load status is overloaded, the current forwarding path is switched to the backup forwarding path, and the SRv6 packets are forwarded to the next-hop node based on the backup SID list.

[0088] In one implementation of this embodiment, the message receiving module 340 implements the above-mentioned adjustment of the QoS of the SRv6 slice based on the end-link resource status data by executing the following method: verifying the legality and integrity of the TLV field; if the verification is successful, identifying the end-link resource load status of the SRv6 slice based on the end-link resource status data, and dynamically adjusting the QoS processing strategy of the SRv6 slice based on the end-link resource load status, the QoS processing strategy including at least one of service scheduling priority adjustment, bandwidth allocation ratio adjustment, cache scheduling mode adjustment, and service latency guarantee level adjustment; if the verification fails, discarding the SRv6 message and sending a packet loss alarm to the slice controller.

[0089] It should be noted that the specific implementation details of the above-mentioned slice resource collaboration device have been explained in detail in the corresponding section of the above-mentioned slice resource collaboration method, so they will not be repeated here.

[0090] In addition, this embodiment also provides a slice resource collaboration system, referencing Figure 4 As shown, the slice resource collaboration system includes a controller layer, a head node layer, an intermediate node layer, and a tail node layer; wherein: The controller layer is equipped with a slice controller, which is used to distribute the slice configuration information, resource load threshold and forwarding decision rules of each SRv6 slice to the head node, intermediate node and tail node. The head node layer is deployed with a head node. When a service forwarding request is received, the head node is used to collect the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs, encapsulate the slice identifier, the first real-time resource status data and its collection timestamp into a TLV field and embed it into the SRH header of the SRv6 message, and forward the SRv6 message to the intermediate node. The intermediate node layer is deployed with at least one intermediate node. The intermediate node is used to receive SRv6 packets and parse the TLV field. It determines the slice load status based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice in the intermediate node and the resource load threshold. It adjusts the forwarding path of SRv6 packets based on the slice load status and forwarding decision rules. The tail node layer is deployed with tail nodes, which are used to receive SRv6 messages and parse the TLV field, and adjust the quality of service of SRv6 slices based on the end-to-end resource status data.

[0091] In one implementation of this embodiment, the tail node is further used to aggregate end-to-end resource status data and report it to the slice controller; the slice controller is further used to perform global optimization and adjustment of the slice configuration information and resource load threshold of each SRv6 slice based on the end-to-end resource status data.

[0092] The hierarchical structure of the above-mentioned slice resource collaboration system will be described in detail below in a specific embodiment: In this specific embodiment, the above-mentioned slice resource collaboration system adopts a layered distributed architecture, which is divided into a controller layer, a head node layer, an intermediate node layer, and a tail node layer from top to bottom. The four layers work together to achieve full-domain control, real-time perception, dynamic forwarding, and closed-loop optimization of slice resources. The positioning, module composition, and core functions of each layer are as follows: The aforementioned controller layer serves as the global decision-making center for the entire system, responsible for slice-wide control and global optimization. It integrates three core modules: a slice resource management module, a decision rule distribution module, and a global status aggregation module. Their specific functions are as follows: This layer establishes communication connections with the head nodes, intermediate nodes, and tail nodes of the entire network through control plane signaling. Its core functions include: the slice resource management module, which is responsible for coordinating slice resources across the entire domain and distributing standardized slice configuration parameters to all nodes in the network, covering slice identifiers, primary and backup SID path lists, and slice resource quotas; the decision rule distribution module, which is responsible for distributing preset control rules, including resource load thresholds and forwarding decision rules for switching backup paths when overloaded; and the global status aggregation module, which is responsible for receiving end-to-end resource status data and business operation and maintenance data periodically reported by tail nodes, and performing global optimization and adjustment of slice configurations, resource thresholds, and forwarding paths based on the aggregated data to ensure the rationality of resource scheduling across the entire network.

[0093] The aforementioned header node layer serves as the system's resource acquisition and message encapsulation endpoint, acting as the starting point for service access and data collection. It integrates three core modules: a slice resource acquisition module, a TLV encapsulation module, and a message forwarding module. Their specific functions are as follows: This layer handles transmission requests initiated by the business side. Its core functions include: the slice resource acquisition module is responsible for collecting three types of core resource data in real time for SRv6 slices: local bandwidth utilization, CPU utilization, and cache utilization; the TLV encapsulation module is responsible for encapsulating the slice identifier, real-time resource data, and acquisition timestamp into a dedicated slice resource TLV field according to a preset 20-byte fixed format; and the packet forwarding module is responsible for embedding the TLV field into the extended area of ​​the SRH header of the SRv6 packet, assembling the complete packet, and forwarding it along the preset path to achieve native binding and transmission of resource data and business packets.

[0094] The aforementioned intermediate node layer is the core of the system's local forwarding decision-making, responsible for packet forwarding and dynamic path scheduling. It integrates three core modules: TLV parsing module, resource status assessment module, and dynamic forwarding module, with the following specific functions: This layer handles SRv6 packets forwarded by the header node. Its core functions include: the TLV parsing module is responsible for extracting header node resource data, collection timestamp, and slice identifier from the packet; the resource status assessment module is responsible for verifying the timeliness of the first real-time resource data, calculating the comprehensive load by combining it with the locally collected second real-time resource data, and determining the slice load status; and the dynamic forwarding module is responsible for executing local decisions, forwarding along the default path when the load is normal, and automatically switching to the backup path when overloaded.

[0095] The aforementioned tail node layer serves as the system's end-point verification and feedback mechanism, a core node for business delivery and data closure. It integrates three core modules: a TLV verification module, a business adaptation module, and a status reporting module, with the following specific functions: This layer, as the end node of the forwarding path, has the following core functions: The TLV verification module is responsible for triple verification of the legality, integrity, and timeliness of the TLV field of the packet, filtering abnormal packets and reporting alarms; The service adaptation module is responsible for integrating the resource data of the entire link, dynamically adjusting the QoS processing strategy according to the needs of slice services, and ensuring that the core service indicators meet the standards; The status reporting module is responsible for summarizing the resource data of the entire link and the service transmission indicators, and reporting them to the controller on a regular basis to form a closed loop of full-domain collaboration.

[0096] It should be noted that the specific implementation details of the above-mentioned slice resource collaboration system have been explained in detail in the corresponding section of the above-mentioned slice resource collaboration method, so they will not be repeated here.

[0097] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0098] An electronic device according to the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements any of the above-mentioned slice resource coordination methods. That is, an electronic device according to the present invention may include, but is not limited to: a processor and a memory; the memory is used to store the computer program; the processor is used to execute the slice resource coordination method shown in any embodiment of the present invention by calling the computer program.

[0099] In one alternative embodiment, an electronic device is provided, such as Figure 5 As shown, Figure 5The illustrated electronic device 5000 includes a processor 5001 and a memory 5003. The processor 5001 and the memory 5003 are connected, for example, via a bus 5002. Optionally, the electronic device 5000 may further include a transceiver 5004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 5004 is not limited to one type, and the structure of the electronic device 5000 does not constitute a limitation on the present invention.

[0100] Processor 5001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this invention. Processor 5001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0101] Bus 5002 may include a path for transmitting information between the aforementioned components. Bus 5002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 5002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The bus 5002 is represented by only one thick line, but this does not mean that there is only one bus or one type of bus.

[0102] The memory 5003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0103] The memory 5003 stores application code (computer program) for executing the present invention, and its execution is controlled by the processor 5001. The processor 5001 executes the application code stored in the memory 5003 to implement the content shown in the foregoing method embodiments.

[0104] Among them, electronic devices can also be terminal devices, which can be any device that can install applications, including at least one of smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, smart TVs, and smart in-vehicle devices.

[0105] It should be noted that, Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the invention.

[0106] The present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements any of the above-described slice resource collaboration methods.

[0107] Alternatively, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, a floppy disk, and an optical data storage device, etc.

[0108] In an exemplary embodiment, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the aforementioned sliced ​​resource coordination method.

[0109] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0110] It should be understood that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of methods and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0111] The computer-readable storage medium provided by this invention can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EEPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0112] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the method shown in the above embodiments.

[0113] The above description is merely a preferred embodiment of the present invention and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this invention is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-disclosed concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this invention.

[0114] It should be noted that the terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and represent a limitation on a specific order or sequence. Where appropriate, the order of use for similar objects can be interchanged so that the embodiments of this application described herein can be implemented in an order other than that shown or described.

[0115] Those skilled in the art will recognize that this invention can be implemented as a system, method, or computer program product. Therefore, this invention can be specifically implemented in the following forms: it can be entirely hardware, entirely software (including firmware, resident software, microcode, etc.), or a combination of hardware and software, generally referred to herein as a "circuit," "module," or "system." Furthermore, in some embodiments, this invention can also be implemented as a computer program product contained in one or more computer-readable media, which includes computer-readable program code.

[0116] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. A method for collaborative resource slicing, characterized in that, The method includes: The slice controller distributes the slice configuration information, resource load thresholds, and forwarding decision rules of each SRv6 slice to the head node, intermediate nodes, and tail node. When the head node receives a service forwarding request, it collects the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs, encapsulates the slice identifier, the first real-time resource status data and its collection timestamp into a TLV field and embeds it into the SRH header of the SRv6 message, and forwards the SRv6 message to the intermediate node. The intermediate node receives the SRv6 packet and parses the TLV field. Based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node, and the resource load threshold, it determines the slice load status and adjusts the forwarding path of the SRv6 packet based on the slice load status and the forwarding decision rule. The tail node receives the SRv6 message and parses the TLV field, and adjusts the quality of service of the SRv6 slice based on the end-to-end resource status data.

2. The method for collaborative management of sliced ​​resources according to claim 1, characterized in that, The method further includes: The tail node summarizes the full-link resource status data and reports it to the slice controller; The slice controller performs global optimization and adjustment of the slice configuration information and resource load threshold of each SRv6 slice based on the full-link resource status data.

3. The method for collaborative management of sliced ​​resources according to claim 1, characterized in that, The first real-time resource status data and the second real-time resource status data include bandwidth utilization, CPU utilization, and cache utilization; the slice configuration information includes the slice identifier and SID list, the SID list includes a default SID list and a backup SID list, the default SID list corresponds to the default forwarding path of the SRv6 packet, and the backup SID list corresponds to the backup forwarding path of the SRv6 packet.

4. The method for collaborative management of sliced ​​resources according to claim 3, characterized in that, The step of determining the slice load status based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node, and the resource load threshold includes: The timeliness of the first real-time resource status data is verified based on the collection timestamp; When the first real-time resource status data passes the timeliness verification, the comprehensive load is determined based on the first real-time resource status data and the second real-time resource status data; The slice load status is determined based on the overall load and the resource load threshold.

5. The method for collaborative management of sliced ​​resources according to claim 4, characterized in that, The timeliness verification of the first real-time resource status data based on the collection timestamp includes: Determine whether the time difference between the collected timestamp and the current time is greater than a preset threshold; If the time difference is greater than the preset threshold, it is determined that the first real-time resource status data has failed the timeliness verification, the SRv6 message is discarded, and a packet loss alarm is sent to the slice controller. Otherwise, the first real-time resource status data is deemed to have passed the timeliness verification.

6. The method for collaborative management of sliced ​​resources according to claim 4, characterized in that, The step of determining the slice load status based on the overall load and the resource load threshold includes: Compare the overall load with its corresponding resource load threshold; If the overall load corresponding to any type of resource is greater than its corresponding resource load threshold, the slice load status is determined to be overloaded; otherwise, it is normal.

7. The method for collaborative management of sliced ​​resources according to claim 6, characterized in that, The adjustment of the forwarding path of the SRv6 packet based on the slice load state and the forwarding decision rule includes: If the slice load status is normal, the SRv6 packet is forwarded to the next hop node according to the default forwarding path based on the default SID list. If the slice load status is overloaded, the current forwarding path is switched to the backup forwarding path, and the SRv6 packet is forwarded to the next hop node based on the backup SID list.

8. The method for collaborative management of sliced ​​resources according to claim 1, characterized in that, The adjustment of the service quality of the SRv6 slice based on end-to-end resource status data includes: Verify the validity and completeness of the TLV field; If the verification is successful, the full-link resource load status of the SRv6 slice is identified based on the full-link resource status data, and the QoS processing strategy of the SRv6 slice is dynamically adjusted based on the full-link resource load status. The QoS processing strategy includes at least one of the following: service scheduling priority adjustment, bandwidth allocation ratio adjustment, cache scheduling mode adjustment, and service latency guarantee level adjustment. If the verification fails, the SRv6 message is discarded and a packet loss alarm is sent to the slice controller.

9. A slicing resource collaboration device, characterized in that, The device includes: The pre-configuration module is used by the slice controller to distribute the slice configuration information, resource load thresholds and forwarding decision rules of each SRv6 slice to the head node, intermediate node and tail node; The message generation module is used to collect the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs when the head node receives the service forwarding request, encapsulate the slice identifier, the first real-time resource status data and its collection timestamp into a TLV field and embed it into the SRH header of the SRv6 message, and forward the SRv6 message to the intermediate node. The resource coordination module is used for the intermediate node to receive the SRv6 packet and parse the TLV field, determine the slice load status based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node and the resource load threshold, and adjust the forwarding path of the SRv6 packet based on the slice load status and the forwarding decision rule. The message receiving module is used by the tail node to receive the SRv6 message and parse the TLV field, and adjust the quality of service of the SRv6 slice based on the end-to-end resource status data.

10. The slicing resource collaboration device according to claim 9, characterized in that, The device further includes a global optimization module; the global optimization module is used for: The tail node summarizes the full-link resource status data and reports it to the slice controller; The slice controller performs global optimization and adjustment of the slice configuration information and resource load threshold of each SRv6 slice based on the full-link resource status data.

11. A sliced ​​resource collaborative system, characterized in that, The system comprises a controller layer, a head node layer, an intermediate node layer, and a tail node layer; wherein: The controller layer is equipped with a slice controller, which is used to distribute the slice configuration information, resource load threshold and forwarding decision rules of each SRv6 slice to the head node, intermediate node and tail node. The head node layer is deployed with a head node. When a service forwarding request is received, the head node is used to collect the first real-time resource status data of the SRv6 slice to which the service forwarding request belongs, encapsulate the slice identifier, the first real-time resource status data and its collection timestamp into a TLV field and embed it into the SRH header of the SRv6 message, and forward the SRv6 message to the intermediate node. The intermediate node layer is deployed with at least one intermediate node. The intermediate node is used to receive the SRv6 packet and parse the TLV field, determine the slice load status based on the first real-time resource status data, the second real-time resource status data of the SRv6 slice at the intermediate node and the resource load threshold, and adjust the forwarding path of the SRv6 packet based on the slice load status and the forwarding decision rule. The tail node layer is deployed with tail nodes, which are used to receive the SRv6 messages and parse the TLV field, and adjust the quality of service of the SRv6 slice based on the end-to-end resource status data.

12. The slice resource collaborative system according to claim 11, characterized in that, The tail node is also used to summarize the end-to-end resource status data and report it to the slice controller; the slice controller is also used to perform global optimization and adjustment of the slice configuration information and resource load threshold of each SRv6 slice based on the end-to-end resource status data.

13. An electronic device, characterized in that, include: processor; Memory for storing the executable instructions of the processor; The processor is configured to execute the instructions to implement the slice resource collaboration method as described in any one of claims 1 to 8.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the slice resource collaboration method according to any one of claims 1 to 8.

Images