CN115242713A

CN115242713A - IPV 6-based segmented routing message forwarding method, configuration method and equipment

Info

Publication number: CN115242713A
Application number: CN202110436526.4A
Authority: CN
Inventors: 龚立艳; 姜文颖; 程伟强; 刘毅松; 王豪杰; 杨雪
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2021-04-22
Filing date: 2021-04-22
Publication date: 2022-10-25

Abstract

A forwarding method, a configuration method and equipment of a segmented routing message based on IPV6 are disclosed, wherein the forwarding method comprises the following steps: when forwarding equipment forwards a first SRv6 message of a first service, a first slice ID is analyzed from an IPv6 header of the first SRv6 message, a Segmented Routing (SR) forwarding table entry is searched, and a first physical output interface and a first flexible algorithm identification (FA ID) corresponding to the first SRv6 message are determined; according to the first physical outgoing interface, the first FA ID and the first slice ID, searching a locally maintained slice forwarding table, and determining a first resource interface corresponding to the first SRv6 message; sending the first SRv6 message through the first resource interface; the slice forwarding table maintains a corresponding relationship among a physical outbound interface, an FA ID, a slice ID and a resource interface. The invention can realize resource isolation under the same physical interface, has small influence on system performance, solves the problem of small ranges of FlexAlgo ID and slice ID, and increases the actual slice number.

Description

IPV 6-based segmented routing message forwarding method, configuration method and equipment

Technical Field

The invention relates to the technical field of data forwarding, in particular to a forwarding method, a configuration method and equipment of a segmented routing message based on IPV 6.

Background

Network slicing is one of the key technologies of fifth generation mobile communication (5G), and can perform split management similar to traffic management on network data, and its essence is to divide a physical network that exists in reality into a plurality of virtual networks of different types on a logical level, and divide the virtual networks according to service requirements of different users by indexes such as delay height, bandwidth size, reliability strength, and the like, so as to cope with complex and varied application scenarios. By slicing, a mobile network operator may classify users into different types, each having a different Service request, and manage the slice types and services each user is entitled to use according to a Service Level Agreement (SLA).

The 5G bearer network is a part of a 5G end-to-end service path, and the bearer network slice divides a plurality of logical virtual transmission subnets in a transmission hardware facility by virtualizing topology resources (such as links, nodes, ports, and network element internal resources) of the network. The virtual transmission sub-network is provided with an independent management plane, a control plane and a forwarding plane, and supports various services independently, so that the isolation among different services is realized.

The Flexible Algorithm (flexile-Algorithm, flexAlgo) is extended by an Inter Gateway Protocol (IGP) Segment Routing (SR), different Segment identifiers (Segment IDs, SID) are allocated to the same device to represent different FlexAlgo planes, and in each FlexAlgo plane, triplets (metricpype, calcpype, and LinkColor) are combined and independently calculated for Shortest Path First (SPF), so as to form an independent Routing forwarding table entry. FlexAlgo has no modification to the forwarding mechanism and can inherit the current SR as well as the IPv6 based segment routing (SRv 6) forwarding mechanism. In addition, flexAlgo is also sometimes abbreviated herein as FA.

Disclosure of Invention

At least one embodiment of the present invention provides a forwarding method, a configuration method, a terminal and a network device for an SRV6 packet, which can implement slice resource isolation at a user service level.

According to an aspect of the present invention, at least one embodiment provides a forwarding method for an IPv 6-based segment routing SRv6 packet, including:

when forwarding equipment forwards a first SRv6 message of a first service, resolving a first slice ID from an IPv6 header of the first SRv6 message, searching a Segmented Routing (SR) forwarding table entry, and determining a first physical output interface and a first flexible algorithm identification (FA ID) corresponding to the first SRv6 message;

according to the first physical outgoing interface, the first FA ID and the first slice ID, searching a locally maintained slice forwarding table, and determining a first resource interface corresponding to the first SRv6 message;

sending the first SRv6 message through the first resource interface;

the slice forwarding table maintains a corresponding relationship among a physical outbound interface, an FA ID, a slice ID and a resource interface.

Furthermore, according to at least one embodiment of the present invention, before forwarding the first SRv6 packet, the forwarding device is a provider backbone router P device of the first service, and the method further includes:

receiving configuration information of physical resources sent by the controller, where the configuration information of the physical resources includes a first physical outgoing 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 outgoing interface, and the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice allocated to the first service by the controller, respectively;

associating the physical resource of the first service configured on the first physical output interface to a first resource interface under the physical output interface;

and maintaining the slice forwarding table according to 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 corresponding relation among the physical outbound interface, the FA ID, the slice ID and the resource interface of each service.

Furthermore, according to at least one embodiment of the present invention, before forwarding the first SRv6 packet, the forwarding device is an operator edge router PE of the first service, and the method further includes:

receiving a first FA ID and a first slice ID sent by a controller, wherein the first FA ID and the first slice ID are respectively identifiers of a first FlexAlgo plane and a first slice which are distributed by the controller for a first service;

maintaining the slice planning table according to the first VPN to which the first service belongs, the first FA ID and the first slice ID, wherein the slice planning table records the corresponding relation among the FA ID, the VPN ID and the slice ID of each service;

receiving configuration information of physical resources sent by the controller, where the configuration information of the physical resources includes a first physical outgoing 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 outgoing interface;

and maintaining a slice forwarding table according to the first physical outgoing interface, the first FA ID, the first slice ID and the first resource interface, wherein the slice forwarding table records the corresponding relation among the physical outgoing interface, the FA ID, the slice ID and the resource interface of each service.

