CN113630300B

CN113630300B - Method and node for message transmission

Info

Publication number: CN113630300B
Application number: CN202010387411.6A
Authority: CN
Inventors: 王震宇
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-05-09
Filing date: 2020-05-09
Publication date: 2023-08-08
Anticipated expiration: 2040-05-09
Also published as: WO2021227873A1; CN113630300A

Abstract

The application provides a method and a device for message transmission. The method comprises the following steps: the first node can store a first association relationship between the first address and the second address of the container in the second node, so that the application management module in the first node can determine the second address of the first container according to the first address and the first association relationship of the first container in the second node, and further write the second address of the first container into the operation system, so that the second container in the first node can obtain the IP address and the MAC address of the first container from the operation system, and the message can be sent to the first container.

Description

Method and node for message transmission

Technical Field

The present application relates to the field of communications, and more particularly, to a method and a node for packet transmission.

Background

With the increase of the network scale, the telecommunication system is more and more complex, so that a plurality of challenges are brought, including the development and online of newly added services, the operation and resource utilization rate of the system, and the like. To address these challenges, telecommunication systems utilize virtualization technology and cloud technology in the information technology (information technology, IT) industry.

Network function virtualization (network functions virtualization, NFV) technology can be understood simply as migrating the functions of individual network elements used in a telecommunications network from a current dedicated hardware platform to a general purpose commercial shelf product server. Each network element used in the telecommunication network is converted into an independent application through the NFV technology, the independent application can be flexibly deployed on a unified infrastructure platform constructed based on other equipment such as a standard server, a storage and a switch, virtual resources are provided for an infrastructure hardware device resource pool and virtualization through a virtualization technology, and virtual resources are provided for an upper layer application, so that the application and hardware decoupling are realized, each application can quickly increase the virtual resources to realize the purpose of quickly expanding the system capacity, or can quickly reduce the virtual resources to realize the purpose of contracting the system capacity, and the elasticity of the network is greatly improved. The shared resource pool is formed by adopting a general commercial off-the-shelf (COTS) server, and newly developed service does not need to independently deploy hardware equipment, so that the on-line time of the new service is greatly shortened.

The most thorough way to cloud a telecommunication system is to transform two-layer communication into three-layer communication. In the conventional scheme, the private two-layer message interaction is realized by encapsulating the two-layer message in a standard internet protocol (internet protocol, IP)/user datagram protocol (user datagram protocol, UDP) message. For example, constructing a two-layer interworking virtual extensible local area network (virtual expandable LAN, VXLAN) network requires that each VXLAN node be aware of all other VXLAN nodes' information, i.e., the IP address and media access control (media access control, MAC) address of the container in all VXLAN nodes. And synchronization of IP addresses and MAC addresses between containers in VXLAN nodes in VXLAN networks requires deployment of VXLAN controllers in the network. That is, in the conventional scheme, the telecommunication system needs to introduce an additional controller, so that the management complexity is high.

Disclosure of Invention

The application provides a method and a node for message transmission, which can reduce the management complexity of a communication system.

In a first aspect, a method for transmitting a message is provided, where an application management module in a first node determines a second address of a first container in a second node according to a first address and a first association relationship of the first container, where the first association relationship is an association relationship between the first address and the second address of the container in the second node, the first address is an IP address, the second address is an MAC address, or the first address is an MAC address, and the second address is an IP address; the application management module writes the second address in an operating system, wherein the second address is a destination address of a second container transmission message in the first node.

The first node can store a first association relationship between the first address and the second address of the container in the second node, so that the application management module in the first node can determine the second address of the first container according to the first address and the first association relationship of the first container in the second node, and further write the second address of the first container into the operation system, so that the second container in the first node can obtain the IP address and the MAC address of the first container from the operation system, and the message can be sent to the first container.

In some possible implementations, before the application management module determines the second address according to the first address, the method further includes: the application management module receives request information from the second container, wherein the request information is used for requesting a second address corresponding to the first address.

Under the condition that the second address corresponding to the first address of the first container is not stored in the operating system of the first node, the second container can send request information to the application management module in the first node so as to request the second address corresponding to the first address, thereby sending the message to the first container. That is, the second container requests the application management module for the second address corresponding to the first address only when there is a demand, so that too many unnecessary addresses can be prevented from being stored in the operating system, thereby saving the storage space of the operating system.

In some possible implementations, in a case where the first address is an IP address, the method further includes: the application management module determines the IP address of the second node according to the IP address of the first container and a second association relationship, wherein the second node is used for forwarding the message to the first container, and the second association relationship is an association relationship between the IP address of the node and the IP address of the container in the second node; the application management module writes the IP address of the second node in the operating system.

