Srv6 source address, network slice configuration management method and system based on srv6 source address

Abstract

The present application relates to the technical field of communication, and especially relates to a SRv6 source address, a network slice configuration management method and system based on the SRv6 source address. The SRv6 source address comprises, from front to back, a slice prefix field, a node identification field, a padding field, a slice channel bandwidth field, a strict mode flag field, a slice channel enable bit flag field and a slice instance field; wherein each slice instance is configured or not configured with a slice channel bandwidth value, and when configured, the slice channel bandwidth value is written into the slice channel bandwidth field; the strict mode flag field is located at the 32nd bit from the end of the SRv6 source address, the slice channel enable bit flag field is located at the 31st bit from the end of the SRv6 source address, and the slice instance field is located at the last 30 bits of the SRv6 source address. The present application realizes full-link slice channel deployment by enabling slice channel deployment and configuring bandwidth at a head node, solves the problem of slice layering of the head node for the message, and avoids message discarding caused by missing configuration of the intermediate node.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to an SRv6 source address, a network slice configuration management method and system based on the SRv6 source address. Background Technology

[0002] SRv6 source address network slicing currently deploys slice source addresses in the header node by assembling the matching slice instance ID and a strict match flag into the slice source address using either BE or TE methods. The assembled source address is then encapsulated in the Source Address field of the IPv6 header. (See [link to relevant documentation]). Figure 1 .

[0003] During slice forwarding at the head node, the destination address in the IPv6 packet header is searched for in the FIB forwarding table. Under the found egress interface, the slice channel configuration is matched based on the slice instance ID. If no slice channel is found and there is no associated slice forwarding port, the packet is discarded in strict mode; in non-strict mode, it is forwarded from the egress interface according to the normal SRv6 packet forwarding mode. At the intermediate Endpoint node, the slice source address carried in the received SRv6 packet is matched with the locally configured slice source address according to the slice prefix length. If a match is found, the slice interface is searched for and forwarded according to the above process; otherwise, it is forwarded as a normal SRv6 packet. Figure 2 .

[0004] SRv6 source address network slice forwarding process: When a slice source address is matched on an intermediate node, it indicates that the user's destination intends to use the slice channel for forwarding. However, if the interface lacks slice configuration or the slice channel is not in effect, the slice channel will not be used for forwarding regardless of whether it is in strict matching mode or non-strict matching mode. For example, in the following scenarios: {--PE1—PE2—PE3--} (1) PE1 is deployed as the headend to deploy network slices and generates Source Address: 2001:db8::8000::1, which means that the slice instance ID is 1 and is in strict matching mode.

[0005] (2) PE1 creates an SRv6 TE Policy tunnel, encapsulates the SRv6 message, and encapsulates the source address in the SourceAddress field.

[0006] (3) After the packet is forwarded to PE2, PE2 has a local configuration of network-slice prefix 2001::db8::100slice-identifier-length 60. It matches the source address in the packet according to the 60-bit length and believes that it needs to be forwarded through the slice channel. However, there is no slice channel under the outgoing interface Ethernet0 / 0 / 1 found according to the destination address, so the packet is discarded according to the strict matching mode.

[0007] Therefore, there is an urgent need to propose a method for forwarding sliced ​​packets by deploying sliced ​​packets at the headend and dynamically deploying sliced ​​channels at path nodes. This method can dynamically deploy sliced ​​channels for forwarding sliced ​​packets even if no sliced ​​channel is configured on the node, thus satisfying the network slice configuration management method of layering packet slices at the headend. Summary of the Invention

[0008] The purpose of this invention is to provide an SRv6 source address-based network slice configuration management method and system. By deploying slice packets at the headend for forwarding via slice channels and dynamically deploying slice channels at path nodes, this method solves the problem of head nodes wanting to layer packet slices, improves the flexibility and reliability of network slice forwarding, avoids packet drop due to missing intermediate node configurations, and implements a user-selectable optimization strategy to prevent SRv6 source address network slices from using network slice channels when no matching slice channel is found.

[0009] To achieve the above objectives, the present invention adopts the following technical solution: In a first aspect, the present invention provides an SRv6 source address, which includes, from front to back, a slice prefix field, a node identifier field, a padding field, a slice channel bandwidth field, a strict mode flag field, a slice channel enable bit flag field, and a slice instance field; wherein, each slice instance is configured or not configured with a slice channel bandwidth value. When configured, the slice channel bandwidth value is written into the slice channel bandwidth field; when not configured, the slice channel bandwidth field is empty; the strict mode flag field is located at the 32nd bit from the end of the SRv6 source address, the slice channel enable bit flag field is located at the 31st bit from the end of the SRv6 source address, and the slice instance field is located at the last 30 bits of the SRv6 source address.

[0010] As one possible implementation, the total length of the slice prefix field, node identifier field, and padding field is 64 bits; The length of the slice channel bandwidth field is 32 bits; Both the strict mode flag field and the slice channel enable bit flag field are 1 bit long; The length of the slice instance field is 30 bits.

[0011] As one possible implementation, the slice channel bandwidth field ranges from 1Mbps to 4294967295Mbps, with a default value of 4294967295Mbps.

[0012] Secondly, this invention provides a method for dynamically deploying slice channels based on SRv6 source address network slices, comprising the following steps: The source address of the network slice is filled into the SRv6 source address to carry the slice information. During filling, the slice channel bandwidth value required by each slice instance is written into the slice channel bandwidth field. If the slice instance has no slice channel bandwidth value, the slice channel bandwidth field is empty. The slice channel enable bit flag field is set. At this time, when the strict mode flag field conflicts with the slice channel enable bit flag field, the strict matching mode is no longer specified. When forwarding network slices from the SRv6 source address, the specific steps include: S10. Determine whether the source address slice prefix configuration on the forwarding node can match the source address in the received SRv6 source address network slice; S11. If so, search for the slice channel. If found, forward the SRv6 source address network slice through the matched slice channel. If not found, if the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance and the slice instance is configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the configured bandwidth value of the slice instance, and the resources are independent and cannot be preempted. If the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance, but the slice instance is not configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the default bandwidth value of the slice channel, and the resources are independent and cannot be preempted. When the remaining bandwidth resources under the outgoing interface do not meet the requirements of the slice instance, create and deploy an independent interface queue for the slice channel according to the remaining bandwidth resources, and the resources are independent and cannot be preempted. S12. Otherwise, SRv6 source address network slice packets are forwarded as ordinary SRv6 packets.