Furthermore, according to at least one embodiment of the present invention, before forwarding the first SRv6 packet of the first service, the method further includes:

receiving a first message of a first service sent by a Customer Edge (CE) device;

searching the slice planning table according to a first VPN to which the first service belongs, and acquiring a first slice ID corresponding to the first VPN;

and according to an SRv6 format, packaging an SR header for the first message, and adding the first slice ID in the IPv6 header to generate the first SRv6 message.

Further, in accordance with at least one embodiment of the present invention, there is also provided:

receiving first physical resource demand information of the first service sent by the controller;

when the slice planning table is maintained, first physical resource demand information of the first service is recorded in the slice planning table.

Furthermore, 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, where the resource ID of the first service corresponds to a first slice ID under the first FA ID;

further, according to at least one embodiment of the present invention, the resource ID of the first service is spliced by the first FA ID and the first slice ID.

And when maintaining the slice forwarding table, recording at least one of the resource ID of the first service and the first physical resource requirement information in the slice forwarding table.

Further in accordance with at least one embodiment of the present invention, the first slice ID is carried in a flow label FlowLabel field in an IPv6 header.

According to another aspect of the present invention, at least one embodiment provides a method for configuring an IPv6 based segment routing SRv6 packet, including:

the method comprises the steps that a controller allocates a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane for a first service, and determines first physical resource demand 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 provider edge router (PE) equipment of the first service;

the controller configures physical resources of the first service for a physical outgoing interface of each forwarding device of the first service according to the first physical resource demand information, and sends configuration information of the physical resources to the forwarding devices, where the configuration information of the physical resources includes the physical outgoing interface, a first FA ID, a first slice ID, and physical resources of the first service configured on the physical outgoing interface, and the forwarding devices include PE devices of the first service and provider backbone router P devices.

Furthermore, 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:

the controller allocates a first flexible algorithm FlexAlgo plane for the first service;

according to the service characteristics of a first service, a first slice under a first FlexAlgo plane is distributed for the first service, and first physical resource requirement information of the first service is determined, wherein the service characteristics comprise at least one of a Virtual Local Area Network (VLAN), a Virtual Private Network (VPN) and a Differentiated Services Code Point (DSCP).

and the controller sends the first physical resource demand information of the first service to the PE equipment of the first service.

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;

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.

Furthermore, 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.

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

the analysis module is used for analyzing a first slice ID from an IPv6 header of a first SRv6 message when the first SRv6 message of a first service is forwarded, searching a segment routing SR forwarding table item, and determining a first physical output interface and a first flexible algorithm identification (FA ID) corresponding to the first SRv6 message;

the searching module is used for searching a locally maintained slice forwarding table according to the first physical outgoing interface, the first FA ID and the first slice ID, and determining a first resource interface corresponding to the first SRv6 message;

a forwarding module, configured to send the first SRv6 packet through the first resource interface;

According to another aspect of the invention, at least one embodiment provides a forwarding device comprising a transceiver and a processor, wherein,

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

the transceiver is configured to send the first SRv6 packet through the first resource interface;

According to another aspect of the present invention, at least one embodiment provides a forwarding device, including: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method as described above.

According to another aspect of the present invention, at least one embodiment provides a controller comprising:

the 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 for the first service and determine first physical resource demand information of the first service; sending the first FA ID of the first FlexAlgo plane and the first slice ID of the first slice to the provider edge router (PE) equipment of the first service;

a second configuration module, configured to configure, according to the first physical resource requirement information, a physical output interface of each forwarding device for the first service with a physical resource of the first service, and send configuration information of the physical resource to the forwarding device, where the configuration information of the physical resource includes the physical output interface, a first FA ID, a first slice ID, and a physical resource of the first service configured on the physical output interface, and the forwarding device includes a PE device of the first service and a provider backbone router P device.

According to another aspect of the present invention, at least one embodiment provides a controller 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 for the first service, and determine first physical resource demand information of the first service; configuring physical resources of the first service for a physical output interface of each forwarding device of the first service according to the first physical resource demand information;

the transceiver is configured to send the first FA ID of the first FlexAlgo plane and the first slice ID of the first slice to an operator edge router PE device of the first service; and sending configuration information of physical resources to the forwarding device, where the configuration information of the physical resources includes the physical outgoing interface, a first FA ID, a first slice ID, and a physical resource of a first service configured on the physical outgoing interface, and the forwarding device includes a PE device of the first service and a P device of an operator backbone router.

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

According to another aspect of the invention, at least one embodiment provides a computer readable storage medium having a program stored thereon, which when executed by a processor, performs the steps of the method as described above.

Compared with the prior art, the forwarding method, the configuration method and the equipment for the IPV 6-based segmented routing message provided by the embodiment of the invention associate the slice ID with the physical link resource on the forwarding level, thereby realizing resource isolation under the same physical interface. In addition, the forwarding surface is added with a slice information table look-up forwarding flow, other operations are not involved, and the influence on the system performance is small. In addition, the embodiment of the invention combines the FA ID and the slice ID to obtain the resource ID finally matched with the physical resource, thereby effectively solving the problem of small ranges of FlexAlgo ID and slice ID and increasing the actual slice number.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

FIG. 1 is a schematic representation of FlexAlgo physical isolation;

FIG. 2 is a schematic of FlexAlgo logical isolation;

