WO2022110535A1 - Packet sending method, device, and system - Google Patents

Abstract

Disclosed are a packet sending method and a related device, used for reducing the number of traffic engineering tunnels in a network, and avoiding complex configuration or management. The present application comprises the packet sending method, comprising: a network device obtains a first packet, an Internet protocol extension header of the first packet comprising a first identifier, and the first identifier being used for indicating a service requirement corresponding to the first packet; the network device determines, according to the first identifier and a second identifier, path indication information corresponding to the first packet, a destination address of the first packet comprising the second identifier, and the path indication information here comprising one or more of a network slice identifier and a segment identifier list; and the network device updates the first packet on the basis of the path indication information to obtain a second packet, and sends the second packet.

Description

A message sending method, device and system

This application claims the priority of the Chinese patent application filed on November 27, 2020, with the application number 202011368375.5 and the application name "A data processing method, device and system", all of this Chinese patent application The contents are incorporated herein by reference.

technical field

The present application relates to the field of communication technologies, and in particular, to a method, device, apparatus, system, and computer-readable storage medium for sending a message.

Background technique

In some scenarios, such as cloud computing scenarios, by distributing computing tasks on a resource pool composed of a large number of computers, various application systems can obtain computing power, storage space and various software services as needed. In a cloud computing system, a cloud server can be centrally deployed, and an application system can run on the cloud server for users, such as individual users or enterprise users, to access the cloud server through terminals.

The way that users access the cloud server through the terminal is usually: the operator establishes an end-to-end connection tunnel between the metropolitan area network connected to the user terminal and the backbone network where the cloud service is located, so that the user can access the cloud based on the tunnel. Server, using this tunnel can guarantee the network quality of users.

However, when tunnels are established in this way, different users or different services often need to configure different tunnels or traffic engineering, resulting in a large number of tunnels or traffic engineering tunnels, and the network is complex.

SUMMARY OF THE INVENTION

The present application provides a method, device, device, system and computer-readable storage medium for sending a message to solve the problems in the related art. The technical solutions are as follows:

In a first aspect, a method for sending a message is provided, which includes: a first network device obtains a first message, and an Internet Protocol (Internet Protocol, IP) extension header of the first message includes a first identifier, the first An identifier is used to indicate the service requirement corresponding to the first packet. After obtaining the first packet, the first network device may determine the path indication information corresponding to the first packet based on the first identifier and the second identifier. The destination address of the first packet includes the second identifier, and the path here is The indication information includes: a network slice identifier and/or a segment identifier list. The first network device updates the first packet based on the path indication information to obtain the second packet, and sends the second packet.

By determining the path indication information corresponding to the packet according to the first identifier and the second identifier corresponding to the service requirement in the obtained packet, such as the network slice identifier and/or the segment identifier list, the packet can be identified according to the corresponding network slice or segment identifier list. The forwarding tunnel indicated by the segment identifier list is used for forwarding, which can reduce the configuration of the tunnel in the network and simplify the network.

In a possible implementation manner, the second identification includes a segment identification. In one example, the segment identification is a VPN segment identification or an intent segment identification.

In a possible implementation manner, the above-mentioned method for determining path indication information based on the first identifier and the second identifier is: determining a forwarding policy for the first packet based on the second identifier, where the forwarding policy includes the first identifier and the path indication The first corresponding relationship of information; the above-mentioned path indication information is determined based on the first identifier and the first corresponding relationship.

In a possible implementation manner, the above-mentioned method for determining path indication information based on the first identifier and the second identifier is: determining a third identifier corresponding to the first identifier based on the first identifier; determining a forwarding policy of the first packet based on the second identifier , the forwarding strategy includes a second correspondence between the third identifier and the path indication information; and the path indication information is determined based on the third identifier and the second correspondence.

In a second aspect, a method for sending a message is provided, the method includes: a first network device obtains a first message, an Internet Protocol IP header of the first message includes a first identifier, and the first identifier is used to indicate the service requirement corresponding to the first packet; after obtaining the first packet, the first network device determines the corresponding path indication information based on the first identifier, where the path indication information includes: a network slice identifier; One message gets the second message, and sends the second message.

In a possible implementation manner, the first network device includes a correspondence between the first identifier and the path indication information, and the above-mentioned implementation manner of determining the corresponding path indication information based on the first identifier is: based on the first identifier and this correspondence The relationship determines the path indication information.

In a possible implementation manner, the first identifier includes a network slice identifier, and the first identifier instructs the first network device to determine the network slice identifier based on the first identifier.

With reference to the second aspect or any possible implementation manner of the first aspect, in a possible implementation manner, the second packet includes the above path indication information. In a possible implementation, the path indication information is a network slice identifier, and the above-mentioned network slice identifier is included in the HBH or destination option header of the second packet.

With reference to the second aspect or any possible implementation manner of the first aspect, in a possible implementation manner, the first identifier includes a segment identifier, and the segment routing header SRH of the first packet includes the first identifier, The IP extension header includes the above-mentioned SRH.

With reference to the second aspect or any possible implementation manner of the first aspect, in a possible implementation manner, the first identifier includes an intent segment identifier, and the intent segment identifier is used to instruct the first network device to determine based on the first identifier Corresponding path indication information. In a possible implementation manner, the first identifier further includes an indicator identifier, where the indicator identifier is used to indicate that the first identifier is an intent segment identifier.

In a third aspect, a method for sending a message is provided, the method includes: a first network device obtains a first message, a hop-by-hop option header HBH or a destination option header of the first message includes a first identifier, and the first An identifier is used to indicate the service requirement corresponding to the first packet; after obtaining the first packet, the first network device can determine the path indication information corresponding to the first packet based on the first identifier, where the path indication information includes: a segment identifier list. The first network device updates the first packet based on the segment identifier list to obtain a second packet, and sends the second packet.

In a possible implementation manner, the second packet includes the segment identifier list.

In a possible implementation manner, the first identifier includes an intent identifier, an HBH or a destination option header of the first packet includes the intent identifier, and the IP extension header includes an HBH or a destination option header.

With reference to any possible implementation manner of the first aspect, the second aspect or the third aspect, the obtaining of the first packet by the first network includes: the first network device receives the packet sent by the second network device, and the first network device receives the packet sent by the second network device. The message includes the first identifier. The first packet is a packet sent by the second network device, or the first network device may generate the first packet based on the packet sent by the second network device. The first network device belongs to the first network, the second network device belongs to the second network, and the first network is different from the second network.

In a possible implementation manner, at least two network devices included in the above-mentioned first network may perform determining corresponding path indication information based on the first identifier, and the at least two network devices include the above-mentioned first network device.

In a possible implementation manner, at least two network devices included in the second network may also perform determining the corresponding path indication information based on the first identifier.

In a possible implementation manner, the first network and the second network belong to different interior gateway protocol IGP domains, or the first network and the second network belong to different autonomous systems AS.

In a possible implementation manner, the first network is a network that supports network slicing, and the second network is a network that supports SRv6.

In a possible implementation manner, the network slice identifier includes a slice identifier SliceID and/or a flexible algorithm identifier.

In a fourth aspect, a method for sending a message is provided, the method comprising: obtaining a first identifier by a first network device, where the first identifier corresponds to a service requirement; and generating a first message by the first network device, the first message The IP extension header of the Internet Protocol includes a first identification, the first packet also includes a second identification, the destination address of the first packet includes the second identification or the segment routing header SRH of the first packet includes the second identification ; The first network device sends the first message to the second network device, and the first identifier and the second identifier in the first message are used to enable the second network device to determine the correspondence of the first message based on the first identifier and the second identifier path indication information, where the path indication information includes a list of network slice identifiers and/or segment identifiers.

In a possible implementation manner, the second identifier includes a virtual private network segment identifier VPN SID or an intent segment identifier.

In a possible implementation manner, the hop-by-hop option header or the destination option header of the first packet includes the first identifier.

A fifth aspect provides a method for sending a message, the method comprising: obtaining a first identifier by a first network device, where the first identifier corresponds to a service requirement; and generating a first message by the first network device, and the first message is The hop-by-hop option header HBH or the destination option header includes a first identifier; the first network device sends a first packet to the second network device, where the first identifier is used to enable the second network device to determine the first packet based on the first identifier Corresponding path indication information, where the path indication information includes a first segment identifier list.

In a possible implementation manner, the first identification includes an intent identification.

In a possible implementation manner, the above-mentioned obtaining the first identifier is specifically: the first network device receives the second segment identifier list sent by the control device, and the second segment identifier list includes the first identifier.

A sixth aspect provides a method for sending an identifier, the method comprising: a control device obtaining a first identifier, the first identifier corresponding to a service requirement; determining a first segment identifier list corresponding to the target service, where the first segment identifier list is Including a first identifier, the first segment identifier list is used to indicate the first forwarding path through which the message corresponding to the target service passes, the first forwarding path passes through the first network device included in the first network, and the first identifier is used for The first network device is made to determine corresponding path indication information based on the first identifier, where the path indication information includes: a network slice identifier and\or a second segment identifier list; the first network device sends the first segment identifier list.

In a possible implementation manner, at least two network devices included in the first network may perform determining corresponding path indication information based on the first identifier, and the at least two network devices included in the first network include the above-mentioned first network device.

In a possible implementation manner, the first segment identifier list is carried in a link state protocol packet or a path calculation unit communication protocol packet and sent.

A seventh aspect provides a network device, the network device includes: an obtaining module, a processing module, and a sending module, the obtaining module is used to obtain a first packet, and the Internet Protocol IP extension header of the first packet includes the first packet. an identifier, the first identifier is used to indicate the service requirement corresponding to the first packet; the processing module is used to determine the path indication information corresponding to the first packet based on the first identifier and the second identifier, and the The destination address includes a second identifier, and the path indication information includes: a network slice identifier and/or a segment identifier list; the processing module is further configured to update the first message based on the path indication information to obtain the second message; the sending module is configured to send Second message.

In a possible implementation manner, the processing module is configured to: determine a forwarding policy of the first packet based on the second identifier, where the forwarding policy includes a first correspondence between the first identifier and the path indication information; the processing module, further for determining path indication information based on the first identifier and the first correspondence.

In a possible implementation manner, the processing module is configured to: determine a third identifier corresponding to the first identifier based on the first identifier; the processing module is further configured to determine a forwarding policy of the first packet based on the second identifier, where the forwarding policy includes The second correspondence between the third identifier and the path indication information; the processing module is further configured to determine the path indication information based on the third identifier and the second correspondence.

In an eighth aspect, a network device is provided, comprising: an obtaining module, a processing module and a sending module, the obtaining module is used to obtain a first message, and the Internet Protocol IP header of the first message includes the first identifier, the first identifier is used to indicate the service requirement corresponding to the first packet; the processing module is used to determine the corresponding path indication information based on the first identifier, and the path indication information includes: the network slice identifier; the processing module, also used The second message is obtained by updating the first message based on the path indication information; the sending module is used for sending the second message.

In a possible implementation manner, the processing module is configured to: determine the path indication information based on the first identifier and a corresponding relationship, where the corresponding relationship is a corresponding relationship between the first identifier and the path indication information.

In a possible implementation manner, the processing module is configured to: encapsulate the path indication information into the second packet.

In a ninth aspect, a network device is provided, comprising: an obtaining module, a processing module and a sending module, the obtaining module is used to obtain a first packet, the hop-by-hop option header HBH or the destination option header of the first packet is in the Including a first identifier, the first identifier is used to indicate the service requirement corresponding to the first message; the processing module is used to determine the path indication information corresponding to the first message based on the first identifier, and the path indication information includes: a segment identifier list; the sending module is configured to update the first message based on the segment identifier list to obtain the second message, and send the second message.

In a possible implementation manner, the processing module is configured to encapsulate the segment identifier list into the second packet.

A tenth aspect provides a network device, the network device includes: an obtaining module, a processing module and a sending module, the obtaining module is used to obtain a first identifier, the first identifier corresponds to a service requirement; the processing module is configured with In generating the first message, the Internet Protocol IP extension header of the first message includes the first identification, the first message also includes the second identification, and the destination address of the first message includes the second identification or the first identification. The segment routing header SRH of the packet includes a second identifier; the sending module is configured to send the first packet to the second network device, and the first identifier and the second identifier are used to make the second network device based on the first identifier and the second identifier. The second identifier determines path indication information corresponding to the first packet, where the path indication information includes a network slice identifier and/or a segment identifier list.

In an eleventh aspect, a network device is provided, the network device includes an obtaining module, a processing module and a sending module, the obtaining module is used to obtain a first identifier, the first identifier corresponds to a service requirement; the processing module is configured with In generating the first message, the IP header of the first message includes a first identifier; the sending module is used to send the first message to the second network device, and the first identifier is used to make the second network The device determines corresponding path indication information based on the first identifier, where the path indication information includes a network slice identifier.

