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 sent by a second network node in a second domain; a first identifier is packaged in a first message header of the first message, and the first identifier and a flow characteristic of the first message have a set mapping relationship; packaging a second message header for the first message to obtain a second message; the first identifier is packaged in the second message header; 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, the increase in domain divisions in the network makes it more difficult for nodes on the message forwarding path to parse Internet Protocol Version 6 (SRv6) messages, affecting the message forwarding efficiency. 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 sent by a second network node in a second domain; a first identifier is encapsulated in a first message header of the first message, and the first identifier has a set mapping relationship with a traffic feature of the first message;

[0007] encapsulating the first message with a second message header to obtain a second message; the second message header is encapsulated with the first identifier;

[0008] The second message is sent.

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

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

[0011] second information, where the second information is used to identify the service corresponding to the first message;

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

[0013] In the above solution, the first identifier is encapsulated in fields of the same field type in the first message header and the second message header respectively.

[0014] In the above solution, the first identifier is encapsulated in a field of a first field type in the first message header, and the first identifier is encapsulated in a field of a second field type in the second message header.

[0015] In the above scheme, the second field type includes: a field type determined based on the first field type, or a field type determined based on the first identifier, or a set field type.

[0016] In the above scheme, the first field type includes one or more of the following: a flow label, a field type of a field in a Hop-by-Hop (HBH) extension header, a field type of a field in a Destination Options Header (DOH) extension header, and a field type of a field in a Segment Routing Header (SRH);

[0017] The field type of the field in the SRH includes one or more of the following: a tag, a type-length-value (TLV), and an arguments segment of a segment identifier (SID).

[0018] In the above solution, the first message represents an SRv6 message;

[0019] The working mode of encapsulating the second message header of the first message includes: encaps mode or insert mode.

[0020] In the above solution, the sending of the second message includes:

[0021] sending the second message to a third network node in the first domain; and / or,

[0022] The second message is sent to a fourth network node in the third domain.

[0023] 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:

[0024] A first receiving unit, configured to receive a first message sent by a second network node in a second domain; a first identifier is encapsulated in a first message header of the first message, and a set mapping relationship exists between the first identifier and a traffic feature of the first message;

[0025] an encapsulation unit, configured to encapsulate the first message with a second message header to obtain a second message; the second message header is encapsulated with the first identifier;

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

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

[0028] The first communication interface is used to receive a first message sent by a second network node in a second domain; a first identifier is encapsulated in a first message header of the first message, and the first identifier has a set mapping relationship with a traffic feature of the first message; and send a second message;

[0029] The first processor is used to encapsulate the first message with a second message header to obtain the second message; the second message header is encapsulated with the first identifier.

[0030] The 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,

[0031] Wherein, the first processor is used to execute the steps of any of the above methods when running the computer program.

[0032] An embodiment of the present application further provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above methods are implemented.

[0033] An embodiment of the present application also provides a computer program product, including a computer program, which implements the steps of any of the above methods when executed by a processor.

[0034] In the embodiment of the present application, the first network node of the first domain receives the first message sent by the second network node of the second domain, where the first message header of the first message is encapsulated with a first identifier, and the first identifier has a set mapping relationship with the traffic characteristics of the first message; then, the second message header is encapsulated in the first message to obtain the second message, and the second message header is encapsulated with the first identifier; then, the second message is sent. In this way, after the message is transmitted across domains, the first identifier that has a set mapping relationship with the traffic characteristics is still encapsulated in the message header, which reduces the difficulty of parsing and improves the message forwarding efficiency compared to related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0038] Figure 4 Another packaging position schematic diagram provided for an embodiment of the present application;

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

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

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

[0042] Figure 8 A schematic diagram of a fourth packaging method provided in an embodiment of the present application;

[0043] Fig. 9 A schematic diagram of an interactive process of a message processing method provided in an embodiment of the present application;

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

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

[0046] In the related art, the increased division of domains in the network makes it more difficult for nodes on the message forwarding path to parse SRv6 messages. For example, nodes on the message forwarding path may need to parse out traffic characteristics such as users corresponding to SRv6 messages during the process of message forwarding. However, the forwarding of SRv6 messages in multiple domains makes the encapsulation level of traffic characteristics too deep, resulting in increased difficulty in parsing, thereby reducing the message forwarding efficiency.