The application management module can find the IP address of the node according to the association relation and the IP address of the container, and forward the message to the container in the node through the IP address of the node. That is, the node in the embodiment of the present application may realize that no additional controller needs to be introduced to obtain the node to which the container to be sent the message belongs, thereby reducing the management complexity of the system.

In some possible implementations, the IP address of the first container includes at least one byte, the IP address of the second node includes at least one byte, and the second association is that a value of a part of bytes in the IP address of the first container is the same as a value of a part of bytes in the IP address of the second node.

The second association relationship may be that part of bytes have the same value, that is, the association between the IP address of the container and the IP address of the node is achieved in a simple manner, so that the management complexity of the system is further reduced.

In some possible implementations, the IP address of the first container includes four bytes, the IP address of the second node includes four bytes, and the second association relationship is that a value of a second byte in the IP address of the first container is the same as a value of a third byte in the IP address of the second node, and a value of a third byte in the IP address of the first container is the same as a value of a fourth byte in the IP address of the second node.

The application management module can find the IP address of the second container of the node according to the association relation and the IP address of the first container, namely, the implementation does not need to introduce an extra controller, and the management complexity of the system is reduced.

In some possible implementations, the MAC address of the first container includes at least one byte, and the IP address of the first container includes at least one byte, and the first association relationship is that a value of a part of bytes in the MAC address of the first container is the same as a value of a part of bytes in the IP address of the first container.

The first association relationship may be that part of bytes have the same value, that is, the association between the IP address of the container and the IP address of the node is achieved in a simple manner, so that the management complexity of the system is further reduced.

In some possible implementations, the MAC address of the first container includes six bytes, the IP address of the first container includes four bytes, the first association is that a value of a fourth byte in the MAC address of the first container is the same as a value of a second byte in the IP address of the first container, a value of a fifth byte in the MAC address of the first container is the same as a value of a third byte in the IP address of the first container, and a value of a sixth byte in the MAC address of the first container is the same as a value of a fourth byte in the IP address of the first container.

In some possible implementations, in a case where the first address is a MAC address, the method further includes: and determining the IP address of the second node according to the MAC address of the first container and a third association relation, wherein the third association relation is the association relation between the IP address of the node and the MAC address of the first container, and the second node is used for forwarding the message to the first container in the IP address writing operation system of the second node.

The application management module can find the IP address of the second node according to the third association relation and the MAC address of the first container, and forward the message to the container in the node through the IP address of the node. That is, the node in the embodiment of the present application may realize that no additional controller needs to be introduced to obtain the node to which the container to be sent the message belongs, thereby reducing the management complexity of the system.

In some possible implementations, the MAC address of the first container includes at least one byte, the IP address of the second node includes at least one byte, and the third association is that a value of a part of bytes in the MAC address of the first container is the same as a value of a part of bytes in the IP address of the second node.

The third association relationship may be that part of bytes have the same value, that is, the association between the IP address of the container and the IP address of the node is realized in a simple manner, so as to further reduce the management complexity of the system.

In some possible implementations, the MAC address of the first container includes six bytes, and the IP address of the second node includes four bytes, and the third association relationship is that a value of a fifth byte in the MAC address of the first container is the same as a value of a third byte in the IP address of the second node, and a value of a sixth byte in the MAC address of the first container is the same as a value of a fourth byte in the IP address of the second node.

In a second aspect, a method for transmitting a message is provided, the method comprising: a second container in a first node sends request information to an application management module, wherein the request information is used for requesting a second address of the first container corresponding to a first address of the first container in the second node, the first address is an IP address, the second address is an MAC address, or the first address is an MAC address, and the second address is an IP address; the second container detects a second address of the first container corresponding to the first address of the first container from an operating system; and the second container sends the message to the first container according to the first address of the first container and the second address of the first container.

Under the condition that the second address corresponding to the first address of the first container is not stored in the operating system of the first node, the second container can send request information to the application management module in the first node so as to request the second address corresponding to the first address, thereby sending the message to the first container. That is, the second container requests the application management module for the second address corresponding to the first address only when there is a demand, so that too many unnecessary addresses can be prevented from being stored in the operating system, thereby saving the storage space of the operating system. Furthermore, the embodiments of the present application reduce the management complexity of the system relative to conventional schemes that introduce additional controllers to obtain the addresses of containers in nodes other than the present node.

In some possible implementations, in a case where the first address is a MAC address and the second address is an IP address, the method further includes: the first container detects the IP address of a second node corresponding to the MAC address of the first container from the operating system; the sending, by the second container, the message to the first container according to the first address of the first container and the second address of the first container includes: the second container sends the message to a second node corresponding to the IP address of the second node, and the second node is used for forwarding the message to the first container.

If the first node cannot directly find the first container (i.e. no routing information to the first container), the second container needs to find the second node including the first container, and then the second node forwards the message to the first container. That is, the corresponding relation can realize the transmission of the messages of the containers among the cross nodes, and compared with the traditional scheme, the method introduces an additional controller, thereby reducing the management complexity of the system.

