Message processing method and device, electronic equipment, storage medium and computer program product

Abstract

The application discloses a message processing method and device, electronic equipment, storage medium and computer program product, wherein the method comprises: a first network node in a first domain receives a first message; a first identifier is encapsulated in a set field of a first message header of the first message; the first identifier represents an identifier having a first set mapping relationship with traffic characteristics of the first message; the set field of the first message header is queried to obtain the first identifier, and the first message is encapsulated based on the first identifier to obtain a second message; wherein the second message encapsulates a second message header corresponding to a first SRv6TE Policy, the first SRv6TE Policy represents an SRv6TE Policy having a second set mapping relationship with the first identifier, and the first SRv6TE Policy is used to describe an SRv6TE Policy of the second message in the first domain; and the second message is sent out.

Description

Technical Field

[0001] This application relates to the field of wireless technology, and in particular to a message processing method, apparatus, electronic device, storage medium, and computer program product. Background Technology

[0002] In related technologies, when a message forwarding path involves multiple domains, any change in a node of any subdomain may cause the head node of the main domain to replan the path, increasing the resource consumption of message forwarding. Summary of the Invention

[0003] To address the related technical issues, embodiments of this application provide a message processing method, apparatus, electronic device, storage medium, and computer program product.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides a message processing method applied to a first network node in a first domain, the method comprising:

[0006] Receive a first message; the first message header of the first message contains a first identifier encapsulated in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message;

[0007] The first identifier is obtained by querying the defined field of the first message header, and the first message is encapsulated based on the first identifier to obtain the second message; wherein the second message encapsulates a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second defined mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second message in the first field;

[0008] Send the second message.

[0009] In the above scheme, querying the set field of the first message header to obtain the first identifier, and encapsulating the first message based on the first identifier to obtain the second message includes:

[0010] Execute the first instruction bound to the first segment identifier (SID); where,

[0011] The first SID represents the destination address in the first packet header; the first instruction is used to instruct the first network node to perform the following operations: query the first identifier in the set field of the first packet header, and encapsulate the first packet based on the first identifier.

[0012] In the above scheme, the working mode of the encapsulated message corresponding to the first instruction includes: encaps mode or insert mode.

[0013] In the above scheme, when the first identifier is encapsulated in a field in the Hop-by-Hop (HBH) extension header and / or a field in the Destination Options Header (DOH) extension header, the first instruction encapsulates the message based on the insert mode.

[0014] In the above scheme, the field type corresponding to the setting field includes one or more of the following: flow label, field type of field located in HBH extension header, field type of field located in DOH extension header, and field type of field located in Segment Routing Header (SRH).

[0015] The field types of the fields located in the SRH include one or more of the following: label, type-length-value (TLV).

[0016] In the above scheme, the first identifier includes one or more of the following:

[0017] The first information is used to identify the user corresponding to the first message;

[0018] The second information is used to identify the service corresponding to the first message;

[0019] The third information is used to identify the network element processing method corresponding to the first message.

[0020] The method in the above scheme further includes:

[0021] Receive the second set mapping relationship sent by the controller or upper-level control node.

[0022] This application embodiment also provides a message processing method applied to a second network node, the second network node representing the head network node in a second domain; the method includes:

[0023] A first message header is encapsulated in a third message to obtain a first message; a first identifier is encapsulated in a setting field of the first message header; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; the first identifier is used by a first network node in a first domain to encapsulate the first message after receiving it to obtain a second message; the second message encapsulates a second message header corresponding to a first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second message in the first domain;

[0024] Send the first message.

[0025] In the above scheme, the field type corresponding to the set field includes one or more of the following: flow tag, field type of field located in HBH extension header, field type of field located in DOH extension header, and field type of field located in SRH.

[0026] In the above scheme, the first identifier includes one or more of the following:

[0027] The first information is used to identify the user corresponding to the first message;

[0028] The second information is used to identify the service corresponding to the first message;

[0029] The third information is used to identify the network element processing method corresponding to the first message.

[0030] The method in the above scheme further includes:

[0031] Receive the first set mapping relationship sent by the controller or upper-level control node.

[0032] This application embodiment also provides a message processing apparatus, applied to a first network node in a first domain, including:

[0033] The first receiving unit is used to receive the first message; the first message header of the first message contains a first identifier encapsulated in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message;

[0034] The first encapsulation unit is used to query the set field of the first message header to obtain the first identifier, and encapsulate the first message based on the first identifier to obtain the second message; wherein, the second message encapsulates a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second message in the first field;

[0035] The first sending unit is used to send the second message.

[0036] This application embodiment also provides a message processing apparatus applied to a second network node, the second network node representing the head network node in a second domain, including:

[0037] The second encapsulation unit is used to encapsulate a first packet header into a third packet to obtain a first packet. The first packet header contains a first identifier in a setting field. The first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first packet. The first identifier is used by the first network node in the first domain to encapsulate the first packet after receiving it to obtain a second packet. The second packet contains a second packet header corresponding to a first SRv6 TE Policy. The first SRv6 TE Policy represents an SRv6 TEPolicy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TEPolicy of the second packet in the first domain.

[0038] The second sending unit is used to send the first message.

[0039] This application also provides an electronic device, including: a first processor and a first communication interface; wherein,

[0040] The first communication interface is used to receive a first message; the first message header of the first message contains a first identifier encapsulated in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; and to send a second message.

[0041] The first processor is configured to query the defined field of the first message header to obtain the first identifier, and encapsulate the first message based on the first identifier to obtain a second message; wherein the second message encapsulates a second message header corresponding to a first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second defined mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second message in the first field.

[0042] This embodiment also provides an electronic device, including: a second processor and a second communication interface; wherein,

[0043] The second processor is configured to encapsulate a first header into a third message to obtain a first message; the first header contains a first identifier in a configuration field; the first identifier represents an identifier that has a first defined mapping relationship with the traffic characteristics of the first message; the first identifier is used by a first network node in the first domain to encapsulate the first message after receiving it to obtain a second message; the second message contains a second header corresponding to a first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second defined mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TEPolicy of the second message in the first domain;

[0044] The second communication interface is used to send the first message.

[0045] This application also provides an electronic device, including: a first processor and a first memory for storing a computer program capable of running on the processor.

[0046] Wherein, when the first processor is used to run the computer program, it executes any of the steps of the method described above on the first network node side.

[0047] This application also provides an electronic device, including: a second processor and a second memory for storing a computer program capable of running on the processor.

[0048] Wherein, when the second processor is used to run the computer program, it executes any of the steps of the method described above on the second network node side.

[0049] This application embodiment also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of any of the methods described above on the first network node side, or implements the steps of any of the methods described above on the second network node side.

[0050] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the methods described above on the first network node side, or implements the steps of any of the methods described above on the second network node side.

[0051] Based on this, in this embodiment of the application, a first network node in the first domain receives a first message; wherein, the first message header of the first message encapsulates a first identifier in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; then, the first network node queries the setting field of the first message header to obtain the first identifier, and encapsulates the first message based on the first identifier to obtain a second message; wherein, the second message encapsulates a second message header corresponding to a first SRv6 TEPolicy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TEPolicy of the second message in the first domain; then, the first network node sends the second message. In the above scheme, the first network node of the first domain encapsulates the first packet with a packet header corresponding to the first SRv6 TE Policy based on the first identifier that has a first set mapping relationship with the traffic characteristics. This enables the second packet obtained after encapsulation to be forwarded in the first domain. That is, the first network node provides traffic redirection service for the packet based on the first identifier. Compared with related technologies, when the head node of the main domain plans the packet forwarding path, even if the nodes in the subdomain change, the head node of the main domain does not need to replan the packet forwarding path, thereby reducing the resource consumption of packet forwarding. Attached Figure Description

[0052] Figure 1 This is a schematic diagram of a hierarchical business chain;

[0053] Figure 2 This is a schematic diagram of message processing in related technologies;

[0054] Figure 3 This is a schematic diagram of another message processing technique in related technologies;

[0055] Figure 4 This is a schematic diagram of the third type of message processing in related technologies;

[0056] Figure 5A schematic diagram illustrating the implementation flow of a message processing method provided in an embodiment of this application;

[0057] Figure 6 A schematic diagram of the packaging location provided in an embodiment of this application;

[0058] Figure 7 This is a schematic diagram of a packaging method provided in an embodiment of this application;

[0059] Figure 8 This is a schematic diagram illustrating another packaging method provided in an embodiment of this application;

[0060] Figure 9 A schematic diagram illustrating the implementation flow of another message processing method provided in this application embodiment;

