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

Abstract

The invention discloses a message processing method and device, electronic equipment, a storage medium and a computer program product, and the method comprises the steps: a first network node in a first domain receives a first message; a first identifier is packaged 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 the traffic characteristic of the first message; querying the set field of the first message header to obtain the first identifier, and packaging the first message based on the first identifier to obtain a second message; wherein a second message header corresponding to a first SRv6TE Policy is packaged in the second message, the first SRv6TE Policy represents the SRv6TE Policy which has a second set mapping relation with the first identifier, and the first SRv6TE Policy is used for describing the SRv6TE Policy of the second message in the first domain; and sending the second message.

Description

Technical Field

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

[0002] In the related art, when a message forwarding path involves multiple domains, a change in a node in any sub-domain may cause the head node of the main domain to re-plan the path, increasing resource consumption of message forwarding. Summary of the invention

[0003] To solve related technical problems, the embodiments of the present application provide a message processing method, device, electronic device, storage medium and computer program product.

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

[0005] The embodiment of the present application provides a message processing method, which is applied to a first network node in a first domain, and the method includes:

[0006] receiving a first message; a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic feature of the first message;

[0007] querying the setting field of the first message header to obtain the first identifier, and encapsulating the first message based on the first identifier to obtain a second message; wherein the second message is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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;

[0008] The second message is sent.

[0009] In the above solution, querying the setting 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 a first instruction bound to a first segment identifier (SID); wherein,

[0011] The first SID represents a destination address in the first message 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 message header, and encapsulate the first message 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 a hop-by-hop (HBH) extension header and / or a field in a destination options (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: a flow label, a field type of a field located in an HBH extension header, a field type of a field located in a DOH extension header, and a field type of a field located in a segment routing header (SRH, Segment Routing Header);

[0015] The field type of the field in the SRH includes one or more of the following: tag, type-length-value (TLV, Type-Length-Value).

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

[0017] first information, where the first information is used to identify a user corresponding to the first message;

[0018] second information, where 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] In the above scheme, the method further comprises:

[0021] The second setting mapping relationship sent by the receiving controller or the upper control node is received.

[0022] The embodiment of the present application further provides a message processing method, which is applied to a second network node, where the second network node represents a head network node in a second domain; the method includes:

[0023] A first message header is encapsulated for 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 having a first setting mapping relationship with a traffic feature of the first message; the first identifier is used for a first network node in a first domain to encapsulate the first message after receiving the first message to obtain a second message; a second message header corresponding to a first SRv6 TE Policy is encapsulated in the second message, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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] The first message is sent.

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

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

[0027] first information, where the first information is used to identify a user corresponding to the first message;

[0028] second information, where 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] In the above scheme, the method further comprises:

[0031] The first setting mapping relationship sent by the controller or the upper control node is received.

[0032] The embodiment of the present application further provides a message processing device, which is applied to a first network node in a first domain, including:

[0033] A first receiving unit, configured to receive a first message; a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic feature of the first message;

[0034] a first encapsulation unit, configured to query the setting 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 is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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;

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

[0036] The embodiment of the present application further provides a message processing device, which is applied to a second network node, where the second network node represents a head network node in a second domain, including:

[0037] a second encapsulation unit, configured to encapsulate a first message header for 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 having a first setting mapping relationship with a traffic feature of the first message; the first identifier is used for a first network node in a first domain to encapsulate the first message after receiving the first message to obtain a second message; a second message header corresponding to a first SRv6 TE Policy is encapsulated in the second message, the first SRv6 TE Policy represents an SRv6 TEPolicy having a second setting 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;

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

[0039] The embodiment of the present application also provides an electronic device, comprising: a first processor and a first communication interface; wherein,

[0040] The first communication interface is used to receive a first message; a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic feature of the first message; and, send a second message;

[0041] The first processor is configured to query the setting 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 is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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.

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

[0043] The second processor is used to encapsulate the first message header for the third message to obtain the first message; the setting field of the first message header is encapsulated with a first identifier; the first identifier represents an identifier having a first setting mapping relationship with the traffic characteristics of the first message; the first identifier is used for 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 is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents the SRv6 TE Policy having a second setting 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] An embodiment of the present application further provides an electronic device, comprising: a first processor and a first memory for storing a computer program that can be run on the processor,

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

[0047] The embodiment of the present application further provides an electronic device, comprising: a second processor and a second memory for storing a computer program that can be run on the processor,

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

[0049] An embodiment of the present application further provides a storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program 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] An embodiment of the present application further provides a computer program product, including a computer program, 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.

[0051] Based on this, in an embodiment of the present application, a first network node in a first domain receives a first message; wherein a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic characteristic of the first message; then, the first network node queries the setting field of the first message header, obtains the first identifier, and encapsulates the first message based on the first identifier to obtain a second message; wherein a second message header corresponding to the first SRv6 TEPolicy is encapsulated in the second message, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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; thereafter, the first network node sends a second message. In the above scheme, the first network node in the first domain encapsulates the first message with a message header corresponding to the first SRv6 TE Policy based on the first identifier having a first set mapping relationship with the traffic characteristics, so that the second message obtained after encapsulation can be forwarded in the first domain, that is, the first network node provides a traffic diversion service for the message based on the first identifier. Compared with the related technology, when the head node of the main domain plans the message forwarding path, even if the nodes in the subdomain change, the head node of the main domain does not need to re-plan the message forwarding path, thereby reducing the resource consumption of message forwarding. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0053] Figure 2 It is a schematic diagram of message processing in the related technology;

[0054] Figure 3 It is another message processing schematic diagram in the related technology;

[0055] Figure 4 It is a schematic diagram of the third message processing in the related technology;

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

[0057] Figure 6 A schematic diagram of a packaging position provided in an embodiment of the present application;

[0058] Figure 7 A schematic diagram of a packaging method provided in an embodiment of the present application;

[0059] Figure 8 A schematic diagram of another packaging method provided in an embodiment of the present application;

[0060] Fig. 9 A schematic diagram of the implementation flow of another message processing method provided in an embodiment of the present application;

[0061] Fig.10 A schematic diagram of the overall process of a message processing method provided in an embodiment of the present application;

[0062] Fig.11 A schematic diagram of a message structure change provided in an embodiment of the present application;

[0063] Fig.12 A schematic diagram of the structure of a message processing device provided in an embodiment of the present application;

[0064] Fig.13 A schematic diagram of the structure of another message processing device provided in an embodiment of the present application;

