CN113132202B

CN113132202B - Message transmission method and related equipment

Info

Publication number: CN113132202B
Application number: CN201911415540.5A
Authority: CN
Inventors: 李久勇
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2023-12-08
Anticipated expiration: 2039-12-31
Also published as: WO2021135397A1; CN113132202A

Abstract

The embodiment of the application discloses a message transmission method and related equipment. The method comprises the steps that first equipment receives a first message from second equipment, wherein the first message comprises a message type indication for indicating that the first message is a unicast message or a BUM message; when the first device determines that the first message is the unicast message according to the message type indication, or when the first device determines that the first message is the BUM message according to the message type indication and the first device is the DF of the target device, the first device sends a second message to the target device; the second message is a message obtained by the first device after the first message is unpacked, the destination device is connected into a plurality of network devices, the plurality of network devices comprise the first device, and therefore the destination device can receive the message, and the message with the same content can only receive one message.

Description

Message transmission method and related equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and related device for transmitting a message.

Background

Server virtualization is increasingly being used in data center networks, and with the development of enterprise services, the rapid growth of the number of virtual machines and virtual machine migration have become a normal service. On this basis, virtual extensible local area networks (virtual extensible local area network, VXLAN) are emerging. VXLAN is one of the three-tier network virtualization (Network Virtualization over Layer, nvo 3) standard technologies, which is essentially a tunneling technology. When a message is forwarded in a VXLAN network, a VXLAN tunnel endpoint (VXLAN tunnel end point, VTEP) connected with a sending end (virtual machine or physical machine) can add a VXLAN header to an original message to obtain the VXLAN message, and forward the VXLAN message to the VTEP connected with a receiving end (virtual machine or physical machine) in a transmission mode of a traditional Internet protocol (Internet Protocol, IP) network; the VTEP connected to the receiving end may remove the outer encapsulation portion of the VXLAN message and send the original message to the receiving end.

However, in practical applications, after a virtual machine is migrated or added in a VXLAN network, a situation that a destination device cannot migrate or add a virtual machine to receive a message or simultaneously receive a plurality of same messages easily occurs.

Disclosure of Invention

In order to solve the above problems, the present application provides a message transmission method and related devices, so that a receiving end can receive a message sent by a sending end, and only one message with the same content can be received.

In a first aspect, the present application provides a method for transmitting a message. The method comprises the steps that first equipment receives a first message from second equipment, wherein the first message comprises a message type indication, and the message type indication is used for indicating that the first message is a unicast message or a broadcast unknown unicast multicast (BUM) message; when the first device determines that the first message is the unicast message according to the message type indication, or when the first device determines that the first message is the BUM message according to the message type indication and the first device is a designated forwarder DF of the destination device, the first device sends a second message to the destination device; the second message is a message obtained by decapsulating the first message by the first device, the destination device is connected to a plurality of network devices in multiple ways, and the plurality of network devices include the first device. In this embodiment, when the first device determines that the received message is a unicast message, the first device directly sends the message to the destination device, which enables the destination device to receive the message, and when the first device determines that the received message is a multicast message, the first device only sends the message to the destination device when the first device is used as the DF of the destination device, so that the destination device can only receive one part of the message, thereby realizing that the destination device can receive the message sent by the sender, and the message with the same content can only receive one part of the message.

Optionally, the message type indication is located in a target field of the first message, and/or the message type indication is a multicast address carried by the first message after being encapsulated by a multicast tunnel. In this embodiment, the first device may determine whether the first message is a unicast message or a multicast message according to the value of the target field in the first message, or determine whether the first message is a unicast message or a multicast message according to the IP address in the first message, when the IP address characterizes the IP address of a single device, it characterizes the first message as a unicast message, and when the IP address is a multicast IP address, it may characterize the first message as a BUM message, so that the first device may determine the message type of the first message according to the IP address in the first message.

Optionally, the first message is a VXLAN message including a VXLAN header of the virtual extensible local area network, and the target field is specifically a reserved field in the VXLAN header. In this embodiment, the first message may be a VXLAN message including a VXLAN header, such that the message type of the first message being a unicast message or a BUM message may be indicated by defining a value of a reserved field in the VXLAN header. Thus, the first device can determine the type of the first message according to the value of the specific reserved field in the header of the first message VXLAN. For example, a BUM flag bit may be defined in the VXLAN header, and when a value of the BUM flag bit is defined to be 0, the first message is represented as a unicast message, and when a value of the BUM flag bit is defined to be 1, the first message is represented as a BUM message.

Optionally, the method further comprises: and when the first device determines that the first message is the BUM message according to the message type indication and the first device is not the designated forwarder DF of the destination device, the first device does not send a second message to the destination device. In this embodiment, when the first device determines that the first message is a BUM message, but is not a DF message of the destination device, the characterizing destination device may obtain the message from another device (the DF of the destination device), so that the first device does not send the message to the destination device, for example, may discard the message, etc., so that the destination device does not repeatedly receive at least two messages with the same content.