In a third aspect, a node for message transmission is provided, the node being configured to perform the method of the first aspect, or any one of the possible implementation manners of the first aspect.

In a fourth aspect, there is provided a node for message transmission, the node being adapted to perform the method of the second aspect, or any one of the possible implementations of the second aspect.

In a fifth aspect, there is provided a node for message transmission, comprising a processor and a memory for storing program instructions, the processor being adapted to invoke the program instructions to perform the method of the first aspect, or any of the possible implementations of the first aspect.

In a sixth aspect, there is provided a node for message transmission, comprising a processor and a memory, the memory being for storing program instructions, the processor being for invoking the program instructions to perform the above-described second aspect, or a method in any one of the possible implementations of the above-described second aspect.

In a seventh aspect, a computer readable storage medium is provided, the computer readable storage medium storing program code for execution by a device, the program code comprising instructions for performing the method of the first aspect, or any one of the possible implementations of the first aspect.

In an eighth aspect, a computer readable storage medium is provided, the computer readable storage medium storing program code for execution by a device, the program code comprising instructions for performing the method of the first aspect, or any one of the possible implementations of the first aspect.

In a ninth aspect, a chip is provided, the chip comprising a processor and a data interface, the processor reading instructions stored on a memory via the data interface to perform the method of the first aspect, or any one of the possible implementation manners of the first aspect.

In a tenth aspect, a chip is provided, the chip comprising a processor and a data interface, the processor reading instructions stored on a memory via the data interface to perform the method of the first aspect, or any one of the possible implementation manners of the first aspect.

In an eleventh aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect described above, or any possible implementation thereof.

In a twelfth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of the second aspect described above, or any possible implementation thereof.

In a thirteenth aspect, there is provided a communication system comprising the node of the third aspect and the node of the fourth aspect. Wherein the node according to the third aspect and the node according to the fourth aspect may be different nodes. For example, the container of the first node may obtain the first address or the second address of the container in the second node from the operating system in the third node. Or the node of the third aspect and the node of the fourth aspect may be the same node, for example, the application management module and the second container in the same node may interactively communicate.

Based on the technical scheme, the first node can store the first association relationship between the first address and the second address of the container in the second node, so that the application management module in the first node can determine the second address of the first container according to the first address and the first association relationship of the first container in the second node, and further write the second address of the first container into the operation system, the second container in the first node can obtain the IP address and the MAC address of the first container from the operation system, and the message can be sent to the first container.

Drawings

FIG. 1 is a schematic block diagram of a communication system of an embodiment of the present application;

fig. 2 is a schematic diagram of the structure of VXLAN messages;

FIG. 3 is a schematic flow chart of a method for message transmission according to an embodiment of the present application;

FIG. 4 is a schematic block diagram of a node for message transmission according to one embodiment of the present application;

FIG. 5 is a schematic block diagram of a node for message transmission according to one embodiment of the present application;

FIG. 6 is a schematic block diagram of a node for message transmission according to another embodiment of the present application;

fig. 7 is a schematic block diagram of a node for message transmission according to another embodiment of the present application.

Detailed Description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

Fig. 1 shows a communication system of an embodiment of the present application. At least two nodes, such as node 1 and node 2 shown in fig. 1, may be included in the communication system. Taking node 1 as an example for illustration, node 1 may include an application management module and a container management module and at least one container (e.g., container 1, container 2, and container 3). The application management module is used for creating an interface, distributing the IP address and the MAC address of the service, and the container management module is used for creating a container.

It is understood that the application management module may be a VXLAN application management module. In the case where the application management module is a VXLAN application management module, the corresponding interface may be a VXLAN interface.

In the traditional scheme, the interaction of the private two-layer messages is realized by encapsulating the two-layer messages in the standard IP/UDP messages. The structure of VXLAN messages is shown in fig. 2. For example, constructing a two-layer interworking virtual extensible local area network (virtual expandable LAN, VXLAN) network requires that each VXLAN node be aware of all other VXLAN nodes' information, i.e., the IP address and media access control (media access control, MAC) address of the container in all VXLAN nodes. And synchronization of IP addresses and MAC addresses between containers in VXLAN nodes in VXLAN networks requires deployment of VXLAN controllers in the network. That is, in the conventional scheme, the telecommunication system needs to introduce an additional controller, so that the management complexity is high.

Fig. 3 shows a schematic flow chart of a method for message transmission according to an embodiment of the present application.

It should be appreciated that embodiments of the present application may be applied to the communication system shown in fig. 1.

301, the second container in the first node may send request information to the application management module, where the request information is used to request a second address corresponding to a first address of the first container in the second node, where the first address is an IP address, the second address is a MAC address, or the first address is a MAC address, and the second address is an IP address.

