Method, device, computing equipment and storage medium for transmitting data

By establishing a tunnel in Ethernet and encapsulating and inversely converting RoCE messages using the target encapsulation format, the complex problem of RDMA technology communication in Ethernet is solved, and efficient RDMA communication outside the data center and within the data center is realized, which simplifies the Equipment replacement and implementation process.

CN113497767BActive Publication Date: 2024-11-01HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010203724.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-03-20
Publication Date
2024-11-01
Estimated Expiration
2040-03-20

AI Technical Summary

Technical Problem

Under the Ethernet architecture, RDMA technology communication is complex, especially in unified scheduling outside the data center and within the data center, multiple network devices need to be replaced, resulting in increased implementation difficulty.

Method used

By establishing tunnels within and outside the data center, encapsulating and inversely converting RoCE messages using the target encapsulation format, RDMA communication within and outside the data center is realized, simplifying RDMA technical support in Ethernet. The specific method includes adding or deleting necessary headers and fields in the RoCE message, and transmitting data through technologies such as Vxlan or Vlan.

Benefits of technology

It realizes that without replacing hardware devices in Ethernet, the RDMA communication process outside the data center and within the data center is simplified, reducing implementation complexity and cost, and improving communication efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113497767B_ABST
    Figure CN113497767B_ABST
Patent Text Reader

Abstract

The present application provides a method, device, computing device and storage medium for transmitting data, which belongs to the field of network communication technology. The method includes: obtaining a first RoCE message, wherein the first RoCE message includes the address information of the destination end, converting the first RoCE message into a message encapsulated using a target encapsulation format, and obtaining a first tunnel transmission message, wherein the target encapsulation format is an encapsulation format corresponding to a tunnel established in a data center and outside a data center, and the first tunnel transmission message is a message that encapsulates the payload of the first RoCE message using the target encapsulation format through a mapping conversion mechanism, and sends the first tunnel transmission message outward through a tunnel, so that the network device at the opposite end of the tunnel sends the payload of the first tunnel transmission message to the destination end according to the address information of the destination end. By adopting the present application, RDMA technology can be supported in Ethernet in a relatively simple and efficient manner.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of network communication technology, and in particular to a method, device, computing equipment and storage medium for transmitting data. Background Art

[0002] With the development of computer technology, powerful high-performance computing (HPC) clusters can be constructed at low cost to obtain higher computing performance, faster calculation of large-scale scientific problems and processing of massive data. Therefore, high-throughput and low-latency network communication has become an important factor in building HPC clusters. In order to achieve low latency and high throughput, HPC clusters are usually deployed on wireless bandwidth (InfiniBand, IB) networks, and remote direct memory access (RDMA) technology is used (RDMA technology is a technology developed to solve the delay of server-side data processing in network transmission).

[0003] Moreover, with the development of cloud technology, HPC clusters are also cloud-based, which uses the flexible and elastic application model of cloud computing to solve the system management problems of the high-performance computing platform itself. When users use HPC clusters to handle high-performance computing problems, HPC cross-cloud deployment will occur, that is, the local HPC cluster capacity is insufficient and it is necessary to elastically expand resources to the HPC cloud (here it can be understood that the HPC cluster outside the data center is insufficient and it is necessary to elastically expand resources to the HPC in the data center). This requires unified scheduling of resources on the HPC cloud and the user's local HPC cluster.

[0004] In the related technology, in Ethernet, when realizing unified scheduling of HPC cloud resources and local HPC clusters and adopting RDMA technology, the network devices under the Ethernet architecture are generally replaced with hardware devices that support IB networks (such as switches, network cards, etc.).

[0005] Since there are many network devices under the Ethernet architecture, it is more complicated to implement changes to the network devices under the Ethernet architecture. Summary of the invention

[0006] In order to solve the problem that RDMA technology communication is relatively complex in Ethernet, the embodiment of the present application provides a method, apparatus, computing device and storage medium for transmitting data. The technical solution is as follows:

[0007] In a first aspect, a method for transmitting data is provided, the method comprising: obtaining a first RoCE message, wherein the first RoCE message includes address information of a destination end. Encapsulating the first RoCE message using a target encapsulation format to obtain a first tunnel transmission message, wherein the target encapsulation format is an encapsulation format corresponding to a tunnel established in a data center and outside a data center, and the first tunnel transmission message is a message that encapsulates a payload of the first RoCE message using the target encapsulation format through a mapping conversion mechanism. The first tunnel transmission message is sent outward through a tunnel, so that a network device at the opposite end of the tunnel sends the payload of the first tunnel transmission message to the destination end according to the address information of the destination end.

[0008] In the scheme shown in the present application, the execution subject of the method can be a tunnel endpoint to which the source end in the data center belongs, referred to as the tunnel endpoint in the data center. When the source end in the data center wants to send a message to the destination end outside the data center, the RDMA network interface card (RNIC) supporting RDMA at the source end in the data center can generate a first RoCE message. Specifically, the content of the first RoCE message is a frame check field, a redundant detection field, a payload (i.e., an IB payload), an IB basic transport header (Base Transport Header, BTH), a user datagram protocol (User Datagram Protocol, UDP) header, an Internet Protocol (Internet Protocol, IP) header, and an Ethernet header. The IP header of the first RoCE message includes the address information of the destination end outside the data center and the address information of the source end. The Ethernet header of the first RoCE message includes the MAC address of the source end and the MAC address of the destination end. The destination port of the UDP header of the first RoCE message is a preset port number (such as 4791), and the port number of the source port of the UDP header is the port number of the application sending the message in the source end. The RNIC at the source end in the data center transmits the first RoCE message to the device to which the tunnel endpoint belongs in the data center. In this way, the device to which the tunnel endpoint belongs in the data center can obtain the first RoCE message. The device to which the tunnel endpoint belongs in the data center can re-encapsulate the payload and IB BTH of the first RoCE message based on the target encapsulation format to obtain the first tunnel transmission message, that is, the first tunnel transmission message is a message that encapsulates the payload of the first RoCE message using the target encapsulation format through a mapping conversion mechanism. After the device to which the tunnel endpoint belongs in the data center converts the first RoCE message into the first tunnel transmission message, it can send the first tunnel transmission message outward through the tunnel to which the tunnel endpoint belongs. In this way, Ethernet supports RDMA technology through the conversion of message encapsulation, and RDMA communication between outside the data center and inside the data center is realized in Ethernet, and the implementation process is relatively simple.

[0009] In a possible implementation, the tunnel is a virtual extensible LAN (Vxlan) tunnel. Encapsulation is performed using a target encapsulation format, including: adding a Vxlan header to a first RoCE message, modifying a source IP address and a destination IP address of an Internet Protocol (IP) header of the first RoCE message to a local tunnel endpoint IP address of the tunnel and a peer tunnel endpoint IP address of the tunnel, respectively, and modifying a source Media Access Control (MAC) address and a destination MAC address of an Ethernet header of the first RoCE message to a local tunnel endpoint MAC address of the tunnel and a MAC address of a next-hop device, respectively.

[0010] In the scheme shown in the present application, the tunnel endpoint in the data center adds a Vxlan header between the IB BTH and the UDP header of the first RoCE message, and the Vxlan header includes flags, reserved fields, and VNI, etc. Among them, VNI is the VNI of the tunnel to which the current tunnel endpoint corresponds to the source port and the source IP address (i.e., the VNI of the tunnel endpoint in the data). The tunnel endpoint in the data center searches the routing table for the MAC address of the destination end and the IP address of the tunnel endpoint of the opposite end of the tunnel corresponding to the VNI. The tunnel endpoint in the data center modifies the source IP address of the IP header of the first RoCE message to the tunnel endpoint IP address in the data center of the tunnel, and modifies the destination IP address to the tunnel endpoint IP address of the opposite end of the tunnel. The tunnel endpoint in the data center modifies the source MAC address of the Ethernet header of the first RoCE message to the MAC address of the tunnel endpoint in the data center, and modifies the destination MAC address of the Ethernet header of the first RoCE message to the MAC address of the tunnel endpoint in the data center, and modifies the destination MAC address of the Ethernet header of the first RoCE message to the MAC address of the next-hop device (the MAC address of the next-hop device can be obtained by searching the routing table using the IP address of the opposite-end tunnel endpoint). In this way, the first RoCE message can be converted into a first tunnel transmission message.

[0011] In a possible implementation manner, encapsulation using the target encapsulation format further includes: deleting a redundant detection field and a frame check field of the first RoCE message.

[0012] In the solution shown in the present application, the tunnel endpoint in the data center can delete the redundant detection field and the frame check field of the first RoCE message. In this way, the length of the first RoCE message can be closer to the length of the first tunnel transmission message.

[0013] In a possible implementation, encapsulation using a target encapsulation format also includes: setting the destination port of the UDP header of the first RoCE message to the port number corresponding to Vxlan.

[0014] In this way, it can be indicated that the message is a Vxlan message.

[0015] In a possible implementation, the source end generating the first RoCE message is a virtual machine, and the destination end is a virtual machine; the encapsulation using the target encapsulation format also includes: adding an optional field to the first RoCE message, wherein the optional field includes an IP address of the destination end and an IP address of the source end.

[0016] In the solution shown in the present application, a virtual machine in a data center communicates with a virtual machine outside the data center, and an optional field can be added to the first RoCE message by the tunnel endpoint in the data center, and the optional field includes the IP address of the destination end and the IP address of the source end. In this way, the tunnel endpoint outside the data center can know the destination end and the source end to be sent to.

[0017] In a possible implementation, the source end for generating the first RoCE message is a bare metal node, and the destination end is a virtual machine or a bare metal node; encapsulation is performed using a target encapsulation format, and further includes: adding an optional field to the first RoCE message, wherein the optional field includes an IP address of the destination end.

[0018] In the solution shown in the present application, a bare metal node in a data center communicates with a virtual machine or bare metal node outside the data center, and an optional field can be added to the first RoCE message by the tunnel endpoint in the data center, and the optional field includes the IP address of the destination. In this way, the tunnel endpoint outside the data center can know the destination to be sent to.