[0061] Figure 10 This is a schematic diagram of the overall process of a message processing method provided in an embodiment of this application;

[0062] Figure 11 This application provides a schematic diagram of a message structure change as illustrated in its embodiments.

[0063] Figure 12 This is a schematic diagram of the structure of a message processing device provided in an embodiment of this application;

[0064] Figure 13 A schematic diagram of another message processing apparatus provided in the embodiments of this application;

[0065] Figure 14 A schematic diagram of the hardware composition of an electronic device provided in an embodiment of this application;

[0066] Figure 15 This is a schematic diagram of the hardware configuration of another electronic device provided in an embodiment of this application. Detailed Implementation

[0067] To facilitate understanding, the main concepts involved in this application will first be explained:

[0068] Service Function Chain (SFC): A technology that provides ordered services to a network. SFC connects nodes that provide services in the network at the logical level, thereby forming an ordered service composition.

[0069] Specifically, SFC paths can be encapsulated in packets to guide traffic through specified nodes in an orderly manner. In practical applications, SFC can be implemented based on policy-based routing (PBR), Next Service Header (NSH), and Segment Routing Internet Protocol Version 6 (SRv6).

[0070] Hierarchical Service Chain: As networks evolve and become increasingly massive, managing service chains becomes more complex and challenging. To address this, related technologies divide the network into multiple independent domains. Each domain builds its own service chain based on nodes within that domain; these service chains can be described as lower-level chains or sub-chains. Then, a service chain is formed based on the edge nodes of these domains. This service chain can span the entire network and can be described as an upper-level chain or main chain. The domain where the nodes in the upper-level chain reside can be considered the main domain, and the domain where the nodes in the lower-level chain reside can be considered sub-domains. The upper-level chain contains edge nodes of the corresponding sub-domains of the lower-level chains. In this way, the upper-level chain can connect lower-level chains located in different sub-domains, realizing a hierarchical service chain and thus providing a complete end-to-end service chain.

[0071] For example, see Figure 1 R1, R2, and R5 can be considered nodes in domain 1, forming a service chain 1. R2, R3, and R4 can be considered nodes in domain 2, forming a service chain 2. R2 is an edge node of domain 2 and also an intermediate node of domain 1. Service chain 2 can be considered a sub-chain of service chain 1, and domain 2 can be considered a sub-domain of domain 1. After receiving a message from R1, R2 can forward the message to a node in domain 2, such as R3, or to a node in another domain.

[0072] SRv6: A protocol designed based on source routing mechanism for forwarding SRv6 messages over a network.

[0073] In practical applications, messages transmitted based on the SRv6 protocol can be represented as SRv6 messages. Nodes along the message transmission path are configured with SIDs, which are presented in the form of Internet Protocol Version 6 (IPv6) addresses. During message transmission, the SIDs of different nodes along the transmission path can be arranged into an ordered list, i.e., a segment list, and this segment list is pushed onto the SRH header in the form of an IPv6 address stack. This allows the SRv6 message to be forwarded in the network according to the path indicated by the SRH; the SRH can also be represented as an SRH extension header.

[0074] In practical applications, SRv6 primarily operates in two modes: SRv6 BE (Best Effort) and SRv6 TE (Traffic Engineering) Policy. SRv6 BE does not constrain the packet forwarding path; it uses only a single SID to specify the destination address and forwards SRv6 packets to that address based on the shortest path algorithm—a best-effort mode. SRv6 TE Policy, on the other hand, requires the SRH to specify the path to be followed during packet forwarding, thus providing end-to-end service from source to destination.

[0075] In practical applications, an SRv6 TE Policy can also be understood as a specific forwarding strategy, or it can be described as a TEPolicy. An SRv6 TE Policy can describe a packet forwarding path based on the SRv6 TE Policy's operating mode. Upper-layer control nodes or controllers can configure SRv6 TE Policies for the header node based on the packet forwarding path planned by the header node of the primary domain. This can also be described as the header node of the primary domain planning SRv6 TE Policies. Each SRv6 TE Policy corresponds to a Segment List in an SRv6 packet.

[0076] For example, see Figure 2R1, R2, and R5 are nodes in domain 1, and R2, R3, and R4 are nodes in domain 2. R1 is the head node of domain 1, and domain 2 is a subdomain of domain 1. R1 is configured with TE Policy 1, and the corresponding segment list for TE Policy 1 is [B->C->D->B->E]. This segment list can also be expressed as (E, B, D, C, B). Here, the packet forwarding path described by TE Policy 1 is: R1->R2->R3->R4->R2->R5, which can also be expressed as: A->B->C->D->B->E. A, B, C, D, and E are all SIDs, and R1, R2, R3, R4, and R5 are identified by A, B, C, D, and E, respectively.

[0077] Endpoint directives: These instruct nodes on the actions they should perform when processing a SID. Each SID is associated with an Endpoint directive. The SID a node processes can be explicitly specified by the SRH or destination address in the received packet, thus providing processing such as forwarding, encapsulation, and decapsulation for the packet.

[0078] For example, the Endpoint directive End can be used to instruct a node to perform the following actions on a packet: decrement the Segment Left value in the packet's SRH by 1, update the SID in the Segment List indexed by the Segment Left value to the destination address of the packet, and then forward the packet based on the updated destination address.

[0079] For example, see Figure 2 R2 is locally configured with End SID = B. Here, R2 can be considered as the node identified by B, and B can be considered as being bound to the Endpoint command End. If the destination address of packet 1 received by R2 is B, then R2 will, according to the End command bound to B, decrement the Segment Left value in the SRH of packet 1 by 1, update the SID in the Segment List indexed by the Segment Left value to the destination address of packet 1, and then forward packet 1 based on the updated destination address.

[0080] In practical applications, when a message forwarding path involves multiple domains, the header node of the primary domain can pre-plan the path. However, any change in the node of any subdomain may cause the header node to replan the path. For example, see... Figure 2The packet forwarding path represented by TE Policy1 planned by R1 is A->B->C->D->B->E. If the node in domain 2 changes, for example, R4 is deleted from domain 2, then R1 needs to replan the path. For example, the replanned packet forwarding path represented by TE Policy1 is A->B->C->B->E.

[0081] In related technologies, packet forwarding is based on Binding SID (BSID) to isolate different domains to a certain extent and prevent changes within a domain from spreading to other domains. It should be noted that BSID can be considered a type of SID.

[0082] Specifically, each BSID identifies one SRv6 TE Policy; that is, each BSID corresponds to one SRv6 TEPolicy, or in other words, each BSID corresponds to one packet forwarding path. The Endpoint command bound to the BSID is End.B6 (Endpoint bound to an SRv6 Policy). This command performs the following actions: resets the SRH for the packet and updates the destination address. The Segment List in the reset SRH corresponds to the SRv6 TE Policy associated with that BSID. In practical applications, one or more BSIDs can be configured to specify one or more SRv6 TE Policies for each edge node of a domain, thereby indicating the forwarding path of packets within that domain.

[0083] For example, see Figure 3 R1, R2, and R5 are nodes in domain 1, and R2, R3, and R4 are nodes in domain 2. R1 is the head node of domain 1, and domain 2 is a subdomain of domain 1. R2 is configured with "End.B6SID=B". Here, B corresponds to TE Policy2, and the segment list corresponding to TE Policy2 is [C->D->B9]. The segment list corresponding to TE Policy1 planned by R1 based on BSID is [B->E]. In this case, the destination address of the packet encapsulated by R1 based on TE Policy1 is B. After receiving the packet with the destination address B, R2 provides traffic redirection service for the packet based on BSID B. Specifically, R2 resets the SRH and updates the destination address of the packet based on the Endpoint instruction End.B6 corresponding to B and the TE Policy2 corresponding to B. The segment list in the reset SRH is (B9, D, C).

[0084] As can be seen in this example, a long packet forwarding path is split into two smaller segments by using BSID B. That is, the packet forwarding path A->B9->C->D->E involving domain 1 and domain 2 is split into: the forwarding path A->B9->E in domain 1 and the forwarding path B9->C->D in domain 2. The TE Policy2 corresponding to B9->C->D is identified by BSID B indicated in TE Policy1.

[0085] Understandably, R2 provides packet redirection services based on BSID. Therefore, when planning TE Policy1, R1 only needs to refer to the BSID already configured in R2, without needing to care about the content of TE Policy2 corresponding to the BSID. Even if the nodes in domain 2 change, R1 can still indicate the original BSID in the planned TE Policy1, and then the upper-layer control node or controller updates the TE Policy2 corresponding to the BSID, thereby realizing the update of the forwarding path.