[0065] Fig.14 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;

[0066] Fig.15 A schematic diagram of the structure of the hardware composition of another electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0067] For ease of understanding, the main concepts involved in this application are first explained:

[0068] Service Function Chain (SFC): A technology that provides ordered services for the network. SFC connects the nodes that provide services in the network at the logical level to form an ordered service combination.

[0069] Specifically, the traffic can be directed to pass through the specified nodes in order by encapsulating the SFC path in the message. 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: With the continuous evolution of the network, the network scale has become super-large, making the management of service chains more complex and challenging. To solve this problem, the relevant technology divides the network into multiple independent domains. Each domain in the network builds its own service chain based on the nodes in the domain. These service chains can be expressed 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 run through the entire network and can be expressed as an upper-level chain or main chain; the domain where the nodes in the upper-level chain are located can be regarded as the main domain, and the domain where the nodes in the lower-level chain are located can be regarded as the sub-domain. The upper-level chain contains the edge nodes of the sub-domain corresponding to the lower-level chain. In this way, the upper-level chain can connect the lower-level chains located in different sub-domains in series, realizing a hierarchical service chain, thereby providing a complete end-to-end service chain service.

[0071] For example, see Figure 1 , R1, R2 and R5 can be regarded as nodes in domain 1, R1, R2 and R5 form a service chain 1, R2, R3 and R4 can be regarded as nodes in domain 2, R2, R3 and R4 form a service chain 2, where R2 is the edge node of domain 2, R2 is also the intermediate node of domain 1, service chain 2 can be regarded as a subchain of service chain 1, and domain 2 can be regarded as a subdomain of domain 1. After receiving the message sent by R1, R2 can send the message to the node in domain 2, such as R3, or send the message to the node in other domains.

[0072] SRv6: A protocol designed based on source routing mechanism to forward SRv6 packets on the network.

[0073] In practical applications, messages transmitted based on the SRv6 protocol can be expressed as SRv6 messages. The nodes on 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 on the message transmission path can be arranged into an ordered list, i.e., a segment list, and the segment list is pushed into the SRH of the message header in the form of an IPv6 address stack, so that the SRv6 message is forwarded in the network along the path indicated by the SRH; the SRH can also be expressed as an SRH extension header.

[0074] In actual applications, SRv6 has two main working modes: SRv6 BE (Best Effort) and SRv6 TE (Traffic Engineering) Policy. Among them, SRv6 BE does not restrict the path for packet forwarding, only uses one SID to specify the destination address, and forwards SRv6 packets to the destination address based on the shortest path algorithm. It is a best-effort working mode; SRv6 TE Policy requires SRH to specify the path to be followed during packet forwarding, thereby providing end-to-end service from source to destination.

[0075] In practical applications, SRv6 TE Policy can also be understood as a specific forwarding strategy, or TEPolicy. An SRv6 TE Policy can be used to describe a message forwarding path based on the SRv6 TE Policy working mode indication. The upper-layer control node or controller can configure an SRv6 TE Policy for the head node based on the message forwarding path planned by the head node of the primary domain. This can also be described as the head node of the primary domain can plan an SRv6 TE Policy. Among them, an SRv6 TE Policy corresponds to the Segment List in the SRv6 message.

[0076] For example, see Figure 2, R1, R2, and R5 are nodes in domain 1, R2, R3, and R4 are nodes in domain 2, R1 is the head node of domain 1, domain 2 is the subdomain of domain 1, R1 is configured with TE Policy 1, and the Segment List corresponding to TE Policy 1 is [B->C->D->B->E], which can also be expressed as (E, B, D, C, B). Here, the message 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. Among them, 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 instruction: used to indicate the action that the node needs to perform when processing a SID. Each SID is bound to an Endpoint instruction. The SID processed by the node can be specified by the SRH or destination address in the received message, thereby providing forwarding, encapsulation, and decapsulation for the message.

[0078] Exemplarily, the Endpoint instruction End can be used to instruct the node to perform the following actions on the message: subtract 1 from the Segment Left value in the SRH of the message, and update the SID indexed by the Segment Left value in the Segment List to the destination address of the message, and then forward the message based on the updated destination address.

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

[0080] In actual applications, when the message forwarding path involves multiple domains, the head node of the main domain can plan the path in advance. However, any change in the node of any subdomain may cause the head node to re-plan the path. For example, see Figure 2The packet forwarding path represented by TE Policy 1 planned by R1 is A->B->C->D->B->E. If the node in domain 2 changes, for example, R4 in domain 2 is deleted, then R1 needs to re-plan the path. For example, the packet forwarding path represented by TE Policy 1 after re-planning is A->B->C->B->E.

[0081] In the related art, messages are forwarded based on a binding segment identifier (BSID, Binding SID), thereby isolating different domains to a certain extent and preventing changes within a domain from extending outside the domain. It should be noted that a BSID can be regarded as a type of SID.

[0082] Specifically, each BSID is used to identify an SRv6 TE Policy, that is, each BSID corresponds to an SRv6 TEPolicy, and it can also be considered that each BSID corresponds to a message forwarding path. The Endpoint instruction bound to the BSID is End.B6 (Endpoint bound to an SRv6 Policy), and the action corresponding to this instruction is: reset the SRH for the message and update the destination address. The Segment List in the reset SRH corresponds to the SRv6 TE Policy corresponding to the BSID. In actual applications, one or more SRv6 TE Policies can be configured for the edge nodes of each domain by configuring one or more BSIDs, thereby indicating the forwarding path of the message within the domain.

[0083] For example, see Figure 3 , R1, R2 and R5 are nodes in domain 1, R2, R3 and R4 are nodes in domain 2, R1 is the head node of domain 1, domain 2 is the subdomain of domain 1, and R2 is configured with "End.B6SID=B". Here, B corresponds to TE Policy2, and the Segment List corresponding to TEPolicy2 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 message encapsulated by R1 based on TE Policy1 is B. After receiving the message with the destination address of B, R2 provides a traffic diversion service for the message based on BSID B. Specifically, R2 resets the SRH for the message and updates the destination address 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] It can be seen that in this example, a long packet forwarding path is split into two small segments through BSID B. That is, the packet forwarding path A->B9->C->D->E involving domains 1 and 2 is split into: forwarding path A->B9->E in domain 1 and forwarding path B9->C->D in domain 2. The TE Policy 2 corresponding to B9->C->D is identified by BSID B indicated in TE Policy 1.