In a second aspect, the present application further provides a message transmission device, where the device includes a receiving module, a processing module and a sending module:

the receiving module is used for receiving a first message from second equipment, wherein the first message comprises a message type indication, and the message type indication is used for indicating that the first message is a unicast message or a broadcast unaware unicast multicast (BUM) message;

the processing module is used for sending a second message to the destination device through the sending module when the first message is determined to be the unicast message according to the message type indication, or when the first message is determined to be the BUM message according to the message type indication and the first device is a designated forwarder DF of the destination device; the second message is a message obtained by decapsulating the first message by the first device, the destination device is connected to a plurality of network devices in multiple ways, and the plurality of network devices include the first device.

Optionally, the message type indication is located in a target field of the first message, and/or the message type indication is a multicast address carried by the first message after being encapsulated by a multicast tunnel.

Optionally, the first message is a VXLAN message including a VXLAN header of the virtual extensible local area network, and the target field is specifically a reserved field in the VXLAN header.

Optionally, the apparatus further comprises: the processing module is further configured to determine not to send a second message to the destination device when the first device determines that the first message is the BUM message according to the message type indication and the first device is not the DF of the destination device.

The message transmission device described in the second aspect corresponds to the message transmission method described in the first aspect, and therefore, various possible embodiments of the second aspect and the beneficial effects thereof may refer to the corresponding embodiments and the related descriptions of the beneficial effects in the first aspect, which are not repeated herein.

In a third aspect, the present application also provides a computer device. The device computer includes a processor and a memory, where the memory is configured to store a computer program or instructions, and the processor is configured to execute the computer program or instructions, so that the computer device performs the foregoing first aspect or any implementation manner of the first aspect.

In a fourth aspect, the present application provides a computer storage medium storing a program for implementing the method for transmitting a message according to the first aspect or any one of the embodiments of the first aspect. When the program runs in the device for transmitting messages, the device is caused to execute the message transmission method described in the first aspect or any implementation manner of the first aspect.

In a fifth aspect, the present application provides a computer program product comprising a program which, when run, causes the message transmission method of the first aspect or any one of the embodiments of the first aspect to be performed.

As can be seen from the above technical solution, in the present application, a first device receives a first message from a second device, where the first message includes a message type indication, where the message type indication is used to indicate that the first message is a unicast message or a broadcast unknown unicast multicast BUM message; when the first device determines that the first message is the unicast message according to the message type indication, or when the first device determines that the first message is the BUM message according to the message type indication and the first device is a designated forwarder DF of the destination device, the first device sends a second message to the destination device; the second message is a message obtained by decapsulating the first message by the first device, the destination device is connected to a plurality of network devices in multiple ways, and the plurality of network devices include the first device. It can be seen that when the first device determines that the received message is a unicast message, the first device directly sends the received message to the destination device, so that the destination device can receive the message, and when the received message is determined to be a BUM message, the first device only sends the message to the destination device when the first device is used as the DF of the destination device, so that the destination device can only receive one part of message, thereby realizing that the destination device can receive the message sent by the sending end, and the message with the same content can only receive one part.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to these drawings for those of ordinary skill in the art.

Fig. 1 is a schematic diagram of an exemplary VXLAN network architecture in accordance with an embodiment of the present application;

fig. 2 is a signaling interaction schematic diagram of a message transmission method in an embodiment of the present application;

fig. 3 is a schematic diagram of VXLAN message format;

fig. 4 is a schematic diagram of a hardware structure of a main control board of the device in the embodiment of the application;

FIG. 5 is a schematic diagram of an interface board hardware structure of a device according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a hardware structure of an apparatus according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a message transmission device according to an embodiment of the present application.

Detailed Description

The application provides a message transmission method, which is used for solving the problem that a scene terminal device (such as a virtual machine, a server, a personal computer, a palm computer and the like) which is accessed into a plurality of access devices by multiple sets receives multiple messages. The following describes the message transmission method provided by the application by taking a VXLAN network as an example in combination with the attached drawings.

Fig. 1 is a schematic structural diagram of a VXLAN network according to an embodiment of the present application. The VXLAN network is overlaid on a leaf-spine (leaf-spine) structured data center network. The data center network includes a leaf layer including a plurality of leaf devices, such as leaf1 through leaf4 in the figures, and a backbone layer including one or more spine devices (one shown in the figures) through which each leaf device communicates with other leaf devices. Each terminal device may access one leaf device (referred to as single homing) or multiple leaf devices simultaneously (referred to as multiple homing). The present application focuses on the scenario where one terminal device accesses multiple leaf devices, for example, virtual Machine (VM) 1 is multi-homed to access leaf1 and leaf2, VM2 is multi-homed to access leaf3 and leaf4, then leaf1 and leaf2 belong to the same multi-homed access group, and leaf3 and leaf4 belong to the same multi-homed access group.