[0086] For example, see Figure 3 If R4 is deleted in domain 2, R1 can still be configured with TE Policy1 with Segment List [B->E]. The upper-layer control node or controller only updates the TE Policy2 configured in R2. The Segment List corresponding to the updated TE Policy2 can be [C->B9]. In this case, R1 will still send the packet to R2. After receiving the packet with destination address B, R2 resets the SRH for the packet and updates the destination address based on the Endpoint instruction End.B6 corresponding to B and the updated TE Policy2. The Segment List in the reset SRH is (B9, C). Thus, the packet forwarding path is updated to A->B9->C->E.

[0087] Therefore, in the BSID-based packet path forwarding scheme, the head node of the primary domain does not need to replan the path for changes in every node in the subdomain, thus achieving inter-domain isolation to a certain extent. However, this isolation is not complete. In practical applications, if changes in the nodes of a subdomain cause changes in the number of forwarding paths for that domain, the number of BSIDs configured on the edge nodes of that domain also needs to be increased or decreased accordingly. This results in the head node of the primary domain needing to replan the path based on the added or deleted BSIDs.

[0088] For example, see Figure 4R1, R2, and R8 are nodes in domain 1, and R2, R3, R4, R5, R6, and R7 are nodes in domain 2. R1 is the head node of domain 1, and domain 2 is a subdomain of domain 1. Here, R2 is configured with "End.B6 SID=B1" and "End.B6 SID=B2", that is, R2 is configured with two SRv6 TE Policies, namely TE Policy 3 and TEPolicy 4. R1 needs to plan two SRv6 TE Policies based on the two BSIDs configured in R2 in order to correspond to the two packet forwarding paths in domain 2. Here, the SRv6 TE Policies planned by R1 are TE Policy 1 and TE Policy 2. Furthermore, if the nodes in domain 2 change, resulting in the addition or deletion of a packet forwarding path in domain 2, the SRv6 TE Policies planned by R1 also need to be adjusted accordingly.

[0089] It can be seen that in the relevant technologies, any change in a node of a subdomain may cause the head node of the main domain to replan the path, increasing the resource consumption of packet forwarding.

[0090] Based on this, in this embodiment of the application, a first network node in the first domain receives a first message; wherein, the first message header of the first message encapsulates a first identifier in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; then, the first network node queries the setting field of the first message header to obtain the first identifier, and encapsulates the first message based on the first identifier to obtain a second message; wherein, the second message encapsulates a second message header corresponding to a first SRv6 TEPolicy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TEPolicy of the second message in the first domain; then, the first network node sends the second message. In the above scheme, the first network node of the first domain encapsulates the first packet with a packet header corresponding to the first SRv6 TE Policy based on the first identifier that has a first set mapping relationship with the traffic characteristics. This enables the second packet obtained after encapsulation to be forwarded in the first domain. That is, the first network node provides traffic redirection service for the packet based on the first identifier. Compared with related technologies, the head node of the main domain does not need to refer to the BSID configured in the edge node of the subdomain when planning the packet forwarding path. Even if the nodes in the subdomain change and the BSID changes, the head node of the main domain does not need to replan the packet forwarding path, thereby reducing the resource consumption of packet forwarding.

[0091] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0092] This application provides a message processing method applied to a first network node in a first domain.

[0093] In practical applications, the first network node can be considered as the head node in the first domain, that is, an edge node. A network node can be understood as a network device that provides services in the network, or it can be described as a network element or node.

[0094] See Figure 5 The method includes:

[0095] Step 501: Receive the first message.

[0096] The first header of the first message contains a first identifier encapsulated in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message.

[0097] In practical applications, the first message can be an SRv6 message.

[0098] In one embodiment, receiving a first message includes:

[0099] Receive the first message sent by the network node of the second domain.

[0100] In practical applications, if the second domain is understood as the primary domain, the first domain can be understood as a subdomain of the second domain. The first and second domains can be connected through the first network node.

[0101] In practical applications, the first message can be sent directly from the second network node to the first network node, that is, the first network node can receive the first message sent by the second network node; where the second network node represents the head network node in the second domain.

[0102] The first message can also be forwarded to the first network node by one or more third network nodes in the second domain after being sent by the second network node; where the third network node represents an intermediate network node in the second domain. In this case, the first message is sent directly from the second network node to the third network node that performs the first forwarding before being forwarded by one or more third network nodes. Then, after one or more third network nodes perform one or more forwardings, the first network node receives the first message sent by the third network node that performs the last forwarding. This case can also be understood as the first message being sent from the second network node to the first network node. It should be noted that the role of the third network node in this case is equivalent to transparent forwarding. Therefore, the corresponding message sent by the second network node for the first message received by the first network node can be understood as the first message.

[0103] In practical applications, when a third network node forwards the first packet, it may change the destination address field in the first packet, but it will not change the encapsulation field of the first identifier in the first packet or the packet forwarding path.

[0104] Here, the first identifier and the traffic characteristics of the first message have a first set mapping relationship, and the first identifier can be used to identify the traffic characteristics of the first message.

[0105] In practical applications, traffic characteristics can include information such as the user, service, and network element processing method corresponding to the first packet, as well as features such as triples and quintuples. The user corresponding to the first packet can be a tenant requesting a service, and the service request initiated by the tenant is transmitted in the network in the form of a packet; the service corresponding to the first packet can be the service requested by the tenant, for example, cloud storage, video telephony, etc.; the network element processing method corresponding to the first packet can be used to indicate how network nodes process the first packet, such as path forwarding.

[0106] In one embodiment, the first identifier includes one or more of the following:

[0107] The first information is used to identify the user corresponding to the first message;

[0108] The second information is used to identify the service corresponding to the first message;

[0109] The third information is used to identify the network element processing method corresponding to the first message.

[0110] In practical applications, the first information may include the user's identifier and name; the second information may include the type of service; and the third information may include the actions corresponding to the network element processing method.

[0111] In practical applications, the first established mapping relationship can be described as a traffic identifier mapping table. This traffic identifier mapping table can map traffic features to relevant information of the first identifier. The relevant information of the first identifier can be: the encapsulation field of the first identifier in the first message, that is, the encapsulation position. The traffic identifier mapping table can include one or more mapping pairs. For example, a mapping pair can be represented as <traffic feature 1, identifier 1 in DOH>. This mapping pair can be understood as: traffic feature 1 corresponds to identifier 1, and identifier 1 needs to be encapsulated in the DOH extension header field of the message. Here, identifier 1 is equivalent to the first identifier in the embodiments of this application.

[0112] In practical applications, the first set mapping relationship can be sent from the controller or the upper-level control node to the second network node. The second network node can generate a first message encapsulated with the first identifier based on the first set mapping relationship.

[0113] Here, the first identifier is encapsulated in the configuration field of the first header of the first message.

[0114] In one embodiment, the field type corresponding to the set field includes one or more of the following: flow tag, field type of the field located in the HBH extension header, field type of the field located in the DOH extension header, and field type of the field located in the SRH.

[0115] Fields located in an SRH have a field type that includes one or more of the following: label, type length value (TLV).

[0116] In practical applications, both the HBH and DOH extension headers are equivalent to an IPv6 extension header. The IPv6 extension header is an optional structure in SRv6 packets, and SRv6 can include multiple IPv6 extension headers.

[0117] In practical applications, the field type corresponding to the field can also include: the field type of fields located in other IPv6 extension headers besides the HBH extension header and the DOH extension header.

[0118] For example, Figure 6 The SRv6 message structure in the related art is shown, and the field where the first identifier may be located in the first message following the message structure is circled.

[0119] Step 502: Query the set fields of the first message header to obtain the first identifier, and encapsulate the first message based on the first identifier to obtain the second message.

[0120] The second message encapsulates a second message header corresponding to the first SRv6 TE Policy. The first SRv6TE Policy represents an SRv6 TE Policy that has a second defined mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second message in the first field.

[0121] In practical applications, the first network node can use the Endpoint command to query the specified fields in the first header of the first message to obtain the first identifier, and then encapsulate the first message based on the first identifier to obtain the second message. The Endpoint command can specify the fields that the first network node needs to query; these fields are the specified fields.

[0122] In practical applications, during the encapsulation of the second header, the first network node can, based on the second established mapping relationship, use the SRv6 TE Policy that matches the first identifier as the first SRv6 TE Policy, and encapsulate the first packet with a new SRH based on the first SRv6 TE Policy, thereby achieving the encapsulation of the second header and obtaining the second packet; the SRH contains the Segment List corresponding to the first SRv6 TE Policy.