A twelfth aspect provides a network device, the network device includes an obtaining module, a processing module and a sending module, the obtaining module is used to obtain a first identifier, and the first identifier corresponds to a service requirement; the processing module is configured with For generating the first message, the hop-by-hop option header HBH or the destination option header of the first message includes a first identifier; the sending module is used to send the first message to the second network device, and the first identifier is used The second network device determines corresponding path indication information based on the first identifier, where the path indication information includes a segment identifier list.

A thirteenth aspect, a control device, characterized in that it includes an obtaining module, a processing module and a sending module, the obtaining module is used to obtain a first identifier, and the first identifier corresponds to a service requirement; the processing module is used to obtain a first identifier. Determine the first segment identifier list corresponding to the target service, the first segment identifier list includes a first identifier, and the first segment identifier list is used to indicate the first forwarding path through which the message corresponding to the target service passes, the first forwarding path Passing through the first network device included in the first network, the first identifier is used to enable the first network device to determine corresponding path indication information based on the first identifier, where the path indication information includes: a network slice identifier and\or a list of second segment identifiers ; The sending module is used to send the first segment of the identification list.

In a possible implementation manner, the processing module is configured to: calculate and obtain the above-mentioned first segment identification list according to the service requirements corresponding to the target service.

A fourteenth aspect provides a communication device, the device comprising: a communication interface and a processor. The processor is configured to perform execution to control the communication interface to receive signals, and to control the communication interface to send signals, and when the processor executes the instructions, the processor causes the processor to execute the above-mentioned first to thirteenth aspects or any one of them method in a possible implementation.

In one possible implementation, the communication device further includes a memory. The memory is used to store the above-mentioned instructions.

In a possible implementation manner, there are one or more processors and one or more memories.

In one possible implementation, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

A fifteenth aspect provides a communication system, the system includes a first network device and a second network device, the first network device is configured to perform the first aspect - the third aspect or any of the first to third aspects In the method in a possible implementation manner, the second network device is configured to execute the method in any possible implementation manner of the fourth aspect - the sixth aspect or the fourth aspect to the sixth aspect.

A sixteenth aspect provides a computer program (product), the computer program (product) comprising: computer program code, which, when executed by a computer, causes the computer to execute the methods in the above aspects.

A seventeenth aspect provides a computer-readable storage medium, where the computer-readable storage medium stores programs or instructions, and when the programs or instructions are run on a computer, the methods in the above aspects are performed.

In an eighteenth aspect, a chip is provided, including a processor for invoking and executing instructions stored in the memory from a memory, so that a communication device on which the chip is installed performs the methods in the above aspects.

A nineteenth aspect provides another chip, comprising: an input interface, an output interface, a processor, and a memory, the input interface, the output interface, the processor, and the memory are connected through an internal connection path, and the processor is used to execute codes in the memory , when the code is executed, the processor is used to perform the methods in the above aspects.

Description of drawings

1 is a schematic diagram of a network fragmentation provided by the present application;

2 is a schematic diagram of a network fragmentation provided by the present application;

3 is a schematic diagram of a network scenario provided by the present application;

4 is a schematic flowchart of a message sending method provided by the present application;

5 is a schematic flowchart of a message sending method provided by the present application;

6 is a schematic flowchart of a method for sending an identification provided by the present application;

FIG. 7 is a schematic diagram of a path arrangement and processing process performed by a control device provided by the present application;

FIG. 8 is an application example diagram of a message sending method provided by the present application;

FIG. 9 is an application example diagram of a message sending method provided by the present application;

10 is an example diagram of a mapping relationship between an aggregated route and an aggregated tunnel provided by the application;

FIG. 11 is a diagram of an application example of a message sending method provided by the present application;

12 is a schematic structural diagram of a network device provided by this application;

13 is a schematic structural diagram of a network device provided by this application;

14 is a schematic structural diagram of a network device provided by this application;

15 is a schematic structural diagram of a network device provided by this application;

16 is a schematic structural diagram of a network device provided by this application;

FIG. 17 is a schematic diagram of a network system provided by this application.

Detailed ways

In order to enable those skilled in the art to better understand the solution of the present invention, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings and the implementation manner.

Segment Routing (SR): It is a protocol designed to forward packets in the network based on the concept of source routing. SR divides the network path into segments, and assigns segment IDs (Segment IDs, SIDs) to these segments and network nodes. By arranging the SIDs in an orderly manner, the SID List (SID List, also known in SR-MPLS) can be obtained. called label stack), SID List can indicate a forwarding path. Through the SR technology, you can specify the nodes and paths that the data packets carrying the SID List pass through, so as to meet the requirements of traffic optimization. To make an analogy, the data package can be compared to luggage, and SR can be compared to the label attached to the luggage. If you want to send the luggage from area A to area D, and pass through area B and area C, you can send the luggage to area A at the origin. Put a label "first to B area, then to C area, and finally to D area", so that each area only needs to identify the label on the luggage, and forward the luggage from one area to another according to the label of the bag. Can. In the SR technology, the head node will add a label to the data packet, and the intermediate node can forward it to the next node according to the label until the data packet reaches the destination node. For example, if <SID1, SID2, SID3> is inserted in the header of the data packet, the data packet will be forwarded first to the node corresponding to SID1, then to the node corresponding to SID2, and then to the node corresponding to SID3. Among them, the full name of SR-MPLS in Chinese and English is Segment Routing Multi-Protocol Label Switching.

Segment routing (SR v6) based on Internet Protocol Version 6 (IPv6): refers to the application of SR technology in IPv6 networks. Use IPv6 address (128bits) as the representation of SID. When forwarding data packets, network devices that support SRv6 will query the local segment identification table (local SID table) according to the destination address (Destination Address, DA) in the data packet. When any SID of the SID matches the longest, according to the policy related to the SID in the local segment identification table, the operation corresponding to the policy is executed. For example, the data packet can be forwarded from the outbound interface corresponding to the SID; if the destination address of the data packet is If there is no longest match with each SID in the local segment identification table, the IPv6 forwarding table is checked again, and the longest matching forwarding is performed according to the IPv6 forwarding table.

Segment Routing Header (SRH): IPv6 packets are composed of IPv6 standard header + extension header (0...n) + payload. To implement SRv6 based on the IPv6 forwarding plane, a new IPv6 extension header, called the SRH extension header, is added. The extension header specifies an IPv6 explicit path and stores the IPv6 segment list. The head node adds an SRH extension header to the IPv6 packet, and the intermediate node can forward it according to the path information contained in the SRH extension header. Specifically, there are two key pieces of information in the SRH, one is the segment list (Segment List) in the form of IPv6 addresses, which is similar to the label stack information in the multi-protocol label switching (MPLS) network. The Segment List composed of one or more segment IDs (Segment ID, SID) arranged is used to indicate the explicit path in the SR; the other is the remaining segment (Segment Left, SL), SL is a pointer, used to indicate The current segment ID.

Segment ID List (SID List): A list containing a set of segment IDs. After receiving the data packet, the head node in the segment routing network inserts a SID List into the data packet to display the indication. a forwarding path.

In the SRv6 network, the value of the DA field of the IPv6 packet is constantly changing, and its value is determined by the SL and the Segment List. When the pointer SL points to a currently pending segment, for example, when it points to the Segment List[2] , you need to copy the IPv6 address of Segment List[2] to the DA field.

At the forwarding level, if the node supports SR, and the segment ID of the node appears in the destination address in the IPv6 packet, after receiving the packet, the node can decrement the SL by 1 and shift the pointer to A new segment is added, and the corresponding segment identifier (that is, the IPv6 address format) after the SL is reduced by one is copied to the DA field, and the packet is forwarded to the next node. Usually, when the SL field is reduced to 0, the node can pop up the SRH packet header, and then process the packet in the next step. If the node does not support SR, then there is no need to process the SRH information in the IPv6 packet, and it only needs to search the IPv6 routing table based on the IPv6 destination address field and perform ordinary IPv6 forwarding.

SR Policy (SR Policy) is a traffic engineering mechanism of SR. Generally, an SR Policy includes a headend, a color, and an endpoint, as well as a list of segment identifiers that indicate the forwarding path. Among them, Headend is used to identify the head node that executes the SR Policy, Color is used to associate SR with service attributes, such as low latency, high bandwidth and other service attributes, to summarize the service capabilities of the SR Policy, and Endpoint is used to identify The destination address of the SR Policy. Usually, an SR Policy is determined by (headend, color, endpoint). For the same headend, it can also use (color, endpoint) to determine a Policy. The SR policy can include one or more segment ID lists to implement load balancing, multi-path backup and other functions. When forwarding a message, the head node can determine the segment ID list corresponding to the message according to the SR policy, so as to determine the forwarding path for forwarding the message, and encapsulate the segment ID list into the message for explicit or decentralized indication. path.

Service requirements: Service requirements for network quality, which can include one or more of the following: delay range, bandwidth range, packet loss rate range, specifying a certain path/node and specifying not to pass a certain path path/node etc. The above range can be a specific value range, or the range can refer to a certain index being better or optimal in the network. For example, the delay range can be less than or equal to a specific delay value, such as 20 milliseconds, or the delay range. Refers to low latency; the bandwidth range can be greater than or equal to a specific bandwidth value, such as 2G, or the bandwidth range is large bandwidth, etc. The network that transmits the service packet can meet the network quality required by the service by providing corresponding network slices, forwarding tunnels, and the like.

Segment ID (segment ID, SID), which can represent a node or a link. In SRv6, the SID is represented as a 128-bit value; in SR-MPLS, the SID is represented as a label value, and an SRv6 segment identifier It may include a function part, the function part indicates that the network device corresponding to the segment identifier needs to perform the corresponding function and action.

Intent SID: A special SID representing service quality assurance, also known as Intent SID, which can be used to indicate the network quality requirements of the target service on the network. The network quality requirements can be such as delay, bandwidth, specific path, etc. one or more of the. When a large network includes multiple sub-networks, in order to express the same network quality requirements, a unified intent SID can be assigned to the multiple sub-networks, or different intent SIDs can be assigned to different sub-networks, or Assign a separate intent SID to a device. In the case of assigning the same intent SID to the sub-network, the intent SID is not used to guide routing in the network domain where it functions, but is only used to determine path indication information. In the case of allocating an independent intent SID to a device, the intent SID can also play a role of guiding routing in the network where the device is located. In an example, the intent SID may have the following functions: a device in the network may, based on the intent SID, determine corresponding path indication information for the message corresponding to the target service, where the path indication information may be one or more of the following: A list of network slice IDs or segment IDs. The device in the network may determine the corresponding path indication information only based on the intent SID, or may determine the corresponding path indication information based on the intent SID and other identifiers together. Intent identifier: an identifier representing service quality assurance, which can be used to indicate the network quality requirements of the target service on the network. The network quality requirements can be one or more of delay, bandwidth, and specific paths. When a large network includes multiple sub-networks, the multiple sub-networks can use the same intent ID to express the same network quality requirement, or use the same intent ID to correspond to different network quality requirements in different sub-networks. In contrast to the intent SID, the intent ID is not a segment ID.

Network slice segment identifier (AlgoSID): A special SID representing a network slice, also known as a network slice SID, which can be an instance of an intent SID and can be used to indicate a network on a network device in the network Slice, or used to indicate the same network slice on multiple network devices in the network, consistent with the intent SID, in the former case, the AlgoSID can also play the role of guiding routing, in the latter case, the AlgoSID In the network domain in which it functions, it is not used to guide routing, but only to determine the network slice identity. The network slice SID may have the following functions: a device in the network may determine a corresponding network slice for a packet according to the network slice SID. When the network slice SID is only an identification of one device, the network slice SID also has the function of indicating the route to this network device.

Network slicing: The network slicing technology can also be understood as a virtual network technology. The network slicing technology can adopt a flexible algorithm (Flexible Algorithm, Flex-Algo) network slicing or forwarding layer slicing technology, or other forms of network slicing technology. The network slice can be represented by: Flex-Algo identifier or slice identifier (SliceID).

1) Principle of Flex-Algo

In the Flex-Algo scenario, the network is planned into multiple planes through the Flex-Algo algorithm to form multiple topologies, and each topology is configured with a special Flex-Algo algorithm. The Flex-Algo algorithm ranges from 128 to 255. The default Flex-Algo 0 algorithm topology exists in the network.

A network node, or a partial link of the network node, can be deployed into one or more Flex-Algo algorithms. As shown in Figure 1, Figure 1 is an example of network sharding. This example shows an example of Flex-Algo forming a sharding topology. The network includes network nodes, namely network device 0 to network device 9. At least 3 network slices can be planned in the network, corresponding to 3 Flex-Algos. Each Flex-Algo algorithm supports a series of path calculation factors, such as :