In the VXLAN network as shown in fig. 1, corresponding VTEPs (VTEP 1, VTEP2, VTEP3, and VTEP4, respectively) may be deployed on each of the leaf1 to leaf 4. Wherein, different VTEPs have different IP addresses, and the message during communication between VM1 and VM2 is transmitted through the VTEP on the leaf node.

Taking VM1 to transmit a message to VM2 as an example, VM1 may send an original message to VTEP1 on a leaf1 node (of course, may also be sent to VTEP2 on a leaf2 node, and is illustrated by VTEP1 here), VTEP1 may encapsulate a VXLAN header of the received original message to obtain a VXLAN message, and then, by looking up a local MAC table, may determine to send the VXLAN message to VTEP3 (the message may be transmitted to VTEP3 via a spike in fig. 1, and it is assumed that the message is sent to VTEP3, or may be sent to VTEP4 in practical application). The VTEP3 performs decapsulation processing on the received VXLAN message to obtain an original message, and can determine to send the original message to the VM2 by searching a corresponding table entry in a local MAC table, so that the original message sent by the VM1 can be transmitted to the VM2.

In general, if forwarding entries for VM2 exist in the local MAC tables of VTEP1 and VTEP3, a message may be successfully transmitted to VM2 based on the corresponding entries in the local MAC tables of VTEP1 and VTEP 3. However, when there is no forwarding table entry for VM2 in the local MAC table of VTEP1, VTEP1 typically looks up the head-end copy list, copies and VXLAN encapsulates the message according to the head-end copy list, generates a broadcast unknown-unicast (BUM) message that is sent to VTEP3 and VTEP4, and sends the BUM message to VTEP3 and VTEP4. Thus, both VTEP3 and VTEP4 can receive one BUM message, and if the local MAC entries of VTEP3 and VTEP4 both store forwarding entries for VM2, VTEP3 and VTEP4 can forward the messages to VM2 respectively, so that VM2 receives two duplicate messages, resulting in network resource waste.

Alternatively, when the forwarding table entry for VM2 is stored in the local MAC table of VTEP1, VTEP1 may send a unicast packet to VTEP3 or VTEP4, for example, may determine to send the unicast packet to VTEP3 or to VTEP4 by means of load sharing. At this time, if VTEP3 receives a message and the forwarding table entry for VM2 is not stored in the VTEP3 local MAC table, VTEP3 will generally trigger the function of designating a forwarder (DF), and when VTEP3 is not the DF of VM2, VTEP3 will not send a message to VM2, but VTEP4, which is the DF of VM2, will not send a message to VM2 because it does not receive a unicast message sent by VTEP1, and eventually, VM2 will not receive a message sent by VM 1. The DF function designates a VTEP as DF for each VM in a multi-homing access group, and is responsible for forwarding a message to the VM, and other VTEPs other than DF do not send a message to the accessed VM.

In practical applications, when VM2 is a migrated VM or a newly added VM, VTEP1 and VTEP3 may not learn the MAC address of the VM2, and a situation that a forwarding table entry corresponding to VM2 does not exist in the local MAC table of VTEP1 or the local MAC table of VTEP3 is easy to occur, so that multiple repeated messages may be received by VM2 or no message may be received. However, in the process of forwarding the message, the situation of sending multiple messages or discarding the message needs to be avoided.

Based on this, the embodiment of the application provides a message transmission method, so that VM2 can receive a message sent by VM1 and only receive one message. Specifically, when VM1 sends an original message to VTEP1, VTEP1 may encapsulate a VXLAN header of the received original message to obtain a VXLAN message, and set a message type indication for indicating whether the first message is a unicast message or a BUM message in the VXLAN message. VTEP1 can then send the encapsulated VXLAN message to VTEP3. After receiving the VXLAN message, the VTEP3 may obtain a message type indication from the VXLAN message.

In this way, when the VTEP3 determines that the VXLAN message received by the VTEP3 is a unicast message according to the message type indication, it indicates that the VTEP1 only sends one VXLAN message, and only the VTEP3 receives the VXLAN message, at this time, the VTEP3 may perform decapsulation processing on the VXLAN message, and directly send the obtained original message to the VM2, so that the VM2 may obtain the original message, otherwise, the VM2 cannot obtain the original message from other VTEPs, thereby avoiding message loss.

When VTEP3 determines that the VXLAN message is a BUM message according to the message type indication, it indicates that VTEP1 sends multiple VXLAN messages, that is, there are other VTEPs that receive the message in addition to VTEP3 receiving the message, so if VTEP3 is determined to be DF of VM2, VTEP3 may send an original message obtained by decapsulating the VXLAN message to VM2, and if VTEP3 is determined not to be DF of VM2, VTEP3 may not send the original message to VM 2. In this way, VM2 receives only the original message from the VTEP as DF, but not from other VTEPs, so that it can avoid receiving multiple identical messages.