[0019] In a possible implementation, the method also includes: receiving a second tunnel transmission message, the second tunnel transmission message is a message that encapsulates the payload of a third RoCE message using a target encapsulation format through a mapping conversion mechanism, and the third RoCE message is a message in which the Vlan number of the Ethernet header is deleted from a RoCE message in a virtual local area network (Virtual Local Area Network, Vlan) format; based on the target encapsulation format, reversely converting the second tunnel transmission message to obtain a fourth RoCE message including the payload of the second tunnel transmission message; and sending the fourth RoCE message to the destination end according to the address information of the destination end of the fourth RoCE message.

[0020] In the scheme shown in the present application, the tunnel endpoint in the data center can also receive a second tunnel transmission message, the second tunnel transmission message is a message that encapsulates the payload of the third RoCE message using the target encapsulation format through a mapping conversion mechanism, and the third RoCE message is a message that deletes the Vlan number of the Ethernet header in the RoCE message in the Vlan format. The tunnel endpoint in the data center can reversely convert the second tunnel transmission message based on the target encapsulation format (reverse conversion is the reverse process of obtaining the first tunnel transmission message) to obtain the fourth RoCE message of the payload of the second tunnel transmission message. The processing is: delete the Vxlan header in the second tunnel transmission message, and modify the destination port of the UDP header to a preset port number (such as 4791). The source IP address of the IP header of the second tunnel transmission message is modified to the device outside the data center that sends the third RoCE message, the destination IP address of the IP header of the second tunnel transmission message is modified to the IP address of the destination end in the data center, the source MAC address of the Ethernet header is modified to the MAC address of the tunnel endpoint in the data center, and the destination MAC address of the Ethernet header is modified to the MAC address of the destination end, and then the redundant detection field and the true check field are added to the message after these processes, that is, the fourth RoCE message is obtained. Then the tunnel endpoint in the data center can use the address information of the destination end of the fourth RoCE message to send the fourth RoCE message to the destination end. In this way, the source end outside the data center can communicate with the destination end in the data center.

[0021] In a second aspect, a method for transmitting data is provided, the method comprising: receiving a first tunnel transmission message through a tunnel, the first tunnel transmission message being a message that encapsulates a payload of a first RoCE message using a target encapsulation format through a mapping conversion mechanism, the target encapsulation format being an encapsulation format corresponding to a tunnel established in a data center and outside a data center. Based on the target encapsulation format, the first tunnel transmission message is reversely converted to obtain a second RoCE message including the payload of the first tunnel transmission message. According to the address information of the destination end of the second RoCE message, the second RoCE message is sent to the destination end.

[0022] In the scheme shown in the present application, the execution subject of the method can be a tunnel endpoint to which the destination end outside the data center belongs, referred to as the tunnel endpoint outside the data center for short, and the tunnel endpoint outside the data center receives the first tunnel transmission message through the tunnel. After receiving the first tunnel transmission message, the tunnel endpoint outside the data center can reversely convert the first tunnel transmission message based on the target encapsulation format corresponding to the tunnel, and obtain a second RoCE message including the payload of the first tunnel transmission message. The tunnel endpoint outside the data center can send the second RoCE message to the destination end based on the destination IP address of the second RoCE message (i.e., the IP address of the destination end). In this way, Ethernet supports RDMA technology through the conversion of message encapsulation, and RDMA communication between outside the data center and inside the data center is realized in Ethernet, and the implementation process is relatively simple.

[0023] In one possible implementation, the tunnel is a Vxlan tunnel; the network between the local tunnel endpoint and the destination end of the tunnel is a Vlan network; based on the target encapsulation format, the first tunnel transmission message is reversely converted, including: deleting the Vxlan header of the first tunnel transmission message; modifying the source IP address and destination IP address of the Internet Protocol IP header of the first tunnel transmission message from which the Vxlan header is deleted to the IP address of the source end and the IP address of the destination end, respectively; according to the stored mapping relationship between the VNI of the Vxlan and the Vlan number, adding the Vlan number corresponding to the VNI of the Vxlan header to the Ethernet header of the first tunnel transmission message from which the Vxlan header is deleted; modifying the port number of the destination port of the UDP in the first tunnel transmission message from which the Vxlan header is deleted to a preset port number; modifying the source MAC address of the Ethernet header to the MAC address of the local tunnel endpoint, and modifying the destination MAC address of the Ethernet header to the MAC address of the next-hop device.

[0024] In the solution shown in the present application, the tunnel endpoint outside the data center decapsulates the Ethernet header of the first tunnel transmission message, and determines that the destination MAC address in the Ethernet header is its own MAC address. The tunnel endpoint outside the data center can delete the Vxlan header of the first tunnel transmission message and obtain the VNI in the Vxlan header. The tunnel endpoint outside the data center obtains the IP address of the source and the IP address of the destination, modifies the source IP address of the IP header of the first tunnel transmission message with the Vxlan header deleted to the IP address of the source, and modifies the destination IP address of the IP header to the IP address of the destination.

[0025] The tunnel endpoint outside the data center will delete the Vxlan header and change the destination port number of the UDP header of the first tunnel transmission message from 4789 to a preset port number, such as 4791.

[0026] The tunnel endpoint outside the data center obtains the Vlan number corresponding to the VNI of the Vxlan header of the first tunnel transmission message from the mapping relationship between the VNI and the Vlan number of the stored Vxlan, and adds the Vlan number to the Ethernet header. In addition, the tunnel endpoint outside the data center modifies the source MAC address of the Ethernet header of the first tunnel transmission message with the Vxlan header deleted to the MAC address of the device to which the tunnel endpoint outside the data center belongs, and modifies the destination MAC address of the Ethernet header to the MAC address of the next-hop device to obtain the second RoCE message. In this way, the tunnel endpoint outside the data center converts the first tunnel transmission message into a second RoCE message including the payload of the first tunnel transmission.

[0027] In a possible implementation, the first tunnel transmission message is reversely converted based on the target encapsulation format, and also includes: adding a redundant detection field and a frame check field to the first tunnel transmission message with the Vxlan header deleted.

[0028] In the solution shown in the present application, the tunnel endpoint outside the data center generates a redundant detection field and a frame check field for the second RoCE message. The tunnel endpoint outside the data center adds the redundant detection field and the frame check field to the second RoCE message to obtain a complete second RoCE message. In this way, the destination end can check the received message.

[0029] In a possible implementation, the source end for generating the first RoCE message is a virtual machine, and the destination end is a virtual machine; based on the target encapsulation format, the first tunnel transmission message is reversely converted, and the method also includes: obtaining the IP address of the source end and the IP address of the destination end in the optional field of the first tunnel transmission message, and deleting the optional field in the first tunnel transmission message.

[0030] In the solution shown in the present application, a virtual machine in a data center communicates with a virtual machine outside the data center, and a tunnel endpoint outside the data center obtains the IP address of the source end and the IP address of the destination end from the optional field of the first tunnel transmission message, and then deletes the optional field. In this way, the tunnel endpoint outside the data center can obtain the IP address of the source end and the IP address of the destination end.

[0031] In a possible implementation, the source end for generating the first RoCE message is a bare metal node, and the destination end is a virtual machine or a bare metal node; based on the target encapsulation format, the first tunnel transmission message is reversely converted, and it also includes: obtaining the IP address of the destination end in the optional field of the first tunnel transmission message, and deleting the optional field in the first tunnel transmission message; according to the stored correspondence between the VNI, the tunnel endpoint IP address, the IP address of the destination end, and the IP address of the source end, the VNI of the Vxlan header, the source IP address of the IP header, and the IP address of the destination end in the optional field are determined.

[0032] In the scheme shown in the present application, the bare metal node in the data center communicates with the virtual machine or bare metal node outside the data center, and the tunnel endpoint outside the data center can obtain the IP address of the destination end in the optional field of the first tunnel transmission message, and then delete the optional field in the first tunnel transmission message. Then, the tunnel endpoint outside the data center can determine the VNI of the Vxlan header, the source IP address of the IP header, and the IP address of the destination end based on the correspondence between the stored VNI, the tunnel endpoint IP address, the IP address of the destination end, and the IP address of the source end. In this way, the IP address of the source end and the IP address of the destination end of the communicating parties can be obtained.

[0033] In one possible implementation, the method also includes: receiving an Address Resolution Protocol (ARP) request through a tunnel, wherein the ARP request includes the IP address of the destination, the IP address of the source, the VNI, and the tunnel endpoint IP address of the tunnel accessed by the source; and storing the correspondence between the VNI, the tunnel endpoint IP address, the IP address of the source, and the IP address of the destination.

[0034] The scheme shown in this application is that when the source end in the data center communicates with the destination end outside the data center for the first time, since the local tunnel endpoint of the source end in the data center (i.e., the tunnel endpoint in the data center) does not have the MAC address of the destination end outside the data center, an ARP request will be broadcast, and the ARP request includes VNI, the IP address of the source end, the IP address of the destination end, and the IP address of the tunnel endpoint to which the source end belongs. The ARP request is a Vxlan message, and the local tunnel endpoint sends the ARP request to the opposite tunnel endpoint (i.e., the tunnel endpoint outside the data center), and the opposite tunnel endpoint sends the ARP request to the destination end. The destination end feeds back a response message to the opposite tunnel endpoint, and the response message includes VNI, the IP address of the destination end, the IP address of the source end, the IP address of the tunnel endpoint to which the destination end belongs, and the MAC address of the destination end. The opposite tunnel endpoint parses the Vxlan message of the ARP request, obtains the MAC address of the source end, the corresponding relationship between the VNI and the IP address of the tunnel endpoint to which the source end belongs, and the corresponding relationship between the VNI, the IP address of the tunnel endpoint to which the source end belongs, the IP address of the destination end, and the IP address of the source end. After the opposite tunnel endpoint sends the response message of the ARP message to the local tunnel endpoint of the source end, the local tunnel endpoint parses the response message to obtain the MAC address of the destination end, the corresponding relationship between the VNI and the IP address of the tunnel endpoint to which the destination end belongs, and the corresponding relationship between the VNI, the IP address of the tunnel endpoint to which the destination end belongs, the IP address of the destination end, and the IP address of the source end. In this way, the corresponding relationship between the VNI, the IP address of the tunnel endpoint, the IP address of the source end, and the IP address of the destination end can be established.