fig. 3 is a schematic diagram of a format of an IPv6 message;

fig. 4 is a schematic diagram illustrating that a flow label field of an IPv6 message carries a slice ID according to an embodiment of the present invention;

fig. 5 is a schematic diagram illustrating a slice ID planning according to an embodiment of the present invention;

fig. 6 is a flowchart of a method for forwarding an SRV6 packet according to an embodiment of the present invention;

fig. 7 is a flowchart of a method for configuring an SRV6 packet according to an embodiment of the present invention;

fig. 8 is an exemplary diagram of a device processing procedure and forwarding plane packet encapsulation according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of a forwarding device according to an embodiment of the present invention;

fig. 10 is another schematic structural diagram of a forwarding device according to an embodiment of the present invention;

FIG. 11 is a schematic structural diagram of a controller according to an embodiment of the present invention;

fig. 12 is a schematic structural diagram of another controller according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged under appropriate circumstances such that the embodiments of the application described herein may be implemented, for example, in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. In the description and in the claims "and/or" means at least one of the connected objects.

The FlexAlgo can divide a physical network into a plurality of virtual networks, and different virtual networks are utilized to realize the differentiated requirements of services. These virtual networks may be physically "isolated," such as fig. 1: adding different nodes or links to different flexalgos, FA 128 and FA 129 respectively, so as to form a virtual network as shown in the right half of fig. 1; it may also be possible to implement logical "isolation", such as fig. 2: the virtual network shown in the right half of fig. 2 can be formed by calculating the path based on the delay, the IGP Metric, and the TE Metric, and at this time, the two virtual networks share the physical link between the device 3 and the device 4. Each rectangular block in fig. 1 and 2 represents a forwarding device, and devices 1 to 6 are included in fig. 1 and 2.

When the FlexAlgo technique is applied to the field of slicing, the inventors found that the following problems exist:

(1) FlexAlgo can typically only implement the port-level coarse-grained slicing function shown in fig. 1. In the scenario shown in fig. 2, the same physical link is in different logical topologies (Topo), and the resources are shared, and no real resource isolation is achieved.

(2) The FlexAlgo extended control plane protocol needs to plan an independent address space for each slice, and performs independent SPF calculation for each slice, where the number of routes increases linearly with the increase of the number of slices, and the convergence performance decreases linearly with the increase of the number of slices. The resource occupation of each slice is large, and a large number of slice scenes cannot be supported.

(3) The maximum number of slices supported by the FlexAlgo is 128 (the FA ID range is 128-255), and the number of slices supported by the FlexAlgo cannot meet the actual requirement of the current network even if the system overhead is not considered.

In order to solve at least one of the above problems, an embodiment of the present invention provides a method for forwarding an SRV6 packet, where a control plane and a forwarding plane are combined to implement a network slicing function. The control plane realizes a port-level coarse-grained slicing function by using FlexAlgo and determines a traffic forwarding physical path.

The embodiment of the invention can allocate different Network slices for different user services by using Software Defined Network (SDN) controller or Network management system planning configuration, carry the slice ID information in the header of an IPv6 message, for example, in a FlowLabel (FlowLabel) field of the IPv6 header, and forward the information according to the slice ID and FlexAlgo, for example, obtain corresponding Resource ID information according to the combination of the slice ID and the FlexAlgo information, and match the corresponding link Resource, thereby finally realizing the user-level Network slicing function.

In the embodiment of the invention, the slice ID is carried in the IPv6 header. As shown in fig. 3, 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 in the network layer. The FlowLabel field may be used for traffic load sharing. Preferably, the slice ID is carried in the FlowLabel field, i.e. the slice ID is carried by using part of bits of the FlowLabel field, which has the following advantages:

1) At present, 20 bits specified by FlowLabel are not practically used in most chips. A partial field may be divided to carry a slice ID. The length of the specific field can be actually determined according to the number of the slices and the application digit of the FlowLabel chip. For example, if the lower 12 bits of the FlowLabel are currently used in practical applications for part of the chip, the upper 8 bits of the FlowLabel can be used to carry the slice ID. FIG. 4 gives an example of using the FlowLabel high 8 bits to carry the slice ID.

2) Even if the device chip in the network uses all 20 bits of the FlowLabel for load sharing, the embodiment of the invention is forward compatible, reduces the number of HASH bits for load sharing, only influences the discrete degree of load sharing, reduces the flow load sharing effect to a certain extent, but does not influence the actual flow receiving and sending.

3) The FlowLabel field has a hop-by-hop attribute in an IPv6 message header, so that the requirement of slice hop-by-hop processing is met, efficient analysis can be realized, and the phenomenon that the message processing efficiency is reduced by adding a slice ID is avoided.

In the embodiment of the present invention, in the same FA plane, according to user service characteristics, such as characteristics of a Virtual Local Area Network (VLAN), a Virtual Private Network (VPN), a Differential Service Code Point (DSCP), and the like, a global planning Slice ID (Slice ID) may be allocated to a corresponding user service and carried in a FlowLabel field of an IPv6 packet header by using an SDN controller or a network management system.