It is noted that the VXLAN network shown in fig. 1 is by way of example only and not intended to be limiting. For example, in practical application, the device for multi-homing access in the VXLAN network to which the embodiment of the present application is applicable may be a device such as a physical machine, besides a virtual machine VM; for example, the VXLAN network to which the embodiment of the present application is applicable may also support single-homing, triple-homing, quad-homing access of a virtual machine or a physical machine. For another example, the network to which the embodiments of the present application are applicable may also be a campus network or an enterprise network.

Various non-limiting implementations of a message transmission method according to embodiments of the present application are described in detail below with reference to the accompanying drawings. Referring to fig. 2, fig. 2 shows a signaling interaction diagram of a message transmission method according to an embodiment of the present application, where the method may be applied to the VXLAN network shown in fig. 1, and may specifically include:

s201: the source device sends a second message to the second device.

In this embodiment, as shown in fig. 2, when the source device needs to send a message to another device (destination device), the message may be sequentially transmitted to the destination device through the second device and the first device in the middle. For example, when the embodiment is applied to the VXLAN network shown in fig. 1, the source device may specifically be VM1 in fig. 1 that needs to send a message to VM2, and the destination device may be VM2, where the first device may be VTEP3 in fig. 1 or a leaf3 device that carries the VTEP3 (of course, may also be VTEP4 or a leaf4 device that carries VTEP 4), and the second device may be VTEP1 in fig. 1 or a leaf1 device that carries the VTEP1 (of course, may also be VTEP2 or a leaf2 device that carries VTEP 2).

In the message transmission process, the source device may send an original message (hereinafter referred to as a second message) to be transmitted to the destination device to the second device, so that the second device performs corresponding processing and forwarding on the second message.

S202: the second device encapsulates the second message to obtain a first message, wherein the first message comprises a message type indication, and the message type indication is used for indicating whether the first message is a unicast message or a BUM message.

In a specific implementation, the second device and the first device may perform packet transmission based on tunneling technology. The second device serves as a tunnel endpoint, and encapsulates the VXLAN header with a second message, and sets a corresponding message type indication in the VXLAN header according to whether the first message to be sent belongs to a unicast message or a BUM message in the encapsulation process, so that the encapsulated first message includes the type indication of the first message.

In an exemplary embodiment, the message type indication may specifically be a reserved field located in the VXLAN header. As shown in fig. 3, when the second device encapsulates the second packet, a VXLAN header, a user datagram protocol (User Datagram Protocol, UDP) header, an outer IP header, and an outer ethernet header may be sequentially added to the original data frame, where the VXLAN header may include a 24-bit VXLAN network identifier (VXLAN network identifier, VNI) field and an 8-bit VXLAN flag bit field, and the remaining fields are reserved fields, and one or more fields in the reserved fields may be used to indicate whether the first packet is a unicast packet or a BUM packet. For example, an 8-bit reserved field after the VXLAN flag field may be defined as a BUM flag, where a value of 0 is defined for the BUM flag to indicate that the first message is a unicast message, and a value of 1 or other non-0 value is defined for the reserved field to indicate that the first message is a BUM message. Correspondingly, when the second device encapsulates the VXLAN header for the first packet, a corresponding value (which is 0 or a non-0 value) may be set in the reserved field according to whether the packet to be sent is a unicast packet or a BUM packet, so that the first packet includes a packet type indication.

In the above embodiment, the type of the first packet is indicated by defining the value of the field, and in other possible embodiments, the received packet may be indicated as a unicast packet or a BUM packet based on the destination IP address of the outer layer of the first packet. As shown in fig. 3, the IP address of the destination terminal VTEP may be included in the outer layer IP header of the first packet obtained by encapsulating the second device (of course, the IP address of the active terminal VTEP may also be included at the same time). If the second device is to send a unicast message, the IP address of the destination end VTEP in the outer layer IP header of the first message may be a single IP address, so that the second device may send a unicast message to only one device; if the second device is to send the BUM message, the IP address of the destination VTEP in the IP header of the first message is the range of IP addresses, that is, the IP address of the destination VTEP is specifically the IP addresses of a plurality of VTEPs included in the range of IP addresses, so that the second device can send the BUM message to the plurality of VTEPs.

The second device may determine whether to send the unicast message or the BUM message according to the query result of the local MAC table, that is, if the second device can find the table entry corresponding to the destination MAC address from the local MAC table, the second device may send the unicast message, and if the second device fails to find the table entry corresponding to the destination MAC address, the second device may send the BUM message.

