Message processing method, electronic device, and storage medium

Abstract

The present application relates to but not limited to the technical field of communications. Provided are a message processing method, an electronic device, and a storage medium. The method comprises: a first network node performing SRH extension encapsulation on a first service message carrying a first service type identifier, so as to obtain a second service message, wherein a segment list [0] in an SRH of the second service message carries a specific SID associated with the first service type identifier. A second network node generates a backhaul session table when an SL value in the SRH of the received second service message is 0 and the segment list [0] in the SRH carries the specific SID, so as to associate to a specific backhaul path on the basis of the backhaul session table after receiving a fourth service message from a server node.

Description

Message processing method, electronic device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on November 16, 2023, with application number 202311529787.6 and invention name “Message processing method, electronic device and storage medium”. The entire contents of the Chinese patent application are incorporated herein by reference. Technical Field

[0003] The embodiments of the present application relate to, but are not limited to, the field of communication technologies, and in particular to a message processing method, an electronic device, and a storage medium. Background Art

[0004] When accessing the network, if the access end is far from the server end, network delay, network freeze and packet loss are likely to occur; or during peak hours, the increase in access volume will increase the probability of network congestion, thereby reducing the user experience. Although in the related art, in order to solve the problems of network delay and service congestion, dedicated lines are usually created for services with higher service quality to redirect service messages that require higher service quality to accelerated channel processing, in actual applications, the same service exists across networks, that is, the network system for service transmission is composed of networks maintained by multiple different managers, such as the access end in the network managed by the operator and the server in the network not managed by the operator such as the enterprise. Therefore, when providing a higher quality user experience, the entire network system needs to meet the following three requirements: (1) identify the service type, (2) use specific channels for the outbound and return of the service, and (3) try not to have protocol extensions or have fewer protocol extensions. However, the message processing method of the service message in the related art cannot meet the above three requirements to provide a higher quality user experience. Therefore, there is an urgent need for a message processing method that can realize the transmission of specific services through specific paths in a network system with cross-networks.

[0005] Summary of the Invention

[0006] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

[0007] The embodiments of the present application provide a message processing method, an electronic device, and a storage medium, which can be implemented in a cross-network network system to realize the transmission of specific services through specific paths.

[0008] In a first aspect, a message processing method provided according to an embodiment of the present application includes: a first network node receives a first service message; when the first service message carries a first service type identifier, the first network node performs SRH header extension encapsulation on the first service message to obtain a second service message, wherein the segment list Segment list[0] in the SRH header of the second service message carries a specific SID associated with the first service type identifier; the first network node sends the second service message to the second network node, so that the second network node performs return message association-related operations according to the specific SID.

[0009] In the second aspect, the message processing method provided in accordance with the embodiment of the present application includes: the second network node receives a fourth service message from the server node, and obtains an association identifier from the fourth service message; the second network node determines the return journey session table corresponding to the fourth service message based on the correspondence between the association identifier and the return journey session table; the second network node determines the second SRv6 Policy path based on the return journey path indication information in the return journey session table; the second network node performs SRH header extension encapsulation on the fourth service message according to the second SRv6 Policy path to obtain a third service message; and maps the third service message to the second SRv6 Policy path to forward the third service message to the first network node through the second SRv6 Policy path.

[0010] In a third aspect, an embodiment of the present application further provides an electronic device comprising: one or more processors; a memory on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement: a message processing method as described in any one of the first aspects; or a message processing method as described in any one of the second aspects.

[0011] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements: a message processing method as described in any one of the first aspects; or a message processing method as described in any one of the second aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG1 is a diagram of a network system architecture for an embodiment of a message processing method provided by the present application;

[0013] FIG2 is a schematic diagram of interaction of a network system in which an embodiment of a message processing method provided by the present application is applied;

[0014] 3 is a diagram of a network system architecture in which the first service message in the service message processing method provided by the present application is an IPv4 message;

[0015] 4 is a diagram of a network system architecture in which the first service message in the service message processing method provided by the present application is an IPv6 message;

[0016] FIG5 is a flow chart of the service message processing method provided in the present application applied to the first network node;

[0017] FIG6 is a flow chart of the service message processing method provided in the present application applied to the second network node;

[0018] 7 is a schematic diagram of a service processing flow in the uplink direction of a service message processing method provided by the present application;

[0019] FIG8 is a schematic diagram of a business processing flow in the downlink direction of a business message processing method provided by the present application;

[0020] FIG9 is a schematic block diagram of the hardware structure corresponding to the service message processing method provided in this application. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solutions and advantages of this application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the embodiments described herein are only used to explain this application and are not intended to limit this application.

[0022] It should be noted that although the device schematics illustrate functional module divisions and the flowcharts illustrate logical sequences, in certain circumstances, the steps shown or described may be performed in a sequence that differs from the module divisions in the device or the sequence in the flowcharts. The terms "first," "second," and so on, in the specification, claims, and drawings, are used to distinguish similar items and are not necessarily used to describe a specific sequence or precedence.

