Forwarding method, configuration method and device of segment routing message based on IPV6

By carrying the slice ID in the IPv6 message and combining the FlexAlgo ID to form a Resource ID, combining the control plane and the forwarding plane, the problem of insufficient resource isolation and limited slice count in the 5G network slicing field is solved, and the user's business-level slice is realized Resource isolation and performance optimization.

CN115242713BActive Publication Date: 2024-11-08CHINA MOBILE COMM LTD RES INST +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110436526.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-04-22
Publication Date
2024-11-08
Estimated Expiration
2041-04-22

AI Technical Summary

Technical Problem

FlexAlgo has problems such as insufficient resource isolation, limited number of slices and degraded system performance in the 5G network slicing field, which is difficult to meet the needs of complex scenarios.

Method used

By carrying the slice ID in the FlowLabel field of the IPv6 message and forming the Resource ID with the FlexAlgo ID, the network slice function is realized, the SDN controller or network management system is used to plan and configure the slice ID, and the user service is realized by combining the control plane and the forwarding plane. Level of slicing resource isolation.

Benefits of technology

It realizes resource isolation under the same physical interface, increases the number of slices, reduces the impact of system performance, supports more slice scenarios, and solves the problem of small range of FlexAlgo ID and slice ID.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115242713B_ABST
    Figure CN115242713B_ABST
Patent Text Reader

Abstract

A forwarding method, configuration method and device for segment routing messages based on IPV6, the forwarding method comprising: when the forwarding device forwards the first SRv6 message of the first service, the first slice ID is parsed from the IPv6 header of the first SRv6 message, and the segment routing SR forwarding table entry is searched to determine the first physical output interface and the first flexible algorithm identifier FA ID corresponding to the first SRv6 message; according to the first physical output interface, the first FA ID and the first slice ID, the locally maintained slice forwarding table is searched to determine the first resource interface corresponding to the first SRv6 message; the first SRv6 message is sent through the first resource interface; wherein the slice forwarding table maintains the correspondence between the physical output interface, FA ID, slice ID and resource interface. The present invention can realize resource isolation under the same physical interface, and has little impact on system performance. In addition, it solves the problem of small range of FlexAlgo ID and slice ID, and increases the actual number of slices.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of data forwarding, and in particular to a forwarding method, a configuration method and a device for an IPv6-based segment routing message. Background Art

[0002] Network slicing is a key technology for fifth-generation mobile communications (5G). It manages network data flow similar to traffic management. Essentially, it logically divides the existing physical network into multiple virtual networks of varying types. These networks are divided based on user service requirements, such as latency, bandwidth, and reliability, to address complex and ever-changing application scenarios. Through slicing, mobile network operators can categorize users into different types, each with different service requirements, and manage the slice types and services each user is eligible for based on service-level agreements (SLAs).

[0003] The 5G bearer network is part of the 5G end-to-end service path. Bearer network slicing virtualizes network topology resources (such as links, nodes, ports, and internal network element resources) to create multiple logical virtual transmission subnets within the transmission hardware. These virtual transmission subnets have independent management, control, and forwarding planes, independently supporting various services and achieving isolation between them.

[0004] The Flexible Algorithm (FlexAlgo) extends the Interior Gateway Protocol (IGP) Segment Routing (SR) by assigning different Segment IDs (SIDs) to the same device, representing different FlexAlgo planes. Within each FlexAlgo plane, a triplet (MetricType, CalcType, and LinkColor) is combined to perform a Shortest Path First (SPF) calculation, forming an independent routing entry. FlexAlgo does not modify the forwarding mechanism and can inherit the current SR and IPv6-based Segment Routing (SRv6) forwarding mechanisms. In this article, FlexAlgo is sometimes abbreviated as FA. Summary of the Invention

[0005] At least one embodiment of the present invention provides an SRV6 message forwarding method, configuration method, terminal and network device, which can achieve slice resource isolation at the user service level.

[0006] According to one aspect of the present invention, at least one embodiment provides a method for forwarding IPv6-based segment routing (SRv6) packets, including:

[0007] When forwarding the first SRv6 packet of the first service, the forwarding device parses the first slice ID from the IPv6 header of the first SRv6 packet, and searches the segment routing SR forwarding table entry to determine the first physical outbound interface and the first flexible algorithm identifier FA ID corresponding to the first SRv6 packet;

[0008] Searching a locally maintained slice forwarding table according to the first physical outbound interface, the first FA ID, and the first slice ID to determine a first resource interface corresponding to the first SRv6 message;

[0009] Sending the first SRv6 message through the first resource interface;

[0010] Among them, the slice forwarding table maintains the correspondence between the physical output interface, FA ID, slice ID and resource interface.

[0011] In addition, according to at least one embodiment of the present invention, the forwarding device is a carrier backbone router P device of the first service. Before forwarding the first SRv6 message, the method further includes:

[0012] Receive configuration information of physical resources sent by the controller, where the configuration information of the physical resources includes a first physical outbound interface, a first FA ID, a first slice ID of the first service on the forwarding device, and physical resources of the first service configured on the first physical outbound interface, where the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice, respectively, allocated by the controller for the first service;

[0013] Associating the physical resources of the first service configured on the first physical outbound interface with the first resource interface under the physical outbound interface;

[0014] According to the first physical output interface, the first FA ID, the first slice ID and the first resource interface, the slice forwarding table is maintained, and the slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID and resource interface of each service.

[0015] In addition, according to at least one embodiment of the present invention, the forwarding device is a provider edge router PE of the first service. Before forwarding the first SRv6 packet, the method further includes:

[0016] Receive a first FA ID and a first slice ID sent by the controller, where the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice, respectively, allocated by the controller for the first service;

[0017] Maintaining the slice planning table according to the first VPN, the first FA ID, and the first slice ID to which the first service belongs, where the slice planning table records the correspondence between the FA ID, VPN ID, and slice ID of each service;

[0018] Receive configuration information of physical resources sent by the controller, where the configuration information of the physical resources includes a first physical outbound interface, a first FA ID, a first slice ID, and the physical resources of the first service configured on the first physical outbound interface of the first service on the forwarding device;

[0019] Associating the physical resources of the first service configured on the first physical outbound interface with the first resource interface under the physical outbound interface;

[0020] According to the first physical output interface, the first FA ID, the first slice ID and the first resource interface, a slice forwarding table is maintained, and the slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID and resource interface of each service.

[0021] In addition, according to at least one embodiment of the present invention, before forwarding the first SRv6 packet of the first service, the method further includes:

[0022] receiving a first message of a first service sent by a user edge CE device;

[0023] According to the first VPN to which the first service belongs, searching the slice planning table to obtain a first slice ID corresponding to the first VPN;

[0024] According to the SRv6 format, an SR header is encapsulated for the first message, and the first slice ID is added to the IPv6 header to generate the first SRv6 message.

[0025] Furthermore, according to at least one embodiment of the present invention, the present invention further comprises:

[0026] receiving first physical resource requirement information of the first service sent by the controller;

[0027] When maintaining the slice planning table, the first physical resource requirement information of the first business is also recorded in the slice planning table.

[0028] In addition, according to at least one embodiment of the present invention, the configuration information of the physical resource further includes first physical resource requirement information of the first service and a resource ID of the first service, wherein the resource ID of the first service corresponds to the first slice ID under the first FA ID;

[0029] In addition, according to at least one embodiment of the present invention, the resource ID of the first service is obtained by concatenating the first FA ID and the first slice ID.

[0030] When maintaining the slice forwarding table, at least one of the resource ID and the first physical resource requirement information of the first service is also recorded in the slice forwarding table.

