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

Abstract

This disclosure relates to the field of network communication technology, and in particular provides a message processing method, apparatus, electronic device, storage medium, and program product. The message processing method is applied to a cloud gateway forwarding plane node based on Vector Packet Processing (VPP), and includes: in response to detecting that the type of the uplink inner packet is an Address Resolution Protocol (ARP) request packet, adjusting the ingress interface of the uplink inner packet to the uplink physical interface, wherein the uplink inner packet corresponds to the original packet sent by the terminal; pointing the next processing node of the uplink inner packet to an ARP proxy node in the cloud gateway forwarding plane node; and generating an ARP proxy response packet corresponding to the uplink inner packet based on the uplink physical interface through the ARP proxy node. This method, by implementing ARP packet proxy processing locally on the cloud gateway forwarding plane, can reduce the processing complexity and resource consumption of the cloud gateway forwarding plane, and improve message forwarding efficiency.

Description

Technical Field

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

[0002] To provide a computing power network that meets usage requirements, a cloud gateway can be deployed within the network architecture. The cloud gateway can be deployed as a network element after the Broadband Remote Access Server (BRAS) in the corresponding data center. In this network architecture, to achieve Layer 2 and Layer 3 convergence at the forwarding layer, the binding between the Virtual Extensible Local Area Network (VXLAN) tunnel and the Bridge Domain is removed. This causes the cloud gateway's forwarding plane node to be unable to complete ARP proxying through the Address Resolution Protocol (ARP) table entries configured in the Bridge Domain. Therefore, the identified ARP packets need to be reported to the cloud gateway's control plane node for processing. This impacts the forwarding efficiency of normal service packets. Summary of the Invention

[0003] This disclosure is made in view of the above-mentioned problems. This disclosure provides a message processing method, a message processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product.

[0004] According to one aspect of this disclosure, a message processing method is provided, applied to a cloud gateway forwarding plane node based on Vector Packet Processing (VPP). The method includes: in response to detecting that the type of an uplink inner message is an Address Resolution Protocol (ARP) request message, adjusting the ingress interface of the uplink inner message to an uplink physical interface, wherein the uplink inner message corresponds to the original message sent by the terminal; pointing the next processing node of the uplink inner message to an ARP proxy node in the cloud gateway forwarding plane node; and generating an ARP proxy response message corresponding to the uplink inner message based on the uplink physical interface through the ARP proxy node.

[0005] Furthermore, according to one aspect of the message processing method of this disclosure, the message processing method may further include: configuring an Internet Protocol IP address range to be proxied for the uplink physical interface; and generating an ARP proxy response message corresponding to the uplink inner message through the ARP proxy node based on the uplink physical interface, including: in response to determining that the target Internet Protocol IP address in the uplink inner message belongs to the IP address range to be proxied, generating an ARP proxy response message through the ARP proxy node.

[0006] Furthermore, according to one aspect of the message processing method of this disclosure, the message processing method may further include: receiving an uplink Virtual Extended Local Area Network (VXLAN) message corresponding to the original message; and removing the outer VXLAN encapsulation of the VXLAN message to obtain an uplink inner message.

[0007] Furthermore, according to one aspect of the message processing method of this disclosure, the message processing method may further include: parsing the outer VXLAN encapsulation of the VXLAN message to obtain the network identifier (VNI) information; and storing the VNI information into the message structure of the VXLAN message.

[0008] Furthermore, according to one aspect of the message processing method of this disclosure, the message processing method may further include: determining the outgoing interface of the ARP proxy response message based on the VNI information stored in the message structure; and adjusting the outgoing interface of the ARP proxy response message to the user VXLAN virtual interface.

[0009] Furthermore, according to one aspect of the message processing method of this disclosure, the above message processing method may further include: pointing the next processing node of the ARP proxy response message to the VXLAN encapsulation node in the cloud gateway forwarding plane node; adding an outer VXLAN encapsulation to the ARP proxy response message based on the user's VXLAN virtual interface through the VXLAN encapsulation node; and sending the encapsulated downlink VXLAN message to the terminal.

[0010] According to another aspect of this disclosure, a message processing apparatus is provided for a cloud gateway forwarding plane node based on Vector Packet Processing (VPP). The apparatus includes an adjustment module, a processing module, and a generation module. The adjustment module is configured to adjust the ingress interface of the uplink inner packet to the uplink physical interface in response to detecting that the type of the uplink inner packet is an Address Resolution Protocol (ARP) request packet, wherein the uplink inner packet corresponds to the original packet sent by the terminal. The processing module is configured to point the next processing node of the uplink inner packet to an ARP proxy node in the cloud gateway forwarding plane node. The generation module is configured to generate an ARP proxy response packet corresponding to the uplink inner packet based on the uplink physical interface through the ARP proxy node.

[0011] According to one aspect of this disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and, when executed by the at least one processor, the instructions are capable of implementing any of the message processing methods described above.

[0012] According to one aspect of this disclosure, a non-transitory computer-readable storage medium is provided for storing computer-readable instructions that, when executed by a computer, cause the computer to perform any of the message processing methods described above.

[0013] According to one aspect of this disclosure, a computer program product including a computer program is provided, which, when executed by a processor, causes the processor to perform any of the message processing methods described above.