For example, sliceids allocated under the two FA planes of the divided FA 128 and the FA 129 in fig. 2 are shown in fig. 5, where in fig. 5, CE represents a Customer Edge device (Customer Edge); a1::1 and B1::1 correspond to two different FA planes (FA 128 and FA 129) of device 1, respectively, and similarly, A2::1 and B2::1 correspond to two different FA planes (FA 128 and FA 129) of device 2, respectively; a3::1 and B3::1 correspond to two different FA planes (FA 128 and FA 129) of the device 3, respectively; a4::1 and B4::1 correspond to two different FA planes (FA 128 and FA 129) of the device 4, respectively. Different VPN user services corresponding to the FA 128 are assigned with different sliceids, different VPN users corresponding to the FA 129 are assigned with different sliceids, and Slice ID assignments between the FA 128 and the FA 129 are independent from each other and have no association relationship, that is, the FA 128 and the FA 129 may have the same Slice ID but respectively correspond to different user services.

The embodiment of the invention can combine the FA ID and the Slice ID to form a final Resource identifier (Resource ID), and the Resource ID is used for identifying the actual link Resource information on the forwarding equipment. As an example of the combination manner, specifically:

Resource ID＝FA ID<<8+Slice ID

the formula shows that the FA ID is spliced with Slice ID after being shifted to the left by 8 bits to obtain Resource ID.

Taking fig. 5 as an 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).

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

One link may belong to different FA planes at the same time, and at this time, the link belonging to different FA planes needs to allocate corresponding physical resources to each FA to ensure physical resources of different FA flows.

It should be noted that the resource ID of a service corresponds to a slice allocated to the service under the FA plane to which the service belongs. The FA plane may be indicated with an FA ID. That is, 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 identifications, and when having the same slice identification, the FA planes to which they respectively belong are different, i.e., correspond to different FA IDs, respectively. The splicing of the FA ID slice IDs allocated to the service to obtain the resource ID of the service is only one example of generating the resource ID, and other manners may also be adopted in the embodiment of the present invention, for example, the controller sets an index corresponding to each combination in advance for all combinations of the FA ID and the slice ID, and takes the index as the resource ID.

Taking fig. 5 as an example, the SDN controller determines, according to VPN information of a user service, a FlexAlgo plane to which the user service belongs and a required physical resource. Slice IDs are assigned to the user traffic within the FlexAlgo plane. The information is issued to Provider Edge router (PE) devices by an SDN controller, and a slice planning table shown in table 1 is formed.

TABLE 1 slicing planning Table

In table 1, flexAlgo ID indicates the FA plane, and the resource information indicates the required physical resource.

The SDN controller converts the FlexAlgo ID and the slice ID planned in table 1 into a corresponding Resource ID (according to the splicing method described above), allocates (configures) physical resources for the forwarding device interface, and the forwarding device plans the physical resources according to the configuration, for example, by using a g.mtn hard slicing technique, associates the physical resources to a corresponding g.mtn subinterface, and finally forms a slice forwarding table on the forwarding device. The slice forwarding tables formed on device 1 and device 3 are shown in table 2 and table 3, respectively. In tables 2 and 3, the egress interface represents a physical egress interface of the packet on the forwarding device, the FlexAlgo ID represents an FA plane, the resource information represents a required physical resource, and the resource interface represents a virtual sub-interface divided under the physical egress interface, where the virtual sub-interface is associated with the physical resource.

Table 2-slice forwarding table for device 1

Outlet interface	FlexAlgo ID	Section 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

Table 3-slice forwarding table for device 3

Fig. 6 provides a flow of a method for forwarding an SRv6 packet, which is applied to a forwarding device according to an embodiment of the present invention. The forwarding device may specifically be an operator backbone router (P) device or an operator edge router (PE) device, as shown in fig. 6, where the method includes:

step 61, when forwarding the first SRv6 packet of the first service, the forwarding device parses a first slice ID from the IPv6 header of the first SRv6 packet, searches an SR forwarding table entry, and determines a first physical egress interface and a first FA ID corresponding to the first SRv6 packet.

Here, the embodiment of the present invention carries the slice ID of the service in the IPv6 header, and can obtain the slice ID of the service by analyzing the IPv6 header. Preferably, the slice ID may be carried in the FlowLabel field in the IPv6 header.

Step 62, according to the first physical outgoing interface, the first FA ID, and the first slice ID, searching a locally maintained slice forwarding table, and determining a first resource interface corresponding to the first SRv6 packet.

Here, the forwarding device in the embodiment of the present invention locally maintains a slice forwarding table, where the table records a correspondence between a physical outbound interface, an FA ID, a slice ID, and a resource interface. Each corresponding relation corresponds to a forwarding table entry of a service, wherein the physical output interface represents a physical output interface of the service on forwarding equipment; the FA ID represents an FA plane; the slice ID indicates the network slice to which the service is assigned; the resource interface is a virtual sub-interface under the physical output interface, the virtual sub-interface being associated with physical resources required by the first service.

Step 63, sending the first SRv6 packet through the first resource interface;

through the steps, the embodiment of the invention realizes the partition resource isolation of the user service level. From the above, it can be seen that the embodiments of the present invention have at least the following advantages:

1. the embodiment of the invention adopts hierarchical network slicing, and not only can realize the resource isolation between physical interfaces, but also can realize the slicing resource isolation in the same interface by combining a control plane and a forwarding plane.

2. The forwarding layer of the embodiment of the invention associates the slice ID with the physical link resource, thereby realizing resource isolation under the same physical interface. The forwarding surface is added with a slice information table look-up forwarding flow, other operations are not involved, and the influence on the system performance is small.

3. According to the embodiment of the invention, the FA ID and the slice ID are combined to obtain the resource ID finally matched with the physical resource, so that the problem of small ranges of FlexAlgo ID and slice ID is effectively solved, and the actual number of slices is increased. Taking FlowLabel as an example, which can occupy 8 bits, the number of slices that can be supported finally is 32768 (128 × 256).