[0123] In practical applications, the second defined mapping relationship can be described as a traffic redirection strategy. This traffic redirection strategy can map the first identifier to the SRv6 TE Policy. The traffic redirection strategy can include one or more mapping strategies. For example, the mapping strategy can be represented as <Identifier 1 in DOH, SRv6 TE Policy 1> or <Class A, SRv6 TE Policy 1>. Class A can be a set of first identifiers of packets following the same first domain forwarding path, or a set of traffic characteristics of packets following the same first domain forwarding path. It can be understood that the first identifier and traffic characteristics have a first defined mapping relationship. Therefore, the mapping relationship between the set of traffic characteristics and the SRv6 TE Policy can also be regarded as the mapping relationship between the set of first identifiers and the SRv6 TE Policy.

[0124] In practical applications, the second mapping relationship can be sent from the controller or upper-level control node to the first network node. Based on this,

[0125] In one embodiment, the method further includes:

[0126] Receive the second set mapping relationship issued by the controller or upper-level control node.

[0127] In practical applications, the first SRv6 TE Policy can be used to describe the packet forwarding path of the second packet in the first field. Here, the second packet header corresponds to the first SRv6 TE Policy, which can be understood as the Segment List in the SRH of the second packet header corresponding to the first SRv6 TE Policy.

[0128] In practical applications, network nodes in the first domain can forward the second packet based on the packet forwarding path indicated by the Segment List in the second packet header. The packet forwarding path indicated by the Segment List in the second packet header is also the packet forwarding path of the first domain described by the first SRv6 TE Policy.

[0129] It can be seen that the first network node encapsulates the first packet with a packet header corresponding to the first SRv6 TE Policy based on the first identifier that has a first set mapping relationship with the traffic characteristics, so that the encapsulated second packet can be forwarded in the first domain. That is, the first network node provides traffic redirection services for the packet in the first domain based on the first identifier.

[0130] In practical applications, the second network node can plan the SRv6 TE Policy for the received message in the second domain. Here, the SRv6 TE Policy planned by the second network node can be described as the second SRv6 TEPolicy. Then, the second network node encapsulates the message header corresponding to the second SRv6 TE Policy for the received message, thereby obtaining the encapsulated message and sending it. The sent message is equivalent to the first message, and the message header corresponding to the second SRv6 TE Policy is equivalent to the first message header.

[0131] As can be seen from the embodiments of this application, after receiving the first packet, the first network node can provide traffic redirection services for the packet in the first domain based on the first identifier. Therefore, the second SRv6 TEPolicy planned by the second network node does not need to involve the specific forwarding path of the packet in the first domain, and can still guarantee the forwarding of the packet in the first domain based on the encapsulation operation of the first network node. Thus, the second SRv6 TEPolicy can also be considered as describing the packet forwarding path in both the first and second domains. Understandably, even if the nodes in the first domain change, the head node of the second domain does not need to replan the packet forwarding path, which is equivalent to eliminating the influence of the first domain on the second domain, isolating the first and second domains, and reducing resource consumption during packet forwarding.

[0132] Step 503: Send the second message.

[0133] In practical applications, the first network node can send the second message based on the message forwarding path indicated by the Segment List in the second message header.

[0134] In this embodiment, the first network node of the first domain encapsulates the first packet with a packet header corresponding to the first SRv6 TE Policy based on a first identifier that has a first set mapping relationship with the traffic characteristics. This enables the encapsulated second packet to be forwarded in the first domain. In other words, the first network node provides traffic redirection services for the packet based on the first identifier. Compared with related technologies, when planning the packet forwarding path, the head node of the main domain does not need to refer to the BSID configured in the edge node of the subdomain. Even if the nodes in the subdomain change and the BSID changes, the head node of the main domain does not need to replan the packet forwarding path, thereby reducing the resource consumption of packet forwarding.

[0135] The following section provides a detailed explanation of the query settings and the method for encapsulating the first message.

[0136] In one embodiment, a first identifier is obtained by querying a specified field in the first header, and a second message is obtained by encapsulating the first message based on the first identifier, including:

[0137] Execute the first instruction bound to the first SID.

[0138] Wherein, the first SID represents the destination address in the first packet header; the first instruction is used to instruct the first network node to perform the following operations: query the first identifier in the setting field of the first packet header, and encapsulate the first packet based on the first identifier.

[0139] In practical applications, a new type of Endpoint instruction can be defined. This type of instruction can be regarded as an Endpoint instruction that dynamically binds to an SRv6 TE Policy, equivalent to the first instruction in the embodiments of this application. For example, this type of instruction can be expressed as End.BD6 (Endpoint Dynamically Bound to an SRv6 TE Policy).

[0140] For example, the End.BD6 instruction may include at least: End.BD6.D, End.BD6.F, End.BD6.H, End.BD6.T, and End.BD6.V, wherein each instruction corresponds to a field type of a first identifier encapsulated field.

[0141] For example, Table 1 lists the full names of several End.BD6 instructions and their corresponding instructions.

[0142] Table 1

[0143]

[0144]

[0145] In practical applications, each End.BD6 instruction can be bound to a SID, which can be described as BDSID, equivalent to the first SID in the embodiments of this application.

[0146] In practical applications, a BDSID can be configured in the first network node. The second network node in the second domain can have this BDSID indicated in its SRv6 TE Policy for the first packet, ensuring that the destination address of the first packet received by the first network node is this BDSID. Upon receiving the first packet, the first network node executes the End.BD6 instruction bound to the BDSID, thereby retrieving the first identifier from the specified field in the first packet header and encapsulating the first packet based on the first identifier to obtain the second packet. Here, the End.BD6 instruction bound to the BDSID indicates the specified field, and the second packet encapsulates a second packet header corresponding to the first SRv6 TE Policy.

[0147] As can be seen, in this embodiment, the first identifier is dynamically queried based on the first instruction, and the SRv6 TE Policy is encapsulated based on the first identifier, thereby realizing the dynamic binding of the SRv6 TE Policy. This enables the first network node to provide traffic redirection services for packets based on the first identifier. Compared with related technologies, when the head node of the main domain plans the packet forwarding path, it does not need to refer to the BSID configured in the edge node of the subdomain. Even if the nodes in the subdomain change and the BSID changes, the head node of the main domain does not need to replan the packet forwarding path, thereby reducing the resource consumption of packet forwarding.

[0148] Furthermore, it is understandable that one BDSID can correspond to multiple SRv6 TE Policies. For example, suppose the DOH extension header of packet 1 received by the first network node encapsulates identifier 1, and the DOH extension header of packet 2 received by the first network node encapsulates identifier 2. Here, both packets 1 and 2 can be considered as the first packet. Although identifier 1 and identifier 2 are encapsulated in the same field type in packets 1 and 2 respectively, identifier 1 and identifier 2 are not the same. Therefore, when identifier 1 and identifier 2 correspond to different SRv6 TE Policies, the first network node can determine different SRv6 TE Policies for packets 1 and 2 based on the End.BD6.D instruction bound to the same BDSID. Thus, it can be seen that one BDSID can correspond to multiple SRv6 TE Policies. Therefore, the first network node can encapsulate different SRv6TE policies for packets by configuring only one BDSID. Compared with the related technology where one BSID corresponds to only one SRv6 TE policy, the solution in this application embodiment reduces the consumption of local configuration of the first domain and further reduces resource consumption.

[0149] In one embodiment, the working mode of the encapsulated message corresponding to the first instruction includes either encaps mode or insert mode.

[0150] In practical applications, the encapsulation method corresponding to the encaps mode is as follows: a new SRv6 header is added to the outer layer of the first packet. The SRv6 header includes the IPv6 basic header, the IPv6 extension header, and the SRH extension header.

[0151] The encapsulation method corresponding to insert mode is: insert a new SRH on top of the SRH of the first message.

[0152] It should be noted that the encapsulated message still contains the content of the original message. That is, the second message still contains the content of the first message, and some fields of the first message in the second message may have changed compared to the first message before encapsulation.

[0153] In practical applications, when the first message is encapsulated to obtain the second message based on the encaps mode, the SRv6 header added to the second message relative to the first message can be regarded as the second message header.

[0154] When the first message is encapsulated to obtain the second message based on the insert mode, the SRH added to the second message relative to the first message, as well as the content of the first message header in the second message other than the SRH, can be regarded as the second message header.