[0013] As one possible implementation, a separate interface queue for slice channels can be dynamically deployed for slice instances in the following way: Deploy the FlexE interface on the forwarding node; The logical layer QoS of the forwarding node utilizes the bandwidth resources of the FlexE interface to request an independent interface queue under the FlexE interface.

[0014] As one possible implementation, the method further includes: After the head node dynamically deploys the slice channel independent interface queue for the SRv6 source address network slice, when the bandwidth resources of the slice channel independent interface queue under a certain forwarding node need to be adjusted from the preset value to the current expected value, the bandwidth resources of the slice channel independent interface queue are reconfigured manually. At this time, the bandwidth resources of the pre-configured slice channel independent interface queue under that forwarding node are cancelled.

[0015] As one possible implementation, intermediate nodes only need to configure the slice source address to match the source address in the SRv6 source address network slice. If the match is successful, the SRv6 source address network slice is forwarded. When configuring the SRv6 source address network slice dynamic deployment slice channel independent interface queue in the intermediate node, it will not actually take effect. That is, the configuration of the slice channel independent interface queue for dynamic deployment of SRv6 source address network slice in the head node shall prevail.

[0016] Thirdly, the present invention provides a system for dynamically deploying slice channels for network slices based on SRv6 source addresses, including a head node and intermediate nodes; wherein, the head node is an SRv6 source address, the source address of the network slice is filled into the SRv6 source address to carry slice information, the slice channel bandwidth value required by each slice instance is written into the slice channel bandwidth field, if the slice instance has no slice channel bandwidth value, the slice channel bandwidth field is empty; the slice channel enable bit flag field is set, at this time, when the strict mode flag field conflicts with the slice channel enable bit flag field, the strict matching mode is no longer specified; Intermediate nodes, when used for SRv6 source address network slice forwarding, specifically include: S10. Determine whether the source address slice prefix configuration on the forwarding node can match the source address in the received SRv6 source address network slice; S11. If so, search for the slice channel. If found, forward the SRv6 source address network slice through the matched slice channel. If not found, if the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance and the slice instance is configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the configured bandwidth value of the slice instance, and the resources are independent and cannot be preempted. If the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance, but the slice instance is not configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the default bandwidth value of the slice channel, and the resources are independent and cannot be preempted. When the remaining bandwidth resources under the outgoing interface do not meet the requirements of the slice instance, create and deploy an independent interface queue for the slice channel according to the remaining bandwidth resources, and the resources are independent and cannot be preempted. S12. Otherwise, SRv6 source address network slice packets are forwarded as ordinary SRv6 packets.

[0017] Compared with the prior art, the beneficial effects of the present invention are as follows: 1. The SRv6 source address proposed in this invention includes, from front to back, a slice prefix field, a node identifier field, a padding field, a slice channel bandwidth field, a strict mode flag field, a slice channel enable bit flag field, and a slice instance field; it enables centralized deployment of slice channels, and by enabling slice channel deployment and configuring bandwidth at the head node, and carrying relevant information in the packet, it achieves full-link slice channel deployment, avoiding deployment errors of slice channels at intermediate nodes, and improving the flexibility and reliability of network slice forwarding.

[0018] 2. The present invention proposes a method for dynamically deploying slice channels based on SRv6 source address network slices. This method involves filling the source address of the network slice into the SRv6 source address to carry slice information. During filling, the slice channel bandwidth value required by each slice instance is written into the slice channel bandwidth field. If a slice instance has no slice channel bandwidth value, the slice channel bandwidth field is empty. The slice channel enable bit flag field is set. In this case, when the strict mode flag field conflicts with the slice channel enable bit flag field, the strict matching mode is no longer specified. This avoids packet loss due to missing intermediate node configurations.

[0019] 3. This invention proposes a system for dynamically deploying slice channels based on SRv6 source address network slices. By designing an SRv6 source address structure including a slice prefix field, node identifier field, padding field, slice channel bandwidth field, strict mode flag field, slice channel enable bit flag field, and slice instance field, it achieves unified deployment of slice channels by re-planning and utilizing slice source addresses, sacrificing 1 bit of the slice instance value, and limiting the matching length of slice source addresses. It makes fuller use of the slice source address structure and, combined with the mechanism of dynamically deploying independent interface queues for slice channels, can still create independent queues based on remaining bandwidth resources even when intermediate nodes are not configured with slice channels, avoiding packet drop due to configuration deficiencies, thereby improving the flexibility and reliability of network slicing. Attached Figure Description

[0020] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this invention, illustrate exemplary embodiments of the invention and are used to explain the invention, but do not constitute an undue limitation of the invention. In the drawings: Figure 1 This is a schematic diagram illustrating the current structure of the SRv6 source address as proposed in an embodiment of the present invention; Figure 2 This is a flowchart of the current SRv6 source address network slice forwarding process proposed in an embodiment of the present invention; Figure 3 This is a schematic diagram illustrating the source address format structure of the solution proposed in this embodiment of the invention; Figure 4This is a flowchart illustrating the slicing process of the solution proposed in this embodiment of the invention; Figure 5 This is a schematic diagram illustrating the new SRv6 source address field proposed in an embodiment of the present invention. Detailed Implementation

[0021] To facilitate a clear description of the technical solutions in the embodiments of the present invention, the terms "first" and "second" are used to distinguish identical or similar items with essentially the same function and effect. For example, the first threshold and the second threshold are merely used to distinguish different thresholds and do not limit their order. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that the terms "first" and "second" are not necessarily different.

[0022] It should be noted that in this invention, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

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

[0024] In existing technologies, static SRv6 source address network slice forwarding relies on the head node pre-configuring slice channels. When the head node does not configure slice channels, packet dropping occurs in strict matching mode, while in non-strict matching mode, slice resource isolation cannot be guaranteed, and packets are forwarded as ordinary SRv6 packets. For example, after the head node generates a source address carrying slice instance values, if an intermediate node matches the slice source address but does not configure a slice channel, effective forwarding of slice packets cannot be achieved regardless of whether strict mode is enabled. To solve the above problems, the inventors discovered that missing slice channel configuration is the root cause of packet dropping. Traditional solutions require each node to pre-configure slice channels, but in actual network deployments, node configurations may be omitted or updated late. This leads to the question: can dynamic parameters be carried in the source address to enable intermediate nodes to automatically create slice channels based on real-time resources? Furthermore, how can the resource isolation of dynamic channels be ensured? Based on this, a technical approach was developed that uses the address field to carry slice channel bandwidth parameters and slice channel enable bits to trigger nodes to allocate independent queues on demand.