[0014] As will be described in detail below, in the message processing method of this disclosure embodiment, when the cloud gateway forwarding plane node based on VPP detects or obtains the decapsulated uplink inner message corresponding to the original message sent by the terminal, the type of the uplink inner message can be determined. If it is determined that the type of the uplink inner message is an ARP request message, its ingress interface is adjusted to an uplink physical interface, so that its ingress interface is switched from the current interface to a physical entity interface with actual proxy capabilities. The next processing node of the uplink inner message is pointed to the ARP proxy node inside the cloud gateway forwarding plane node, so as to guide the uplink inner message into the local message proxy processing flow of the cloud gateway forwarding plane. That is, the ARP proxy node directly realizes the reply to the ARP request message based on the uplink physical interface, i.e., generates an ARP proxy response message. This allows ARP request packets to be answered directly in the cloud gateway forwarding plane without having to go through the cloud gateway control plane. This eliminates the need for deep parsing of ARP request packets, reducing the processing complexity and resource consumption of the cloud gateway forwarding plane. At the same time, since the ARP proxy logic is implemented in the cloud gateway forwarding plane, the dependence on the cloud gateway control plane is reduced, alleviating the pressure on the cloud gateway control plane, thereby improving packet forwarding efficiency and network configuration flexibility.

[0015] It should be understood that both the foregoing general description and the following detailed description are exemplary and intended to provide further illustration of the claimed technology. Attached Figure Description

[0016] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of the embodiments thereof in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the embodiments of this disclosure to explain the disclosure and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.

[0017] Figure 1 This is a schematic diagram of a cloud gateway architecture.

[0018] Figure 2This is a flowchart illustrating a message processing method according to an embodiment of the present disclosure.

[0019] Figure 3 This is a flowchart illustrating a message processing method according to another embodiment of the present disclosure.

[0020] Figure 4 This is a flowchart illustrating a message processing method in an application scenario according to an embodiment of the present disclosure; Figure 5 This is a block diagram illustrating a message processing apparatus according to an embodiment of the present disclosure.

[0021] Figure 6 This is a hardware block diagram illustrating an electronic device according to an embodiment of the present disclosure.

[0022] Figure 7 This is a schematic diagram illustrating a computer-readable storage medium according to an embodiment of the present disclosure. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of this disclosure more apparent, exemplary embodiments according to this disclosure will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this disclosure, and not all embodiments of this disclosure. It should be understood that this disclosure is not limited to the exemplary embodiments described herein.

[0024] To build network infrastructure that meets the demands of high-efficiency computing power, cloud gateways are currently being introduced into the network architecture of related technologies. For example... Figure 1 The network architecture 100 shown depicts a cloud gateway deployed in a corresponding data center as a network element following the BRAS. In this architecture, user access is typically achieved through VXLAN tunneling technology. Each home gateway's Optical Network Unit (ONU) establishes a unique VXLAN tunnel with the cloud gateway. The original packets from user terminals (such as PCs and mobile phones) are encapsulated with a VXLAN tunnel header at the ONU and forwarded to the cloud gateway via the Optical Line Terminal (OLT) and BRAS. Upon receiving a VXLAN packet, the cloud gateway decapsulates the packet to obtain the inner original packet and performs appropriate routing, forwarding, or other processing based on the packet type.

[0025] In the aforementioned network architecture, to achieve Layer 2 and Layer 3 convergence at the forwarding layer, the binding relationship between the VXLAN tunnel and the Bridge Domain is removed. This prevents the cloud gateway forwarding plane node from directly answering user ARP requests by configuring ARP entries in the Bridge Domain. Therefore, a roundabout processing path is required: when the cloud gateway forwarding plane node identifies the decapsulated inner packet as an ARP request, it must send the request packet to the cloud gateway control plane node for processing via a separate control tunnel, such as the VNI 6000 tunnel. For example, in a cloud gateway scenario, the user's internet access process is as follows: (1) The home gateway initiates a Point-to-Point Protocol Over Ethernet (PPPOE) dial-up connection and obtains the Internet Protocol (IP) that can be accessed from the BRAS. (2) Use the IP obtained by PPPoE dialing as the local IP and the pre-allocated Virtual Networking Index (VNI) value to create a VXLAN tunnel between the cloud gateway; (3) When a user terminal, such as a mobile phone or PC, initiates a Dynamic Host Configuration Protocol (DHCP) request, it encapsulates a VXLAN tunnel, such as VNI100 or VNI100000, on the ONU and forwards it to the cloud gateway forwarding plane node. The VXLAN packet is decapsulated at the cloud gateway forwarding plane node and the inner original packet is recapsulated into a double-layer virtual local area network (802.1Q-in-802.1Q, QINQ) and a new VXLAN tunnel, such as VNI6000, and forwarded to the cloud gateway control plane node. The DHCP server of the control plane node assigns an internal network address to the user terminal and notifies the user terminal of the gateway, Domain Name System (DNS) information, etc. at the same time. (4) The user terminal initiates an Address Resolution Protocol (ARP) request to the cloud gateway. The message is passed through to the control plane node in the same way as in (3) above, and the cloud gateway control plane node responds with an ARP reply (REPLY). (5) When the user terminal accesses the Internet normally (including DNS), the message arrives at the cloud gateway and the policy routing determines whether it is a service that needs to be accelerated: For non-accelerated services, the public IP is used to perform Network Address Translation (NAT) and the public network is offloaded and forwarded; for accelerated services, the message is sent to the acceleration server and enters the acceleration network.