[0155] In practical applications, the second header can also encapsulate a first identifier. The first identifier can be encapsulated in a field of the same type in both the first and second headers, or it can be encapsulated in a field of different types in the first and second headers. Understandably, the network node receiving the second packet can obtain the first identifier by performing a single layer of parsing, thereby determining the traffic characteristics and performing subsequent processing based on these characteristics. This reduces the parsing difficulty, decreases performance overhead, and thus improves packet forwarding efficiency.

[0156] In practical applications, the first message and the second message can be understood as messages in the same forwarding path and together form a batch of traffic. Therefore, the traffic characteristics of the first message can also be understood as the traffic characteristics of the second message.

[0157] The following example, using the encapsulation of the first identifier, illustrates the working mode of the encapsulated message corresponding to the first instruction. It should be noted that in the following example, the first identifier is encapsulated in a field of the same type in both the first and second message headers. Figure 7 as well as Figure 8 The identifier 1 in the document corresponds to the first identifier in the embodiments of this application.

[0158] In practical applications, when the first identifier is encapsulated in a field of the first field type in the first header of the first message, during the encapsulation of the first message based on the encaps mode, the first identifier needs to be copied into a field of the first field type in the newly added SRv6 header.

[0159] For example, see Figure 7 When the first identifier is encapsulated in a field of the DOH extension header in the first header of the first message 1, after the first message is encapsulated based on the encaps mode to obtain the second message 1, the first identifier is located in a field of the DOH extension header in the newly added SRv6 header.

[0160] In practical applications, when the first identifier is encapsulated in a field of the first field type in the first header of the first message, and the first field type is a field type other than the field in the SRH, no processing is required on the first identifier during the encapsulation of the first message based on the insert mode.

[0161] For example, see Figure 8 When the first identifier is encapsulated in a field of the DOH extension header in the first header of the first message 1, after the first message 1 is encapsulated to obtain the second message 1 based on the insert mode, the first identifier is still located in a field of the DOH extension header.

[0162] In practical applications, when the first identifier is encapsulated in a field of the first field type in the first header of the first message, and the first field type is the field type of the field in the SRH, during the encapsulation of the first message based on the insert mode, the first identifier needs to be copied into the field of the first field type in the newly added SRH.

[0163] For example, see Figure 8 When the first identifier is encapsulated in the Tag field of the SRH in the first header of the first message 2, after the first message 2 is encapsulated based on the insert mode to obtain the second message 2, the first identifier is located in the Tag field of the newly added SRH.

[0164] In practical applications, the HBH and DOH extension headers contain a lot of content. Understandably, copying these extension headers during packet encapsulation could increase performance overhead. Based on the above example, it can be seen that when the first identifier is encapsulated in a field of type 1 in the first header of the first packet, and this first field type is a field type other than that in the SRH header, no processing of the first identifier is needed during the encapsulation of the first packet using insert mode. Therefore, in practical applications, when the first identifier is encapsulated in a field in the HBH extension header and / or a field in the DOH extension header, it is recommended that the first instruction encapsulate the packet using insert mode. Based on this,

[0165] In one embodiment, when the first identifier is encapsulated in a field in the HBH extension header and / or a field in the DOH extension header, the first instruction encapsulates the message based on insert mode.

[0166] This avoids the need to copy the HBH extension head and / or DOH extension head during the packaging process, thus reducing performance overhead.

[0167] Corresponding to the message processing method applied to the first network node in the above embodiments, this application also provides a message processing method applied to a second network node, where the second network node represents the head network node in the second domain. In practical applications, a network node can be understood as a network device used to provide services in the network, or it can be described as a network element or node.

[0168] See Figure 9 The method includes:

[0169] Step 901: Encapsulate the first message header into the third message to obtain the first message.

[0170] The first message header contains a first identifier encapsulated in a configuration field. The first identifier represents an identifier that has a first defined mapping relationship with the traffic characteristics of the first message. The first identifier is used by the first network node in the first domain to encapsulate the first message after receiving it, thus obtaining a second message. The second message contains a second message header corresponding to the first SRv6 TE Policy. The first SRv6 TE Policy represents an SRv6 TE Policy that has a second defined mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second message in the first domain.

[0171] Step 902: Send the first message.

[0172] In practical applications, the first network node can be considered as the head node, or edge node, of the first domain. If the second domain is understood as the main domain, then the first domain can be understood as a subdomain of the second domain. The first and second domains can be connected through the first network node.

[0173] In practical applications, the second network node can plan the SRv6TEPolicy of the third message in the second domain. Here, the planned SRv6 TE Policy is referred to as the second SRv6 TE Policy. Then, the second network node can encapsulate the header corresponding to the second SRv6 TE Policy for the third message, thereby obtaining the first message and sending it. Here, the header corresponding to the second SRv6 TE Policy is equivalent to the header of the first message.

[0174] During the encapsulation of the first packet header, the second network node can, based on the third mapping relationship, use the SRv6 TE Policy that matches the first identifier as the second SRv6 TE Policy, and encapsulate the first packet with a new SRH based on the second SRv6 TE Policy, thereby achieving the encapsulation of the first packet header and obtaining the first packet; the SRH contains the Segment List corresponding to the second SRv6 TE Policy.

[0175] In practical applications, the third mapping relationship can be described as a traffic redirection strategy. This traffic redirection strategy can map the first identifier to the SRv6 TE Policy. The traffic redirection strategy can include one or more mapping strategies. For example, the mapping strategy can be represented as <Identifier 1 in DOH, SRv6 TE Policy 1> or <Class A, SRv6 TE Policy 1>. Class A can be a set of first identifiers of packets following the same first domain forwarding path, or a set of traffic characteristics of packets following the same first domain forwarding path. It can be understood that the first identifier and traffic characteristics have a first mapping relationship. Therefore, the mapping relationship between the set of traffic characteristics and the SRv6 TE Policy can also be regarded as the mapping relationship between the set of first identifiers and the SRv6 TE Policy.

[0176] In practical applications, the third setting mapping relationship can be sent from the controller or the upper-level control node to the second network node. Based on this, in one embodiment, the method further includes: receiving the third setting mapping relationship sent from the controller or the upper-level control node.

[0177] In practical applications, the first message can be sent directly from the second network node to the first network node; that is, the first network node can receive the first message sent by the second network node.

[0178] The first message can also be forwarded from the second network node to the first network node by one or more third network nodes in the second domain after being sent by the second network node; where the third network node represents an intermediate network node in the second domain. In this case, before being forwarded by one or more third network nodes, the first message is sent directly from the second network node to the third network node that performs the initial forwarding. Then, after one or more forwardings by one or more third network nodes, the first network node receives the first message sent by the third network node that performs the final forwarding. This can also be understood as the first message being sent from the second network node to the first network node. It should be noted that the role of the third network node in this case is equivalent to transparent forwarding. Therefore, the corresponding message received by the first network node for the first message sent by the second network node can be understood as the first message. During the forwarding of the first message, the third network node may change the destination address field in the first message, but will not change the encapsulation field of the first identifier in the first message or the message forwarding path of the message.

[0179] In practical applications, after receiving the first message, the first network node can query the first identifier in the specified field of the first message header based on the Endpoint instruction, and then encapsulate the first message based on the first identifier to obtain the second message. The Endpoint instruction can specify the field that the first network node needs to query; this field is the specified field.

[0180] During the encapsulation of the second packet header, the first network node can, based on the second established mapping relationship, use the SRv6 TE Policy matching the first identifier as the first SRv6 TE Policy, and encapsulate the first packet with a new SRH based on the first SRv6 TE Policy, thereby achieving the encapsulation of the second packet header and obtaining the second packet. This SRH contains the Segment List corresponding to the first SRv6 TE Policy. The first SRv6 TE Policy can be used to describe the packet forwarding path of the second packet in the first domain. Here, the second packet header corresponds to the first SRv6 TE Policy; this can be understood as the Segment List in the SRH of the second packet header corresponding to the first SRv6 TE Policy. Network nodes in the first domain can forward the second packet based on the packet forwarding path indicated by the Segment List in the second packet. The packet forwarding path indicated by the Segment List in the second packet header is also the packet forwarding path in the first domain described by the first SRv6 TE Policy.

[0181] In practical applications, the second defined mapping relationship can be described as a traffic redirection strategy. This traffic redirection strategy can map the first identifier to the SRv6 TE Policy. The traffic redirection strategy can include one or more mapping strategies. For example, the mapping strategy can be represented as <Identifier 1 in DOH, SRv6 TE Policy 1> or <Class A, SRv6 TE Policy 1>. Class A can be a set of first identifiers of packets following the same first domain forwarding path, or a set of traffic characteristics of packets following the same first domain forwarding path. It can be understood that the first identifier and traffic characteristics have a first defined mapping relationship. Therefore, the mapping relationship between the set of traffic characteristics and the SRv6 TE Policy can also be regarded as the mapping relationship between the set of first identifiers and the SRv6 TE Policy.