[0023] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0024] When accessing the network, if the access point is far from the server, network delay, network freeze and packet loss are likely to occur; or during peak hours, the increase in access volume will increase the probability of network congestion, thereby reducing the user experience. Although in related technologies, in order to solve the problems of network delay and service congestion, dedicated lines are usually created for services with higher service quality to redirect service messages that require higher service quality to accelerated channel processing, in actual applications, the same service exists across networks, that is, the network system for service transmission is composed of networks maintained by multiple different managers, such as the access point in the network managed by the operator and the server in the network not managed by the operator such as the enterprise. Therefore, when providing a higher quality user experience, the entire network system needs to meet the following three requirements: (1) identify the service type, (2) use specific channels for the outbound and return of the service, and (3) try to avoid or have fewer protocol extensions. In response to the above problems, the industry has proposed an APN (Application-aware Networking) solution to solve this problem, but it requires both the access end and the server end to be able to identify the APN service layer identifier, which makes it not feasible. For example, taking the game service as an example, the APN service layer is added to the game terminal to carry the identifier of the game service, but the APN service layer identifier needs to be recognized on the opposite game server side. However, the game server is owned by the game content manufacturer and does not fall under the management of the operator. Therefore, the protocol extension solution brought by the APN non-standard technology is not feasible. Therefore, the message processing method of the service message in the related technology cannot meet the above three requirements to provide a higher quality user experience. Therefore, there is an urgent need for a message processing method that can realize the transmission of specific services through a specific path in a network system that exists across networks. Based on this, the embodiment of the present application provides a message processing method, an electronic device and a storage medium that can realize the transmission of specific services through a specific path in a network system that exists across networks.

[0025] It should be noted that this application is based on the standard SRv6 (Segment Routing) technology expansion to add a network programming SID to solve the above problem. The Binding SID currently used in relevant standards cannot solve this problem. The reason is that the role of the Binding SID is to carry the Binding SID information at the network head node. After the tail node receives this Binding SID, it will be associated with a series of Segment lists. This series of Segment lists can be associated with the return path of the message. At the same time, the Binding SID can reduce the data overhead carried by the Segment list. However, in the scenario of a cross-network system, taking the cross-network system consisting of an operator network and a game content provider network as an example, after the network tail node corresponding to the Binding SID receives the corresponding SRH message at the operator, the message needs to continue to be forwarded to the game content provider network outside the operator's management. When the game content provider network re-encapsulates the data message and sends it again from the Binding SID network to the network tail node of the operator network, the network tail node has no way of identifying whether this message belongs to a game business message that needs to be accelerated. Therefore, the embodiment of the present application improves the network programming SID to solve the service quality problem across networks in the same network system.

[0026] The following are the Chinese and English definitions of the fields in the IPV4 and IPV6 messages in the embodiments of this application.

[0027] The following is an explanation of the nouns and terms involved in the embodiments of this application.

[0028] Edge nodes, also known as Edge code, are located in the aggregation layer.

[0029] The core node, also known as the Core code, is located in the core layer. The core layer is the hub of the network and is used to achieve optimized transmission between backbone networks.

[0030] SR, or Segment Routing, is a type of source routing technology.

[0031] SRv6 is the application of SR technology to the IPv6 network plane. SRv6 forwards packets based on native IPv6. SRv6 implements this by extending the packet header, without changing the original IPv6 packet encapsulation structure. SRv6 packets remain IPv6 packets and can be recognized by standard IPv6 devices. SRv6 technology adds the Segment Routing Header (SRH) to IPv6 packets to store a list of SRv6 SIDs (segment IDs) in the format of 128-bit IPv6 addresses. As shown in Table 1, the 128-bit SRv6 SID consists of three main parts: the locator field, the function field, and the argument field. The locator field is primarily used for path planning, the function field is used to define the application, and the argument field is used to define application parameters. A standard SRv6 SID defines the path information, services, and functions of a specific node.

[0032] Table 1

[0033] Among them, the basic features of SRv6 include: SID is routable and node path and functional service information can be defined simultaneously through SID.

[0034] SRv6 extends the Routing Header definition in the IPv6 standard RFC2460, adding a new Segment Routing Header (SRH) to include the SID. As shown in Table 2 below, a value of 43 in the Next Header field (i.e., the Next Header field) in the IPv6 header indicates that the lower-layer header is a Routing Extension Header. A value of 4 in the Routing Extension Header indicates that the Routing Extension Header is a Segment Routing Header (SRH).

[0035] Table 2

[0036] Among them, Segment list[0] represents the last segment, and Segment list[N] represents the first segment.

[0037] It is understandable that the message processing method provided in the embodiments of the present application can be applied to the network system shown in Figure 1. As shown in Figure 1, the network system includes a first network and a second network, and the first network includes a first network node and a second network node. The second network is used to deploy cross-network content source nodes, and the second network node is used to connect to the cross-network content source nodes and receive return messages transmitted by the cross-network content source nodes.