[0031] In addition, according to at least one embodiment of the present invention, the first slice ID is carried in a flow label FlowLabel field in an IPv6 header.

[0032] According to another aspect of the present invention, at least one embodiment provides a method for configuring an IPv6-based segment routing (SRv6) message, including:

[0033] The controller allocates a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane to the first service, and determines first physical resource requirement information of the first service;

[0034] The controller sends the first FA ID of the first FlexAlgo plane and the first slice ID of the first slice to the provider edge router PE device of the first service;

[0035] The controller configures the physical resources of the first service for the physical output interface of each forwarding device of the first service based on the first physical resource requirement information, and sends the configuration information of the physical resources to the forwarding device. The configuration information of the physical resources includes the physical output interface, the first FA ID, the first slice ID and the physical resources of the first service configured on the physical output interface. The forwarding device includes the PE device of the first service and the operator backbone router P device.

[0036] In addition, according to at least one embodiment of the present invention, the controller allocates a first FlexAlgo plane and a first slice under the first FlexAlgo plane to the first service, and determines first physical resource requirement information of the first service, specifically:

[0037] The controller allocates a first flexible algorithm FlexAlgo plane to the first service;

[0038] According to the service characteristics of the first service, a first slice under the first FlexAlgo plane is allocated to the first service, and first physical resource requirement information of the first service is determined, wherein the service characteristics include at least one of a virtual local area network VLAN, VPN and a differentiated service code point DSCP.

[0039] Furthermore, according to at least one embodiment of the present invention, the present invention further comprises:

[0040] The controller sends the first physical resource requirement information of the first service to the PE device of the first service.

[0041] Furthermore, according to at least one embodiment of the present invention, the present invention further comprises:

[0042] The controller generates a resource ID of the first service, wherein the resource ID of the first service corresponds to a first slice ID under the first FA ID;

[0043] The physical resource configuration information also includes first physical resource requirement information of the first service and a resource ID of the first service.

[0044] In addition, according to at least one embodiment of the present invention, the resource ID of the first service is obtained by concatenating the first FA ID and the first slice ID.

[0045] According to another aspect of the present invention, at least one embodiment provides a forwarding device, including:

[0046] a parsing module, configured to, when forwarding a first SRv6 packet of a first service, parse the first slice ID from the IPv6 header of the first SRv6 packet, and search a segment routing SR forwarding table entry to determine a first physical outbound interface and a first flexible algorithm identifier FA ID corresponding to the first SRv6 packet;

[0047] A search module, configured to search a locally maintained slice forwarding table according to the first physical outbound interface, the first FA ID, and the first slice ID, and determine the first resource interface corresponding to the first SRv6 message;

[0048] a forwarding module, configured to send the first SRv6 message through the first resource interface;

[0049] Among them, the slice forwarding table maintains the correspondence between the physical output interface, FA ID, slice ID and resource interface.

[0050] According to another aspect of the present invention, at least one embodiment provides a forwarding device, including a transceiver and a processor, wherein:

[0051] The processor is configured to, when forwarding a first SRv6 message of a first service, parse a first slice ID from an IPv6 header of the first SRv6 message, and search a segment routing SR forwarding table entry to determine a first physical outbound interface and a first flexible algorithm identifier FA ID corresponding to the first SRv6 message; search a locally maintained slice forwarding table according to the first physical outbound interface, the first FA ID, and the first slice ID to determine a first resource interface corresponding to the first SRv6 message;

[0052] The transceiver is configured to send the first SRv6 message through the first resource interface;

[0053] Among them, the slice forwarding table maintains the correspondence between the physical output interface, FA ID, slice ID and resource interface.

[0054] According to another aspect of the present invention, at least one embodiment provides a forwarding device, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program implements the steps of the method described above when executed by the processor.

[0055] According to another aspect of the present invention, at least one embodiment provides a controller, including:

[0056] A first configuration module is configured to: allocate a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane to a first service, determine first physical resource requirement information of the first service, and send a first FA ID of the first FlexAlgo plane and a first slice ID of the first slice to a provider edge router (PE) device of the first service;

[0057] The second configuration module is used to configure the physical resources of the first service for the physical output interface of each forwarding device of the first service according to the first physical resource requirement information, and send the configuration information of the physical resources to the forwarding device, wherein the configuration information of the physical resources includes the physical output interface, the first FA ID, the first slice ID and the physical resources of the first service configured on the physical output interface, and the forwarding device includes the PE device of the first service and the operator backbone router P device.

[0058] According to another aspect of the present invention, at least one embodiment provides a controller including a transceiver and a processor, wherein:

[0059] The processor is configured to control the allocation of a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane to a first service, and determine first physical resource requirement information of the first service; and, based on the first physical resource requirement information, configure physical resources of the first service for a physical outbound interface of each forwarding device of the first service;

[0060] The transceiver is used to send the first FA ID of the first FlexAlgo plane and the first slice ID of the first slice to the operator edge router PE device of the first service; and send the configuration information of the physical resources to the forwarding device, the configuration information of the physical resources includes the physical output interface, the first FA ID, the first slice ID and the physical resources of the first service configured on the physical output interface, and the forwarding device includes the PE device of the first service and the operator backbone router P device.

[0061] According to another aspect of the present invention, at least one embodiment provides a controller comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program implements the steps of the method described above when executed by the processor.

[0062] According to another aspect of the present invention, at least one embodiment provides a computer-readable storage medium having a program stored thereon. When the program is executed by a processor, the steps of the method described above are implemented.

[0063] Compared to the prior art, the forwarding method, configuration method, and device for IPV6-based segmented routing messages provided by the embodiments of the present invention associate slice IDs with physical link resources at the forwarding level, achieving resource isolation under the same physical interface. Furthermore, the forwarding plane adds a slice information lookup forwarding process, which does not involve other operations and has a minimal impact on system performance. Furthermore, the embodiments of the present invention combine the FA ID with the slice ID to obtain the resource ID that ultimately matches the physical resource, effectively resolving the issue of the limited range of FlexAlgo IDs and slice IDs and increasing the number of actual slices. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present invention. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:

[0065] Figure 1 A schematic diagram of FlexAlgo physical isolation;

[0066] Figure 2 A schematic diagram of FlexAlgo logical isolation;

[0067] Figure 3 A schematic diagram of the format of an IPv6 message;

[0068] Figure 4 This is a schematic diagram of an embodiment of the present invention using the flow label field of an IPv6 message to carry a slice ID;

[0069] Figure 5 A schematic diagram of slice ID planning provided by an embodiment of the present invention;

[0070] Figure 6 A flow chart of a method for forwarding an SRV6 message according to an embodiment of the present invention;

[0071] Figure 7 A flow chart of a method for configuring an SRV6 message according to an embodiment of the present invention;

[0072] Figure 8 This is an example diagram of the device processing process and forwarding layer message encapsulation in an embodiment of the present invention;

[0073] Figure 9 A schematic structural diagram of a forwarding device provided in an embodiment of the present invention;

[0074] Figure 10 Another structural diagram of a forwarding device provided in an embodiment of the present invention;

[0075] Figure 11 A schematic diagram of the structure of a controller provided in an embodiment of the present invention;

[0076] Figure 12 Another structural diagram of a controller provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0077] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present invention and to fully convey the scope of the present invention to those skilled in the art.

[0078] The terms "first", "second" etc. in the specification and claims of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable in appropriate circumstances, so that the embodiments of the present application described herein, for example, can be implemented in an order other than those illustrated or described herein. In addition, the terms "comprise" and "have" and any of their variations are intended to cover non-exclusive inclusions, for example, the process, method, system, product or equipment comprising a series of steps or units need not be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or that are intrinsic to these processes, methods, products or equipment. "And / or" in the specification and claims represents at least one of the connected objects.