In a specific implementation, after receiving a second message sent by a source device, a second device may acquire a destination MAC address of the second message, for example, may parse a destination MAC address from the second message, and query whether a table entry corresponding to the destination MAC address is recorded in a locally stored MAC table, where the table entry corresponding to the destination MAC address may include, for example, an IP address of a destination VTEP; when the second device searches the table entry corresponding to the target address from the MAC table, the second device may determine to send a unicast message to the output port device corresponding to the searched table entry, and accordingly, the message type indication included in the first message may specifically be an indication that the first message is a unicast message; and when the second device cannot find the table entry corresponding to the destination MAC address from the MAC table, the second device may determine to send the BUM message.

Taking the VM1 shown in fig. 1 as an example of sending a message to the VM2, after the VM1 sends an original message (i.e., the second message) to the VTEP1 (i.e., the second device), the VTEP1 may query a local MAC table as shown in table 1, and since it queries an entry (whose exit port points to the IP address of the VTEP3, i.e., the exit port is a tunnel entry) corresponding to the destination MAC address (i.e., the MAC address of the VM 2), the VTEP1 may determine to send a unicast message to the VTEP3, and a message (i.e., the first message) obtained by encapsulating the original message includes a message type indication for indicating that the message is a unicast message.

TABLE 1

MAC table entry	Outlet port
		MAC address of VM2	IP address of VTEP3

Of course, if the table entry corresponding to the MAC address of VM2 is not recorded in the local MAC table of the VTEP, VTEP1 may determine to send a BUM message, and generate a BUM message (i.e. the first message) sent to VTEP3 and VTEP4 respectively, where the generated BUM message may include a message type indication for indicating that the message is a BUM message.

In practical application, when the message type indication is located in the VXLAN header, if the second device finds an entry corresponding to the destination MAC address from the MAC table, the message type indication for indicating the unicast message may be set at the corresponding reserved field in the VXLAN header, and if the entry corresponding to the destination MAC address is not found, the message type indication for indicating the BUM message may be set at the corresponding reserved field in the VXLAN header.

When the message type indicates that the message is the outer layer destination IP address of the first message, if the second device finds the table entry corresponding to the destination MAC address from the MAC table, the second device may use the IP address corresponding to the found table entry as the outer layer destination IP address, and complete message encapsulation, so that the single destination IP address may be used to indicate that the first message is a unicast message, and if the table entry corresponding to the destination MAC address is not found, the multicast IP address may be used as the outer layer destination IP address, so that the multicast IP address may be used to indicate that the first message is a BUM message.

It should be noted that, in practical applications, the second device may determine whether to send the unicast message or the BUM message in other manners. For example, when the second device is configured as intra-domain multicast, the BUM message may be generated directly, and the type of the transmission message may not be determined by looking up the MAC table entry.

Accordingly, the second device may also determine in advance to which device to send the message before sending the first message. As an example, when the second device finds a single entry corresponding to the destination MAC address from the MAC table, the port device indicated by the entry is the first device. In practical applications, there may be a plurality of entries corresponding to the destination MAC address, which are found by the second device from the MAC table, and the entries correspond to a plurality of egress port devices. For example, in the VXLAN network shown in fig. 1, the VTEP1 can find from the local MAC table that the entries corresponding to the MAC address of VM2 are the IP address of VTEP3 and the IP address of VTEP4, respectively. At this time, load may be applied to the plurality of output port devices, and specifically, a device that receives the first packet may be determined from the plurality of output port devices based on HASH (HASH) algorithm, where the determined device is the first device. And when the second device cannot find the table entry corresponding to the destination MAC address from the MAC table, the second device may use the two-layer network device in communication with the second device as the first device. The two-layer network device refers to a network device which can realize communication with the second device through MAC addressing.

S203: the second device sends a first message to the first device.

In this embodiment, after the second device encapsulates to obtain the first packet, the second device may send the first packet to the first device based on a conventional IP protocol.

S204: the first device decapsulates the received first message to obtain a second message, and determines whether the first message is a unicast message or a BUM message according to a message type indication included in the first message.

The first message is obtained after the second message is encapsulated, so that the first device can perform corresponding decapsulation processing on the first message after receiving the first message to obtain the second message.

And if the predefined or collaborative message type indication is located in the target field of the first message, such as the reserved field in the header of the first message VXLAN, the message type indication may be obtained from the first message target field, and it is determined whether the first message is a unicast message or a BUM message according to the message type indication. For example, one or more reserved fields in the VXLAN header may be predefined as a BUM flag bit, when the value of the BUM flag bit is 1, the first message may be determined to be a BUM message, and when the value of the BUM flag bit is 0, the first message may be determined to be a unicast message.

If the predefined or co-negotiated message type indicates a destination IP address, in particular, in a first message, it is possible to parse from the first message whether the destination IP address characterizes a single IP address or a multicast IP address (i.e. characterizes a range segment of multiple IP addresses). When the destination IP address is a single IP address, the first device may determine that the first packet is a unicast packet, and when the destination address is a multicast IP address, the first device may determine that the first packet is a BUM packet.