[0038] In which, the first network node receives a first service message; when the first service message carries a first service type identifier, the first network node performs SRH header extension encapsulation on the first service message to obtain a second service message, wherein the segment list Segment list[0] in the SRH header of the second service message carries a specific SID associated with the first service type identifier; the first network node sends a second service message to the second network node, so that the second network node performs return message association-related operations according to the specific SID; the second network node receives the second service message, and when the SL (Segment Left) value in the SRH header of the second service message is 0 and the Segment list[0] in the SRH header carries a specific SID, the second network node generates a return session table, wherein the return session table is used to indicate the diversion strategy corresponding to the return message associated with the second service message. The second network node receives the fourth service message (i.e., the return message) sent by the second network, and obtains an association identifier from the fourth service message; the second network node determines the return session table corresponding to the fourth service message based on the correspondence between the association identifier and the return session table, so as to transmit the fourth service message from the specific return path corresponding to the return session table to the corresponding first network node through the corresponding return session table.

[0039] It should be noted that the first network node described in the embodiment of the present application may be the edge node in Figure 1, and the second network node may be the core node in Figure 1. The first network node is deployed with an outbound traffic diversion strategy; the second network node is deployed with a return traffic diversion strategy. In some embodiments, the network system further includes a controller to implement dynamic configuration of the outbound traffic diversion strategy and the return traffic diversion strategy. In other embodiments, the network system further includes a controller and an orchestrator, and the orchestrator is used for dynamic registration of services to establish associations with the outbound traffic diversion strategy and the return traffic diversion strategy configured by the controller; the configuration process is shown in Figure 2, and the steps are as follows.

[0040] Step 1: The controller pre-deploys the outbound SRv6 Policy (i.e., outbound traffic diversion policy) for different color services to the Edge Node.

[0041] Step 2: The controller pre-deploys the backhaul SRv6 Policy (i.e., backhaul traffic diversion policy) for different color services to the Core Node.

[0042] Step 3: The controller sends a service registration request to the orchestrator, carrying information such as the service head node, tail node, service level, and network QoS parameters.

[0043] Step 4: When the terminal device makes a service request / discovery, a specific service level deployment is given based on the head node, tail node, and corresponding QoS requirement information associated with the preset service level on the orchestrator.

[0044] Among them, information such as the service head node, tail node, service level, and network QoS parameters are shown in Table 3 below.

[0045] Table 3

[0046] Step 5: The terminal carries the service-level specific service identifier and sends the service message to the Edge Node for subsequent service-specific path selection and return-specific path binding processing.

[0047] It should be noted that in some embodiments, the first network is divided into multiple network layers, including a convergence layer and a core layer. The first network node is located in the convergence layer, and the second network node is located in the core layer. For example, as shown in Figure 1, the convergence layer is the convergence network shown in Figure 1. In some embodiments, to adapt to different types of messages sent by the access terminal, the convergence network also includes a BRAS device and a cloud resource pool (i.e., the cloud node shown in Figure 1); the BRAS device is used to generate user session table entries, and the cloud resource pool is used for specific service processing to form the first service message. In some embodiments, as shown in Figure 1, the core layer also includes a backbone network and a data center; the backbone network is used for backbone transmission, and the data center is used for redundancy backup.

[0048] It should be noted that the present application does not limit the type of the first service message. The first service message may be an IPv4 message as shown in FIG. 3 or an IPv6 message as shown in FIG. 4 .

[0049] It can be understood that, in the first aspect, as shown in FIG5 , the message processing method provided in accordance with the embodiment of the present application includes the following steps.

[0050] Step S110: The first network node receives a first service message.

[0051] Step S120: When the first service message carries the first service type identifier, the first network node performs SRH header extension encapsulation on the first service message to obtain a second service message, wherein the segment list Segment list[0] in the SRH header of the second service message carries a specific SID associated with the first service type identifier.

[0052] Step S130: The first network node sends a second service message to the second network node, so that the second network node performs backhaul message association-related operations according to a specific SID.

[0053] Therefore, by performing SRH header extension on the first service message carrying the first service type identifier, the first service message can be transmitted from a specific path to the second network node based on the SRv6 technology. When the second network node performs return message association-related operations according to the specific SID, the specific path of the return can also be determined based on the specific SID. Compared with the relevant technology, the embodiment of the present application retains the message format of the service message transmitted between the first network node and the second network node, so that the second network node can determine the path taken by the return and outbound messages based on the SID, thereby realizing the transmission of a specific path for the first service message carrying the first service type identifier, and meeting the business requirements of the first service message. Therefore, compared with the relevant technology, the embodiment of the present application can realize the transmission of a specific service via a specific path in a network system with cross-network.

[0054] It should be noted that the first service message can be either an IPv4 message or an IPv6 message, and those skilled in the art can selectively set it based on actual needs. The first service type identifier can be carried by DSCP or a flow label. For example, for IPv4 messages, it can be carried by DSCP; for IPv6 messages, it can be carried by DSCP or a flow label. Those skilled in the art can choose to carry the first service type identifier based on actual needs.

[0055] It should be noted that the second service message is an IPv6-based SRv6 message.

[0056] It should be noted that a forward traffic diversion strategy is configured on the first network node, and a return traffic diversion strategy is configured on the second network node. The first service type identifier and the forward traffic diversion strategy are set correspondingly, and the specific SID and the return traffic diversion strategy are set correspondingly. Therefore, the first network node can perform SRH header extension encapsulation when receiving the first service message carrying the first service type identifier, and the second network node can perform return message association-related operations based on the specific SID. At this time, the second network node does not need to identify the first service type identifier, and can also realize the return message from a specific path back to the first network node without protocol extension. It should be noted that the first network node is the source node of the forward traffic diversion strategy set in the forward traffic diversion strategy, and the second network node is the destination node in the forward traffic diversion strategy. The first network node and the second network node are in the same first network, and the first network node communicates with the network node located in the second network through the second network node, thereby realizing cross-network communication.