[0035] In a possible implementation, the method further includes: receiving a RoCE message in a Vlan format; deleting the Vlan number of the Ethernet header in the RoCE message in the Vlan format to obtain a third RoCE message; converting the third RoCE message into a message encapsulated using a target encapsulation format through a mapping conversion mechanism to obtain a second tunnel transmission message, wherein the second tunnel transmission message is a message that encapsulates the payload of the third RoCE message using the target encapsulation format through the mapping conversion mechanism. The second tunnel transmission message is sent outward through the tunnel, so that the opposite end network device of the tunnel sends the payload of the second tunnel transmission message to the destination end indicated by the destination address information in the third RoCE message.

[0036] In the solution shown in the present application, when the source end outside the data center sends a message to the destination end in the data center, the source end outside the data center can generate a RoCE message in Vlan format and send it to the tunnel endpoint outside the data center. The tunnel endpoint outside the data center can delete the Vlan number of the Ethernet header in the RoCE message in Vlan format to obtain a third RoCE message. The tunnel endpoint outside the data center can use the target encapsulation format to convert the third RoCE message into a second tunnel transmission message, and the processing is that the tunnel endpoint outside the data center adds a Vxlan header to the third RoCE message, and modifies the source IP address in the IP header to the IP address of the tunnel endpoint outside the data center, and modifies the destination address to the IP address of the tunnel endpoint to which the destination end in the data center belongs; the tunnel endpoint outside the data center modifies the source MAC address of the Ethernet header in the third RoCE message to the MAC address of the tunnel endpoint outside the data center, and modifies the destination MAC address of the Ethernet header to the MAC address of the next hop device; modifies the destination port number in the UDP header to the port number of the Vxlan message; deletes the redundant detection field and frame check field of the third RoCE message, and obtains the second tunnel transmission message through these processes by the tunnel endpoint outside the data center. Then the tunnel endpoint outside the data center transmits the second tunnel transmission message to the tunnel endpoint in the data center through the tunnel. In this way, the RoCE message can be transmitted to the tunnel endpoint in the data center through the tunnel.

[0037] In a third aspect, a device for transmitting data is provided, the device comprising a plurality of modules, and the method described in the first aspect is executed by executing instructions through the plurality of modules.

[0038] In a fourth aspect, a device for transmitting data is provided, the device comprising a plurality of modules, and the method described in the second aspect is executed by executing instructions through the plurality of modules.

[0039] In a fifth aspect, the present application provides a computing device, comprising a memory and a processor, wherein the processor executes computer instructions stored in the memory, so that the computing device performs the method described in the first aspect above, or enables the computing device to implement the functions of the apparatus described in the third aspect.

[0040] In a sixth aspect, the present application provides a computing device, comprising a memory and a processor, wherein the processor executes computer instructions stored in the memory, so that the computing device executes the method described in the first aspect above, or enables the computing device to implement the functions of the apparatus described in the fourth aspect.

[0041] In the seventh aspect, the present application provides a non-volatile readable computer storage medium, which stores a computer program. When the computer program is executed by a computing device, it implements the method described in the first aspect above, or enables the computing device to implement the function of the apparatus described in the third aspect.

[0042] In an eighth aspect, the present application provides a non-volatile readable computer storage medium, which stores a computer program. When the computer program is executed by a computing device, it implements the method described in the first aspect above, or enables the computing device to implement the function of the apparatus described in the third aspect.

[0043] In a ninth aspect, the present application provides a computer program product, wherein the computer program product comprises computer instructions. When the computer instructions are executed by a computing device, the computing device executes the method described in the first aspect above.

[0044] In a tenth aspect, the present application provides a computer program product, wherein the computer program product comprises computer instructions. When the computer instructions are executed by a computing device, the computing device executes the method described in the first aspect above.

[0045] An eleventh method, the present application provides a system for transmitting data, the system comprising a first network device and a second network device, the first network device being such as the apparatus described in the third aspect above, and the second network device being such as the apparatus described in the fourth aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 This is a schematic diagram of a data transmission scenario provided by an embodiment of the present application;

[0047] Figure 2 This is a schematic diagram of a data transmission scenario provided by an embodiment of the present application;

[0048] Figure 3 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0049] Figure 4 It is a flowchart of a method for transmitting data provided by an embodiment of the present application;

[0050] Figure 5 It is a flowchart of a method for transmitting data provided by an embodiment of the present application;

[0051] Figure 6 It is a schematic diagram of conversion between a RoCE message and a Vxlan message provided in an embodiment of the present application;

[0052] Figure 7It is a schematic diagram of conversion between a Vxlan message and a RoCE message provided in an embodiment of the present application;

[0053] Figure 8 is a structural schematic diagram of a device for transmitting data provided in an embodiment of the present application;

[0054] Fig. 9 is a structural schematic diagram of a device for transmitting data provided in an embodiment of the present application;

[0055] Fig.10 It is a structural diagram of a device for transmitting data provided in an embodiment of the present application. DETAILED DESCRIPTION

[0056] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0057] In order to facilitate the understanding of the embodiments of the present application, the concepts of the terms involved are first introduced below:

[0058] RDMA technology is a technology that moves data from one system to a remote system memory without causing any impact on the system's operating system. It frees up memory bandwidth and central processing unit (CPU) cycles, not only saving a lot of CPU resources, but also reducing the system's network communication latency.

[0059] RDMA over Converged Ethernet (RoCE) is a network protocol that allows Ethernet to use RDMA.

[0060] A network card that supports RDMA and is used to implement RoCE message encapsulation, i.e., the Ethernet network card of the virtual machine in the HPC cluster. The RNIC can be a network card that introduces RoCE software into a common network card, or it can be a directly designed RNIC network card. In the second version of the RoCE (RoCEv2) protocol stack, IB BTH, UDP, IP, and Ethernet layers are all encapsulated layer by layer by RNIC.

[0061] This application is applicable to Ethernet scenarios, and is used for efficient intercommunication between HPC clusters outside the data center and inside the data center, and supports unified management of HPC clusters using RoCE inside and outside the data center. Tunnels are established outside the data center and inside the data center, and the tunnels can be tunnels using Vxlan technology (referred to as Vxlan tunnels), tunnels using Generic Network Virtualization Encapsulation (GENEVE) technology, tunnels using Network Virtualization UsingGeneric Routing Encapsulation (NVGRE) technology, tunnels using Stateless Transport Tunneling (STT) technology, and the like.

[0062] Furthermore, the tunnel established outside the data center and inside the data center can be a tunnel established between a computing node of an HPC cluster outside the data center (virtual machines are deployed on the computing nodes) and a computing node of an HPC cluster inside the data center, or a tunnel established between a computing node in an HPC cluster inside the data center and a gateway device outside the data center, or a tunnel established between a gateway device inside the data center and a gateway device outside the data center.

[0063] This application takes the tunnel established between the computing node in the HPC cluster in the data center and the gateway device outside the data center as an example, and the established tunnel is a Vxlan tunnel as an example for explanation. The network architecture diagram may include Figure 1 The network architecture shown and Figure 2 The network architecture shown in Figure 1 In the data center, the HPC cluster outside the data center and the HPC cluster inside the data center are deployed in the Ethernet. The HPC cluster outside the data center includes multiple computing nodes, each of which can be set up with multiple virtual machines. The HPC cluster inside the data center also includes multiple computing nodes, each of which can be set up with multiple virtual machines. The data center and the data center are in the same core network. Figure 2 In the data center, the HPC cluster outside the data center and the HPC cluster inside the data center are deployed on the Ethernet. The HPC cluster outside the data center includes multiple bare metal nodes (referring to a computing node used as a node, on which no virtual machine is deployed), and the HPC cluster inside the data center also includes multiple computing nodes, each of which has no virtual machine deployed (can be called a bare metal node) or has a virtual machine deployed. Figure 1 and Figure 2In the data center, a Vxlan tunnel is established between each computing node in the data center and a gateway device outside the data center (such as L2 bridge (Layer2Bridge, L2BR), L3 gateway (Layer 3Gateway, L3GW), etc.). In this way, tunnels are used to transmit messages between computing nodes in the data center and gateway devices outside the data center.

[0064] In order to achieve efficient intercommunication between HPC clusters outside and inside a data center, the present application provides a method for transmitting data, which can be performed by a gateway device or a computing node. The gateway device and the computing node can be hardware devices, such as routers or switches implemented based on hardware, and the gateway device and the computing node can also be software devices, such as software installed on a computing device. The computing device is a hardware device, such as a server.

[0065] Figure 3 A possible architecture diagram of a computing device of the present application is provided as an example. The computing device may include a processor 301, a memory 302, a communication interface 303, and a bus 304. In the computing device, the number of processors 301 may be one or more. Figure 3 Only one of the processors 301 is shown. Optionally, the processor 301 may be a CPU. If the computing device has multiple processors 301, the types of the multiple processors 301 may be different or the same. Optionally, the multiple processors of the computing device may also be integrated into a multi-core processor.

[0066] The memory 302 stores computer instructions and data. The memory 302 can store computer instructions and data required to implement the method for transmitting data provided in the present application. The memory 302 can be any one or any combination of the following storage media: non-volatile memory (such as read-only memory (ROM), solid state disk (SSD), hard disk (HDD), optical disk, etc.), volatile memory.

[0067] The communication interface 303 may be any one or any combination of the following devices: a network interface (such as an Ethernet interface), a wireless network card, or other devices with a network access function.

[0068] The communication interface 303 is used for data communication between the computing device and other nodes or terminal devices.

[0069] Figure 3A bus 304 is also exemplarily drawn. The bus 304 can connect the processor 301 with the memory 302 and the communication interface 303. Thus, through the bus 304, the processor 301 can access the memory 302, and can also use the communication interface 303 to exchange data with other computing devices or terminal devices.

[0070] In the present application, the computing device executes the computer instructions in the memory 302, and uses the computing device to implement the method for transmitting data provided in the present application. For example, the computing device executes the steps performed by the encapsulation module in the above-mentioned method for transmitting data.

[0071] The following will be combined with specific implementation methods. Figure 4 The processing flow shown is described in detail, and the content can be as follows:

[0072] Step 401: A device to which a tunnel endpoint in a data center belongs obtains a first RoCE message, wherein the first RoCE message includes address information of a destination end.