[0026] In the above process, the cloud gateway forwarding plane node needs to decapsulate the VXLAN tunnel, identify the user's uplink ARP packets, and perform deep parsing of the ARP packets. This includes identifying uplink and downlink packets, recording and maintaining the mapping relationship between the source Media Access Control (MAC) address and the user's VNI in the packets, and recapsulating the VXLAN tunnel before forwarding it to the control plane node. This increases the processing complexity of the forwarding plane node, consumes computing resources for processing normal service traffic, and thus affects the forwarding efficiency of normal service packets.

[0027] In the above process, the cloud gateway control plane node is configured on the VXLAN port of the Linux kernel. It utilizes the capabilities of the Linux kernel protocol stack to decapsulate VXLAN tunnels and respond to user ARP requests. Since the ARP response packets returned from the control plane node do not carry user VNI information, the forwarding plane node needs to establish and maintain a large-scale mapping table of terminal MAC addresses and user VNIs to accurately forward packets to the corresponding user tunnels. During uplink packets, the mapping between device MAC addresses and user VNIs is recorded in the table. During downlink packets, the cloud gateway forwarding plane receives and identifies ARP REPLY packets, looks up the user VNI using the destination MAC address, encapsulates the corresponding VXLAN tunnel, and sends the downlink packet to the home gateway corresponding to the VNI. Therefore, with tens of thousands of users accessing the network, the number of entries in this table can exceed one hundred thousand. Continuous addition, deletion, modification, and query operations consume considerable memory and computing resources, impacting the cloud gateway's forwarding capabilities.

[0028] In the above process, because the cloud gateway control plane node uses the Linux kernel protocol stack to reply to ARP requests, all users can only use the same gateway IP address. Otherwise, some users' ARP requests will not be responded to, reducing the flexibility of cloud gateway network configuration.

[0029] Therefore, a message processing solution that can improve message forwarding efficiency and the flexibility of cloud gateways is needed.

[0030] The message processing scheme of the present disclosure embodiments will now be described with reference to the accompanying drawings.

[0031] Figure 2 This is a flowchart illustrating a message processing method according to an embodiment of the present disclosure, such as... Figure 2 The flowchart 200, which illustrates the packet processing method applied to the forwarding plane node of a cloud gateway based on Vector Packet Processing (VPP), may include the following: Step 201: In response to the detection that the type of the uplink inner packet is an Address Resolution Protocol (ARP) request packet, the ingress interface of the uplink inner packet is adjusted to the uplink physical interface.

[0032] This step aims to ensure that, when the cloud gateway forwarding plane node based on VPP detects or receives an ARP request packet from a terminal (or user terminal), its ingress interface can be adjusted to the uplink physical interface to ensure subsequent processing of the ARP request packet at the cloud gateway forwarding plane level based on the VPP framework. This is achieved through the execution entity of the packet processing method. The VPP framework can refer to the high-performance user-space network packet processing framework used by the cloud gateway forwarding plane node, which enables high-speed packet processing and supports ARP. For example, the cloud gateway forwarding plane node can refer to a forwarding plane entity based on the VPP framework.

[0033] In one example embodiment of this disclosure, the implementation of adjusting the ingress interface of the aforementioned uplink inner layer message to the uplink physical interface includes, but is not limited to: modifying the value of the field in the message metadata that identifies its receiving interface, i.e., the ingress interface, from the current interface index to an index representing the uplink physical interface. For example, the uplink physical interface may refer to the physical network port on the cloud gateway forwarding plane node that connects to the upstream network.

[0034] In one example embodiment of this disclosure, the aforementioned uplink inner message is a decapsulated message corresponding to the original message sent by the terminal, or it can be understood that the uplink inner message is determined based on the original message.

[0035] In one example embodiment of this disclosure, the type of the uplink inner packet can be determined by querying the value of the Ethernet type field of the uplink inner packet. This is achieved by comparing the packet header information with predefined protocol features. Specifically, when the value of the Ethernet type field of the uplink inner packet is detected to be the value corresponding to that of an ARP request packet, the type of the uplink inner packet is determined to be an ARP request packet.

[0036] Step 202: Point the next processing node of the uplink inner layer message to the ARP proxy node in the cloud gateway forwarding plane node.

[0037] In this embodiment, the next processing node of the aforementioned uplink inner packet can be directed to the ARP proxy node through the ARP proxy node in the cloud gateway forwarding plane node. This allows for precise control of the processing flow of the uplink inner packet and the establishment of a fast ARP proxy channel locally on the cloud gateway forwarding plane node. This ensures that the ARP request packet can be accurately guided to the dedicated processing node, i.e., the ARP proxy node, thereby enabling efficient processing of the ARP request packet and avoiding unnecessary processing delays and overhead.

[0038] Step 203: Generate an ARP proxy response message corresponding to the uplink inner layer message through the ARP proxy node based on the uplink physical interface.