[0057] It should be noted that the first service type identifier is used to identify the transmission channel through which the message is transmitted. In some embodiments, the first service type identifier is defined as an accelerated service identifier to identify the required transmission channel as an accelerated channel. The SID is used by the destination node to determine whether it is the target node based on this identifier. For example, in some embodiments, the specific SID is set to End.ACC.

[0058] It should be noted that the return message association-related operation is used to identify whether to use the return traffic diversion strategy corresponding to the specific SID to process the fourth service message when the fourth service message sent by the second network is received.

[0059] It should be noted that Segment list[0] represents the last segment. The SID can be selectively set according to actual needs to identify whether it is necessary to enter the acceleration channel. Each SID is associated with a predetermined action to generate a return session table entry based on the return diversion strategy.

[0060] It can be understood that the first network node sends the second service message to the second network node, including: the first network node maps the second service message to the first SRv6 Policy path to transmit the second service message to the second network node through the first SRv6 Policy path; wherein, the first SRv6 Policy path is determined according to the source address and the first service type identifier corresponding to the first service message.

[0061] It should be noted that the first SRv6 Policy path is the transmission path specified in the outbound traffic diversion policy. The first node of the first SRv6 Policy path is the first network node, and the last node is the second network node. In some embodiments, the first SRv6 Policy path can be dynamically configured by the SDN controller.

[0062] It is understandable that after the first network node receives the first business message, the method also includes: the first network node determines the color value corresponding to the first business message based on the source address and the first service type identifier carried by the first business message; the first network node determines the outbound target diversion strategy corresponding to the first business message based on the correspondence between the color value and the outbound diversion strategy; the first network node determines the first SRv6 Policy path based on the outbound path indication information corresponding to the outbound target diversion strategy.

[0063] It should be noted that the first network node is configured with multiple outbound traffic diversion strategies to process service packets from different sources separately. Therefore, the first network node needs to determine the outbound target traffic diversion strategy to determine the first SRv6 Policy path.

[0064] It should be noted that in some embodiments, the outbound diversion strategy is configured based on the color value. Therefore, when the color value has a mapping relationship with the source address and the first service type identifier, the color value can be determined based on the source address and the first service type identifier, and then the outbound target diversion strategy can be determined based on the color value.

[0065] It should be noted that the outbound target diversion strategy includes outbound path indication information; the outbound path indication information is used to indicate the transmission path information, and therefore, the first SRv6 Policy path can be determined based on the outbound path indication information.

[0066] It is understandable that before the first network node receives the first service message, the method further includes: the first network node receives one or more outbound traffic diversion strategies issued by the controller, each outbound traffic diversion strategy having a corresponding color value and outbound path indication information.

[0067] It should be noted that, by sending the outbound traffic diversion policy through the controller, dynamic configuration of the outbound traffic diversion policy can be achieved. In some embodiments, the controller is an SDN controller.

[0068] It is understandable that after the first network node sends the second service message to the second network node, the method also includes: the first network node receives a third service message, wherein the third service message includes an SRH header; when the SL value in the SRH header of the third service message is 0, the first network node removes the SRH header of the third service message to obtain a return original service message; the first network node forwards the return original service message according to the destination address carried by the third service message.

[0069] It should be noted that an SL value of 0 indicates that the first network node is the return destination node of the third service message. The return original service message is forwarded to the network node corresponding to the destination address.

[0070] It should be noted that the return original service message can be in IPv4 format or IPv6 format.

[0071] It should be noted that the third service message is transmitted from the second network node to the first network node through the second SRv6 Policy path corresponding to the backhaul session table determined by the backhaul message association related operation.

[0072] It is understandable that the first service message is an IPv4 message, and the first service type identifier is located in the DSCP field of the first service message.

[0073] It is understandable that the first service message is an IPv6 message, and the first service type identifier is located in the DSCP field or the flow label field of the first service message.

[0074] It should be noted that the flow label field is also called flow label.

[0075] It can be understood that, in the second aspect, as shown in FIG6 , the message processing method provided in accordance with an embodiment of the present application includes the following steps.

[0076] Step S210: The second network node receives a second service message, where the second service message includes an SRH header.

[0077] Step S220: When the SL value in the SRH header of the second service message is 0 and the Segment list[0] in the SRH header carries a specific SID, the second network node generates a return session table, wherein the return session table is used to indicate the diversion strategy corresponding to the return message associated with the second service message.

[0078] Therefore, by performing SRH header extension on the first service message carrying the first service type identifier to obtain the second message, the second service message can be transmitted from a specific path to the second network node based on the SRv6 technology. When the second network node performs return message association-related operations according to the specific SID, the specific path of the return can also be determined based on the specific SID. Compared with the relevant technology, the embodiment of the present application retains the message format of the service message transmitted between the first network node and the second network node, so that the second network node can determine the path taken by the return and outbound messages based on the SID, thereby realizing the transmission of a specific path for the first service message carrying the first service type identifier, and meeting the business requirements of the first service message. Therefore, compared with the relevant technology, the embodiment of the present application can realize the transmission of a specific service via a specific path in a network system with cross-network.