Specifically, if the second container in the first node wants to send a message to the first container in the second node, if only the first address of the first container is known (for example, only the first address of the first container is stored in the operating system of the first node), request information may be sent to the application management module in the first node to request the second address corresponding to the first address. Wherein, if the first address is an IP address, the second address may be a MAC address; if the first address is a MAC address, the second address may be an IP address. That is, the second container needs to obtain the IP address and the MAC address of the first container to enable sending the message to the first container.

It will be appreciated that the first node may include other containers besides the second container, which is not limited in this application. Similarly, the second node may further include other containers besides the first container, which is not limited in this application.

302, an application management module in a first node determines a second address of the first container according to a first address and a first association relationship of the first container, where the first association relationship is an association relationship between the first address and the second address of the container in the second node.

Specifically, the application management module may store a first association relationship between a first address and a second address of a container in the second node. That is, the application management module may obtain the second address according to the first address and the first association relationship, for example, directly obtain the second address, or indirectly derive the second address.

It is understood that the first association may include that a first address of a certain container (e.g., a first container) in the second node has an association with a second address of the first container, or may include that a first address of each container in one or more containers in the second node has an association with a second address. For example, the first association relationship includes a correspondence relationship between an IP address of the first container and a MAC address of the first container.

It is further understood that the first association may also be regarded as a pre-established rule. The management module should derive the second address from the first address and the rule.

Optionally, in the case that the MAC address of the first container includes at least one byte, the IP address of the first container includes at least one byte, the first association relationship is that a value of a part of bytes in the MAC address of the first container is the same as a value of a part of bytes in the IP address of the first container.

Specifically, when the number of partial bytes having the same value as the number of partial bytes in the IP address in the MAC address is plural, the plural bytes may be continuous or discontinuous, and the present application is not limited thereto. That is, the value of each byte in the partial bytes in the MAC address of the first container may be the same as the value of a certain byte in the plurality of bytes of the IP address of the first container, or the whole value of the partial bytes in the MAC address of the first container may be the same as the whole value of the plurality of bytes of the IP address of the first container.

It is understood that a byte may include one or more bits. The bits included in different bytes with the same value may be the same or different, which is not limited in this application.

It is further understood that the embodiments of the present application may be applied to (internet protocol version 4, IPv 4) scenarios, and may also be referred to in IPv6 scenarios, which are not limited in this application.

It may be further understood that the first association relationship may be temporarily generated, or may be known to be stored in an application management module, which is not limited in this application.

Optionally, in the case that the MAC address of the first container includes six bytes, the IP address of the first container includes four bytes, the first association relationship is that the value of the fourth byte in the MAC address of the first container is the same as the value of the second byte in the IP address of the first container, the value of the fifth byte in the MAC address of the first container is the same as the value of the third byte in the IP address of the first container, and the value of the sixth byte in the MAC address of the first container is the same as the value of the fourth byte in the IP address of the first container.

Specifically, if the MAC address includes six bytes, the MAC address may have a structure of "0a:0a:0a: service IP 4 th byte: service IP 5 th byte: service IP 6 th byte".

Wherein the second byte of the service IP address may be different from the fourth byte of the MAC address in system. For example, the IP address is "10.101.10The MAC address corresponding to 100 "is" 0a:0a:65:0a64 "(the numbers on the underline have correspondence, the numbers of the inclined fonts also have correspondence). I.e. IPBytes of the address are represented by binary, and bytes of the MAC address are represented by 16.

It should be noted that, the bytes other than the bytes having the association relationship may be preset, for example, the first byte in the IP address is set to "10", the first three bytes of the MAC address are set to "0a:0 a", or may be other preset values, which are not limited in this application.

Optionally, in the case that the first address is an IP address, the application management module may further determine an IP address of the second node according to the IP address of the first container and the second association relationship, and write the IP address of the second node into the system. The second node is configured to forward a message to the first container, where the second association relationship is an association relationship between an IP address of the node and an IP address of a container in the second node.

Specifically, if the first address is an IP address and the second address is an MAC address, if the first node cannot directly find the first container (i.e., no routing information to the first container), the second container needs to find the second node including the first container, and then the second node forwards the message to the first container. For example, the second container sends layer 3MISS (L3 MISS) information to the application management module, and the application management module knows that the IP address lacks routing information when detecting the L3MISS information.

It may be understood that the second association relationship may include a correspondence relationship between a certain container (for example, the first container) in the second node and an IP address of the second node, or may include an association relationship between each container in the plurality of containers in the second node and an IP address of the node, which is not limited in this application.

Optionally, the IP address of the first container includes at least one byte, and the IP address of the second node includes at least one byte, and the second association relationship is that a value of a part of bytes in the IP address of the first container is the same as a value of a part of bytes in the IP address of the second node.