[0182] In practical applications, the second mapping relationship can be set by the controller or the upper-level control node and sent to the first network node.

[0183] It should be noted that both the third and second mapping relationships can be regarded as traffic redirection strategies. In the embodiments of this application, the third mapping relationship can be regarded as a traffic redirection strategy for packets in the second domain, used to determine the forwarding path of packets in the second domain. The second mapping relationship can be regarded as a traffic redirection strategy for packets in the first domain, used to determine the forwarding path of packets in the first domain.

[0184] It can be seen that the first network node can encapsulate the first packet with a header corresponding to the first SRv6 TE Policy based on a first identifier that has a first predetermined mapping relationship with the traffic characteristics. This enables the encapsulated second packet to be forwarded in the first domain. In other words, the first network node provides traffic redirection services for the packet in the first domain based on the first identifier. Therefore, the second SRv6 TE Policy planned by the second network node does not need to involve the specific forwarding path of the packet in the first domain. It can still guarantee the forwarding of the packet in the first domain based on the encapsulation operation of the first network node. Thus, the second SRv6 TE Policy can also be regarded as describing the packet forwarding path in both the second and first domains.

[0185] In this embodiment, the head network node of the second domain, i.e., the second network node, encapsulates the first packet header into the third packet, obtains the first packet, and sends it. The first identifier is used by the first network node of the first domain to encapsulate the first packet with the packet header corresponding to the first SRv6 TE Policy after receiving the first packet, so that the encapsulated second packet can be forwarded in the first domain. That is, the first network node provides traffic redirection service for the packet based on the first identifier. Compared with related technologies, the head node of the main domain does not need to refer to the BSID configured in the edge node of the subdomain when planning the packet forwarding path. Even if the nodes in the subdomain change and the BSID changes, the head node of the main domain does not need to replan the packet forwarding path, thereby reducing the resource consumption of packet forwarding.

[0186] The first identifier will be further explained below.

[0187] In one embodiment, the first identifier includes one or more of the following:

[0188] The first information is used to identify the user corresponding to the first message;

[0189] The second information is used to identify the service corresponding to the first message;

[0190] The third information is used to identify the network element processing method corresponding to the first message.

[0191] In practical applications, the first information may include the user's identifier and name; the second information may include the type of service; and the third information may include the actions corresponding to the network element processing method.

[0192] In practical applications, the first established mapping relationship can be described as a traffic identifier mapping table. This traffic identifier mapping table can map traffic features to relevant information of the first identifier. The relevant information of the first identifier can be: the encapsulation field of the first identifier in the first message, that is, the encapsulation position. The traffic identifier mapping table can include one or more mapping pairs. For example, a mapping pair can be represented as <traffic feature 1, identifier 1 in DOH>. This mapping pair can be understood as: traffic feature 1 corresponds to identifier 1, and identifier 1 needs to be encapsulated in the DOH extension header field of the message. Here, identifier 1 is equivalent to the first identifier in the embodiments of this application.

[0193] In practical applications, the first predefined mapping relationship can be sent from the controller or upper-level control node to the second network node. The second network node can then generate a first message encapsulated with a first identifier based on this mapping relationship. Therefore,

[0194] In one embodiment, the method further includes: receiving a first set mapping relationship issued by the controller or an upper-level control node.

[0195] In practical applications, the first identifier is encapsulated in the configuration field of the first header of the first message.

[0196] In one embodiment, the field type corresponding to the set field includes one or more of the following: flow tag, field type of the field located in the HBH extension header, field type of the field located in the DOH extension header, and field type of the field located in the SRH.

[0197] Fields located in an SRH have a field type that includes one or more of the following: label, type length value (TLV).

[0198] In practical applications, both the HBH and DOH extension headers are equivalent to an IPv6 extension header. The IPv6 extension header is an optional structure in SRv6 packets, and SRv6 can include multiple IPv6 extension headers.

[0199] In practical applications, the field type corresponding to the field can also include: the field type of fields located in other IPv6 extension headers besides the HBH extension header and the DOH extension header.

[0200] For example, Figure 6 The SRv6 message structure in the related art is shown, and the field where the first identifier may be located in the first message following the message structure is circled.

[0201] For ease of understanding, the overall interaction flow of the solution provided in the embodiments of this application is described below based on an example. See also Figure 10 In this context, R1, R2, and R8 are nodes in domain 1, R2, R3, R4, R5, R6, and R7 are nodes in domain 2, R1 is the head node of domain 1, and domain 2 is a subdomain of domain 1. Here, domain 2 is equivalent to the first domain in this embodiment, domain 1 is equivalent to the second domain in this embodiment, R2 is equivalent to the first network node in this embodiment, and R1 is equivalent to the second network node in this embodiment.

[0202] The overall interaction process includes the following steps:

[0203] Step 1: The controller sends the identifier mapping table, traffic redirection strategy, and SRv6 TE Policy to R1.

[0204] In this example, the identifier mapping table includes: <Traffic Feature 1, Identifier 1 in DOH> and <Traffic Feature 2, Identifier 2 in DOH>; the traffic redirection strategy includes: <Class A, TE Policy P>, where both Traffic Feature 1 and Traffic Feature 2 belong to Class A; the SRv6 TE Policy includes TE Policy P, that is, Segment List [B->H].

[0205] In practical applications, the SRv6 TE Policy issued by the controller can be regarded as the determination of the packet forwarding path based on the R1 plan.

[0206] Step 2: The controller sends the traffic redirection strategy and SRv6 TE Policy to R2.

[0207] In this example, the referral strategy includes: <Identifier 1 in DOH, TE Policy P1> and <Identifier 2 in DOH, TE Policy P2>; SRv6 TE Policy includes: TE Policy P1 and TE Policy P2, where TE Policy P1 is Segment List [C->D->E->G->B9] and TE Policy P2 is Segment List [C->F->G->B9].

[0208] Step 3: R1 generates the first message and sends it.

[0209] In this example, R1 receives message 1 and determines that the traffic feature of message 1 matches <traffic feature 1, identifier 1 in DOH> in the identifier mapping table and the traffic redirection policy <class A, TE Policy P>. Then, R1 encapsulates message 1 with message header 1 to obtain message 2 and sends message 2. The Segment List in the SRH of message header 1 corresponds to TE Policy P, and message header 1 includes a DOH extension header, which encapsulates identifier 1. Here, message 1 is equivalent to the third message in this embodiment, message 2 is equivalent to the first message in this embodiment, and message header 1 is equivalent to the first message header in this embodiment.

[0210] Step 4: R2 encapsulates the first message into a second message and sends the second message.

[0211] In this example, the packet forwarding path described by TE Policy P is A->B->H. Therefore, the destination address of packet 2 when forwarded to R2 is B, which is a BDSID configured locally by R2. This BDSID corresponds to the instruction End.BD6.D. Based on this, R2 executes the instruction End.BD6.D. Specifically, R2 queries the identifier 1 in the DOH extension header of packet 2 and determines that identifier 1 matches the redirection policy <Identifier 1 in DOH, TE Policy P1>. Then, it encapsulates packet 2 with the packet header 2 corresponding to TE Policy P1 to obtain packet 3, and then forwards packet 3. Here, packet 3 is equivalent to the second packet in this embodiment, packet header 2 is equivalent to the second packet header in this embodiment, and the TE Policy for packet 3 in domain 2 is P1. In this example, the network nodes in domain 2 will forward packet 3 according to the packet forwarding path described by TE Policy P1, that is, according to the path B->C->D->E->G->B9.

[0212] Step 5: R2 decapsulates the second message and continues to forward the decapsulated message according to the message forwarding path described in TE Policy P.

[0213] In this example, message 3 reaches B9 after passing through the message forwarding path B->C->D->E->G->B9. That is, after being forwarded back to R2, the path of message 3 in domain 2 ends. R2 decapsulates message header 2 in message 3 to obtain the decapsulated message; then R2 forwards the decapsulated message based on the message forwarding path indicated by TE Policy P, that is, it sends it to R8, so that the message can travel through the remaining network nodes in domain 1; here, the decapsulated message can be regarded as the re-obtained message 2.

[0214] It should be noted that in this example, message 2 sent by R1 is encapsulated based on message 1, and message 3 sent by R2 is encapsulated based on message 2. The TE Policy of message 2 in domain 1 is P, and the TE Policy of message 3 in domain 2 is P1. This can also be understood as: the TE Policy of message 1 in domain 1 is P, and the TE Policy of message 1 in domain 2 is P1. The changes in message structure during the forwarding process of message 1 can be found in [reference needed]. Figure 11 .