The forwarding device can also perform different table entry maintenance operations according to different identity roles of the forwarding device. The following description will be made separately.

1. The forwarding device is a P device

When the forwarding device is a P device, the forwarding device may further receive information sent by a controller (including an SDN controller and a network manager), and locally maintain a slice forwarding table. Specifically, before the step 61:

1) The forwarding device may receive configuration information of a physical resource sent by the controller, where the configuration information of the physical resource includes a first physical outgoing interface, a first FA ID, a first slice ID of the first service on the forwarding device, and the physical resource of the first service configured on the first physical outgoing interface, and the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice allocated to the first service by the controller, respectively.

2) And the forwarding equipment associates the physical resource of the first service configured on the first physical output interface with a first resource interface under the physical output interface.

3) And the forwarding equipment maintains the slice forwarding table according to the first physical outgoing interface, the first FA ID, the first slice ID and the first resource interface, wherein the slice forwarding table records the corresponding relation among the physical outgoing interface, the FA ID, the slice ID and the resource interface of each service.

Optionally, the configuration information of the physical resource may further include first physical resource requirement information of the first service and a resource ID of the first service, where the resource ID of the first service corresponds to a 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, at least one of the resource ID of the first service and the first physical resource requirement information may also be recorded in the slice forwarding table. As an implementation manner, the resource ID may be obtained by concatenation of an FA ID and a slice ID. Of course, the resource ID may also be generated in other manners, and is an identifier corresponding to each combination of the FA ID and the slice ID.

2. The forwarding device is a PE device

When the forwarding device is a PE device, the forwarding device may further receive information sent by a controller (including an SDN controller and a network manager), and locally maintain a slice planning table and a slice forwarding table. Specifically, before the above step 61:

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 a first FlexAlgo plane and a first slice allocated by the controller for the first service, respectively.

2) And maintaining the slice planning table according to the first VPN to which the first service belongs, the first FA ID and the first slice ID, wherein the slice planning table records the corresponding relation among the FA ID, the VPN ID and the slice ID of each service.

Optionally, the forwarding device may further receive first physical resource demand information of the first service sent by the controller, and then record the first physical resource demand information of the first service in the slice planning table when maintaining the slice planning table.

3) Receiving configuration information of physical resources sent by the controller, where the configuration information of the physical resources includes a first physical outgoing 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 outgoing interface.

4) And associating the physical resource of the first service configured on the first physical output interface to a first resource interface under the physical output interface.

5) And maintaining a slice forwarding table according to the first physical outgoing interface, the first FA ID, the first slice ID and the first resource interface, wherein the slice forwarding table records the corresponding relation among the physical outgoing interface, the FA ID, the slice ID and the resource interface of each service.

Optionally, the configuration information of the physical resource further includes first physical resource requirement information of the first service; in this way, when the forwarding device maintains the slice forwarding table, at least one of the resource ID of the first service and the first physical resource requirement information may also be recorded in the slice forwarding table, where the resource ID is obtained by splicing the FA ID and the slice ID.

In addition, when the forwarding device is a PE device, the forwarding device may further encapsulate the SRv6 packet and fill the slice ID, specifically, before forwarding the first SRv6 packet of the first service in step 61, the forwarding may receive the first packet of the first service sent by the CE device at the user edge; then, according to a first VPN to which the first service belongs, searching the slice planning table to obtain a first slice ID corresponding to the first VPN; then, according to the SRv6 format, an SR header is encapsulated for the first packet, and the first slice ID is added to the IPv6 header, so as to generate the first SRv6 packet.

Fig. 7 shows a relevant configuration operation of a controller (which may be an SDN controller or a network manager) in an embodiment of the present invention, and as shown in fig. 7, the configuration method of an SRv6 packet provided in the embodiment of the present invention, when applied to the controller, includes:

step 71, the controller allocates a first FlexAlgo plane and a first slice under the first FlexAlgo plane for the first service, and determines first physical resource demand information of the first service.

Here, the controller may plan the FlexAlgo planes to which different services belong in advance, and may specifically perform partitioning according to service features. In this way, the controller may assign a certain FA plane (assumed as the first FlexAlgo plane) to the first service according to a predetermined plan. Then, the controller may also allocate a first slice under a first FlexAlgo plane to the first service according to the service characteristics of the first service, and determine first physical resource requirement information of the first service. Here, the service feature includes at least one of a VLAN, a VPN, and a DSCP to which the service belongs.

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.

Step 73, the controller configures the physical resource of the first service for the physical outgoing interface of each forwarding device of the first service according to the first physical resource requirement information, and sends configuration information of the physical resource to the forwarding device, where the configuration information of the physical resource includes the physical outgoing interface, the first FA ID, the first slice ID, and the physical resource of the first service configured on the physical outgoing interface, and the forwarding device includes the PE device and the P device of the first service.

Through the steps, the controller configures the relevant information which can be used for generating the slice forwarding table for the forwarding equipment, thereby providing support for realizing the isolation of the slice resources at the user service level.

In this embodiment of the present invention, the controller may further 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 in the slice planning table.

Similarly, the controller may generate a resource ID for a first service, where the resource ID for the first service corresponds to a first slice ID under the first FA ID, and different resource IDs correspond to different combinations of FA IDs and slice IDs. The specific generation manner of the resource ID may be generated by splicing the FA ID and the slice ID, or an index corresponding to a combination of each FA ID and the slice ID may be pre-established, and the index is used as the resource ID corresponding to the combination, and so on.