[0047] Based on this, in the embodiment of the present application, the first network node of the first domain receives the first message sent by the second network node of the second domain, where the first message header of the first message is encapsulated with a first identifier, and the first identifier has a set mapping relationship with the traffic characteristics of the first message; then, the second message header is encapsulated in the first message to obtain the second message, and the second message header is encapsulated with the first identifier; then, the second message is sent. In this way, after the message is transmitted across domains, the first identifier that has a set mapping relationship with the traffic characteristics is still encapsulated in the message header, which reduces the difficulty of parsing and improves the efficiency of message forwarding compared to related technologies.

[0048] For ease of understanding, the main concepts involved in the embodiments of the present application are first explained:

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

[0050] 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.

[0051] 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.

[0052] Endpoint instruction: used to instruct the node to perform actions when processing a SID. Each SID is bound to an Endpoint instruction. The SID processed by the node can be specified by the SRH display in the received message, thereby providing forwarding, encapsulation, and decapsulation for the message.

[0053] 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.

[0054] 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), network service header (NSH), SRv6, etc.

[0055] 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, the edge nodes based on these domains form a service chain, which can run through the entire network and can be expressed as an upper-level chain or main chain. The nodes in the upper-level chain can also be regarded as forming a domain, that is, the main domain. The domain composed of the nodes in the lower-level chains in the upper-level chain can be regarded as a sub-domain of the main domain. In this way, the upper-level chain can connect the lower-level chains in different sub-domains in series, realizing a hierarchical service chain, thereby providing a complete end-to-end service chain service.

[0056] 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, R5, R6 and R7 can be regarded as nodes in domain 3, R5, R6 and R7 form a service chain 3, where R2 is the edge node of domain 2, R5 is the edge node of domain 3, R2 and R5 are also the intermediate nodes of domain 1, service chain 2 and service chain 3 can be regarded as subchains of service chain 1, and domain 2 and domain 3 can be regarded as subdomains 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, such as R5.

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

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

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

[0060] See also Figure 2 , the method comprising:

[0061] Step 201: Receive a first message sent by a second network node in a second domain.

[0062] Among them, a first identifier is encapsulated in the first message header of the first message, and the first identifier has a set mapping relationship with the traffic characteristics of the first message.

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

[0064] Here, the first domain and the second domain may be connected through the first network node.

[0065] In practical applications, when the second domain is understood as a main domain, the first domain can be understood as a subdomain of the second domain.

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

[0067] In practical applications, traffic characteristics may be information such as the user, service, and network element processing method corresponding to the first message. 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 processing method of the network node for the first message, such as the path forwarding method.

[0068] In practical applications, the mapping relationship can be set and sent by the controller or the upper control node.

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

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

[0071] Second information, where the second information is used to identify the service corresponding to the first message;

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

[0073] 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.

[0074] In practical applications, after receiving the first message, the first network node may parse the first identifier from the first message header. The first identifier may be encapsulated in a field of the first field type in the first message header.

[0075] In one embodiment, the first field type 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;

[0076] The field types of the fields in the SRH include one or more of the following: a tag, a TLV, and an arguments segment of a SID.

[0077] 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.

[0078] In practical applications, the first field type may also include: field types of fields located in other IPv6 extension headers except the HBH extension header and the DOH extension header.

[0079] For example, Figure 3 and Figure 4 The SRv6 message structure in the related art is shown, wherein: Figure 4 Equivalent to Figure 3 An item in the Segment List in the SRH extension header shown, that is, a SID, and Figure 3 and Figure 4 Fields where the first identifier may be located in the first message following the message structure are circled.

[0080] in, Figure 3 Flow Label is equivalent to flow label. Figure 3 The Tag in the SRH extension header is equivalent to the label in the SRH. Figure 4 The arguments in the SID field are equivalent to the arguments field of the SID in the SRH.

[0081] Step 202: encapsulate the first message with a second message header to obtain a second message.

[0082] The second message header is encapsulated with the first identifier.

[0083] In actual applications, the first network node may parse 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.