The path calculation factor of Flex-Algo 0 can be defined as the minimum cost, and this Flex-Algo can include all nodes;

The path calculation factor of Flex-Algo 128 can be defined as the minimum delay, and includes network nodes 1-4 shown in solid lines in Figure 1, and network nodes 0 and 9;

The path calculation factor of the Flex-Algo 129 can be defined as the minimum traffic engine-metric (TE-Metric) value, and includes network nodes 5-8, and network nodes 0 and 9, shown in dashed lines in FIG. 1 .

The devices in the network can flexibly select the Algo algorithm according to the service or network deployment requirements. For example, the network can be sliced according to the metric, delay, TE Metric, etc., and the following figure can be obtained. Schematic diagram of network sharding.

2) SliceID slicing principle

By introducing the global network slice identifier SliceID, the forwarding plane SliceID is enabled in the virtual routing and forwarding (VRF) instance of the traditional network control plane. The forwarding plane packet carries the SliceID, and the hop-by-hop node identification of the intermediate transmission packet is reported. The SliceID in this article also restricts the traffic to be forwarded in specific reserved resources to ensure the SLA of the sharded service.

In the fragmentation deployment of the SliceID mode, for different services, such as mobile services, private line services and other services carried by the network that wish to reserve network forwarding resources, the overall pre-fragmentation method can be used, that is, the entire basic network port According to certain bandwidth requirements (such as convergence ratio, port percentage, etc.), flexible Ethernet (FlexE)/channelized sub-interfaces are used for resource guarantee and configuration, and a fragmented network covering the entire network is generated. Each fragment corresponds to The port reserves a certain bandwidth.

The network sliced through SliceID supports a flexible network slice virtual private network (VPN) bearer scheme. One network slice can share a single VRF instance, or multiple network slices can share a VRF instance, and differentiate services through different services. Code point (differentiated services code point, DSCP) into multiple shards.

As shown in FIG. 2 , a schematic diagram of a network for network slicing through SliceID is shown. The network includes three shards: SliceID1, SliceID2, and SliceID3. The three network slices serve the three slice services Slice Service 1, Slice Service 2, and Slice Service 3 respectively. The service corresponds to three different virtual local area network (VLAN)/DSCP access bearer network logical interfaces, and each logical interface is bound to a VRF instance.

The network side plans a globally unique SliceID for each network slice. After the service packet reaches the network, the public network side device uses the sliceID to map to the specific reserved resources corresponding to the network slice on the forwarding plane to ensure the service of each slice. Service Level Agreement (SLA) requirements. An operator's existing bearer network may also be called a default fragment, and the forwarding resources under each physical interface can be allocated to the default fragment and each service fragment. The Layer 3 attributes of the physical interface are shared by all network segments, including the IPv6 address/link cost on the physical main interface, the Layer 3 neighbors of the physical interface, and the link delay measured based on the physical main interface. The adjacency SID label assigned by the interface, etc. The "resource reservation" sub-interfaces of each network slice occupy the reserved resources under the physical main interface, and configure the corresponding slice IDs for these "resource reservation" sub-interfaces.

Default fragmentation: The physical bearer network before fragmentation, which bears the basic Interior Gateway Protocol (IGP)/Border Gateway Protocol (Border Gateway Protocol, BGP) protocol, and services that do not specify a fragmentation are in the default fragmentation The default shard can also be used as the disaster recovery backup shard for the service shard.

Service shards: shards created based on service SLA requirements. Different service shards can be logically or physically isolated. For example, each VPN instance shares a shard exclusively or multiple VPNs share a shard (DSCP mapping shard). In an IPv6 network, SliceID is used to identify a slice, and the control plane completes the mapping between the network slice identifier SliceID and the "reserved resources" of the forwarding plane slice. On the user access side, services enter different network segments according to service identifiers.

IP header: It can be divided into a basic header or an extended header, that is, the header can include a basic header or an extended header, where the basic header can also be called a standard header. In an example, the IP header is an IPv6 header, and the IPv6 header may include an IPv6 basic header and an IPv6 extension header. The IPv6 extension header may include one or more of a destination option header, a hop-by-hop options header (HBH), an SRH, and the like.

In the above, the related technologies of the embodiments of the present application are briefly introduced, and the technical solutions provided by the present application will be introduced below in conjunction with the network scenario shown in FIG. 3 . The network includes a backbone network (core), a metropolitan area network (metro) 1, optionally, a metropolitan area network (metro) 2, or more metropolitan area networks. In metropolitan area network 1, it includes access (ACC) device ACC1, aggregation (aggregation, AGG) device AGG1 and (metro core node, MC) device MC1; in the backbone network, including PE1, PE2, PE3, PE4, Operator (Provider, P) equipment: P1, P2, P3, and P4. The metropolitan area network includes network equipment such as ACC2, AGG2, and MC2. Among them, PE1 and PE2 are connected with the MC equipment of the metropolitan area network, for example, PE1 is connected with MC1, and PE3 and PE4 are connected with the MV equipment of the metropolitan area network 2, for example, PE3 is connected with MC2. In this network scenario, more networks may also be included, such as private networks of enterprise customers, more metropolitan area networks, or other backbone networks. In the above, the ACC device, the AGG device and the MC device are used as examples, which are applied to other scenarios, such as wireless network access scenarios. The ACC device can also be called a customer site gateway (CSG) device, and the AGG device can also be It is called an aggregation site gateway (ASG) device, and the MC device may also be called a radio service gateway (RSG) device.

In the network shown in Figure 3, in order to provide corresponding SLAs for services, it is usually necessary to establish an end-to-end (E2E) SRv6 Policy or adopt the above-mentioned network slicing technology to provide deterministic latency for services , bandwidth and other service quality requirements. Especially for private line services with high SLA requirements, to ensure the service quality of network tenants, it is necessary to create forward and reverse E2E tunnels for each tenant. For tunnel protection and service protection, it is also necessary to create supporting backup tunnels. The above is a certain one. The total number of round-trip tunnels, protection tunnels, and local tunnels created by services can reach 20-30, which greatly challenges the tunnel bearing capacity of network equipment and the ability of controllers to manage and maintain tunnels. Especially in the private line cloud service scenario, service packets are usually transmitted through a large network, which may include multiple small networks, such as backbone networks or metropolitan area networks, because E2E tunnels may span multiple networks. In autonomous system (AS) or Interior Gateway Protocol (IGP) domains, there are too many nodes and the end-to-end tunnel configuration is extremely complicated. Especially when the service needs to be transmitted through multiple networks, when multiple networks use different network technologies to provide services for the service, the configuration is more complicated. For example, the backbone network uses network slicing technology to ensure network quality, while When the metropolitan area network adopts SRv6 technology for network quality assurance. In an example, the backbone network and the metropolitan area network 1 here belong to different IGP domains, or belong to different ASs. In one scenario, the cloud operator edge device (provider edge, PE) device will become the tunnel PE aggregation node of each metropolitan area network private line service, and a large number of tunnels need to be created. In a larger network, not only the private line for going to the cloud, but also the B2B private line will create a large number of tunnels in the entire network. The controller needs to manage, control, and operate the large number of tunnels. With the development of services, the number of tunnels created on network devices will increase, and the number of tunnels managed by control devices will also increase.

The present application provides various technical solutions for solving the problem of too many tunnels configured in the above network in order to ensure service quality.

As shown in FIG. 4 , a schematic flowchart of a message sending method provided by the present application is provided, including the following steps:

S405: The first network device obtains the first packet, and the IP extension header of the packet includes the first identifier.

The first identifier is used to indicate a service requirement corresponding to the first packet, and the first identifier may be the above-mentioned intent SID or intent identifier.

The manner in which the first network device obtains the first packet includes the following two cases:

Case 1: Receive a packet sent by the second network device, and the packet is the first packet.

Case 2: After receiving the message sent by the second network device, the first network device updates the message to obtain the first message. For example, when the message includes a segment identifier list, the first network device can update the DA of the message according to the segment identifier list, and the first message obtained by the first network device is the message after updating the DA.

The above-mentioned second network device may be in the same network as the first network device, or may be in a different network. Applied to the network shown in FIG. 3 , the second network device may be, for example, an ACC1 device or an MC1 device of the metropolitan area network 1 in the network shown in FIG. 3 . The first network device may be, for example, a device such as PE1 or PE2 in the backbone network in the network shown in FIG. 3 , or a device such as MC2 in the metropolitan area network 2 . For another example, the P2 device of the backbone network in the network shown in FIG. 3 may be the second network device, and the PE1 may be the first network device.

In an example, the first identifier may be a segment identifier, such as an intent segment identifier. When the first identifier is a segment identifier, the SRH of the first packet includes the first identifier. Optionally, the SRH may also include the foregoing second identifier. In another example, the first identifier may be an intent identifier, and at this time, the HBH of the packet may include the first identifier.

That is, the packet sent by the second network device to the first network device includes the first identifier, and the identifier corresponds to the service requirement. The manner in which the first identifier is included in the packet sent by the second network device to the first network device includes but is not limited to the following situations:

Case A: The second network device obtains the first identifier sent by the control device, and then encapsulates it into a message.

The control device can calculate an end-to-end forwarding path according to the network topology and service requirements, such as from the MAN 1-backbone-MAN 2 shown in Figure 3, and the forwarding path can correspond to a segment The identification list, that is, the segment identification list indicates this forwarding path. The segment identifier list may include at least one identifier, and the at least one identifier includes the first identifier. For example, if the service needs to focus on ensuring the quality of the forwarding path of the backbone network, the control device may only send the first identifier applicable to the backbone network to the second network device. For example, the first identifier may be the segment identifier of PE1, and the forwarding path passes through PE1. In an example, the segment identifier list obtained by the second network device may only include the first identifier: such as intent SID: IntentSID1, this SID represents the final confirmation of the forwarding path of the A service in the backbone network according to the service requirements corresponding to IntentSID1. In another example, the segment identifier list may include IntentSID2, IntentSID1, and IntentSID3, and the first identifier may be, for example, IntentSID1, IntentSID2, or IntentSID3. Wherein, IntentSID1 may be the intent SID of ACC1 or the intent SID of at least two devices in metropolitan area network 1, and the at least two devices may be edge devices in metropolitan area network 1, such as ACC1 and MC1. IntentSID2 may be the intent SID on PE1 or the intent SID of at least two devices in the backbone network, and the at least two devices may be edge devices in the backbone network, such as PE1, PE2, PE3, and PE4. The IntentSID3 may be the intent SID on the ACC2 or the intent SID of at least two devices in the metropolitan area network 2, and the at least two devices may be edge devices in the metropolitan area network 2, such as ACC2 and MC2. Here and in the following, the intent SID is the intent SID of at least two devices, which means that at least two network devices included in the first network can determine the path indication information corresponding to the packet based on the first identifier.

The control device may also send the intent identifier to the second network device according to the network planning in combination with the planning of each network. The intent identifier may have different meanings in each network, or may have the same meaning in multiple networks. For example, the control device can send an intent identifier to ACC1, where the intent identifier can be IntentID1, which can act on the backbone network, metro network 1, etc. shown in FIG. 3 at the same time, which can represent services on both the backbone network and metro network The requirements are such as: low latency. Or IntentID1 represents that the target service requires low latency for backbone network services, and requires high bandwidth and low latency for metropolitan area network services.

In the above, the control device may send the segment identifier list obtained by the above calculation through the link state protocol message or the path calculation unit communication protocol message.

Case B: The second network device encapsulates the first identifier in the received packet according to the obtained configured first identifier.

The second network device can also obtain the first identifier configured by the administrator through the management device, the management interface, and the like in an unlimited manner. Then, in the received message, the first identifier is encapsulated, and then the message is sent to the first network device.

Case C: The second network device receives a packet sent by its upstream device, and the packet carries the first identifier.

In an example, when the second network device is MC1 in FIG. 3 , when it receives a packet sent by ACC1, the packet already carries the first identifier.

In the above, the IP extension header in the packet sent by the second network device to the first network device includes the above-mentioned first identifier. The IP extension header can be an HBH or a destination option header.

In an example, the destination address of the packet further includes a second identifier.

S410: The first network device determines path indication information corresponding to the first packet based on the first identifier and the second identifier.

Corresponding to the two situations in which the first network device obtains the first message, the destination address (destination address, DA) in the message received by the first network device may be the above-mentioned second identifier, or, the second network device After updating the DA of the message to obtain the first message, the DA of the first message is the above-mentioned second identifier. That is, the DA of the first packet includes the second identifier.