Specifically, the IP address of the first container includes four bytes, the IP address of the second node includes four bytes, and the second association relationship is that the value of the second byte in the IP address of the first container is the same as the value of the third byte in the IP address of the second node, and the value of the third byte in the IP address of the first container is the same as the value of the fourth byte in the IP address of the second node.

For example, if the IP address of the first container is "10".10110.100", the IP address of the second node is" 172.16".101.10”。

Note that the first two bytes of the IP address of the node may be preset, for example, "172.16" is the first two bytes of the IP address of the node. Wherein the last byte in the IP address of the container may be a unique sequence number within the node.

Optionally, when the first address is a MAC address, the application management module may further determine an IP address of the second node according to the MAC address of the first container and a third association relationship, where the third association relationship is an association relationship between the IP address of the node and the MAC address of the first container, and write the IP address of the second node into the system. The second node is configured to forward the message to the first container.

Specifically, if the second container cannot find the first container according to the MAC address of the first container, the second container needs to find the second node including the first container first, and then the second node forwards the message to the first container. For example, the second container sends layer 2MISS (L2 MISS) information to the application management module, and the application management module knows that the MAC address lacks routing information when detecting the L2MISS information.

Optionally, the MAC address of the first container includes at least one byte, the IP address of the second node includes at least one byte, and the third association relationship is that a value of a part of bytes in the MAC address of the first container is the same as a value of a part of bytes in the IP address of the second node.

Specifically, the MAC address of the first container includes six bytes, the IP address of the second node includes four bytes, and the third association relationship is that the value of the fifth byte in the MAC address of the first container is the same as the value of the third byte in the IP address of the second node, and the value of the sixth byte in the MAC address of the first container is the same as the value of the fourth byte in the IP address of the second node.

For example, the MAC address of the first container is "0a:0a:0a:661e:6a ", the IP address of the corresponding second node is" 172.16".102.30”。

It will be appreciated that the first two bytes of the IP address of the node may be pre-set, e.g., the first two bytes of the IP address of the node is "172.16".

303, the application management module writes the second address in the operating system, where the second address is a destination address of the second container transmission packet in the first node.

In particular, the application management module may write a second address into a system cache of the system, for example, the second address into a forwarding database (forwarding database, FDB) table.

It will be appreciated that the application management module may be started with the operating system being started, after which it may be checked whether the interface of the first node is properly configured. If the configuration is not correct, the configuration of the interface is carried out. For example, the interface is a VXLAN interface.

It is also understood that the operating system may be an OS.

It is further understood that the application management module may also actively perform updating the second address corresponding to the first address, for example, a timing update. That is, step 301 may not be performed in the present application.

304, the second container detects a second address of the first container corresponding to the first address of the first container from the operating system.

305, the second container sends a message to the first container according to the second address of the first container and the first address of the first container.

The first node can store a first association relationship between the first address and the second address of the container in the second node, so that the application management module in the first node can determine the second address of the first container according to the first address and the first association relationship of the first container in the second node, and further write the second address of the first container into the operation system, so that the second container can obtain the IP address and the MAC address of the first container from the operation system, and the message can be sent to the first container.

It should be understood that the specific examples in the embodiments of the present application are intended only to help those skilled in the art to better understand the embodiments of the present application and are not intended to limit the scope of the embodiments of the present application.

It should be further understood that the sequence numbers of the above processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and the internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

It is also to be understood that in the various embodiments of the application, terms and/or descriptions of the various embodiments are consistent and may be referenced to one another in the absence of a particular explanation or logic conflict, and that the features of the various embodiments may be combined to form new embodiments in accordance with their inherent logic relationships.

The method provided in the embodiment of the present application is described in detail above with reference to fig. 3. The following describes in detail the nodes provided in the embodiments of the present application with reference to fig. 4 to 7. It should be understood that the descriptions of the apparatus embodiments and the descriptions of the method embodiments correspond to each other, and thus, descriptions of details not shown may be referred to the above method embodiments, and for the sake of brevity, some parts of the descriptions are omitted.

Fig. 4 shows a schematic block diagram of a node 400 for message transmission according to an embodiment of the present application.

It should be appreciated that the node 400 may implement the method of the embodiment shown in fig. 3. For example, the node 400 may include an application management module 410 and an operating system 420 as shown in FIG. 3. Optionally, the node 400 may also include a second container as shown in fig. 3.

It is also understood that the node 400 may be a physical machine or a virtual machine.

The application management module 410 is configured to determine, according to a first address and a first association relationship of a first container in a second node, a second address of the first container, where the first association relationship is an association relationship between the first address and the second address of the container in the second node, the first address is an IP address, the second address is an MAC address, or the first address is an MAC address, and the second address is an IP address;

The application management module 410 is further configured to write the second address in the operating system 420, where the second address is a destination address of a second container transport packet in the first node