[0085] It can be understood that R2 provides traffic diversion services for packets based on BSID. Therefore, when planning TE Policy 1, R1 only needs to refer to the BSID configured in R2, and does not need to care about the TE Policy 2 content corresponding to the BSID. Even if the nodes in domain 2 change, R1 can still indicate the original BSID in the planned TE Policy 1, and then the upper-layer control node or controller updates the TE Policy 2 corresponding to the BSID, thereby updating the forwarding path.

[0086] For example, see Figure 3 , when 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 TE Policy2 configured by R2. The Segment List corresponding to the updated TEPolicy2 can be [C->B9]. In this case, R1 will still send the message to R2. After receiving the message with the destination address as B, R2 resets the SRH for the message 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). In this way, the message forwarding path is updated to A->B9->C->E.

[0087] It can be seen that in the scheme of forwarding message paths based on BSID, the head node of the main domain does not need to re-plan the path for each node change in the sub-domain, that is, to a certain extent, the isolation between domains is achieved. However, this isolation is not thorough. In actual applications, if the nodes in the sub-domain change and the number of forwarding paths in the domain changes, the number of BSIDs configured for the edge nodes of the domain also needs to be increased or decreased accordingly, which causes the head node of the main domain to re-plan the path based on the newly added or deleted BSID.

[0088] For example, see Figure 4, 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, 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 TEPolicy4; R1 needs to plan two SRv6 TE Policies based on the two BSIDs configured by R2 to correspond to the two message forwarding paths in domain 2. Here, the SRv6 TE Policies planned by R1 are TE Policy1 and TE Policy2; and if the nodes in domain 2 change, resulting in the addition or deletion of a message forwarding path in domain 2, the SRv6 TE Policy planned by R1 also needs to be adjusted accordingly.

[0089] It can be seen that in the related art, any change in the node of any sub-domain may cause the head node of the main domain to re-plan the path, increasing the resource consumption of message forwarding.

[0090] Based on this, in an embodiment of the present application, a first network node in a first domain receives a first message; wherein a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic characteristic of the first message; then, the first network node queries the setting field of the first message header, obtains the first identifier, and encapsulates the first message based on the first identifier to obtain a second message; wherein a second message header corresponding to the first SRv6 TEPolicy is encapsulated in the second message, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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; thereafter, the first network node sends a second message. In the above scheme, the first network node of the first domain encapsulates the first message with a message header corresponding to the first SRv6 TE Policy based on the first identifier having a first set mapping relationship with the traffic characteristics, so that the second message obtained after encapsulation can be forwarded in the first domain, that is, the first network node provides a traffic diversion service for the message based on the first identifier. Compared with the related technology, 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 message forwarding path. Even if the node in the subdomain changes, resulting in a change in the BSID, the head node of the main domain does not need to re-plan the message forwarding path, thereby reducing the resource consumption of message forwarding.

[0091] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0092] An embodiment of the present application provides a message processing method, which is applied to a first network node in a first domain.

[0093] In practical applications, the first network node can be regarded as a head node in the first domain, that is, an edge node. A network node can be understood as a network device used to provide services in a network, and can also be expressed as a network element or a node.

[0094] See also Figure 5 , the method comprising:

[0095] Step 501: Receive a first message.

[0096] Among them, a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic feature of the first message.

[0097] In actual applications, the first message may be an SRv6 message.

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

[0099] A first message sent by a network node in the second domain is received.

[0100] In actual applications, when the second domain is understood as a main domain, the first domain can be understood as a subdomain of the second domain. The first domain and the second domain can be connected through the first network node.

[0101] In actual 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; wherein the second network node represents the head network node in the second domain.

[0102] The first message may 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; wherein 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 directly sent by the second network node to the third network node that performs the first forwarding, and then, after one or more third network nodes forward it once or multiple times, the first network node receives the first message sent by the third network node that performs the last forwarding; this case may also be understood as the first message being sent by 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, and therefore, corresponding to the first message received by the first network node, the corresponding message sent by the second network node may be understood as the first message.

[0103] In actual applications, the third network node may change the destination address field in the first message during the process of forwarding the first message, but will not change the encapsulation field of the first identifier in the first message and the message forwarding path of the message.