In an example, the above-mentioned second identifier is a segment identifier, such as a virtual private network (virtual private network, VPN) SID, an intent segment identifier or other segment identifiers, and the second identifier is also carried in the SRH of the first packet. In another example, the second identifier is the destination address in the foregoing IPv6 packet header, and is not carried in the SRH of the first packet. The foregoing second identifier may be used by the first network device to perform routing addressing, determine a forwarding policy, and the like based on the second identifier.

The above path indication information includes one or more of the following: a network slice identifier, a segment identifier list, best effort (best effort, BE) forwarding, and the like. The network slice identifier may be used to identify a network slice for forwarding the first packet, and the network slice identifier may only be the identifier of the slice by the first network device, or may be the first network device where the first network device is located. The identifier of the slice of multiple devices in a network, the network slice identifier can be one or both of the flexible slice identifier or sliceID. The segment identifier list may be used to indicate a forwarding tunnel for forwarding the first packet, which may include one or more segment identifiers, and the segment identifiers may include one of a network segment identifier, an intent segment identifier, or other segment identifiers. or more.

The first network device determines the corresponding path indication information based on the first identifier and the second identifier, including but not limited to the following ways:

Manner 1: The first network device determines a forwarding policy corresponding to the first packet based on the second identifier, where the forwarding policy includes a first correspondence between the first identifier and the path indication information.

Then, the first network device may determine the path indication information based on the first identifier and the first correspondence.

In one example, the forwarding policy may include only one correspondence, and in another example, the forwarding policy may include multiple correspondences. That is, the forwarding policy may be a single policy or a policy group.

In an example, the corresponding relationship may be as shown in Table 1, where the table includes the second identifier, the first identifier, and path indication information. The identification information included in the first packet is as follows: the second identification is VPNSID1 indicating the sending direction of the first packet, and the first identification is the intent SID of the packet, such as IntentSID1. Then, according to the corresponding relationship shown in Table 1, it can be known that the first packet can determine that the path indication information corresponding to the first packet is 129, and in this example, 129 is a flexible algorithm identifier.

Table 1

second sign first sign path indication

VPNSID1 IntentSID1 129 VPNSID1 IntentSID2 128

In an example, the corresponding relationship may be as shown in Table 2. The first network device may determine the forwarding policy as shown in Table 2 through the second identifier, and then determine that its corresponding path indication information is 129 through IntentSID1.

Table 2

first sign path indication IntentSID1 129 IntentSID2 128

In another example, Table 3 illustrates a case where the forwarding policy is a policy group, and the forwarding policy may be shown as the policy group policy group10 shown below.

table 3

first sign path indication IntentSID1 policy 1 (low latency + large bandwidth) IntentSID2 policy 2 (low latency + high reliability) + SliceID 1 IntentSID8 SliceID 1

The policy group includes a corresponding relationship between the first identifier and the path indication information, that is, includes a corresponding policy between the first identifier and the path indication information. The first network device can determine the policy group10 shown in Table 3 through the second identifier such as VPNSID1. The policy group10 includes multiple correspondences, that is, multiple detailed policies, wherein the intentSID1 corresponds to the policy1, and the service requirements of the intentSID1 are: Low latency and large bandwidth, and policy1 is an SR policy or a segment ID list. When the policy1 is an SR policy, it can determine a corresponding segment ID list. The forwarding path indicated by the segment identifier list can meet the transmission requirements of low delay and large bandwidth. Similarly, the path indication information corresponding to IntentSID2 includes the segment identifier list provided by policy2 and sliceID1. It indicates that when the intent SID in the packet is intentSID2, the packet is sent according to the network slice indicated by sliceID in the forwarding path corresponding to the segment identifier list indicated by policy2. The first identifier in the third correspondence is intentSID8, which is an intent identifier, and the corresponding path indication information is sliceID1, indicating that when the first identifier in the packet is intentSID8, the first identifier can be sent based on the network slice indicated by sliceID1. a message.

Mode 2: The first network device determines a third identifier corresponding to it based on the first identifier, and determines a forwarding policy corresponding to the first packet based on the second identifier, where the forwarding policy includes the first correspondence between the third identifier and the path indication information. relation.

Then, the first network device may determine the path indication information based on the third identifier and the second correspondence.

In this manner, the first network device also determines a third identifier corresponding to the first identifier based on the first identifier. In an example, the first network device further stores the correspondence between the first identifier and the third identifier, as shown in Table 4 below.

Table 4

first sign third sign IntentSID1 IntentID2 IntentSID2 IntentID3

Then, after obtaining the third identifier based on the first identifier, the first network device may determine the path indication information corresponding to it based on any one of the various examples provided in the first manner above. This application will not repeat them here. The method of adding the third identifier can make the control device use the same intent SID to realize the service arrangement of the whole network, and each network or each device is configured with a different third identifier, which can be passed through the first identifier and the third identifier. Corresponding relationship, obtaining corresponding path indication information, is more conducive to the realization of hierarchical network management.

S415: The first network device updates the first packet based on the path indication information to obtain the second packet.

After determining the path indication information corresponding to the first packet, the first network device may update the first packet to obtain the second packet. The manner in which the first network device updates the first packet to obtain the second packet includes, but is not limited to, the following manners: Manner 1, after determining the path indication information, the first network device may encapsulate the path indication information into the first packet The second packet is obtained in the middle, so that the device that needs to continue to forward the packet can forward the packet according to the path indication information obtained by the first network device, which can reduce the configuration of tunnel information in the network.

In an example, the path indication information is a segment identifier list, then the first network device may encapsulate a new IPv6 header for the first packet, the IPv6 header includes an SRH, and the SRH includes path indication information A list of corresponding segment IDs.

In another example, the path indication information is a network slice identifier, and the first network device may encapsulate a new IPv6 header for the first packet, where the IPv6 header includes an HBH or a destination option header, where the HBH Or the destination option header includes the network slice identifier corresponding to the path indication information.

In another example, the path indication information is a flexible algorithm identifier and a network slice identifier, then the first network device may encapsulate a new IPv6 packet header for the first packet, and the IPv6 packet header includes at least one HBH, The flexible algorithm identifier and network slice identifier described above are included in at least one HBH, that is, the flexible algorithm identifier and the network slice identifier can be carried in the same HBH or in different HBHs.

Manner 2: The first network device may also not encapsulate the path indication information. When the path indication information is a network slice identifier or a segment identifier list, the first network device may determine an outbound interface for sending the first packet according to the path indication information. After determining the outgoing interface of the first packet, the first network device may update the first packet according to information such as a media access control (Media Access Control, MAC) address of the outgoing interface to obtain a second packet. When the path indication information is a segment identifier list, the segment identifier list may only include a segment identifier, and when the segment identifier is the SID of the first network device itself, the first network device may determine to send the data according to the SID. The outbound interface of the first packet.

The above is only an example in which the first network device updates the first packet to obtain the second packet, and the first network device may also update the first packet based on other methods, such as updating an existing HBH header. This application does not limit the manner in which the first network device updates the first packet.

S420: Send the second message.

After determining the corresponding path indication information, the first network device may send the second packet based on the path indication information. As shown in Table 1, after the first network device determines that the corresponding path indication information is the flexible algorithm identifier 129, it can send the second packet according to the flexible algorithm identifier 129. During this process, the first network device may also combine The destination address of the second packet and the flexible algorithm identifier determine the exit for sending the second packet, and the like.

As shown in FIG. 5 , a schematic flowchart of a message sending method provided by the present application is provided, including the following steps:

S505: The first network device obtains a first packet, where the first packet includes a first identifier.

In the following, the scheme of the method will be described in detail in two cases.

Case A: The IP header of the first packet includes the first identifier.

The IP header of the first message may be the above-mentioned basic header or extended header, which is not limited herein. The first identifier may be the above-mentioned intent SID, intent identifier or network segment identifier. When the first identifier is a network slice identifier, such as a flexible algorithm segment identifier (AlgoSID), then the network slice identifier can correspond to, for example, a flexible algorithm identifier or sliceID on PE1, which corresponds to a network slice on PE1. Or the first identifier can correspond to a network slice in the backbone network, that is, the AlgoSID can be the identifiers of at least two network devices in the network, and the at least two devices can be edge devices in the backbone network, such as PE1, PE2 , PE3 and PE4 or more devices. The AlgoSID mentioned here and later is an identifier of at least two devices, which means that at least two network devices included in the first network can determine the path indication information corresponding to the first packet based on the first identifier.

Case B: The HBH or destination option header of the first packet includes a first identifier, and the first identifier is an intent ID.

The above-mentioned first identifier is used to indicate the service requirement corresponding to the first packet.

In the above cases A and B, the manner in which the first network device obtains the first packet includes the following two cases:

Case 1: Receive a packet sent by the second network device, and the packet is the first packet.

Case 2: After the first network device receives the message sent by the second network device, and updates the message, the updated message is the first message obtained by the first network device. For example, when the message includes a segment identifier list, the first network device can update the DA of the message according to the segment identifier list, and the first message obtained by the first network device is the message after updating the DA.

The above-mentioned second network device may be in the same network as the first network device, or may be in a different network. Applied to the network shown in FIG. 3 , the second network device may be, for example, an ACC1 device or an MC1 device of the metropolitan area network 1 in the network shown in FIG. 3 . The first network device may be, for example, a device such as PE1 or PE2 in the backbone network in the network shown in FIG. 3 , or a device such as MC2 in the metropolitan area network 2 . For another example, the P2 device of the backbone network in the network shown in FIG. 3 may be the second network device, and the PE1 may be the first network device.

In an example of case A, the first identifier may be a segment identifier, such as an intent segment identifier or a network segment identifier. When the first identifier is a segment identifier, the SRH of the first packet includes the first identifier. In another example, the first identifier may be an intent ID, and when the first identifier is an intent ID, the first identifier may be included in the HBH or destination option of the first packet.

Wherein, for the case A, the first identifier may be carried in the IP header of the packet sent by the second network device to the first network device. For case B, the first identifier may be carried in the HBH or destination option header of the packet sent by the second network device to the first network device and include the above-mentioned first identifier.

Above, the IP packet header and the various situations in which the first identifier is included in the packet sent by the second network device to the first network device are similar to S405 and related contents in the method embodiment shown in FIG. 4 . This will not be repeated here. S510: The first network device determines corresponding path indication information based on the first identifier.

Case A:

The path indication information is the network slice identifier. The network slice identifier may be used to identify a network slice for forwarding the first packet, and the network slice identifier may only be the identifier of the slice by the first network device, or may be the first network device where the first network device is located. The identifier of the slice of multiple devices in a network, the network slice identifier can be one or both of the flexible slice identifier or sliceID.

The first network device determines the corresponding path indication information based on the first identifier, including but not limited to the following ways:

Manner 1: The first network device includes a correspondence between the first identifier and the path indication information, and the first network device determines the path indication information based on the correspondence between the first identifier and the path indication information.

In an example, the corresponding relationship may be as shown in Table 5, and the first network device may determine that its corresponding path indication information is 129 through IntentSID1.

table 5

first sign path indication IntentSID1 129 IntentSID2 128

Manner 2: The first network device determines a third identifier corresponding to the first identifier based on the first identifier, and determines the path indication information based on the correspondence between the third identifier and the path indication information.

Then, the first network device may determine the path indication information based on the third identifier and the above-mentioned corresponding relationship.

In this manner, the first network device also determines a third identifier corresponding to the first identifier based on the first identifier. In an example, the first network device also stores a correspondence between the first identifier and the third identifier, as shown in Table 6 below.

Table 6

first sign third sign IntentSID1 IntentID2 IntentSID2 IntentID3

Then, after the first network device obtains the third identifier based on the first identifier, it can then determine the path indication information corresponding to it based on the manner provided in the first manner above. This application will not repeat them here.

Case B:

The path indication information is a list of segment identifiers. That is, the first network device may determine the corresponding segment identifier list based on the intent ID and the segment identifier list, or the corresponding relationship between the intent ID and the SR Policy.

S515: The first network device updates the first packet to obtain the second packet.

Case A: The manner in which the first network device updates the first packet to obtain the second packet is similar to the manner in which the path indication information in S415 is the network slice identifier in the method embodiment shown in FIG. Repeat.

Situation B: The manner in which the first network device updates the first packet to obtain the second packet is similar to the manner in which the path indication information in S415 is a segment identifier list in the method embodiment shown in FIG. Repeat.

S520: Send the second packet.

After determining the corresponding path indication information, the first network device may send the second packet based on the path indication information. As shown in Table 1, after the first network device determines that the corresponding path indication information is the flexible algorithm identifier 129, it can send the second packet according to the flexible algorithm identifier 129. During this process, the first network device may also combine The destination address of the second packet and the flexible algorithm identifier determine the exit for sending the second packet, and the like.

As shown in FIG. 6 , a schematic flowchart of an identification sending method provided by the present application is provided. The method flow is applied to a control device in a network, and includes the following steps:

S605: The control device obtains the first identifier.

The control device may be a controller, a management device, an orchestrator, or a certain router, switch, etc. in the network. The first identifier corresponds to the service requirement. The first identifier is the first identifier in the method embodiment shown in FIG. 4 or FIG. 5 above, and the first identifier may be an intent segment identifier or a network segment identifier.

The manner in which the control device obtains the first identifier includes but is not limited to the following manners:

Manner 1: The control device generates the first identifier. For example, the control device generates an intent segment identifier based on network service planning and the like.

Manner 2: The control device receives the first identifier sent by the network device. The control device may receive a message carrying the first identifier sent by the network device, where the message may be a link state protocol message or a path computing unit communication protocol message, so as to obtain the first identifier from the message.

S610: The control device determines a first segment identifier list corresponding to the target service, where the first segment identifier list includes the above-mentioned first identifier.

The control device may determine the segment identifier list corresponding to the target service based on network planning, or may also be connected with other service systems. The first segment identifier list includes the above-mentioned first identifier.

Optionally, the first segment identifier list also includes other segment identifiers, such as network segment identifiers, intent segment identifiers, VPN SIDs, and the like.

The first segment identifier list determined by the control device may be a segment identifier list indicating the end-to-end forwarding path of the forwarding target service message. As applied to the scenario shown in The segment identifier list of the end-to-end forwarding path from the network to the metropolitan area network 2 may also be a segment identifier list indicating a certain segment path, for example, a segment identifier list indicating only the forwarding path of the backbone network. In an example, the foregoing forwarding path may be sent to a device such as ACC1 or PE1 through a first network device included in the first network. The first identifier may be used to enable the first network device to determine corresponding path indication information based on the first identifier, where the path indication information includes: a network slice identifier and/or a second segment identifier list.

S615: The control device sends the first segment of the identification list.

After determining the first segment identifier list corresponding to the target service, the control device may send the segment identifier list to one or more devices in the network. Applied to the network scenario shown in FIG. 3 , the first segment identifier list may be sent to the head node of the forwarding path, for example, may be sent to devices such as ACC1 or PE1.

The control device may send the above-mentioned first segment identification list through a link state protocol message or a path calculation unit communication protocol message.

The technical solutions provided by the present application have been briefly introduced above, and the method embodiments shown in FIG. 4 , FIG. 5 , or FIG. 6 will be applied to the network scenario shown in FIG. 3 , and the technical solutions provided by the present application will be described in detail below. Applications.

Example 1, the first identifier is an intent identifier, and the first network device may be the network device PE1 as shown in FIG. 3 . PE1 can receive a message sent from MC1, and the message carries an intent identifier. The intent identifier may be updated by ACC1 into the message after receiving the message. In an example, the HBH of the packet carries the intent identifier.

Then, after receiving the packet, PE1 determines the corresponding sliceID identifying the network slice according to the intent identifier, and forwards the packet based on the sliceID. Optionally, PE1 can also update the packet, strip the existing HBH header of the packet, and encapsulate a new HBH header for the packet. The new HBH includes the sliceID, which is in the subnet that supports network slicing. After receiving the packet, other devices in the device can forward the packet on the corresponding network slice according to the SliceID. For example, in the scenario where different Flex-Algos plan the same Locator address, the Flex-Algo ID that identifies the Flex-Algo network slice can be carried in the IPv6 extension header HBH. In the subnet that supports network slicing, according to the Flex-Algo ID Instructs packets to be forwarded on the corresponding network slice.

Example 2, define an AlgoSID. The definition of the AlgoSID can be shown in Table 7 below.

Table 7

The action of AlgoSID is as follows:

After the network device receives the SRv6 packet, when the current active SID in the SRH is the AlgoSID, that is, when the network device determines that it can process the AlgoSID, the slice ID is obtained according to the correspondence between the AlgoSID and the network slice ID. , and encapsulate the slice ID into the packet HBH to instruct the packet to be forwarded in the specified slice. In this paper, the corresponding relationship is also called the mapping relationship, which is specifically mapped on PE1. The mapping relationship is shown in Table 8 below:

Table 8

Algo SID Intent ID/Flex-Algo ID A1:1::200 128 A1:1::201 129 ... ...

1. When the controller arranges the path, it can arrange the Algo SID into the E2E tunnel SID List according to the quality requirements of the service on the network, and the ACC1 encapsulates the Algo SID in the SRH of the packet.

2. When the packet enters the subnet, the current processing SID in the SRH is the Algo SID, then the device converts the Algo SID into an "intent ID" or "slice ID" according to the correspondence between the Algo SID and the network slice identifier. ”, encapsulate the intent ID or Flex-Algo ID in the packet HBH. The packet is forwarded according to the intent ID or Flex-Algo ID in the routing table corresponding to the Flex-Algo, and the packets corresponding to the target service are restricted to be forwarded in this network slice.

In an example, the process of routing and processing by the control device is shown in FIG. 7 below. Steps 1-6 shown in Figure 7 are as follows:

1. The orchestrator arranges paths according to business requirements, such as SLA requirements.

2. The orchestrator requests the controller to obtain the SID corresponding to the intent. The request can carry Flex-Algo information and backbone (Core) network entry and exit PE node information;

3. The controller obtains the first identifier-AlgoSID corresponding to the Flex-Algo on the specified incoming PE node according to the Flex-Algo information and the incoming and outgoing node information in the instructions of the orchestrator, and returns it to the orchestrator;

4. The arranger arranges and sends the path SID List to the network device ACC through the controller, which carries the AlgoSID;

5. The tunnel head node in the network device encapsulates SRH with AlgoSID, such as ACC1 encapsulates SRH;

6. After the Core network PE1 that supports Flex-Algo slicing receives the packet, and its current SID is AlgoSID, it converts the AlgoSID to the intent ID or Flex-Algo ID and encapsulates it in the HBH.

As shown in Figure 8, applied to the network shown in Figure 3, Metro1 and Metro2 are networks that support SRv6 Policy, and the backbone network is a network that supports flex-aglo network slicing. The scheduler arranges the end-to-end forwarding tunnel according to the service requirements of the target service, as shown in Figure 8: the (AGG1 SID, MC1 SID) of the forwarding path in the Metro1 network are the segment identifiers of AGG1 and MC1, respectively, representing the target service The packets need to be forwarded through AGG1 and MC1 of Metro1. Indicates the (MC2 SID, AGG2 SID, ACC2 SID) of the path in the Metro2 network, which are the segment identifiers of MC2, AGG2, and ACC2, respectively. The tunnels in Metro1 and Metro2 are respectively SID Lists in the form of SRv6 Policy tunnels. In the backbone network, the same Locator address can be planned for different Flex-Algo network slices in advance, for example: Algo SID1-128 represents the Flex-Algo 128 of the PE1 node, which plays the role of indicating the shard and can also play the role of specifying the route of the PE. effect. The orchestrator can obtain the information of the head node and the tail node of the backbone network capable of slicing, and the orchestrator can select the Flex-Algo of the CORE network, such as AlgoSID1-128, for the core network according to the business intent. The orchestrator may obtain the corresponding relationship between the intent ID or the AlgoSID and the network slice identifier in advance. In an example, the mapping relationship is shown in Table 9 below:

Table 9

Intent ID/AlgoSID Slice ID Intent 1 (guaranteed bandwidth) Flex-Algo 128 Intent 2 (guaranteed low latency) Flex-Algo 129 Intention 3 (do not take the XXX link) Flex-Algo XXX

After the orchestrator obtains the above segment identifier list, it can send the segment identifier list to ACC1, and the forwarding process of the message shown in Figure 8 is as follows:

1. After the ACC1 of Metro1 receives the message corresponding to the target service sent by the customer terminal equipment (customer-premises equipment, CPE), it will obtain a list of segment identifiers (AGG1 SID, MC1 SID, AlgoSID1-128, MC2 SID, AGG2 SID), and obtain the AGG2 VPN SID according to the destination address of the message, encapsulate it into the message, and then forward the message.

2. After the access point PE1 of the Core network receives the packet, the active SID of the packet is AlgoSID1-128, then PE1 determines the corresponding path indication information according to AlgoSID1-128 as slice ID: 128, then PE1 can slice the slice. The ID 128 is encapsulated into the HBH of the packet, and the 128 slice is selected to continue to forward the packet.

3. After receiving the packet, other devices in the Core network such as P1 and P2 will check the routing table of the corresponding Flex-Algo according to the slice ID128 carried in the packet and forward it.

Here, the corresponding relationship between Algo SID and slice ID is set on the PE node device of the core network, as shown in Table 10 below:

Table 10

node AlgoSID Flex-Algo ID PE1 AlgoSID1-128 128 PE1 AlgoSID1-129 129 PE1 AlgoSID1-130 130 PE2 AlgoSID2-128 128

PE2 AlgoSID2-129 129 PE2 AlgoSID2-130 130

Among them, the (AGG1 SID, MC1 SID) representing the path in the Metro1 network in the message SID List in Figure 8 and the (MC2 SID, AGG2 SID, ACC2 SID) representing the path in the Metro2 network are only used to express the paths in different networks , and the paths in these networks can also be expressed by bonding segment identifiers (bonding SIDs, BSIDs). That is, the head node ACC1 may also obtain the segment identifier list including the BSID, and the network device transmitting the packet may expand the BSID after receiving the packet, and reseal the SRH of the local tunnel in the outer layer of the packet. . Since the edge network only accesses local users, the number of access users and tunnels is much less than that of the converged network like the backbone network. Therefore, the technical solution focuses on solving the problem of too many tunnels on the backbone network. Of course, if a certain metro network also supports Flex-Algo network slicing and HBH, the above technical solutions can also be applied to the edge metro network to further reduce the number of tunnels on the edge metro network. The present invention is not limited to the network and scenario of application. At the same time, this technical solution does not require a large number of edge network devices to be upgraded to support HBH, new AlgoSID devices can be automatically generated, and SRv6 Policy can be deployed on edge networks that do not support network slicing and HBH; the backbone that supports slicing and HBH carrying slice ID or intent ID Network upgrade deploys Flex-Algo network slicing or network slicing with SliceID; therefore, it is more suitable for scenarios where edge network cannot be upgraded to support network slicing, backbone network supports network slicing and HBH carries slice ID or intent ID, and this kind of scenario is exactly The most likely problems encountered in network deployment at present.

Example 3: Uniformly allocate a dedicated SID representing the same Flex-Algo slice in the entire subnet. The core difference between this technical solution and Example 2 is that the AlgoSID in Example 2 is allocated for each device in the same network. However, the AlgoSID in this example is for the same slice, and the same AlgoSID is allocated, and the network devices are not distinguished. For networks that support network slicing, nodes are not distinguished, and different Algo SIDs are assigned to each slice. For example, Algo SID-128 in the above figure represents the slice Flex-Algo 128 in the Core network. This SID only serves to indicate the slice. , which does not distinguish between nodes. That is, the AlgoSID may be the SIDs of at least two devices in a certain network.

For this kind of SID, a special type of SID is newly defined, such as a flexible slice anycast segment identifier (AlgoAnycastSID), which may be a special type of AlgoSID. An example of its Function definition is shown in Table 11 below:

Table 11

The action of AlgoAnycastSID is as follows:

When the device receives the SRv6 packet and the current active SID in the SRH is AlgoAnycastSID, it obtains the slice ID according to the mapping relationship between the AlgoAnycastSID and the network slice ID, and encapsulates the slice ID in the packet HBH, instructing the packet to be specified in the specified Forward in slices. The mapping relationship can be shown in Table 12 below:

Table 12

AlgoAnycastSID Flex-Algo ID Flex-Algo SID-128 128 Flex-Algo SID-129 129 Flex-Algo SID-130 130 Flex-Algo SID-131 131 Flex-Algo SID-132 132 Flex-Algo SID-133 133

Similar to "Example 2", the orchestrator can save and manage the following correspondences as shown in Table 13 below:

Table 13

Intent ID corresponding slice Intent 1 (guaranteed bandwidth) Flex-Algo 128 Intent 2 (guaranteed low latency) Flex-Algo 129 Intention 3 (do not take the XXX link) Flex-Algo XXX

In the technical solution provided in this example, the MAN aggregated route can be advertised to the backbone network, and the AlgoAnycastSID Locator aggregated by the backbone network can be advertised to the MAN. Backbone network traffic is forwarded according to the aggregation route. Therefore, the orchestrator only needs to issue the intent and does not need to know the boundary nodes of the backbone network, which greatly reduces the requirements of the orchestrator.

During the forwarding process, the tunnel head node device encapsulates the AlgoAnycastSID in the E2E SRH. However, after the packet leaves the metropolitan area network, such as metro1, it only performs routing lookup table forwarding according to its DA, that is, the AlgoAnycastSID, and does not care about the packet from the MAN. Which node enters the backbone network.