[0215] Understandably, for a message received by R1 that hits <identifier 2in DOH, TE Policy P2>, such as message 4, the TE Policy of this message in domain 1 is P, which is the same as the TE Policy of message 1 in domain 1. The TE Policy used in domain 2 is P2, which is different from the TE Policy of message 1 in domain 2.

[0216] As can be seen, in this example, configuring only one TE Policy in R1 and only one BDSID in R2 is sufficient to address the TE Policy difference between packet 2 and packet 4 during forwarding. However, if the scenario in this example is implemented based on the BSID scheme in related technologies, R1 would need to plan two TE Policies, and R2 would also need to configure two BSIDs. Obviously, the scheme in related technologies consumes more resources. Therefore, the solution in this embodiment reduces the resource consumption for packet forwarding compared to related technologies.

[0217] Based on the embodiments described above, this application also provides a message processing apparatus applied to a first network node in a first domain, see [link to previous document]. Figure 12 The message processing device includes:

[0218] First receiving unit 1201: for receiving a first message; the first message header of the first message contains a first identifier encapsulated in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message;

[0219] First encapsulation unit 1202: used to query the set field of the first message header to obtain the first identifier, and encapsulate the first message based on the first identifier to obtain a second message; wherein, the second message encapsulates a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second message in the first field;

[0220] First sending unit 1203: used to send the second message.

[0221] In one embodiment, the first encapsulation unit 1202 queries the set field of the first message header to obtain the first identifier, and encapsulates the first message based on the first identifier to obtain a second message, including:

[0222] Execute the first instruction bound to the first identifier SID; where,

[0223] The first SID represents the destination address in the first packet header; the first instruction is used to instruct the first network node to perform the following operations: query the first identifier in the set field of the first packet header, and encapsulate the first packet based on the first identifier.

[0224] In one embodiment, the working mode of the encapsulated message corresponding to the first instruction includes either encaps mode or insert mode.

[0225] In one embodiment, if the first identifier is encapsulated in a field in the HBH extension header and / or a field in the DOH extension header, the first instruction encapsulates the message based on the insert mode.

[0226] In one embodiment, the field type corresponding to the set field includes one or more of the following: stream tag, field type of a field located in the HBH extension header, field type of a field located in the DOH extension header, and field type of a field located in the SRH.

[0227] The field types of the fields located in the SRH include one or more of the following: tag, TLV.

[0228] In one embodiment, the first identifier includes one or more of the following:

[0229] The first information is used to identify the user corresponding to the first message;

[0230] The second information is used to identify the service corresponding to the first message;

[0231] The third information is used to identify the network element processing method corresponding to the first message.

[0232] In one embodiment, the first receiving unit 1201 is further configured to receive a first message sent by a network node of the second domain.

[0233] In practical applications, the first receiving unit 1201, the first encapsulation unit 1202, and the first sending unit 1203 can all be implemented by the processor in the message processing device.

[0234] It should be noted that the message processing device provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the message processing device and message processing method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0235] Based on the embodiments described above, this application also provides a message processing apparatus applied to a second network node, wherein the second network node represents the head network node in a second domain, see [link to previous document]. Figure 13 The message processing device includes:

[0236] The second encapsulation unit 1301 is used to encapsulate a first message header into a third message to obtain a first message; the first message header contains a first identifier in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; the first identifier is used by the first network node of the first domain to encapsulate the first message after receiving the first message to obtain a second message; the second message contains a second message header corresponding to a first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TEPolicy of the second message in the first domain.

[0237] Second sending unit 1302: used to send the first message.

[0238] In one embodiment, the field type corresponding to the set field includes one or more of the following: flow tag, field type of a field located in the HBH extension header, field type of a field located in the DOH extension header, and field type of a field located in the SRH.

[0239] In one embodiment, the first identifier includes one or more of the following:

[0240] The first information is used to identify the user corresponding to the first message;

[0241] The second information is used to identify the service corresponding to the first message;

[0242] The third information is used to identify the network element processing method corresponding to the first message.

[0243] In one embodiment, the message processing device further includes a second receiving unit; the second receiving unit is used to receive the first set mapping relationship issued by the controller or the upper-layer control node.

[0244] In practical applications, the second encapsulation unit 1301, the second sending unit 1302, and the second receiving unit 1303 can all be implemented by the processor in the message processing device.

[0245] It should be noted that the message processing device provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the message processing device and message processing method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0246] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiments of this application, this application also provides an electronic device, see [link to relevant documentation]. Figure 14 The electronic device includes:

[0247] The first communication interface 1401 is capable of exchanging information with other devices;

[0248] The first processor 1402 is connected to the first communication interface 1401 to enable information interaction with other devices and to execute the methods provided by one or more technical solutions in the above embodiments when running a computer program. The computer program is stored in the first memory 1403.

[0249] Specifically, the first communication interface 1401 is used to receive a first message; the first message header of the first message encapsulates a first identifier in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; and to send a second message.

[0250] The first processor 1402 is configured to query the set field of the first message header to obtain the first identifier, and encapsulate the first message based on the first identifier to obtain a second message; wherein the second message encapsulates a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second message in the first field.

[0251] In one embodiment, the first processor 1402 queries the defined field of the first message header to obtain the first identifier, and encapsulates the first message based on the first identifier to obtain a second message, including:

[0252] Execute the first instruction bound to the first identifier SID; where,

[0253] The first SID represents the destination address in the first packet header; the first instruction is used to instruct the first network node to perform the following operations: query the first identifier in the set field of the first packet header, and encapsulate the first packet based on the first identifier.

[0254] In one embodiment, the working mode of the encapsulated message corresponding to the first instruction includes either encaps mode or insert mode.

[0255] In one embodiment, if the first identifier is encapsulated in a field in the HBH extension header and / or a field in the DOH extension header, the first instruction encapsulates the message based on the insert mode.

[0256] In one embodiment, the field type corresponding to the set field includes one or more of the following: stream tag, field type of a field located in the HBH extension header, field type of a field located in the DOH extension header, and field type of a field located in the SRH.

[0257] The field types of the fields located in the SRH include one or more of the following: tag, TLV.

[0258] In one embodiment, the first identifier includes one or more of the following:

[0259] The first information is used to identify the user corresponding to the first message;

[0260] The second information is used to identify the service corresponding to the first message;

[0261] The third information is used to identify the network element processing method corresponding to the first message.

[0262] In one embodiment, the first communication interface 1401 is further configured to receive the second set mapping relationship issued by the controller or the upper-level control node.

[0263] Of course, in practical applications, the various components in an electronic device are coupled together through the bus system 1404. It can be understood that the bus system 1404 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1404 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, in... Figure 14 The general designated all buses as Bus System 1404.

[0264] The first memory 1403 in this embodiment is used to store various types of data to support operation in the electronic device. Examples of such data include any computer program used to operate on the electronic device.

[0265] The methods disclosed in the above embodiments of this application can be applied to the first processor 1402, or implemented by the first processor 1402. The first processor 1402 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 1402. The first processor 1402 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 1402 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 1403. The first processor 1402 reads the information in the first memory 1403 and completes the steps of the aforementioned method in combination with its hardware.

[0266] In an exemplary embodiment, the electronic device may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0267] It is understood that the first memory 1403 in this embodiment can be volatile memory or non-volatile memory, or both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); the magnetic surface memory can be disk storage or magnetic tape storage. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0268] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiments of this application, this application also provides an electronic device, see [link to relevant documentation]. Figure 15 The electronic device includes:

[0269] The second communication interface 1501 is capable of exchanging information with other devices;

[0270] The second processor 1502 is connected to the second communication interface 1501 to enable information interaction with other devices. When running a computer program, it executes the methods provided by one or more technical solutions in the above embodiments. The computer program is stored in the second memory 1503.

[0271] Specifically, the second processor 1502 is used to encapsulate a first header into a third message to obtain a first message; the first header contains a first identifier in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; the first identifier is used by the first network node of the first domain to encapsulate the first message after receiving it to obtain a second message; the second message contains a second header corresponding to a first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second message in the first domain;

[0272] The second communication interface 1501 is used to send the first message.

[0273] In one embodiment, the field type corresponding to the set field includes one or more of the following: flow tag, field type of a field located in the HBH extension header, field type of a field located in the DOH extension header, and field type of a field located in the SRH.

