CN108390812B - Message forwarding method and device - Google Patents

Message forwarding method and device Download PDF

Info

Publication number
CN108390812B
CN108390812B CN201810542714.3A CN201810542714A CN108390812B CN 108390812 B CN108390812 B CN 108390812B CN 201810542714 A CN201810542714 A CN 201810542714A CN 108390812 B CN108390812 B CN 108390812B
Authority
CN
China
Prior art keywords
container
address
message
gre
data message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810542714.3A
Other languages
Chinese (zh)
Other versions
CN108390812A (en
Inventor
孟宪军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Information Technologies Co Ltd
Original Assignee
Hangzhou H3C Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou H3C Technologies Co Ltd filed Critical Hangzhou H3C Technologies Co Ltd
Priority to CN201810542714.3A priority Critical patent/CN108390812B/en
Publication of CN108390812A publication Critical patent/CN108390812A/en
Application granted granted Critical
Publication of CN108390812B publication Critical patent/CN108390812B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4633Interconnection of networks using encapsulation techniques, e.g. tunneling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing

Abstract

The disclosure relates to a message forwarding method and device. The method is applied to a first Virtual Machine (VM), a GRE tunnel is established between the first VM and remote routing switching equipment, and the method comprises the following steps: when a GRE message is received, identifying a reserved field of a GRE message header, wherein the reserved field is used for carrying an IP address of a container deployed in a VM (virtual machine); if the reserved field comprises the IP address of the container, acquiring the IP address of the container; decapsulating the GRE message to obtain a first data message; when the VM deploying the container is the first VM, the first data message is forwarded according to the IP address of the container, so that the router in one site can communicate with the container deployed in the VM in another site through a GRE tunnel.

Description

Message forwarding method and device
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for forwarding a packet.
Background
The Generic Routing Encapsulation (GRE) protocol is used to encapsulate data packets of some network layer protocols, so that the encapsulated data packets can be transmitted in another network layer protocol. The path of the GRE message transmitted in the network is called a GRE tunnel. The GRE tunnel is a virtual point-to-point connection, and the devices at both ends encapsulate and decapsulate data packets respectively. The network layer Protocol may include a network Protocol (IP), an Internet packet switching Protocol (IPX), a Multi-Protocol label switching (MPLS) Protocol, and the like.
In the related art, in a cloud computing network, multiple hosts may be deployed at each site in different areas, and multiple Virtual Machines (VM) may be created in each host. Fig. 1 illustrates a networking diagram of a cloud computing network in the related art. As shown in fig. 1, if a router in site a wants to access each VM in site B, multiple pieces of traffic need to be created, and the increase in the amount of traffic puts a great strain on network maintenance and security management. Therefore, the GRE tunnel can be adopted to reach each station, and the data message is encapsulated in the GRE tunnel for transmission.
Disclosure of Invention
In view of this, the present disclosure provides a message forwarding method and apparatus, so as to solve the problem in the related art that a router in one site cannot communicate with a container deployed in a VM in another site through a GRE tunnel.
According to an aspect of the present disclosure, a packet forwarding method is provided, where the method is applied to a first virtual machine VM, and a GRE tunnel is established between the first VM and a remote routing switch device, where the method includes:
when a GRE message is received, identifying a reserved field of a GRE message header, wherein the reserved field is used for carrying an IP address of a container deployed in a VM (virtual machine);
if the reserved field comprises the IP address of the container, acquiring the IP address of the container;
decapsulating the GRE message to obtain a first data message;
and when the VM deploying the container is the first VM, forwarding the first data message according to the IP address of the container.
According to another aspect of the present disclosure, a packet forwarding method is provided, which is applied to a host, where the host establishes a GRE tunnel with a remote routing switch device, and a VM is created in the host, where the method includes:
when a GRE message is received, identifying a reserved field of a GRE message header, wherein the reserved field is used for carrying an IP address of a container deployed in a VM (virtual machine);
if the reserved field comprises the IP address of the container, acquiring the IP address of the container;
decapsulating the GRE message to obtain a first data message;
and sending the first data message and the IP address of the container to the VM which deploys the container, so that the VM which deploys the container forwards the first data message according to the IP address of the container.
According to another aspect of the present disclosure, a packet forwarding method is provided, which is applied to a routing switching device, where the routing switching device and a remote device establish a GRE tunnel, and the method includes:
when an original data message is received or generated according to a message generation instruction, if a receiver of the original data message is determined to be a container deployed in a VM according to a destination IP address of the original data message, acquiring the IP address of the VM deployed in the container;
replacing the target IP address of the original data message with the IP address of the VM to obtain a corresponding first data message;
carrying out GRE encapsulation on the first data message to obtain a GRE message; wherein, the reserved field of the GRE message header carries the IP address of the container;
and forwarding the GRE message through the GRE tunnel.
According to another aspect of the present disclosure, a packet forwarding apparatus is provided, where the packet forwarding apparatus is applied to a first virtual machine VM, and a GRE tunnel is established between the first VM and a remote routing switch device, the apparatus includes:
the identification module is used for identifying a reserved field of a GRE message header when the GRE message is received, wherein the reserved field is used for carrying an IP address of a container deployed in a VM (virtual machine);
a first obtaining module, configured to obtain an IP address of a container if the reserved field includes the IP address of the container;
the decapsulation module is used for decapsulating the GRE message to obtain a first data message;
and the first forwarding module is used for forwarding the first data message according to the IP address of the container when the VM in which the container is deployed is the first VM.
According to another aspect of the present disclosure, there is provided a packet forwarding apparatus, which is applied to a host, where a GRE tunnel is established between the host and a remote routing switch device, and a VM is created in the host, the apparatus including:
the identification module is used for identifying a reserved field of a GRE message header when the GRE message is received, wherein the reserved field is used for carrying an IP address of a container deployed in a VM (virtual machine);
a first obtaining module, configured to obtain an IP address of a container if the reserved field includes the IP address of the container;
the decapsulation module is used for decapsulating the GRE message to obtain a first data message;
and the first forwarding module is used for sending the first data message and the IP address of the container to the VM which deploys the container, and is used for enabling the VM which deploys the container to forward the first data message according to the IP address of the container.
According to another aspect of the present disclosure, a packet forwarding apparatus is provided, which is applied to a routing switching device, where the routing switching device and a remote device establish a GRE tunnel, and the apparatus includes:
the second obtaining module is used for obtaining the IP address of the VM where the container is deployed if the receiver of the original data message is determined to be the container deployed in the VM according to the destination IP address of the original data message when the original data message is received or the original data message is generated according to the message generation instruction;
the replacing module is used for replacing the target IP address of the original data message with the IP address of the VM to obtain a corresponding first data message;
the encapsulation module is used for carrying out GRE encapsulation on the first data message to obtain a GRE message; wherein, the reserved field of the GRE message header carries the IP address of the container;
and the sending module is used for forwarding the GRE message through the GRE tunnel.
The message forwarding method and the device identify the reserved field of the header of the GRE message when the GRE message is received, acquire the IP address of the container if the reserved field comprises the IP address of the container, decapsulate the GRE message to obtain the first data message, and forward the first data message according to the IP address of the container, so that a router in one site can communicate with the container deployed in a VM in another site through a GRE tunnel.
Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.
Fig. 1 illustrates a networking diagram of a cloud computing network in the related art.
Fig. 2 is a schematic diagram illustrating a GRE packet in the related art.
Fig. 3 is a diagram illustrating a GRE packet according to an embodiment of the present disclosure.
Fig. 4 illustrates a networking diagram of a cloud computing network in the related art.
Fig. 5 illustrates a networking schematic of a cloud computing network according to an embodiment of the present disclosure.
Fig. 6 shows a flowchart of a packet forwarding method according to an embodiment of the present disclosure.
Fig. 7 shows a schematic diagram of a GRE header according to an embodiment of the present disclosure.
Fig. 8 shows a flowchart of a packet forwarding method according to an embodiment of the present disclosure.
Fig. 9 shows a flowchart of a packet forwarding method according to an embodiment of the present disclosure.
Fig. 10 shows a flowchart of a packet forwarding method according to an embodiment of the present disclosure.
Fig. 11 shows a block diagram of a message forwarding device according to an embodiment of the present disclosure.
Fig. 12 shows a block diagram of a message forwarding device according to an embodiment of the present disclosure.
Fig. 13 shows a block diagram of a message forwarding device according to an embodiment of the present disclosure.
Fig. 14 shows a block diagram of a message forwarding device according to an embodiment of the present disclosure.
Detailed Description
Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present invention, a brief description will be given below of some technical terms involved in the embodiments of the present invention.
Fig. 2 is a schematic diagram illustrating a GRE packet in the related art. As shown in fig. 2:
payload data (English: Payload Packet): data messages need to be encapsulated and transmitted. The Protocol type of payload data is called Passenger Protocol (english). The passenger protocol may be any network layer protocol.
GRE Header (English: GRE Header): and the message header added by encapsulating the payload data by adopting the GRE protocol comprises the contents of the number of encapsulating layers, the version, the passenger protocol type, the check sum information, the Key information and the like. The GRE Protocol, which encapsulates payload data, is called the Encapsulation Protocol (english).
Transport protocol Header (English: Delivery Header): and a message header is added to the GRE message so that the transmission protocol can forward the GRE message. The transport Protocol (english: Delivery Protocol) refers to a network layer Protocol responsible for forwarding the GRE packet. The device supports both IPv4 and IPv6 transport protocols. When the transmission protocol is IPv4, the GRE tunnel is called GRE over IPv4 tunnel; when the transport protocol is IPv6, the GRE tunnel is referred to as a GREover IPv6 tunnel.
In order to make the messages described in the following embodiments unambiguous, the messages involved in the embodiments of the present disclosure are described in the present disclosure:
in this disclosure, a GRE message refers to: and encapsulating the GRE message header and the data message after the transmission protocol message header. As shown in fig. 3, if the passenger protocol is IP, the GRE packet includes an outer IP packet header, a GRE packet header, an inner IP packet header, and a data portion.
Original data message: if the passenger protocol is the IP protocol, the original data message is the IP message. As shown in fig. 3, the original data packet includes an inner IP packet header and a data portion, and the destination IP address of the inner IP packet header is the IP address of the container deployed in the VM. That is, the receiver of the original data packet is a container deployed in the VM.
Fig. 4 illustrates a networking diagram of a cloud computing network in the related art. As shown in fig. 4, a router exists in site a and a host exists in site B. Multiple VMs, such as VM1, VM2, and VM3, may be created in the hosts in site B. Wherein the IP address of the router is 1.1.1.1, the IP address of the host is 2.2.2.2, the IP address of VM1 is 3.3.3.1, the IP address of VM2 is 3.3.3.2, and the IP address of VM3 is 3.3.3.3.
As shown in fig. 4, the GRE tunnel is established between the router in the site a and the host in the site B, i.e. the GRE tunnel portal is configured on the router and the host, respectively. For example, the IP address of the GRE tunnel port on the router is 10.1.1.1, and the IP address of the GRE tunnel port on the host is 11.1.1.1. If the IP message is sent from the router to the VM2 in the host, the source IP address is the IP address 1.1.1.1 of the router and the destination IP address is the IP address 3.3.3.2 of the VM2 in the inner IP message header of the IP message.
As shown in fig. 4, the IP packet traverses the IP network through the GRE tunnel, and needs to go through two processes, i.e., encapsulation and decapsulation. The encapsulation process is as follows: the router encapsulates the GRE message header and the outer layer IP message header to the IP message to obtain the GRE message. In the outer layer IP header of the GRE packet, the source IP address is the IP address 10.1.1.1 of the GRE tunnel portal on the router, and the destination IP address is the IP address 11.1.1.1 of the GRE tunnel portal on the host. The router sends the GRE message through the GRE tunnel, and the host receives the GRE message. The decapsulation process is as follows: the host strips off the outer layer IP message header and the GRE message header included in the GRE message to obtain the IP message.
It should be noted that those skilled in the art can understand that the establishment of the GRE tunnel has diversity. As shown in fig. 4, the GRE tunnel may be established between the router and the host, or between the VM1, VM2, or VM3 in the router and the host, which is not limited by the present disclosure.
Currently, with the continuous development of cloud computing networks, the functional requirements of VMs are increasing. For example, containers may be deployed in VMs, the containers deployed in VMs belonging to the same subnet. However, since only one destination IP address can be encapsulated in the header of the inner IP packet, the IP packet can only reach the VM and cannot reach the container deployed in the VM, so that the router in one site cannot communicate with the container deployed in the VM in another site through the GRE tunnel.
Fig. 5 illustrates a networking schematic of a cloud computing network according to an embodiment of the present disclosure. Fig. 5 is a schematic example of the packet forwarding method according to the embodiment of the present disclosure shown in fig. 6, 8, 9, and 10. In addition, in the embodiments corresponding to fig. 6, 8, 9, and 10, the passenger protocol is schematically exemplified as the IP protocol.
As shown in fig. 5, there is a router in site a and a host in site B. Multiple VMs may be created in a host in site B, for example VM1, VM2, and VM3 are created in the host. One or more containers may be deployed in each VM, the containers deployed in each VM belonging to the same subnet. For example, container 1 is deployed in VM1, container 1 belonging to subnet 1; container 2 and container 3 are deployed in VM2, container 2 and container 3 belonging to subnet 2; container 4 and container 5 are deployed in VM3, and container 4 and container 5 belong to subnet 3.
The IP address of the router is 1.1.1.1, the IP address of the host is 2.2.2, the IP address of the VM1 is 3.3.3.1, the IP address of the container 1 is 4.4.4.1, the IP address of the VM2 is 3.3.3.2, the IP address of the container 2 is 4.4.4.2, the IP address of the container 3 is 4.4.4.3, the IP address of the VM3 is 3.3.3.3, the IP address of the container 4 is 4.4.4, and the IP address of the container 5 is 4.4.4.5.
Fig. 6 shows a flowchart of a packet forwarding method according to an embodiment of the present disclosure. The method is applied to a first VM, and a GRE tunnel is established between the first VM and a remote routing switching device. As shown in fig. 6, the message forwarding method includes steps S11 to S14.
In step S11, upon receiving the GRE packet, a reserved field of the header of the GRE packet is identified, where the reserved field is used to carry an IP address of a container deployed in the VM.
The routing switch device may be a Router or a Virtual Router (VSR), which is not limited in this disclosure.
Fig. 7 shows a schematic diagram of a GRE header according to an embodiment of the present disclosure. As shown in fig. 7, in the related art, the GRE header may include fields such as recursive control (Recur), flag bits (Flags), version (Ver), protocol type (procollType), Checksum (Checksum), offset (offset), Key (Key), Sequence Number (Sequence Number), and Routing (Routing).
In one implementation, the reserved field of the GRE header may be an existing field included in the GRE header. For example, the reserved field of the GRE header is a checksum field and an offset field included in the GRE header.
It can be understood that, since the checksum field and the offset field are adjacent fields, and both the checksum field and the offset field are optional fields, and the field lengths thereof are 2 bytes, the checksum field and the offset field can be taken as a reserved field as a whole, and the reserved field has a length of 4 bytes, which is the same as the IP address of the container, and can be used for encapsulating the IP address of the container.
It should be noted that, although the reserved field of the GRE header is described by taking the checksum field and the offset field as an example of the reserved field as a whole, those skilled in the art will understand that the disclosure should not be limited thereto. Those skilled in the art can flexibly set the reserved field of the GRE message header according to the actual application scene.
In one implementation, the container deployed in the VM is a Docker container deployed in the VM.
It should be noted that, although the container deployed in the VM is described by taking the Docker container deployed in the VM as an example, the skilled person can understand that the disclosure should not be limited thereto. Those skilled in the art can flexibly set the containers deployed in the VM according to the actual application scenario, that is, other devices that may be deployed in the VM and belong to the same subnet are applicable in the present disclosure.
In step S12, if the reserved field includes the IP address of the container, the IP address of the container is acquired.
In step S13, the GRE packet is decapsulated to obtain a first data packet.
In step S14, when the VM deploying the container is the first VM, the first data packet is forwarded according to the IP address of the container.
In one implementation, forwarding the first data packet according to the IP address of the container (step S14), includes: replacing the destination IP address of the first data message with the container IP address to obtain a corresponding original data message; and forwarding the original data message according to the destination IP address of the original data message.
As an example, as shown in fig. 5, a GRE tunnel is established between the router in site a and the VM3 in site B, i.e., a GRE tunnel port is configured on the router and the VM3, respectively. If the router in the site a communicates with the container 5 deployed in the VM3 in the site B, when the GRE message is sent from the router to the VM3, the process of the VM3 on the GRE message is as follows:
as shown in fig. 5, the VM3 receives a GRE packet sent by a router through a GRE tunnel. VM3 identifies the reserved field of the GRE header. The reserved field includes the IP address 4.4.4.5 of the container, then VM3 obtains the IP address 4.4.4.5 of the container (i.e., the IP address of container 5). The VM3 strips off the outer IP header and the GRE header included in the GRE packet, to obtain a first data packet. In this embodiment, a data packet is taken as an IP packet for example. The first data packet is an IP packet 1 obtained after the VM3 decapsulates the outer IP header of the GRE packet and the GRE packet header. The destination IP address of IP message 1 is 3.3.3.3 (i.e., the IP address of VM 3). The VM3 determines that the VM deploying the container 5 is the VM3 for establishing the GRE tunnel according to the destination IP address 3.3.3.3 of the IP packet 1, that is, the container 5 is deployed on the VM 3. Therefore, the VM3 replaces the destination IP address 3.3.3.3 of the IP packet 1 with 4.4.4.5, and obtains the original IP packet corresponding to the IP packet 1. VM3 forwards the original IP packet, i.e., sends the original IP packet to container 5.
In one implementation, the method further comprises: if the reserved field does not comprise the IP address of the container, decapsulating the GRE message to obtain a second data message included in the GRE message; and forwarding the second data message according to the destination IP address of the second data message.
As an example, as shown in fig. 5, the VM3 receives a GRE message sent by a router through a GRE tunnel. VM3 identifies the reserved field of the GRE header. The reserved field does not include the IP address of the container. The VM3 strips off the outer IP header and the GRE header included in the GRE packet, and obtains a second data packet. In this embodiment, a data packet is taken as an IP packet for example. The second data packet is an IP packet 4 obtained after the VM3 decapsulates the outer IP header of the GRE packet and the GRE packet header. If the destination IP address of the IP packet 4 is 3.3.3.2 (i.e., the IP address of the VM 2), the VM3 forwards the IP packet 4, i.e., sends the IP packet 4 to the VM 2.
The message forwarding method disclosed by the invention carries the IP address of the container deployed in the first VM through the reserved field of the header of the GRE message, acquires the IP address of the container when the first VM which establishes the GRE tunnel receives the GRE message, and forwards the data message obtained by decapsulating the GRE message according to the IP address of the container, thereby realizing the communication between the routing exchange equipment in one site and the container deployed in the VM in another site through the GRE tunnel.
Fig. 8 shows a flowchart of a packet forwarding method according to an embodiment of the present disclosure. The method is applied to a first VM, and a GRE tunnel is established between the first VM and a remote routing switching device. As shown in fig. 8, the message forwarding method includes steps S11 to S15.
In step S11, upon receiving the GRE packet, a reserved field of the header of the GRE packet is identified, where the reserved field is used to carry an IP address of a container deployed in the VM.
In step S12, if the reserved field includes the IP address of the container, the IP address of the container is acquired.
In step S13, the GRE packet is decapsulated to obtain a first data packet.
In step S14, when the VM deploying the container is the first VM, the first data packet is forwarded according to the IP address of the container.
In step S15, when the VM deploying the container is another VM other than the first VM, the VM deploying the container sends the first data packet and the IP address of the container to the VM deploying the container, so that the VM deploying the container forwards the first data packet according to the IP address of the container.
In one implementation, forwarding the first data packet according to the IP address of the container (step S15), includes: replacing the destination IP address of the first data message with the container IP address to obtain a corresponding original data message; and forwarding the original data message according to the destination IP address of the original data message.
As an example, as shown in fig. 5, a GRE tunnel is established between the router in site a and the VM3 in site B, i.e., a GRE tunnel port is configured on the router and the VM3, respectively. If the router in the site a communicates with the container 3 deployed in the VM2 in the site B, when the GRE message is sent from the router to the VM3, the processing procedure of the VM3 on the GRE message is as follows:
as shown in fig. 5, the VM3 receives a GRE packet sent by a router through a GRE tunnel. VM3 identifies the reserved field of the GRE header. The reserved field includes the IP address 4.4.4.3 of the container, then VM3 obtains the IP address 4.4.4.3 of the container (i.e., the IP address of container 3). The VM3 strips off the outer IP header and the GRE header included in the GRE packet, to obtain a first data packet. In this embodiment, a data packet is taken as an IP packet for example. The first data packet is an IP packet 2 obtained after the VM3 decapsulates the outer IP header of the GRE packet and the GRE packet header. The destination IP address of IP packet 2 is 3.3.3.2 (i.e., the IP address of VM 2). The VM3 determines that the VM deploying the container 3 is a VM other than the VM3 establishing the GRE tunnel according to the destination IP address 3.3.3.2 of the IP packet 2, that is, the container 3 is deployed on the VM 2. Whereby VM3 sends IP packet 2 and IP address 4.4.4.3 to VM 2. The VM2 receives the IP packet 2 and the IP address 4.4.4.3, and replaces the destination IP address 3.3.3.2 of the IP packet 2 with 4.4.4.3 to obtain the original IP packet corresponding to the IP packet 2. VM2 forwards the original IP packet, i.e., sends the original IP packet to container 3.
The message forwarding method disclosed by the invention carries the IP address of the container deployed in the second VM through the reserved field of the header of the GRE message, and when the first VM establishing the GRE tunnel receives the GRE message, the IP address of the container is obtained, and the data message obtained by decapsulating the GRE message and the IP address of the container are sent to the second VM, so that the second VM forwards the data message according to the IP address of the container, and therefore, the communication between the routing exchange equipment in one site and the container deployed in the VM in another site through the GRE tunnel can be realized.
Fig. 9 shows a flowchart of a packet forwarding method according to an embodiment of the present disclosure. The method is applied to a host, a GRE tunnel is established between the host and remote routing switching equipment, and a VM is established in the host. As shown in fig. 9, the message forwarding method includes steps S21 to S24.
In step S21, upon receiving the GRE packet, a reserved field of the header of the GRE packet is identified, where the reserved field is used to carry an IP address of a container deployed in the VM.
In step S22, if the reserved field includes the IP address of the container, the IP address of the container is acquired.
In step S23, the GRE packet is decapsulated to obtain a first data packet.
In step S24, the first data packet and the IP address of the container are sent to the VM deploying the container, so that the VM deploying the container forwards the first data packet according to the IP address of the container.
In one implementation, the reserved field of the GRE header may be an existing field included in the GRE header. For example, the reserved field of the GRE header is a checksum field and an offset field included in the GRE header. Reference may be made to the description of this section to the embodiment shown in fig. 6.
In one implementation, the container deployed in the VM is a Docker container deployed in the VM. Reference may be made to the description of this section to the embodiment shown in fig. 6.
In one implementation, forwarding the first data packet according to the IP address of the container (step S24), includes: replacing the destination IP address of the first data message with the container IP address to obtain a corresponding original data message; and forwarding the original data message according to the destination IP address of the original data message.
As an example, as shown in fig. 5, a GRE tunnel is established between a router in a site a and a host in a site B, i.e., a GRE tunnel portal is configured on the router and the host, respectively. If the router in the site a communicates with the container 3 deployed in the VM2 in the site B, when the GRE message is sent from the router to the host, the host processes the GRE message as follows:
as shown in fig. 5, the host receives a GRE message sent by the router through the GRE tunnel. The host identifies the reserved field of the GRE header. The reserved field includes the IP address 4.4.4.3 of the container, the host obtains the IP address 4.4.4.3 of the container (i.e., the IP address of container 3). The VM3 strips off the outer IP header and the GRE header included in the GRE packet, to obtain a first data packet. In this embodiment, a data packet is taken as an IP packet for example. The first data message is an IP message 3 obtained after the host decapsulates an outer layer IP header of the GRE message and a GRE message header. The destination IP address of IP packet 3 is 3.3.3.2 (i.e., the IP address of VM 2). The host sends IP message 3 and IP address 4.4.4.3 to VM 2. The VM2 receives the IP packet 3 and the IP address 4.4.4.3, and replaces the destination IP address 3.3.3.2 of the IP packet 3 with 4.4.4.3 to obtain the original IP packet corresponding to the IP packet 3. VM2 forwards the original IP packet, i.e., sends the original IP packet to container 3.
In one implementation, the method further comprises: if the reserved field does not comprise the IP address of the container, decapsulating the GRE message to obtain a second data message included in the GRE message; and forwarding the second data message according to the destination IP address of the second data message.
As an example, as shown in FIG. 5, a host receives a GRE message sent by a router through a GRE tunnel. The host identifies the reserved field of the GRE header. The reserved field does not include the IP address of the container. The host strips off the outer layer IP message header and the GRE message header included in the GRE message to obtain a second data message. In this embodiment, a data packet is taken as an IP packet for example. The second data message is an IP message 5 obtained after the host decapsulates the outer layer IP header of the GRE message and the GRE message header. If the destination IP address of the IP packet 5 is 3.3.3.2 (i.e., the IP address of VM 2), the host forwards the IP packet 5, i.e., sends the IP packet 5 to VM 2.
The message forwarding method disclosed by the invention carries the IP address of the container deployed in the VM through the reserved field of the header of the GRE message, when the host computer which establishes the GRE tunnel receives the GRE message, the IP address of the container is obtained, and the data message obtained by decapsulating the GRE message and the IP address of the container are sent to the VM which deploys the container, so that the VM which deploys the container forwards the data message according to the IP address of the container, and therefore, the routing exchange equipment in one site can communicate with the container deployed in the VM in another site through the GRE tunnel.
Fig. 10 shows a flowchart of a packet forwarding method according to an embodiment of the present disclosure. The method is applied to the route switching equipment, and the route switching equipment and the remote equipment establish a GRE tunnel. As shown in fig. 10, the message forwarding method includes step S31 and step S34.
In step S31, when the original data packet is received or generated according to the packet generation instruction, if it is determined that the recipient of the original data packet is a container deployed in the VM according to the destination IP address of the original data packet, the IP address of the VM where the container is deployed is obtained.
The remote device may be a host or a VM, which is not limited by the present disclosure.
In one implementation, the router may act as a forwarder of the original data packet. In this case, when the router receives the original data packet, it determines whether the receiver of the original data packet is a container deployed in the VM according to the destination IP address of the original data packet.
In another implementation, the router may act as the initial sender of the original data packet. In this case, when the router generates the original data packet according to the packet generation instruction, it determines whether the receiver of the original data packet is a container deployed in the VM according to the destination IP address of the original data packet.
In one implementation, if the passenger protocol is an IP protocol, a static table is configured in the router, and the static table stores a correspondence between an IP address of the container and an IP address of a VM deploying the container. When the router receives an original IP message or generates the original IP message according to a message generation instruction, the router acquires the IP address of the original IP message and searches a static table according to the IP address of the original IP message.
If the IP address of the original IP message is matched with the IP of the container stored in the static table, the router determines that the receiver of the original IP message is the container deployed in the VM. If the IP address of the original IP message does not match the IP of the container stored in the static table, the router determines that the receiver of the original IP message is not the container deployed in the VM.
As an example, as shown in fig. 5, the router receives an original IP packet, which has a destination IP address of 4.4.4.3. The router looks up a static table based on the destination IP address 4.4.4.3 of the original IP packet. Table 1 shows a static table according to an embodiment of the present disclosure. As shown in table 1, if the destination IP address 4.4.4.3 of the original IP packet matches the IP of container 3 stored in the static table, the router determines that the receiver of the original IP packet is container 3 deployed in VM 2. The router obtains the IP address 3.3.3.2 of VM2 of deployment container 3.
TABLE 1
Container label IP address of container Identification of VM Deploying the containerIP address of VM of
Container 1 4.4.4.1 VM1 3.3.3.1
Container 2 4.4.4.2 VM2 3.3.3.2
Container 3 4.4.4.3 VM2 3.3.3.2
Container 4 4.4.4.4 VM3 3.3.3.3
Container 5 4.4.4.5 VM3 3.3.3.3
In step S32, the destination IP address of the original data packet is replaced with the IP address of the VM, so as to obtain a corresponding first data packet.
In step S33, GRE encapsulation is performed on the first data packet to obtain a GRE packet; wherein, the reserved field of the GRE message header carries the IP address of the container.
In step S34, the GRE message is forwarded through the GRE tunnel.
Taking over the example of the step S31, as shown in fig. 5, the router receives the original IP packet, and the destination IP address of the original IP packet is 4.4.4.3. The router determines that the recipient of the original IP packet is container 3 deployed in VM 2. The router obtains the IP address 3.3.3.2 of VM2 of deployment container 3. The router replaces the destination IP address 4.4.4.3 of the original IP packet with the IP address 3.3.3.2 of the VM2 to obtain a first data packet. The destination IP address of the first datagram is 3.3.3.2. The router performs GRE encapsulation on the first data message to obtain a GRE message; wherein, the reserved field of the GRE header carries the IP address 4.4.4.3 of the container 3. And the router forwards the GRE message through the GRE tunnel.
According to the message forwarding method, when a routing switching device receives an original data message or generates the original data message according to a message generation instruction, if a receiver of the original data message is determined to be a container deployed in a VM according to a destination IP address of the original data message, the IP address of the VM deployed with the container is obtained, the destination IP address of the original data message is replaced by the IP address of the VM to obtain a corresponding data message, and a GRE message encapsulating the data message is forwarded through a GRE tunnel, so that the routing switching device in one site can communicate with the container deployed in the VM in another site through the GRE tunnel.
Fig. 11 shows a block diagram of a message forwarding device according to an embodiment of the present disclosure. The apparatus is applied to a first virtual machine VM, and a GRE tunnel is established between the first VM and a remote routing switch device, as shown in fig. 11, the apparatus includes:
the identification module 11 is configured to identify a reserved field of a GRE packet header when the GRE packet is received, where the reserved field is used to carry an IP address of a container deployed in the VM; a first obtaining module 12, configured to obtain an IP address of the container if the reserved field includes the IP address of the container; a decapsulation module 13, configured to decapsulate the GRE packet to obtain a first data packet; the first forwarding module 14 is configured to forward the first data packet according to the IP address of the container when the VM deploying the container is the first VM.
In one implementation, the apparatus further comprises: the first forwarding module 14 is further configured to send the first data packet and the IP address of the container to the VM deploying the container when the VM deploying the container is another VM except the first VM, so that the VM deploying the container forwards the first data packet according to the IP address of the container.
In one implementation, forwarding the first data packet according to the IP address of the container includes: replacing the destination IP address of the first data message with the container IP address to obtain a corresponding original data message; and forwarding the original data message according to the destination IP address of the original data message.
In one implementation, the apparatus further comprises: the decapsulation module 13 is further configured to decapsulate the GRE packet to obtain a second data packet if the reserved field does not include the IP address of the container; and a second forwarding module 15, configured to forward the second data packet according to the destination IP address of the second data packet.
In one implementation, the container deployed in the VM is a Docker container deployed in the VM.
The message forwarding device disclosed by the invention carries the IP address of the container deployed in the first VM through the reserved field of the header of the GRE message, acquires the IP address of the container when the first VM which establishes the GRE tunnel receives the GRE message, and forwards the data message obtained by de-encapsulating the GRE message according to the IP address of the container, or sends the data message obtained by de-encapsulating the GRE message and the IP address of the container to the second VM, so that the second VM forwards the data message according to the IP address of the container, and therefore, the routing switching equipment in one site can communicate with the container deployed in the VM in another site through the GRE tunnel.
Fig. 12 shows a block diagram of a message forwarding device according to an embodiment of the present disclosure. The apparatus is applied to a host, a GRE tunnel is established between the host and a remote routing switching device, a VM is created in the host, as shown in fig. 12, the apparatus includes:
an identifying module 21, configured to identify a reserved field of a GRE packet header when the GRE packet is received, where the reserved field is used to carry an IP address of a container deployed in a VM; a first obtaining module 22, configured to obtain an IP address of the container if the reserved field includes the IP address of the container; a decapsulation module 23, configured to decapsulate the GRE packet to obtain a first data packet; a first forwarding module 24, configured to send the first data packet and the IP address of the container to the VM deploying the container, so that the VM deploying the container forwards the first data packet according to the IP address of the container.
In one implementation, forwarding the first data packet according to the IP address of the container includes: replacing the destination IP address of the first data message with the container IP address to obtain a corresponding original data message; and forwarding the original data message according to the destination IP address of the original data message.
In one implementation, the apparatus further comprises: the decapsulation module 23 is further configured to decapsulate the GRE packet to obtain a second data packet if the reserved field does not include the IP address of the container; and a second forwarding module 25, configured to forward the second data packet according to the destination IP address of the second data packet.
In one implementation, the container deployed in the VM is a Docker container deployed in the VM.
The message forwarding device disclosed by the invention carries the IP address of the container deployed in the VM through the reserved field of the header of the GRE message, when the host machine which establishes the GRE tunnel receives the GRE message, the IP address of the container is obtained, and the data message obtained by decapsulating the GRE message and the IP address of the container are sent to the VM which deploys the container, so that the VM which deploys the container forwards the data message according to the IP address of the container, and therefore, the routing exchange equipment in one site can communicate with the container deployed in the VM in another site through the GRE tunnel.
Fig. 13 shows a block diagram of a message forwarding device according to an embodiment of the present disclosure. The apparatus is applied to a routing switching device, the routing switching device establishes a GRE tunnel with a remote device, as shown in fig. 13, the apparatus includes:
a second obtaining module 31, configured to, when an original data packet is received or an original data packet is generated according to a packet generation instruction, if it is determined that a receiver of the original data packet is a container deployed in a VM according to a destination IP address of the original data packet, obtain an IP address of the VM where the container is deployed;
a replacing module 32, configured to replace the destination IP address of the original data packet with the IP address of the VM, so as to obtain a corresponding first data packet;
an encapsulation module 33, configured to perform GRE encapsulation on the first data packet to obtain a GRE packet; wherein, the reserved field of the GRE message header carries the IP address of the container;
and the sending module 34 is configured to forward the GRE packet through the GRE tunnel.
According to the message forwarding device disclosed by the invention, when a routing switching device receives an original data message or generates the original data message according to a message generation instruction, if a receiver of the original data message is determined to be a container deployed in a VM according to a destination IP address of the original data message, the IP address of the VM deployed with the container is obtained, the destination IP address of the original data message is replaced by the IP address of the VM to obtain a corresponding data message, and a GRE message encapsulating the data message is forwarded through a GRE tunnel, so that the routing switching device in one site can communicate with the container deployed in the VM in another site through the GRE tunnel.
Fig. 14 shows a block diagram of a message forwarding device according to an embodiment of the present disclosure. Referring to fig. 14, the apparatus 900 may include a processor 901, a machine-readable storage medium 902 having stored thereon machine-executable instructions. The processor 901 and the machine-readable storage medium 902 may communicate via a system bus 903. And, the processor 901 executes the message forwarding method executed by the aggregation switch by reading the machine-executable instruction corresponding to the message forwarding logic in the machine-readable storage medium 902.
The present disclosure may also provide another message forwarding device that may include a processor, and a machine-readable storage medium having stored thereon machine-executable instructions. The processor and the machine-readable storage medium may communicate via a system bus. And the processor reads the machine-executable instruction corresponding to the message forwarding logic in the machine-readable storage medium to execute the message forwarding method executed by the resource pool gateway.
A machine-readable storage medium as referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein were chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the techniques in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims (14)

1. A message forwarding method is applied to a first Virtual Machine (VM), wherein a GRE tunnel is established between the first VM and a remote routing switching device, and the method comprises the following steps:
when a GRE message is received, identifying a reserved field of a GRE message header, wherein the reserved field is used for carrying an IP address of a container deployed in a VM (virtual machine);
if the reserved field comprises the IP address of the container, acquiring the IP address of the container;
decapsulating the GRE message to obtain a first data message;
and when the VM deploying the container is the first VM, forwarding the first data message according to the IP address of the container.
2. The method of claim 1, further comprising:
and when the VM deploying the container is other VMs except the first VM, sending the first data message and the IP address of the container to the VM deploying the container, so that the VM deploying the container forwards the first data message according to the IP address of the container.
3. A message forwarding method is applied to a host, a GRE tunnel is established between the host and a remote routing switching device, and a VM is created in the host, and the method comprises the following steps:
when a GRE message is received, identifying a reserved field of a GRE message header, wherein the reserved field is used for carrying an IP address of a container deployed in a VM (virtual machine);
if the reserved field comprises the IP address of the container, acquiring the IP address of the container;
decapsulating the GRE message to obtain a first data message;
and sending the first data message and the IP address of the container to the VM which deploys the container, so that the VM which deploys the container forwards the first data message according to the IP address of the container.
4. The method according to any of claims 1 to 3, wherein forwarding the first data packet according to the IP address of the container comprises:
replacing the destination IP address of the first data message with the container IP address to obtain a corresponding original data message;
and forwarding the original data message according to the destination IP address of the original data message.
5. The method according to any one of claims 1 to 3, further comprising:
if the reserved field does not comprise the IP address of the container, decapsulating the GRE message to obtain a second data message;
and forwarding the second data message according to the destination IP address of the second data message.
6. The method of any of claims 1 to 3, wherein the container deployed in the VM is a Docker container deployed in the VM.
7. A message forwarding method is characterized in that the method is applied to a route switching device, the route switching device and a remote device establish a GRE tunnel, and the method comprises the following steps:
when an original data message is received or generated according to a message generation instruction, if a receiver of the original data message is determined to be a container deployed in a VM according to a destination IP address of the original data message, acquiring the IP address of the VM deployed in the container;
replacing the target IP address of the original data message with the IP address of the VM to obtain a corresponding first data message;
carrying out GRE encapsulation on the first data message to obtain a GRE message; wherein, the reserved field of the GRE message header carries the IP address of the container;
and forwarding the GRE message through the GRE tunnel.
8. A message forwarding device is applied to a first Virtual Machine (VM), wherein a GRE tunnel is established between the first VM and a remote routing switching device, and the device comprises:
the identification module is used for identifying a reserved field of a GRE message header when the GRE message is received, wherein the reserved field is used for carrying an IP address of a container deployed in a VM (virtual machine);
a first obtaining module, configured to obtain an IP address of a container if the reserved field includes the IP address of the container;
the decapsulation module is used for decapsulating the GRE message to obtain a first data message;
and the first forwarding module is used for forwarding the first data message according to the IP address of the container when the VM in which the container is deployed is the first VM.
9. The apparatus of claim 8, further comprising:
the first forwarding module is further configured to send the first data packet and the IP address of the container to the VM deploying the container when the VM deploying the container is another VM except the first VM, so that the VM deploying the container forwards the first data packet according to the IP address of the container.
10. A message forwarding apparatus, applied to a host, where the host establishes a GRE tunnel with a remote routing switch device, and a VM is created in the host, the apparatus comprising:
the identification module is used for identifying a reserved field of a GRE message header when the GRE message is received, wherein the reserved field is used for carrying an IP address of a container deployed in a VM (virtual machine);
a first obtaining module, configured to obtain an IP address of a container if the reserved field includes the IP address of the container;
the decapsulation module is used for decapsulating the GRE message to obtain a first data message;
and the first forwarding module is used for sending the first data message and the IP address of the container to the VM which deploys the container, and is used for enabling the VM which deploys the container to forward the first data message according to the IP address of the container.
11. The apparatus according to any one of claims 8 to 10, wherein forwarding the first data packet according to the IP address of the container comprises:
replacing the destination IP address of the first data message with the container IP address to obtain a corresponding original data message;
and forwarding the original data message according to the destination IP address of the original data message.
12. The apparatus of any one of claims 8 to 10, further comprising:
the decapsulation module is further configured to decapsulate the GRE packet to obtain a second data packet if the reserved field does not include the IP address of the container;
and the second forwarding module is used for forwarding the second data message according to the destination IP address of the second data message.
13. The apparatus of any of claims 8 to 10, wherein the container deployed in the VM is a Docker container deployed in the VM.
14. A message forwarding device is applied to a route switching device, wherein a GRE tunnel is established between the route switching device and a remote device, and the device comprises:
the second obtaining module is used for obtaining the IP address of the VM where the container is deployed if the receiver of the original data message is determined to be the container deployed in the VM according to the destination IP address of the original data message when the original data message is received or the original data message is generated according to the message generation instruction;
the replacing module is used for replacing the target IP address of the original data message with the IP address of the VM to obtain a corresponding first data message;
the encapsulation module is used for carrying out GRE encapsulation on the first data message to obtain a GRE message; wherein, the reserved field of the GRE message header carries the IP address of the container;
and the sending module is used for forwarding the GRE message through the GRE tunnel.
CN201810542714.3A 2018-05-30 2018-05-30 Message forwarding method and device Active CN108390812B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810542714.3A CN108390812B (en) 2018-05-30 2018-05-30 Message forwarding method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810542714.3A CN108390812B (en) 2018-05-30 2018-05-30 Message forwarding method and device

Publications (2)

Publication Number Publication Date
CN108390812A CN108390812A (en) 2018-08-10
CN108390812B true CN108390812B (en) 2020-07-07

Family

ID=63071562

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810542714.3A Active CN108390812B (en) 2018-05-30 2018-05-30 Message forwarding method and device

Country Status (1)

Country Link
CN (1) CN108390812B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109450768B (en) * 2018-11-01 2021-06-01 中国联合网络通信集团有限公司 Method for interconnecting containers and system for interconnecting containers
CN110611625B (en) * 2018-11-27 2020-11-06 新华三技术有限公司 Network equipment and logic device applied to same
CN110147344B (en) * 2019-05-21 2022-02-11 优刻得科技股份有限公司 Method, apparatus, storage medium, and system for communicating between multiple physical machines
CN115277586A (en) * 2022-07-29 2022-11-01 中国电信股份有限公司 Method, system, equipment and storage medium for processing Pod flow

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103067270A (en) * 2013-01-08 2013-04-24 杭州华三通信技术有限公司 Virtual machine exchange visit safety control method and device
CN105591873A (en) * 2015-10-27 2016-05-18 杭州华三通信技术有限公司 Virtual machine isolation method and device
CN106169994A (en) * 2016-06-29 2016-11-30 中国联合网络通信集团有限公司 The method of controlling security communicated between container and device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8019837B2 (en) * 2009-01-14 2011-09-13 International Business Machines Corporation Providing network identity for virtual machines

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103067270A (en) * 2013-01-08 2013-04-24 杭州华三通信技术有限公司 Virtual machine exchange visit safety control method and device
CN105591873A (en) * 2015-10-27 2016-05-18 杭州华三通信技术有限公司 Virtual machine isolation method and device
CN106169994A (en) * 2016-06-29 2016-11-30 中国联合网络通信集团有限公司 The method of controlling security communicated between container and device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
《虚拟专用网隧道技术分析》;刘桂开等;《计算机科学》;20030115;第30卷(第1期);全文 *

Also Published As

Publication number Publication date
CN108390812A (en) 2018-08-10

Similar Documents

Publication Publication Date Title
US11671367B1 (en) Methods and apparatus for improving load balancing in overlay networks
US9825856B2 (en) Service function chaining in a packet network
CN108390812B (en) Message forwarding method and device
CN108632098B (en) Flow classifier, service routing trigger, message processing method and system
US9444642B2 (en) LAN multiplexing apparatus
US10412008B2 (en) Packet processing method, apparatus, and system
CN108718269B (en) Message processing method and device
US20120099602A1 (en) End-to-end virtualization
CN111937358B (en) Multiple VRF generic device internet protocol addresses for fabric edge devices
US20170324849A1 (en) Partial reassembly and fragmentation for decapsulation
CN107645433B (en) Message forwarding method and device
EP4160950A1 (en) Method and apparatus for sending message, and network device, system and storage medium
CN107547340B (en) Message forwarding method and device
EP2548346B1 (en) Packet node for applying service path routing at the mac layer
CN108900414B (en) Forwarding table generation method and device
US10454882B2 (en) DHCP in layer-3 overlay with anycast address support and network address transparency
WO2022026208A1 (en) Normalized lookup and forwarding for diverse virtual private networks
CN108259298A (en) A kind of message forwarding method and device
CN112737954B (en) Message processing method, device, system, equipment and storage medium
US8189530B2 (en) Methods and apparatus for VPN support in mobility management
CN108471374B (en) Data message forwarding method and device
CN108156066B (en) Message forwarding method and device
US9998376B2 (en) Control device, communication system, control method, and non-transitory recording medium
CN111010344B (en) Message forwarding method and device, electronic equipment and machine-readable storage medium
CN112565044B (en) Message processing method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20230619

Address after: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province

Patentee after: H3C INFORMATION TECHNOLOGY Co.,Ltd.

Address before: 310052 Changhe Road, Binjiang District, Hangzhou, Zhejiang Province, No. 466

Patentee before: NEW H3C TECHNOLOGIES Co.,Ltd.

TR01 Transfer of patent right