[0084] In the embodiment of the present application, the first identifier is encapsulated in the second message header of the second message. In this way, it can be understood that the first identifier can be obtained by performing a layer of parsing on the second message, and then the traffic characteristics can be determined, which reduces the difficulty of parsing, reduces performance consumption, and thus improves the message forwarding efficiency.

[0085] 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.

[0086] Step 203: Send a second message.

[0087] In one embodiment, sending a second message includes:

[0088] Sending a second message to a third network node in the first domain; and / or,

[0089] A second message is sent to a fourth network node in the third domain.

[0090] In actual applications, the first network node may send the second message only to the third network node, may send the second message only to the fourth network node, or may send the second message to both the third network node and the fourth node.

[0091] In actual applications, after receiving the second message, the third network node and / or the fourth network node can parse out the first identifier in the second message, thereby obtaining the traffic characteristics of the message, and performing traffic processing based on the traffic characteristics. Exemplarily, the traffic processing can be: providing a service matching the service type based on the service type indicated by the traffic characteristics, or performing processing such as message forwarding based on the traffic characteristics.

[0092] In the embodiment of the present application, the first network node of the first domain receives the first message sent by the second network node of the second domain, where the first message header of the first message is encapsulated with a first identifier, and the first identifier has a set mapping relationship with the traffic characteristics of the first message; then, the second message header is encapsulated in the first message to obtain the second message, and the second message header is encapsulated with the first identifier; then, the second message is sent. In this way, after the message is transmitted across domains, the first identifier that has a set mapping relationship with the traffic characteristics is still encapsulated in the message header, which reduces the difficulty of parsing and improves the message forwarding efficiency compared to related technologies.

[0093] The method of encapsulating the second message header is described in detail below.

[0094] In one embodiment, the first message represents an SRv6 message; and the working mode of encapsulating the second message header into the first message includes: encaps mode or insert mode.

[0095] 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.

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

[0097] 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.

[0098] 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;

[0099] 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.

[0100] In actual applications, the first network node may encapsulate the first identifier in the second message header.

[0101] In one embodiment, the first identifier is encapsulated in fields of the same field type in the first message header and the second message header respectively.

[0102] In one embodiment, the first identifier is encapsulated in a field of a first field type in the first message header, and the first identifier is encapsulated in a field of a second field type in the second message header.

[0103] It can be seen that the field in which the first identifier is encapsulated in the second message header may include two situations:

[0104] Case 1: The first identifier is encapsulated in fields of the same field type in the first message header and the second message header.

[0105] In case 1, the relationship between the field encapsulating the first identifier in the first message header and the field encapsulating the first identifier in the second message header can be regarded as an inheritance relationship.

[0106] The following describes the message encapsulation method corresponding to situation 1 in combination with the working mode of the encapsulated message. It should be noted that in the following example, Figure 5 as well as Figure 6 The identifier 1 in the figure is equivalent to the first identifier in the embodiment of the present application.

[0107] 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.

[0108] For example, see Figure 5 , 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.

[0109] 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.

[0110] For example, see Figure 6 , 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.

[0111] 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.

[0112] For example, see Figure 6 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.

[0113] Case 2: The first identifier is encapsulated in fields of different field types in the first message header and the second message header.

[0114] Here, the first identifier is encapsulated in a field of a first field type in the first message header, and the first identifier is encapsulated in a field of a second field type in the second message header.

[0115] In case 2, the relationship between the field encapsulating the first identifier in the first message header and the field encapsulating the first identifier in the second message header can be regarded as an isolation relationship.

[0116] In actual applications, for security reasons, there may be a demand for a sub-domain to have an exclusive first identifier. The sub-domain having an exclusive first identifier means that when the network node in the sub-domain parses the first identifier in the message, the field parsed needs to be different from the encapsulation field of the message with the first identifier in the main domain.

[0117] In the embodiment of the present application, the first message can be regarded as a message in the first domain, and the second message can be regarded as a message in the second domain. Therefore, the difference in the field type of the encapsulation field of the first identifier in the first message header of the first message and the second message header of the second message can be regarded as the difference in the field type of the encapsulation field of the first identifier in the message in the first domain and the message in the second domain, that is, the isolation of the first identifier between domains is achieved. It can be understood that in the case where the first domain is understood as a subdomain of the second domain, the embodiment of the present application can achieve exclusive use of the first identifier by the subdomain, thereby improving the security of message processing.