[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 may include information such as the user, service, and network element processing method corresponding to the first message, and may also include triples, quintuples, and other features. The user corresponding to the first message may be a tenant requesting a service, and the service request initiated by the tenant is transmitted in the network in the form of a message; the service corresponding to the first message may be: the service requested by the tenant, which may be, for example, cloud storage, video phone, and other services; the network element processing method corresponding to the first message may be used to indicate the network node's processing method for the first message, such as a path forwarding method.

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

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

[0108] Second information, where 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 actual applications, the first information may include information such as the user's identification and name; the second information may include information such as the type of service; and the third information may include information such as actions corresponding to the network element processing method.

[0111] In practical applications, the first set mapping relationship can be expressed as a traffic identifier mapping table, which can map traffic characteristics with 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 may include one or more mapping pairs. Exemplarily, the mapping pair can be illustrated as <traffic characteristic 1, identifier 1 in DOH>. The mapping pair can be understood as: traffic characteristic 1 corresponds to identifier 1, and identifier 1 needs to be encapsulated in the DOH extended header field of the message. Here, identifier 1 is equivalent to the first identifier in the embodiment of the present application.

[0112] In practical applications, the first set mapping relationship may be sent by the controller or the upper control node to the second network node, and the second network node may generate a first message encapsulating the first identifier based on the first set mapping relationship.

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

[0114] In one embodiment, the field type corresponding to the setting field includes one or more of the following: a flow label, a field type of a field located in an HBH extension header, a field type of a field located in a DOH extension header, and a field type of a field located in an SRH;

[0115] The field type of the fields in the SRH includes one or more of the following: tag, type-length-value TLV.

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

[0117] In actual applications, the field type corresponding to the setting field may also include: the field type of the field in other IPv6 extension headers except 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 setting 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.

[0120] The second message is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6TEPolicy represents the SRv6 TE Policy having 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.

[0121] In actual applications, the first network node can query the first identifier in the setting field of the first message header of the first message based on the Endpoint instruction, and encapsulate the first message based on the first identifier to obtain the second message. The Endpoint instruction can indicate that there is a field that the first network node needs to query, which is also the setting field.

[0122] In actual applications, in the process of encapsulating the second message header, the first network node can use the SRv6 TE Policy that matches the first identifier as the first SRv6 TE Policy based on the second set mapping relationship, and encapsulate a new SRH for the first message based on the first SRv6 TEPolicy, thereby implementing the encapsulation of the second message header to obtain the second message; the SRH includes the Segment List corresponding to the first SRv6 TE Policy.

[0123] In actual applications, the second set mapping relationship can be expressed as a diversion strategy, which can map the first identifier with the SRv6 TE Policy. The diversion strategy can include one or more mapping strategies. For example, the mapping strategy can be illustrated as <identifier 1in DOH, SRv6 TE Policy1>, or <class A, SRv6 TE Policy1>, where class A can be a collection of first identifiers of messages that follow the same message forwarding path of the first domain, or a collection of traffic characteristics of messages that follow the same message forwarding path of the first domain. It can be understood that the first identifier and the traffic characteristic have a first set mapping relationship. Therefore, the mapping relationship between the collection of traffic characteristics and the SRv6 TE Policy can also be regarded as: the mapping relationship between the collection of first identifiers and the SRv6 TE Policy.

[0124] In practical applications, the second set mapping relationship may be sent from the controller or the upper control node to the first network node.

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

[0126] A second setting mapping relationship sent by a receiving controller or an upper control node is received.

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

[0128] In actual applications, the network nodes in the first domain can forward the second message based on the message forwarding path indicated by the Segment List in the second message. The message forwarding path indicated by the Segment List in the second message header is also the message 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 message header corresponding to the first SRv6 TE Policy for the first message based on the first identifier having a first set mapping relationship with the traffic characteristics, so that the second message obtained after encapsulation can be forwarded in the first domain, that is, the first network node provides the message with a traffic diversion service in the first domain based on the first identifier.

[0130] In actual applications, the second network node can plan an SRv6 TE Policy for the received message in the second domain. Here, the SRv6 TE Policy planned by the second network node can be expressed as a second SRv6 TE Policy. Then, the second network node encapsulates the received message with a message header corresponding to the second SRv6 TE Policy, and then obtains the encapsulated message and sends it out. 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] According to the embodiment of the present application, after the first network node receives the first message, it can provide the message with a traffic diversion service in the first domain according to the first identifier. It can be seen that the second SRv6 TEPolicy planned by the second network node does not need to involve the specific forwarding path of the message in the first domain, and can also ensure the forwarding of the message in the first domain based on the encapsulation operation of the first network node. Therefore, the second SRv6 TE Policy can also be regarded as describing the message forwarding path in the second domain and the first domain. It can be understood that in this way, even if the nodes in the first domain change, the head node of the second domain does not need to re-plan the message forwarding path, which is equivalent to eliminating the influence of the first domain on the second domain, isolating the first domain and the second domain, and reducing resource consumption in the message forwarding process.

[0132] Step 503: Send a second message.

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

[0134] In an embodiment of the present application, a first network node in a first domain encapsulates a message header corresponding to a first SRv6 TE Policy for a first message based on a first identifier having a first set mapping relationship with a traffic feature, so that a second message obtained after encapsulation can be forwarded in the first domain, that is, the first network node provides a traffic diversion service for the message based on the first identifier. Compared with the related art, when planning a message 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 node in the subdomain changes, resulting in a change in the BSID, the head node of the main domain does not need to re-plan the message forwarding path, thereby reducing resource consumption for message forwarding.

[0135] The following describes in detail the method of querying the setting field and encapsulating the first message.

[0136] In one embodiment, querying a setting field of a first message header to obtain a first identifier, and encapsulating the first message based on the first identifier to obtain a second message includes:

[0137] A first instruction bound to the first SID is executed.

[0138] The first SID represents the destination address in the first message 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 message header, and encapsulate the first message based on the first identifier.

[0139] In practical applications, a new type of Endpoint instruction can be defined, which can be regarded as an Endpoint instruction for dynamically binding an SRv6 TE Policy, equivalent to the first instruction in the embodiment of the present application. Exemplarily, this type of instruction can be expressed as End.BD6 (Endpoint Dynamically Bound to an SRv6 TE Policy).

[0140] Exemplarily, 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 an encapsulation field of a first identifier.

[0141] Exemplarily, Table 1 lists the full names of multiple End.BD6 instructions and the corresponding instruction actions.

[0142] Table 1

[0143]

[0144]

[0145] In actual applications, each End.BD6 instruction can be bound to a SID, which can be expressed as BDSID, which is equivalent to the first SID in the embodiment of the present application.

[0146] In actual applications, the BDSID can be configured in the first network node; the second network node in the second domain can indicate the BDSID in the SRv6 TE Policy of the second domain planned for the first message, so that the destination address of the first message received by the first network node is the BDSID. After receiving the first message, the first network node executes the End.BD6 instruction bound to the BDSID, thereby querying the first identifier in the setting field in the first message header, and encapsulating the first message based on the first identifier to obtain the second message. Here, the End.BD6 instruction bound to the BDSID indicates the setting field, and the second message is encapsulated with the second message header corresponding to the first SRv6 TE Policy.

[0147] It can be seen that in the embodiment of the present application, based on the first instruction, the first identifier is dynamically queried, and the SRv6 TE Policy is encapsulated based on the first identifier, thereby realizing dynamic binding of the SRv6 TE Policy, so that the first network node can provide a diversion service for the message based on the first identifier. Compared with the related art, 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 message forwarding path. Even if the node in the subdomain changes, resulting in a change in the BSID, the head node of the main domain does not need to re-plan the message forwarding path, thereby reducing the resource consumption of message forwarding.

[0148] And it can be understood that one BDSID can correspond to multiple SRv6 TE Policies. For example, assume that the DOH extension header of message 1 received by the first network node is encapsulated with identifier 1, and the DOH extension header of message 2 received by the first network node is encapsulated with identifier 2. Here, message 1 and message 2 can both be regarded as the first message. Although identifier 1 and identifier 2 are respectively encapsulated in the same field type of message 1 and message 2, identifier 1 and identifier 2 are not the same. Then, when identifier 1 and identifier 2 correspond to different SRv6TE Policies, the first network node can determine different SRv6 TE Policies for message 1 and message 2 based on the End.BD6.D instruction bound to the same BDSID. It can be seen that one BDSID can correspond to multiple SRv6 TE Policies. Then, the first network node only needs to configure one BDSID to encapsulate different SRv6 TE Policies for the message. Compared with the solution in the related art that one BSID corresponds to only one SRv6 TE Policy, the solution in the embodiment of the present application 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: encaps mode or insert mode.