S205: when the first device determines that the first message is a unicast message or the first device determines that the first message is a BUM message and the first device is a DF of the destination device, the first device sends a second message to the destination device.

In this embodiment, when the first device determines that the first message is a unicast message, it indicates that the second device only sends the first message to the first device, so, in order to improve the success rate of the destination device obtaining the second message sent by the source device, the first device may directly send the second message obtained by decapsulating the first message to the destination device. Specifically, when the first device searches the table entry corresponding to the destination MAC address from the local MAC table, the second message may be sent to the destination device according to the table entry, and when the first device cannot find the table entry corresponding to the destination MAC address, the second message may be sent to the accessed device, and since the network device to which the destination device is multi-access includes the first device, the destination device can generally receive the second message from the first device.

Therefore, whether the local MAC table of the first device comprises the table item corresponding to the destination MAC address or not, the destination device can receive the second message, so that the situation that the first device does not send the second message to the destination device because the first device is not the DF of the destination device when the table item of the destination MAC address is not recorded in the local MAC table can be avoided, and further, the message loss (namely, the destination device cannot receive the message) can be avoided.

When the first device determines that the first message is a BUM message, it indicates that the second device simultaneously sends the BUM message to the plurality of devices, and at this time, since the destination device is multiple-access to the plurality of network devices (including the first device), the destination device can receive the messages from the plurality of network devices. Based on this, in order to avoid that the destination device receives multiple second messages from multiple network devices, the DF election function may be triggered, that is, a network device is designated for the destination device to forward a message (the designated network device is DF), and the other network devices to which the destination device has multiple access cannot send a message to the destination device. Based on this, when determining that the first packet is a BUM packet, the first device may further determine whether the first device is a DF corresponding to the destination device that is characterized by the destination MAC address, if so, the first device may send the second packet to the destination device, and if not, the first device may not send the second packet to the destination device, for example, may discard the second packet, and so on. In this way, although the destination device accesses multiple network devices in multiple ways, the destination device will only receive the second message from the DF corresponding to the destination device, so that the situation of multiple packets (i.e. the destination device receives multiple repeated messages) can be avoided.

It can be understood that, when the first device determines that the received first message is a unicast message, whether the table entry corresponding to the destination MAC address is recorded in the local MAC table or not, the second message may be sent to the destination device, and when the first device determines that the received first message is a BUM message, the first device sends the second message to the destination device only when the first device is the DF of the destination device, which makes it possible for the destination device to receive the second message and only receive one second message, so that the situation of packet loss or multiple packets can be avoided, whether the table entries corresponding to the destination MAC address are recorded in the local MAC tables of the first device and the second device or not.

For the scenario that whether the table entry corresponding to the destination MAC address is recorded in the MAC table of the first device and the second device, there may be a combination of multiple messaging behaviors of the first device and the second device, which is specifically shown in table 2:

TABLE 2

The "first MAC table record" and "first MAC table record" in the above table represent, respectively, that a table item corresponding to a destination MAC address is recorded in a MAC table on the first device and a table item corresponding to a non-recorded destination MAC address are recorded in a MAC table on the second device, "second MAC table record" and "second MAC table record" represent, respectively, that a table item corresponding to a destination MAC address is recorded in a MAC table on the second device and a table item corresponding to a non-recorded destination MAC address are recorded in the MAC table on the second device, a "unicast message" in a forwarding action of the second device represents that the second device sends a unicast message to the first device, a "BUM message" in a forwarding action of the first device represents that the first device sends a message to the destination device according to a corresponding table item in the first MAC table, and a "DF send" represents that the first device sends a message to the destination device when the first device is a DF corresponding to the destination device, and a "DF check send" represents that the first device sends a DF message to the destination device regardless of whether the first device is the DF corresponding to the destination device or not.

It should be noted that, in an embodiment, the first device and/or the second device in the above embodiment of the method may include a main control board and an interface board, where the main control board and a processor in the interface board may cooperate to perform the above actions performed by the first device or the second device, and control a packet forwarding behavior of an ethernet switch chip (LAN switch, LSW) in the interface board. Specifically, referring to fig. 4 and 5, fig. 4 shows a hardware structure schematic of the main control board, and fig. 5 shows a hardware structure schematic of the interface board.

As shown in fig. 4, the main control board may include a processor 1, an ethernet interface (for managing a network port), a physical layer ethernet interface 1, an ethernet interface connected to the interface board processor, a volatile memory 1 (such as a random access memory RAM) and a nonvolatile memory 1 (such as a flash memory flash). The processor 1 is connected to the volatile memory 1, the nonvolatile memory 1, an ethernet interface (for managing a network port), and an ethernet interface connected to the interface board processor 1, and the ethernet interface (for managing a network port) is connected to the physical layer ethernet interface 1, and the ethernet interface connected to the interface board processor 2 is connected to the physical layer ethernet interface 2.

