WO2021227873A1 - 用于报文传输的方法和节点 - Google Patents

用于报文传输的方法和节点 Download PDF

Info

Publication number
WO2021227873A1
WO2021227873A1 PCT/CN2021/090513 CN2021090513W WO2021227873A1 WO 2021227873 A1 WO2021227873 A1 WO 2021227873A1 CN 2021090513 W CN2021090513 W CN 2021090513W WO 2021227873 A1 WO2021227873 A1 WO 2021227873A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
container
node
byte
value
Prior art date
Application number
PCT/CN2021/090513
Other languages
English (en)
French (fr)
Inventor
王震宇
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2021227873A1 publication Critical patent/WO2021227873A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/54Organization of routing tables
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/58Caching of addresses or names
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00Indexing scheme associated with group H04L61/00
    • H04L2101/60Types of network addresses
    • H04L2101/618Details of network addresses
    • H04L2101/622Layer-2 addresses, e.g. medium access control [MAC] addresses

Definitions

  • This application relates to the field of communications, and more specifically, to a method and node for message transmission.
  • the telecommunications system With the growth of the network scale, the telecommunications system becomes more and more complex, which brings many challenges, including the development and launch of new services, system operation and maintenance, and resource utilization. In order to cope with these challenges, the telecommunication system utilizes the virtualization technology and cloud technology of the information technology (IT) industry.
  • IT information technology
  • Network functions virtualization (NFV) technology can be simply understood as the migration of the functions of each network element used in the telecommunications network from the current dedicated hardware platform to the general commercial shelf product server.
  • NFV technology Through NFV technology, each network element used in the telecommunications network is transformed into an independent application, which can be flexibly deployed on a unified infrastructure platform constructed by standard-based servers, storage, switches and other equipment.
  • Facility hardware equipment resource pooling and virtualization providing virtual resources for upper-layer applications, realizing application and hardware decoupling, so that each application can quickly increase virtual resources to achieve rapid expansion of system capacity, or to quickly reduce virtual resources to achieve
  • COTS common commercial off-the-shelf
  • VXLAN virtual expandable LAN
  • IP Internet Protocol
  • UDP User Datagram Protocol
  • MAC media access control
  • the synchronization of the IP address and MAC address between the containers in the VXLAN node in the VXLAN network requires the deployment of a VXLAN controller in the network. That is to say, in the traditional solution, the telecommunication system needs to introduce an additional controller, which makes the management more complicated.
  • the present application provides a method and node for message transmission, which can reduce the management complexity of the communication system.
  • a method for packet transmission includes: an application management module in a first node determines the The second address of the first container, the first association relationship is the association relationship between the first address and the second address of the container in the second node, the first address is an IP address, and the second address Is a MAC address, or the first address is a MAC address, and the second address is an IP address; the application management module writes the second address in the operating system, and the second address is the first The destination address of the message transmitted by the second container in the node.
  • 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 according to the first address and the first address of the first container in the second node
  • the first association relationship determines the second address of the first container, and then writes the second address of the first container into the operating system, which helps the second container in the first node to obtain the second address from the operating system.
  • the IP address and MAC address of the first container can thus be implemented to send a message to the first container.
  • an additional controller is introduced.
  • the embodiment of the present application reduces the management complexity of the system.
  • the method 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, so The request information is used to request a second address corresponding to the first address.
  • the second container may send request information to the application management module in the first node to request the second address.
  • One address corresponds to the second address, so that the message can be sent to the first container. That is to say, the second container only requests the second address corresponding to the first address from the application management module when there is a demand, which can avoid storing too many unnecessary addresses in the operating system, thereby saving the storage of the operating system space.
  • the method when the first address is an IP address, the method further includes: the application management module determines the The IP address of the second node, the second node is used to forward the message to the first container, and the second association relationship is between the IP address of the node and the IP address of the container in the second node The association relationship; 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 relationship 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 to say, the node in the embodiment of the present application can realize that it does not need to introduce an additional controller to learn the node to which the container that is about to send the message belongs, thereby reducing the management complexity of the system.
  • the IP address of the first container includes at least one byte
  • the IP address of the second node includes at least one byte
  • the second association relationship is the IP of the first container
  • the value of some bytes in the address is the same as the value of some bytes in the IP address of the second node.
  • the second association relationship may be that some 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, thereby further reducing the management complexity of the system.
  • 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 the IP of the first container
  • the value of the second byte in the address is the same as the value of the third byte in the IP address of the second node
  • the value of the third 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 first container.
  • the value of the fourth byte in the IP address of the second node is the same.
  • the application management module can find the IP address of the second container of the node according to the association relationship and the IP address of the first container, that is, the realization does not need to introduce an additional controller, which reduces the management complexity of the system.
  • 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 the MAC address of the first container.
  • the value of some bytes in the address is the same as the value of some bytes in the IP address of the first container.
  • the first association relationship may be that some 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, thereby further reducing the management complexity of the system.
  • 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 the MAC address of the first container.
  • the value of the fourth byte in the address is the same as the value of the second byte in the IP address of the first container, and the value of the fifth byte in the MAC address of the first container.
  • the value of the third byte in the IP address of the first container is the same
  • the value of the sixth byte in the MAC address of the first container is the same as that of the IP address of the first container.
  • the value of the fourth byte of is the same.
  • the method when the first address is a MAC address, the method further includes: determining the IP address of the second node according to the MAC address of the first container and the third association relationship, and combining the second node
  • the third association relationship is the association relationship between the IP address of the node and the MAC address of the first container
  • the second node is used to forward the message to the first container.
  • the application management module can find the IP address of the second node of the node according to the third association relationship 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 to say, the node in the embodiment of the present application can realize that it does not need to introduce an additional controller to learn the node to which the container that is about to send the message belongs, thereby reducing the management complexity of the system.
  • the MAC address of the first container includes at least one byte
  • the IP address of the second node includes at least one byte
  • the third association relationship is part of the MAC address of the first container
  • the value of the byte is the same as the value of some bytes in the IP address of the second node.
  • the third association relationship may be that some 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, thereby further reducing the management complexity of the system.
  • the MAC address of the first container includes six bytes
  • the IP address of the second node includes four bytes
  • the third association relationship is the MAC address of the first container
  • the value of the fifth byte in the IP address of the second node is the same as the value of the third byte in the IP address of the second node
  • the value of the sixth byte in the MAC address of the first container is the same as the value of the The value of the fourth byte in the IP address of the second node is the same.
  • a method for transmitting a message includes: a second container in a first node sends request information to an application management module, and the request information is used to request the first container in the second node.
  • the first address of the container corresponds to the second address of the first container, 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 Is the IP address;
  • the second container detects the second address of the first container corresponding to the first address of the first container from the operating system; the second container is based on the first address of the first container And the second address of the first container, sending a message to the first container.
  • the second container may send request information to the application management module in the first node to request the second address.
  • One address corresponds to the second address, so that the message can be sent to the first container. That is to say, the second container only requests the second address corresponding to the first address from the application management module when there is a demand, which can avoid storing too many unnecessary addresses in the operating system, thereby saving the storage of the operating system space.
  • an additional controller is introduced to obtain the address of the container in a node other than the current node. The embodiment of the present application reduces the management complexity of the system.
  • the method when the first address is a MAC address and the second address is an IP address, the method further includes: the first container detects the The IP address of the second node corresponding to the MAC address of the first container; wherein, the second container sends to the first container according to the first address of the first container and the second address of the first container
  • the message 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 configured to forward the message to the first container.
  • the second container needs to find the second node that includes the first container, and then the second node forwards the message to The first container. That is to say, through this correspondence, message transmission across containers between nodes can be realized. Compared with the traditional solution, an additional controller is introduced, which reduces the management complexity of the system.
  • a node for packet transmission is provided, and the node is configured to execute the above-mentioned first aspect or the method in any one of the possible implementations of the above-mentioned first aspect.
  • a node for packet transmission is provided, and the node is configured to execute the above-mentioned second aspect or the method in any one of the possible implementations of the above-mentioned second aspect.
  • a node for message transmission including a processor and a memory, where the memory is used to store program instructions, and the processor is used to call the program instructions to execute the above-mentioned first aspect or the above-mentioned first aspect Any one of the possible implementation methods.
  • a node for message transmission including a processor and a memory, where the memory is used to store program instructions, and the processor is used to call the program instructions to execute the above-mentioned second aspect or the above-mentioned second aspect Any one of the possible implementation methods.
  • a computer-readable storage medium stores program code for device execution.
  • the program code includes the program code for executing the above-mentioned first aspect or any one of the above-mentioned first aspects. Methods in possible implementations.
  • a computer-readable storage medium stores program code for device execution.
  • the program code includes the program code for executing the above-mentioned first aspect or any one of the above-mentioned first aspects. Methods in possible implementations.
  • a chip in a ninth aspect, includes a processor and a data interface.
  • the processor reads instructions stored in a memory through the data interface to execute the first aspect or any one of the first aspects.
  • One of the possible implementation methods One of the possible implementation methods.
  • a chip in a tenth aspect, includes a processor and a data interface.
  • the processor reads instructions stored in a memory through the data interface to execute the first aspect or any one of the first aspects.
  • One of the possible implementation methods One of the possible implementation methods.
  • a computer program product containing instructions which when running on a computer, causes the computer to execute the method in the first aspect described above, or any possible implementation manner thereof.
  • a computer program product containing instructions which when running on a computer, causes the computer to execute the method in the second aspect described above, or any possible implementation manner thereof.
  • a communication system which includes the node described in the third aspect and the node described in the fourth aspect.
  • the node described in the third aspect and the node described in the fourth aspect may be different nodes.
  • 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.
  • the node described in the third aspect and the node described in the fourth aspect may be the same node, for example, the application management module and the second container in the same node perform interactive communication.
  • 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 be based on the first container in the second node.
  • the first address and the first association relationship determine the second address of the first container, and then write the second address of the first container into the operating system, which will help the second container in the first node from
  • the operating system obtains the IP address and MAC address of the first container, so that the message can be sent to the first container.
  • an additional controller is introduced. The embodiment of the present application reduces the management complexity of the system.
  • Fig. 1 is a schematic block diagram of a communication system according to an embodiment of the present application.
  • Figure 2 is a schematic diagram of the structure of a VXLAN message
  • FIG. 3 is a schematic flowchart of a method for packet transmission according to an embodiment of the present application.
  • Fig. 4 is a schematic block diagram of a node for packet transmission according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a node for message transmission according to an embodiment of the present application.
  • Fig. 6 is a schematic block diagram of a node for packet transmission according to another embodiment of the present application.
  • Fig. 7 is a schematic structural diagram of a node for packet transmission according to another embodiment of the present application.
  • Fig. 1 shows a communication system according to an embodiment of the present application.
  • the communication system may include at least two nodes, for example, node 1 and node 2 shown in FIG. 1.
  • node 1 may include an application management module, a container management module, and at least one container (for example, container 1, container 2, and container 3).
  • the application management module is used to create interfaces and assign IP addresses and MAC addresses of services
  • the container management module is used to create containers.
  • the application management module may be a VXLAN application management module.
  • the corresponding interface may be a VXLAN interface.
  • FIG. 2 shows the structure of the VXLAN message.
  • VXLAN virtual expandable LAN
  • each VXLAN node needs to know the information of all other VXLAN nodes, that is, the IP addresses and media access control (media access control) of the containers in all VXLAN nodes. access control, MAC) address.
  • the synchronization of the IP address and MAC address between the containers in the VXLAN node in the VXLAN network requires the deployment of a VXLAN controller in the network. That is to say, in the traditional solution, the telecommunication system needs to introduce an additional controller, which makes the management more complicated.
  • Fig. 3 shows a schematic flowchart of a method for packet transmission according to an embodiment of the present application.
  • 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 the 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.
  • the request information can be sent to the application management module in the first node to request the second address corresponding to the first address.
  • the first address is an IP address
  • the second address may be a MAC address
  • the first address is a MAC address
  • the second address may be an IP address.
  • the second container needs to obtain the IP address and MAC address of the first container to send a message to the first container.
  • the first node may also include other containers, which is not limited in this application.
  • the second node may also include other containers, which is not limited in this application.
  • the application management module in the first node determines the second address of the first container according to the first address of the first container and the first association relationship, and the first association relationship is the first address of the container in the second node.
  • the association relationship between the address and the second address is the first address of the container in the second node.
  • the application management module may store the first association relationship between the first address and the second address of the container in the second node.
  • the application management module may obtain the second address according to the first address and the first association relationship, for example, obtain it directly, or obtain it indirectly.
  • the first association relationship may include that the first address of a certain container (for example, the first container) in the second node has an association relationship with the second address of the first container, and may also include the second node
  • the first address of each of the one or more containers in the container has an associated relationship with the second address.
  • the first association relationship includes the corresponding relationship between the IP address of the first container and the MAC address of the first container.
  • the management module can derive the second address according to the first address and the rule.
  • the first association relationship is part of the word in the MAC address of the first container.
  • the value of the section is the same as the value of some bytes in the IP address of the first container.
  • the multiple bytes may be continuous or discontinuous, which is not limited in this application.
  • the value of each byte in the partial bytes of the MAC address of the first container can be the same as the value of a byte in the multiple bytes of the IP address of the first container, or it can be It is that the overall value of some bytes in the MAC address of the first container is the same as the overall value of multiple bytes of the IP address of the first device.
  • 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.
  • IPv4 Internet Protocol Version 4, IPv4
  • IPv6 Internet Protocol Version 6
  • the first association relationship may be temporarily generated, or may be known to be stored in the application management module, which is not limited in this application.
  • the first association relationship is the fourth of the MAC addresses of the first container
  • the value of the byte 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 IP address of the first container
  • the value of the third byte in is the same
  • 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.
  • the structure of the MAC address may be "0a:0a:0a: 4th byte of service IP: 5th byte of service IP: 6th byte of service IP".
  • the second byte of the service IP address and the fourth byte of the MAC address may have different hexadecimals.
  • the MAC address corresponding to the IP address "10.101.10.100” is "0a:0a:0a:65:0a:64" (the numbers on the underline have a corresponding relationship, and the numbers in the slanted font also have a corresponding relationship). That is, the bytes of the IP address are expressed in binary, and the bytes of the MAC address are expressed in hexadecimal.
  • the bytes other than the associated bytes can be preset, for example, the first byte in the IP address is set to "10", the first three bytes of the MAC address It is set to "0a:0a:0a”, or other preset values, which are not limited in this application.
  • the application management module may also determine the IP address of the second node according to the IP address of the first container and the second association relationship, and combine the IP address of the second node The IP address is written into the operating system.
  • the second node is used to forward a message to the first container
  • 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 second container when the first address is an IP address and the second address is a MAC address, if the first node cannot directly find the first container (that is, there is no routing information to the first container), the second container needs to be The second node that includes the first container is found, and the second node forwards the message to the first container.
  • the second container sends layer3miss (L3MISS) information to the application management module, and the application management module detects the L3MISS information and learns that the IP address lacks routing information.
  • L3MISS layer3miss
  • the second association relationship may include the correspondence between a certain container (for example, the first container) in the second node and the IP address of the second node, or may include multiple containers in the second node.
  • the association relationship between each container in and the IP address of the node is not limited in this application.
  • the IP address of the first container includes at least one byte
  • the IP address of the second node includes at least one byte
  • the second association relationship is a partial byte of the IP address of the first container.
  • the value is the same as the value of some bytes in the IP address of the second node.
  • 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 the second word in the IP address of the first container
  • the value of the section is the same as the value of the third byte in the IP address of the second node
  • the value of the third byte in the IP address of the first container is the same as that of the second node.
  • the value of the fourth byte in the address is the same.
  • the IP address of the first container is "10.101.10.100”
  • the IP address of the second node is "172.16.101.10”.
  • the first two bytes of the IP address of the node may be preset.
  • the first two bytes of the IP address of the node are "172.16".
  • the last byte in the IP address of the container may be a unique serial number in the node.
  • the application management module may also determine the IP address of the second node according to the MAC address of the first container and the third association relationship, and compare the IP address of the second node The IP address is written into the operating system, and the third association relationship is the association relationship between the IP address of the node and the MAC address of the first container.
  • the second node is used to forward the message to the first container.
  • the second container needs to find the second node that includes the first container, and then the second node forwards the message to the first container.
  • the second container sends layer 2 miss (L2MISS) information to the application management module, and the application management module detects the L2MISS information and learns that the MAC address lacks routing information.
  • L2MISS layer 2 miss
  • the MAC address of the first container includes at least one byte
  • the IP address of the second node includes at least one byte
  • the third association relationship is the selection of some bytes in the MAC address of the first container.
  • the value is the same as the value of some bytes in the IP address of the second node.
  • the MAC address of the first container includes six bytes
  • the IP address of the second node includes four bytes
  • the third association relationship is the fifth word in the MAC address of the first container.
  • the value of the section is the same as the value of the third byte in the IP address of the second node
  • the value of the sixth byte in the MAC address of the first container is the same as the value of the second node’s IP address.
  • the value of the fourth byte in the address is the same.
  • the corresponding IP address of the second node is "172.16.102.30".
  • the first two bytes of the node's IP address may be preset, for example, the first two bytes of the node's IP address are "172.16".
  • the application management module writes the second address in the operating system, where the second address is the destination address of the packet transmitted by the second container in the first node.
  • the application management module may write the second address into the system cache of the operating system, for example, the second address is written into a forwarding database (FDB) table.
  • FDB forwarding database
  • the application management module can be started when the operating system is started, and after starting, it can be checked whether the interface of the first node is correctly configured. If it is not configured correctly, configure the interface.
  • the interface is a VXLAN interface.
  • the operating system may be an OS.
  • step 301 may not be executed in this application.
  • the second container detects the second address of the first container corresponding to the first address of the first container from the operating system.
  • 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 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 according to the first address and the first address of the first container in the second node
  • the first association relationship determines the second address of the first container, and then writes the second address of the first container into the operating system, which helps the second container to obtain the IP address of the first container from the operating system And the MAC address, so as to be able to send a message to the first container.
  • an additional controller is introduced.
  • the embodiment of the present application reduces the management complexity of the system.
  • FIG. 4 shows a schematic block diagram of a node 400 for packet transmission according to an embodiment of the present application.
  • the node 400 may implement the method of the embodiment shown in FIG. 3.
  • the node 400 may include the application management module 410 and the operating system 420 shown in FIG. 3.
  • the node 400 may also include the second container shown in FIG. 3.
  • the node 400 may be a physical machine or a virtual machine.
  • the application management module 410 is configured to determine the second address of the first container according to the first address of the first container in the second node and the first association relationship, where the first association relationship is the second node The relationship between the first address and the second address of the middle container, 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 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 the destination address of the second container in the first node to transmit packets
  • 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.
  • the application management module 410 is further configured to determine the IP address of the second node according to the IP address of the first container and the second association relationship, and the second node is used to send the information to the first container.
  • a container forwards the message, and the second association relationship is the association relationship between the IP address of the node and the IP address of the container in the second node; the application management module is also configured to log in to the operating system Write the IP address of the second node in.
  • the IP address of the first container includes at least one byte
  • the IP address of the second node includes at least one byte
  • the second association relationship is part of the IP address of the first container
  • the value of the byte is the same as the value of some bytes in the IP address of the second node.
  • 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 the first container's IP address.
  • the value of the two bytes is the same as the value of the third byte in the IP address of the second node
  • the value of the third byte in the IP address of the first container is the same as that of the second node.
  • the value of the fourth byte in the IP address is the same.
  • 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 a part of the MAC address of the first container
  • the value of the byte is the same as the value of some bytes in the IP address of the first container.
  • 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 the first of the MAC addresses of the first container.
  • the value of the four bytes 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 that of the first container.
  • the value of the third byte in the IP address of a container is the same
  • the value of the sixth byte in the MAC address of the first container is the same as the value of the fourth in the IP address of the first container
  • the value of the byte is the same.
  • Fig. 5 shows a node 500 for packet transmission provided by an embodiment of the present application.
  • the node can adopt the hardware architecture shown in Figure 5.
  • the node may include a processor 510 and a transceiver 520.
  • the node may also include a memory 530.
  • the processor 510, the transceiver 520, and the memory 530 communicate with each other through an internal connection path.
  • a part of the related functions implemented by the application management module 410 in FIG. 4 may be realized by the processor 510, and another part of the related functions may be realized by the processor 510 controlling the transceiver 520.
  • the processor 510 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), a dedicated processor, or one or more It is an integrated circuit that implements the technical solutions of the embodiments of the present application.
  • a processor may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processor can be used to control communication devices (such as base stations, terminals, or chips), execute software programs, and process data in the software programs.
  • the processor 510 may include one or more processors, for example, include one or more central processing units (central processing unit, CPU).
  • CPU central processing unit
  • the CPU may be a single processor.
  • the core CPU can also be a multi-core CPU.
  • the transceiver 520 is used to send and receive data and/or signals, and to receive data and/or signals.
  • the transceiver may include a transmitter and a receiver, the transmitter is used to send data and/or signals, and the receiver is used to receive data and/or signals.
  • the memory 530 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable memory (erasable read only memory, EPROM), and read-only memory.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable read only memory
  • EPROM erasable read only memory
  • a compact disc read-only memory, CD-ROM.
  • the memory 530 is used to store related instructions and data.
  • the memory 530 is used to store program codes and data of the network device, and may be a separate device or integrated in the processor 510.
  • the processor 510 is configured to control the transceiver to perform information transmission with the second container.
  • the processor 510 is configured to control the transceiver to perform information transmission with the second container.
  • the node 500 may further include an output device and an input device.
  • the output device communicates with the processor 510 and can display information in a variety of ways.
  • the output device can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc.
  • the input device communicates with the processor 510 and can receive user input in a variety of ways.
  • the input device can be a mouse, a keyboard, a touch screen device, or a sensor device.
  • FIG. 5 only shows a simplified design of the communication node.
  • the node can also contain other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, etc., and all nodes that can implement this application are protected by this application. Within range.
  • the node 500 may also be a chip or a chip system.
  • the application management module 410 in the node 500 may include a data transmission interface, an interface circuit, a data transmission circuit or pins, and a processor, a processing circuit or a logic circuit, and the storage unit may be a memory Or storage circuit.
  • FIG. 6 shows a schematic block diagram of a node 600 for packet transmission according to an embodiment of the present application.
  • the node 600 can implement the method shown in FIG. 3.
  • the node may include the second container in the embodiment shown in FIG. 3.
  • the node 600 may also include the application management module and operating system described in FIG. 3.
  • the node shown in FIG. 4 and the node shown in FIG. 6 are the same node. That is, the content application management module of the same node interacts with the second container.
  • the node shown in FIG. 4 and the node shown in FIG. 6 are different nodes.
  • the second container of the first node may obtain the first container of the first container in the second node from the operating system in the third node. Address or second address.
  • the node 600 may be a physical machine or a virtual machine.
  • the node 600 may include units for performing various operations in the foregoing method embodiments.
  • each module in the node 600 is to implement the corresponding process of the second container in any of the foregoing methods.
  • the node 600 includes a transceiver module 610 and a processing module 620.
  • the transceiver module 610 is configured to send request information to the application management module.
  • the request information is used to request the second address of the first container corresponding to the first address of the first container in the second node.
  • the address is an IP address
  • the second address is a MAC address
  • the first address is a MAC address
  • the second address is an IP address
  • the processing module 620 is configured to detect the second address of the first container corresponding to the first address of the first container from the operating system;
  • 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.
  • the processing module 620 is further configured to detect from the operating system the second container corresponding to the MAC address of the first container.
  • the IP address of the node; the transceiver module 610 is specifically configured to: send the message to a second node corresponding to the IP address of the second node, and the second node is configured to forward the message to the first container Message.
  • Fig. 7 shows a node 700 for packet transmission provided by an embodiment of the present application.
  • the node can adopt the hardware architecture shown in Figure 7.
  • the node may include a processor 710 and a transceiver 720.
  • the node may also include a memory 730.
  • the processor 710, the transceiver 720, and the memory 730 communicate with each other through an internal connection path.
  • Part of the relevant functions implemented by the processing module 620 in FIG. 6 may be implemented by the processor 710, and part of the relevant functions implemented by the transceiver module 610 may be implemented by the processor 710 controlling the transceiver 720.
  • the processor 710 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), a dedicated processor, or one or more It is an integrated circuit that implements the technical solutions of the embodiments of the present application.
  • a processor may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processor can be used to control communication nodes (such as base stations, terminals, or chips), execute software programs, and process data in the software programs.
  • the processor 710 may include one or more processors, for example, include one or more central processing units (central processing unit, CPU).
  • CPU central processing unit
  • the CPU may be a single processor.
  • the core CPU can also be a multi-core CPU.
  • the transceiver 720 is used to send and receive data and/or signals, and to receive data and/or signals.
  • the transceiver may include a transmitter and a receiver, the transmitter is used to send data and/or signals, and the receiver is used to receive data and/or signals.
  • the memory 730 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable memory (erasable read only memory, EPROM), and read-only memory.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable read only memory
  • read-only memory erasable read only memory
  • CD-ROM compact disc
  • the memory 730 is used to store program codes and data of the network device, and may be a separate device or integrated in the processor 710.
  • the processor 710 is configured to control the transceiver and the application management module to perform information transmission.
  • the processor 710 is configured to control the transceiver and the application management module to perform information transmission.
  • the node 700 may further include an output device and an input device.
  • the output device communicates with the processor 710 and can display information in a variety of ways.
  • the output device can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc.
  • the input device communicates with the processor 710 and can receive user input in a variety of ways.
  • the input device can be a mouse, a keyboard, a touch screen device, or a sensor device.
  • FIG. 7 only shows a simplified design of the communication node.
  • the node can also contain other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, etc., and all network devices that can implement this application are protected by this application. Within range.
  • the node 700 may also be a chip or a chip system.
  • 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, a storage unit It can be a memory or a storage circuit.
  • the chip may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip. , SoC), it can also be a central processor unit (CPU), a network processor (NP), a digital signal processing circuit (digital signal processor, DSP), or a micro
  • the controller microcontroller unit, MCU may also be a programmable logic device (PLD) or other integrated chips.
  • the embodiment of the present application also shows a system, which includes the node 400 shown in FIG. 4 and the node 600 shown in FIG. 6.
  • a computer-readable storage medium is provided, and an instruction is stored thereon, and the method in the foregoing method embodiment is executed when the instruction is executed.
  • a computer program product containing instructions is provided, and when the instructions are executed, the method in the foregoing method embodiment is executed.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • 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 a website, computer, server, or data center.
  • 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 or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk, SSD)) etc.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • the steps of the foregoing method embodiments may be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (field programmable gate array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • Programming logic devices discrete gates or transistor logic devices, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically accessible memory. Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous link dynamic random access memory synchronous link DRAM, SLDRAM
  • direct memory bus random access memory direct rambus RAM, DR RAM
  • At least one refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • component used in this specification are used to denote computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution.
  • the component may be, but is not limited to, a process, a processor, an object, an executable file, an execution thread, a program, and/or a computer running on a processor.
  • the application running on the computing device and the computing device can be components.
  • One or more components may reside in processes and/or threads of execution, and components may be located on one computer and/or distributed among two or more computers.
  • these components can be executed from various computer readable media having various data structures stored thereon.
  • the component can be based on, for example, a signal having one or more data packets (e.g. data from two components interacting with another component in a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through a signal) Communicate through local and/or remote processes.
  • a signal having one or more data packets (e.g. data from two components interacting with another component in a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through a signal) Communicate through local and/or remote processes.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Small-Scale Networks (AREA)

Abstract

本申请提供了一种用于报文传输的方法和装置。该方法包括:第一节点可以存储第二节点中容器的第一地址和第二地址之间的第一关联关系,这样第一节点中的应用管理模块可以根据第二节点中的第一容器的第一地址和该第一关联关系确定出该第一容器的第二地址,进而将第一容器的第二地址写入操作系统中,这样有助于该第一节点中的第二容器从操作系统中获得该第一容器的IP地址和MAC地址,从而能够实现向第一容器发送报文,相对于传统方案引入额外的控制器,本申请实施例降低了系统的管理复杂度。

Description

用于报文传输的方法和节点
本申请要求于2020年5月9日提交中国国家知识产权局、申请号为202010387411.6、申请名称为“用于报文传输的方法和节点”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域,更具体地,涉及一种用于报文传输的方法和节点。
背景技术
随着网络规模的增长,电信系统越来越复杂,从而带来了诸多的挑战,包括新增业务的开发上线、系统的运维和资源利用率等。为了应对这些挑战,电信系统利用了信息技术(information technology,IT)业界的虚拟化技术及云技术。
网络功能虚拟化(network functions virtualization,NFV)技术可以简单地理解为将电信网络中使用的各个网元的功能从目前的专用硬件平台迁移至通用的商用货架产品服务器上。通过NFV技术将电信网络中使用的各个网元转变称为独立的应用,可以灵活部署在基于标准的服务器、存储以及交换机等其他设备构建的统一基础设施平台上,并通过虚拟化技术,对基础设施硬件设备资源池化及虚拟化,对上层应用提供虚拟资源,实现应用、硬件解耦,使得每一个应用能够快速增加虚拟资源以实现快速扩展系统容量的目的,或者能够快速减少虚拟资源以实现收缩系统容量的目的,大大提升网络的弹性。采用通用的商业现货(COTS)服务器组成共享的资源池,新开发的业务,不需要单独部署硬件设备,大大缩短新业务上线时间。
电信系统上云最为彻底的方式便是把二层通讯改造为三层通讯。传统方案,设备之间通过将二层报文封装在标准的互联网协议(internet protocol,IP)/用户数据报协议(user datagram protocol,UDP)报文中,以实现私有二层报文的交互。例如,构建一个二层互通的虚拟可扩展局域网(virtual expandable LAN,VXLAN)网络,需要每个VXLAN的节点知道其余所有VXLAN节点的信息,即所有VXLAN节点中容器的IP地址和媒体访问控制(media access control,MAC)地址。而VXLAN网络中VXLAN节点中的容器之间的IP地址和MAC地址的同步,需要网络中部署VXLAN控制器。也就是说,传统方案中,电信系统需要引入额外的控制器,使得管理复杂度较高。
发明内容
本申请提供一种用于报文传输的方法和节点,能够减少通信系统的管理复杂度。
第一方面,提供了一种用于报文传输的方法,该方法包括:第一节点中的应用管理模块根据第二节点中的第一容器的第一地址和第一关联关系,确定所述第一容器的第二地址,所述第一关联关系为所述第二节点中容器的第一地址和第二地址之间的关联关系,所述第一地址为IP地址,所述第二地址为MAC地址,或者所述第一地址为MAC地址,所述第二地址为IP地址;所述应用管理模块在操作系统中写入所述第二地址,所述第二地址为所述第一节点中的第二容器传输报文的目的地址。
第一节点可以存储第二节点中容器的第一地址和第二地址之间的第一关联关系,这样第一节点中的应用管理模块可以根据第二节点中的第一容器的第一地址和该第一关联关系确定出该第一容器的第二地址,进而将第一容器的第二地址写入操作系统中,这样有助于该第一节点中的第二容器从操作系统中获得该第一容器的IP地址和MAC地址,从而能够实现向第一容器发送报文,相对于传统方案引入额外的控制器,本申请实施例降低了系统的管理复杂度。
在一些可能的实现方式中,所述应用管理模块根据所述第一地址确定所述第二地址之前,所述方法还包括:所述应用管理模块接收来自所述第二容器的请求信息,所述请求信息用于请求所述第一地址对应的第二地址。
在该第一节点的操作系统中没有存储该第一容器的第一地址对应的第二地址的情况下,第二容器可以向该第一节点中的应用管理模块发送请求信息,以请求该第一地址对应的第二地址,从而能够实现向第一容器发送报文。也就是说,第二容器在存在需求的情况下才向应用管理模块请求第一地址对应的第二地址,这样可以避免在操作系统中存储太多不必要的地址,从而节省了操作系统的存储空间。
在一些可能的实现方式中,在所述第一地址为IP地址的情况下,所述方法还包括:所述应用管理模块根据所述第一容器的IP地址和第二关联关系,确定所述第二节点的IP地址,所述第二节点用于向所述第一容器转发所述报文,所述第二关联关系为节点的IP地址与所述第二节点中容器的IP地址之间的关联关系;所述应用管理模块在所述操作系统中写入所述第二节点的IP地址。
应用管理模块可以根据关联关系和容器的IP地址找到节点的IP地址,并通过节点的IP地址向节点内的容器转发报文。也就是说,本申请实施例中节点可以实现不需要引入额外的控制器获知即将发送报文的容器所属的节点,从而降低了系统的管理复杂度。
在一些可能的实现方式中,所述第一容器的IP地址包括至少一个字节,所述第二节点的IP地址包括至少一个字节,所述第二关联关系为所述第一容器的IP地址中的部分字节的取值与所述第二节点的IP地址中的部分字节的取值相同。
该第二关联关系可以是部分字节取值相同,即通过简单的方式实现容器的IP地址和节点的IP地址的关联,从而更进一步降低系统的管理复杂度。
在一些可能的实现方式中,所述第一容器的IP地址包括四个字节,所述第二节点的IP地址包括四个字节,所述第二关联关系为所述第一容器的IP地址中的第二字节的取值与所述第二节点的IP地址中的第三个字节的取值相同,所述第一容器的IP地址中的第三字节的取值与所述第二节点的IP地址中的第四个字节的取值相同。
应用管理模块可以根据关联关系和第一容器的IP地址找到节点第二容器的IP地址,即实现不需要引入额外的控制器,降低了系统的管理复杂度。
在一些可能的实现方式中,所述第一容器的MAC地址包括至少一个字节,所述第一容器的IP地址包括至少一个字节,所述第一关联关系为所述第一容器的MAC地址中的部分字节的取值与所述第一容器的IP地址中的部分字节的取值相同。
该第一关联关系可以是部分字节取值相同,即通过简单的方式实现容器的IP地址和节点的IP地址的关联,从而更进一步降低系统的管理复杂度。
在一些可能的实现方式中,所述第一容器的MAC地址包括六个字节,所述第一容器的IP地址包括四个字节,所述第一关联关系为所述第一容器的MAC地址中的第四个字节的取值与 所述第一容器的IP地址中的第二个字节的取值相同,所述第一容器的MAC地址中的第五个字节的取值与所述第一容器的IP地址中的第三个字节的取值相同,以及所述第一容器的MAC地址中的第六个字节的取值与所述第一容器的IP地址中的第四个字节的取值相同。
在一些可能的实现方式中,在第一地址为MAC地址的情况下,该方法还包括:根据该第一容器的MAC地址和第三关联关系确定该第二节点的IP地址,并将该第二节点的IP地址写入操作系统中,该第三关联关系为节点的IP地址与第一容器的MAC地址的关联关系,该第二节点用于向该第一容器转发报文。
应用管理模块可以根据第三关联关系和第一容器的MAC地址找到节点第二节点的IP地址,并通过节点的IP地址向节点内的容器转发报文。也就是说,本申请实施例中节点可以实现不需要引入额外的控制器获知即将发送报文的容器所属的节点,从而降低了系统的管理复杂度。
在一些可能的实现方式中,该第一容器的MAC地址包括至少一个字节,该第二节点的IP地址包括至少一个字节,该第三关联关系为该第一容器的MAC地址中的部分字节的取值与该第二节点的IP地址中的部分字节的取值相同。
该第三关联关系可以是部分字节取值相同,即通过简单的方式实现容器的IP地址和节点的IP地址的关联,从而更进一步降低系统的管理复杂度。
在一些可能的实现方式中,所述第一容器的MAC地址包括六个字节,所述第二节点的IP地址包括四个字节,该第三关联关系为所述第一容器的MAC地址中的第五字节的取值与所述第二节点的IP地址中的第三个字节的取值相同,所述第一容器的MAC地址中的第六字节的取值与所述第二节点的IP地址中的第四个字节的取值相同。
第二方面,提供了一种用于传输报文的方法,该方法包括:第一节点中的第二容器向应用管理模块发送请求信息,所述请求信息用于请求第二节点中的第一容器的第一地址对应的所述第一容器的第二地址,所述第一地址为IP地址,所述第二地址为MAC地址,或者所述第一地址为MAC地址,所述第二地址为IP地址;所述第二容器从操作系统中检测所述第一容器的第一地址对应的所述第一容器的第二地址;所述第二容器根据所述第一容器的第一地址和所述第一容器的第二地址,向所述第一容器发送报文。
在该第一节点的操作系统中没有存储该第一容器的第一地址对应的第二地址的情况下,第二容器可以向该第一节点中的应用管理模块发送请求信息,以请求该第一地址对应的第二地址,从而能够实现向第一容器发送报文。也就是说,第二容器在存在需求的情况下才向应用管理模块请求第一地址对应的第二地址,这样可以避免在操作系统中存储太多不必要的地址,从而节省了操作系统的存储空间。此外,相对于传统方案引入额外的控制器来获得本节点之外的节点中的容器的地址,本申请实施例降低了系统的管理复杂度。
在一些可能的实现方式中,在所述第一地址为MAC地址,所述第二地址为IP地址的情况下,所述方法还包括:所述第一容器从所述操作系统中检测所述第一容器的MAC地址对应的第二节点的IP地址;其中,所述第二容器根据所述第一容器的第一地址和所述第一容器的第二地址,向所述第一容器发送报文包括:所述第二容器向所述第二节点的IP地址对应的第二节点发送所述报文,所述第二节点用于向所述第一容器转发所述报文。
若第一节点无法直接找到第一容器(即没有到该第一容器的路由信息),则第二容器需要先找到包括该第一容器的第二节点,再由第二节点将报文转发给第一容器。也就是说,通过该对应关系可以实现跨节点之间容器的报文传输,相对于传统方案引入额外的控制器,降低 了系统的管理复杂度。
第三方面,提供一种用于报文传输的节点,该节点用于执行上述第一方面,或上述第一方面中的任意一种可能的实现方式中的方法。
第四方面,提供一种用于报文传输的节点,该节点用于执行上述第二方面,或上述第二方面中的任意一种可能的实现方式中的方法。
第五方面,提供了一种用于报文传输的节点,包括处理器和存储器,该存储器用于存储程序指令,该处理器用于调用该程序指令来执行上述第一方面,或上述第一方面中的任意一种可能的实现方式中的方法。
第六方面,提供了一种用于报文传输的节点,包括处理器和存储器,该存储器用于存储程序指令,该处理器用于调用该程序指令来执行上述第二方面,或上述第二方面中的任意一种可能的实现方式中的方法。
第七方面,提供了一种计算机可读存储介质,该计算机可读介质存储用于设备执行的程序代码,该程序代码包括用于执行上述第一方面,或上述第一方面中的任意一种可能的实现方式中的方法。
第八方面,提供了一种计算机可读存储介质,该计算机可读介质存储用于设备执行的程序代码,该程序代码包括用于执行上述第一方面,或上述第一方面中的任意一种可能的实现方式中的方法。
第九方面,提供了一种芯片,该芯片包括处理器与数据接口,该处理器通过该数据接口读取存储器上存储的指令,以执行上述第一方面,或上述第一方面中的任意一种可能的实现方式中的方法。
第十方面,提供了一种芯片,该芯片包括处理器与数据接口,该处理器通过该数据接口读取存储器上存储的指令,以执行上述第一方面,或上述第一方面中的任意一种可能的实现方式中的方法。
第十一方面,提供了一种包含指令的计算机程序产品,其在计算机上运行时,使得计算机执行上述第一方面,或其任意可能的实现方式中的方法。
第十二方面,提供了一种包含指令的计算机程序产品,其在计算机上运行时,使得计算机执行上述第二方面,或其任意可能的实现方式中的方法。
第十三方面,提供了一种通信系统,该通信系统包括上述第三方面所述的节点和上述第四方面所述的节点。其中,上述第三方面所述的节点和上述第四方面所述的节点可以是不同的节点。例如,第一节点的容器可以从第三节点中的操作系统中获取第二节点中的容器的第一地址或第二地址。或者上述第三方面所述的节点和上述第四方面所述的节点可以是同一个节点,例如,在同一个节点中的应用管理模块和第二容器进行交互通信。
基于上述技术方案,第一节点可以存储第二节点中容器的第一地址和第二地址之间的第一关联关系,这样第一节点中的应用管理模块可以根据第二节点中的第一容器的第一地址和该第一关联关系确定出该第一容器的第二地址,进而将第一容器的第二地址写入操作系统中,这样有助于该第一节点中的第二容器从操作系统中获得该第一容器的IP地址和MAC地址,从而能够实现向第一容器发送报文,相对于传统方案引入额外的控制器,本申请实施例降低了系统的管理复杂度。
附图说明
图1是本申请实施例的通信系统的示意性框图;
图2是VXLAN报文的结构的示意图;
图3是本申请实施例的用于报文传输的方法的示意性流程图;
图4是本申请一个实施例的用于报文传输的节点的示意性框图;
图5是本申请一个实施例的用于报文传输的节点的示意性结构图;
图6是本申请另一个实施例的用于报文传输的节点的示意性框图;
图7是本申请另一个实施例的用于报文传输的节点的示意性结构图。
具体实施方式
下面将结合附图,对本申请中的技术方案进行描述。
图1示出了本申请实施例的通信系统。该通信系统中可以包括至少两个节点,例如,图1所示的节点1和节点2。以节点1为例进行说明,节点1中可以包括应用管理模块和容器管理模块以及至少一个容器(例如,容器1、容器2和容器3)。其中,应用管理模块用于创建接口以及分配业务的IP地址和MAC地址,容器管理模块用于创建容器。
可以理解的是,该应用管理模块可以是VXLAN应用管理模块。在该应用管理模块为VXLAN应用管理模块的情况下,对应的接口可以是VXLAN接口。
传统方案中,设备之间通过将二层报文封装在标准的IP/UDP报文中,以实现私有二层报文的交互。如图2示出了VXLAN报文的结构。例如,构建一个二层互通的虚拟可扩展局域网(virtual expandable LAN,VXLAN)网络,需要每个VXLAN的节点知道其余所有VXLAN节点的信息,即所有VXLAN节点中容器的IP地址和媒体访问控制(media access control,MAC)地址。而VXLAN网络中VXLAN节点中的容器之间的IP地址和MAC地址的同步,需要网络中部署VXLAN控制器。也就是说,传统方案中,电信系统需要引入额外的控制器,使得管理复杂度较高。
图3示出了本申请实施例的用于报文传输的方法的示意性流程图。
应理解,本申请实施例可以应用于图1所示的通信系统中。
301,第一节点中的第二容器可以向应用管理模块发送请求信息,该请求信息用于请求第二节点中的第一容器的第一地址对应的第二地址,该第一地址为IP地址,该第二地址为MAC地址,或该第一地址为MAC地址,该第二地址为IP地址。
具体地,第一节点中的第二容器想要向第二节点中的第一容器发送报文,若只知道第一容器的第一地址(例如,该第一节点的操作系统中只存储该第一容器的第一地址),则可以向该第一节点中的应用管理模块发送请求信息,以请求该第一地址对应的第二地址。其中,若第一地址是IP地址,则第二地址可以是MAC地址;若第一地址是MAC地址,则第二地址可以是IP地址。也就是说,第二容器需要获得第一容器的IP地址和MAC地址才能实现向第一容器发送报文。
可以理解的是,该第一节点中除包括该第二容器,还可以包括其他容器,本申请对此不进行限定。类似地,该第二节点中除包括该第一容器,还可以包括其他容器,本申请对此不进行限定。
302,第一节点中的应用管理模块根据该第一容器的第一地址和第一关联关系,确定该第 一容器的第二地址,该第一关联关系为该第二节点中容器的第一地址和第二地址之间的关联关系。
具体地,应用管理模块可以存储第二节点中容器的第一地址和第二地址之间的第一关联关系。也就是说,应用管理模块可以根据该第一地址和该第一关联关系得到第二地址,例如,直接获得,或者间接推导得到。
可以理解的是,该第一关联关系可以包括第二节点中的某一个容器(例如,第一容器)的第一地址与该第一容器的第二地址具有关联关系,也可以包括第二节点中的一个或多个容器中的每个容器的第一地址与第二地址具有关联关系。例如,该第一关联关系包括第一容器的IP地址与第一容器的MAC地址的对应关系。
还可以理解的是,该第一关联关系也可以是看作是一种预先制定的规则。应该管理模块可以根据该第一地址和该规则推导得到该第二地址。
可选地,在第一容器的MAC地址包括至少一个字节,该第一容器的IP地址包括至少一个字节的情况下,该第一关联关系为该第一容器的MAC地址中的部分字节的取值与该第一容器的IP地址中的部分字节的取值相同。
具体地,MAC地址中的与IP地址中取值相同的部分字节为多个的情况下,该多个字节可以是连续的,也可以是不连续的,本申请对此不进行限定。也就是说,第一容器的MAC地址中的部分字节中的每个字节的取值可以分别与第一容器的IP地址的多个字节中某个字节的取值相同,也可以是该第一容器的MAC地址中的部分字节的整体取值与该第一器的IP地址的多个字节的整体取值相同。
可以理解的是,一个字节可以包括一个或多个比特位。其中,取值相同的不同字节包括的比特位可以相同,也可以不同,本申请对此不进行限定。
还可以理解的是,本申请实施例可以应用于(互联网协议第4版,IPv4)场景中,也可以引用于IPv6场景中,本申请对此不进行限定。
还可以理解的是,该第一关联关系可以是临时生成的,也可以是已知存储在应用管理模块中的,本申请对此不进行限定。
可选地,在第一容器的MAC地址包括六个字节,第一容器的IP地址包括四个字节的情况下,该第一关联关系为该第一容器的MAC地址中的第四个字节的取值与该第一容器的IP地址中的第二个字节的取值相同,该第一容器的MAC地址中的第五个字节的取值与该第一容器的IP地址中的第三个字节的取值相同,以及该第一容器的MAC地址中的第六个字节的取值与该第一容器的IP地址中的第四个字节的取值相同。
具体地,若MAC地址包括六个字节,则MAC地址的结构可以为“0a:0a:0a:业务IP第4字节:业务IP第5字节:业务IP第6字节”。
其中,业务IP地址的第二字节与MAC地址的第四字节的进制可以不同。例如,IP地址为“10.101.10.100”对应的MAC地址为“0a:0a:0a:65:0a:64”(下划线上的数字具有对应关系,倾斜字体的数字也具有对应关系)。即IP地址的字节通过二进制表示,MAC地址的字节通过16进制表示。
需要说明的是,除具有关联关系的字节之外的字节可以是预先设定的,例如,IP地址中的第一个字节设定为“10”,MAC地址的前三个字节设定为“0a:0a:0a”,或者还可以是其他预先设定的取值,本申请对此不进行限定。
可选地,在第一地址为IP地址的情况下,该应用管理模块还可以根据该第一容器的IP地址和第二关联关系确定该第二节点的IP地址,并将该第二节点的IP地址写入操作系统中。其中,该第二节点用于向该第一容器转发报文,该第二关联关系为节点的IP地址与第二节点中容器的IP地址之间的关联关系。
具体地,在第一地址为IP地址,第二地址为MAC地址的情况下,若第一节点无法直接找到第一容器(即没有到该第一容器的路由信息),则第二容器需要先找到包括该第一容器的第二节点,再由第二节点将报文转发给第一容器。例如,第二容器向应用管理模块发送3层信息缺失(layer3miss,L3MISS)信息,应用管理模块在检测到该L3MISS信息,得知IP地址缺少路由信息。
可以理解的是,该第二关联关系可以包括第二节点中的某一个容器(例如,第一容器)与第二节点的IP地址的对应关系,也可以是包括第二节点中的多个容器中的每个容器分别与节点的IP地址的关联关系,本申请对此不进行限定。
可选地,该第一容器的IP地址包括至少一个字节,该第二节点的IP地址包括至少一个字节,该第二关联关系为该第一容器的IP地址中的部分字节的取值与该第二节点的IP地址中的部分字节的取值相同。
具体地,所述第一容器的IP地址包括四个字节,所述第二节点的IP地址包括四个字节,该第二关联关系为所述第一容器的IP地址中的第二字节的取值与所述第二节点的IP地址中的第三个字节的取值相同,所述第一容器的IP地址中的第三字节的取值与所述第二节点的IP地址中的第四个字节的取值相同。
例如,若该第一容器的IP地址为“10.101.10.100”,则第二节点的IP地址为“172.16.101.10”。
需要说明的是,节点的IP地址的前两个字节可以是预先设定的,例如,节点的IP地址的前两个字节为“172.16”。其中,容器的IP地址中的最后一个字节可以是节点内的唯一序号。
可选地,在第一地址为MAC地址的情况下,该应用管理模块还可以根据该第一容器的MAC地址和第三关联关系确定该第二节点的IP地址,并将该第二节点的IP地址写入操作系统中,该第三关联关系为节点的IP地址与第一容器的MAC地址的关联关系。其中,该第二节点用于向该第一容器转发报文。
具体地,若第二容器根据该第一容器的MAC地址无法找到第一容器,则第二容器需要先找到包括该第一容器的第二节点,再由第二节点将报文转发给第一容器。例如,第二容器向应用管理模块发送2层信息缺失(layer 2miss,L2MISS)信息,应用管理模块在检测到该L2MISS信息,得知MAC地址缺少路由信息。
可选地,该第一容器的MAC地址包括至少一个字节,该第二节点的IP地址包括至少一个字节,该第三关联关系为该第一容器的MAC地址中的部分字节的取值与该第二节点的IP地址中的部分字节的取值相同。
具体地,所述第一容器的MAC地址包括六个字节,所述第二节点的IP地址包括四个字节,该第三关联关系为所述第一容器的MAC地址中的第五字节的取值与所述第二节点的IP地址中的第三个字节的取值相同,所述第一容器的MAC地址中的第六字节的取值与所述第二节点的IP地址中的第四个字节的取值相同。
例如,该第一容器的MAC地址为“0a:0a:0a:66:1e:6a”,则对应的第二节点的IP地址为“172.16.102.30”。
可以理解的是,节点的IP地址的前两个字节可以是预先设定的,例如,节点的IP地址的前两个字节为“172.16”。
303,该应用管理模块在操作系统中写入该第二地址,该第二地址为该第一节点中的第二容器传输报文的目的地址。
具体地,应用管理模块可以将第二地址写入操作系统的系统缓存中,例如,该第二地址写入转发数据库(forwarding database,FDB)表。
可以理解的是,应用管理模块可以随操作系统启动而启动,启动后可以检查第一节点的接口是否正确配置。若没有正确配置,则进行接口的配置。例如,该接口为VXLAN接口。
还可以理解的是,该操作系统可以是OS。
还可以理解的是,该应用管理模块也可以主动执行更新第一地址对应的第二地址,例如,定时更新。也就是说,本申请中可以不执行步骤301。
304,该第二容器从操作系统中检测该第一容器的第一地址对应的该第一容器的第二地址。
305,该第二容器根据该第一容器的第二地址和该第一容器的第一地址,向该第一容器发送报文。
第一节点可以存储第二节点中容器的第一地址和第二地址之间的第一关联关系,这样第一节点中的应用管理模块可以根据第二节点中的第一容器的第一地址和该第一关联关系确定出该第一容器的第二地址,进而将第一容器的第二地址写入操作系统中,这样有助于第二容器从操作系统中获得该第一容器的IP地址和MAC地址,从而能够实现向第一容器发送报文,相对于传统方案引入额外的控制器,本申请实施例降低了系统的管理复杂度。
应理解,本申请实施例中的具体的例子只是为了帮助本领域技术人员更好地理解本申请实施例,而非限制本申请实施例的范围。
还应理解,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
还应理解,在本申请的各个实施例中,如果没有特殊说明以及逻辑冲突,不同的实施例之间的术语和/或描述具有一致性、且可以相互引用,不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
以上,结合图3详细说明了本申请实施例提供的方法。以下,结合图4-图7详细说明本申请实施例提供的节点。应理解,装置实施例的描述与方法实施例的描述相互对应,因此,未详细描述的内容可以参见上文方法实施例,为了简洁,部分内容不再赘述。
图4示出了本申请实施例的用于报文传输的节点400的示意性框图。
应理解,该节点400可以实现图3所示的实施例的方法。例如,该节点400可以包括图3所示的应用管理模块410和操作系统420。可选地,该节点400还可以包括图3所示的第二容器。
还可以理解的是,该节点400可以是物理机或者虚拟机。
该应用管理模块410,用于根据第二节点中的第一容器的第一地址和第一关联关系,确定所述第一容器的第二地址,所述第一关联关系为所述第二节点中容器的第一地址和第二地址之间的关联关系,所述第一地址为IP地址,所述第二地址为MAC地址,或者所述第一地址 为MAC地址,所述第二地址为IP地址;
所述应用管理模块410,还用于在操作系统420中写入所述第二地址,所述第二地址为所述第一节点中的第二容器传输报文的目的地址
可选地,所述应用管理模块410,还用于接收来自所述第二容器的请求信息,所述请求信息用于请求所述第一地址对应的第二地址。
可选地,所述应用管理模块410,还用于根据所述第一容器的IP地址和第二关联关系,确定所述第二节点的IP地址,所述第二节点用于向所述第一容器转发所述报文,所述第二关联关系为节点的IP地址与所述第二节点中容器的IP地址之间的关联关系;所述应用管理模块,还用于在所述操作系统中写入所述第二节点的IP地址。
可选地,所述第一容器的IP地址包括至少一个字节,所述第二节点的IP地址包括至少一个字节,所述第二关联关系为所述第一容器的IP地址中的部分字节的取值与所述第二节点的IP地址中的部分字节的取值相同。
可选地,所述第一容器的IP地址包括四个字节,所述第二节点的IP地址包括四个字节,所述第二关联关系为所述第一容器的IP地址中的第二字节的取值与所述第二节点的IP地址中的第三个字节的取值相同,所述第一容器的IP地址中的第三字节的取值与所述第二节点的IP地址中的第四个字节的取值相同。
可选地,所述第一容器的MAC地址包括至少一个字节,所述第一容器的IP地址包括至少一个字节,所述第一关联关系为所述第一容器的MAC地址中的部分字节的取值与所述第一容器的IP地址中的部分字节的取值相同。
可选地,所述第一容器的MAC地址包括六个字节,所述第一容器的IP地址包括四个字节,所述第一关联关系为所述第一容器的MAC地址中的第四个字节的取值与所述第一容器的IP地址中的第二个字节的取值相同,所述第一容器的MAC地址中的第五个字节的取值与所述第一容器的IP地址中的第三个字节的取值相同,以及所述第一容器的MAC地址中的第六个字节的取值与所述第一容器的IP地址中的第四个字节的取值相同。
图5示出了本申请实施例提供的用于报文传输的节点500。该节点可以采用如图5所示的硬件架构。该节点可以包括处理器510和收发器520,可选地,该节点还可以包括存储器530,该处理器510、收发器520和存储器530通过内部连接通路互相通信。图4中的应用管理模块410的所实现的一部分相关功能可以由处理器510来实现,另一部分相关功能可以由处理器510控制收发器520来实现。
可选地,处理器510可以是一个通用中央处理器(central processing unit,CPU),微处理器,特定应用集成电路(application-specific integrated circuit,ASIC),专用处理器,或一个或多个用于执行本申请实施例技术方案的集成电路。或者,处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。例如可以是基带处理器、或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理,中央处理器可以用于对通信装置(如,基站、终端、或芯片等)进行控制,执行软件程序,处理软件程序的数据。
可选地,该处理器510可以包括是一个或多个处理器,例如包括一个或多个中央处理单元(central processing unit,CPU),在处理器是一个CPU的情况下,该CPU可以是单核CPU,也可以是多核CPU。
该收发器520用于发送和接收数据和/或信号,以及接收数据和/或信号。该收发器可以包括发射器和接收器,发射器用于发送数据和/或信号,接收器用于接收数据和/或信号。
该存储器530包括但不限于是随机存取存储器(random access memory,RAM)、只读存储器(read-only memory,ROM)、可擦除可编程存储器(erasable programmable read only memory,EPROM)、只读光盘(compact disc read-only memory,CD-ROM),该存储器530用于存储相关指令及数据。
存储器530用于存储网络设备的程序代码和数据,可以为单独的器件或集成在处理器510中。
具体地,所述处理器510用于控制收发器与第二容器进行信息传输。具体可参见方法实施例中的描述,在此不再赘述。
在具体实现中,作为一种实施例,节点500还可以包括输出设备和输入设备。输出设备和处理器510通信,可以以多种方式来显示信息。例如,输出设备可以是液晶显示器(liquid crystal display,LCD),发光二级管(light emitting diode,LED)显示设备,阴极射线管(cathode ray tube,CRT)显示设备,或投影仪(projector)等。输入设备和处理器510通信,可以以多种方式接收用户的输入。例如,输入设备可以是鼠标、键盘、触摸屏设备或传感设备等。
可以理解的是,图5仅仅示出了通信节点的简化设计。在实际应用中,该节点还可以分别包含必要的其他元件,包含但不限于任意数量的收发器、处理器、控制器、存储器等,而所有可以实现本申请的节点备都在本申请的保护范围之内。
还应理解,该节点500还可以是芯片或芯片系统。在该节点为芯片或芯片系统时,该节点500中的应用管理模块410可以包括数据传输接口、接口电路、数据传输电路或管脚,和处理器、处理电路或逻辑电路,存储单元可以为存储器或存储电路。
图6示出了本申请实施例的用于报文传输的节点600的示意性框图。
应理解,该节点600可以实现图3所示的方法。该节点可以包括图3所示实施例中的第二容器。该节点600还可以包括图3所述的应用管理模块和操作系统。也就是说,图4所述的节点与图6所示的节点为同一个节点。即同一个节点内容应用管理模块和第二容器进行交互。或者图4所述的节点与图6所示的节点为不同的节点,例如,第一节点的第二容器可以从第三节点中的操作系统中获取第二节点中的第一容器的第一地址或第二地址。
还可以理解的是,该节点600可以是物理机或者虚拟机。
该节点600可以包括用于执行前述方法实施例中的各个操作的单元。并且,该节点600中的各模块分别为了实现前述任意方法中第二容器的相应流程。该节点600包括收发模块610和处理模块620。
该收发模块610,用于向应用管理模块发送请求信息,所述请求信息用于请求第二节点中的第一容器的第一地址对应的所述第一容器的第二地址,所述第一地址为IP地址,所述第二地址为MAC地址,或者所述第一地址为MAC地址,所述第二地址为IP地址;
该处理模块620,用于从操作系统中检测所述第一容器的第一地址对应的所述第一容器的第二地址;
所述收发模块610,还用于根据所述第一容器的第一地址和所述第一容器的第二地址,向所述第一容器发送报文。
可选地。在所述第一地址为MAC地址,所述第二地址为IP地址的情况下,所述处理模块620,还用于从所述操作系统中检测所述第一容器的MAC地址对应的第二节点的IP地址;所述收发模块610具体用于:向所述第二节点的IP地址对应的第二节点发送所述报文,所述第二节点用于向所述第一容器转发所述报文。
图7示出了本申请实施例提供的用于报文传输的节点700。该节点可以采用如图7所示的硬件架构。该节点可以包括处理器710和收发器720,可选地,该节点还可以包括存储器730,该处理器710、收发器720和存储器730通过内部连接通路互相通信。图6中的处理模块620的所实现的部分相关功能可以由处理器710来实现,收发模块610所实现的部分相关功能可以由处理器710控制收发器720来实现。
可选地,处理器710可以是一个通用中央处理器(central processing unit,CPU),微处理器,特定应用集成电路(application-specific integrated circuit,ASIC),专用处理器,或一个或多个用于执行本申请实施例技术方案的集成电路。或者,处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。例如可以是基带处理器、或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理,中央处理器可以用于对通信节点(如,基站、终端、或芯片等)进行控制,执行软件程序,处理软件程序的数据。
可选地,该处理器710可以包括是一个或多个处理器,例如包括一个或多个中央处理单元(central processing unit,CPU),在处理器是一个CPU的情况下,该CPU可以是单核CPU,也可以是多核CPU。
该收发器720用于发送和接收数据和/或信号,以及接收数据和/或信号。该收发器可以包括发射器和接收器,发射器用于发送数据和/或信号,接收器用于接收数据和/或信号。
该存储器730包括但不限于是随机存取存储器(random access memory,RAM)、只读存储器(read-only memory,ROM)、可擦除可编程存储器(erasable programmable read only memory,EPROM)、只读光盘(compact disc read-only memory,CD-ROM),该存储器730用于存储相关指令及数据。
存储器730用于存储网络设备的程序代码和数据,可以为单独的器件或集成在处理器710中。
具体地,所述处理器710用于控制收发器与应用管理模块进行信息传输。具体可参见方法实施例中的描述,在此不再赘述。
在具体实现中,作为一种实施例,节点700还可以包括输出设备和输入设备。输出设备和处理器710通信,可以以多种方式来显示信息。例如,输出设备可以是液晶显示器(liquid crystal display,LCD),发光二级管(light emitting diode,LED)显示设备,阴极射线管(cathode ray tube,CRT)显示设备,或投影仪(projector)等。输入设备和处理器710通信,可以以多种方式接收用户的输入。例如,输入设备可以是鼠标、键盘、触摸屏设备或传感设备等。
可以理解的是,图7仅仅示出了通信节点的简化设计。在实际应用中,该节点还可以分别包含必要的其他元件,包含但不限于任意数量的收发器、处理器、控制器、存储器等,而所有可以实现本申请的网络设备都在本申请的保护范围之内。
还应理解,该节点700还可以是芯片或芯片系统。在该节点为芯片或芯片系统时,该节 点700中的收发模块710可以为数据传输接口、接口电路、数据传输电路或管脚,处理模块720可以为处理器、处理电路或逻辑电路,存储单元可以为存储器或存储电路。
应理解,上述节点为芯片时,该芯片可以是现场可编程门阵列(field programmable gate array,FPGA),可以是专用集成芯片(application specific integrated circuit,ASIC),还可以是系统芯片(system on chip,SoC),还可以是中央处理器(central processor unit,CPU),还可以是网络处理器(network processor,NP),还可以是数字信号处理电路(digital signal processor,DSP),还可以是微控制器(micro controller unit,MCU),还可以是可编程控制器(programmable logic device,PLD)或其他集成芯片。
可选地,本申请实施例还示出了一种系统,该系统包括图4所示的节点400和图6所示的节点600。
作为本实施例的另一种形式,提供一种计算机可读存储介质,其上存储有指令,该指令被执行时执行上述方法实施例中的方法。
作为本实施例的另一种形式,提供一种包含指令的计算机程序产品,该指令被执行时执行上述方法实施例中的方法。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如,软盘、硬盘、磁带)、光介质(例如,高密度数字视频光盘(digital video disc,DVD))、或者半导体介质(例如,固态硬盘(solid state disk,SSD))等。
应理解,处理器可以是集成电路芯片,具有信号的处理能力。在实现过程中,上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现成可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。
可以理解,本申请实施例中的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(read-only memory, ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchronous link DRAM,SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM,DR RAM)。
本申请中,“至少一个”是指一个或者多个,“多个”是指两个或两个以上。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B的情况,其中A,B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达,是指的这些项中的任意组合,包括单项(个)或复数项(个)的任意组合。例如,a,b,或c中的至少一项(个),可以表示:a,b,c,a-b,a-c,b-c,或a-b-c,其中a,b,c可以是单个,也可以是多个。
应理解,说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本发明的至少一个实施例中。因此,在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外,这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。应理解,在本发明的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本发明实施例的实施过程构成任何限定。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如,部件可以是但不限于,在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示,在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中,部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外,这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据,例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
还应理解,本文中涉及的第一、第二以及各种数字编号仅为描述方便进行的区分,并不用来限制本申请实施例的范围。
应理解,本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。其中,单独存在A或B,并不限定A或B的数量。以单独存在A为例,可以理解为具有一个或多个A。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范 围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(read-only memory,ROM)、随机存取存储器(random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。

Claims (14)

  1. 一种用于报文传输的方法,特征在于,包括:
    第一节点中的应用管理模块根据第二节点中的第一容器的第一地址和第一关联关系,确定所述第一容器的第二地址,所述第一关联关系为所述第二节点中容器的第一地址和第二地址之间的关联关系,所述第一地址为互联网协议IP地址,所述第二地址为媒体访问控制MAC地址,或者所述第一地址为MAC地址,所述第二地址为IP地址;
    所述应用管理模块在操作系统中写入所述第二地址,所述第二地址为所述第一节点中的第二容器传输报文的目的地址。
  2. 根据权利要求1所述的方法,其特征在于,所述应用管理模块根据所述第一地址确定所述第二地址之前,所述方法还包括:
    所述应用管理模块接收来自所述第二容器的请求信息,所述请求信息用于请求所述第一地址对应的第二地址。
  3. 根据权利要求1或2所述的方法,其特征在于,在所述第一地址为IP地址的情况下,所述方法还包括:
    所述应用管理模块根据所述第一容器的IP地址和第二关联关系,确定所述第二节点的IP地址,所述第二节点用于向所述第一容器转发所述报文,所述第二关联关系为节点的IP地址与所述第二节点中容器的IP地址之间的关联关系;
    所述应用管理模块在所述操作系统中写入所述第二节点的IP地址。
  4. 根据权利要求3所述的方法,其特征在于,所述第一容器的IP地址包括至少一个字节,所述第二节点的IP地址包括至少一个字节,所述第二关联关系为所述第一容器的IP地址中的部分字节的取值与所述第二节点的IP地址中的部分字节的取值相同。
  5. 根据权利要求4所述的方法,其特征在于,所述第一容器的IP地址包括四个字节,所述第二节点的IP地址包括四个字节,所述第二关联关系为所述第一容器的IP地址中的第二字节的取值与所述第二节点的IP地址中的第三个字节的取值相同,所述第一容器的IP地址中的第三字节的取值与所述第二节点的IP地址中的第四个字节的取值相同。
  6. 根据权利要求1至5中任一项所述的方法,其特征在于,所述第一容器的MAC地址包括至少一个字节,所述第一容器的IP地址包括至少一个字节,所述第一关联关系为所述第一容器的MAC地址中的部分字节的取值与所述第一容器的IP地址中的部分字节的取值相同。
  7. 根据权利要求6所述的方法,其特征在于,所述第一容器的MAC地址包括六个字节,所述第一容器的IP地址包括四个字节,所述第一关联关系为所述第一容器的MAC地址中的第四个字节的取值与所述第一容器的IP地址中的第二个字节的取值相同,所述第一容器的MAC地址中的第五个字节的取值与所述第一容器的IP地址中的第三个字节的取值相同,以及所述第一容器的MAC地址中的第六个字节的取值与所述第一容器的IP地址中的第四个字节的取值相同。
  8. 一种用于报文传输的节点,特征在于,包括:
    应用管理模块,用于根据第二节点中的第一容器的第一地址和第一关联关系,确定所述第一容器的第二地址,所述第一关联关系为所述第二节点中容器的第一地址和第二地址之间的关联关系,所述第一地址为互联网协议IP地址,所述第二地址为媒体访问控制MAC地址, 或者所述第一地址为MAC地址,所述第二地址为IP地址;
    所述应用管理模块,还用于在操作系统中写入所述第二地址,所述第二地址为所述第一节点中的第二容器传输报文的目的地址。
  9. 根据权利要求8所述的节点,其特征在于,所述应用管理模块,还用于接收来自所述第二容器的请求信息,所述请求信息用于请求所述第一地址对应的第二地址。
  10. 根据权利要求8或9所述的节点,其特征在于,所述应用管理模块,还用于根据所述第一容器的IP地址和第二关联关系,确定所述第二节点的IP地址,所述第二节点用于向所述第一容器转发所述报文,所述第二关联关系为节点的IP地址与所述第二节点中容器的IP地址之间的关联关系;
    所述应用管理模块,还用于在所述操作系统中写入所述第二节点的IP地址。
  11. 根据权利要求10所述的节点,其特征在于,所述第一容器的IP地址包括至少一个字节,所述第二节点的IP地址包括至少一个字节,所述第二关联关系为所述第一容器的IP地址中的部分字节的取值与所述第二节点的IP地址中的部分字节的取值相同。
  12. 根据权利要求11所述的节点,其特征在于,所述第一容器的IP地址包括四个字节,所述第二节点的IP地址包括四个字节,所述第二关联关系为所述第一容器的IP地址中的第二字节的取值与所述第二节点的IP地址中的第三个字节的取值相同,所述第一容器的IP地址中的第三字节的取值与所述第二节点的IP地址中的第四个字节的取值相同。
  13. 根据权利要求8至12中任一项所述的节点,其特征在于,所述第一容器的MAC地址包括至少一个字节,所述第一容器的IP地址包括至少一个字节,所述第一关联关系为所述第一容器的MAC地址中的部分字节的取值与所述第一容器的IP地址中的部分字节的取值相同。
  14. 根据权利要求13所述的节点,其特征在于,所述第一容器的MAC地址包括六个字节,所述第一容器的IP地址包括四个字节,所述第一关联关系为所述第一容器的MAC地址中的第四个字节的取值与所述第一容器的IP地址中的第二个字节的取值相同,所述第一容器的MAC地址中的第五个字节的取值与所述第一容器的IP地址中的第三个字节的取值相同,以及所述第一容器的MAC地址中的第六个字节的取值与所述第一容器的IP地址中的第四个字节的取值相同。
PCT/CN2021/090513 2020-05-09 2021-04-28 用于报文传输的方法和节点 WO2021227873A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010387411.6 2020-05-09
CN202010387411.6A CN113630300B (zh) 2020-05-09 2020-05-09 用于报文传输的方法和节点

Publications (1)

Publication Number Publication Date
WO2021227873A1 true WO2021227873A1 (zh) 2021-11-18

Family

ID=78377479

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/090513 WO2021227873A1 (zh) 2020-05-09 2021-04-28 用于报文传输的方法和节点

Country Status (2)

Country Link
CN (1) CN113630300B (zh)
WO (1) WO2021227873A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116996435A (zh) * 2022-04-25 2023-11-03 华为技术有限公司 一种报文处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106953943A (zh) * 2017-04-25 2017-07-14 中国联合网络通信集团有限公司 适用于交换机通信的方法及装置
CN107070691A (zh) * 2017-01-12 2017-08-18 阿里巴巴集团控股有限公司 Docker容器的跨主机通信方法和系统
CN108574705A (zh) * 2017-03-09 2018-09-25 中国移动通信集团湖北有限公司 一种容器间的通信方法、装置及系统
US20180375825A1 (en) * 2017-06-23 2018-12-27 Cisco Technology, Inc. Container networking for connecting network controller applications to a switch fabric
CN110858821A (zh) * 2018-08-23 2020-03-03 阿里巴巴集团控股有限公司 容器通信方法及装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7185107B1 (en) * 2002-10-02 2007-02-27 Cisco Technology Inc. Redirecting network traffic through a multipoint tunnel overlay network using distinct network address spaces for the overlay and transport networks
CN102469170B (zh) * 2010-11-03 2014-04-16 英业达集团(天津)电子技术有限公司 Dos系统下静态ip地址的生成方法
EP2854377B1 (en) * 2013-09-27 2016-07-13 Alcatel Lucent A method for centralized address resolution
CN105635326A (zh) * 2014-10-27 2016-06-01 国基电子(上海)有限公司 网络设备及ip地址分配方法
CN106489252B (zh) * 2015-05-25 2020-09-04 华为技术有限公司 一种数据传输方法及装置
CN106254256B (zh) * 2015-06-04 2019-08-16 新华三技术有限公司 基于三层vxlan网关的数据报文转发方法和设备
US10523796B2 (en) * 2015-12-22 2019-12-31 Intel Corporation Techniques for embedding fabric address information into locally-administered Ethernet media access control addresses (MACs) and a multi-node fabric system implementing the same
US10169048B1 (en) * 2017-06-28 2019-01-01 International Business Machines Corporation Preparing computer nodes to boot in a multidimensional torus fabric network
CN108964972B (zh) * 2018-05-24 2021-02-12 华为技术有限公司 一种计算节点管理的方法、装置和系统
CN110932890B (zh) * 2019-11-20 2022-09-09 厦门网宿有限公司 一种数据传输方法、服务器及计算机可读存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107070691A (zh) * 2017-01-12 2017-08-18 阿里巴巴集团控股有限公司 Docker容器的跨主机通信方法和系统
CN108574705A (zh) * 2017-03-09 2018-09-25 中国移动通信集团湖北有限公司 一种容器间的通信方法、装置及系统
CN106953943A (zh) * 2017-04-25 2017-07-14 中国联合网络通信集团有限公司 适用于交换机通信的方法及装置
US20180375825A1 (en) * 2017-06-23 2018-12-27 Cisco Technology, Inc. Container networking for connecting network controller applications to a switch fabric
CN110858821A (zh) * 2018-08-23 2020-03-03 阿里巴巴集团控股有限公司 容器通信方法及装置

Also Published As

Publication number Publication date
CN113630300A (zh) 2021-11-09
CN113630300B (zh) 2023-08-08

Similar Documents

Publication Publication Date Title
CN109587281B (zh) 容器配置方法和计算节点
CN112398817B (zh) 数据发送的方法及设备
CN111490923B (zh) 基于bras系统的报文封装方法、装置及系统
WO2020164290A1 (zh) 策略控制方法、装置及系统
CN104221331B (zh) 用于以太网交换机的没有查找表的第2层分组交换
US10348612B2 (en) Set up of direct mapped routers located across independently managed compute and storage networks
CN112040030B (zh) 报文传输方法、装置、计算机设备及存储介质
US11829309B2 (en) Data forwarding chip and server
WO2020119310A1 (zh) 查找表存储方法、装置及计算机可读存储介质
WO2020038443A1 (zh) 桥接通信的方法和设备
EP3217616A1 (en) Memory access method, switch and multi-processor system
WO2021227873A1 (zh) 用于报文传输的方法和节点
US20220107752A1 (en) Data access method and apparatus
WO2023125565A1 (zh) 网络节点的配置和访问请求的处理方法、装置
US20230045914A1 (en) Method and apparatus for controlling device in internet of things, and gateway device and storage medium
WO2022199357A1 (zh) 数据处理方法及装置、电子设备、计算机可读存储介质
CN112910910B (zh) Opcda协议报文处理方法、装置、设备以及存储介质
JP2024510438A (ja) コンピューティング・システムにおけるメモリ動作管理
US11909624B2 (en) Communication method, apparatus, device, system, and computer-readable storage medium
WO2022228184A1 (zh) 通信方法、装置、设备、系统及计算机可读存储介质
US11509562B1 (en) System and method for a system level data sharding analysis of information handling systems
US20230205448A1 (en) System and method for a local level data sharding analysis of information handling systems
WO2023207278A1 (zh) 一种报文处理方法及装置
US11874940B2 (en) Method and system for limiting access of multiple data nodes to shared storage during the performance of data protection services through load balancing
WO2022228401A1 (zh) 数据传输方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21805058

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21805058

Country of ref document: EP

Kind code of ref document: A1