After the traffic enters the backbone network, the PE that receives the traffic first, such as PE1 or PE2, converts the AlgoAnycastSID into "Flex-Algo ID" and encapsulates it in the HBH. Other devices in the backbone network check the routing table of the corresponding Flex-Algo according to the "intent ID or Flex-Algo ID" in the HBH, which means that the traffic is constrained to be forwarded in this network slice.

Compared with Example 2, the features and advantages of this solution:

1. Networks that support network slicing, such as all nodes in the backbone network or all edge nodes, such as PE equipment, assign an identical AlgoSID to each shard, which is equivalent to all nodes sharing a SID in the same Flex-Algo slice, which can The Locator address is saved and the implementation is simpler. The AlgoAnycastSID needs to be consistent across the entire subnet.

2. The orchestrator does not need to orchestrate the boundary points of the slicing network, but only needs to directly orchestrate the business requirements of the slicing network, which greatly simplifies the processing of the orchestrator.

Example 4. Through the unified intent SID of the whole network and the SID that can guide the direction of packet forwarding, such as VPN SID, the service traffic can be guided to select a network slice or a tunnel or directly forward the local IP (Native IP) without the need for Establishing a large number of E2E tunnels can better solve the problem of massive tunnels. This example can briefly include the following steps:

1. Establish a tunnel group based on tail node + mask (that is, aggregate tunnel), such as establishing a tunnel group based on tail node and mask based on the backbone network, and combine the tunnels based on each tail node of the remote network in this subnet. Classify into a tunnel based on a certain subnet, reducing the number of tunnels to the remote network;

2. The Locator routes of each subnet are aggregated and advertised to other networks. When the packet enters each subnet, the corresponding Policy group is found according to the default route or aggregation route of its VPNSID;

3. The orchestrator specifies the corresponding intent SID for the target service and sends it to the head node of the tunnel. After entering the subnet, it finds the corresponding Policy group according to the VPNSID, and then selects the Policy Group according to the intent ID mapped by the intent SID. specific tunnels or slices.

In this example, an example of the definition of the intent SID is shown in Table 14 below:

Table 14

The action of the IntentSID is as follows:

When the device receives an SRv6 packet and the current active SID in the SRH is the IntentSID, it obtains the service SLA according to the mapping relationship between the IntentSID and network resources, such as network forwarding channel resources, such as network slices, policy tunnels, and BE forwarding. The path indication information of the forwarding channel, according to the path indication information, instruct the packet to be forwarded in the corresponding network channel.

The specific processing methods of the actions corresponding to the IntentSID include but are not limited to the following:

1) When the channel resource mapped by the IntentSID is an SRv6 Policy, the SRH of the SRv6 Policy corresponding to the IntentSID is encapsulated in the message to guide forwarding.

2) When the channel resource mapped by the IntentSID is a network slice, such as a Flex-Algo or a SliceID slice, the slice ID is obtained according to the mapping relationship between the IntentSID and the slice ID, and the slice ID is encapsulated in the packet HBH to guide the packet in the specified slice. forwarded in.

3) When the channel resource mapped by IntentSID is Native IP forwarding, BE forwarding is performed directly according to VPNSID or next-hop SID.

This example is described below with reference to Figure 9. As shown in Figure 9, with an end-to-end tunnel, the packets of the target service, such as from CPE1 to CPE2, are forwarded through the backbone network and multiple metropolitan area networks.

1) In the network shown in Figure 3, each network can create a Policy Group within its own network. The Policy Group can use a mask to match the destination address. The Policy Group can contain SRv6 Policy, Flex-Algo slice, SliceID slice, SRv6 BE et al.

Examples of tunnel and slice type models that a Policy Group can contain are as follows:

For example, in the backbone network, it can be matched to Policy Group10 through the Metro2 aggregation route:

In Policy Group10, the forwarding models included are as follows:

Intent ID1->policy 1 (low latency + large bandwidth)

Intent ID2->policy 2 (low latency + high reliability)+SliceID 1

Intent ID3->policy 3 (low latency + low jitter)

Intent ID4->FlexAlgo 128 (low latency)

Intent ID5->FlexAlgo 128 (low latency)+SliceID 1

Intent ID6->FlexAlgo 128 (low latency)+SliceID 2

Intent ID7->policy 5 (large bandwidth+…)

Intent ID8->SliceID 1

Intent ID9->SliceID 2

...

Intent ID N->native ip(BE)

2) In other subnets published after the Locators of each subnet are aggregated. MC2 aggregates all Locators of Metro2 and releases it to PE3. The backbone networks PE1 and PE2 aggregate the Locators of the backbone network and publish them to the Metro1 network, and publish the aggregated Locators of Metro2 to Metro1. Conversely, the way to release from Metro1 to Metro2 is the same.

3) Metro2: MC2 establishes the SRv6 Policy tunnel and Policy Group within the domain to the ACC2 Locator. And match the endpoint/mask exactly, associate the Locator route with the Group, and classify the traffic matching the route.

4) Backbone network: PE1 uses the aggregated route of Metro2 as the endpoint (Endpoint) to establish an SRv6 Policy/SRv6 Policy Group, and uses the endpoint/mask (mask) to accurately match, associate the Locator route with the Group, and match the traffic of the route to flow Classification.

5) Metro1: ACC1 establishes an SRv6 Policy/SRv6 Policy Group with the default route as the Endpoint, and matches exactly with the endpoint/mask, associates the Locator route with the Group, and classifies the traffic matching the route.

As described above, an example of the mapping relationship between the aggregated routes and aggregated tunnels formed between different subnets is shown in FIG. 10 .

Routing on Metro 1:

Metro 2 aggregated route->Policy Group 1, where the aggregated route prefix of Metro2 can be such as: prefix1.

Metro 3 aggregated route->Policy Group 2, where the aggregated route prefix of Metro2 can be such as: prefix2.

Metro 4 aggregated route -> Policy Group 3, where the aggregated route prefix of Metro2 can be such as: prefix3.

Use VPNSID to check routing traffic classification.

Routing on Core:

Metro 1 aggregated route->Policy Group 1, where the aggregated route prefix of Metro1 can be such as: prefix4.

Metro 2 aggregated route -> Policy Group 2, where the aggregated route prefix of Metro2 can be such as: prefix5.

Metro 3 aggregated route->Policy Group 3, where the aggregated route prefix of Metro2 can be such as: prefix6.

Metro 4 aggregated route->Policy Group 4, where the aggregated route prefix of Metro2 can be such as: prefix7.

Use VPNSID to check routing traffic classification

2. Intent SID Planning

A unified intent SID is planned for the entire network. This SID is not used for addressing and only carries service intent. The high-order bits of the intent SID can use a special value to identify the SID as a special SID that carries the intent ID. An intent ID can express the meaning of the forwarding requirements of both the metropolitan area network and the backbone network; if the metropolitan area network has more types of intent IDs, the backbone network needs to set the ratio of "intent ID: forwarding tunnel or slice" to "N:1" ” mapping relationship. Therefore, when planning the intent SID of the whole network, it can be planned according to the hierarchical aggregation, so as to reduce the configuration of such "N:1" mapping relationship.

Below, the technical solution provided by this example will be described in detail in conjunction with the packet forwarding process on the forwarding plane shown in FIG. 9 , including the following steps:

1. ACC1 in the Metro1 network, after receiving the target service message sent by CPE1, the DA of the message is the address of CPE2, then ACC1 checks the private network routing table according to the DA to obtain the VPNSID corresponding to the message as ACC2 VPN SID, according to this SID, look up the routing table to match the default route, or aggregate the route, the route is associated with the SRv6 Policy Group. After ACC1 determines the Policy Group according to the VPNSID, ACC1 obtains the stack top SID in the SRH according to the configuration requirements, such as the intent SID shown in the figure, and then maps it to the corresponding intent ID according to the intent SID, and determines the corresponding SRv6 to which the traffic is to be drained by the intent ID. Policy or network slice. If the intent ID is mapped to a Policy tunnel, ACC1 encapsulates the SRH of the Policy tunnel in the outer layer of the packet; if the intent ID is mapped to a network slice, the slice ID is encapsulated in an IPv6 HBH to indicate that the packet is in the specified slice Forward. If the mapping is Native IP forwarding, only check the routing table according to the VPNSID and go to SRv6 BE forwarding.

In this example, after ACC1 obtains the corresponding segment identifier list (intent SID, ACC2 VPN SID), according to the VPN SID and intent SID, the determined path indication information is the policy tunnel, that is, the segment identifier list (AGG1 SID, MC1 SID) ), update it into the packet, so that the packet is forwarded in Metro1 according to the tunnel indicated by this segment ID list.

2. When the packet is forwarded to MC1 in the Metro1 network, so that the SRv6 Policy is terminated or the network slice is forwarded, MC1 matches the default route according to the ACC2 VPNSID, and forwards it to PE1 through BE.

3. After PE1 on the Core network receives the packet, it matches the Metro2 aggregated route according to the VPNSID and diverts the traffic to the aggregated SRv6 Policy Group of Metro2. After the Policy Group is determined, PE1 obtains the top-of-stack SID in the SRH according to the configuration requirements, that is, the intent SID, and then maps the intent SID to the corresponding intent ID, and determines the corresponding SRv6 Policy or network slice to which the traffic is directed based on the intent ID. If it is a Policy tunnel, the segment ID list (P1 SID, P2 SID, PE3 SID) of the Policy tunnel is encapsulated in the outer layer of the packet; if it is a network slice, the slice ID is encapsulated in IPv6 HBH to indicate that the packet is in the specified Intra-slice forwarding. If the mapping is Native IP forwarding, only the routing table is checked according to the ACC2 VPNSID and forwarded by SRv6 BE.

4. The packet is forwarded to PE3 of the Core network after the SRv6 Policy is terminated or the network slicing is forwarded according to the above information, and the route is aggregated according to the ACC2 VPN SID and forwarded to MC2 through BE.

5. In the Metro2 network, MC2 matches the ACC2 Locator route according to the ACC2 VPNSID, and diverts traffic to the corresponding SRv6 Policy Group. After the Policy Group is determined, ACC2 obtains the intent SID at the top of the stack in the SRH according to the configuration requirements, maps it to the corresponding intent ID according to the intent SID, and determines the corresponding SRv6 Policy or network slice to which the traffic is directed based on the intent ID. If the intent ID directly matches a Policy tunnel, such as (AGG2 SID, ACC2 SID), the packet is forwarded according to this tunnel. If it matches a network slice, the slice ID is encapsulated in IPv6 HBH to indicate that the packet is forwarded within the specified slice. If the mapping is Native IP forwarding, only the routing table is checked according to the ACC2 VPNSID and forwarded by SRv6 BE.

Example 5. Each subnet uses an independent intent SID to complete segment tunnel forwarding. This example is an extension of Example 4 above. Example 4: Adopt the unified intent SID of the whole network, push the intent SID into the top of the SRH stack of the target service, carry it from the head node to the end node of the end-to-end tunnel, and indicate the SLA requirement of service forwarding through the intent ID mapped to the intent SID , and use VPNSID for packet routing and forwarding. That is, the VPN SID with routing capability and the intent SID with service SLA requirements are used as a whole to complete forwarding, so that the network does not need to create an E2E tunnel. This technical solution requires the overall planning intent SID of the network.

This example is further extended on the basis of the above solution. Different intent SIDs are independently assigned to each subnet, and the intent SIDs are encapsulated in the form of SID List in the SRH to guide packet forwarding. Each subnet entry node first records the current intent SID in the SID list of the received target packet as the SID indicating the service SLA, and then the SID List is shifted backward to the next intent SID, and the intent SID is used to check the route matching to the corresponding SRv6 Policy Group.

The packet forwarding process is shown in Figure 11:

After ACC1 receives the message of the target service sent by CPE1, the DA of the message is the address of CPE2, and the corresponding segment identifier list is determined as (MI intent SID, core intent SID, M2 intent SID), and ACC1 according to this DA checks the private network routing table and obtains that the VPNSID corresponding to the packet is the ACC2 VPN SID. According to this SID, the routing table is checked to match the default route, or the aggregated route is associated with the SRv6 Policy Group. Then ACC1 determines its corresponding segment identifier list as (AGG1 SID, MC1 SID) according to the M1 intent SID, and encapsulates it into the message.