[0150] In actual applications, the encapsulation method corresponding to the encaps mode is: adding a new SRv6 header to the outer layer of the first message. The SRv6 header includes the IPv6 basic message header, the IPv6 extension header, and the SRH extension header.

[0151] The encapsulation method corresponding to the insert mode is: inserting 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 the content of the first message in the second message may have some fields changed compared with the first message before encapsulation.

[0153] In actual applications, when the first message is encapsulated based on the encaps mode to obtain the second message, the SRv6 header newly 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 based on the insert mode to obtain the second message, the SRH newly added to the second message relative to the first message, and the content of the first message header in the second message except the SRH can be regarded as the second message header.

[0155] In practical applications, the second message header may also be encapsulated with a first identifier. The first identifier may be encapsulated in a field of the same field type in the first message header and the second message header, or the first identifier may be encapsulated in a field of a different field type in the first message header and the second message header. It is understandable that the network node receiving the second message can obtain the first identifier by performing a layer of parsing on the second message, and then determine the traffic characteristics, and perform subsequent processing based on the traffic characteristics, which reduces the difficulty of parsing, reduces performance consumption, and thus improves the message 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 constitute 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 takes the encapsulation of the first identifier as an example to illustrate the working mode of the encapsulation 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 field type in the first message header and the second message header. Figure 7 as well as Figure 8 The identifier 1 in the figure is equivalent to the first identifier in the embodiment of the present application.

[0158] In actual applications, when the first identifier is encapsulated in a field of the first field type in the first message header of the first message, during the encapsulation of the first message based on the encaps mode, the first identifier needs to be copied to the 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 in a DOH extension header in a first message header of a first message 1, after the first message is encapsulated based on the encaps mode to obtain a second message 1, the first identifier is located in a field in a DOH extension header in a newly added SRv6 header.

[0160] In actual applications, when the first identifier is encapsulated in a field of the first field type in the first message header of the first message, and the first field type is the field type of other fields except the field in the SRH, the first identifier does not need to be processed 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 in a DOH extension header in a first message header of a first message 1, after the first message 1 is encapsulated based on the insert mode to obtain a second message 1, the first identifier is still located in the field in the DOH extension header.

[0162] In actual applications, when the first identifier is encapsulated in a field of the first field type in the first message header of the first message, and the first field type is the field type of the field in the SRH, during the process of encapsulating the first message based on the insert mode, the first identifier needs to be copied to 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 in the SRH in the first message 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 in the newly added SRH.

[0164] In actual applications, there are more contents in the HBH extension header and the DOH extension header. It is understandable that copying these extension headers during the message encapsulation process may increase performance overhead. Based on the above example, it can be seen that when the first identifier is encapsulated in a field of the first field type in the first message header of the first message, and the first field type is a field type of other fields except the field in the SRH, in the process of encapsulating the first message based on the insert mode, the first identifier does not need to be processed. Therefore, in actual 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 message based on the 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 the insert mode.

[0166] In this way, the copying operation of the HBH extension header and / or the DOH extension header during the encapsulation process is avoided, thereby reducing the performance overhead.

[0167] Corresponding to the message processing method applied to the first network node in the above embodiment, the embodiment of the present application also provides a message processing method, which is applied to the second network node, and 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, and can also be expressed as a network element or node.

[0168] See also Fig. 9 , the method comprising:

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

[0170] Among them, a first identifier is encapsulated in a setting field of the first message header; the first identifier represents an identifier having a first setting mapping relationship with a traffic characteristic of the first message; the first identifier is used for a first network node in the first domain to encapsulate the first message after receiving the first message to obtain a second message; a second message header corresponding to the first SRv6 TE Policy is encapsulated in the second message, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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 a first message.

[0172] In practical applications, the first network node can be regarded as a head node in the first domain, that is, an edge node. When the second domain is regarded as a main domain, the first domain can be regarded as a subdomain of the second domain. The first domain and the second domain can be connected through the first network node.

[0173] In actual applications, the second network node may plan an SRv6TEPolicy for the third message in the second domain. Here, the planned SRv6 TE Policy is expressed as a second SRv6 TE Policy. Then, the second network node may encapsulate a message header corresponding to the second SRv6 TE Policy for the third message, thereby obtaining the first message and sending it out. Here, the message header corresponding to the second SRv6 TE Policy is equivalent to the first message header.

[0174] In the process of encapsulating the first message header, the second network node can, based on the third set mapping relationship, use the SRv6 TE Policy matching the first identifier as the second SRv6 TE Policy, and encapsulate a new SRH for the first message based on the second SRv6 TE Policy, thereby implementing the encapsulation of the first message header to obtain the first message; the SRH includes a Segment List corresponding to the second SRv6 TE Policy.

[0175] In actual applications, the third set mapping relationship can be expressed as a diversion strategy, which can map the first identifier with the SRv6 TE Policy. The diversion strategy can include one or more mapping strategies. For example, the mapping strategy can be illustrated as <identifier 1in DOH, SRv6 TE Policy1>, or <class A, SRv6 TE Policy1>, where class A can be a collection of first identifiers of messages that follow the same message forwarding path of the first domain, or a collection of traffic characteristics of messages that follow the same message forwarding path of the first domain. It can be understood that the first identifier and the traffic characteristic have a first set mapping relationship. Therefore, the mapping relationship between the collection of traffic characteristics and the SRv6 TE Policy can also be regarded as: the mapping relationship between the collection of first identifiers and the SRv6 TE Policy.

[0176] In practical applications, the third setting mapping relationship may be sent from the controller or the upper 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 control node.

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

[0178] The first message may 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; wherein 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 directly sent by the second network node to the third network node that performs the first forwarding, and 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 by the second network node to the first network node, and it should be noted that the role of the third network node in this case is equivalent to transparent forwarding, therefore, corresponding to the first message sent by the second network node, the corresponding message received by the first network node can be understood as the first message. In the process of forwarding 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 and the message forwarding path of the message.

[0179] In actual applications, after receiving the first message, the first network node can query the setting field of the first message header of the first message based on the Endpoint instruction to obtain the first identifier, and encapsulate the first message based on the first identifier to obtain the second message. The Endpoint instruction can indicate that there is a field that the first network node needs to query, which is also the setting field.