[0025] In a first aspect, the present invention provides an SRv6 source address, comprising, from front to back, a slice prefix field, a node identifier field, a padding field, a slice channel bandwidth field, a strict mode flag field, a slice channel enable bit flag field, and a slice instance field. Each slice instance may or may not have a slice channel bandwidth value configured. When configured, the slice channel bandwidth value is written to the slice channel bandwidth field; otherwise, the field is empty. The strict mode flag field is located at the 32nd bit from the end of the SRv6 source address, the slice channel enable bit flag field is located at the 31st bit from the end, and the slice instance field is located in the last 30 bits.

[0026] Specifically, the head node performs extended planning on the slice source address structure. The last 31 bits of the slice source address are reserved for the slice instance, and the 32nd bit from the end is used as a strict matching mode flag. One bit of the slice instance is sacrificed, and the 31st bit from the end is reserved as a dynamic planning slice channel enable bit flag. Simultaneously, another 32 bits are reserved before the last 32 bits to carry the bandwidth value of this slice instance. See the source address format for this scheme. Figure 3 .

[0027] Compared to existing technologies, traditional solutions rely on static configuration of slice channels on nodes, which cannot adapt to dynamic networking requirements. This solution extends the planning through the address field, enabling intermediate nodes to automatically create channels based on real-time resources. In existing technologies, if a slice channel cannot be found and there is no associated slice forwarding port, the packet is discarded in strict mode and forwarded as a normal SRv6 packet in non-strict mode. This solution solves this problem by separating the field position, supporting the creation of queues based on remaining resources and improving network resource utilization.

[0028] Through the above technical solution, this embodiment of the invention achieves dynamic deployment of intermediate node slice channels, eliminating dependence on pre-configuration. When outgoing interface resources are sufficient, independent bandwidth is allocated on demand; when resources are insufficient, queue capacity is adaptively adjusted to avoid packet drop due to configuration deficiencies. The field structure design ensures resource isolation between different slice instances, guaranteeing the quality of service for critical businesses.

[0029] As one possible implementation, the total length of the slice prefix field, node identifier field, and padding field is 64 bits; the length of the slice channel bandwidth field is 32 bits; the length of the strict mode flag field and the slice channel enable bit flag field is 1 bit; and the length of the slice instance field is 30 bits.

[0030] The slice prefix field, node identifier field, and padding field are defined with a total length of 64 bits. Specifically, they can be implemented using the first 64 bits of the IPv6 network prefix to ensure compatibility with existing IPv6 address structures. The slice channel bandwidth field is defined with a length of 32 bits, and can be written as an unsigned integer, supporting precise representation of bandwidth ranges from 1 Mbps to 4,294,967,295 Mbps. The strict mode flag field and the slice channel enable bit flag field are both defined with a length of 1 bit, and can be implemented using binary bit status marking, controlling the logical switch between strict matching mode and slice channel enable using a single bit. The slice instance field is defined with a length of 30 bits, and can be implemented using segmented encoding to assign a unique identifier to each slice instance, supporting the independent identification requirements of large-scale slice instances.

[0031] Specifically, by limiting the total length of the slice prefix, node identifier, and padding fields to 64 bits, the forwarding node can directly comply with the standardized processing flow of IPv6 network prefixes when resolving SRv6 source addresses. The 32-bit length of the slice channel bandwidth field allows bandwidth values ​​to be written precisely as unsigned integers, avoiding bandwidth truncation or overflow due to insufficient field length. The 1-bit length setting for the strict mode flag and slice channel enable flag simplifies the control logic judgment process of the forwarding node; only a single bit needs to be read to determine whether to enable strict matching mode or slice channel functionality. The 30-bit length of the slice instance field provides ample identification space, supporting the forwarding node in accurately distinguishing the independent resource requirements of different slice instances when dynamically deploying slice channels.

[0032] Compared to existing technologies, static SRv6 source addresses do not explicitly define the bit length of each field, which can lead to resource allocation errors by forwarding nodes when processing slice channel bandwidth due to field length mismatches. For example, in existing technologies, insufficient bandwidth field length may fail to cover high-bandwidth demand scenarios, while this solution uses a 32-bit bandwidth field to precisely quantify resource requirements, avoiding bandwidth truncation. Furthermore, existing technologies have limited slice instance identifier space, which can lead to identifier conflicts due to a surge in the number of instances, while this solution's 30-bit instance field supports unique identifiers for over a billion slice instances, meeting the needs of large-scale network slice deployments.

[0033] Through the above technical solution, this invention addresses the problem of inaccurate resource allocation caused by ambiguous field lengths in SRv6 source addresses. By standardizing field length definitions, it ensures that forwarding nodes can accurately parse slice channel bandwidth values, avoiding resource allocation errors caused by insufficient or redundant field lengths. Simultaneously, strict bit length constraints simplify the processing logic of forwarding nodes and improve the efficiency of dynamically deploying slice channels. Sufficient identifier space in the slice instance field further supports the large-scale expansion needs of network slices, avoiding identifier conflicts or resource allocation failures caused by an increase in the number of instances.

[0034] As one possible implementation, the slice channel bandwidth field ranges from 1Mbps to 4294967295Mbps, with a default value of 4294967295Mbps.

[0035] The range of the slice channel bandwidth field refers to the upper and lower limits of the bandwidth parameter that can be written to this field. Specifically, it can be implemented using a 32-bit unsigned integer value range. The lower limit of 1Mbps is used to avoid invalid zero-bandwidth configurations, and the upper limit of 4294967295Mbps is used to match the maximum theoretical bandwidth capacity of the physical interface. The default value refers to the value automatically filled when the slice instance has not explicitly configured bandwidth parameters. This can be implemented using a preset static constant, set to the upper limit of 4294967295Mbps, to trigger the maximum bandwidth resource allocation logic in scenarios where parameters are missing.

[0036] Specifically, during the dynamic deployment of slice channels, when a slice instance does not carry explicit bandwidth parameters, the slice channel bandwidth field is automatically filled with the default value of 4294967295Mbps. This allows forwarding nodes to create independent interface queues based on the maximum available bandwidth when the remaining bandwidth resources of the outgoing interface meet the requirements. When a slice instance carries explicit bandwidth parameters, these parameters are limited to the range of 1Mbps to 4294967295Mbps to prevent queue creation failure due to exceeding the physical interface's capacity. Through this mechanism, even when bandwidth parameters are missing or misconfigured, the system can still complete resource allocation decisions based on default values, ensuring the continuity of the dynamic deployment process of slice channels.