As shown in fig. 5, the interface board may include a processor 2, an ethernet interface connected to the main control board processor 1, an LSW, a physical layer ethernet interface 3, a volatile memory 2, and a nonvolatile memory 2. The processor 2 is respectively connected with the volatile memory 2, the nonvolatile memory 2, the LSW and the Ethernet interface connected with the main control board processor 1, and the volatile memory 3 is connected with the LSW.

The processor 1 and the processor 2 may be control units of a main control board and an interface board, respectively, and the running programs and static configuration parameters thereof may be stored in corresponding nonvolatile memories, while the codes executed when the programs run and related data may be placed in corresponding volatile memories. The processor 1 and the processor 2 can cooperatively complete the related operation of the first device or the second device in the above method embodiment, and effectively control the forwarding behavior of the LSW, and at the same time, can also control the LSW to initialize, send service table entries, send and receive protocol messages, process various interrupts (including port on-line and off-line processing), and the like. And, the LSW may have an external volatile memory 3, and the volatile memory 3 may be used to store a message that needs to be sent by the first device or the second device. In some application scenarios, the volatile memory 3 may also alleviate the problem of insufficient internal cache of the LSW chip. The physical layer ethernet interface 3 of the LSW connection may be in butt joint with the physical layer ethernet interface 2 on the main control board to complete the ethernet interface of the optical port or the electrical port.

In addition, in the embodiment of the present application, another schematic diagram of a hardware structure of the first device and/or the second device is provided. Referring to fig. 6, fig. 6 is a schematic diagram showing a hardware structure of another device according to an embodiment of the present application.

The device may be the first device of the above-described method embodiments, and the device may include at least one processor 601 and at least one memory 602. The processor 601 may be connected to a memory 602, for example by a bus 603 as shown in fig. 6. Of course, in practical applications, the connection between the processor 601 and the memory 602 may include various interfaces, transmission lines or buses, and the embodiment is not limited thereto.

The memory 602 may be used to store computer programs or instructions;

the processor 601 may be adapted to execute the computer program or instructions and to perform the following steps according to said computer program or instructions:

receiving a first message from a second device, wherein the first message comprises a message type indication, and the message type indication is used for indicating that the first message is a unicast message or a broadcast unknown unicast multicast (BUM) message;

when the first message is determined to be the unicast message according to the message type indication, or when the first message is determined to be the BUM message according to the message type indication and the first device is a designated forwarder DF of the destination device, sending a second message to the destination device;

The second message is a message obtained by decapsulating the first message by the first device, the destination device is connected to a plurality of network devices in multiple ways, and the plurality of network devices include the first device.

In some possible embodiments, the message type indicates a target field located in the first message, and/or the message type indicates a multicast address carried by the first message after being encapsulated by the multicast tunnel.

In some possible implementations, the first message is a VXLAN message including a VXLAN header of a virtual extensible local area network, and the target field is specifically a reserved field in the VXLAN header.

In some possible embodiments, the processor 601 may further perform the following steps according to the computer program or instructions:

and when the first message is determined to be the BUM message according to the message type indication and the first equipment is not DF of the target equipment, not sending a second message to the target equipment.

It should be noted that, the processor in the present application may include, but is not limited to, at least one of the following: a central processing unit (central processing unit, CPU), microprocessor, digital signal processor (digital signal processing, DSP), microcontroller (microcontroller unit, MCU), or artificial intelligence processor, each of which may include one or more cores for executing software instructions to perform operations or processes. The processor may be a single semiconductor chip, or may be integrated with other circuitry into a single semiconductor chip, for example, may form a system-on-a-chip (system-on-a-chip) with other circuitry (such as codec circuitry, hardware accelerator circuitry, or various buses and interface circuitry), or may be integrated into an application-specific integrated circuit (ASIC) as a built-in processor of the ASIC, which may be packaged separately or with other circuitry. The processor may further include necessary hardware accelerators, such as field programmable gate arrays (field programmable gate array, FPGAs), programmable logic devices (programmable logic device, PLDs), or logic circuits implementing dedicated logic operations, in addition to the cores for executing software instructions to perform the operations or processing.

The memory in the embodiment of the application can comprise at least one of the following types: read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM) or other types of dynamic storage devices that can store information and instructions, and electrically erasable programmable read-only memory (electrically erasable programmable-only memory, EEPROM). In some scenarios, the memory may also be, but is not limited to, a compact disk (compact disc read-only memory) or other optical disk storage, optical disk storage media, magnetic disk storage or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