[0079] FlexAlgo can divide the physical network into multiple virtual networks and use different virtual networks to achieve differentiated business demands. These virtual networks can be physically isolated, for example Figure 1 :Add different nodes or links to different FlexAlgo, FA 128 and FA 129 respectively, so as to form Figure 1 The virtual network shown in the right half can also be used to achieve logical "isolation", for example Figure 2 : Calculate the path based on delay, calculate the path based on IGP Metric value, calculate the path based on TEMetric value, so as to form the following Figure 2 The right half shows the virtual network. In this case, the two virtual networks share the physical link between device 3 and device 4. Figure 1 and Figure 2 Each rectangular block in the figure represents a forwarding device. Figure 1 and Figure 2 It includes devices 1 to 6.

[0080] When applying the FlexAlgo technology to the slicing field, the inventors discovered the following problems:

[0081] (1)FlexAlgo can usually only achieve Figure 1 The port level coarse-grained slicing functionality is shown. Figure 2 In the scenario shown, the same physical link is used in different logical topologies, and resources are shared, but true resource isolation is not achieved.

[0082] (2) The FlexAlgo extended control plane protocol requires independent address space planning for each slice and independent SPF calculation for each slice. The number of routes increases linearly with the number of slices, while convergence performance decreases linearly with the number of slices. Each slice consumes a large amount of resources and cannot support scenarios with a large number of slices.

[0083] (3) The maximum number of slices supported by FlexAlgo is 128 (the FA ID range is 128 to 255). Even without considering the system overhead, the number of slices supported by FlexAlgo is difficult to meet the actual needs of the existing network.

[0084] To address at least one of the above issues, an embodiment of the present invention provides a method for forwarding SRV6 packets, which implements network slicing by combining a control plane with a forwarding plane. The control plane uses FlexAlgo to implement coarse-grained port-level slicing and determine the physical path for traffic forwarding.

[0085] The embodiments of the present invention can utilize a software-defined network (SDN) controller or a network management system to plan and configure, allocate different network slices to different user services, and carry the slice ID information in the header of the IPv6 message, for example, in the flow label (FlowLabel) field of the IPv6 header. The forwarding device forwards according to the slice ID and FlexAlgo information, for example, obtains the corresponding Resource ID information based on the combination of the slice ID and FlexAlgo information, and matches the corresponding link resources, thereby ultimately realizing the user-level network slicing function.

[0086] In the embodiment of the present invention, the slice ID is carried in the IPv6 header. Figure 3 As shown in FIG, the FlowLabel field in the IPv6 message occupies 20 bits (bit) and is used to mark the message of a specific flow so as to distinguish different messages at the network layer. The FlowLabel field can be used for traffic load sharing. Preferably, the slice ID is carried in the FlowLabel field, that is, the slice ID is carried by using some bits of the FlowLabel field, which has the following advantages:

[0087] 1) Currently, the 20 bits specified by FlowLabel are not actually used in most chips. Therefore, a portion of the field can be divided to carry the slice ID. The specific field length can be determined based on the number of slices and the number of FlowLabel bits used in the chip. For example, if some chips currently use the lower 12 bits of FlowLabel, the upper 8 bits of FlowLabel can be used to carry the slice ID. Figure 4 An example of using the upper 8 bits of FlowLabel to carry the slice ID is given.

[0088] 2) Even if the device chip in the network uses all 20 bits of FlowLabel for load balancing, the embodiment of the present invention is forward compatible. Reducing the number of load balancing HASH bits only affects the degree of load balancing dispersion and reduces the traffic load balancing effect to a certain extent, but does not affect the actual traffic transmission and reception.

[0089] 3) The FlowLabel field in the IPv6 packet header has a hop-by-hop attribute, which not only meets the requirements of slice-by-hop processing, but also enables efficient parsing, avoiding the reduction of packet processing efficiency by adding a new slice ID.

[0090] In the embodiment of the present invention, an SDN controller or a network management system can globally plan a slice ID (Slice ID) within the same FA plane based on user service characteristics, such as virtual local area network (VLAN), virtual private network (VPN), and differentiated services code point (DSCP), and assign it to the corresponding user service. The Slice ID is carried in the FlowLabel field of the IPv6 packet header.

[0091] For example, Figure 2 The SliceIDs allocated to the two FA planes FA 128 and FA 129 are as follows: Figure 5 As shown, Figure 5 In this example, CE stands for Customer Edge. A1::1 and B1::1 correspond to two different FA planes (FA 128 and FA 129) on device 1. Similarly, A2::1 and B2::1 correspond to two different FA planes (FA 128 and FA 129) on device 2. A3::1 and B3::1 correspond to two different FA planes (FA 128 and FA 129) on device 3. A4::1 and B4::1 correspond to two different FA planes (FA 128 and FA 129) on device 4. Different VPN user services under FA 128 are assigned different Slice IDs, and different VPN users under FA 129 are assigned different Slice IDs. The Slice IDs assigned to FA 128 and FA 129 are independent and unrelated. That is, FA 128 and FA 129 may have the same Slice ID, but they correspond to different user services.

[0092] In the embodiment of the present invention, the FA ID and the Slice ID can be combined to form a final resource identifier (ResourceID), which is used to identify the actual link resource information on the forwarding device. As an example of the combination method, specifically:

[0093] Resource ID=FA ID<<8+Slice ID

[0094] The above formula indicates that the FA ID is shifted left by 8 bits and then concatenated with the Slice ID to obtain the Resource ID.

[0095] by Figure 5 For example, for the FA 128 plane, the Resource ID corresponding to VPN1 is 32769 (128<<8+1), the Resource ID corresponding to VPN2 is 32770 (128<<8+2), and the Resource ID corresponding to VPN3 is 32771 (128<<8+3).

[0096] For the FA 129 plane, the Resource ID corresponding to VPN4 is 33024 (129<<8+1), the Resource ID corresponding to VPN5 is 33025 (129<<8+2), and the Resource ID corresponding to VPN6 is 33026 (129<<8+3).

[0097] A link may belong to different FA planes at the same time. In this case, the links belonging to different FA planes need to allocate corresponding physical resources to each FA to ensure the physical resources for different FA traffic.

[0098] It should be noted that the resource ID of a service corresponds to the slice allocated to the service under the FA plane to which the service belongs. The FA plane can be indicated by a FA ID. That is to say, different resource IDs correspond to different combinations of FA IDs and slice IDs. Here, the different combinations of FA IDs and slice IDs may have the same or different slice identifiers. When they have the same slice identifier, they belong to different FA planes, that is, they correspond to different FA IDs. The above splicing of the FA ID and slice ID allocated to the service to obtain the resource ID of the service is only an example of generating a resource ID. The embodiments of the present invention can also adopt other methods. For example, the controller pre-sets the index corresponding to each combination for all combinations of FA ID and slice ID, and uses the index as the resource ID.

[0099] by Figure 5 For example, the SDN controller determines the FlexAlgo plane to which the user service belongs and the required physical resources based on the VPN information of the user service. A slice ID is allocated for the user service within the FlexAlgo plane. This information is sent by the SDN controller to the provider edge router (PE) device, forming the slice planning table shown in Table 1.

[0100]

[0101]

[0102] Table 1 - Slicing Planning Table

[0103] In Table 1, FlexAlgo ID represents the FA plane, and resource information represents the required physical resources.