[0037] Compared to existing technologies, traditional solutions cannot generate effective slice channel configurations when bandwidth values ​​are not configured, leading to interruptions in the dynamic deployment process or requiring manual intervention. This solution, by predefining bandwidth ranges and default values, allows the system to make autonomous decisions when bandwidth parameters are missing, avoiding resource allocation failures caused by incomplete configurations. Furthermore, upper limit constraints eliminate the impact of invalid bandwidth configurations on physical interfaces.

[0038] Through the above technical solution, the embodiments of the present invention solve the problem of interruption of resource allocation logic caused by the lack of configured bandwidth parameters during the dynamic deployment of network slices, and ensure that the system can still complete the creation of independent queues based on the maximum bandwidth value in the scenario of missing parameters, thus maintaining the dynamic deployment capability of slice channels.

[0039] Secondly, this invention provides a method for dynamically deploying slice channels based on SRv6 source address network slices, comprising the following steps: The source address of the network slice is filled into the SRv6 source address to carry the slice information. During filling, the slice channel bandwidth value required by each slice instance is written into the slice channel bandwidth field. If the slice instance has no slice channel bandwidth value, the slice channel bandwidth field is empty. The slice channel enable bit flag field is set. At this time, when the strict mode flag field conflicts with the slice channel enable bit flag field, the strict matching mode is no longer specified. For the SRv6 source address network slice forwarding process, please refer to [link / reference]. Figure 4 Specifically, it includes: S10. Determine whether the source address slice prefix configuration on the forwarding node can match the source address in the received SRv6 source address network slice; S11. If so, search for the slice channel. If found, forward the SRv6 source address network slice through the matched slice channel. If not found, if the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance and the slice instance is configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the configured bandwidth value of the slice instance, and the resources are independent and cannot be preempted. If the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance, but the slice instance is not configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the default bandwidth value of the slice channel, and the resources are independent and cannot be preempted. When the remaining bandwidth resources under the outgoing interface do not meet the requirements of the slice instance, create and deploy an independent interface queue for the slice channel according to the remaining bandwidth resources, and the resources are independent and cannot be preempted. S12. Otherwise, SRv6 source address network slice packets are forwarded as ordinary SRv6 packets.

[0040] Setting the slice channel enable bit flag field activates the field, which can be achieved by setting the binary bit to 1. This instructs the forwarding node to execute dynamic channel deployment logic. Dynamically deploying a slice channel's independent interface queue automatically creates a dedicated queue based on remaining bandwidth resources when the interface is not pre-configured with slice channels. This can be implemented using the bandwidth allocation mechanism of the FlexE interface, ensuring that queue resources are independent and cannot be preempted by other services. An empty slice channel bandwidth field means that the field does not carry a specific value. This can be achieved by setting it to zero or retaining a specific encoding state. In this case, the forwarding node will use a predefined default bandwidth value for resource allocation.

[0041] Header Node Operation: When deploying source address slices, the head node can configure the required slice channel bandwidth value for each slice instance, ranging from 1 to 4294967295 Mbps. Simultaneously, by enabling dynamic slice channel deployment via the command `network-slice force tunnel`, the slice channel enable bit flag is set to 1 when assembling the source address, and the configured bandwidth value for that instance is filled into the bandwidth field. If not configured, the default value is 4294967295 Mbps. Configuring dynamic slice channel deployment conflicts with the strict matching mode; a strict matching mode cannot be specified after dynamically deploying a slice channel. For example, in the scenario above, if the head node enables dynamic deployment of the slice channel for slice-id 1 and specifies a slice channel bandwidth value of 2^31 = 2147483648 Mbps, the generated source address after assembly will be: 2001:db8::8000:0000:4000:0001.

[0042] Slice forwarding process: During slice forwarding, if a slice channel can be matched under the interface, forwarding is performed according to the existing slice channel. If no slice channel can be matched under the interface, and the slice channel enable bit flag in the packet is set, an independent interface queue resource is created for this slice instance under the interface. The bandwidth value is the bandwidth value carried by the source address in the packet, and the resource is independent and cannot be preempted. The packet is forwarded from this slice channel. If the remaining bandwidth resources under the interface cannot meet the slice requirements, an interface queue is created according to the remaining resources, and the packet is forwarded exclusively.

[0043] In the above scenario, PE2 has a configured slice: 2001:db8::200 slice-identifier-length 60, which matches the source address 2001:db8::8000:0000:4000:0001 in the packet. However, there is no slice channel on the outgoing interface Ethernet0 / 0 / 1. Therefore, an interface queue is created on Ethernet0 / 0 / 1 with a bandwidth of 2^31 = 2147483648 Mbps, exclusively using the bandwidth resource to forward slice packets. If a slice channel corresponding to slice instance 1 exists on Ethernet0 / 0 / 1 of PE2, it is forwarded according to the existing slice channel, ignoring the dynamically deployed slice channel information carried in the source address.

[0044] The configuration is as follows: PE1: / / Configure source address slicing [DeviceA] network slicing [DeviceA-network-slicing] slice-prefix mode / / Configures the slice mode to source address mode. [DeviceA-network-slicing] slice-id 1 [DeviceA-network-slicing-1] quit [DeviceA-network-slicing] slice-prefix ipv6 2001:db8:: slice-identifier-length 60 prefix-length 61 / / Configuring slices in TE [DeviceA] segment-routing [DeviceA-sr] srv6 [DeviceA-srv6] traffic-eng [DeviceA-srv6-te] srv6-policy p1 color 1 endpoint 3::3 [DeviceA-srv6-te-policy-p1] candidate-path preference 10 [DeviceA-srv6-te-policy-p1-cpath-10] slice-id 1 / / Configure to enable dynamic deployment of slice channels [DeviceA] network slicing [DeviceA-network-slicing] network-slice force tunnel / / Configure slice instance channel bandwidth value [DeviceA] network slicing [DeviceA-network-slicing] slice-id 1 [DeviceA-network-slicing-1] slice tunnel flex-channel 2147483648 PE2: / / Configure source address slicing for matching [DeviceA] network slicing [DeviceA-network-slicing] slice-prefix mode / / Configures the slice mode to source address mode. [DeviceA-network-slicing] slice-prefix ipv6 2001:db8::200 slice-identifier-length 60 prefix-length 61 Specifically, when a forwarding node receives an SRv6 source address carrying slice information, it first performs slice prefix matching verification. If the match is successful but no pre-configured slice channel is found, the system checks whether the remaining bandwidth of the interface meets the requirements: if the remaining bandwidth is sufficient and the slice instance is configured with a bandwidth value, an independent queue is created according to that value; if no bandwidth value is configured, the default value is used for allocation; if the remaining bandwidth is insufficient, a queue is created according to the actual remaining value; if the match is successful and a pre-configured slice channel is found, forwarding is performed from the slice channel. During this process, all newly created queues are marked as independent resource types, preventing other services from preempting them. If prefix matching fails, the regular SRv6 forwarding process is executed directly to avoid forwarding interruption due to slice processing.