[0118] The following describes the message encapsulation method corresponding to situation 2 in combination with the working mode of the encapsulated message. It should be noted that in the following example, 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.

[0119] In actual applications, during the process of encapsulating the first message based on the encaps mode, the first identifier needs to be copied to the field of the second field type in the newly added SRv6 header.

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

[0121] In actual applications, when the second field type is a field type other than the field in the SRH, during the encapsulation of the first message based on the insert mode, the first identifier needs to be copied to the field of the second field type already existing in the first message header.

[0122] For example, see Figure 8 When the first field type is the field type of the field in DOH and the second field type is Flow Label, after the first message 1 is encapsulated based on the insert mode to obtain the second message 1, the first identifier is located in the Flow Label field.

[0123] In actual applications, when the second field type is the field type of a 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 second set field type in the newly added SRH.

[0124] For example, see Figure 8When the first field type is the field type of the field in DOH and the second field type is the Tag in SRH, 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.

[0125] In actual applications, before encapsulating the second message header into the first message, the second field type may be determined first.

[0126] In one embodiment, the second field type includes: a field type determined based on the first field type, or a field type determined based on the first identifier, or a set field type.

[0127] In practical applications, the second field type can be determined based on the following three methods:

[0128] Method 1: Determine the second field type based on the first field type.

[0129] In actual applications, based on the first set mapping relationship, the field type matching the first field type can be determined as the second field type.

[0130] Exemplarily, when the first identifier is encapsulated in the Tag field in the SRH in the first message header, the arguments segment of the SID in the SRH can be determined as the second field type; when the first identifier is encapsulated in the TLV field in the SRH in the first message header, the field type of the field in the DOH extension header can be determined as the second field type.

[0131] Method 2: Determine the second field type based on the first identifier.

[0132] In actual applications, based on the second set mapping relationship, the field type matching the first identifier can be determined as the second field type.

[0133] In actual applications, the second field type can be determined based on the meaning of the first identifier used for identification. For example, when the first identifier is used to identify the user corresponding to the first message, the arguments segment of the SID in the SRH can be determined as the second field type; when the first identifier is used to identify the service corresponding to the first message, the Flow Label can be determined as the second field type.

[0134] In practical applications, the second field type may also be determined based on the content of the first identifier. For example, when the first identifier indicates that the user corresponding to the first message is user A, Flow Label may be determined as the second field type.

[0135] It can be understood that, in this way, no matter what type of field the first identifier is encapsulated in in the first message header, the encapsulation field of the first identifier in the second message header can be unified based on the first identifier. In practical applications, this unification of the encapsulation field can also be expressed as encapsulation normalization of the first identifier.

[0136] Exemplarily, if the first network node receives the first message 1 and the first message 2, wherein the first identifier 1 is encapsulated in the Flow Label field of the first message 1, and the first identifier 2 is encapsulated in the field in the DOH extension header of the first message 2, and the second field type determined according to the first identifier 1 and the first identifier 2 is the Tag in the SRH, then, after the first network node encapsulates the first message 1 into the second message 1 and the first message 2 into the second message 2, the first identifier 1 is encapsulated in the Tag in the SRH of the second message 1, and the first identifier 2 is encapsulated in the Tag in the SRH of the second message 2. It can be seen that the encapsulation normalization of the first identifier is achieved.

[0137] Method 3: Determine the set field type as the second field type.

[0138] Exemplarily, the Flow Label field may be determined as the second field type.

[0139] In this way, no matter what type of field the first identifier is encapsulated in in the first message header, the encapsulation field of the first identifier in the second message header can be kept unified, that is, the encapsulation of the first identifier is normalized.

[0140] In actual applications, after receiving multiple second messages that have been encapsulated and normalized to achieve the first identifier, the network node can parse the first identifier from a unified location, thereby reducing the difficulty and performance consumption of parsing the second message by the network node and improving processing efficiency.