[0104] The SDN controller converts the FlexAlgo ID and slice ID planned in Table 1 into the corresponding Resource ID (according to the splicing method above), allocates (configures) physical resources for the forwarding device interface, and the forwarding device plans the physical resources according to the configuration. For example, using G.MTN hard slicing technology, the physical resources are associated with the corresponding G.MTN sub-interface, and finally a slice forwarding table is formed on the forwarding device. Among them, the slice forwarding tables formed on device 1 and device 3 are shown in Table 2 and Table 3 respectively. In Table 2 and Table 3, the outbound interface represents the physical outbound interface of the message on the forwarding device, the FlexAlgo ID represents the FA plane, the resource information represents the required physical resources, and the resource interface represents the virtual sub-interface divided under the physical outbound interface. The virtual sub-interface is associated with the physical resource.

[0105]

[0106]

[0107] Table 2 - Slice forwarding table for device 1

[0108] Outbound interface FlexAlgo ID Slice ID Resource ID Resource Information Resource Interface GE1 / 0 / 0 128 1 32769 BW:10G GE1 / 0 / 0.MTN1 GE1 / 0 / 0 128 2 32770 BW:20G GE1 / 0 / 0.MTN2 GE1 / 0 / 0 128 3 32771 BW:30G GE1 / 0 / 0.MTN3 GE1 / 0 / 0 129 1 33024 BW:10G GE1 / 0 / 0.MTN4 GE1 / 0 / 0 129 2 33025 BW:20G GE1 / 0 / 0.MTN5 GE1 / 0 / 0 129 3 33026 BW:30G GE1 / 0 / 0.MTN6

[0109] Table 3 - Slice forwarding table for device 3

[0110] Figure 6 The present invention provides an SRv6 message forwarding method according to an embodiment of the present invention, and a process when applied to a forwarding device. The forwarding device may be a carrier backbone router (P) device or a carrier edge router (PE) device, such as Figure 6 As shown, the method includes:

[0111] In step 61, when forwarding the first SRv6 packet of the first service, the forwarding device parses the first slice ID from the IPv6 header of the first SRv6 packet, and searches the SR forwarding table entry to determine the first physical outbound interface and the first FA ID corresponding to the first SRv6 packet.

[0112] Here, the embodiment of the present invention carries the slice ID of the service in the IPv6 header, and the slice ID of the service can be obtained by parsing the IPv6 header. Preferably, the slice ID can be carried in the FlowLabel field in the IPv6 header.

[0113] Step 62: Search the locally maintained slice forwarding table according to the first physical outbound interface, the first FA ID, and the first slice ID to determine the first resource interface corresponding to the first SRv6 message.

[0114] Here, the forwarding device of an embodiment of the present invention locally maintains a slice forwarding table, which records the correspondence between the physical outbound interface, FA ID, slice ID, and resource interface. Each correspondence corresponds to a forwarding table entry for a service, where the physical outbound interface represents the physical outbound interface of the service on the forwarding device; the FA ID represents the FA plane; the slice ID represents the network slice to which the service is allocated; and the resource interface is a virtual sub-interface under the physical outbound interface, which is associated with the physical resources required by the first service.

[0115] Step 63: Send the first SRv6 message through the first resource interface;

[0116] Through the above steps, the embodiment of the present invention realizes the isolation of slice resources at the user service level. From the above description, it can be seen that the embodiment of the present invention has at least the following advantages:

[0117] 1. The embodiment of the present invention adopts hierarchical network slicing, which, through the combination of the control plane and the forwarding plane, can not only achieve resource isolation between physical interfaces, but also achieve slice resource isolation within the same interface.

[0118] 2. The forwarding plane in this embodiment of the present invention associates slice IDs with physical link resources to achieve resource isolation on the same physical interface. This adds a slice information lookup and forwarding process to the forwarding plane, which does not involve other operations and has minimal impact on system performance.

[0119] 3. This embodiment combines the FA ID with the slice ID to obtain the resource ID that ultimately matches the physical resource. This effectively addresses the limited range of FlexAlgo IDs and slice IDs, increasing the number of slices supported. For example, given that FlowLabel can occupy 8 bits, the number of slices supported is 32,768 (128 x 256).

[0120] Depending on the different roles of the forwarding device, the forwarding device can also perform different entry maintenance operations. These operations are described below.

[0121] 1. The forwarding device is a P device

[0122] When the forwarding device is a P device, the forwarding device can also receive information sent by the controller (including the SDN controller and the network management) and maintain the slice forwarding table locally. Specifically, before the above step 61:

[0123] 1) The forwarding device can receive the configuration information of physical resources sent by the controller, and the configuration information of the physical resources includes the first physical output interface, the first FA ID, the first slice ID of the first service on the forwarding device, and the physical resources of the first service configured on the first physical output interface. The first FA ID and the first slice ID are respectively the identifiers of the first FlexAlgo plane and the first slice allocated by the controller to the first service.

[0124] 2) The forwarding device associates the physical resources of the first service configured on the first physical outbound interface with the first resource interface under the physical outbound interface.

[0125] 3) The forwarding device maintains the slice forwarding table based on the first physical output interface, the first FA ID, the first slice ID and the first resource interface, and the slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID and resource interface of each service.

[0126] Optionally, the configuration information of the physical resource may further include the first physical resource requirement information of the first service and the resource ID of the first service, wherein the resource ID of the first service corresponds to the first slice ID under the first FA ID, and different resource IDs correspond to different combinations of FA IDs and slice IDs; in this way, when the forwarding device maintains the slice forwarding table, it may also record at least one of the resource ID of the first service and the first physical resource requirement information in the slice forwarding table. As an implementation method, the resource ID may be obtained by concatenating the FA ID and the slice ID. Of course, the resource ID may also be an identifier generated by other methods, corresponding one-to-one to each combination of FA ID and slice ID.

[0127] 2. Forwarding device is PE device

[0128] When the forwarding device is a PE device, the forwarding device can also receive information sent by the controller (including the SDN controller and the network management) and maintain the slice planning table and slice forwarding table locally. Specifically, before the above step 61:

[0129] 1) The forwarding device may receive a first FA ID and a first slice ID sent by the controller, where the first FA ID and the first slice ID are identifiers of the first FlexAlgo plane and the first slice respectively allocated by the controller to the first service.

[0130] 2) According to the first VPN, the first FA ID and the first slice ID to which the first service belongs, the slice planning table is maintained, and the slice planning table records the correspondence between the FA ID, VPN ID and slice ID of each service.

[0131] Optionally, the forwarding device may also receive the first physical resource requirement information of the first service sent by the controller, and then, when maintaining the slice planning table, also record the first physical resource requirement information of the first service in the slice planning table.

[0132] 3) Receive the configuration information of the physical resources sent by the controller, the configuration information of the physical resources includes the first physical output interface, the first FA ID, the first slice ID of the first service on this forwarding device, and the physical resources of the first service configured on the first physical output interface.

[0133] 4) Associating the physical resources of the first service configured on the first physical outbound interface with the first resource interface under the physical outbound interface.

[0134] 5) Maintain a slice forwarding table based on the first physical outbound interface, the first FA ID, the first slice ID and the first resource interface, wherein the slice forwarding table records the correspondence between the physical outbound interface, FA ID, slice ID and resource interface of each service.

[0135] Optionally, the configuration information of the physical resources also includes the first physical resource requirement information of the first service; in this way, when the forwarding device maintains the slice forwarding table, it can also record at least one of the resource ID and the first physical resource requirement information of the first service in the slice forwarding table, where the resource ID is obtained by concatenating the FA ID and the slice ID.