[0045] Compared to existing technologies, which discard packets without a configured channel in strict matching mode, this method automatically creates dedicated channels within the limits of interface resources through a dynamic queue deployment mechanism, ensuring continuous forwarding of sliced ​​packets. Existing technologies rely on manual pre-configuration of sliced ​​channels, while this method achieves on-demand automatic deployment through bandwidth field parsing and dynamic resource allocation, reducing operational complexity.

[0046] Through the above technical solution, this invention addresses the problem of packet loss due to the lack of configured slice channels. While maintaining strict mode functionality, it ensures slice service continuity through a dynamic resource allocation mechanism. Even when outgoing interface bandwidth resources are insufficient, channels can still be created based on actual available resources, preventing service interruption. The non-preemptible nature of independent interface queues effectively isolates different slice instances, ensuring consistent service quality.

[0047] As one possible implementation, a separate interface queue for slice channels can be dynamically deployed for slice instances in the following way: Deploy the FlexE interface on the forwarding node; the logical layer QoS of the forwarding node utilizes the bandwidth resources of the FlexE interface to request an independent interface queue under the FlexE interface.

[0048] Forwarding relies on the FlexE interface: by deploying the FlexE interface, bandwidth can be flexibly allocated for different services. The FlexE interface refers to the physical and service interfaces based on the Flexible Ethernet protocol, which has the ability to divide physical layer bandwidth into multiple independent logical channels, providing physically isolated transmission resources for different slice instances.

[0049] FlexE Physical Interface: A physical interface that switches from an Ethernet interface to Flexible Ethernet mode. FlexE physical interfaces can be added to FlexE-Group interfaces; the bandwidth of a FlexE-Group interface is equal to the sum of the bandwidths of all FlexE physical interfaces.

[0050] FlexE Service Interface: A logical interface for flexibly specifying bandwidth. The bandwidth of the FlexE-Group interface can be allocated to the FlexE service interface on demand, thereby enabling different bandwidth allocations for different services.

[0051] Logical layer QoS refers to a resource scheduling mechanism based on quality of service policies. Specifically, it can be implemented through a software-defined network controller or a local policy engine. It is used to dynamically request and allocate independent queue resources for FlexE interfaces based on real-time bandwidth requirements. Logical layer QoS uses the bandwidth resources to request an independent interface queue under the interface. After reaching the transport layer, the FlexE interface allocates an independent bandwidth resource queue for the slice instance to use.

[0052] Adjusting independent interface queue resources: For example, all slice channels deployed through this technology have a bandwidth of 100M, but a user on a certain node may need to adjust the outgoing interface slice channel of this node to 200M. In this case, the user can manually configure the slice channel on this node, which will only cancel the original slice channel deployed on this node and replace it with the channel manually deployed by the user.

[0053] Specifically, when a forwarding node detects that a slice channel is not pre-configured, the physical layer bandwidth partitioning function of the FlexE interface is activated, dividing the available bandwidth into multiple independent logical channels. The logical layer QoS requests an independent queue for the corresponding bandwidth from the FlexE interface based on the bandwidth requirements of the slice instance, which can be a value within the range of 1Mbps to 4294967295Mbps or a default value. This queue implements resource isolation at the interface level, ensuring that the transmission resources of different slice instances do not preempt each other. For example, when a slice instance needs to dynamically deploy slice channels, the FlexE interface can allocate time slot resources matching the demand, and the logical layer QoS will create an independent queue based on these resources and bind it to the slice instance, achieving hard isolation and independent scheduling of bandwidth.

[0054] Compared to existing technologies, traditional solutions rely on pre-configured sliced ​​channels, which can only drop packets or forward them as ordinary packets when forwarding nodes lack configuration. This solution, through the collaboration of the FlexE interface and logical layer QoS, directly creates independent queues based on physical layer resource segmentation and logical layer dynamic scheduling in scenarios without pre-configuration, thus avoiding service interruptions caused by configuration deficiencies.

[0055] Through the above technical solution, this embodiment of the invention enables forwarding nodes to dynamically deploy independent interface queues on demand even without pre-configured slice channels, solving the problem of slice packet forwarding failure caused by unallocated resources. By using the physical isolation of the FlexE interface and the dynamic resource allocation of the logical layer QoS, the bandwidth exclusivity of slice instances is guaranteed, ensuring that service quality is not affected by other service traffic.

[0056] As one possible implementation, it also includes: after the head node dynamically deploys the slice channel independent interface queue for the SRv6 source address network slice, when the bandwidth resources of the slice channel independent interface queue under a certain forwarding node need to be adjusted from the preset value to the current expected value, the bandwidth resources of the slice channel independent interface queue are reconfigured manually. At this time, the bandwidth resources of the pre-configured slice channel independent interface queue under that forwarding node are cancelled.

[0057] Manual configuration refers to modifying network device parameters manually. This can be achieved by entering adjustment commands through a command-line interface or a graphical management platform. This method can avoid resource allocation errors caused by misjudgments in automatic algorithms.

[0058] Cancelling pre-configured bandwidth resources means releasing the bandwidth quota occupied by the original slice channel independent interface queue. Specifically, this can be achieved by clearing the original queue configuration and re-applying for resources. This method ensures that the newly configured bandwidth value completely replaces the old value, avoiding resource residue.

[0059] Specifically, when the independent interface queue of the slice channel under the forwarding node needs to be adjusted from the initial preset bandwidth to the current service requirement, the operator inputs the new bandwidth parameters through the device management interface. After receiving the instruction, the system first unbinds the original queue from the physical port, then reallocates the independent interface queue according to the new parameters, and associates the adjusted bandwidth resources with the outgoing interface. During this process, the resources occupied by the original queue are completely released, and the new queue establishes an independent, non-preemptible transmission channel based on the updated bandwidth value.