[0073] The device to which the tunnel endpoint in the data center belongs may be a gateway device in the data center, a computing node in the data center, etc.

[0074] In this embodiment, when the source end in the data center wants to send a message to the destination end outside the data center, the RNIC of the source end in the data center can generate a first RoCE message. Specifically, the content of the first RoCE message is a frame check field, a redundant detection field, a payload (i.e., an IB payload), an IB BTH, a UDP header, an IP header, and an Ethernet header. The IP header of the first RoCE message includes the address information of the destination end outside the data center and the address information of the source end. The Ethernet header of the first RoCE message includes the MAC address of the source end and the MAC address of the destination end. The destination port of the UDP header of the first RoCE message is a preset port number (such as 4791), and the source port of the UDP header is the port number of the application sending the message in the source end. The RNIC of the source end in the data center transmits the first RoCE message to the device to which the tunnel endpoint belongs in the data center. In this way, the device to which the tunnel endpoint belongs in the data center can obtain the first RoCE message.

[0075] In step 402, a device belonging to a tunnel endpoint in the data center converts the first RoCE message into a message encapsulated using a target encapsulation format to obtain a first tunnel transmission message. The target encapsulation format is an encapsulation format corresponding to a tunnel established in the data center and outside the data center. The first tunnel transmission message is a message that encapsulates the payload of the first RoCE message using the target encapsulation format through a mapping conversion mechanism.

[0076] In this embodiment, the device to which the tunnel endpoint belongs in the data center can re-encapsulate the payload and IB BTH of the first RoCE message based on the target encapsulation format to obtain a first tunnel transmission message, that is, the first tunnel transmission message is a message that encapsulates the payload of the first RoCE message using the target encapsulation format through a mapping conversion mechanism.

[0077] Step 403: The device to which the tunnel endpoint belongs in the data center sends a first tunnel transmission message outward through the tunnel.

[0078] In this embodiment, after the device to which the tunnel endpoint belongs in the data center converts the first RoCE message into the first tunnel transmission message, the first tunnel transmission message can be sent outward through the tunnel to which the tunnel endpoint belongs.

[0079] Step 404: a device to which a tunnel endpoint outside the data center belongs receives a first tunnel transmission message through the tunnel.

[0080] Step 405: The device to which the tunnel endpoint belongs outside the data center performs a reverse conversion on the first tunnel transmission message based on the target encapsulation format to obtain a second RoCE message including the payload of the first tunnel transmission message.

[0081] In this embodiment, after receiving the first tunnel transmission message, the device to which the tunnel endpoint outside the data center belongs can reversely convert the first tunnel transmission message based on the target encapsulation format corresponding to the tunnel to obtain a second RoCE message including the payload of the first tunnel transmission message.

[0082] Step 406: The device to which the tunnel endpoint belongs outside the data center sends the second RoCE message to the destination end.

[0083] In this embodiment, the device to which the tunnel endpoint belongs outside the data center can send the second RoCE message to the destination end based on the destination IP address of the second RoCE message (that is, the IP address of the destination end).

[0084] In this way, even if the hardware device in the Ethernet is not replaced, RDMA communication between the outside of the data center and the inside of the data center can be realized in the Ethernet, and the implementation process is relatively simple. In addition, in this embodiment, the first RoCE message is converted into a first tunnel transmission message for transmission, rather than directly encapsulating it in the outer layer of the first RoCE message using the target encapsulation format, so even if the length of the header of the first tunnel transmission message is greater than the length of the header of the first RoCE message, the length of the original first RoCE message will not increase significantly.

[0085] RDMA technology can include the process of reading data and the process of writing data. In this embodiment, a tunnel is established between the computing node in the HPC cluster in the data center and the gateway device outside the data center, and the established tunnel is a Vxlan tunnel. The following process is the process of virtual machine B outside the data center writing data to virtual machine A in the data center (i.e. Figure 1 The solution is described using the network architecture of Figure 5 As shown, the execution flow can be as follows:

[0086] Step 501: An application of virtual machine A in a data center generates an RDMA request and transmits it to the RNIC of virtual machine A. The RNIC of virtual machine A generates a first RoCE message. The RNIC of virtual machine A sends the first RoCE message to the tunnel endpoint of the computing node to which virtual machine A belongs.

[0087] Among them, virtual machine A is deployed on a computing node in the data center, and virtual machine B is deployed on a computing node outside the data center.

[0088] In this embodiment, when application A of virtual machine A in the data center wants to send a message to application B of virtual machine B outside the data center, application A of virtual machine A generates an RDMA request. Without the need for any kernel memory participation, application A transmits the RDMA request to the RNIC of virtual machine A. The RNIC of virtual machine A reads the memory key and storage address information from application A. The memory key is used for authentication when virtual machine B accesses the storage address information. The RNIC of virtual machine A packages the memory key and storage address information into an IB payload, adds an IB BTH, a UDP header, an IP header, and an Ethernet header to the IB payload in sequence, and generates a redundant detection field and a frame check field to obtain a first RoCE message. The fields of the first RoCE message include an Ethernet header, an IP header, a UDP header, an IB BTH, an IB payload, a redundant detection field, and a frame check field in sequence from the beginning to the end. The IP header includes the address information of virtual machine B outside the data center (i.e., the IP address of the destination virtual machine) and the address information of virtual machine A (i.e., the IP address of the source virtual machine). The Ethernet header includes the MAC address of the source virtual machine (i.e., the MAC address of virtual machine A) and the MAC address of the destination virtual machine (i.e., the MAC address of virtual machine B). In the UDP header, the port number of the destination port is 4791 (4791 is the port number used by RoCE messages), and the port number of the source port is the port number of application A. The RNIC of virtual machine A transmits the first RoCE message to the tunnel endpoint of the computing node to which virtual machine A belongs.

[0089] In step 502, the tunnel endpoint of the computing node to which virtual machine A belongs performs the following process on the first RoCE message to obtain a first tunnel transmission message: a) adding a Vxlan header to the first RoCE message, wherein the VNI of the Vxlan header is the VNI corresponding to the source IP address and source port of the first RoCE message; b) modifying the source IP address of the IP header of the first RoCE message to the IP address of the local tunnel endpoint of the tunnel, and modifying the destination IP address of the IP header of the first RoCE message to the IP address of the opposite tunnel endpoint of the tunnel; c) modifying the source MAC address and the destination MAC address of the Ethernet header of the first RoCE message to the MAC address of the local tunnel endpoint of the tunnel and the MAC address of the next-hop device, respectively; d) deleting the redundant detection field and the frame check field of the first RoCE message; e) adding the IP address of virtual machine B and the IP address of virtual machine A to the first RoCE message.

[0090] Among them, the tunnel is a Vxlan tunnel.

[0091] In this embodiment, the tunnel endpoint of the computing node to which virtual machine A belongs is referred to as the local tunnel endpoint in step 502. The local tunnel endpoint adds a Vxlan header between the IB BTH and the UDP header of the first RoCE message, and the Vxlan header includes flags, reserved fields, and VNI, etc. Among them, VNI is the VNI of the tunnel to which the current tunnel endpoint corresponds to the source port and source IP address (i.e., the VNI of the local tunnel endpoint). The local tunnel endpoint searches the routing table for the MAC address of virtual machine B and the IP address of the opposite tunnel endpoint of the tunnel corresponding to the VNI. The local tunnel endpoint modifies the source IP address of the IP header of the first RoCE message to the IP address of the local tunnel endpoint of the tunnel, and modifies the destination IP address to the IP address of the opposite tunnel endpoint of the tunnel. The local tunnel endpoint modifies the source MAC address of the Ethernet header of the first RoCE message to the MAC address of the local tunnel endpoint, and modifies the destination MAC address of the Ethernet header of the first RoCE message to the MAC address of the next-hop device (the MAC address of the next-hop device can be obtained by searching the routing table using the IP address of the opposite tunnel endpoint). The local tunnel endpoint deletes the redundant detection field and the frame check field of the first RoCE message. The local tunnel endpoint adds the IP address of virtual machine A and the IP address of virtual machine B between the IB BTH field and the Vxlan header of the first RoCE message (the field name of the added content can be called an optional field), and these two IP addresses can be obtained from the IP header of the first RoCE message. After the local tunnel endpoint performs the above processing on the first RoCE message, it obtains the first tunnel transmission message, that is, the first RoCE message is converted into the first tunnel transmission message. In this way, since the length of the redundant detection field and the frame check field is equal to the Vxlan header, the length of the first tunnel transmission message is only the length of the optional field increased compared to the length of the first RoCE message.

[0092] In addition, the local tunnel endpoint sets the destination port of the UDP header of the first tunnel transmission message to the port number corresponding to Vxlan to identify that the first tunnel transmission message is a Vxlan message, where the port number corresponding to Vxlan is 4789.

[0093] like Figure 6As shown, this embodiment also gives the difference between the first RoCE message and the first tunnel transmission message. The content of the first RoCE message includes an Ethernet header, an IP header, a UDP header, an optional field, an IB BTH, an IB load, a redundant detection field and a frame check field from the beginning to the end. The content of the first tunnel transmission message includes an Ethernet header, an IP header, a UDP header, a Vxlan header, an optional field, an IB BTH, and an IB load from the beginning to the end. Although the first RoCE message and the first tunnel transmission message both include an Ethernet header, a UDP header and an IP header, their Ethernet headers have different source MAC addresses and destination MAC addresses, their UDP headers have different destination ports, and their IP headers have different source IP addresses and destination IP addresses. It should be noted here that Figure 6 Only the modified parts are shown, and the remaining unmodified parts are not shown.

[0094] Step 503: The local tunnel endpoint transmits the first tunnel transmission message to the network device to which the opposite tunnel endpoint of the tunnel belongs.

[0095] In this embodiment, the network device to which the opposite end tunnel endpoint of the tunnel belongs is a gateway device outside the data center, such as L2BR.

[0096] The local tunnel endpoint sends the first tunnel transmission message to the next hop device until it is sent to the opposite tunnel endpoint of the tunnel.

[0097] Step 504: The network device to which the opposite tunnel endpoint of the tunnel belongs receives the first tunnel transmission message through the tunnel.