[0141] For ease of understanding, the overall interaction process of the solution provided in the embodiment of the present application is described below, wherein the entities participating in the interaction include: a first network node, a second network node, and a processing network element; the processing network element includes: a third network node and / or a fourth network node.

[0142] See also Fig. 9 ,The overall interaction process includes the following steps:

[0143] Step 1: The second network node sends a first message to the first network node.

[0144] Among them, the first message header of the first message is encapsulated with a first identifier, and the first identifier has a set mapping relationship with the traffic characteristics of the first message.

[0145] Step 2: The first network node receives a first message.

[0146] Step 3: The first network node parses the first identifier in the first message.

[0147] Step 4: The first network node encapsulates the first message to obtain a second message.

[0148] The first identifier is encapsulated in the second message header of the second message.

[0149] Step 5: The first network node sends a second message to the processing network element.

[0150] Step 6: The processing network element receives the second message.

[0151] Step 7: The processing network element parses the second message header of the second message, obtains the first identifier, and performs traffic processing based on the first identifier.

[0152] In an embodiment of the present application, a first network node in a first domain receives a first message sent by a second network node in a second domain, wherein a first identifier is encapsulated in a first message header of the first message, and the first identifier has a set mapping relationship with the traffic characteristics of the first message; then, the second message header is encapsulated in the first message to obtain a second message, and the second message header is encapsulated with the first identifier; then, the second message is sent. In this way, after the message is transmitted across domains, the first identifier that has a set mapping relationship with the traffic characteristics is still encapsulated in the message header, which reduces the difficulty of parsing and improves the message forwarding efficiency compared to related technologies.

[0153] 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.10 , the message processing device comprises:

[0154] The first receiving unit 1001 is configured to receive a first message sent by a second network node in a second domain; a first identifier is encapsulated in a first message header of the first message, and a set mapping relationship exists between the first identifier and a traffic feature of the first message;

[0155] The encapsulation unit 1002 is configured to encapsulate the first message with a second message header to obtain a second message; the second message header is encapsulated with the first identifier;

[0156] The first sending unit 1003 is configured to send the second message.

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

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

[0159] second information, where the second information is used to identify the service corresponding to the first message;

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

[0161] In one embodiment, the first identifier is encapsulated in fields of the same field type in the first message header and the second message header, respectively.

[0162] In one embodiment, the first identifier is encapsulated in a field of a first field type in the first message header, and the first identifier is encapsulated in a field of a second field type in the second message header.

[0163] In one embodiment, the second field type includes: a field type determined based on the first field type, or a field type determined based on the first identifier, or a set field type.

[0164] In one embodiment, the first field type 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;

[0165] The field type of the field in the SRH includes one or more of the following: a tag, a TLV, and an arguments segment of a SID.

[0166] In one embodiment, the first message represents an SRv6 message;

[0167] The working mode of encapsulating the second message header of the first message includes: encaps mode or insert mode.

[0168] In one embodiment, the first sending unit 1003 sends the second message, including:

[0169] sending the second message to a third network node in the first domain; and / or,

[0170] The second message is sent to a fourth network node in the third domain.

[0171] In actual application, the first receiving unit 1001, the encapsulation unit 1002 and the first sending unit 1003 can all be implemented by a processor in the message processing device.

[0172] 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.

[0173] Based on the hardware implementation of the above program module, and in order to implement the method of the embodiment of the present application, the present application also provides an electronic device, referring to Fig.11 , the electronic device comprises:

[0174] The first communication interface 1 is capable of exchanging information with other devices;

[0175] The first processor 2 is connected to the first communication interface 1 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 3.

[0176] Specifically, the first communication interface 1 is used to receive a first message sent by a second network node in a second domain; a first identifier is encapsulated in a first message header of the first message, and the first identifier has a set mapping relationship with a traffic feature of the first message; and, send a second message;

[0177] The first processor 2 is used to encapsulate the first message with a second message header to obtain the second message; the second message header is encapsulated with the first identifier.

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

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

[0180] second information, where the second information is used to identify the service corresponding to the first message;

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

[0182] In one embodiment, the first identifier is encapsulated in fields of the same field type in the first message header and the second message header, respectively.