The memory may be independent and coupled to the processor. The memory can store program codes for executing the technical scheme of the embodiment of the application, and the program codes are controlled by the processor to be executed, and the executed computer program codes can be also regarded as a driving program of the processor. For example, the processor is configured to execute computer program codes stored in the memory, thereby implementing the technical solution in the embodiment of the present application.

In addition, the embodiment of the present application further provides a message transmission apparatus, where the apparatus 700 may be applied to the first device in the foregoing method embodiment, and the apparatus 700 may specifically include a receiving module 701, a processing module 702 and a sending module 703:

a receiving module 701, configured to receive a first packet from a second device, where the first packet includes a packet type indication, where the packet type indication is used to indicate that the first packet is a unicast packet or a broadcast-unknown unicast multicast BUM packet;

a processing module 702, configured to send, when the first packet is determined to be the unicast packet according to the packet type indication, or when the first packet is determined to be the BUM packet according to the packet type indication and the first device is a designated forwarder DF of the destination device, a second packet to the destination device through a sending module 703;

In some possible implementations, the processing module 702 is further configured to determine not to send the second message to the destination device when the first device determines that the first message is the BUM message according to the message type indication and the first device is not the DF of the destination device.

It should be noted that, because the content of information interaction and execution process between the modules of the above-mentioned apparatus is based on the same concept as the method embodiment in the embodiment of the present application, the technical effects brought by the content are the same as the method embodiment in the embodiment of the present application, and specific content can be referred to the description in the foregoing method embodiment shown in the embodiment of the present application, which is not repeated here.

It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described apparatus, modules and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the present application, "english: of", corresponding "(english: retrieving)" and "corresponding" (english: corresponing) "may sometimes be used in combination, and it should be noted that the meaning to be expressed is consistent when the distinction is not emphasized.

It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment of the present application is not to be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the present application, "at least one" means one or more. "plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural. In addition, in order to facilitate the clear description of the technical solution of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", etc. are used to distinguish the same item or similar items having substantially the same function and effect. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.

The system architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution provided in the embodiments of the present application, and do not constitute a limitation on the technical solution provided in the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiments of the present application is equally applicable to similar technical problems.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims

1. A method for transmitting a message, the method comprising:

the method comprises the steps that first equipment receives a first message from second equipment, wherein the first message comprises a message type indication, and the message type indication is used for indicating that the first message is a unicast message or a broadcast unknown unicast multicast (BUM) message;

When the first device determines that the first message is the unicast message according to the message type indication, under the condition that an item of a target MAC address corresponding to the target device is not recorded in a local Media Access Control (MAC) table of the first device, the first device sends a second message to a plurality of devices, wherein the plurality of devices comprise the target device; or when the first device determines that the first message is the BUM message according to the message type indication and the first device is a designated forwarder DF of the destination device, the first device sends a second message to the destination device;

2. The method according to claim 1, wherein the message type indication is located in a target field of the first message, and/or the message type indication is a multicast address carried by the first message after being encapsulated by a multicast tunnel.

3. The method according to claim 2, wherein the first message is a VXLAN message comprising a virtual extensible local area network VXLAN header, the destination field being in particular a reserved field in the VXLAN header.

4. A method according to any one of claims 1 to 3, further comprising:

and when the first device determines that the first message is the BUM message according to the message type indication and the first device is not the DF of the target device, the first device does not send a second message to the target device.

5. A message transmission device, wherein the device is applied to a first device, and the device comprises a receiving module, a processing module and a sending module:

the receiving module is configured to receive a first packet from a second device, where the first packet includes a packet type indication, where the packet type indication is used to indicate that the first packet is a unicast packet or a broadcast-unaware unicast multicast BUM packet;

the processing module is configured to, when it is determined that the first packet is the unicast packet according to the packet type indication, send, by the first device, a second packet to a plurality of devices, where the table entry of the target MAC address corresponding to the destination device is not recorded in the local MAC table of the first device, where the plurality of devices includes the destination device; or when the first message is determined to be the BUM message according to the message type indication and the first device is a designated forwarder DF of the destination device, sending a second message to the destination device through the sending module;

6. The apparatus of claim 5, wherein the message type indication is located in a target field of the first message, and/or wherein the message type indication is a multicast address carried by the first message after being encapsulated by a multicast tunnel.

7. The apparatus of claim 6, wherein the first message is a VXLAN message including a virtual extensible local area network VXLAN header, and wherein the destination field is specifically a reserved field in the VXLAN header.

8. The apparatus according to any one of claims 5 to 7, further comprising:

the processing module is further configured to determine not to send a second message to the destination device when the first message is determined to be the BUM message according to the message type indication and the first device is not the DF of the destination device.

9. A computer device comprising a processor and a memory;

The memory is used for storing a computer program or instructions;

the processor is configured to execute the computer program or instructions to cause the computer device to perform the method for transmitting a message according to any one of claims 1 to 4.

10. A storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of message transmission of any of claims 1 to 4.