Optionally, the application management module 410 is further configured to receive request information from the second container, where the request information is used to request a second address corresponding to the first address.

Optionally, the application management module 410 is further configured to determine an IP address of the second node according to an IP address of the first container and a second association relationship, where the second node is configured to forward the packet to the first container, and the second association relationship is an association relationship between an IP address of a node and an IP address of a container in the second node; the application management module is further configured to write an IP address of the second node in the operating system.

Optionally, the IP address of the first container includes four bytes, the IP address of the second node includes four bytes, the second association relationship is that a value of a second byte in the IP address of the first container is the same as a value of a third byte in the IP address of the second node, and a value of a third byte in the IP address of the first container is the same as a value of a fourth byte in the IP address of the second node.

Optionally, the MAC address of the first container includes at least one byte, and the IP address of the first container includes at least one byte, where the first association relationship is that a value of a part of bytes in the MAC address of the first container is the same as a value of a part of bytes in the IP address of the first container.

Optionally, the MAC address of the first container includes six bytes, the IP address of the first container includes four bytes, the first association relationship is that a value of a fourth byte in the MAC address of the first container is the same as a value of a second byte in the IP address of the first container, a value of a fifth byte in the MAC address of the first container is the same as a value of a third byte in the IP address of the first container, and a value of a sixth byte in the MAC address of the first container is the same as a value of a fourth byte in the IP address of the first container.

Fig. 5 illustrates a node 500 for message transmission according to an embodiment of the present application. The node may employ a hardware architecture as shown in fig. 5. The node may include a processor 510 and a transceiver 520, and optionally the node may further include a memory 530, the processor 510, transceiver 520 and memory 530 communicating with each other through an internal connection path. Some of the relevant functions implemented by the application management module 410 in fig. 4 may be implemented by the processor 510, and another part of the relevant functions may be implemented by the processor 510 controlling the transceiver 520.

Alternatively, the processor 510 may be a general purpose central processing unit (central processing unit, CPU), microprocessor, application-specific integrated circuit (ASIC), special purpose processor, or one or more integrated circuits for performing the techniques of embodiments of the present application. In the alternative, a processor may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions). For example, a baseband processor, or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processor may be used to control a communication device (e.g., a base station, a terminal, or a chip, etc.), execute a software program, and process the data of the software program.

Alternatively, the processor 510 may comprise one or more processors, e.g. one or more central processing units (central processing unit, CPU), which in case of a single CPU may be a single core CPU or a multi-core CPU.

The transceiver 520 is used to transmit and receive data and/or signals, as well as to receive data and/or signals. The transceiver may include a transmitter for transmitting data and/or signals and a receiver for receiving data and/or signals.

The memory 530 includes, but is not limited to, random access memory (random access memory, RAM), read-only memory (ROM), erasable programmable memory (erasable programmable read only memory, EPROM), and compact disc read-only memory (compact disc read, CD-ROM), the memory 530 for storing related instructions and data.

Memory 530 is used to store program codes and data for the network device, either as a separate device or integrated in processor 510.

Specifically, the processor 510 is configured to control the transceiver to perform information transmission with the second container. Reference may be made specifically to the description of the method embodiments, and no further description is given here.

In a specific implementation, the node 500 may also include an output device and an input device, as one embodiment. The output device communicates with the processor 510 and may display information in a variety of ways. For example, the output device may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a Cathode Ray Tube (CRT) display device, or a projector (projector), or the like. The input device(s) is in communication with the processor 510 and may receive user input in a variety of ways. For example, the input device may be a mouse, a keyboard, a touch screen device, a sensing device, or the like.

It will be appreciated that figure 5 shows only a simplified design of a communication node. In practical applications, the node may also include necessary other elements, including but not limited to any number of transceivers, processors, controllers, memories, etc., and all nodes that can implement the present application are within the scope of protection of the present application.

It should also be appreciated that the node 500 may also be a chip or a system-on-chip. When the node is a chip or a system-on-chip, the application management module 410 in the node 500 may include a data transmission interface, an interface circuit, a data transmission circuit or pin, and a processor, a processing circuit or a logic circuit, and the storage unit may be a memory or a storage circuit.

Fig. 6 shows a schematic block diagram of a node 600 for message transmission according to an embodiment of the present application.

It should be appreciated that the node 600 may implement the method shown in fig. 3. The node may comprise a second container in the embodiment shown in fig. 3. The node 600 may also include an application management module and an operating system as described in fig. 3. That is, the node shown in fig. 4 is the same node as the node shown in fig. 6. I.e. the same node content application management module interacts with the second container. Or the node shown in fig. 4 is a different node than the node shown in fig. 6, for example, the second container of the first node may obtain the first address or the second address of the first container in the second node from the operating system in the third node.