[0183] In one embodiment, the first identifier is encapsulated in a field of a first field type in the first message header, and the first identifier is encapsulated in a field of a second field type in the second message header.

[0184] In one embodiment, the second field type includes: a field type determined based on the first field type, or a field type determined based on the first identifier, or a set field type.

[0185] In one embodiment, the first field type 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;

[0186] The field type of the field in the SRH includes one or more of the following: a tag, a TLV, and an arguments segment of a SID.

[0187] In one embodiment, the first message represents an SRv6 message;

[0188] The working mode of encapsulating the second message header of the first message includes: encaps mode or insert mode.

[0189] In one embodiment, the first communication interface 1 sends the second message, including:

[0190] sending the second message to a third network node in the first domain; and / or,

[0191] The second message is sent to a fourth network node in the third domain.

[0192] It should be noted that the specific processing process of the first communication interface 1 can be understood by referring to the above method.

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

[0194] The first memory 3 in the embodiment of the present application is used to store various types of data to support operations in the electronic device. Examples of these data include: any computer program for operating on an electronic device. The method disclosed in the above embodiment of the present application can be applied to the first processor 2, or implemented by the first processor 2. The first processor 2 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 2 or an instruction in the form of software. The above-mentioned first processor 2 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 2 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiment 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 can be located in a storage medium, which is located in the first memory 3. The first processor 2 reads the information in the first memory 3 and completes the steps of the above method in combination with its hardware.

[0195] 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.

[0196] It can be understood that the first memory 3 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.

[0197] In an exemplary embodiment, the present application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, for example, an electronic device storing a computer program, and the computer program can be executed by the first processor 2 of the electronic device to complete the steps of the aforementioned method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface storage, optical disk, or CD-ROM.

[0198] In an exemplary embodiment, the embodiment of the present application further provides a computer program product, including a computer program, and the computer program can be executed by the first processor 2 of the electronic device to complete the steps of any of the aforementioned methods.

[0199] 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.

[0200] The term "and / or" herein is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent the three situations that A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "one or more" herein represents any combination of at least two of any one or more of a plurality. 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.

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

[0202] 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 sent by a second network node in a second domain; a first identifier is encapsulated in a first message header of the first message, and the first identifier has a set mapping relationship with a traffic feature of the first message; encapsulating the first message with a second message header to obtain a second message; the second message header is encapsulated with the first identifier; The second message is sent.

2. 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.

3. The method according to claim 1, characterized in that The first identifier is encapsulated in fields of the same field type in the first message header and the second message header respectively.

4. The method according to claim 1, characterized in that: The first identifier is encapsulated in a field of a first field type in the first message header, and the first identifier is encapsulated in a field of a second field type in the second message header.

5. The method according to claim 4, characterized in that The second field type includes: a field type determined based on the first field type, or a field type determined based on the first identifier, or a set field type.

6. The method according to claim 3 or 4, characterized in that: The first field type includes one or more of the following: a flow label, a field type of a field located in a HBH extension header, a field type of a field located in a destination option 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: a tag, a type-length-value TLV, and a parameter arguments segment of a segment identifier SID.

7. The method according to claim 1, characterized in that The first message represents an Internet Protocol version 6 segment routing SRv6 message; The working mode of encapsulating the second message header of the first message includes: encaps mode or insert mode.

8. The method according to claim 1, characterized in that The sending of the second message includes: sending the second message to a third network node in the first domain; and / or, The second message is sent to a fourth network node in the third domain.

9. A message processing device, characterized in that: A first network node applied in a first domain includes: A first receiving unit, configured to receive a first message sent by a second network node in a second domain; a first identifier is encapsulated in a first message header of the first message, and a set mapping relationship exists between the first identifier and a traffic feature of the first message; an encapsulation unit, configured to encapsulate the first message with a second message header to obtain a second message; the second message header is encapsulated with the first identifier; The first sending unit is used to send the second message.

10. 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 sent by a second network node in a second domain; a first identifier is encapsulated in a first message header of the first message, and the first identifier has a set mapping relationship with a traffic feature of the first message; and send a second message; The first processor is used to encapsulate the first message with a second message header to obtain the second message; the second message header is encapsulated with the first identifier.

11. 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.

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

13. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images