In this way, the controller may further carry, in the configuration information of the physical resource sent to the forwarding device, the first physical resource requirement information of the first service and the resource ID of the first service, so that the forwarding device may add at least one of the resource ID of the first service and the first physical resource requirement information in the slice forwarding table.

The method of the embodiment of the present invention is described above from the forwarding devices (PE device and P device) and the controller side, respectively. It can be seen that, since the slice ID is carried in the IPv6 packet header (the FLowLabel field), the embodiment of the present invention naturally supports IPv6 forwarding and SRv6 forwarding, and fig. 8 provides schematic diagrams of an apparatus processing process and forwarding layer packet encapsulation by taking SRv6Policy forwarding as an example.

Wherein, at the forwarding device corresponding to the PE device, i.e. A1::1 in FIG. 8, the following steps are executed:

901. inheriting an SRv6Policy encapsulation mode and encapsulating the message.

902. And according to the table 1, namely a slice planning table, encapsulating the corresponding slice ID into an IPv6 message FlowLabel field.

903. And searching an SR forwarding table entry according to an SRv6 forwarding mechanism, and confirming a physical output interface and a FlexAlgo ID.

904. And searching a table 2-slice forwarding table according to the physical output interface, the FlexAlgo ID and the slice ID, acquiring a resource interface, and forwarding the message according to the resource information.

At the P device, i.e., the forwarding device corresponding to A2::1 and A3::1 in FIG. 8, the following steps are performed:

911. and searching an SR forwarding table entry according to an SRv6 forwarding mechanism, and confirming a physical output interface and a FlexAlgo ID.

912. And analyzing the slice ID in the IPv6 message header, searching a 'table 2-slice forwarding table' according to the physical output interface, the FlexAlgo ID and the slice ID, acquiring a resource interface, and forwarding the message according to resource information.

At the egress device, namely the forwarding device corresponding to A4::1 in FIG. 8, the following steps are performed:

921. decapsulating the message according to the SRv6 forwarding mechanism

Various methods of embodiments of the present invention have been described above. An apparatus for carrying out the above method is further provided below.

Referring to fig. 9, an embodiment of the present invention provides a forwarding device, including:

the analysis module 91 is configured to, when forwarding a first SRv6 packet of a first service, analyze a first slice ID from an IPv6 header of the first SRv6 packet, search a segment routing SR forwarding table entry, and determine a first physical egress interface and a first flexible algorithm identifier FA ID corresponding to the first SRv6 packet;

a searching module 92, configured to search a locally maintained slice forwarding table according to the first physical outgoing interface, the first FA ID, and the first slice ID, and determine a first resource interface corresponding to the first SRv6 packet;

a forwarding module 93, configured to send the first SRv6 packet through the first resource interface;

the slice forwarding table maintains the corresponding relationship among the physical outbound interface, the FA ID, the slice ID and the resource interface.

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

a first receiving module, configured to receive configuration information of a physical resource sent by the controller, where the configuration information of the physical resource includes a first physical outgoing interface, a first FA ID, a first slice ID of the first service on the forwarding device, and a physical resource of the first service configured on the first physical outgoing interface, and the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice allocated by the controller for the first service, respectively;

a first configuration module, configured to associate a physical resource of the first service configured on the first physical output interface with a first resource interface under the physical output interface;

and the first maintenance module is used for maintaining the slice forwarding table according to the first physical outgoing interface, the first FA ID, the first slice ID and the first resource interface, wherein the slice forwarding table records the corresponding relation among the physical outgoing interface, the FA ID, the slice ID and the resource interface of each service.

Preferably, the forwarding device is an operator edge router PE of the first service, and the forwarding device further includes:

the second receiving module is used for receiving a first FA ID and a first slice ID which are sent by the controller, wherein the first FA ID and the first slice ID are respectively an identifier of a first FlexAlgo plane and a first slice which are distributed by the controller for a first service;

a second maintenance module, configured to maintain the slice planning table according to the first VPN to which the first service belongs, the first FA ID, and the first slice ID, where a correspondence relationship among the FA ID, the VPN ID, and the slice ID of each service is recorded in the slice planning table;

a third receiving module, configured to receive configuration information of a physical resource sent by the controller, where the configuration information of the physical resource includes a first physical outgoing interface, a first FA ID, a first slice ID of the first service on the forwarding device, and a physical resource of the first service configured on the first physical outgoing interface;

a second configuration module, configured to associate the physical resource of the first service configured on the first physical output interface with the first resource interface under the physical output interface;

and a third maintenance module, configured to maintain a slice forwarding table according to the first physical outgoing interface, the first FA ID, the first slice ID, and the first resource interface, where the slice forwarding table records a correspondence between the physical outgoing interface, the FA ID, the slice ID, and the resource interface of each service.

Preferably, the forwarding device further includes:

the device comprises an encapsulation module, a service forwarding module and a service forwarding module, wherein the encapsulation module is used for receiving a first message of a first service sent by a user edge (CE) device before forwarding the first SRv6 message of the first service; searching the slice planning table according to a first VPN to which the first service belongs, and acquiring a first slice ID corresponding to the first VPN; and according to an SRv6 format, packaging an SR header for the first message, and adding the first slice ID in the IPv6 header to generate the first SRv6 message.

Preferably, the forwarding device further includes:

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