[0136] In addition, when the forwarding device is a PE device, the forwarding device will also encapsulate the SRv6 message and fill in the slice ID. Specifically, before forwarding the first SRv6 message of the first service in step 61, the forwarding device can receive the first message of the first service sent by the user edge CE device; then, according to the first VPN to which the first service belongs, search the slice planning table to obtain the first slice ID corresponding to the first VPN; then, according to the SRv6 format, encapsulate the SR header for the first message, and add the first slice ID in the IPv6 header to generate the first SRv6 message.

[0137] Figure 7 The relevant configuration operations of the controller (which can be an SDN controller or a network management system) in the embodiment of the present invention are given, such as Figure 7As shown, the SRv6 message configuration method provided in an embodiment of the present invention, when applied to a controller, includes:

[0138] In step 71 , the controller allocates a first FlexAlgo plane and a first slice under the first FlexAlgo plane to a first service, and determines first physical resource requirement information of the first service.

[0139] Here, the controller can pre-plan the FlexAlgo planes to which different services belong, specifically by dividing them based on service characteristics. In this way, the controller can allocate a specific FA plane (assuming it is the first FlexAlgo plane) to the first service based on the pre-planned plan. The controller can then allocate the first slice under the first FlexAlgo plane to the first service based on the service characteristics of the first service and determine the first physical resource requirement information for the first service. Here, the service characteristics include at least one of the VLAN, VPN, and DSCP to which the service belongs.

[0140] Step 72: The controller sends the first FA ID of the first FlexAlgo plane and the first slice ID of the first slice to the PE device of the first service.

[0141] In step 73, the controller configures the physical resources of the first service for the physical output interface of each forwarding device of the first service based on the first physical resource requirement information, and sends the configuration information of the physical resources to the forwarding device. The configuration information of the physical resources includes the physical output interface, the first FA ID, the first slice ID, and the physical resources of the first service configured on the physical output interface. The forwarding device includes the PE device and P device of the first service.

[0142] Through the above steps, the controller of an embodiment of the present invention configures the forwarding device with relevant information that can be used to generate a slice forwarding table, thereby providing support for achieving slice resource isolation at the user service level.

[0143] In an embodiment of the present invention, the controller may also send the first physical resource requirement information of the first service to the PE device of the first service, so that the PE device may add the first physical resource requirement information of the first service to the slice planning table.

[0144] Similarly, the controller can generate a resource ID for the first service, wherein the resource ID for the first service corresponds to the first slice ID under the first FA ID, and different resource IDs correspond to different combinations of FA IDs and slice IDs. The specific method for generating the resource ID can be to concatenate the FA ID and slice ID described above, or to pre-establish an index that corresponds to each combination of FA ID and slice ID, and use the index as the resource ID corresponding to the combination, and so on.

[0145] In this way, the controller can also carry the first physical resource requirement information of the first service and the resource ID of the first service in the configuration information of the physical resources sent to the forwarding device, so that the forwarding device can add at least one of the resource ID of the first service and the first physical resource requirement information in the slice forwarding table.

[0146] The above describes the method of the embodiment of the present invention from the perspectives of the forwarding device (PE device and P device) and the controller side. It can be seen that since the slice ID is carried in the IPv6 packet header (FLowLabel field), the embodiment of the present invention naturally supports IPv6 forwarding and SRv6 forwarding. Figure 8 Taking SRv6 Policy forwarding as an example, this section provides a diagram of the device processing process and message encapsulation at the forwarding layer.

[0147] Among them, in PE equipment, that is, Figure 8 At the forwarding device corresponding to A1::1 in the example, perform the following steps:

[0148] 901. Inherits the SRv6 Policy encapsulation method and encapsulates the message.

[0149] 902. According to Table 1 - Slice Planning Table, encapsulate the corresponding slice ID into the IPv6 message FlowLabel field.

[0150] 903. Based on the SRv6 forwarding mechanism, search the SR forwarding table entry to confirm the physical outbound interface and FlexAlgo ID.

[0151] 904. Search "Table 2 - Slice Forwarding Table" based on the physical outbound interface, FlexAlgo ID, and slice ID, obtain the resource interface, and forward the message according to the resource information.

[0152] In the P device, that is Figure 8 At the forwarding devices corresponding to A2::1 and A3::1, perform the following steps:

[0153] 911. Based on the SRv6 forwarding mechanism, search the SR forwarding table entry and confirm the physical outbound interface and FlexAlgo ID.

[0154] 912. Parse the slice ID in the IPv6 packet header, search "Table 2 - Slice Forwarding Table" based on the physical outbound interface, FlexAlgo ID, and slice ID, obtain the resource interface, and forward the packet according to the resource information.

[0155] In the export equipment, i.e. Figure 8 At the forwarding device corresponding to A4::1 in the example, perform the following steps:

[0156] 921. Decapsulate the message according to the SRv6 forwarding mechanism

[0157] The above describes various methods of the embodiments of the present invention. The following further provides apparatuses for implementing the above methods.

[0158] Please refer to Figure 9 , an embodiment of the present invention provides a forwarding device, including:

[0159] A parsing module 91 is configured to parse a first slice ID from an IPv6 header of a first SRv6 packet when forwarding the first service, and search a segment routing (SR) forwarding table entry to determine a first physical outbound interface and a first flexible algorithm identifier (FA ID) corresponding to the first SRv6 packet.

[0160] A search module 92 is configured to search a locally maintained slice forwarding table according to the first physical outbound interface, the first FA ID, and the first slice ID, and determine the first resource interface corresponding to the first SRv6 message;

[0161] A forwarding module 93, configured to send the first SRv6 message through the first resource interface;

[0162] Among them, the slice forwarding table maintains the correspondence between the physical output interface, FA ID, slice ID and resource interface.

[0163] Preferably, the forwarding device is a backbone router P device of an operator of the first service, and the forwarding device further includes:

[0164] a first receiving module, configured to receive configuration information of physical resources sent by the controller, the configuration information of the physical resources including a first physical outbound interface, a first FA ID, a first slice ID of the first service on the local forwarding device, and physical resources of the first service configured on the first physical outbound interface, where the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice, respectively, allocated by the controller for the first service;

[0165] A first configuration module is configured to associate the physical resources of the first service configured on the first physical outbound interface with a first resource interface under the physical outbound interface;

[0166] The first maintenance module is used to maintain the slice forwarding table based on the first physical output interface, the first FA ID, the first slice ID and the first resource interface. The slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID and resource interface of each service.

[0167] Preferably, the forwarding device is a provider edge router PE of the first service, and the forwarding device further includes:

[0168] A second receiving module is configured to receive a first FA ID and a first slice ID sent by the controller, where the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice respectively allocated by the controller for the first service;

[0169] A second maintenance module is configured to maintain the slice planning table according to the first VPN, the first FA ID, and the first slice ID to which the first service belongs, wherein the slice planning table records the correspondence between the FA ID, VPN ID, and slice ID of each service;

[0170] A third receiving module is configured to receive configuration information of physical resources sent by the controller, where the configuration information of the physical resources includes a first physical outbound interface, a first FA ID, a first slice ID, and physical resources of the first service configured on the first physical outbound interface of the first service on the local forwarding device;

[0171] A second configuration module is used to associate the physical resources of the first service configured on the first physical outbound interface with the first resource interface under the physical outbound interface;

[0172] The third maintenance module is used to maintain a slice forwarding table based on the first physical output interface, the first FA ID, the first slice ID and the first resource interface. The slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID and resource interface of each service.

[0173] Preferably, the forwarding device further includes:

[0174] The encapsulation module is used to receive the first message of the first service sent by the user edge CE device before forwarding the first SRv6 message of the first service; search the slice planning table according to the first VPN to which the first service belongs, and obtain the first slice ID corresponding to the first VPN; encapsulate the SR header for the first message according to the SRv6 format, and add the first slice ID in the IPv6 header to generate the first SRv6 message.

[0175] Preferably, the forwarding device further includes:

[0176] a fourth receiving module, configured to receive first physical resource requirement information of the first service sent by the controller;

[0177] The fourth maintenance module is used to record the first physical resource requirement information of the first business in the slice planning table when maintaining the slice planning table.

[0178] Preferably, the configuration information of the physical resource also includes first physical resource requirement information of the first service and a resource ID of the first service, wherein the resource ID of the first service corresponds to the first slice ID under the first FA ID; the forwarding device also includes:

[0179] The fifth maintenance module is used to record at least one of the resource ID and the first physical resource requirement information of the first service in the slice forwarding table when maintaining the slice forwarding table.

[0180] Preferably, the first slice ID is carried in the FlowLabel field in the IPv6 header.

[0181] Preferably, the resource ID of the first service is obtained by concatenating the first FA ID and the first slice ID.

[0182] It should be noted that the device in this embodiment is the same as the above Figure 6 The device corresponding to the method shown, the implementation methods in the above embodiments are all applicable to the embodiments of the device, and can also achieve the same technical effects. The above device provided by the embodiment of the present invention can implement all the method steps implemented by the above method embodiment and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be detailed here.

[0183] Please refer to Figure 10 , an embodiment of the present invention provides a structural diagram of a forwarding device, including: a processor 1001, a transceiver 1002, a memory 1003 and a bus interface, wherein:

[0184] In this embodiment of the present invention, the forwarding device further includes: a program stored in the memory 1003 and executable on the processor 1001, wherein the program, when executed by the processor 1001, implements the following steps:

[0185] When forwarding a first SRv6 packet of a first service, parse the first slice ID from the IPv6 header of the first SRv6 packet, and search the segment routing SR forwarding table entry to determine the first physical outbound interface and the first flexible algorithm identifier FA ID corresponding to the first SRv6 packet;

[0186] Searching a locally maintained slice forwarding table according to the first physical outbound interface, the first FA ID, and the first slice ID to determine a first resource interface corresponding to the first SRv6 message;

[0187] Sending the first SRv6 message through the first resource interface;

[0188] Among them, the slice forwarding table maintains the correspondence between the physical output interface, FA ID, slice ID and resource interface.

[0189] The forwarding device is a backbone router P device of an operator of the first service. When the processor executes the program, the processor further implements the following steps:

[0190] Before forwarding the first SRv6 message, receive physical resource configuration information sent by the controller, where the physical resource configuration information includes a first physical outbound interface, a first FA ID, a first slice ID of the first service on the local forwarding device, and physical resources of the first service configured on the first physical outbound interface, where the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice, respectively, allocated by the controller for the first service;

[0191] Associating the physical resources of the first service configured on the first physical outbound interface with the first resource interface under the physical outbound interface;

[0192] According to the first physical output interface, the first FA ID, the first slice ID and the first resource interface, the slice forwarding table is maintained, and the slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID and resource interface of each service.

[0193] Optionally, the forwarding device is a provider edge router PE of the first service, and the processor further implements the following steps when executing the program:

[0194] Before forwarding the first SRv6 message, receive a first FA ID and a first slice ID sent by the controller, where the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice, respectively, allocated by the controller for the first service;

[0195] Maintaining the slice planning table according to the first VPN, the first FA ID, and the first slice ID to which the first service belongs, where the slice planning table records the correspondence between the FA ID, VPN ID, and slice ID of each service;

[0196] Receive configuration information of physical resources sent by the controller, where the configuration information of the physical resources includes a first physical outbound interface, a first FA ID, a first slice ID, and the physical resources of the first service configured on the first physical outbound interface of the first service on the forwarding device;

[0197] Associating the physical resources of the first service configured on the first physical outbound interface with the first resource interface under the physical outbound interface;

[0198] According to the first physical output interface, the first FA ID, the first slice ID and the first resource interface, a slice forwarding table is maintained, and the slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID and resource interface of each service.

[0199] Optionally, when executing the program, the processor further implements the following steps:

[0200] Before forwarding the first SRv6 packet of the first service, receiving a first packet of the first service sent by a user edge CE device;

[0201] According to the first VPN to which the first service belongs, searching the slice planning table to obtain a first slice ID corresponding to the first VPN;

[0202] According to the SRv6 format, an SR header is encapsulated for the first message, and the first slice ID is added to the IPv6 header to generate the first SRv6 message.

[0203] Optionally, when executing the program, the processor further implements the following steps:

[0204] receiving first physical resource requirement information of the first service sent by the controller;

[0205] When maintaining the slice planning table, the first physical resource requirement information of the first business is also recorded in the slice planning table.

[0206] Optionally, the configuration information of the physical resource also includes first physical resource requirement information of the first service and a resource ID of the first service, wherein the resource ID of the first service corresponds to the first slice ID under the first FA ID; when the processor executes the program, it further implements the following steps:

[0207] When maintaining the slice forwarding table, at least one of the resource ID and the first physical resource requirement information of the first service is also recorded in the slice forwarding table.

[0208] Optionally, the resource ID of the first service is obtained by concatenating the first FA ID and the first slice ID.

[0209] Optionally, the first slice ID is carried in a flow label FlowLabel field in an IPv6 header.

[0210] It is understandable that in the embodiment of the present invention, when the computer program is executed by the processor 1001, the above Figure 6 The various processes of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0211] exist Figure 10 In the embodiment of the present invention, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits such as one or more processors represented by processor 1001 and memory represented by memory 1003. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore not further described herein. The bus interface provides an interface. The transceiver 1002 can be multiple components, namely, a transmitter and a receiver, providing a means for communicating with various other devices over a transmission medium.

[0212] The processor 1001 is responsible for managing the bus architecture and general processing, and the memory 1003 can store data used by the processor 1001 when performing operations.

[0213] It should be noted that the terminal in this embodiment is the same as the above Figure 6The device corresponding to the method shown, and the implementation methods in the above embodiments are all applicable to the embodiments of the terminal, and can also achieve the same technical effects. In this device, transceiver 1002 and memory 1003, as well as transceiver 1002 and processor 1001, can be communicatively connected via a bus interface. The functions of processor 1001 can also be implemented by transceiver 1002, and the functions of transceiver 1002 can also be implemented by processor 1001. It should be noted that the above-mentioned device provided by the embodiment of the present invention can implement all the method steps implemented by the above-mentioned method embodiment and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be detailed here.

[0214] In some embodiments of the present invention, a computer-readable storage medium is further provided, on which a program is stored. When the program is executed by a processor, the following steps are implemented:

[0215] When forwarding a first SRv6 packet of a first service, parse the first slice ID from the IPv6 header of the first SRv6 packet, and search the segment routing SR forwarding table entry to determine the first physical outbound interface and the first flexible algorithm identifier FA ID corresponding to the first SRv6 packet;

[0216] Searching a locally maintained slice forwarding table according to the first physical outbound interface, the first FA ID, and the first slice ID to determine a first resource interface corresponding to the first SRv6 message;

[0217] Sending the first SRv6 message through the first resource interface;

[0218] Among them, the slice forwarding table maintains the correspondence between the physical output interface, FA ID, slice ID and resource interface.

[0219] When the program is executed by the processor, it can implement all the implementation methods of the above-mentioned SRV6 message forwarding method applied to the forwarding device and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0220] The embodiment of the present invention provides Figure 11 A controller as shown includes:

[0221] The first configuration module 111 is configured to: allocate a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane to a first service, determine first physical resource requirement information of the first service, and send a first FA ID of the first FlexAlgo plane and a first slice ID of the first slice to a provider edge router (PE) device of the first service;

[0222] The second configuration module 112 is used to configure the physical resources of the first service for the physical output interface of each forwarding device of the first service according to the first physical resource requirement information, and send the configuration information of the physical resources to the forwarding device, wherein the configuration information of the physical resources includes the physical output interface, the first FA ID, the first slice ID and the physical resources of the first service configured on the physical output interface, and the forwarding device includes the PE device of the first service and the operator backbone router P device.

[0223] Optionally, the first configuration module 111 is also used to allocate a first flexible algorithm FlexAlgo plane to the first service; according to the service characteristics of the first service, allocate a first slice under the first FlexAlgo plane to the first service, and determine the first physical resource requirement information of the first service, wherein the service characteristics include at least one of virtual local area network VLAN, VPN and differentiated service code point DSCP.

[0224] Optionally, the controller further includes:

[0225] The first sending module is configured to send the first physical resource requirement information of the first service to a PE device of the first service.

[0226] Optionally, the controller further includes:

[0227] an identification generation module, configured to generate a resource ID for the first service, wherein the resource ID for the first service corresponds to a first slice ID under the first FA ID;

[0228] The physical resource configuration information also includes first physical resource requirement information of the first service and a resource ID of the first service.

[0229] Optionally, the resource ID of the first service is obtained by concatenating the first FA ID and the first slice ID.

[0230] It should be noted that the device in this embodiment is the same as the above Figure 7 The device corresponding to the method shown, the implementation methods in the above embodiments are all applicable to the embodiments of the device, and can also achieve the same technical effects. It should be noted that the above device provided by the embodiment of the present invention can implement all the method steps implemented by the above method embodiment and can achieve the same technical effects. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0231] Please refer to Figure 12, an embodiment of the present invention provides a schematic diagram of a controller structure, including: a processor 1201, a transceiver 1202, a memory 1203 and a bus interface, wherein:

[0232] In an embodiment of the present invention, the controller further includes: a program stored in the memory 1203 and executable on the processor 1201, wherein the program, when executed by the processor 1201, implements the following steps:

[0233] Allocate a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane to a first service, and determine first physical resource requirement information of the first service;

[0234] The controller sends the first FA ID of the first FlexAlgo plane and the first slice ID of the first slice to the provider edge router PE device of the first service;

[0235] The controller configures the physical resources of the first service for the physical output interface of each forwarding device of the first service based on the first physical resource requirement information, and sends the configuration information of the physical resources to the forwarding device. The configuration information of the physical resources includes the physical output interface, the first FA ID, the first slice ID and the physical resources of the first service configured on the physical output interface. The forwarding device includes the PE device of the first service and the operator backbone router P device.

[0236] Optionally, when executing the program, the processor further implements the following steps:

[0237] Allocate a first flexible algorithm FlexAlgo plane to the first service;

[0238] According to the service characteristics of the first service, a first slice under the first FlexAlgo plane is allocated to the first service, and first physical resource requirement information of the first service is determined, wherein the service characteristics include at least one of a virtual local area network VLAN, VPN and a differentiated service code point DSCP.

[0239] Optionally, when executing the program, the processor further implements the following steps:

[0240] The first physical resource requirement information of the first service is sent to a PE device of the first service.

[0241] Optionally, when executing the program, the processor further implements the following steps:

[0242] Generate a resource ID for the first service, where the resource ID for the first service corresponds to a first slice ID under the first FA ID;

[0243] The physical resource configuration information also includes first physical resource requirement information of the first service and a resource ID of the first service.

[0244] Optionally, the resource ID of the first service is obtained by concatenating the first FA ID and the first slice ID.

[0245] It is understandable that in the embodiment of the present invention, when the computer program is executed by the processor 1201, the above Figure 7 The various processes of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0246] exist Figure 12 In the embodiment of the present invention, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits such as one or more processors represented by processor 1201 and memory represented by memory 1203. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore not further described herein. The bus interface provides an interface. The transceiver 1202 can be multiple components, namely, a transmitter and a receiver, providing a means for communicating with various other devices over a transmission medium.

[0247] The processor 1201 is responsible for managing the bus architecture and general processing, and the memory 1203 can store data used by the processor 1201 when performing operations.

[0248] It should be noted that the terminal in this embodiment is the same as the above Figure 7 The device corresponding to the method shown, and the implementation methods in the above embodiments are all applicable to the embodiments of the terminal, and can also achieve the same technical effects. In this device, transceiver 1202 and memory 1203, as well as transceiver 1202 and processor 1201, can be connected through a bus interface for communication. The functions of processor 1201 can also be implemented by transceiver 1202, and the functions of transceiver 1202 can also be implemented by processor 1201. It should be noted that the above-mentioned device provided by the embodiment of the present invention can implement all the method steps implemented by the above-mentioned method embodiment and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be detailed here.

[0249] In some embodiments of the present invention, a computer-readable storage medium is further provided, on which a program is stored. When the program is executed by a processor, the following steps are implemented:

[0250] Allocate a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane to a first service, and determine first physical resource requirement information of the first service;

[0251] The controller sends the first FA ID of the first FlexAlgo plane and the first slice ID of the first slice to the provider edge router PE device of the first service;

[0252] The controller configures the physical resources of the first service for the physical output interface of each forwarding device of the first service based on the first physical resource requirement information, and sends the configuration information of the physical resources to the forwarding device. The configuration information of the physical resources includes the physical output interface, the first FA ID, the first slice ID and the physical resources of the first service configured on the physical output interface. The forwarding device includes the PE device of the first service and the operator backbone router P device.

[0253] When the program is executed by the processor, it can implement all the implementation methods in the above-mentioned configuration method of the SRV6 message applied to the controller, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0254] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0255] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0256] In the embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0257] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.

[0258] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0259] If the functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or the portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard drive, ROM, RAM, a magnetic disk, or an optical disk.

[0260] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A method for forwarding SRv6 packets based on IPv6 segment routing, characterized in that: include: When forwarding a first SRv6 message of a first service, the forwarding device parses a first slice ID from an IPv6 header of the first SRv6 message, and searches for a segment routing SR forwarding table entry to determine a first physical outbound interface and a first flexible algorithm identifier FA ID corresponding to the first SRv6 message; According to the first physical outbound interface, the first FA ID, and the first slice ID, searching the locally maintained slice forwarding table to determine the first resource interface corresponding to the first SRv6 message; Sending the first SRv6 message through the first resource interface; Among them, the slice forwarding table maintains the correspondence between the physical output interface, FA ID, slice ID and resource interface.

2. The method according to claim 1, characterized in that The forwarding device is a backbone router P device of an operator of the first service. Before forwarding the first SRv6 message, the method further includes: Receive configuration information of physical resources sent by the controller, where the configuration information of the physical resources includes a first physical outbound interface, a first FA ID, a first slice ID, and a physical resource of the first service configured on the first physical outbound interface of the first service on the forwarding device, where the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice respectively allocated by the controller to the first service; Associating the physical resources of the first service configured on the first physical outbound interface with the first resource interface under the first physical outbound interface; According to the first physical output interface, the first FA ID, the first slice ID and the first resource interface, the slice forwarding table is maintained, and the slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID and resource interface of each service.