[0079] It should be noted that the second service message is obtained by the first network node performing SRH header extension encapsulation on the first service message when receiving the first service message carrying the first service type identifier.

[0080] It should be noted that an SL value of 0 indicates that the second network node is the tail node of the outbound journey of the second service message.

[0081] It should be noted that an association is established between the specific SID and the return session table, so that when the second network node receives the fourth service message, it can determine whether there is a diversion strategy matching the fourth service message for return transmission based on the return session table.

[0082] It should be noted that the return session table can be associated with the return path. When the fourth service message (i.e., the return message) from the server node passes through the second network node, the second network node can associate it with the specific return path of the fourth service message based on the return session table.

[0083] It is understandable that the method of the embodiment of the present application also includes: the second network node removes the SRH header in the second service message to obtain the outbound original service message; the second network node forwards the outbound original service message according to the destination address carried by the second service message.

[0084] It should be noted that the outbound original service message must eventually be forwarded to the destination address.

[0085] It is understandable that after the second network node generates the backhaul session table, the method of the embodiment of the present application further includes: the second network node obtaining the association identifier from the second service message, and establishing a correspondence between the association identifier and the backhaul session table.

[0086] It should be noted that the backhaul session table is used to indicate the backhaul transmission channel between two fixed nodes, the first network node and the second network node, and the association identifier represents the source address in the outbound message. In some embodiments, the source address in the second service message is directly extracted as the association identifier. Therefore, by establishing a relationship between the association identifier and the backhaul session table, when a fourth service message is received, the service message can be transmitted based on the backhaul session table with the matching association identifier, depending on whether the fourth service message contains a matching association identifier.

[0087] It is understandable that the method of the embodiment of the present application also includes: the second network node receives the fourth business message from the server node, and obtains an association identifier from the fourth business message; the second network node determines the return journey session table corresponding to the fourth business message based on the correspondence between the association identifier and the return journey session table; the second network node determines the second SRv6Policy path based on the return journey path indication information in the return journey session table; the second network node performs SRH header extension encapsulation on the fourth business message according to the second SRv6 Policy path to obtain a third business message; and maps the third business message to the second SRv6Policy path to forward the third business message to the first network node through the second SRv6 Policy path.

[0088] It should be noted that the second SRv6 Policy path is the transmission path of the fourth service packet from the second network node to the first network node. The SRH header extension encapsulation requires the egress node to be specified. Therefore, the egress node is determined based on the second SRv6 Policy path for SRH header extension encapsulation.

[0089] Take the case where the association identifier is an address identifier. When constructing the return session table, the source address of the outbound message is used as the association identifier of the return session table. Then, for the fourth service message, when the fourth service message is a return message with the same source address, the destination address in the fourth service message is the source address, that is, the destination address in the fourth service message can be extracted as the association identifier to be verified. At this time, by comparing the outbound source address and the return destination address, the return session table associated with the outbound source address can be found; and then a second SRv6 Policy path is established in the return session table, and the SRH-encapsulated third service message is forwarded to the first network node through the second SRv6 Policy path.

[0090] Exemplarily, obtaining the association identifier from the second service message includes: obtaining the address identifier from a source address field of the second service message.

[0091] Exemplarily, obtaining the association identifier from the fourth service message includes: obtaining the address identifier from the destination address field of the fourth service message.

[0092] It is understandable that the method of the embodiment of the present application also includes: the second network node receives one or more backhaul diversion strategies issued by the controller, each backhaul diversion strategy has a corresponding color value and backhaul path indication information.

[0093] It should be noted that by configuring the backhaul traffic diversion policy for the second network node through the controller, dynamic configuration of the backhaul traffic diversion policy for the second network node can be achieved.

[0094] It is understandable that the second network node generates a return session table, including: the second network node determines the color value corresponding to the second service message based on the source address and specific SID carried by the second service message; the second network node determines the return target diversion strategy based on the correspondence between the color value and the return diversion strategy; the second network node generates a return session table based on the return path indication information corresponding to the return target diversion strategy.

[0095] It should be noted that by generating a backhaul session table, when multiple backhaul traffic diversion policies are configured, the corresponding second SRv6 Policy path can be quickly found through the backhaul session table.

[0096] It should be noted that when configuring the return traffic diversion strategy, the configuration is based on the color value. Therefore, the return target traffic diversion strategy can be determined based on the color value.

[0097] It should be noted that by binding the color value with the source address and a specific SID, service requirements of different businesses can be established.

[0098] Exemplarily, the first service type identifier is used for acceleration, the upstream direction is from the first network node to the second network node, and the downstream direction is from the second network node to the first network node. The fourth business message comes from the game server; the game server provides a cross-border content source as an example. With reference to Figures 7 and 8, the business processing flow of the message processing method of the present application is described as follows.