[0098] Step 505, the network device to which the tunnel endpoint at the opposite end of the tunnel belongs performs the following process on the first tunnel transmission message to obtain a second RoCE message including the payload of the first tunnel transmission message: a) deleting the Vxlan header of the first tunnel transmission message; b) modifying the source IP address of the IP header of the first tunnel transmission message from the tunnel endpoint IP address to the source virtual machine IP address, and modifying the destination IP address of the IP header to the destination virtual machine IP address; c) modifying the port number of the destination port of the User Datagram Protocol UDP in the first tunnel transmission message from which the Vxlan header is deleted to a preset port number; d) according to the stored mapping relationship between the VNI of the Vxlan and the Vlan number, adding the Vlan number corresponding to the VNI of the Vxlan header to the Ethernet header of the first tunnel transmission message, modifying the source MAC address of the Ethernet header to the MAC address of the local tunnel endpoint, and modifying the destination MAC address of the Ethernet header to the MAC address of the next-hop device; e) adding a redundant detection field and a frame check field to the first tunnel transmission message; f) deleting the optional fields in the first tunnel transmission message.

[0099] In this embodiment, the network device to which the opposite end tunnel endpoint of the tunnel belongs is a gateway device outside the data center.

[0100] In this embodiment, after receiving the first tunnel transmission message, the network device to which the tunnel endpoint of the opposite end of the tunnel belongs decapsulates the Ethernet header of the first tunnel transmission message, and determines in the Ethernet header that the destination MAC address is its own MAC address. The network device can delete the Vxlan header and optional field of the first tunnel transmission message, and obtain the VNI in the Vxlan header. The network device obtains the IP address of the source end (the IP address of virtual machine A) and the IP address of the destination end (the IP address of virtual machine B) in the optional field of the first tunnel transmission message, modifies the source IP address of the IP header of the first tunnel transmission message from which the Vxlan header is deleted to the IP address of virtual machine A, and modifies the destination IP address of the IP header to the IP address of virtual machine B.

[0101] The network device to which the tunnel endpoint at the opposite end of the tunnel belongs will delete the Vxlan header and change the destination port number of the UDP header of the first tunnel transmission message from 4789 to 4791.

[0102] The network device to which the tunnel endpoint at the opposite end of the tunnel belongs obtains the Vlan number corresponding to the VNI of the Vxlan header of the first tunnel transmission message from the stored mapping relationship between the VNI of the Vxlan and the Vlan number, and adds the Vlan number to the Ethernet header. The network device also modifies the source MAC address of the Ethernet header of the first tunnel transmission message from which the Vxlan header is deleted to the MAC address of the network device, and modifies the destination MAC address of the Ethernet header to the MAC address of the next-hop device, to obtain the second RoCE message. In this way, the network device to which the tunnel endpoint at the opposite end of the tunnel belongs converts the first tunnel transmission message into a second RoCE message including the payload transmitted by the first tunnel.

[0103] Then the network device to which the tunnel endpoint of the opposite end of the tunnel belongs generates a redundant detection field and a frame check field for the second RoCE message. The network device adds the redundant detection field and the frame check field to the second RoCE message to obtain a complete second RoCE message.

[0104] In addition, it should be noted that the tunnel has two tunnel endpoints, the local tunnel endpoint and the opposite tunnel endpoint correspond to each other. If the current tunnel endpoint sends a message to another tunnel endpoint, the current tunnel endpoint is the local tunnel endpoint, and the other tunnel endpoint is the opposite tunnel endpoint relative to the current tunnel endpoint.

[0105] like Figure 7As shown, this embodiment also gives the difference between the first tunnel transmission message and the second RoCE message processed by the tunnel endpoint of the tunnel peer. The content of the first tunnel transmission message includes, from the beginning to the end, an Ethernet header, an IP header, a UDP header, a Vxlan header, an optional field, an IB BTH, and an IB load. The content of the second RoCE message includes, from the beginning to the end, an Ethernet header, an IP header, a UDP header, an IB BTH, an IB load, a redundant detection field, and a frame check field. Although the second RoCE message and the first tunnel transmission message both include an Ethernet header and an IP header, their source MAC address and destination MAC address of the Ethernet header are different, their source IP address and destination IP address of the IP header are different, and the second RoCE message also includes a Vlan number. It should be noted here that Figure 7 Only the modified parts are shown, and the remaining unmodified parts are not shown.

[0106] Step 506: The network device to which the opposite tunnel endpoint of the tunnel belongs sends the second RoCE message to virtual machine B.

[0107] In this embodiment, the opposite tunnel endpoint of the tunnel sends the second RoCE message to the RNIC of the destination virtual machine (ie, virtual machine B) based on the destination IP address of the RoCE message (ie, the IP address of virtual machine B).

[0108] Step 507: Virtual machine B sends a write request of a RoCE message to virtual machine A in the data center.

[0109] In this embodiment, after receiving the second RoCE message, the RNIC of virtual machine B can decapsulate the second RoCE message to obtain the IB payload. The RNIC of virtual machine B can obtain the memory key and storage address information provided by application A in virtual machine A in the IB payload. Then the RNIC of virtual machine B obtains the storage address information of the data to be sent of virtual machine B from application B to which the data to be sent belongs. The RNIC of virtual machine B packages the memory key and storage address information obtained from the IB payload and the storage address information of the data to be sent into an IB payload. Then the RNIC of virtual machine B adds IB BTH, UDP header, IP header and Ethernet header to the outer layer of the IB payload in sequence to obtain a write request for the RoCE message. In addition, the RoCE message also includes a redundant detection field and a frame check field. In this RoCE message, the source IP address of the IP header is the IP address of virtual machine B, and the destination IP address is the IP address of virtual machine A; the source MAC address of the Ethernet header is the MAC address of the computing node to which virtual machine B belongs, and the destination MAC address is the MAC address of the next-hop device; the port number of the source port of the UDP header is the port number of application B, and the destination port of the UDP header uses the preset port number (such as 4791).

[0110] Then virtual machine B sends the write request of the RoCE message to the network device outside the data center through the link between the network device outside the data center. The network device converts the RoCE message into a second tunnel transmission message and sends it to virtual machine A in the data center (the detailed process is described later).

[0111] Step 508: Virtual machine B sends the to-be-sent data of the RoCE message to the source virtual machine in the data center.

[0112] In this embodiment, after virtual machine B sends the write request of the RoCE message to the RNIC of virtual machine A, the RNIC of virtual machine B can use the data to be sent as the IB load, generate a RoCE message, and send the data to be sent to the RNIC of virtual machine A based on the RoCE message.

[0113] Step 509: Virtual machine B sends a RoCE message sending completion message to the source virtual machine in the data center.

[0114] In this embodiment, after the RNIC of virtual machine B sends all the data to be sent to the RNIC of virtual machine A, the RNIC of virtual machine B can generate a sending completion message of the RoCE message. Then the RNIC of virtual machine B sends the sending completion message to the RNIC of virtual machine A. The sending completion message is used to indicate that the data to be sent by virtual machine B to virtual machine A has been sent.

[0115] After the RNIC of virtual machine A receives the sending completion message sent by virtual machine B, the RNIC of virtual machine A can write the data to be sent received from virtual machine B into the cache area of ​​application A that receives the data to be sent (i.e., the cache area indicated by the storage address information provided by application A).

[0116] In addition, in this embodiment, a processing process after a network device outside the data center (i.e., a network device to which the local tunnel endpoint currently belongs) receives a RoCE message in a Vlan format sent by a virtual machine B in the data center is also provided:

[0117] The network device outside the data center deletes the Vlan number of the Ethernet header of the RoCE message in Vlan format to obtain a third RoCE message. The network device outside the data center establishes a correspondence between the source port, source IP address and VNI of the tunnel to which the current tunnel endpoint belongs in the UDP header in the third RoCE message. Then the network device outside the data center adds a Vxlan header between the IB BTH and the UDP header of the third RoCE message, and the Vxlan header includes an identifier, a reserved field and a VNI, etc. Among them, the VNI is the VNI of the tunnel endpoint outside the data center. The network device outside the data center adds an optional field between the IB BTH and the Vxlan header of the third RoCE message, and the optional field includes the address information of the destination virtual machine (i.e., the IP address of virtual machine A) and the address information of the source virtual machine (i.e., the IP address of virtual machine B). The network device outside the data center modifies the source IP address of the IP header of the third RoCE message to the IP address of the network device outside the data center, and modifies the destination IP address to the IP address of the opposite tunnel endpoint in the data center. The network device outside the data center modifies the source MAC address of the Ethernet header of the third RoCE message to the MAC address of the network device outside the data center, and modifies the destination MAC address of the Ethernet header of the third RoCE message to the MAC address of the next-hop device (the MAC address is determined in the routing table based on the IP address of the opposite tunnel endpoint in the data center). The network device outside the data center deletes the redundant detection field and the frame check field of the third RoCE message. Through these processes, the network device outside the data center obtains the second tunnel transmission message. In this way, since the length of the redundant detection field and the frame check field is equal to the Vxlan header, the length of the second tunnel transmission message is only increased by the length of the optional field compared to the length of the third RoCE message.

[0118] In addition, the network equipment outside the data center sets the destination port of the UDP header of the second tunnel transmission message to the port corresponding to Vxlan to identify it as a Vxlan message, where the port number corresponding to Vxlan is 4789.

[0119] Then the network device outside the data center sends the second tunnel transmission message to the opposite tunnel endpoint in the data center. The opposite tunnel endpoint in the data center decapsulates the Ethernet header of the second tunnel transmission message, and determines that the destination MAC address is its own MAC address in the Ethernet header. Then the opposite tunnel endpoint in the data center can delete the Vxlan header of the second tunnel transmission message and delete the optional field. Then the opposite tunnel endpoint in the data center obtains the source virtual machine IP address (i.e., the IP address of virtual machine B) and the destination virtual machine IP address (i.e., the IP address of virtual machine A) in the optional field, modifies the source IP address of the IP header of the second tunnel transmission message that deletes the Vxlan header to the IP address of virtual machine B, and modifies the destination IP address of the IP header to the IP address of virtual machine A. The opposite tunnel endpoint in the data center modifies the destination port number of the UDP header of the second tunnel transmission message that deletes the Vxlan header to 4791. The opposite tunnel endpoint in the data center modifies the source MAC address of the Ethernet header to the MAC address of the opposite tunnel endpoint, modifies the destination MAC address of the Ethernet header to the MAC address of virtual machine A, and obtains the fourth RoCE message. In this way, the network device to which the opposite tunnel endpoint in the data center belongs converts the second tunnel transmission message into the fourth RoCE message. Then the tunnel endpoint in the data center generates a redundant detection field and a frame check field for the fourth RoCE message, adds the redundant detection field and the frame check field to the fourth RoCE message, and obtains a complete fourth RoCE message. The opposite tunnel endpoint in the data center sends the complete fourth RoCE message to the RNIC of virtual machine A. The RNIC of virtual machine A can decapsulate the RNIC and obtain the memory key and storage address information sent by virtual machine B (the memory key and storage address information sent by virtual machine A to virtual machine B) and the storage address information of the data to be sent.