[0060] Compared to existing technologies, the bandwidth resources of sliced ​​channels in current solutions cannot be dynamically adjusted after initial deployment, leading to resource waste or performance bottlenecks when preset values ​​do not match actual needs. This solution introduces a manual configuration mechanism that allows bandwidth resources to be flexibly adjusted according to changes in business requirements. Simultaneously, by clearing existing configurations, it ensures the accuracy of resource allocation, thus resolving the issue of resource fixation.

[0061] Through the above technical solution, this embodiment of the invention achieves the ability to dynamically adjust the bandwidth resources of the independent interface queue of the slice channel. It can quickly adapt to new bandwidth requirements when business needs change, avoiding low resource utilization or insufficient transmission performance caused by unreasonable preset values. At the same time, manual configuration ensures the controllability of the adjustment process, preventing resource allocation fluctuations that may be caused by automatic algorithms and maintaining the stability of network transmission.

[0062] As one possible implementation, intermediate nodes only need to configure the slice source address to match the source address in the SRv6 source address network slice. If the match is successful, the SRv6 source address network slice is forwarded. When configuring the SRv6 source address network slice dynamic deployment slice channel independent interface queue in the intermediate node, it will not actually take effect. That is, the configuration of the slice channel independent interface queue for dynamic deployment of SRv6 source address network slice in the head node shall prevail.

[0063] Slice source address matching refers to the intermediate node comparing the bit length of the pre-stored slice source address prefix with the source address in the packet. This can be implemented using an address prefix mask matching algorithm to ensure that the intermediate node only performs basic address verification. Dynamic deployment of slice channel configuration not taking effect means that the intermediate node's configuration operations for the slice channel's independent interface queue are logically isolated. This can be achieved through a hierarchical permission configuration mechanism, allowing the intermediate node's queue configuration commands to be intercepted or ignored in the system kernel.

[0064] Specifically, upon receiving an SRv6 network slice packet, the intermediate node first extracts the packet's source address field and matches it with the locally configured slice source address prefix. If a match is successful, the intermediate node only performs a forwarding path lookup operation and does not trigger the creation or modification process of the local slice channel. When an intermediate node attempts to configure an independent interface queue for a slice channel, the system automatically identifies the node as a non-head node and refuses to perform queue bandwidth allocation operations. All slice channel deployment decisions are centrally controlled by the head node, and intermediate nodes directly use the queue resource parameters pre-established by the head node for forwarding. This mechanism eliminates the need for intermediate nodes to maintain complex slice channel status tables, relying solely on the queue configuration issued by the head node to complete packet forwarding.

[0065] Compared to existing technologies, current solutions require intermediate nodes to simultaneously perform address matching and slice channel configuration. For example, in the slice forwarding process, the PE2 node may drop packets in strict mode due to a lack of slice channel configuration on its outgoing interface. This solution eliminates the forwarding interruption problem caused by missing local configurations on intermediate nodes by separating the address matching function from the channel deployment permissions. Existing technologies rely on intermediate nodes independently maintaining slice channel resources, which can easily lead to configuration conflicts between multiple nodes. This solution, however, ensures the consistency of slice channel parameters throughout the entire path through centralized control by the head node.

[0066] Through the above technical solution, this invention addresses the problem of packet dropping caused by missing or ineffective slice channel configurations at intermediate nodes. Intermediate nodes only need to perform source address matching and verification, eliminating the need to handle complex channel deployment logic and reducing the risk of configuration errors. The head node centrally controls slice channel resource allocation, avoiding resource contention caused by conflicts between local intermediate node configurations and global policies. This mechanism ensures that packets can still be forwarded according to the head node's preset parameters even if a slice channel is not pre-configured at the intermediate node, improving the reliability of network slice forwarding.

[0067] Thirdly, the present invention provides a system for dynamically deploying slice channels for network slices based on SRv6 source addresses, including a head node and intermediate nodes; wherein, the head node is an SRv6 source address, the source address of the network slice is filled into the SRv6 source address to carry slice information, the slice channel bandwidth value required by each slice instance is written into the slice channel bandwidth field, if the slice instance has no slice channel bandwidth value, the slice channel bandwidth field is empty; the slice channel enable bit flag field is set, at this time, when the strict mode flag field conflicts with the slice channel enable bit flag field, the strict matching mode is no longer specified; Intermediate nodes, when used for SRv6 source address network slice forwarding, specifically include: S10. Determine whether the source address slice prefix configuration on the forwarding node can match the source address in the received SRv6 source address network slice; S11. If so, search for the slice channel. If found, forward the SRv6 source address network slice through the matched slice channel. If not found, if the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance and the slice instance is configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the configured bandwidth value of the slice instance, and the resources are independent and cannot be preempted. If the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance, but the slice instance is not configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the default bandwidth value of the slice channel, and the resources are independent and cannot be preempted. When the remaining bandwidth resources under the outgoing interface do not meet the requirements of the slice instance, create and deploy an independent interface queue for the slice channel according to the remaining bandwidth resources, and the resources are independent and cannot be preempted. S12. Otherwise, SRv6 source address network slice packets are forwarded as ordinary SRv6 packets.

[0068] The slice channel enable bit flag field is a control bit used to activate the dynamic deployment of slice channels by intermediate nodes. When set, it forces intermediate nodes to execute the dynamic creation logic of slice channels. This flag can be implemented by modifying the binary value of a specific bit in the SRv6 source address.

[0069] The conflict handling mechanism between the strict mode flag field and the slice channel enable bit flag field means that when both are set at the same time, the dynamic deployment slice channel logic is executed first. This mechanism is implemented through preset priority determination rules to ensure that the execution right of the dynamic deployment function is higher than that of the traditional strict mode.

[0070] The independent and non-preemptible resource characteristics of the independent interface queue mean that the bandwidth resources allocated to the slice instance are exclusive. This can be achieved through the physical layer isolation technology of the FlexE interface, ensuring the service quality of the slice channel.

[0071] The bandwidth allocation logic for dynamically deployed slice channel independent interface queues includes three processing modes: when there is sufficient remaining bandwidth, it is allocated according to the configured value or the default value; when there is insufficient bandwidth, it is allocated according to the actual remaining value. This logic is implemented in collaboration with the queue creation interface through a real-time bandwidth monitoring algorithm.

[0072] The slice channel enable bit flag field is a binary flag used to identify whether dynamic deployment of slice channels is enabled. Specifically, the dynamic deployment logic of slice channels in intermediate nodes can be triggered by setting the bit to 1 or 0. Setting this field makes intermediate nodes ignore strict mode conflicts and prioritize the dynamic resource allocation of slice channels.