and the fourth maintenance module is used for recording the first physical resource demand information of the first service in the slicing planning table when the slicing planning table is maintained.

Preferably, 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, where the resource ID of the first service corresponds to a first slice ID under the first FA ID; the forwarding device further comprises:

and a fifth maintaining module, configured to record at least one of the resource ID of the first service and the first physical resource requirement information in the slice forwarding table when the slice forwarding table is maintained.

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

Preferably, the resource ID of the first service is obtained by splicing the first FA ID and the first slice ID.

It should be noted that the apparatus in this embodiment is an apparatus corresponding to the method shown in fig. 6, and the implementation manners in the above embodiments are all applicable to the embodiment of this apparatus, and the same technical effects can be achieved. The device provided by the embodiment of the present invention can implement all the method steps implemented by the method embodiment, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are not repeated herein.

Referring to fig. 10, an embodiment of the present invention provides a structural schematic diagram of a forwarding device, including: a processor 1001, a transceiver 1002, a memory 1003, and a bus interface, wherein:

in this embodiment of the present invention, the forwarding device further includes: a program stored on the memory 1003 and executable on the processor 1001, which when executed by the processor 1001 performs the steps of:

when a first SRv6 message of a first service is forwarded, a first slice ID is analyzed from an IPv6 header of the first SRv6 message, a Segmented Routing (SR) forwarding table entry is searched, and a first physical output interface and a first flexible algorithm identification (FA ID) corresponding to the first SRv6 message are determined;

sending the first SRv6 message through the first resource interface;

The forwarding device is an operator backbone router P device of the first service, and the processor further implements the following steps when executing the program:

before forwarding a first SRv6 packet, receiving configuration information of a physical resource sent by the controller, where the configuration information of the physical resource includes a first physical outgoing interface, a first FA ID, a first slice ID of the first service on the forwarding device, and a physical resource of the first service configured on the first physical outgoing interface, and the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice allocated by the controller to the first service, respectively;

and maintaining the slice forwarding table according to the first physical outgoing interface, the first FA ID, the first slice ID and the first resource interface, wherein the slice forwarding table records the corresponding relation among the physical outgoing interface, the FA ID, the slice ID and the resource interface of each service.

Optionally, the forwarding device is an operator edge router PE of the first service, and the processor further implements the following steps when executing the program:

before forwarding a first SRv6 message, receiving a first FA ID and a first slice ID sent by a controller, wherein the first FA ID and the first slice ID are respectively identifiers of a first FlexAlgo plane and a first slice allocated to a first service by the controller;

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

before forwarding a first SRv6 message of a first service, receiving a first message of the first service sent by a Customer Edge (CE) device;

Optionally, 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, where the resource ID of the first service corresponds to a first slice ID under the first FA ID; the processor, when executing the program, further implements the steps of:

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 recorded in the slice forwarding table.

Optionally, the resource ID of the first service is obtained by splicing the first FA ID and the first slice ID.

Optionally, the first slice ID is carried in a FlowLabel field in an IPv6 header.

It can be understood that, in the embodiment of the present invention, when the computer program is executed by the processor 1001, each process of the method embodiment shown in fig. 6 can be implemented, and the same technical effect can be achieved.

In fig. 10, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 1001 and various circuits of memory represented by memory 1003 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1002 may be a number of elements including a transmitter and receiver that provide a means for communicating with various other apparatus over a transmission medium.

The processor 1001 is responsible for managing a bus architecture and general processes, and the memory 1003 may store data used by the processor 1001 in performing operations.

It should be noted that the terminal in this embodiment is a device corresponding to the method shown in fig. 6, and the implementation manners in the foregoing embodiments are all applied to the embodiment of the terminal, and the same technical effects can be achieved. In the apparatus, the transceiver 1002 and the memory 1003, and the transceiver 1002 and the processor 1001 may be communicatively connected through a bus interface, and the function of the processor 1001 may also be implemented by the transceiver 1002, and the function of the transceiver 1002 may also be implemented by the processor 1001. It should be noted that, the apparatus provided in the embodiment of the present invention can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.

In some embodiments of the invention, there is also provided a computer readable storage medium having a program stored thereon, the program when executed by a processor implementing the steps of:

sending the first SRv6 message through the first resource interface;

When being executed by the processor, the program can realize all the implementation modes in the method for forwarding the SRV6 packet applied to the forwarding device, and can achieve the same technical effect, and is not described herein again to avoid repetition.

An embodiment of the present invention provides a controller shown in fig. 11, including:

a first configuration module 111, configured to allocate, by a controller, a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane for a first service, and determine first physical resource requirement information of the first service; sending the first FA ID of the first FlexAlgo plane and the first slice ID of the first slice to the PE equipment of the provider edge router of the first service;

a second configuration module 112, configured to configure, according to the first physical resource demand information, a physical outgoing interface of each forwarding device of the first service with a physical resource of the first service, and send configuration information of the physical resource to the forwarding device, where the configuration information of the physical resource includes the physical outgoing interface, a first FA ID, a first slice ID, and a physical resource of the first service configured on the physical outgoing interface, and the forwarding device includes a PE device of the first service and a provider backbone router P device.

Optionally, the first configuration module 111 is further configured to allocate a FlexAlgo plane for the first service; according to the service characteristics of a first service, a first slice under a first FlexAlgo plane is distributed for the first service, and first physical resource requirement information of the first service is determined, wherein the service characteristics comprise at least one of a Virtual Local Area Network (VLAN), a Virtual Private Network (VPN) and a Differentiated Services Code Point (DSCP).