[0180] In the process of encapsulating the second message header, the first network node may, based on the second set mapping relationship, use the SRv6 TE Policy that matches the first identifier as the first SRv6 TE Policy, and encapsulate a new SRH for the first message based on the first SRv6 TE Policy, thereby implementing the encapsulation of the second message header, thereby obtaining the second message; the SRH includes the Segment List corresponding to the first SRv6 TE Policy. The first SRv6 TE Policy can be used to describe the message forwarding path of the second message in the first domain. Here, the second message header corresponds to the first SRv6 TE Policy, which can be understood as the Segment List in the SRH in the second message header corresponding to the first SRv6 TE Policy. The network node in the first domain can forward the second message based on the message forwarding path indicated by the Segment List in the second message, and the message forwarding path indicated by the Segment List in the second message header is also the message forwarding path of the first domain described by the first SRv6 TE Policy.

[0181] In actual applications, the second set mapping relationship can be expressed as a diversion strategy, which can map the first identifier with the SRv6 TE Policy. The diversion strategy can include one or more mapping strategies. For example, the mapping strategy can be illustrated as <identifier 1in DOH, SRv6 TE Policy1>, or <class A, SRv6 TE Policy1>, where class A can be a collection of first identifiers of messages that follow the same message forwarding path of the first domain, or a collection of traffic characteristics of messages that follow the same message forwarding path of the first domain. It can be understood that the first identifier and the traffic characteristic have a first set mapping relationship. Therefore, the mapping relationship between the collection of traffic characteristics and the SRv6 TE Policy can also be regarded as: the mapping relationship between the collection of first identifiers and the SRv6 TE Policy.

[0182] In practical applications, the second set mapping relationship may be sent from the controller or the upper control node to the first network node.

[0183] It should be noted that the third setting mapping relationship and the second setting mapping relationship can both be regarded as diversion strategies. In the embodiment of the present application, the third setting mapping relationship can be regarded as the diversion strategy of the message in the second domain, which is used to determine the forwarding path of the message in the second domain. The second setting mapping relationship can be regarded as the diversion strategy of the message in the first domain, which is used to determine the forwarding path of the message in the first domain.

[0184] It can be seen that the first network node can encapsulate the first message with the message header corresponding to the first SRv6 TE Policy based on the first identifier having a first set mapping relationship with the traffic characteristics, so that the second message obtained after encapsulation can be forwarded in the first domain, that is, the first network node provides the message with a traffic diversion service in the first domain based on the first identifier. It can be seen that the second SRv6TE Policy planned by the second network node does not need to involve the specific forwarding path of the message in the first domain, and can also ensure the forwarding of the message in the first domain based on the encapsulation operation of the first network node. Therefore, the second SRv6 TE Policy can also be regarded as describing the message forwarding path in the second domain and the first domain.

[0185] In an embodiment of the present application, the head network node of the second domain, that is, the second network node, encapsulates the first message header for the third message, obtains the first message and sends it out, and the first identifier is used for the first network node of the first domain to encapsulate the message header corresponding to the first SRv6 TE Policy for the first message after receiving the first message, so that the second message obtained after encapsulation can be forwarded in the first domain, that is, the first network node provides a traffic diversion service for the message based on the first identifier. Compared with the related art, 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 message forwarding path. Even if the node in the subdomain changes, resulting in a change in the BSID, the head node of the main domain does not need to re-plan the message forwarding path, thereby reducing the resource consumption of message forwarding.

[0186] The first identifier is further described below.

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

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

[0189] Second information, where 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 actual applications, the first information may include information such as the user's identification and name; the second information may include information such as the type of service; and the third information may include information such as actions corresponding to the network element processing method.

[0192] In practical applications, the first set mapping relationship can be expressed as a traffic identifier mapping table, which can map traffic characteristics with 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 may include one or more mapping pairs. Exemplarily, the mapping pair can be illustrated as <traffic characteristic 1, identifier 1 in DOH>. The mapping pair can be understood as: traffic characteristic 1 corresponds to identifier 1, and identifier 1 needs to be encapsulated in the DOH extended header field of the message. Here, identifier 1 is equivalent to the first identifier in the embodiment of the present application.

[0193] In practical applications, the first set mapping relationship can be sent by the controller or the upper control node to the second network node, and the second network node can generate a first message encapsulating the first identifier based on the first set mapping relationship.

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

[0195] In actual applications, the first identifier is encapsulated in a setting field of the first message header of the first message.

[0196] In one embodiment, the field type corresponding to the setting field includes one or more of the following: a flow label, a field type of a field located in an HBH extension header, a field type of a field located in a DOH extension header, and a field type of a field located in an SRH;

[0197] The field type of the fields in the SRH includes one or more of the following: tag, type-length-value TLV.

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

[0199] In actual applications, the field type corresponding to the setting field may also include: the field type of the field in other IPv6 extension headers except 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 process of the solution provided in the embodiment of the present application is described below based on an example. Fig.10 , wherein 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 the subdomain of domain 1; here, domain 2 is equivalent to the first domain in the embodiment of the present application, domain 1 is equivalent to the second domain in the embodiment of the present application, R2 is equivalent to the first network node in the embodiment of the present application, and R1 is equivalent to the second network node in the embodiment of the present application.

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

[0203] Step 1: The controller sends the identifier mapping table, traffic diversion policy, 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 diversion policy includes: <class A, TE Policy P>, where traffic feature 1 and traffic feature 2 both belong to class A; the SRv6 TE Policy includes TE Policy P, that is, Segment List [B->H].

[0205] In actual applications, the SRv6 TE Policy delivered by the controller can be regarded as the packet forwarding path determined based on the R1 plan.

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

[0207] In this example, the traffic diversion policy includes: <Identifier 1 in DOH, TE Policy P1> and <Identifier 2 in DOH, TEPolicy P2>; the SRv6 TE Policy includes: TE Policy P1 and TE Policy P2. 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 and sends the first message.

[0209] In this example, R1 may receive message 1, and R1 determines that the traffic characteristics of message 1 hit the <traffic characteristics 1, identification 1 in DOH> and the diversion strategy <class A, TE Policy P> in the identification mapping table. Then, R1 encapsulates message header 1 for message 1, obtains message 2, and sends message 2; wherein, the Segment List in the SRH in message header 1 corresponds to TE Policy P, and message header 1 includes a DOH extension header, and the DOH extension header encapsulates identification 1. Here, message 1 is equivalent to the third message in the embodiment of the present application, message 2 is equivalent to the first message in the embodiment of the present application, and message header 1 is equivalent to the first message header in the embodiment of the present application.

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