[0073] The slice channel bandwidth field is a 32-bit field that stores the bandwidth parameters required by the slice instance. Specifically, the bandwidth value can be stored in a numerical data format. When this field is empty, the intermediate node performs resource allocation based on the default bandwidth value to ensure that slice instances without configured bandwidth can still obtain basic forwarding capabilities.

[0074] The strict mode flag field refers to the binary flag bits that control the packet forwarding policy. Specifically, it can be determined in conjunction with the slice channel enable bit to eliminate policy uncertainty caused by mode conflicts, so that intermediate nodes will prioritize dynamically deploying slice channels instead of dropping packets when channels are missing.

[0075] Independent interface queues refer to logically isolated bandwidth resources allocated to slice channels. Specifically, they can be implemented by dividing physical layer time slots or logical layer QoS queues using FlexE interfaces. The independent and non-preemptible nature of these resources ensures the transmission stability of slice channels.

[0076] Source address slice prefix configuration refers to the address prefix pre-set on the forwarding node to identify slice packets. It can be implemented through the IPv6 address prefix matching algorithm and is used to trigger the slice channel processing flow.

[0077] The slice channel independent interface queue refers to a dynamically created independent resource queue, which can be implemented through the bandwidth allocation technology of the FlexE interface to ensure that queue resources are not preempted by other services.

[0078] The default bandwidth of a slice channel refers to a pre-set bandwidth baseline value, such as 4294967295Mbps, which is used as the resource allocation baseline when bandwidth is not explicitly configured.

[0079] Independent and non-preemptible resources refer to isolating queue resources through logical layer QoS strategies, such as using hardware queue priority control mechanisms, to ensure the service quality of sliced ​​services.

[0080] Specifically, when constructing an SRv6 packet, the head node activates the dynamic processing capability of intermediate nodes by setting the slice channel enable bit flag field. Upon receiving a packet, the intermediate node first performs source address slice prefix matching; if the match fails, it executes the normal forwarding process. If a match is successful, and no pre-configured slice channel is found, an independent queue is dynamically created based on the remaining bandwidth resources of the outgoing interface: when the remaining bandwidth meets the instance requirements, a queue is created according to the configured value or default value; when the bandwidth is insufficient, a queue is created according to the actual remaining value. If a match is successful and a pre-configured slice channel is found, the packet is forwarded from that slice channel. A conflict handling mechanism ensures that when there is a conflict between strict mode and dynamically deployed slice channel functionality, the latter is prioritized, avoiding packet drop due to mode conflicts.

[0081] The head node embeds the bandwidth requirement and channel enable flag of the slice instance into the SRv6 source address, and the intermediate nodes identify the packet by parsing the slice prefix in the source address. When an intermediate node interface has no pre-configured slice channel, it dynamically creates an independent queue based on the remaining bandwidth resources of the interface: if the slice instance is configured with an explicit bandwidth value, resources are requested according to that value; if no bandwidth value is configured, the default value is used; if the remaining resources are insufficient, a queue is created according to the actual remaining value. This mechanism allows intermediate nodes to achieve slice packet forwarding without relying on pre-configured channels, through real-time resource assessment and queue creation. The normal SRv6 packet forwarding mode serves as an alternative path to ensure network compatibility.

[0082] Upon receiving a packet, the forwarding node first performs source address slice prefix matching. If the match is successful, it enters the slice channel processing flow: when the pre-configured channel does not exist, it checks whether the remaining bandwidth of the interface meets the requirements of the slice instance. For example, if the remaining bandwidth is greater than or equal to the configured value, an independent queue is created according to the configured value; if no bandwidth is configured, the default value is used; when the remaining bandwidth is insufficient, a queue is created according to the actual remaining value. All dynamic queues achieve resource isolation through bandwidth allocation of the FlexE interface to avoid resource preemption. If prefix matching fails, it is directly processed according to the normal SRV6 forwarding process to ensure network connectivity. This solution, through multi-level bandwidth detection and dynamic resource allocation, can still create independent queues based on real-time bandwidth status even when intermediate nodes have not pre-configured slice channels, avoiding packet drop due to missing static configurations.

[0083] Compared to existing technologies, current solutions discard packets directly when no slice channel is configured at intermediate nodes. This system, however, automatically creates channels through a dynamic deployment mechanism. For example, when no slice channel is configured on the PE2 node, it automatically creates an independent queue to forward packets based on the remaining interface bandwidth, avoiding service interruptions due to configuration deficiencies. Existing solutions rely on manual pre-configuration of slice channels, while this system achieves adaptive management of network resources through real-time bandwidth resource detection and dynamic queue allocation.

[0084] Existing solutions, when a slice channel configuration is missing at an intermediate node, directly discard packets in strict matching mode and switch to normal forwarding in non-strict mode, but this cannot guarantee the quality of service for slices. This solution dynamically deploys independent queues, creating isolated queues based on real-time bandwidth resources when a channel is missing, preventing packet drop and maintaining the bandwidth isolation characteristics of slice channels. For example, in a scenario where the PE2 node interface has no pre-configured channel, the existing solution discards packets due to strict mode, while this solution dynamically allocates queues based on the remaining bandwidth of the interface, ensuring that slice packets receive independent resource guarantees.

[0085] Through the above technical solution, this invention solves the problem of packet dropping due to unconfigured slice channels at intermediate nodes, and enables path nodes to automatically create slice channels. After deploying slice packets at the head node, intermediate nodes can dynamically establish forwarding channels based on real-time bandwidth resources without pre-configuration. An independent, non-preemptible resource mechanism ensures the quality of service (QoS) of the slice channels, while the normal packet forwarding mode maintains network compatibility, forming a complete dynamic resource allocation and forwarding guarantee system. For example, when the remaining bandwidth of the outgoing interface is 10Gbps and the slice instance requirement is 5Gbps, the system automatically allocates a 5Gbps independent queue; when the remaining bandwidth is only 3Gbps, a 3Gbps queue is allocated to continue forwarding, ensuring service continuity. The independent, non-preemptible resource mechanism guarantees the QoS of the slice channels while maintaining compatibility with the normal packet forwarding mode, constructing a layered and elastic network management system.

[0086] Although the invention has been described herein in conjunction with various embodiments, those skilled in the art will understand and implement other variations of the disclosed embodiments by reviewing the accompanying drawings, disclosure, and other materials. In this specification, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple components. A single processor or other unit can implement several functions listed in the specification. While certain measures are described in different embodiments, this does not mean that these measures cannot be combined to produce good results.