[0099] First, as shown in Figure 7, in the service upstream and downstream directions, the user sends a cross-border game message, which carries a specific service identifier through DSCP or Flow Label.

[0100] Secondly, as shown in Figure 7, in the uplink direction of the service, the first network node, as the source node, checks the data message sent by the trusted source (i.e., the first service message shown in Figure 1), parses the data message, and obtains the specific service identifier in the data message. If it is a service message that needs to be accelerated, the message that needs to be accelerated is mapped to the first SRv6 Policy path, and the last hop SID of the message encapsulation is End.ACC, which is used for backhaul acceleration channel identification and association.

[0101] 7 , the intermediate node located between the first network node and the second network node performs hop-by-hop parsing processing according to the Segment list based on the received SRH data message, and completes forwarding the SRH data message to the next hop.

[0102] Secondly, as shown in Figure 7, in the uplink direction of the service, the second network node, as the destination node, receives the SRH message carrying the last hop Segment list value of End.ACC, decapsulates the message and performs the End.ACC association operation, generates a return session table associated with the second downstream SRv6 Policy path, completes the SRH message header stripping, and forwards the message to the next hop.

[0103] For example, as shown in Figure 8, in the downlink direction, the return message sent by the cross-border content source, the second network node acts as the source node in the downlink direction. The source node checks the data return message sent by the game content source (that is, the cross-border content source), parses the data return message, and queries whether the destination of the data return message matches the return session table information. If it matches, the message to be accelerated is mapped to the second SRv6 Policy path; if it does not match, it is forwarded normally according to the pre-configured routing policy. When it matches, the source node adds an SRH message header to the data return message and performs insulation encapsulation according to the Segment list configured by the second SRv6 Policy.

[0104] 8 , in the downlink direction, the intermediate node between the first network node and the second network node performs hop-by-hop parsing of the received SRH data message according to the Segment list to complete forwarding the SRH data message to the next hop.

[0105] 8 , in the downlink direction, the first network node, as the destination node, receives the SRH data message, completes the second SRv6 Policy function, completes SRH message header stripping, and forwards the message to the next hop.

[0106] For example, in combination with Figure 3, taking the first business message in IPv4 format, the first network as the operator network, the second network as the network managed by the game service provider, and the game server set in the second network as an example, the processing flow of the message processing method in this application in the network system is described as shown in Figure 2.

[0107] In step 1, a cross-network user sends a request to join the game. The BRAS device generates a user session table entry for the game user and forwards the traffic to the cloud resource pool (i.e., the Cloud Node in the converged network shown in Figure 3) for cross-network game-specific service processing.

[0108] In step 2, the cloud node encapsulates the cross-network gaming service message into an IPv4 payload, carrying the local cloud node's IPv4 address as the source address and the cross-network content source's IPv4 address as the destination address. The DSCP value is set to a specific value, and the message is sent to the network edge node for processing. The message encapsulation structure is shown in Table 4.

[0109] Table 4

[0110] Step 3: Based on the BGP-FS traffic diversion policy issued by the controller, the policy content matches the source address segment and the ServiceLevel of the DSCP field, and the action is to import the corresponding Policy+END.ACC. After receiving this cross-network gaming service message, the Edge Node parses the IPv4 message structure to determine whether it is sent from the cloud resource pool and whether the DSCP value is a cross-network service-specific value. If so, it maps the message to the first SRv6 Policy path.

[0111] When the Edge Node performs message encapsulation, it needs to add the SRH message header and encapsulate a series of Segment lists. The Segment list[0] information of the last hop of the SID is End.ACC, which is used to associate the return path of the cross-network game service. The message encapsulation is shown in Figure 5.

[0112] Table 5

[0113] The DSCP identifier processing process is shown in Table 4, and the table entry matching method is as follows.

[0114] Step 1: Check whether the source address of the message is the IP address of a trusted cloud computer. If it is, jump to step 2; otherwise, jump to step 5.

[0115] Step 2: Read the ServiceLevel from the DSCP field of the message; jump to step 3.

[0116] Step 3: Determine whether an entry matching the ServiceLevel is found in the SRv6 Policy list. If a matching entry is found, jump to step 4; otherwise, jump to step 5.

[0117] Step 4: Import the message into the policy.

[0118] Step 5: Other forwarding processes.

[0119] Step 4: After receiving the cross-network game service message, the intermediate node Transit Node parses the SRH message header in the message and forwards the message to the next hop according to the SID in the message.

[0120] In step 5, after receiving the uplink cross-network gaming service message from the Edge Node, the destination Core Node decapsulates the received SRv6 message and resolves the last hop of the SID to End.ACC. It needs to perform the specific action corresponding to End.ACC and generate a cross-network gaming service backhaul session table for mapping the backhaul service message to the second SRv6 Policy path, thereby accelerating the processing of cross-network gaming-related services.

[0121] The destination node strips the SRH message header from the message, and forwards the message to its destination IPv4 address, ie, the cross-network content source, according to the service IPv4 message header encapsulation information.

[0122] Step 6: The cross-network content source sends a return message. After reaching the Core Node, the IPv4 message header is parsed. After the destination IPv4 address is parsed to be the IPv4 address of the cloud resource pool device, a cross-network game service return session table query is performed. After the query matches, a return service specific path is selected and mapped to the second SRv6 Policy path.