It is also understood that the node 600 may be a physical machine or a virtual machine.

The node 600 may comprise means for performing the various operations of the method embodiments described above. Each module in the node 600 is configured to implement a corresponding flow of the second container in any of the methods described above. The node 600 includes a transceiver module 610 and a processing module 620.

The transceiver module 610 is configured to send request information to an application management module, where the request information is used to request a second address of a first container corresponding to a first address of the first container in a second node, where the first address is an IP address, the second address is a MAC address, or the first address is a MAC address, and the second address is an IP address;

The processing module 620 is configured to detect, from an operating system, a second address of the first container corresponding to the first address of the first container;

the transceiver module 610 is further configured to send a message to the first container according to the first address of the first container and the second address of the first container.

Optionally, the method comprises the step of. The processing module 620 is further configured to detect, from the operating system, an IP address of a second node corresponding to the MAC address of the first container, where the first address is the MAC address and the second address is the IP address; the transceiver module 610 is specifically configured to: and sending the message to a second node corresponding to the IP address of the second node, wherein the second node is used for forwarding the message to the first container.

Fig. 7 illustrates a node 700 for message transmission provided in an embodiment of the present application. The node may employ a hardware architecture as shown in fig. 7. The node may include a processor 710 and a transceiver 720, and optionally the node may further include a memory 730, the processor 710, the transceiver 720 and the memory 730 communicating with each other through an internal connection path. Some of the relevant functions implemented by the processing module 620 in fig. 6 may be implemented by the processor 710, and some of the relevant functions implemented by the transceiver module 610 may be implemented by the processor 710 controlling the transceiver 720.

Alternatively, the processor 710 may be a general purpose central processing unit (central processing unit, CPU), microprocessor, application-specific integrated circuit (ASIC), special purpose processor, or one or more integrated circuits for performing the techniques of embodiments of the present application. In the alternative, a processor may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions). For example, a baseband processor, or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processor may be used to control communication nodes (e.g., base stations, terminals, or chips, etc.), execute software programs, and process data of the software programs.

Alternatively, the processor 710 may include one or more processors, including, for example, one or more central processing units (central processing unit, CPU), which may be a single-core CPU or a multi-core CPU in the case where the processor is a CPU.

The transceiver 720 is used to transmit and receive data and/or signals, as well as to receive data and/or signals. The transceiver may include a transmitter for transmitting data and/or signals and a receiver for receiving data and/or signals.

The memory 730 includes, but is not limited to, random access memory (random access memory, RAM), read-only memory (ROM), erasable programmable memory (erasable programmable read only memory, EPROM), compact disc read-only memory (compact disc read-only memory, CD-ROM), and the memory 730 is configured to store associated instructions and data.

Memory 730 is used to store program codes and data for the network devices, either as separate devices or integrated in processor 710.

Specifically, the processor 710 is configured to control the transceiver to perform information transmission with the application management module. Reference may be made specifically to the description of the method embodiments, and no further description is given here.

In a specific implementation, the node 700 may also include an output device and an input device, as one embodiment. The output device communicates with the processor 710 and can display information in a variety of ways. For example, the output device may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a Cathode Ray Tube (CRT) display device, or a projector (projector), or the like. The input device(s) is in communication with the processor 710 and may receive user input in a variety of ways. For example, the input device may be a mouse, a keyboard, a touch screen device, a sensing device, or the like.

It will be appreciated that figure 7 shows only a simplified design of a communication node. In practical applications, the node may also include necessary other elements, including but not limited to any number of transceivers, processors, controllers, memories, etc., and all network devices that may implement the present application are within the scope of the present application.

It should also be appreciated that the node 700 may also be a chip or a system-on-chip. When the node is a chip or a system-on-chip, the transceiver module 710 in the node 700 may be a data transmission interface, an interface circuit, a data transmission circuit or a pin, the processing module 720 may be a processor, a processing circuit or a logic circuit, and the storage unit may be a memory or a storage circuit.

It should be understood that when the above node is a chip, the chip may be a field programmable gate array (field programmable gate array, FPGA), an application specific integrated chip (application specific integrated circuit, ASIC), a system on chip (SoC), a central processing unit (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chips.

Optionally, the embodiment of the present application further shows a system, which includes the node 400 shown in fig. 4 and the node 600 shown in fig. 6.

As another form of the present embodiment, there is provided a computer-readable storage medium having stored thereon instructions that, when executed, perform the method of the above-described method embodiment.

As another form of this embodiment, there is provided a computer program product containing instructions that, when executed, perform the method of the above-described method embodiment.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

It should be appreciated that the processor may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), an off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

In the present application, "at least one" means one or more, and "a 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.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present invention, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between 2 or more computers. Furthermore, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with one another in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