[0039] In this embodiment, after receiving the aforementioned uplink inner packet, the ARP proxy node can respond to the ARP request packet based on the aforementioned uplink physical interface, that is, generate an ARP proxy response packet corresponding to the uplink inner packet. In this way, the processing of the ARP request packet is implemented locally at the cloud gateway forwarding plane node, without the need for the cloud gateway forwarding plane node to forward it to the cloud gateway control plane node for processing.

[0040] In the message processing method of this disclosure embodiment, when the cloud gateway forwarding plane node based on VPP detects or obtains the decapsulated uplink inner message corresponding to the original message sent by the terminal, the type of the uplink inner message can be determined. If it is determined that the type of the uplink inner message is an ARP request message, its ingress interface is adjusted to an uplink physical interface, so that its ingress interface is switched from the current interface to a physical entity interface with actual proxy capabilities. The next processing node of the uplink inner message is pointed to the ARP proxy node inside the cloud gateway forwarding plane node, so as to guide the uplink inner message into the local message proxy processing flow of the cloud gateway forwarding plane. That is, the ARP proxy node directly realizes the reply to the ARP request message based on the uplink physical interface, i.e., generates an ARP proxy response message. This allows ARP request packets to be answered directly in the cloud gateway forwarding plane without having to go through the cloud gateway control plane. This eliminates the need for deep parsing of ARP request packets, reducing the processing complexity and resource consumption of the cloud gateway forwarding plane. At the same time, since the ARP proxy logic is implemented in the cloud gateway forwarding plane, the dependence on the cloud gateway control plane is reduced, alleviating the pressure on the cloud gateway control plane, thereby improving packet forwarding efficiency and network configuration flexibility.

[0041] Figure 3 This is a flowchart illustrating a message processing method according to another embodiment of the present disclosure, such as... Figure 3 The flowchart 300, which illustrates the packet processing method applied to the forwarding plane node of a VPP-based cloud gateway, may include the following: Step 301: Configure the IP address range to be proxied for the uplink physical interface.

[0042] This step aims to pre-configure the IP address ranges that need to be proxied by the uplink physical interfaces in the cloud gateway forwarding plane node, which is the execution body of this packet processing method and the aforementioned VPP-based cloud gateway forwarding plane node. This provides a precise policy basis for subsequent efficient and accurate ARP proxy responses. The IP address range can be one or more sets of IP addresses, either consecutive or non-consecutive. For example, when the cloud gateway forwarding plane node has multiple uplink physical interfaces, different IP address ranges to be proxied can be configured independently for each uplink physical interface to achieve differentiated services. For example, the mapping relationship between uplink physical interfaces and the IP address ranges to be proxied can be maintained in the form of an "interface-address range" mapping table, such as a hash table, and can be stored in the memory space of the cloud gateway forwarding plane node during runtime.

[0043] Step 302: In response to the detection that the type of the uplink inner packet is an Address Resolution Protocol (ARP) request packet, the ingress interface of the uplink inner packet is adjusted to the uplink physical interface.

[0044] Step 303: Point the next processing node of the uplink inner layer message to the ARP proxy node in the cloud gateway forwarding plane node.

[0045] Steps 302-303 above and as follows Figure 2 Steps 201-202 shown are the same; for the same parts, please refer to the corresponding parts of the previous embodiment, which will not be repeated here. Further, the above... Figure 2 Step 203 in the corresponding embodiment is in Figure 3 In the corresponding embodiment, step 304 can be specifically implemented as follows: In response to determining that the target Internet Protocol IP address in the uplink inner message belongs to the IP address range to be proxied, an ARP proxy response message is generated through the ARP proxy node.

[0046] In this embodiment, when the target IP address in the uplink inner packet falls within the pre-configured IP address range, the ARP proxy node generates an ARP proxy response packet for the ARP request packet, ensuring the accuracy and controllability of the ARP proxy behavior. For example, the target IP address in the uplink inner packet can refer to the network layer address that the terminal initiating the ARP request expects to resolve. Optionally, the field value corresponding to the target IP address can be extracted from the payload of the uplink inner packet.

[0047] In the message processing method of this embodiment, an IP address range to be proxied is pre-configured for the uplink physical interface corresponding to the aforementioned uplink inner message. When it is determined that the type of the uplink inner message is an ARP request message, its ingress interface is adjusted to the uplink physical interface configured with the IP address range to be proxied. This switches the ingress interface from the current interface to a physical entity interface with actual proxy capabilities. The next processing node for the uplink inner message is then directed to the ARP proxy node inside the cloud gateway forwarding plane node. This guides the uplink inner message into the local message proxy processing flow of the cloud gateway forwarding plane. Specifically, when the ARP proxy node verifies that the target IP address in the uplink inner message falls within the pre-configured IP address range, it directly responds to the ARP request message, generating an ARP proxy response message. This avoids unnecessary responses or erroneous proxying of addresses that should not be processed by the gateway, ensuring the accuracy and security of the ARP proxy response.

[0048] In the above Figure 2 or Figure 3 Based on the corresponding embodiments, in an example embodiment of this disclosure, the message processing method in any of the above embodiments may further include the following: receiving an uplink Virtual Extended Local Area Network (VXLAN) message corresponding to the original message; removing the outer VXLAN encapsulation of the VXLAN message to obtain an uplink inner message.