When the Core network PE1 receives the packet, the current Active SID of the packet is "Core Intent SID", then PE1 records the "Core Intent SID" and shifts it to the next SID in the SID List as "M2 Intent SID" ". The Metro2 aggregated route is matched according to the "M2 intent SID" and then the traffic is diverted to the aggregated SRv6 Policy Group of Metro2. After the Policy Group is determined, PE1 maps the recorded "Core Intent SID" to the corresponding Intent ID according to the configuration requirements, and determines the corresponding SRv6 Policy or network slice to which the traffic is to be diverted from the Intent ID. If it is a Policy tunnel, the segment ID list (P1 SID, P2 SID, PE3 SID) of the Policy tunnel is encapsulated in the outer layer of the packet; if it is a network slice, the slice ID is encapsulated in IPv6 HBH to indicate that the packet is in the specified Intra-slice forwarding. If the mapping is Native IP forwarding, only check the routing table according to the "M2 intent SID" and go to SRv6 BE forwarding.

When the Metor2 network MC2 receives the message, the current Active SID of the message is "M2 intent SID", then MC2 records the "M2 intent SID" and shifts it to the next SID in the SID List as "ACC2 VPN SID" ". After matching the route according to "ACC2 VPN SID", the traffic is diverted to the SRv6 Policy Group. After the Policy Group is determined, MC2 maps the recorded "M2 Intent SID" to the corresponding Intent ID according to the configuration requirements, and determines the segment ID list (AGG2 SID, ACC2 SID) corresponding to the corresponding SRv6 Policy to be drained by the Intent ID. The outer layer of the packet is forwarded.

The main difference between the forwarding processing in Example 5 and Example 4 is that the forwarding is based on the SID List formed by the intent SID. The intent SID in Example 5 also has routing capabilities. The ingress interface node of each subnet needs to be based on the current SID and the next The SID coordination is completed. When a packet is received, the current SID is used to identify the service SLA in this subnet, and the next SID after the offset is used for routing, matching the corresponding aggregation tunnel Policy Group. The VPNSID and the role type in the common SRv6 Policy are used after the destination is finally reached.

The method embodiments provided by the present application are described above, and the network equipment provided by the present application is described below.

The present application provides an apparatus (for example, a repeater/network device) having a function of implementing the behavior of the network device in the above method. The functions can be implemented based on hardware, and can also be implemented based on hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. See, for example, Figures 12, 13 and 14 below.

As shown in FIG. 12 , FIG. 12 is a schematic structural diagram of a network device 1200 provided by an embodiment of the present application. The network device 1200 may be configured to execute the first network device in the method shown in FIG. 4 or FIG. 5 above. The method, that is, the network device 1200 can be used to execute the network device in any of the above-mentioned exemplary methods in FIG. 7 to FIG. 11 , such as the method executed by PE1. As shown in FIG. 12 , the network device 1200 includes: an obtaining module 1201 , a processing module 1202 , and a sending module 1203 . The obtaining module 1201 may be configured to execute the related method of the network device obtaining the first packet including the first identifier in the above method embodiments; the processing module 1202 may be configured to execute the method of determining the correspondence of the first packet according to the first identifier in the above method related methods such as path indication information, obtaining the second packet, etc.; the sending module 1203 can be configured to execute the related method of sending the second packet in the above method.

It should be noted that, when the network device provided in FIG. 12 performs the above-mentioned packet sending method, only the division of the above-mentioned functional units is used for illustration. In practical applications, the above-mentioned functions can be allocated by Different functional units are completed, that is, the internal structure of the network device is divided into different functional units to complete all or part of the functions described above; or a unified functional unit is used to complete the functions of the above-mentioned multiple units. It should be understood that the network device 1200 and the foregoing packet processing method embodiments belong to the same concept, and only the steps performed by each unit of the network device 1200 are exemplified here, but it does not mean that it does not execute the steps in the foregoing embodiments. For other steps or optional methods, the specific implementation process thereof is detailed in the relevant description of the above method example section, which is not repeated here.

As shown in FIG. 13 , FIG. 13 is a schematic structural diagram of a network device 1300 provided by an embodiment of the present application, where the network device 1300 may be configured to execute the method performed by the second network device in the method shown in FIG. 4 or FIG. 5 above. The method, that is, the network device 1300 can be used to execute the method performed by the network device in any of the above-mentioned exemplary methods in FIGS. 7-11 , such as the method executed by ACC1 or MC1. As shown in FIG. 13 , the network device 1300 includes: an obtaining module 1301 , a processing module 1302 , and a sending module 1303 . The obtaining module 1301 can be used to execute the method related to the network device obtaining the first identifier in the above method; the processing module 1302 can be used to execute the method related to generating the first packet including the first identifier in the above method; the sending module 1303 can be used for executing the related method of sending the first message in the above method.

It should be noted that, when the network device provided in FIG. 13 performs the above-mentioned packet sending method, only the division of the above-mentioned functional units is used as an example for illustration. In practical applications, the above-mentioned functions can be allocated by Different functional units are completed, that is, the internal structure of the network device is divided into different functional units to complete all or part of the functions described above; or a unified functional unit is used to complete the functions of the above-mentioned multiple units. It should be understood that the network device 1300 and the foregoing packet processing method embodiments belong to the same concept, and only the steps performed by each unit of the network device are illustrated here, but it does not mean that it does not execute the steps in the foregoing embodiments. For other steps or optional methods, the specific implementation process thereof is detailed in the relevant description of the above method example section, which is not repeated here.

As shown in FIG. 14 , FIG. 14 is a schematic structural diagram of a control device 1400 provided by an embodiment of the present application, and the control device 1400 can be used to execute the control device execution in the method shown in FIG. 4 , FIG. 5 or FIG. 6 above. method, that is: the control device 1400 can be used to execute the method executed by the control device in any of the above-mentioned exemplary methods in FIGS. 7 to 11 . As shown in FIG. 14 , the network device 1400 includes: an obtaining module 1401 , a processing module 1402 , and a sending module 1403 . The obtaining module 1401 can be used to execute the related method for the control device to obtain the first identifier in the above method; the processing module 1402 can be used to execute the related method of determining the first segment identifier list corresponding to the target service in the above method; the sending module 1403, A related method of transmitting a segment identification list including the first identification may be used to perform the above method.

It should be noted that, when the control device provided in FIG. 14 performs the above-mentioned method for sending the identifier, only the division of the above-mentioned functional units is used as an example for illustration. The functional unit of the control device is completed, that is, the internal structure of the control device is divided into different functional units to complete all or part of the functions described above; or a unified functional unit is used to complete the functions of the above-mentioned multiple units. It should be understood that the control device 1400 belongs to the same concept as the above-mentioned method for processing a message and a method for sending an identifier. Only the steps performed by each unit of the control device are illustrated here, but it does not mean that the above-mentioned implementation is not implemented. For other steps or optional methods in the example, the specific implementation process thereof can be found in the relevant description of the above method example section, and details are not repeated here.

Corresponding to the method embodiments and the virtual device embodiments provided by the present application, the embodiments of the present application further provide a network device, and the hardware structure of the network device is introduced below.

FIG. 15 is a schematic structural diagram of a network device 1500 provided by an embodiment of the present application. The apparatus 1500 can execute the first network device, the second network device or the control device shown in FIG. 4 , FIG. 5 , and FIG. 6 ; or the first network device shown in FIG. 7 to FIG. 11 such as PE1 , the second network device such as ACC1 or MC1, or a method for controlling device execution. Referring to the schematic structural diagram of the apparatus shown in FIG. 15 , the apparatus 1500 includes at least one processor 1501 , a communication bus 1502 and at least one communication interface 1504 , and optionally, the apparatus 1500 may further include a memory 1503 .

Optionally, the network device 1500 may be implemented by a general bus architecture, such as the communication bus 1502 shown in FIG. 15 .

The processor 1501 may be a general-purpose CPU, NP, microprocessor, or may be one or more integrated circuits for implementing the solutions of the present application, such as application-specific integrated circuits (ASIC), programmable logic A device (programmable logic device, PLD) or a combination thereof. The above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general-purpose array logic (generic array logic, GAL) or any combination thereof.

The communication bus 1502 is used to transfer information between the aforementioned components. The communication bus 1502 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

The memory 1503 can be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, or can be random access memory (RAM) or can store information and instructions Other types of dynamic storage devices, it can also be electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage , optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage medium or other magnetic storage device, or can be used to carry or store desired program code in the form of instructions or data structures and any other medium that can be accessed by a computer, but is not limited thereto. The memory 1503 may exist independently and be connected to the processor 1501 through the communication bus 1502 . The memory 1503 may also be integrated with the processor 1501.

Communication interface 1504 uses any transceiver-like device for communicating with other devices or a communication network. The communication interface 1504 includes a wired communication interface and may also include a wireless communication interface. Wherein, the wired communication interface may be, for example, an Ethernet interface. The Ethernet interface can be an optical interface, an electrical interface or a combination thereof. The wireless communication interface may be a wireless local area network (wireless local area networks, WLAN) interface, a cellular network communication interface or a combination thereof, and the like. The communication interface 1504 can also be used to receive a configuration instruction, so that the processor 801 can obtain the first identifier according to the instruction of the configuration instruction, obtain the first message according to the first identifier, and the like. The network device may also include other communication interfaces with which configuration instructions are received.

In a specific implementation, as an example, the network device 1500 may include multiple processors, such as the processor 1501 and the processor 1505 shown in FIG. 15 . Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

In some embodiments, the memory 1503 is used to store the program code 1510 for executing the solutions of the present application, and the processor 1501 can execute the program code 1510 stored in the memory 1503 . That is, the network device 1500 can implement the method provided by the method embodiment through the processor 1501 and the program code 1510 in the memory 1503 .

FIG. 16 is a schematic structural diagram of a network device 1600 provided by an embodiment of the present application. The apparatus 1500 can execute the first network device, the second network device or the control device shown in FIG. 4 , FIG. 5 , and FIG. 6 ; or the first network device shown in FIG. 7 to FIG. 11 such as PE1 , the second network device such as ACC1 or MC1, or a method for controlling device execution. Refer to the schematic diagram of the device structure shown in FIG. 16 . The apparatus 1600 includes a main control board and one or more interface boards, and the main control board is communicatively connected with the interface boards. The main control board is also called the main processing unit (MPU) or the route processor card (route processor card). The main control board is responsible for the control and management of each component in the device 1600, including routing calculation, equipment management and maintenance functions . Interface boards, also known as line processing units (LPUs) or line cards, are used to forward data. In some embodiments, the apparatus 1600 may also include a switch fabric board, the switch fabric board is communicatively connected to the main control board and the interface board, the switch fabric board is used to forward data between the interface boards, and the switch fabric board may also be referred to as a switch fabric Board unit (switch fabric unit, SFU). The interface board includes a central processing unit, a memory, a forwarding chip and a physical interface card (PIC). The central processing unit is connected in communication with the memory, the network processor and the physical interface card, respectively. The memory is used to store the forwarding table. The forwarding chip is used to forward the received message based on the forwarding table stored in the memory. If the destination address of the message is the address of the device 1600, the message is sent to the central processing unit (CPU), such as Processing by the central processing unit 1631; if the destination address of the message is not the address of the device 1600, the next hop and outgoing interface corresponding to the destination address are found from the forwarding table according to the destination address, and the message is forwarded to the destination address the corresponding outgoing interface. The forwarding chip may be a network processor (NP). The PIC, also known as a daughter card, can be installed on the interface board and is responsible for converting photoelectric signals into data packets and forwarding the data packets to the forwarding chip for processing after checking the validity of the data packets. In some embodiments, the central processing unit can also perform the function of a forwarding chip, for example, software forwarding is implemented based on a general-purpose CPU, so that a forwarding chip is not required in the interface board. The communication connection between the main control board, the interface board, and the switching network board can be realized through the bus. In some embodiments, the forwarding chip may be implemented by an application-specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

Logically, the apparatus 1600 includes a control plane and a forwarding plane, the control plane includes a main control board and a central processing unit, and the forwarding plane includes various components that perform forwarding, such as memory, PIC, and NP. The control plane performs functions such as routers, generating forwarding tables, processing signaling and protocol packets, and configuring and maintaining device status. The control plane delivers the generated forwarding tables to the forwarding plane. The forwarding table forwards the message received by the PIC of the device 1600 by looking up the table. The forwarding table issued by the control plane can be stored in the memory. In some embodiments, the control plane and forwarding plane may be completely separate and not on the same device.

It is worth noting that there may be one or more main control boards, and when there are multiple main control boards, they may include the main main control board and the backup main control board. There may be one or more interface boards. The stronger the data processing capability of the network device, the more interface boards are provided. There can also be one or more physical interface cards on the interface board. There may be no switching fabric boards, or there may be one or more boards. When there are multiple boards, they can jointly implement load sharing and redundant backup. Under the centralized forwarding architecture, the network device does not need to switch the network board, and the interface board is responsible for the processing function of the service data of the entire system. Under the distributed forwarding architecture, a network device may have at least one switching network board, and the switching network board realizes data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network devices in a distributed architecture are greater than those in a centralized architecture. Optionally, the form of the network device can also be that there is only one board, that is, there is no switching network board, and the functions of the interface board and the main control board are integrated on this board. The central processing unit on the board can be combined into a central processing unit on this board to perform the functions of the two superimposed, the data exchange and processing capacity of this form of equipment is low (for example, low-end switches or routers and other networks. equipment). The specific architecture used depends on the specific networking deployment scenario, and there is no restriction here.