[0211] In this example, the message forwarding path described by TE Policy P is: A->B->H. Therefore, the destination address of message 2 when forwarded to R2 is B, which is a BDSID configured locally by R2, and the BDSID corresponds to the instruction End.BD6.D. Based on this, R2 executes the instruction End.BD6.D. Specifically, R2 queries for identifier 1 in the DOH extension header of message 2, and determines that identifier 1 hits the diversion policy <identifier 1in DOH, TE Policy P1>, and then encapsulates message header 2 corresponding to TE Policy P1 for message 2, obtains message 3, and then forwards message 3. Here, message 3 is equivalent to the second message in the embodiment of the present application, message header 2 is equivalent to the second message header in the embodiment of the present application, and the TE Policy of message 3 in domain 2 is P1. In this example, the network nodes in domain 2 will forward message 3 according to the message forwarding path described by TE Policy P1, that is, forward message 3 according to the path of 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, packet 3 reaches B9 after passing through the packet forwarding path B->C->D->E->G->B9. That is, after being forwarded back to R2, the path of packet 3 in domain 2 ends. R2 decapsulates packet header 2 in packet 3 to obtain a decapsulated packet; then R2 forwards the decapsulated packet based on the packet forwarding path indicated by TE Policy P, that is, sends it to R8, so that the packet passes through the remaining network nodes in domain 1; here, the decapsulated packet can be regarded as the re-obtained packet 2.

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

[0215] It can be understood that for the message received by R1 that hits <identifier 2in DOH, TE Policy P2>, such as message 4, the TE Policy of the message in domain 1 is P, which is the same as the TE Policy of message 1 in domain 1, and the TE Policy used in domain 2 is P2, which is different from the TE Policy of message 1 in domain 2.

[0216] It can be seen that in this example, R1 only needs to configure one TE Policy, and R2 only needs to configure one BDSID to implement the TE Policy difference scenario in the forwarding process of message 2 and message 4. However, if the scenario in this example is implemented based on the BSID solution in the related art, R1 needs to plan two TE Policies, and R2 also needs to configure two BSIDs. Obviously, the solution in the related art consumes more resources, that is, the solution of the embodiment of the present application reduces the resource consumption of message forwarding compared with the related art.

[0217] Based on the above embodiments, the present application also provides a message processing device, which is applied to a first network node in a first domain, see Fig.12 , the message processing device comprises:

[0218] The first receiving unit 1201 is used to receive a first message; a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic feature of the first message;

[0219] The first encapsulation unit 1202 is configured to query the setting 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 is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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;

[0220] The first sending unit 1203 is configured to send the second message.

[0221] In one embodiment, the first encapsulation unit 1202 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 the second message, including:

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

[0223] The first SID represents a destination address in the first message 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 message header, and encapsulate the first message based on the first identifier.

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

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

[0226] In one embodiment, the field type corresponding to the setting field includes one or more of the following: a flow label, a field type of a field located in an HBH extension header, a field type of a field located in a DOH extension header, and a field type of a field located in an SRH;

[0227] The field type of the field in the SRH includes one or more of the following: tag, TLV.

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

[0229] first information, where the first information is used to identify a user corresponding to the first message;

[0230] second information, where 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 in the second domain.

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

[0234] It should be noted that: when the message processing device provided in the above embodiment performs message processing, only the division of the above program modules is used as an example. In actual application, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the message processing device provided in the above embodiment and the message processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0235] Based on the above embodiments, the present application further provides a message processing device, which is applied to a second network node, wherein the second network node represents a head network node in a second domain, Fig.13 , the message processing device comprises:

[0236] The second encapsulation unit 1301 is used to encapsulate the first message header for the third message to obtain the first message; the setting field of the first message header is encapsulated with a first identifier; the first identifier represents an identifier having a first setting mapping relationship with the traffic characteristics of the first message; the first identifier is used for a first network node in a first domain to encapsulate the first message after receiving the first message to obtain a second message; the second message is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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] The second sending unit 1302 is configured to send the first message.

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

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

[0240] first information, where the first information is used to identify a user corresponding to the first message;

[0241] second information, where 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 setting mapping relationship sent by a controller or an upper control node.

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

[0245] It should be noted that: when the message processing device provided in the above embodiment performs message processing, only the division of the above program modules is used as an example. In actual application, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the message processing device provided in the above embodiment and the message processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, 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 embodiment of the present application, the present application also provides an electronic device, see Fig.14 , the electronic device comprises:

[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 implement information exchange with other devices, and is used to execute the method 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; a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic feature of the first message; and, 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 is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy having 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.

[0251] In one embodiment, the first processor 1402 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 the second message, including:

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

[0253] The first SID represents a destination address in the first message 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 message header, and encapsulate the first message based on the first identifier.

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

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

[0256] In one embodiment, the field type corresponding to the setting field includes one or more of the following: a flow label, a field type of a field located in an HBH extension header, a field type of a field located in a DOH extension header, and a field type of a field located in an SRH;

[0257] The field type of the field in the SRH includes one or more of the following: tag, TLV.

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

[0259] first information, where the first information is used to identify a user corresponding to the first message;

[0260] second information, where 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 used to receive the second setting mapping relationship sent by a controller or an upper control node.

[0263] Of course, in actual application, the various components in the 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, Fig.14 Various buses are labeled as bus system 1404.

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

[0265] The method disclosed in the above embodiment of the present 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 an integrated logic circuit of the hardware in the first processor 1402 or an instruction in the form of software. The above-mentioned first processor 1402 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The first processor 1402 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module 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 above 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 methods.

[0267] It can be understood that the first memory 1403 of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and 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), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAMbus random access memory (DRRAM, Direct Rambus Random Access Memory).The memories described in the embodiments of the present 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 embodiment of the present application, the present application also provides an electronic device, see Fig.15 , the electronic device comprises:

[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 implement information exchange with other devices and is used to execute the method provided by one or more technical solutions in the above embodiments when running the computer program. The computer program is stored in the second memory 1503.

[0271] Specifically, the second processor 1502 is used to encapsulate the first message header for the third message to obtain the first message; the setting field of the first message header is encapsulated with a first identifier; the first identifier represents an identifier having a first setting mapping relationship with the traffic characteristics of the first message; the first identifier is used for 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 is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents the SRv6 TE Policy having a second setting 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 setting field includes one or more of the following: a flow label, a field type of a field located in an HBH extension header, a field type of a field located in a DOH extension header, and a field type of a field located in an SRH.

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

[0275] first information, where the first information is used to identify a user corresponding to the first message;

[0276] second information, where 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 further configured to receive the first setting mapping relationship sent by a controller or an upper control node.

[0279] Of course, in actual application, the various components in the electronic device are coupled together through the bus system 1504. It can be understood that the bus system 1504 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1504 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.15 Various buses are labeled as bus system 1504.

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

[0281] The method disclosed in the above embodiment of the present application can be applied to the second processor 1502, or implemented by the second processor 1502. The second processor 1502 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 hardware integrated logic circuit or software instructions in the second processor 1502. The above-mentioned second processor 1502 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The second processor 1502 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the second memory 1503. The second processor 1502 reads the information in the second memory 1503 and completes the steps of the above method in combination with its hardware.

[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 methods.

[0283] It can be understood that the second memory 1503 of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and 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), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAMbus random access memory (DRRAM, Direct Rambus Random Access Memory).The memories described in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0284] In an exemplary embodiment, the embodiment of the present application further provides a storage medium, that is, a computer storage medium, specifically a computer-readable storage medium, for example, including a first memory 1403 storing a computer program, and the computer program can be executed by a first processor 1402 of an electronic device to complete the steps of the aforementioned first network node side method. For another example, including a second memory 1503 storing a computer program, the computer program can be executed by a second processor 1502 of an electronic device to complete the steps of the aforementioned second network node side method.

[0285] In an exemplary embodiment, the embodiment of the present application further provides a computer program product, including a computer program, which can be executed by the first processor 1402 of the electronic device to complete the steps of the first network node side method. For example, a second memory 1503 storing the computer program is included, and the computer program can be executed by the second processor 1502 of the electronic device to complete the steps of the second network node side method.

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

[0287] The term "and / or" herein is only a description of the association relationship of the associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "at least one" herein represents any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C can represent including any one or more elements selected from the set consisting of A, B, and C.

[0288] In addition, the technical solutions described in the embodiments of the present application can be combined arbitrarily without conflict.

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

Claims

1. A message processing method, characterized in that: Applied to a first network node in a first domain, the method comprises: receiving a first message; a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic feature of the first message; querying the setting field of the first message header to obtain the first identifier, and encapsulating the first message based on the first identifier to obtain a second message; wherein the second message is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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; The second message is sent.

2. The method according to claim 1, characterized in that The querying the setting 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: Execute the first instruction bound to the first segment identifier SID; wherein, The first SID represents a destination address in the first message 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 message header, and encapsulate the first message based on the first identifier.

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

4. The method according to claim 3, characterized in that In the case where the first identifier is encapsulated in a field in a hop-by-hop HBH extension header and / or a field in a destination option 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 field type corresponding to the setting field includes one or more of the following: a flow label, a field type of a field located in an HBH extension header, a field type of a field located in a DOH extension header, and a field type of a field located in a segment routing header SRH; The field type of the field in the SRH includes one or more of the following: tag, type-length-value TLV.

6. The method according to claim 1, characterized in that The first identifier includes one or more of the following: first information, where the first information is used to identify a user corresponding to the first message; second information, where 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.

7. The method according to claim 1, characterized in that The method further comprises: The second setting mapping relationship sent by the receiving controller or the upper control node is received.

8. The method according to claim 1, characterized in that The receiving of the first message comprises: A first message sent by a network node in the second domain is received.

9. A message processing method, characterized in that: Applied to a second network node, the second network node represents a head network node in a second domain; the method comprises: A first message header is encapsulated for 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 having a first setting mapping relationship with a traffic feature of the first message; the first identifier is used for a first network node in a first domain to encapsulate the first message after receiving the first message to obtain a second message; a second message header corresponding to a first SRv6 TE Policy is encapsulated in the second message, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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 first message is sent.

10. The method according to claim 9, characterized in that The field type corresponding to the setting field includes one or more of the following: a flow label, a field type of a field located in an HBH extension header, a field type of a field located in a DOH extension header, and a field type of a field located in an SRH.

11. The method according to claim 9, characterized in that The first identifier includes one or more of the following: first information, where the first information is used to identify a user corresponding to the first message; second information, where 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.

12. The method according to claim 9, characterized in that The method further comprises: The first setting mapping relationship sent by the controller or the upper control node is received.

13. A message processing device, characterized in that: A first network node applied in a first domain includes: A first receiving unit is configured to receive a first message; a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic feature of the first message; a first encapsulation unit, configured to query the setting 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 is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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 first sending unit is used to send the second message.

14. A message processing device, characterized in that: Applied to a second network node, where the second network node represents a head network node in a second domain, comprising: a second encapsulation unit, configured to encapsulate a first message header for 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 having a first setting mapping relationship with a traffic feature of the first message; the first identifier is used for a first network node in a first domain to encapsulate the first message after receiving the first message to obtain a second message; a second message header corresponding to a first SRv6 TE Policy is encapsulated in the second message, the first SRv6 TE Policy represents an SRv6 TEPolicy having a second setting 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; The second sending unit is used to send the first message.

15. 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; a first identifier is encapsulated in a setting field of a first message header of the first message; the first identifier represents an identifier having a first setting mapping relationship with a traffic feature of the first message; and, send a second message; The first processor is configured to query the setting 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 is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TE Policy having a second setting 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.

16. An electronic device, characterized in that: include: A second processor and a second communication interface; wherein, The second processor is used to encapsulate the first message header for the third message to obtain the first message; the setting field of the first message header is encapsulated with a first identifier; the first identifier represents an identifier having a first setting mapping relationship with the traffic characteristics of the first message; the first identifier is used for 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 is encapsulated with a second message header corresponding to the first SRv6 TE Policy, the first SRv6 TE Policy represents an SRv6 TEPolicy having a second setting 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; The second communication interface is used to send the first message.

17. An electronic device, characterized in that: include: a first processor and a first memory for storing a computer program executable on the processor, Wherein, when the first processor is used to run the computer program, the steps of the method described in any one of claims 1 to 8 are executed.

18. An electronic device, characterized in that: include: a second processor and a second memory for storing a computer program executable on the processor, Wherein, when the second processor is used to run the computer program, the steps of the method described in any one of claims 9 to 12 are executed.

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

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

Images