[0049] In this embodiment, when the cloud gateway forwarding plane node receives an encapsulated uplink VXLAN packet corresponding to the original packet sent by the terminal, in order to successfully perform an accurate ARP request reply operation locally on the cloud gateway forwarding plane node, it needs to decapsulate the packet from the terminal. That is, by removing the outer VXLAN encapsulation of the VXLAN packet, the original user data frame encapsulated inside and unchanged is obtained, which is the uplink inner packet.

[0050] In one example embodiment of this disclosure, the uplink VXLAN packet can be scheduled to a decapsulation node responsible for processing the VXLAN protocol in order to perform the decapsulation operation in accordance with the VXLAN protocol specification.

[0051] In an example embodiment of this disclosure, the process of adjusting the ingress interface of the aforementioned uplink inner layer message to the uplink physical interface can be performed as follows: since the uplink inner layer message originates from the decapsulation of the uplink VXLAN message sent by the terminal, the process can be performed as follows: adjusting the ingress interface of the uplink inner layer message, i.e., the virtual interface of the VXLAN tunnel, to the uplink physical interface.

[0052] In one example embodiment of this disclosure, the message processing method in any of the above embodiments may further include the following: parsing the outer VXLAN encapsulation of the VXLAN message to obtain the network identifier (VNI) information; and storing the VNI information in the message structure of the VXLAN message.

[0053] In this embodiment, during the process of the cloud gateway forwarding plane node performing decapsulation on the received uplink VXLAN packet, it is necessary to capture and retain its key Virtual Network Ownership Identifier (VNI) information while the glass packet transmission shell is being processed. The VNI information can be used to uniquely identify a specific VXLAN network segment, providing a reliable context for the subsequent tunneling backhaul processing. Furthermore, by storing the VNI information in the packet structure of the VXLAN packet, it can be ensured that the packet can be identified as having its original and accurate virtual network origin at any subsequent processing stage.

[0054] In one example embodiment of this disclosure, the message processing method in any of the above embodiments may further include the following: determining the outgoing interface of the ARP proxy response message based on the VNI information stored in the message structure; and adjusting the outgoing interface of the ARP proxy response message to the user VXLAN virtual interface.

[0055] In this embodiment, to ensure that the generated ARP proxy response message is accurately sent back to the requesting terminal, the outgoing interface of the ARP proxy response message needs to be adjusted to the VXLAN virtual interface based on the VNI information stored in the message structure. Thus, by directly using the VNI information carried in the message itself to determine the outgoing interface, the reliance on a large dynamic mapping table, such as the mapping table between MAC addresses and virtual network identifiers (VNI information), can be avoided. This eliminates the need to maintain the MAC-VNI mapping table used for accurate message forwarding, reducing the processing complexity of the cloud gateway forwarding plane nodes, the overhead of maintenance and queries, and resource consumption, saving memory space, thereby reducing forwarding plane memory consumption, simplifying processing logic, and increasing forwarding performance. Simultaneously, it enables stable and reliable ARP proxy response message delivery, ensuring that it is accurately delivered back to its source tunnel.

[0056] In one example embodiment of this disclosure, the outgoing interface of the ARP proxy response message can be determined by querying the "VNI-Virtual Interface" mapping table maintained by the system, such as a hash table, based on the VNI information.

[0057] In one example embodiment of this disclosure, the implementation of adjusting the outgoing interface of the ARP proxy response message to the user's VXLAN virtual interface includes, but is not limited to: modifying the value of the field in the message metadata that identifies its sending interface, i.e., the outgoing interface, from the current interface index to an index representing the user's VXLAN virtual interface.

[0058] In one example embodiment of this disclosure, the message processing method in any of the above embodiments may further include the following: pointing the next processing node of the ARP proxy response message to the VXLAN encapsulation node in the cloud gateway forwarding plane node; adding an outer VXLAN encapsulation to the ARP proxy response message based on the user's VXLAN virtual interface through the VXLAN encapsulation node; and sending the encapsulated downlink VXLAN message to the terminal.

[0059] In this embodiment, when the outgoing interface of the ARP proxy response message is successfully identified as the user's VXLAN virtual interface, in order to reliably return the response message to the user terminal, the ARP proxy response message can be encapsulated by the VXLAN encapsulation node in the cloud gateway forwarding plane node, which is used to implement tunnel encapsulation function. This allows the encapsulated downlink VXLAN message to be accurately sent to the terminal, while also improving the efficient utilization of network status by the cloud gateway forwarding plane node.

[0060] In one example embodiment of this disclosure, the message processing method in any of the above embodiments may further include the following: in response to detecting that the type of the uplink inner message is not the aforementioned ARP request message, then according to... Figure 1 The process shown performs message processing, executing the operation of generating ARP proxy response messages corresponding to the uplink inner layer messages by the cloud gateway control plane node.

[0061] To facilitate understanding, in a specific scenario, the processing of APR request messages is provided as follows: Figure 4 The packet processing method shown is implemented in a way that the cloud gateway uses the high-performance network forwarding framework Vector Packet Processing (VPP) as the forwarding plane, pre-configures the IP ranges to be proxied on the uplink physical interface, and enables the ARP proxy function. For example... Figure 4 As shown, process 400 may include the following: Step 401: The cloud gateway forwarding plane node based on VPP receives VXLAN packets.