[0274] In one embodiment, the first identifier includes one or more of the following:

[0275] The first information is used to identify the user corresponding to the first message;

[0276] The second information is used to identify the service corresponding to the first message;

[0277] The third information is used to identify the network element processing method corresponding to the first message.

[0278] In one embodiment, the second communication interface 1501 is also used to receive the first set mapping relationship issued by the controller or the upper-level control node.

[0279] Of course, in practical applications, the various components in an electronic device are coupled together through a bus system 1504. It can be understood that the bus system 1504 is used to achieve communication between these components. In addition to a data bus, the bus system 1504 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 15 The general labeled all buses as Bus System 1504.

[0280] The second memory 1503 in this embodiment is used to store various types of data to support operation in the electronic device. Examples of such data include any computer program used to operate on the electronic device.

[0281] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the second processor 1502. The second processor 1502 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the form of software within the second processor 1502. The second processor 1502 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 1502 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a second memory 1503. The second processor 1502 reads information from the second memory 1503 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0282] In an exemplary embodiment, the electronic device may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0283] It is understood that the second memory 1503 in this application embodiment can be volatile memory or non-volatile memory, or both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); the magnetic surface memory can be disk storage or magnetic tape storage. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0284] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a first memory 1403 storing a computer program, which can be executed by a first processor 1402 of an electronic device to complete the steps described in the aforementioned first network node-side method. Alternatively, it may include a second memory 1503 storing a computer program, which can be executed by a second processor 1502 of an electronic device to complete the steps described in the aforementioned second network node-side method.

[0285] In an exemplary embodiment, this application also provides a computer program product, including a computer program executable by a first processor 1402 of an electronic device to perform the steps described in the aforementioned first network node-side method. Alternatively, it may include a second memory 1503 storing the computer program, which can be executed by a second processor 1502 of an electronic device to perform the steps described in the aforementioned second network node-side method.

[0286] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0287] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0288] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0289] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A message processing method, characterized in that, The method, applied to a first network node in a first domain, includes: Receive a first message; the first message header of the first message contains a first identifier encapsulated in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; The first identifier is obtained by querying the defined field of the first packet header, and the first packet is encapsulated based on the first identifier to obtain the second packet; wherein, the second packet encapsulates a second packet header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second defined mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TEPolicy of the second packet in the first field; the field type corresponding to the defined field includes one or more of the following: flow label, field type of field located in HBH extension header, field type of field located in DOH extension header, field type of field located in Segment Routing Header SRH; the field type of field located in SRH includes one or more of the following: label, type length value (TLV); Send the second message.

2. The method according to claim 1, characterized in that, The process of querying the defined fields in the first message header to obtain the first identifier, and encapsulating the first message based on the first identifier to obtain the second message, includes: Execute the first instruction bound to the first identifier SID; where, The first SID represents the destination address in the first packet header; the first instruction is used to instruct the first network node to perform the following operations: query the first identifier in the set field of the first packet header, and encapsulate the first packet based on the first identifier.

3. The method according to claim 2, characterized in that, The working modes of the encapsulated message corresponding to the first instruction include: encaps mode or insert mode.

4. The method according to claim 3, characterized in that, When the first identifier is encapsulated in a field in the hop-by-hop HBH extension header and / or a field in the Destination Options DOH extension header, the first instruction encapsulates the message based on the insert mode.

5. The method according to claim 1, characterized in that, The first identifier includes one or more of the following: The first information is used to identify the user corresponding to the first message; The second information is used to identify the service corresponding to the first message; The third information is used to identify the network element processing method corresponding to the first message.

6. The method according to claim 1, characterized in that, The method further includes: Receive the second set mapping relationship sent by the controller or upper-level control node.

7. The method according to claim 1, characterized in that, Receiving the first message includes: Receive the first message sent by the network node of the second domain.

8. A message processing method, characterized in that, Applied to a second network node, the second network node representing the head network node in a second domain; the method includes: A first message header is encapsulated in a third message to obtain a first message; a first identifier is encapsulated in a setting field of the first message header; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; the first identifier is used by a first network node in a first domain to encapsulate the first message after receiving it to obtain a second message; the second message encapsulates a second message header corresponding to a first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second message in the first domain; the field type corresponding to the setting field includes one or more of the following: flow label, field type of a field located in the HBH extension header, field type of a field located in the DOH extension header, and field type of a field located in the SRH; the field type of a field located in the SRH includes one or more of the following: label, type length value (TLV); Send the first message.

9. The method according to claim 8, characterized in that, The first identifier includes one or more of the following: The first information is used to identify the user corresponding to the first message; The second information is used to identify the service corresponding to the first message; The third information is used to identify the network element processing method corresponding to the first message.

10. The method according to claim 8, characterized in that, The method further includes: Receive the first set mapping relationship sent by the controller or upper-level control node.

11. A message processing apparatus, characterized in that, The first network node applied in the first domain includes: The first receiving unit is used to receive the first message; the first message header of the first message contains a first identifier encapsulated in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; The first encapsulation unit is configured to query the defined field of the first packet header to obtain the first identifier, and encapsulate the first packet based on the first identifier to obtain a second packet; wherein the second packet encapsulates a second packet header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second defined mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second packet in the first field; the field type corresponding to the defined field includes one or more of the following: flow label, field type of a field located in the HBH extension header, field type of a field located in the DOH extension header, and field type of a field located in the Segment Routing Header (SRH); the field type of the field located in the SRH includes one or more of the following: label, type length value (TLV); The first sending unit is used to send the second message.

12. A message processing apparatus, characterized in that, Applied to a second network node, which represents the head network node in the second domain, including: The second encapsulation unit is used to encapsulate the first packet header into the third packet to obtain the first packet. The first packet header contains a first identifier encapsulated in a setting field. The first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first packet. The first identifier is used by the first network node in the first domain to encapsulate the first packet after receiving it, to obtain the second packet. The second packet contains a second packet header corresponding to a first SRv6 TE Policy. The first SRv6 TE Policy represents an SRv6 TEPolicy that has a second set mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TEPolicy of the second packet in the first domain. The field type corresponding to the setting field includes one or more of the following: flow label, field type of a field located in the HBH extension header, field type of a field located in the DOH extension header, and field type of a field located in the SRH. The field type of the field located in the SRH includes one or more of the following: label, type length value (TLV). The second sending unit is used to send the first message.

13. An electronic device, characterized in that, include: A first processor and a first communication interface; wherein... The first communication interface is used to receive a first message; the first message header of the first message contains a first identifier encapsulated in a setting field; the first identifier represents an identifier that has a first set mapping relationship with the traffic characteristics of the first message; and to send a second message. The first processor is configured to query the defined field of the first packet header to obtain the first identifier, and encapsulate the first packet based on the first identifier to obtain a second packet; wherein the second packet encapsulates a second packet header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy that has a second defined mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TE Policy of the second packet in the first field; the field type corresponding to the defined field includes one or more of the following: flow label, field type of a field located in the HBH extension header, field type of a field located in the DOH extension header, and field type of a field located in the Segment Routing Header (SRH); the field type of the field located in the SRH includes one or more of the following: label, type length value (TLV).

14. An electronic device, characterized in that, include: A second processor and a second communication interface; wherein... The second processor is configured to encapsulate a first header into a third packet to obtain a first packet. A first identifier is encapsulated in a setting field of the first header. The first identifier represents an identifier that has a first predetermined mapping relationship with the traffic characteristics of the first packet. The first identifier is used by a first network node in the first domain to encapsulate the first packet after receiving it, resulting in a second packet. The second packet encapsulates a second header corresponding to a first SRv6 TE Policy. The first SRv6 TE Policy represents an SRv6 TEPolicy that has a second predetermined mapping relationship with the first identifier, and the first SRv6 TE Policy is used to describe the SRv6 TEPolicy of the second packet in the first domain. The field type corresponding to the setting field includes one or more of the following: flow label, field type of a field located in the HBH extension header, field type of a field located in the DOH extension header, and field type of a field located in the SRH. The field type of the field located in the SRH includes one or more of the following: label, type length value (TLV). The second communication interface is used to send the first message.

15. An electronic device, characterized in that, include: A first processor and a first memory for storing computer programs capable of running on the processor. Wherein, when the first processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 7.

16. An electronic device, characterized in that, include: A second processor and a second memory for storing computer programs that can run on the processor. Wherein, when the second processor is used to run the computer program, it performs the steps of the method according to any one of claims 8 to 10.

17. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7, or the steps of the method according to any one of claims 8 to 10.

18. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7, or the steps of the method according to any one of claims 8 to 10.

Images