[0120] Subsequently, virtual machine B encapsulates the data to be sent into a RoCE message and sends it to virtual machine A. The specific sending form is the same as the form of the write request for sending the RoCE message, which will not be repeated here.

[0121] Through the above embodiments, the conversion and mapping mechanism of RoCE messages and Vxlan messages can be realized under the Ethernet architecture, and the Vxlan tunnel communication inside and outside the data center is used to transmit RoCE messages. In addition, when the network outside the data center is a Vlan network, the gateway device outside the data center converts the Vxlan message into a RoCE message in the Vlan format, and transmits the RoCE message in the Vlan format to the destination virtual machine outside the data center through the traditional Vlan network.

[0122] exist Figure 2In order to achieve high-performance computing under the network architecture, the data center includes bare metal nodes (i.e. computing nodes without virtual machines deployed), and computing nodes outside the data center are deployed with virtual machines or not deployed with virtual machines (computing nodes without virtual machines deployed can be called bare metal nodes). Figure 2 The RoCE message sending process under the network architecture can be compared with Figure 1 The RoCE message sending process under the network architecture is exactly the same. Of course, in order to save the number of bytes occupied in the header of the sent message, the following method can be used:

[0123] and Figure 1 The only difference under the network architecture is that: (1) When the bare metal node in the data center sends a message to the destination outside the data center, the optional field does not include the IP address of the source end, and can only include the IP address of the destination end. In this way, when the gateway device outside the data center determines the IP address of the destination end, it obtains it from the optional field. When the gateway device outside the data center determines the IP address of the source end, it determines the VNI of the Vxlan header, the source IP address of the IP header, and the IP address of the destination end in the optional field. The corresponding relationship between the stored VNI, the tunnel endpoint IP address, the IP address of the destination end, and the IP address of the source end (the tunnel endpoint is the tunnel endpoint to which the source end belongs) determines the IP address of the source end corresponding to the VNI of the Vxlan header, the source IP address of the IP header, and the IP address of the destination end in the optional field.

[0124] (2) When the source end outside the data center sends a message to the destination end inside the data center, the optional field does not include the IP address of the destination end, but only includes the IP address of the source end (i.e., the IP address of the source end outside the data center). In this way, when the bare metal node in the data center determines the IP address of the source end, it obtains it from the optional field. When the bare metal node in the data center determines the IP address of the destination end, it determines the IP address of the destination end corresponding to the VNI of the Vxlan header, the destination IP address of the IP header, and the IP address of the source end in the optional field from the corresponding relationship among the stored VNI, the IP address of the tunnel endpoint, the IP address of the destination end, and the IP address of the source end (the tunnel endpoint is the tunnel endpoint to which the source end belongs).

[0125] The IP addresses included in the optional fields in (1) and (2) are actually the IP addresses of bare metal nodes in the data center.

[0126] In addition, this embodiment also provides a process for establishing a corresponding relationship between the VNI, the tunnel endpoint IP address, the destination IP address, and the source IP address:

[0127] When the bare metal node (source) in the data center communicates with the destination outside the data center for the first time, since the local tunnel endpoint of the bare metal node in the data center does not have the MAC address of the destination outside the data center, an ARP request will be broadcast. The ARP request includes VNI, the IP address of the source, the IP address of the destination, and the IP address of the tunnel endpoint to which the source belongs. The ARP request is a Vxlan message. The local tunnel endpoint sends the ARP request to the opposite tunnel endpoint, and the opposite tunnel endpoint sends the ARP request to the destination. The destination sends a response message to the opposite tunnel endpoint. The response message includes VNI, the IP address of the destination, the IP address of the source, the IP address of the tunnel endpoint to which the destination belongs, and the MAC address of the destination. The opposite tunnel endpoint parses the Vxlan message of the ARP request to obtain the MAC address of the source, the corresponding relationship between the VNI and the IP address of the tunnel endpoint to which the source belongs, and the corresponding relationship between the VNI, the IP address of the tunnel endpoint to which the source belongs, the IP address of the destination, and the IP address of the source. After the opposite tunnel endpoint sends the response message of the ARP message to the local tunnel endpoint of the source end, the local tunnel endpoint parses the response message to obtain the MAC address of the destination end, the correspondence between the VNI and the IP address of the tunnel endpoint to which the destination end belongs, and the correspondence between the VNI, the IP address of the tunnel endpoint to which the destination end belongs, the IP address of the destination end, and the IP address of the source end.

[0128] Of course, if a Vxlan tunnel is established between a bare metal node in a data center and a bare metal node outside the data center, the transmitted Vxlan message may not include the optional field.

[0129] Of course, if a Vxlan tunnel is established between a gateway device in the data center and a gateway device outside the data center, the optional fields in the transmitted Vxlan message include the IP address of the source end and the IP address of the destination end.

[0130] It should be noted that the above is explained using the Vxlan tunnel established within and outside the data center as an example. Of course, it can also be a tunnel using GENEVE technology established within and outside the data center, or a tunnel using NVGRE technology, or a tunnel using STT technology, etc. When the first RoCE message is converted into a first tunnel transmission message at the tunnel endpoints of these tunnels, the difference from the Vxlan tunnel is that at the Vxlan tunnel endpoint, certain contents of the first RoCE message can be directly modified, while for the tunnel endpoints of the tunnel using GENEVE technology, the tunnel endpoints of the tunnel using NVGRE technology, and the tunnel endpoints of the tunnel using STT technology, the Ethernet header, UDP header, and IP header of the RoCE message are stripped off, and then the encapsulation of the current tunnel is added to obtain the first tunnel transmission message.

[0131] In addition, in this embodiment, the RoCE protocol is explained by taking the RoCEv2 protocol that supports the Ethernet scenario RDMA technology as an example. Of course, the RoCE protocol can also be applied to the RoCEv1 protocol that supports the Ethernet scenario RDMA technology, but RoCEv1 requires the switch to support flow control technologies such as priority flow control (Priority-based Flow Control, PFC). As long as the switch in the Ethernet supports flow control technologies such as PFC, the process transmission RoCE message of the above embodiment can be realized.

[0132] In addition, in this embodiment, an efficient mapping and conversion mechanism for Vxlan messages and RoCE messages is supported, without the need for redundant message encapsulation and nesting, thereby reducing the load space loss of messages caused by multi-layer nested encapsulation and ensuring forwarding performance as much as possible.

[0133] In addition, in this embodiment, only the process of virtual machine A requesting data from virtual machine B and virtual machine B writing data to virtual machine A is described. The process of virtual machine B reading data from virtual machine A is similar to the above process. Both are based on the above principles to achieve communication between virtual machine B and virtual machine A, except that the content in the IB load of the RoCE message is different.

[0134] Figure 8 1 is a structural diagram of a data transmission device provided in an embodiment of the present application. The device can be implemented as part or all of the device through software, hardware, or a combination of both. The device provided in an embodiment of the present application can implement the embodiment of the present application. Figure 4 , Figure 5 The process described above, the device includes: an acquisition module 810, a packaging module 820 and a sending module 830, wherein:

[0135] An acquisition module 810 is used to acquire a first remote direct data access RoCE message based on converged Ethernet, wherein the first RoCE message includes address information of a destination end, and can be specifically used to implement the acquisition function of step 401 and the implicit steps included in step 401;

[0136] The encapsulation module 820 is used to encapsulate the first RoCE message using a target encapsulation format to obtain a first tunnel transmission message, wherein the target encapsulation format is an encapsulation format corresponding to a tunnel established in the data center and outside the data center, and the first tunnel transmission message is a message that encapsulates the payload of the first RoCE message using the target encapsulation format through a mapping conversion mechanism, and can be specifically used to implement the encapsulation function of step 402 and the implicit steps included in step 402;

[0137] The sending module 830 is used to send the first tunnel transmission message outward through the tunnel, so that the opposite network device of the tunnel sends the payload of the first tunnel transmission message to the destination according to the address information of the destination. It can be specifically used to implement the sending function of step 403 and the implicit steps contained in step 403.

[0138] In a possible implementation, the tunnel is a Vxlan tunnel;

[0139] The encapsulation module 820 is used to:

[0140] A Vxlan header is added to the first RoCE message, the source IP address and the destination IP address of the Internet Protocol IP header of the first RoCE message are modified to the local tunnel endpoint IP address of the tunnel and the opposite tunnel endpoint IP address of the tunnel, respectively, and the source Media Control Protocol MAC address and the destination MAC address of the Ethernet header of the first RoCE message are modified to the local tunnel endpoint MAC address of the tunnel and the MAC address of the next-hop device, respectively.

[0141] In a possible implementation manner, the encapsulation module 820 is further used for:

[0142] The redundant detection field and the frame check field of the first RoCE message are deleted.

[0143] In a possible implementation manner, the encapsulation module 820 is further used for:

[0144] Set the destination port of the User Datagram Protocol UDP header of the first tunnel transmission message to the port number corresponding to Vxlan.

[0145] In a possible implementation manner, the source end generating the first RoCE message is a virtual machine, and the destination end is a virtual machine;

[0146] The encapsulation module 820 is further used for:

[0147] An optional field is added to the first RoCE message, wherein the optional field includes the IP address of the destination end and the IP address of the source end.

[0148] In a possible implementation manner, the source end for generating the first RoCE message is a bare metal node, and the destination end is a virtual machine or a bare metal node;

[0149] The encapsulation module 820 is further used for:

[0150] An optional field is added to the first RoCE message, wherein the optional field includes the IP address of the destination.