3. The method according to claim 1, characterized in that The forwarding device is a provider edge router PE of the first service. Before forwarding the first SRv6 message, the method further includes: Receive a first FA ID and a first slice ID sent by the controller, where the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice respectively allocated by the controller for the first service; Maintain a slice planning table according to the first VPN, the first FA ID, and the first slice ID to which the first service belongs, wherein the slice planning table records the correspondence between the FA ID, the VPN ID, and the slice ID of each service; Receive configuration information of physical resources sent by the controller, where the configuration information of the physical resources includes a first physical outbound interface, a first FA ID, a first slice ID, and physical resources of the first service configured on the first physical outbound interface of the first service on the forwarding device; Associating the physical resources of the first service configured on the first physical outbound interface with the first resource interface under the first physical outbound interface; According to the first physical output interface, the first FA ID, the first slice ID and the first resource interface, a slice forwarding table is maintained, and the slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID and resource interface of each service.

4. The method according to claim 3, characterized in that Before forwarding the first SRv6 message of the first service, the method further includes: Receiving a first message of a first service sent by a user edge CE device; According to the first VPN to which the first service belongs, searching the slice planning table to obtain a first slice ID corresponding to the first VPN; According to the SRv6 format, an SR header is encapsulated for the first message, and the first slice ID is added to the IPv6 header to generate the first SRv6 message.

5. The method according to any one of claims 3 to 4, characterized in that: Also includes: Receiving first physical resource requirement information of the first service sent by the controller; When maintaining the slice planning table, the first physical resource requirement information of the first service is also recorded in the slice planning table.

6. The method according to any one of claims 2 to 4, characterized in that: The configuration information of the physical resources also includes first physical resource requirement information of the first service and a resource ID of the first service, wherein the resource ID of the first service corresponds to a first slice ID under the first FA ID; When maintaining the slice forwarding table, at least one of the resource ID of the first service and the first physical resource requirement information is also recorded in the slice forwarding table.

7. The method according to claim 6, characterized in that The resource ID of the first service is obtained by concatenating the first FA ID and the first slice ID.

8. The method according to any one of claims 1 to 4, characterized in that The first slice ID is carried in the flow label FlowLabel field in the IPv6 header.

9. A method for configuring a segment routing SRv6 message based on IPv6, characterized in that: include: The controller allocates a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane to the first service, and determines first physical resource requirement information of the first service; The controller sends the first FA ID of the first FlexAlgo plane and the first slice ID of the first slice to the operator edge router PE device of the first service; The controller configures the physical resources of the first service for the first physical output interface of each forwarding device of the first service according to the first physical resource demand information, and sends the configuration information of the physical resources to the forwarding device, wherein the configuration information of the physical resources includes the first physical output interface, the first FA ID, the first slice ID, and the physical resources of the first service configured on the first physical output interface, so that the forwarding device maintains a slice forwarding table according to the first physical output interface, the first FA ID, the first slice ID, and the first resource interface, wherein the slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID, and resource interface of each service, wherein the first resource interface is the resource interface under the first physical output interface to which the forwarding device associates the physical resources of the first service configured on the first physical output interface, and the forwarding device includes a PE device of the first service and an operator backbone router P device.

10. The method according to claim 9, characterized in that The controller allocates a first FlexAlgo plane and a first slice under the first FlexAlgo plane to a first service, and determines first physical resource requirement information of the first service, specifically: The controller allocates a first flexible algorithm FlexAlgo plane to the first service; According to the service characteristics of the first service, a first slice under the first FlexAlgo plane is allocated to the first service, and first physical resource requirement information of the first service is determined, wherein the service characteristics include at least one of a virtual local area network VLAN, VPN and a differentiated service code point DSCP.

11. The method according to claim 9 or 10, characterized in that Also includes: The controller sends first physical resource requirement information of the first service to a PE device of the first service.

12. The method according to claim 11, characterized in that Also includes: The controller generates a resource ID of the first service, wherein the resource ID of the first service corresponds to a first slice ID under the first FAID; The configuration information of the physical resources also includes first physical resource requirement information of the first service and a resource ID of the first service.

13. The method according to claim 12, characterized in that The resource ID of the first service is obtained by concatenating the first FAID and the first slice ID.

14. A forwarding device, characterized in that: include: A parsing module, configured to parse a first slice ID from an IPv6 header of a first SRv6 message when forwarding the first SRv6 message of the first service, and to search for a segment routing SR forwarding table entry to determine a first physical outbound interface and a first flexible algorithm identifier FA ID corresponding to the first SRv6 message; A search module, configured to search a locally maintained slice forwarding table according to the first physical outbound interface, the first FA ID, and the first slice ID, and determine a first resource interface corresponding to the first SRv6 message; A forwarding module, configured to send the first SRv6 message through the first resource interface; Among them, the slice forwarding table maintains the correspondence between the physical output interface, FA ID, slice ID and resource interface.

15. A forwarding device, characterized in that: comprising a transceiver and a processor, wherein: The processor is configured to parse a first slice ID from an IPv6 header of the first SRv6 message when forwarding the first SRv6 message of the first service, and search for a segment routing SR forwarding table entry to determine a first physical outbound interface and a first flexible algorithm identifier FA ID corresponding to the first SRv6 message; search for a locally maintained slice forwarding table according to the first physical outbound interface, the first FA ID, and the first slice ID to determine a first resource interface corresponding to the first SRv6 message; The transceiver is used to send the first SRv6 message through the first resource interface; Among them, the slice forwarding table maintains the correspondence between the physical output interface, FA ID, slice ID and resource interface.

16. A forwarding device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method according to any one of claims 1 to 8.

17. A controller, characterized in that: include: A first configuration module is used for the controller to allocate a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane to a first service, and determine first physical resource requirement information of the first service; send a first FA ID of the first FlexAlgo plane and a first slice ID of the first slice to a carrier edge router PE device of the first service; The second configuration module is used to configure the physical resources of the first service for the first physical output interface of each forwarding device of the first service according to the first physical resource demand information, and send the configuration information of the physical resources to the forwarding device, the configuration information of the physical resources includes the first physical output interface, the first FA ID, the first slice ID and the physical resources of the first service configured on the first physical output interface, so that the forwarding device maintains a slice forwarding table according to the first physical output interface, the first FA ID, the first slice ID and the first resource interface, the slice forwarding table records the correspondence between the physical output interface, FAID, slice ID and resource interface of each service, the first resource interface is the resource interface under the first physical output interface to which the forwarding device associates the physical resources of the first service configured on the first physical output interface, and the forwarding device includes a PE device of the first service and an operator backbone router P device.

18. A controller, characterized in that: comprising a transceiver and a processor, wherein: The processor is used for the controller to allocate a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane to the first service, and determine the first physical resource requirement information of the first service; and, according to the first physical resource requirement information, configure the physical resources of the first service for the first physical outbound interface of each forwarding device of the first service; The transceiver is used to send the first FA ID of the first FlexAlgo plane and the first slice ID of the first slice to the operator edge router PE device of the first service; and send the configuration information of physical resources to the forwarding device, the configuration information of physical resources includes the first physical output interface, the first FA ID, the first slice ID and the physical resources of the first service configured on the first physical output interface, so that the forwarding device maintains a slice forwarding table according to the first physical output interface, the first FA ID, the first slice ID and the first resource interface, the slice forwarding table records the correspondence between the physical output interface, FA ID, slice ID and resource interface of each service, the first resource interface is the resource interface under the first physical output interface to which the forwarding device associates the physical resources of the first service configured on the first physical output interface, and the forwarding device includes the PE device of the first service and the operator backbone router P device.

19. A controller, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the method according to any one of claims 9 to 13 are implemented.

20. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 13 are implemented.