Optionally, the controller further includes:

a first sending module, configured to send the first physical resource requirement information of the first service to the PE device of the first service.

Optionally, the controller further includes:

an identifier generating module, configured to generate a resource ID of the first service, where the resource ID of the first service corresponds to a first slice ID under the first FA ID;

It should be noted that the apparatus in this embodiment is a device corresponding to the method shown in fig. 7, and the implementation manners in the above embodiments are all applicable to the embodiment of this device, and the same technical effects can be achieved. It should be noted that, the apparatus provided in the embodiment of the present invention can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.

Referring to fig. 12, an embodiment of the invention provides a structural schematic diagram of a controller, including: a processor 1201, a transceiver 1202, a memory 1203, and a bus interface, wherein:

in an embodiment of the present invention, the controller further includes: a program stored on the memory 1203 and executable on the processor 1201, which when executed by the processor 1201, performs the steps of:

allocating a first flexible algorithm FlexAlgo plane and a first slice under the first FlexAlgo plane for a first service, and determining first physical resource demand information of the first service;

allocating a first flexible algorithm FlexAlgo plane for the first service;

and sending the first physical resource demand information of the first service to the PE equipment of the first service.

generating 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;

It can be understood that, in the embodiment of the present invention, when being executed by the processor 1201, the computer program can implement the processes of the method embodiment shown in fig. 7, and can achieve the same technical effect, and details are not described here to avoid repetition.

In fig. 12, the bus architecture may include any number of interconnected buses and bridges, with various circuits linking one or more processors, represented by the processor 1201, and memory, represented by the memory 1203. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1202 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

The processor 1201 is responsible for managing a bus architecture and general processing, and the memory 1203 may store data used by the processor 1201 in performing operations.

It should be noted that the terminal in this embodiment is a device corresponding to the method shown in fig. 7, and the implementation manners in the above embodiments are all applicable to the embodiment of the terminal, and the same technical effects can be achieved. In the device, the transceiver 1202 and the memory 1203, and the transceiver 1202 and the processor 1201 may be communicatively connected by a bus interface, the functions of the processor 1201 may also be implemented by the transceiver 1202, and the functions of the transceiver 1202 may also be implemented by the processor 1201. It should be noted that the apparatus provided in the embodiment of the present invention can implement all the method steps implemented by the method embodiment, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.

In some embodiments of the invention, there is also provided a computer readable storage medium having a program stored thereon, which when executed by a processor, performs the steps of:

When executed by the processor, the program can implement all implementation manners in the above configuration method for SRV6 messages applied to the controller, and can achieve the same technical effect, and is not described herein again to avoid repetition.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention or a part thereof which substantially contributes to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present invention, and shall cover the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A forwarding method of SRv6 message based on IPv6 segment routing is characterized in that the forwarding method comprises the following steps:

sending the first SRv6 message through the first resource interface;

2. The method of claim 1, wherein the forwarding device is an operator backbone router (P) device for the first service, and prior to forwarding the first SRv6 packet, the method further comprises:

receiving configuration information of physical resources sent by a controller, where the configuration information of the physical resources includes a first physical outgoing interface, a first FA ID, a first slice ID of the first service on the forwarding device, and the physical resources of the first service configured on the first physical outgoing interface, and the first FA ID and the first slice ID are identifiers of a first FlexAlgo plane and a first slice allocated to the first service by the controller, respectively;

3. The method of claim 1, wherein the forwarding device is an operator edge router PE of the first service, and prior to forwarding the first SRv6 packet, the method further comprises:

4. The method of claim 3, wherein prior to forwarding the first SRv6 packet of the first service, the method further comprises:

and according to the SRv6 format, packaging an SR header for the first message, and adding the first slice ID in the IPv6 header to generate the first SRv6 message.

5. The method of any of claims 3 to 4, further comprising:

when maintaining the slice planning table, first physical resource demand information of the first service is also recorded in the slice planning table.

6. The method of any of claims 2 to 4, wherein the configuration information of the physical resources further comprises 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;

7. The method of claim 6, wherein the resource ID of the first service is concatenated from the first FA ID and a first slice ID.

8. The method of any one of claims 1 to 4, wherein the first slice ID is carried in a flow Label FlowLabel field in an IPv6 header.

9. A method for configuring an SRv6 message based on IPv6 segment routing is characterized by comprising the following steps:

10. The method according to claim 9, wherein the controller allocates a first FlexAlgo plane and a first slice below the first FlexAlgo plane for the first service, and determines first physical resource requirement information of the first service, specifically:

according to the service characteristics of a first service, a first slice under a first FlexAlgo plane is distributed for the first service, and first physical resource demand information of the first service is determined, wherein the service characteristics comprise at least one of a Virtual Local Area Network (VLAN), a Virtual Private Network (VPN) and a Differential Service Code Point (DSCP).

11. The method of claim 9 or 10, further comprising:

12. The method of claim 11, further comprising:

13. The method of claim 12, wherein the resource ID of the first service is concatenated from the first FA ID and a first slice ID.

14. A forwarding device, comprising:

15. A forwarding device comprising a transceiver and a processor, wherein,

16. A forwarding device, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method according to any one of claims 1 to 8.

17. A controller, comprising:

18. A controller comprising a transceiver and a processor, wherein,

19. A controller, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method according to any of claims 9 to 13.

20. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 13.