It should also be understood that the first, second, and various numerical numbers referred to herein are merely descriptive convenience and are not intended to limit the scope of embodiments of the present application.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. Wherein a or B is present alone, the number of a or B is not limited. Taking a alone as an example, it is understood that there are one or more a.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

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

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods 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 each embodiment 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 functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for message transmission, comprising:

the method comprises the steps that an application management module in a first node derives a second address of a first container according to a first address and a first association relation of the first container in a second node, wherein the first association relation is the association relation between the first address and the second address of the container in the second node, the first association relation is a preset rule, the first address is an Internet Protocol (IP) address, the second address is a Media Access Control (MAC) address, or the first address is an MAC address, and the second address is an IP address;

the application management module writes the second address in an operating system, wherein the second address is a destination address of a second container transmission message in the first node.

2. The method of claim 1, wherein the application management module is further configured to, prior to determining the second address from the first address:

the application management module receives request information from the second container, wherein the request information is used for requesting a second address corresponding to the first address.

3. The method according to claim 1 or 2, wherein in case the first address is an IP address, the method further comprises:

The application management module determines the IP address of the second node according to the IP address of the first container and a second association relationship, wherein the second node is used for forwarding the message to the first container, and the second association relationship is an association relationship between the IP address of the second node and the IP address of the container in the second node;

the application management module writes the IP address of the second node in the operating system.

4. A method according to claim 3, wherein the IP address of the first container comprises at least one byte, the IP address of the second node comprises at least one byte, and the second association is that the value of a part of the bytes in the IP address of the first container is the same as the value of a part of the bytes in the IP address of the second node.

5. The method of claim 4, wherein the IP address of the first container comprises four bytes, the IP address of the second node comprises four bytes, the second association is that the value of the second byte in the IP address of the first container is the same as the value of the third byte in the IP address of the second node, and the value of the third byte in the IP address of the first container is the same as the value of the fourth byte in the IP address of the second node.

6. The method according to claim 1 or 2, wherein the MAC address of the first container comprises at least one byte, the IP address of the first container comprises at least one byte, and the first association is that the value of a part of bytes in the MAC address of the first container is the same as the value of a part of bytes in the IP address of the first container.

7. The method of claim 6, wherein the MAC address of the first container comprises six bytes, the IP address of the first container comprises four bytes, the first association is that the value of the fourth byte in the MAC address of the first container is the same as the value of the second byte in the IP address of the first container, the value of the fifth byte in the MAC address of the first container is the same as the value of the third byte in the IP address of the first container, and the value of the sixth byte in the MAC address of the first container is the same as the value of the fourth byte in the IP address of the first container.

8. A node for message transmission, comprising:

the application management module is used for deducing a second address of a first container in a second node according to a first address and a first association relation of the first container, wherein the first association relation is the association relation between the first address and the second address of the container in the second node, the first association relation is a preset rule, the first address is an Internet Protocol (IP) address, the second address is a Media Access Control (MAC) address, or the first address is an MAC address, and the second address is an IP address;

The application management module is further configured to write the second address in the operating system, where the second address is a destination address of the second container transmission message in the node for message transmission.

9. The node of claim 8, wherein the application management module is further configured to receive request information from the second container, the request information being configured to request a second address corresponding to the first address.

10. The node according to claim 8 or 9, wherein the application management module is further configured to determine an IP address of the second node according to an IP address of the first container and a second association relationship, where the second node is configured to forward the packet to the first container, and the second association relationship is an association relationship between the IP address of the second node and an IP address of a container in the second node;

the application management module is further configured to write an IP address of the second node in the operating system.

11. The node of claim 10, wherein the IP address of the first container comprises at least one byte, the IP address of the second node comprises at least one byte, and the second association is that the value of a portion of the bytes in the IP address of the first container is the same as the value of a portion of the bytes in the IP address of the second node.

12. The node of claim 11, wherein the IP address of the first container comprises four bytes and the IP address of the second node comprises four bytes, and the second association is that the value of the second byte in the IP address of the first container is the same as the value of the third byte in the IP address of the second node, and the value of the third byte in the IP address of the first container is the same as the value of the fourth byte in the IP address of the second node.

13. The node according to claim 8 or 9, wherein the MAC address of the first container comprises at least one byte, the IP address of the first container comprises at least one byte, and the first association is that the value of a part of bytes in the MAC address of the first container is the same as the value of a part of bytes in the IP address of the first container.

14. The node of claim 13, wherein the MAC address of the first container comprises six bytes, the IP address of the first container comprises four bytes, the first association is that the value of the fourth byte in the MAC address of the first container is the same as the value of the second byte in the IP address of the first container, the value of the fifth byte in the MAC address of the first container is the same as the value of the third byte in the IP address of the first container, and the value of the sixth byte in the MAC address of the first container is the same as the value of the fourth byte in the IP address of the first container.