[0087] Although the invention has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made therein without departing from the spirit and scope of the invention. Accordingly, this specification and drawings are merely illustrative of the invention and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the invention. Clearly, those skilled in the art can make various alterations and modifications to the invention without departing from its spirit and scope. Thus, if such modifications and modifications fall within the scope of the invention and its equivalents, the invention is also intended to include such modifications and modifications.

Claims

1. A method for dynamically deploying network slice channels based on SRv6 source addresses, characterized in that, Includes the following steps: The source address of the network slice is filled into the SRv6 source address to carry the slice information; during filling, the slice channel bandwidth value required by each slice instance is written into the slice channel bandwidth field. If the slice instance has no slice channel bandwidth value, the slice channel bandwidth field is empty. When the slice channel enable bit flag field is set, a strict matching mode is no longer specified when the strict mode flag field conflicts with the slice channel enable bit flag field. The SRv6 source address includes a slice prefix field, a node identifier field, a padding field, a slice channel bandwidth field, a strict mode flag field, a slice channel enable bit flag field, and a slice instance field. Each slice instance may or may not have a slice channel bandwidth value configured. If configured, the slice channel bandwidth value is written to the slice channel bandwidth field; otherwise, the slice channel bandwidth field is empty. The strict mode flag field is located at the 32nd bit from the end of the SRv6 source address, the slice channel enable bit flag field is located at the 31st bit from the end of the SRv6 source address, and the slice instance field is located at the last 30 bits of the SRv6 source address. The total length of the slice prefix field, node identifier field, and padding field is 64 bits; the slice channel bandwidth field is 32 bits long; the strict mode flag field and the slice channel enable bit flag field are both 1 bit long; and the slice instance field is 30 bits long. When forwarding network slices from the SRv6 source address, the specific steps include: S10. Determine whether the source address slice prefix configuration on the forwarding node can match the source address in the received SRv6 source address network slice; S11. If so, search for the slice channel. If found, forward the SRv6 source address network slice through the matched slice channel. If not found, if the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance and the slice instance is configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the configured bandwidth value of the slice instance, and the resources are independent and cannot be preempted. If the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance, but the slice instance is not configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the default bandwidth value of the slice channel, and the resources are independent and cannot be preempted. When the remaining bandwidth resources under the outgoing interface do not meet the requirements of the slice instance, create and deploy an independent interface queue for the slice channel according to the remaining bandwidth resources, and the resources are independent and cannot be preempted. S12. Otherwise, SRv6 source address network slice packets are forwarded as ordinary SRv6 packets.

2. The method for dynamically deploying network slice channels based on SRv6 source addresses according to claim 1, characterized in that, Dynamically deploy independent interface queues for slice channels to slice instances using the following method: Deploy the FlexE interface on the forwarding node; The logical layer QoS of the forwarding node utilizes the bandwidth resources of the FlexE interface to request an independent interface queue under the FlexE interface.

3. The method for dynamically deploying network slice channels based on SRv6 source addresses according to claim 1, characterized in that, The method further includes: After the head node dynamically deploys the slice channel independent interface queue for the SRv6 source address network slice, when the bandwidth resources of the slice channel independent interface queue under a certain forwarding node need to be adjusted from the preset value to the current expected value, the bandwidth resources of the slice channel independent interface queue are reconfigured manually. At this time, the bandwidth resources of the pre-configured slice channel independent interface queue under that forwarding node are cancelled.

4. The method for dynamically deploying network slice channels based on SRv6 source addresses according to any one of claims 1 to 3, characterized in that, Intermediate nodes only need to configure the slice source address, which is used to match the source address in the SRv6 source address network slice. If the match is successful, the SRv6 source address network slice is forwarded. When configuring the SRv6 source address network slice dynamic deployment slice channel independent interface queue in the intermediate node, it will not actually take effect. That is, the configuration of the slice channel independent interface queue of the head node for the SRv6 source address network slice dynamic deployment shall prevail.

5. A network slice dynamic deployment slice channel system based on SRv6 source addresses, characterized in that, This includes a head node and intermediate nodes. The head node is the SRv6 source address. The source address of the network slice is filled into the SRv6 source address to carry slice information. The slice channel bandwidth value required by each slice instance is written into the slice channel bandwidth field. If a slice instance has no slice channel bandwidth value, the slice channel bandwidth field is empty. The slice channel enable bit flag field is set. In this case, when the strict mode flag field conflicts with the slice channel enable bit flag field, the strict matching mode is no longer specified. The SRv6 source address includes a slice prefix field, a node identifier field, a padding field, a slice channel bandwidth field, a strict mode flag field, a slice channel enable bit flag field, and a slice instance. Example fields; where each slice instance has either a configured or unconfigured slice channel bandwidth value. When configured, the slice channel bandwidth value is written to the slice channel bandwidth field; when not configured, the slice channel bandwidth field is empty. The strict mode flag field is located at the 32nd bit from the end of the SRv6 source address, the slice channel enable bit flag field is located at the 31st bit from the end of the SRv6 source address, and the slice instance field is located at the last 30 bits of the SRv6 source address. The total length of the slice prefix field, node identifier field, and padding field is 64 bits; the length of the slice channel bandwidth field is 32 bits; the length of the strict mode flag field and the slice channel enable bit flag field is 1 bit each; the length of the slice instance field is 30 bits. Intermediate nodes, when used for SRv6 source address network slice forwarding, specifically include: S10. Determine whether the source address slice prefix configuration on the forwarding node can match the source address in the received SRv6 source address network slice; S11. If so, search for the slice channel. If found, forward the SRv6 source address network slice through the matched slice channel. If not found, if the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance and the slice instance is configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the configured bandwidth value of the slice instance, and the resources are independent and cannot be preempted. If the remaining bandwidth resources under the outgoing interface meet the requirements of the slice instance, but the slice instance is not configured with a bandwidth value, dynamically deploy an independent interface queue for the slice channel based on the default bandwidth value of the slice channel, and the resources are independent and cannot be preempted. When the remaining bandwidth resources under the outgoing interface do not meet the requirements of the slice instance, create and deploy an independent interface queue for the slice channel according to the remaining bandwidth resources, and the resources are independent and cannot be preempted. S12. Otherwise, SRv6 source address network slice packets are forwarded as ordinary SRv6 packets.

Images