[0151] In a possible implementation, the acquisition module 810 is further used to receive a second tunnel transmission message, where the second tunnel transmission message is a message that encapsulates the payload of a third RoCE message using a target encapsulation format through a mapping conversion mechanism, and the third RoCE message is a message in which the Vlan number of the Ethernet header is deleted from the RoCE message in the virtual local area network Vlan format;

[0152] The encapsulation module 820 is further configured to perform a reverse conversion on the second tunnel transmission message based on the target encapsulation format to obtain a fourth RoCE message including a payload of the second tunnel transmission message;

[0153] The sending module 830 is further configured to send the fourth RoCE message to the destination end according to the address information of the destination end of the fourth RoCE message.

[0154] In the embodiment of the present application, even if the hardware device in the Ethernet is not replaced, RDMA communication between the outside of the data center and the inside of the data center can be implemented in the Ethernet, and the implementation process is relatively simple.

[0155] The division of modules in the above embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0156] Fig. 9 1 is a structural diagram of a data transmission device provided in an embodiment of the present application. The device can be implemented as part or all of the device through software, hardware, or a combination of both. The device provided in an embodiment of the present application can implement the embodiment of the present application. Figure 4 , Figure 5 The process described above, the device includes: a receiving module 910, a packaging module 920 and a sending module 930, wherein:

[0157] The receiving module 910 is used to receive a first tunnel transmission message through a tunnel, wherein the first tunnel transmission message is a message that encapsulates the payload of a first remote direct data access RoCE message based on converged Ethernet using a target encapsulation format through a mapping conversion mechanism, and the target encapsulation format is an encapsulation format corresponding to a tunnel established in a data center and outside a data center, and can be specifically used to implement the receiving function of step 404 and the implicit steps included in step 404;

[0158] An encapsulation module 920 is used to perform a reverse conversion on the first tunnel transmission message based on the target encapsulation format to obtain a second RoCE message including the payload of the first tunnel transmission message, which can be specifically used to implement the encapsulation function of step 405 and the implicit steps included in step 405;

[0159] The sending module 930 is used to send the second RoCE message to the destination end according to the address information of the destination end of the second RoCE message, and can be specifically used to implement the sending function of step 406 and the implicit steps included in step 406.

[0160] In a possible implementation manner, the tunnel is a Vxlan tunnel; the network between the local tunnel endpoint of the tunnel and the destination end is a Vlan network,

[0161] The encapsulation module 820 is used to:

[0162] Deleting the Vxlan header of the first tunnel transmission message;

[0163] The source IP address and destination IP address of the Internet Protocol IP header of the first tunnel transmission message that deletes the Vxlan header are modified to the IP address of the source end and the IP address of the destination end respectively; according to the stored mapping relationship between the virtual local area network identifier VNI and the Vlan number of the Vxlan virtual local area network, the Vlan number corresponding to the VNI of the Vxlan header is added to the Ethernet header of the first tunnel transmission message that deletes the Vxlan header; the port number of the destination port of the User Datagram Protocol UDP in the first tunnel transmission message that deletes the Vxlan header is modified to a preset port number; the source Media Control Protocol MAC address of the Ethernet header is modified to the MAC address of the local tunnel endpoint, and the destination MAC address of the Ethernet header is modified to the MAC address of the next-hop device.

[0164] In a possible implementation manner, the encapsulation module 920 is further used for:

[0165] Add a redundant detection field and a frame check field to the first tunnel transmission message from which the Vxlan header is deleted.

[0166] In a possible implementation manner, the source end generating the first RoCE message is a virtual machine, and the destination end is a virtual machine;

[0167] The encapsulation module 920 is further used for:

[0168] The IP address of the source end and the IP address of the destination end are obtained in an optional field of the first tunnel transmission message, and the optional field in the first tunnel transmission message is deleted.

[0169] In a possible implementation manner, the source end for generating the first RoCE message is a bare metal node, and the destination end is a virtual machine or a bare metal node;

[0170] The encapsulation module 920 is further used for:

[0171] Obtaining the IP address of the destination end from an optional field of the first tunnel transmission message, and deleting the optional field in the first tunnel transmission message;

[0172] According to the correspondence between the stored VNI, tunnel endpoint IP address, destination IP address and source IP address, determine the source IP address corresponding to the VNI of the Vxlan header, the source IP address of the IP header and the destination IP address in the optional field.

[0173] In a possible implementation, the receiving module 910 is further configured to receive an address resolution protocol ARP request through a tunnel, wherein the ARP request includes an IP address of a destination end, an IP address of a source end, a VNI, and a tunnel endpoint IP address of a tunnel accessed by the source end;

[0174] like Fig.10 As shown, the device also includes:

[0175] The storage module 940 is used to store the correspondence between the VNI, the tunnel endpoint IP address, the source IP address and the destination IP address.

[0176] In a possible implementation, the receiving module 910 is further configured to receive a RoCE message in a Vlan format;

[0177] The encapsulation module 920 is further configured to delete the Vlan number of the Ethernet header in the RoCE message in the Vlan format to obtain a third RoCE message; convert the third RoCE message into a message encapsulated using the target encapsulation format through a mapping conversion mechanism to obtain a second tunnel transmission message, wherein the second tunnel transmission message is a message that encapsulates the payload of the third RoCE message using the target encapsulation format through a mapping conversion mechanism;

[0178] The sending module 930 is further configured to send the second tunnel transmission message outward through the tunnel, so that the opposite end network device of the tunnel sends the payload of the second tunnel transmission message to the destination end indicated by the destination address information in the third RoCE message.

[0179] In the embodiment of the present application, even if the hardware device in the Ethernet is not replaced, RDMA communication between the outside of the data center and the inside of the data center can be implemented in the Ethernet, and the implementation process is relatively simple.

[0180] The division of modules in the above embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0181] It should be noted that: the data transmission device provided in the above embodiment only uses the division of the above functional modules as an example when transmitting data. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the data transmission device provided in the above embodiment and the data transmission method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0182] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a server or terminal, the process or function described in the embodiment of the present application is generated in whole or in part. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a server or terminal or a data storage device such as a server or data center that includes one or more available media integration. The available medium can be a magnetic medium (such as a floppy disk, a hard disk and a tape, etc.), or an optical medium (such as a digital video disk (Digital Video Disk, DVD), etc.), or a semiconductor medium (such as a solid-state hard disk, etc.).

[0183] The above description is only an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for transmitting data, characterized in that: The method comprises: Acquire a first remote direct data access RoCE message based on converged Ethernet, wherein the first RoCE message includes address information of a destination end; encapsulating the first RoCE message using a target encapsulation format to obtain a first tunnel transmission message, wherein the target encapsulation format is an encapsulation format corresponding to a tunnel established in a data center and outside a data center, and the first tunnel transmission message is a message obtained by encapsulating a payload of the first RoCE message using the target encapsulation format through a mapping conversion mechanism; The first tunnel transmission message is sent outward through the tunnel, so that the opposite end network device of the tunnel sends the payload of the first tunnel transmission message to the destination end according to the address information of the destination end.

2. The method according to claim 1, characterized in that The tunnel is a virtual local area network Vxlan tunnel; The encapsulation using the target encapsulation format includes: A Vxlan header is added to the first RoCE message, the source IP address and the destination IP address of the Internet Protocol IP header of the first RoCE message are modified to the local tunnel endpoint IP address of the tunnel and the opposite tunnel endpoint IP address of the tunnel, respectively, and the source Media Control Protocol MAC address and the destination MAC address of the Ethernet header of the first RoCE message are modified to the local tunnel endpoint MAC address of the tunnel and the MAC address of the next-hop device, respectively.

3. The method according to claim 2, characterized in that The encapsulation using the target encapsulation format also includes: The redundant detection field and the frame check field of the first RoCE message are deleted.

4. The method according to claim 2 or 3, characterized in that: The encapsulation using the target encapsulation format also includes: The destination port of the User Datagram Protocol UDP header of the first RoCE message is set to the port number corresponding to Vxlan.

5. The method according to claim 2 or 3, characterized in that: The source end generating the first RoCE message is a virtual machine, and the destination end is a virtual machine; The encapsulation using the target encapsulation format also includes: An optional field is added to the first RoCE message, wherein the optional field includes the IP address of the destination end and the IP address of the source end.

6. The method according to claim 2 or 3, characterized in that: The source end for generating the first RoCE message is a bare metal node, and the destination end is a virtual machine or a bare metal node; The encapsulation using the target encapsulation format also includes: An optional field is added to the first RoCE message, wherein the optional field includes the IP address of the destination.

7. The method according to claim 2 or 3, characterized in that: The method further comprises: Receive a second tunnel transmission message, wherein the second tunnel transmission message is a message that encapsulates the payload of a third RoCE message using a target encapsulation format through a mapping conversion mechanism, and the third RoCE message is a message in which a Vlan number of an Ethernet header is deleted from a RoCE message in a virtual local area network Vlan format; Based on the target encapsulation format, reversely convert the second tunnel transmission message to obtain a fourth RoCE message including the payload of the second tunnel transmission message; Send the fourth RoCE message to the destination end according to the address information of the destination end of the fourth RoCE message.

8. A method for transmitting data, characterized in that: The method comprises: Receiving a first tunnel transmission message through a tunnel, wherein the first tunnel transmission message is a message that encapsulates a payload of a first remote direct data access RoCE message based on converged Ethernet using a target encapsulation format through a mapping conversion mechanism, and the target encapsulation format is an encapsulation format corresponding to a tunnel established within a data center and outside a data center; Based on the target encapsulation format, reversely convert the first tunnel transmission message to obtain a second RoCE message including the payload of the first tunnel transmission message; The second RoCE message is sent to the destination end according to the address information of the destination end of the second RoCE message.