In a possible design, the present application provides a network device, where the network device includes a controller and a first forwarding sub-device. The first forwarding sub-device includes: an interface board, and further, may also include a switching network board. The first forwarding sub-device is configured to perform the function of the interface board in the above-mentioned FIG. 16 , and further, may also perform the function of the switching network board in the above-mentioned FIG. 16 . The controller includes a receiver, a processor, a transmitter, random access memory, read only memory, and a bus. Wherein, the processor is respectively coupled to the receiver, the transmitter, the random access memory and the read only memory through the bus. Wherein, when the controller needs to be operated, the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to start the controller, and the controller is guided to enter the normal operation state. After the controller enters the normal operation state, the application program and the operating system are run in the random access memory, so that the processor executes the functions of the above-mentioned main control board.

The steps of the methods or algorithms described in conjunction with the disclosure of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage known in the art in the medium. An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium may reside in an ASIC. Alternatively, the ASIC may be located in the user equipment. Of course, the processor and storage medium may also exist in the user equipment as discrete components.

The present application provides a computer storage medium for storing programs, codes or instructions used by the above-mentioned network device. When the processor or hardware device executes these programs, codes or instructions, the functions or steps of the above-mentioned network device can be completed.

An embodiment of the present application further provides a chip system, including: a processor, where the processor is coupled with a memory, the memory is used to store a program or an instruction, and when the program or instruction is executed by the processor, the The system-on-a-chip implements the method in any of the above method examples.

Optionally, the number of processors in the chip system may be one or more. The processor can be implemented by hardware or by software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software codes stored in memory.

Optionally, there may also be one or more memories in the chip system. The memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application. Exemplarily, the memory can be a non-transitory processor, such as a read-only memory ROM, which can be integrated with the processor on the same chip, or can be provided on different chips. The setting method of the processor is not particularly limited.

Exemplarily, the system-on-chip may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC), It can also be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller). controller unit, MCU), it can also be a programmable logic device (PLD) or other integrated chips.

It should be understood that each step in the above method examples may be implemented by hardware integrated logic circuits in a processor or instructions in the form of software. The method steps disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

The present application provides a network system, as shown in FIG. 17 , the network system includes a first network device and a second network device. The first network device may execute the method executed by the first network device shown in FIG. 4 , FIG. 5 , and FIG. 6 , or the method executed by the first network device shown in FIG. 7 to FIG. 11 such as PE1; the first network device The device may perform the method performed by the second network device shown in FIG. 4 , FIG. 5 , and FIG. 6 , or the method performed by the second network device shown in FIG. 7 to FIG. 11 such as ACC1 or MC1 .

Optionally, the network system further includes a control device, and the control device can perform the methods performed by the control devices shown in FIG. 4 , FIG. 5 , and FIG. 6 , or the methods performed by the control devices shown in FIGS. 7 to 11 .

Those skilled in the art should appreciate that, in one or more of the above examples, the functions described in this application may be implemented in hardware or in a combination of hardware and software. When implemented using a combination of hardware and software, the software may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

It should be understood that the processor mentioned in the embodiments of the present invention may be a central processing unit (Central Processing Unit, CPU), and may also be other general-purpose processors, digital signal processors (Digital Signal Processors, DSP), application-specific integrated circuits ( Application Specific Integrated Circuit, ASIC), off-the-shelf Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory mentioned in the embodiments of the present invention may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be ROM, PROM, erasable EPROM, EEPROM or flash memory. Volatile memory may be random access memory RAM, which acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as SRAM, DRAM, SDRAM, DDR SDRAM, ESDRAM, SLDRAM, and DR RAM, among others.

It should be noted that the memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.

In various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not imply the sequence of execution, some or all of the steps may be executed in parallel or sequentially, and the execution sequence of each process should be determined by its function and inherent logic , and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art can realize 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. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, a network device or a terminal device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The relevant parts of the various method embodiments of the present invention may refer to each other; the apparatus provided by each apparatus embodiment is used to execute the method provided by the corresponding method embodiment, so each apparatus embodiment may refer to the relevant method embodiments in the relevant method embodiments. partially understood.

The device structure diagrams given in each device embodiment of the present invention only show a simplified design of the corresponding device. In practical applications, the apparatus may include any number of transmitters, receivers, processors, memories, etc., to implement the functions or operations performed by the apparatus in each apparatus embodiment of the present invention, and all apparatuses that can implement the present application All are within the scope of protection of this application.

The names of messages/frames/indication information, modules or units provided in the embodiments of the present invention are only examples, and other names may be used as long as the messages/frames/indication information, modules or units have the same functions.

The terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. As used in the embodiments of the present invention and the appended claims, the singular forms "a," "the," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

The specific embodiments described above further describe the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that different embodiments can be combined, and the above are only specific embodiments of the present invention. , is not used to limit the protection scope of the present invention, any combination, modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included within the protection scope of the present invention. As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand: The technical solutions described in the embodiments are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims (35)

A message sending method, comprising: The first network device obtains a first packet, and an Internet Protocol IP extension header of the first packet includes a first identifier, where the first identifier is used to indicate a service requirement corresponding to the first packet; Based on the first identifier and the second identifier, determine the path indication information corresponding to the first packet, the destination address of the first packet includes the second identifier, and the path indication information includes: network slice a list of identifiers and/or segment identifiers; The first packet is updated based on the path indication information to obtain a second packet, and the second packet is sent. The method of claim 1, wherein the second identification comprises a segment identification. The method according to claim 1 or 2, wherein the determining the path indication information based on the first identifier and the second identifier comprises: Determine a forwarding policy for the first packet based on the second identifier, where the forwarding policy includes a first correspondence between the first identifier and the path indication information; The path indication information is determined based on the first identifier and the first correspondence. The method according to claim 1 or 2, wherein the determining the path indication information based on the first identifier and the second identifier comprises: determining a third identifier corresponding to the first identifier based on the first identifier; Determine a forwarding policy of the first packet based on the second identifier, where the forwarding policy includes a second correspondence between the third identifier and the path indication information; The path indication information is determined based on the third identifier and the second correspondence. A message sending method, comprising: The first network device obtains a first packet, and an Internet Protocol IP header of the first packet includes a first identifier, where the first identifier is used to indicate a service requirement corresponding to the first packet; Corresponding path indication information is determined based on the first identifier, where the path indication information includes: a network slice identifier; The first packet is updated based on the path indication information to obtain a second packet, and the second packet is sent. The method according to claim 5, wherein the first network device includes a correspondence between the first identifier and the path indication information, and the determination of the corresponding path indication information based on the first identifier ,include: The path indication information is determined based on the first identifier and the corresponding relationship. The method according to claim 5 or 6, wherein the first identifier comprises a network slice identifier, and the first identifier instructs the first network device to determine the network slice identifier based on the first identifier . The method according to any one of claims 1-6, wherein the second packet includes the path indication information. The method according to claim 8, wherein the path indication information includes the network slice identifier, and the HBH or destination option header of the second packet includes the network slice identifier. The method according to any one of claims 1-9, wherein the first identifier includes a segment identifier, a segment routing header SRH of the first packet includes the first identifier, the IP address The extension header includes the SRH. The method according to any one of claims 1-10, wherein the first identifier includes an intent segment identifier, and the intent segment identifier instructs the first network device to determine a corresponding path based on the first identifier Instructions. The method according to claim 11, wherein the first identification further includes an indication mark, and the indication mark indicates that the first mark is an intent segment identification. A message sending method, comprising: The first network device obtains the first packet, and the hop-by-hop option header HBH or the destination option header of the first packet includes a first identifier, where the first identifier is used to indicate a service requirement corresponding to the first packet ; Path indication information corresponding to the first packet is determined based on the first identifier, where the path indication information includes: a segment identifier list; The first packet is updated based on the segment identifier list to obtain a second packet, and the second packet is sent. The method according to claim 13, wherein the second message includes the segment identifier list. The method according to any one of claims 1-6, 8, 13 or 14, wherein the first identifier includes an intent identifier, and the first packet includes a hop-by-hop option header HBH or a destination option header in the The intent identifier is included, and the IP extension header includes the HBH or the destination option header. The method according to any one of claims 1-15, wherein the obtaining, by the first network device, the first packet includes: receiving, by the first network device, a third packet sent by the second network device, where the third packet includes the first identifier; The first packet is the third packet, or the first network device generates the first packet based on the third packet, the first network device belongs to the first network, and the first network device belongs to the first network. Two network devices belong to a second network, and the first network is different from the second network. The method according to claim 16, wherein at least two network devices included in the first network can perform the determining of the corresponding path indication information based on the first identifier, and the at least two network devices include the first network device. The method according to claim 17, wherein at least two network devices included in the second network can also perform the determining of the corresponding path indication information based on the first identifier. The method according to any one of claims 16-18, wherein the first network and the second network belong to different interior gateway protocol (IGP) domains, or the first network and the second network belong to different interior gateway protocol (IGP) domains, or the first network and the second network belong to different autonomous systems AS. The method according to any one of claims 1-19, wherein the network slice identifier includes a slice identifier SliceID and/or a flexible algorithm identifier. A message sending method, comprising: The first network device obtains a first identifier, where the first identifier corresponds to a service requirement; Generating a first packet, the Internet Protocol IP extension header of the first packet includes the first identifier, the first packet further includes a second identifier, and the destination address of the first packet includes the The second identifier or the segment routing header SRH of the first packet includes the second identifier; Sending the first message to a second network device, where the first identifier and the second identifier are used to enable the second network device to determine the first message based on the first identifier and the second identifier Path indication information corresponding to the packet, where the path indication information includes a list of network slice identifiers and/or segment identifiers. The method according to claim 21, wherein the second identifier comprises a virtual private network segment identifier VPN SID or an intent segment identifier. A message sending method, comprising: The first network device obtains a first identifier, where the first identifier corresponds to a service requirement; generating a first packet, where the IP header of the first packet includes the first identifier; Send the first packet to a second network device, where the first identifier is used to enable the second network device to determine corresponding path indication information based on the first identifier, where the path indication information includes a network slice identifier. The method according to any one of claims 21-23, wherein the first identifier includes a segment identifier, and a segment routing header SRH of the first packet includes the first identifier. The method according to any one of claims 21-23, wherein the first identifier is included in a hop-by-hop option header HBH or a destination option header of the first packet. A message sending method, comprising: The first network device obtains a first identifier, where the first identifier corresponds to a service requirement; generating a first packet, where the first identifier is included in the hop-by-hop option header HBH or the destination option header of the first packet; Sending the first packet to the second network device, where the first identifier is used to enable the second network device to determine path indication information corresponding to the first packet based on the first identifier, where the path indicates The information includes a list of first segment identifiers. The method according to any one of claims 21-23, 25 or 26, wherein the first identification comprises an intent identification. The method according to any one of claims 21-26, wherein the obtaining the first identification comprises: A second-segment identification list sent by the control device is received, where the second-segment identification list includes the first identification. A method for sending an identifier, comprising: the control device obtains a first identifier, where the first identifier corresponds to a service requirement; Determine the first segment identifier list corresponding to the target service, the first segment identifier list includes the first identifier, and the first segment identifier list is used to indicate the first forwarding path through which the message corresponding to the target service passes , the first forwarding path passes through a first network device included in the first network, and the first identifier is used to enable the first network device to determine corresponding path indication information based on the first identifier, and the path indication information Including: network slice identifier and \ or second segment identifier list; The first segment identification list is sent. The method according to claim 29, wherein the first identifier comprises an intent segment identifier or a network slice segment identifier. The method according to claim 29 or 30, wherein the determining the first segment identifier list corresponding to the target service comprises: According to the service requirements corresponding to the target service, the first segment identification list is obtained by calculation. The method according to any one of claims 29-31, wherein the first segment identification list further includes a second identification, and the second identification includes a virtual private network segment identification VPN SID or an intent segment identification. The method according to claim 32, wherein at least two network devices included in the first network can perform the determining of corresponding path indication information based on the first identifier, and the first network includes at least two network devices. The two network devices include the first network device. The method according to any one of claims 29-33, wherein the first segment identifier list is carried in a link state protocol packet or a path calculation unit communication protocol packet and sent. A network device, characterized in that the device comprises a communication interface and a processor; the processor loads and executes instructions to implement the method of any one of claims 1-34.

Images