[0123] After receiving the SRH message header, the Edge Node determines that it is an SRv6 Policy tail node, strips off the SRH message header, and forwards the service message to the game user.

[0124] For example, in combination with Figure 4, taking the first business message in IPv6 format, the first network being the operator network, the second network being the game network, and the first business message being the game message as an example, the processing flow of the message processing method in this application in the network system is described, as shown in Figure 4.

[0125] In step 1, a cross-border game user (i.e., the user terminal shown in FIG4 ) sends a request to join the game. The BRAS device generates a user session entry for the game user, and the traffic is forwarded to the cloud resource pool for cross-border game-specific service processing.

[0126] In step 2, the cloud resource pool node encapsulates the cross-border gaming service message into the payload of an IPv6 message, carries the IPv6 address of the local cloud resource pool as the source address and the IPv6 address of the cross-domain content source as the destination address, sets the DSCP to a specific value, and sends the message to the network Edge Node for processing. Unlike the embodiment shown in Figure 3, the IPv6 message can carry the user service identifier via DSCP or flow label. The format of the IPv6 message carrying the first service type identifier via DSCP is shown in Table 6, and the format of the IPv6 message carrying the first service type identifier via flow label is shown in Table 7.

[0127] Table 6

[0128] Table 7

[0129] In step 3, after detecting the DSCP user service identifier carried in the IPv6 packet, the Edge Node executes the DSCP processing process described in Example 2. If the Flow Label user service identifier carried in the IPv6 packet is detected, the Edge Node performs the following Flow Label processing; referring to Table 7, the outbound Flow Label table entry matching method is as follows.

[0130] Step 1: Check whether the source address of the message is the IP address of a trusted cloud computer; if it is confirmed to be the IP address of a trusted cloud computer, jump to step 2; otherwise, jump to step 5.

[0131] Step 2: Read the ServiceLevel from the Flow Label field of the message; jump to step 3.

[0132] Step 3: Determine whether a matching entry is found in the ServiceLevel list of the SRv6 Policy. If a matching entry is found, jump to step 4. If not, jump to step 5.

[0133] Step 4: Import the message into the policy.

[0134] Step 5: Other forwarding processes.

[0135] The controller issues a BGP-FS traffic diversion policy. The policy content matches the source address segment, DSCP, or ServiceLevel in the Flow Label field. The action is to strip the outer IPv6 packet and redirect the inner original packet to the corresponding Policy+END.ACC.

[0136] Steps 4 to 6 are the same as the IPv4 processing method in the example of FIG2 , except that IPv4 is replaced by IPv6, and will not be described in detail here.

[0137] Therefore, in conjunction with Figures 7 and 8, the backhaul discovery network programming function SID defined in this application is associated with a specific table writing action for backhaul specific path association.

[0138] 1) The destination node of the SRv6 Policy upstream path (from the user to the game server) newly defines a backhaul discovery network programming function SID (such as End.ACC) to identify the backhaul path association of the backhaul service message.

[0139] 2) The backhaul discovery network programming function SID needs to be associated with the underlying table writing action to generate a session table entry that associates the game service with the second SRv6 Policy.

[0140] 3) The SRv6 Policy uplink path is the first SRv6 Policy path, and the SRv6 Policy destination node SID needs to be specified as the backhaul discovery network programming function SID.

[0141] 4) The SRv6 Policy upstream path source node needs to add an SRH data message header for message encapsulation, carrying the last hop Segment list[0] information as the return discovery network programming function SID.

[0142] 5) After the downlink service message (from the game server to the user) reaches the destination node of the first SRv6 Policy uplink path, it needs to parse the message and query the session table entry associated with the user and the second SRv6 Policy. If a match is found, the second SRv6 Policy path is associated and the service message is forwarded; if a match is found, other conventional forwarding is performed.

[0143] It is understandable that, as shown in Figure 9, an embodiment of the present application also provides an electronic device, including: one or more processors 101; a memory 102, on which one or more programs are stored, and when the one or more programs are executed by the one or more processors 101, the one or more processors 101 implement: a message processing method as applied to a first network node; or a message processing method as applied to a second network node.

[0144] The memory 102 is a non-transient network system that can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory 102 may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 102 may optionally include a memory 102 remotely located relative to the processor 101, and these remote memories 102 may be connected to the processor 101 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0145] The memory 102 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 102 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 102 and is called by the processor 101 to execute the methods of the embodiments of this application.

[0146] The processor 101 can be implemented using a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0147] In some embodiments, as shown in Figure 9, the electronic device also includes: an input / output interface for realizing information input and output; a communication interface for realizing communication interaction between the device and other devices, and communication can be realized through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.); a bus for transmitting information between various components of the device (such as processor 101, memory 102, input / output interface and communication interface); wherein the processor 101, memory 102, input / output interface and communication interface can realize communication connection with each other within the device through the bus.

[0148] An embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions for executing: a message processing method as applied to a first network node; or a message processing method as applied to a second network node.

[0149] An embodiment of the present application also provides a computer program product, including a computer program or computer instructions, which are stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, so that the computer device performs: a message processing method as applied to a first network node; or a message processing method as applied to a second network node.