9. The method according to claim 8, characterized in that The tunnel is a virtual local area network (Vxlan) tunnel; the network between the local tunnel endpoint of the tunnel and the destination end is a virtual local area network (Vlan) network; The performing reverse conversion on the first tunnel transmission message based on the target encapsulation format includes: Deleting the Vxlan header of the first tunnel transmission message; The source IP address and destination IP address of the Internet Protocol IP header of the first tunnel transmission message that deletes the Vxlan header are modified to the IP address of the source end and the IP address of the destination end respectively; according to the stored mapping relationship between the virtual local area network identifier VNI of the Vxlan and the Vlan number, the Vlan number corresponding to the VNI of the Vxlan header is added to the Ethernet header of the first tunnel transmission message that deletes the Vxlan header; the port number of the destination port of the User Datagram Protocol UDP in the first tunnel transmission message that deletes the Vxlan header is modified to a preset port number; the source Media Control Protocol MAC address of the Ethernet header is modified to the MAC address of the local tunnel endpoint, and the destination MAC address of the Ethernet header is modified to the MAC address of the next-hop device.

10. The method according to claim 9, characterized in that The performing reverse conversion on the first tunnel transmission message based on the target encapsulation format further includes: Add a redundant detection field and a frame check field to the first tunnel transmission message from which the Vxlan header is deleted.

11. The method according to claim 9 or 10, characterized in that: The source end generating the first RoCE message is a virtual machine, and the destination end is a virtual machine; The performing reverse conversion on the first tunnel transmission message based on the target encapsulation format further includes: The IP address of the source end and the IP address of the destination end are obtained in an optional field of the first tunnel transmission message, and the optional field in the first tunnel transmission message is deleted.

12. The method according to claim 9 or 10, characterized in that: The source end for generating the first RoCE message is a bare metal node, and the destination end is a virtual machine or a bare metal node; The performing reverse conversion on the first tunnel transmission message based on the target encapsulation format further includes: Obtaining the IP address of the destination end from an optional field of the first tunnel transmission message, and deleting the optional field in the first tunnel transmission message; According to the correspondence between the stored VNI, tunnel endpoint IP address, destination IP address and source IP address, determine the source IP address corresponding to the VNI of the Vxlan header, the source IP address of the IP header and the destination IP address in the optional field.

13. The method according to claim 12, characterized in that The method further comprises: Receiving an Address Resolution Protocol ARP request through a tunnel, wherein the ARP request includes an IP address of a destination end, an IP address of a source end, a VNI, and a tunnel endpoint IP address of a tunnel accessed by the source end; Stores the correspondence between the VNI, the tunnel endpoint IP address, the source IP address, and the destination IP address.

14. The method according to claim 9 or 10, characterized in that The method further comprises: Receive RoCE messages in Vlan format; Deleting the Vlan number of the Ethernet header in the RoCE message in the Vlan format to obtain a third RoCE message; Convert the third RoCE message into a message encapsulated using the target encapsulation format through a mapping conversion mechanism to obtain a second tunnel transmission message, wherein the second tunnel transmission message is a message that encapsulates the payload of the third RoCE message using the target encapsulation format through a mapping conversion mechanism; The second tunnel transmission message is sent outward through the tunnel, so that the opposite end network device of the tunnel sends the payload of the second tunnel transmission message to the destination end indicated by the destination address information in the third RoCE message.

15. A device for transmitting data, characterized in that: The device comprises: An acquisition module, configured to acquire a first remote direct data access RoCE message based on converged Ethernet, wherein the first RoCE message includes address information of a destination end; an encapsulation module, configured to encapsulate the first RoCE message using a target encapsulation format to obtain a first tunnel transmission message, wherein the target encapsulation format is an encapsulation format corresponding to a tunnel established in a data center and outside a data center, and the first tunnel transmission message is a message in which a payload of the first RoCE message is encapsulated using the target encapsulation format through a mapping conversion mechanism; The sending module is used to send the first tunnel transmission message outward through the tunnel, so that the opposite end network device of the tunnel sends the payload of the first tunnel transmission message to the destination end according to the address information of the destination end.

16. The device according to claim 15, characterized in that The tunnel is a virtual local area network Vxlan tunnel; The packaging module is used for: A Vxlan header is added to the first RoCE message, the source IP address and the destination IP address of the Internet Protocol IP header of the first RoCE message are modified to the local tunnel endpoint IP address of the tunnel and the opposite tunnel endpoint IP address of the tunnel, respectively, and the source Media Control Protocol MAC address and the destination MAC address of the Ethernet header of the first RoCE message are modified to the local tunnel endpoint MAC address of the tunnel and the MAC address of the next-hop device, respectively.

17. The device according to claim 16, characterized in that The encapsulation module is further used for: The redundant detection field and the frame check field of the first RoCE message are deleted.

18. The device according to claim 16 or 17, characterized in that The encapsulation module is further used for: The destination port of the User Datagram Protocol UDP header of the first RoCE message is set to the port number corresponding to Vxlan.

19. The device according to claim 16 or 17, characterized in that The source end generating the first RoCE message is a virtual machine, and the destination end is a virtual machine; The encapsulation module is further used for: An optional field is added to the first RoCE message, wherein the optional field includes the IP address of the destination end and the IP address of the source end.

20. The device according to claim 16 or 17, characterized in that The source end for generating the first RoCE message is a bare metal node, and the destination end is a virtual machine or a bare metal node; The encapsulation module is further used for: An optional field is added to the first RoCE message, wherein the optional field includes the IP address of the destination.

21. The device according to claim 16 or 17, characterized in that The acquisition module is further used to receive a second tunnel transmission message, wherein the second tunnel transmission message is a message that encapsulates the payload of the third RoCE message using the target encapsulation format through a mapping conversion mechanism, and the third RoCE message is a message in which the Vlan number of the Ethernet header is deleted in the RoCE message in the virtual local area network Vlan format; The encapsulation module is further used to perform inverse conversion on the second tunnel transmission message based on the target encapsulation format to obtain a fourth RoCE message including the payload of the second tunnel transmission message; The sending module is further configured to send the fourth RoCE message to the destination end according to the address information of the destination end of the fourth RoCE message.

22. A device for transmitting data, characterized in that: The device comprises: A receiving module, configured to receive a first tunnel transmission message through a tunnel, wherein the first tunnel transmission message is a message that encapsulates a payload of a first remote direct data access RoCE message based on converged Ethernet using a target encapsulation format through a mapping conversion mechanism, and the target encapsulation format is an encapsulation format corresponding to a tunnel established within a data center and outside a data center; an encapsulation module, configured to perform a reverse conversion on the first tunnel transmission message based on the target encapsulation format to obtain a second RoCE message including a payload of the first tunnel transmission message; A sending module is used to send the second RoCE message to the destination end according to the address information of the destination end of the second RoCE message.

23. The device according to claim 22, characterized in that The tunnel is a virtual local area network (Vxlan) tunnel; the network between the local tunnel endpoint of the tunnel and the destination end is a virtual local area network (Vlan) network; The packaging module is used for: Deleting the Vxlan header of the first tunnel transmission message; The source IP address and destination IP address of the Internet Protocol IP header of the first tunnel transmission message from which the Vxlan header is deleted are modified to the IP address of the source end and the IP address of the destination end respectively; according to the stored mapping relationship between the virtual local area network identifier VNI and the Vlan number of the Vxlan virtual local area network, the Vlan number corresponding to the VNI of the Vxlan header is added to the Ethernet header of the first tunnel transmission message from which the Vxlan header is deleted, the source Media Control Protocol MAC address of the Ethernet header is modified to the MAC address of the local tunnel endpoint, and the destination MAC address of the Ethernet header is modified to the MAC address of the next-hop device.

24. The device according to claim 23, characterized in that The encapsulation module is further used for: Add a redundant detection field and a frame check field to the first tunnel transmission message from which the Vxlan header is deleted.

25. The device according to claim 23 or 24, characterized in that The source end generating the first RoCE message is a virtual machine, and the destination end is a virtual machine; The encapsulation module is further used for: The IP address of the source end and the IP address of the destination end are obtained in an optional field of the first tunnel transmission message, and the optional field in the first tunnel transmission message is deleted.

26. The device according to claim 23 or 24, characterized in that The source end for generating the first RoCE message is a bare metal node, and the destination end is a virtual machine or a bare metal node; The encapsulation module is further used for: Obtaining the IP address of the destination end from an optional field of the first tunnel transmission message, and deleting the optional field in the first tunnel transmission message; According to the correspondence between the stored VNI, tunnel endpoint IP address, destination IP address and source IP address, determine the source IP address corresponding to the VNI of the Vxlan header, the source IP address of the IP header and the destination IP address in the optional field.

27. The device according to claim 26, characterized in that The receiving module is further used to receive an address resolution protocol ARP request through a tunnel, wherein the ARP request includes an IP address of a destination end, an IP address of a source end, a VNI, and a tunnel endpoint IP address of a tunnel accessed by the source end; The device also includes: The storage module is used to store the correspondence between the VNI, the tunnel endpoint IP address, the source IP address and the destination IP address.

28. The device according to claim 23 or 24, characterized in that The receiving module is further used to receive the RoCE message in Vlan format; The encapsulation module is further used to delete the Vlan number of the Ethernet header in the RoCE message in the Vlan format to obtain a third RoCE message; convert the third RoCE message into a message encapsulated using the target encapsulation format through a mapping conversion mechanism to obtain a second tunnel transmission message, wherein the second tunnel transmission message is a message that encapsulates the payload of the third RoCE message using the target encapsulation format through a mapping conversion mechanism; The sending module is also used to send the second tunnel transmission message outward through the tunnel, so that the opposite end network device of the tunnel sends the payload of the second tunnel transmission message to the destination end indicated by the destination address information in the third RoCE message.

29. A computing device for transmitting data, characterized in that The computing device comprises a processor and a memory, wherein: The memory stores computer instructions; The processor executes the computer instructions so that the computing device implements the method described in any one of claims 1 to 7, or the computing device implements the function of the apparatus described in any one of claims 15 to 21.

30. A computing device for transmitting data, characterized in that The computing device comprises a processor and a memory, wherein: The memory stores computer instructions; The processor executes the computer instructions so that the computing device implements the method described in any one of claims 8 to 14, or the computing device implements the function of the apparatus described in any one of claims 22 to 28.

31. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, which instruct a computing device to execute the method described in any one of claims 1 to 7, or the computer instructions instruct the computing device to deploy the apparatus described in any one of claims 15 to 21.

32. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, which instruct a computing device to execute the method described in any one of claims 8 to 14, or the computer instructions instruct the computing device to deploy the apparatus described in any one of claims 22 to 28.