[0062] Step 402: The cloud gateway forwarding plane node decapsulates the received VXLAN packets, removing the tunnel header to obtain the inner packet. Simultaneously, it records the received VNI information into the packet structure.

[0063] Step 403: The cloud gateway forwarding surface node determines whether the type of the inner packet is an ARP request packet. If so, proceed to step 404. Otherwise, for non-ARP packets, process them according to the predetermined process, such as performing a routing table lookup and determining the next hop of the packet based on the policy routing result, such as entering the public network forwarding path or guiding it to the accelerated network path. No specific restrictions are made here.

[0064] Step 404: Change the ingress interface of the packet to the uplink physical port, and point the next node to the ARP-PROXY node for processing.

[0065] Step 405: Determine if the ARP-PROXY proxy is successful. If it is, proceed to step 406; otherwise, proceed to step 407.

[0066] In this step, the ARP-PROXY node queries the configured proxy IP range based on the ingress interface information and compares it with the requested IP. If the requested IP is within the configured proxy IP range, an ARP REPLY packet is constructed, indicating that the proxy is successful; otherwise, if the requested IP is not within the configured proxy IP range, the proxy fails.

[0067] Step 406: Extract the ingress VNI information from the message structure, find the outgress interface, change the message outgress interface to the user VXLAN virtual interface, point the next node to the VXLAN encapsulation node (VXLAN-ENCAP), and perform operations such as encapsulating the tunnel header.

[0068] Furthermore, the ARP REPLY message is sent back to the user terminal through an encapsulated VXLAN tunnel.

[0069] Step 407: Discard the message.

[0070] In this implementation scheme, The cloud gateway uses the high-performance network forwarding framework Vector Packet Processing (VPP) as its forwarding plane. Leveraging VPP's ARPPROXY feature, it implements ARP proxy functionality for cloud gateway users' ARP packets on the forwarding plane. In a cloud gateway scenario, all user packets are encapsulated in VXLAN tunnels and sent to the forwarding plane. On traditional network devices, configuring the IP range to be proxied on the VXLAN virtual interface achieves ARP proxying. However, in a VPP environment, the VXLAN virtual interface does not have a MAC address, so enabling ARP proxying on the VXLAN interface is ineffective. Therefore, in this implementation, ARP proxying is enabled on the uplink physical interface. After the cloud gateway forwarding plane decapsulates the VXLAN tunnel and identifies the inner ARP packet, it modifies the packet's ingress interface to the uplink physical interface and designates the next processing node as the ARP-PROXY node. Utilizing the physical interface's ARP proxy capability, it constructs an ARP REPLY packet to directly reply to the user, thus achieving ARP packet proxying on the forwarding plane in the cloud gateway scenario. In this way, ARP requests from users are terminated at the cloud gateway forwarding plane. Leveraging the flexible and programmable nature of the Vector Packet Processing (VPP), ARP proxy capabilities are implemented at the cloud gateway forwarding plane. This allows for responses to user-sent Address Resolution Protocol (ARP) requests without needing to be sent to the control plane for processing, avoiding the performance overhead of sending ARP packets to the control plane, improving forwarding performance, enhancing flexibility, and reducing the pressure on the cloud gateway control plane. Simultaneously, by utilizing the ARP proxy functionality of the forwarding plane VPP, the processing logic and node order for ARP packets are optimized. Using physical ports for ARP proxying solves the limitation that VXLAN virtual ports cannot be configured with ARP proxies in cloud gateway scenarios. Furthermore, there is no need for the forwarding plane to record the mapping relationship between terminal MAC and VNI, saving memory space. The forwarding plane only needs to determine the ARP packet type based on the outer protocol, without needing deep parsing to distinguish uplink and downlink packets or hash lookups, reducing performance overhead and improving forwarding performance. Since it is no longer limited by the control plane kernel protocol stack, different gateway addresses can be assigned to different cloud gateway users as needed, providing greater flexibility.

[0071] Figure 5 This is a block diagram further illustrating a message processing apparatus according to an embodiment of the present disclosure. Figure 5 The packet processing apparatus 500 shown is applied to a cloud gateway forwarding plane node based on Vector Packet Processing (VPP) and can implement the packet processing method described above. The packet processing apparatus 500 can be implemented individually in hardware, individually in software, or in a combination thereof in various ways, and this disclosure is not limited to any of them; for example, it may specifically include a controller or a processor. The packet processing apparatus 400 according to embodiments of this disclosure can be deployed in various electronic devices.

[0072] like Figure 5As shown, the packet processing device 500 applied to the forwarding plane node of a cloud gateway based on vector packet processing (VPP) includes: an adjustment module 501, a processing module 502, and a generation module 503.

[0073] Specifically, the adjustment module 501 is configured to adjust the ingress interface of the uplink inner packet to the uplink physical interface in response to detecting that the type of the uplink inner packet is an Address Resolution Protocol (ARP) request packet, wherein the uplink inner packet corresponds to the original packet sent by the terminal; the processing module 502 is configured to point the next processing node of the uplink inner packet to the ARP proxy node in the cloud gateway forwarding plane node; and the generation module 503 is configured to generate an ARP proxy response packet corresponding to the uplink inner packet based on the uplink physical interface through the ARP proxy node.