[0150] The system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0151] Those skilled in the art will appreciate that all or some of the steps and systems in the method disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, and the computer-readable medium can include computer storage media (or non-transitory media) and communication media (or temporary media). As known to those skilled in the art, the term computer storage media is included in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data) and is volatile and non-volatile, removable, and non-removable. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0152] The above description of some embodiments of the present application with reference to the accompanying drawings does not limit the scope of the present invention. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present invention shall be within the scope of the present application.

Claims

1. A message processing method, the method comprising the following steps: The first network node receives a first service message; In the case where the first service message carries the first service type identifier, the first network node performs SRH header extension encapsulation on the first service message to obtain a second service message, wherein the segment list Segment list[0] in the SRH header of the second service message carries a specific SID associated with the first service type identifier; The first network node sends the second service message to the second network node, so that the second network node performs a backhaul message association-related operation according to the specific SID.

2. The method according to claim 1, wherein: The first network node sending the second service message to the second network node includes: The first network node maps the second service message to a first SRv6 Policy path to transmit the second service message to the second network node through the first SRv6 Policy path; wherein the first SRv6 Policy path is determined according to the source address corresponding to the first service message and the first service type identifier.

3. The method according to claim 2, wherein: After the first network node receives the first service message, the method further includes: The first network node determines, according to the source address and the first service type identifier carried by the first service message, a color value corresponding to the first service message; The first network node determines, according to the correspondence between the color value and the outbound traffic diversion strategy, an outbound target traffic diversion strategy corresponding to the first service message; The first network node determines a first SRv6 Policy path according to the outbound path indication information corresponding to the outbound target traffic diversion strategy.

4. The method according to claim 3, wherein: Before the first network node receives the first service message, the method further includes: The first network node receives one or more outbound traffic diversion strategies issued by the controller, each of the outbound traffic diversion strategies having a corresponding color value and outbound path indication information.

5. The method according to claim 1, wherein: After the first network node sends the second service message to the second network node, the method further includes: The first network node receives a third service message, wherein the third service message includes an SRH header; When the SL value in the SRH header of the third service message is 0, the first network node removes the SRH header of the third service message to obtain a backhaul original service message; The first network node forwards the return original service message according to the destination address carried by the third service message.

6. The method according to claim 1, wherein: The first service message is an IPv4 message, and the first service type identifier is located in a DSCP field of the first service message.

7. The method according to claim 1, wherein: The first service message is an IPv6 message, and the first service type identifier is located in a DSCP field or a flow label field of the first service message.

8. A message processing method, the method comprising the following steps: The second network node receives a second service message, wherein the second service message includes an SRH header; When the SL value in the SRH header of the second service message is 0 and the Segment list[0] in the SRH header carries a specific SID, the second network node generates a return session table, wherein the return session table is used to indicate the diversion strategy corresponding to the return message associated with the second service message.

9. The method according to claim 8, wherein: The method further comprises: The second network node removes the SRH header in the second service message to obtain an outbound original service message; The second network node forwards the outbound original service message according to the destination address carried by the second service message.

10. The method according to claim 8, wherein: After the second network node generates the backhaul session table, the method further includes: The second network node obtains an association identifier from the second service message, and establishes a corresponding relationship between the association identifier and the backhaul session table.

11. The method according to claim 10, wherein: The method further comprises: The second network node receives a fourth service message from the server node, and obtains an association identifier from the fourth service message; The second network node determines the backhaul session table corresponding to the fourth service message according to the correspondence between the association identifier and the backhaul session table; The second network node determines a second SRv6 Policy path according to the backhaul path indication information in the backhaul session table; The second network node performs SRH header extension encapsulation on the fourth service message according to the second SRv6 Policy path to obtain a third service message; Map the third service message to the second SRv6 Policy path to forward the third service message to the first network node through the second SRv6 Policy path.

12. The method according to claim 11, wherein: The association identifier is an address identifier; The acquiring the association identifier from the second service message comprises: acquiring the address identifier from a source address field of the second service message; The acquiring the association identifier from the fourth service message includes: acquiring the address identifier from a destination address field of the fourth service message.

13. The method according to claim 11, wherein: The method further comprises: The second network node receives one or more return traffic diversion strategies sent by the controller, each of the return traffic diversion strategies having a corresponding color value and return path indication information.

14. The method according to claim 13, wherein: The second network node generates a backhaul session table, including: The second network node determines, according to the source address and the specific SID carried by the second service message, a color value corresponding to the second service message; The second network node determines the backhaul target traffic diversion strategy according to the correspondence between the color value and the backhaul traffic diversion strategy; The second network node generates the backhaul session table according to the backhaul path indication information corresponding to the backhaul target traffic diversion strategy.

15. An electronic device, comprising: one or more processors; A memory having one or more programs stored thereon, when the one or more programs are executed by the one or more processors, the one or more processors implement: The message processing method according to any one of claims 1 to 7; or, A message processing method as described in any one of claims 8 to 14.

16. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the program implements: The message processing method according to any one of claims 1 to 7; or, A message processing method as described in any one of claims 8 to 14.

Images