[0074] In the embodiments of this disclosure, the specific processing of the adjustment module 501, processing module 502, and generation module 503 in the message processing apparatus 500, and the resulting technical effects, can be found in the following references. Figure 2 The relevant descriptions of steps 201-203 in the corresponding embodiments will not be repeated here.

[0075] In one example embodiment of this disclosure, the processing module 502 may be further configured to: configure the Internet Protocol IP address range to be proxied for the uplink physical interface; and the generation module 503 may be further configured to: generate an ARP proxy response message through the ARP proxy node in response to determining that the target Internet Protocol IP address in the uplink inner packet belongs to the IP address range to be proxied.

[0076] In one example embodiment of this disclosure, the above-mentioned message processing device 500 may further include a receiving module (not shown in the figure), configured to receive an uplink Virtual Extended Local Area Network (VXLAN) message corresponding to the original message; and the above-mentioned processing module 502 may further be configured to remove the outer VXLAN encapsulation of the VXLAN message to obtain an uplink inner message.

[0077] In one example embodiment of this disclosure, the processing module 502 may further be configured to: parse the outer VXLAN encapsulation of the VXLAN packet to obtain the network identifier (VNI) information; and store the VNI information in the packet structure of the VXLAN packet.

[0078] In one example embodiment of this disclosure, the processing module 502 may further be configured to: determine the outgoing interface of the ARP proxy response message based on the VNI information stored in the message structure; and adjust the outgoing interface of the ARP proxy response message to the user VXLAN virtual interface.

[0079] In one example embodiment of this disclosure, the message processing apparatus 500 may further include a sending module (not shown in the figure), wherein the processing module 502 may be further configured to: point the next processing node of the ARP proxy response message to the VXLAN encapsulation node in the cloud gateway forwarding plane node; add an outer VXLAN encapsulation to the ARP proxy response message based on the user's VXLAN virtual interface through the VXLAN encapsulation node; and the sending module is configured to: send the encapsulated downlink VXLAN message to the terminal.

[0080] According to the message processing apparatus of this disclosure, when a cloud gateway forwarding plane node based on VPP detects or obtains an uplink inner packet corresponding to the original packet sent by the terminal after decapsulation, it can determine the type of the uplink inner packet. If it is determined that the type of the uplink inner packet is an ARP request packet, its ingress interface is adjusted to an uplink physical interface, so that its ingress interface is switched from the current interface to a physical entity interface with actual proxy capabilities. The next processing node of the uplink inner packet is then pointed to the ARP proxy node inside the cloud gateway forwarding plane node, so as to guide the uplink inner packet into the local message proxy processing flow of the cloud gateway forwarding plane. That is, the ARP proxy node directly responds to the ARP request packet based on the uplink physical interface, i.e., generates an ARP proxy response packet. This allows ARP request packets to be answered directly at the cloud gateway forwarding plane without having to go through the cloud gateway control plane. This eliminates the need for deep parsing of ARP request packets and avoids maintaining a mapping table between the Media Access Control (MAC) address and Virtual Networking Index (VNI) information in the packet used to accurately forward ARP request packets. This reduces the overhead of maintenance and lookup, thereby reducing the processing complexity and resource consumption of the cloud gateway forwarding plane. At the same time, since the ARP proxy logic is implemented in the cloud gateway forwarding plane, the dependence on the cloud gateway control plane can be reduced, which in turn improves packet forwarding efficiency and network configuration flexibility.

[0081] Figure 6 This is a hardware block diagram illustrating an electronic device according to an embodiment of the present disclosure. Figure 6A schematic block diagram of an example electronic device 600 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0082] like Figure 6 As shown, device 600 includes a computing unit 601, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 602 or a computer program loaded into random access memory (RAM) 603 from storage unit 608. RAM 603 may also store various programs and data required for the operation of device 600. The computing unit 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0083] Multiple components in electronic device 600 are connected to I / O interface 605, including: input unit 606, such as keyboard, mouse, etc.; output unit 607, such as various types of displays, speakers, etc.; storage unit 608, such as disk, optical disk, etc.; and communication unit 609, such as network card, modem, wireless transceiver, etc. Communication unit 609 allows electronic device 600 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0084] The computing unit 601 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 601 performs the various methods and processes described above, such as message processing methods. For example, in some embodiments, the message processing method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 600 via ROM 502 and / or communication unit 609. When the computer program is loaded into RAM 603 and executed by the computing unit 601, one or more steps of the message processing method described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform message processing methods by any other suitable means (e.g., by means of firmware).

[0085] Figure 7 This is a schematic diagram illustrating a non-transitory computer-readable storage medium according to an embodiment of the present disclosure. Figure 7 As shown, a computer-readable storage medium 700 according to an embodiment of this disclosure stores computer-readable instructions 701 thereon. When the computer-readable instructions 701 are executed by a processor, the message processing method described with reference to the above figures is performed. The computer-readable storage medium includes, but is not limited to, volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, optical disk, magnetic disk, etc.

[0086] A computer program product according to an embodiment of the present disclosure includes a computer program that, when executed by a processor, performs a message processing method described with reference to any of the foregoing embodiments.

[0087] The above description, with reference to the accompanying drawings, illustrates a message processing scheme according to an embodiment of this disclosure. When a cloud gateway forwarding plane node based on VPP detects or obtains a decapsulated uplink inner packet corresponding to the original packet sent by the terminal, the type of the uplink inner packet can be determined. If the type of the uplink inner packet is determined to be an ARP request packet, its ingress interface is adjusted to an uplink physical interface, switching it from the current interface to a physical entity interface with actual proxy capabilities. The next processing node for the uplink inner packet is then directed to the ARP proxy node within the cloud gateway forwarding plane node. This guides the uplink inner packet into the local message proxy processing flow of the cloud gateway forwarding plane, whereby the ARP proxy node directly responds to the ARP request packet based on the uplink physical interface, generating an ARP proxy response packet. This allows ARP request packets to be answered directly at the cloud gateway forwarding plane without having to go through the cloud gateway control plane. This eliminates the need for deep parsing of ARP request packets and avoids maintaining a mapping table between the Media Access Control (MAC) address and Virtual Networking Index (VNI) information in the packet used to accurately forward ARP request packets. This reduces the overhead of maintenance and lookup, thereby reducing the processing complexity and resource consumption of the cloud gateway forwarding plane. At the same time, since the ARP proxy logic is implemented in the cloud gateway forwarding plane, the dependence on the cloud gateway control plane can be reduced, which in turn improves packet forwarding efficiency and network configuration flexibility.

[0088] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0089] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0090] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0091] Additionally, as used herein, the "or" used in a list of items beginning with "at least one" indicates a separate list, such that a list of, for example, "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not imply that the described example is preferred or better than other examples.

[0092] It should also be noted that in the systems and methods of this disclosure, the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent solutions of this disclosure. Furthermore, the terms "first," "second," "third," "fourth," "fifth," etc., used in this disclosure are used to distinguish similar objects and not to describe a specific order or sequence.

[0093] Various changes, substitutions, and modifications can be made to the technology described herein without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of this disclosure is not limited to the specific aspects of the processes, machines, manufactures, events, means, methods, and actions described above. Currently existing or later-developed processes, machines, manufactures, events, means, methods, or actions that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein can be utilized. Therefore, the appended claims include such processes, machines, manufactures, events, means, methods, or actions within their scope.

[0094] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0095] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.

Claims

1. A message processing method, characterized in that, Applied to cloud gateway forwarding plane nodes based on vector packet processing VPP, including: In response to the detection that the type of the uplink inner packet is an Address Resolution Protocol (ARP) request packet, the ingress interface of the uplink inner packet is adjusted to the uplink physical interface, wherein the uplink inner packet corresponds to the original packet sent by the terminal; The next processing node of the uplink inner layer message is pointed to the ARP proxy node in the cloud gateway forwarding plane node; The ARP proxy node generates an ARP proxy response message corresponding to the uplink inner message based on the uplink physical interface.

2. The method according to claim 1, characterized in that, Also includes: Configure the Internet Protocol (IP) address range to be proxied for the uplink physical interface; as well as The step of generating an ARP proxy response message corresponding to the uplink inner message through the ARP proxy node based on the uplink physical interface includes: In response to determining that the target Internet Protocol IP address in the uplink inner message belongs to the IP address range to be proxied, the ARP proxy response message is generated through the ARP proxy node.

3. The method according to claim 1 or 2, characterized in that, Also includes: Receive the uplink Virtual Extended Local Area Network (VXLAN) message corresponding to the original message; Remove the outer VXLAN encapsulation of the VXLAN packet to obtain the uplink inner packet.

4. The method according to claim 3, characterized in that, Also includes: Parse the outer VXLAN encapsulation of the VXLAN packet to obtain the Network Identifier (VNI) information; The VNI information is stored in the message structure of the VXLAN message.

5. The method according to claim 4, characterized in that, Also includes: Based on the VNI information stored in the message structure, the outgoing interface of the ARP proxy response message is determined; Adjust the outgoing interface of the ARP proxy response message to the user's VXLAN virtual interface.

6. The method according to claim 5, characterized in that, Also includes: The next processing node for the ARP proxy response message is directed to the VXLAN encapsulation node in the cloud gateway forwarding plane node. The VXLAN encapsulation node adds an outer VXLAN encapsulation to the ARP proxy response message based on the user's VXLAN virtual interface; The encapsulated downlink VXLAN message is sent to the terminal.

7. A message processing apparatus, characterized in that, Applied to cloud gateway forwarding plane nodes based on vector packet processing VPP, including: The adjustment module is configured to adjust the ingress interface of the uplink inner packet to the uplink physical interface in response to detecting that the type of the uplink inner packet is an Address Resolution Protocol (ARP) request packet, wherein the uplink inner packet corresponds to the original packet sent by the terminal. The processing module is configured to direct the next processing node of the uplink inner packet to the ARP proxy node in the cloud gateway forwarding plane node; The generation module is configured to generate an ARP proxy response message corresponding to the uplink inner layer message based on the uplink physical interface through the ARP proxy node.

8. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, implement the message processing method according to any one of claims 1-6.

9. A non-transitory computer-readable storage medium storing computer-readable instructions, the computer-readable instructions being used to cause the computer to perform the message processing method according to any one of claims 1-6.

10. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the message processing method according to any one of claims 1-6.

Images