A message addressing method, apparatus and readable storage medium

Abstract

A message addressing method, apparatus, and readable storage medium are disclosed, relating to the field of communication technology, for achieving low-cost, high-efficiency message forwarding path addressing. The method includes: a first device receiving a first message through a first port, the first message including first addressing information, the first addressing information including at least one port number in a forwarding list, the at least one port number including a second port number of a second port of the first device; the first device sending a second message through the second port, the second message including second addressing information, the second addressing information being an update of the first addressing information, wherein the second port number in the second addressing information is updated to the first port number of the first port.

Description

[0001] This application claims priority to Chinese Patent Application No. 202311563704.5, filed on November 21, 2023, entitled “A message addressing method, apparatus and readable storage medium”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a message addressing method, apparatus and readable storage medium. Background Technology

[0003] In high-speed interconnected networks, after receiving a packet, a target device often needs to reply with an acknowledgment packet to the source device of the packet to confirm that the packet has been successfully received. Therefore, any device in the network needs to obtain the packet's path information when it receives a packet. In some network topologies, there are situations where the source device and path length of a packet received by a device are uncertain, making it impossible for devices in the network to statically configure the packet path. Therefore, there is an urgent need for a low-cost, high-efficiency addressing method that supports obtaining the packet forwarding path. Summary of the Invention

[0004] This application provides a message addressing method, apparatus, and readable storage medium, which enables low-cost and high-efficiency message forwarding path addressing.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, a message addressing method is provided, the method comprising: a first device receiving a first message through a first port (or receiving port), the first device being an intermediate device for forwarding the first message; the first message including first addressing information, the first addressing information including at least one port number in a forwarding list, the at least one port number including the port number of each of at least one intermediate device, the at least one port number including the second port number of a second port (or sending port) of the first device; the first device sending a second message through the second port, the second message including second addressing information, the second addressing information being an update of the first addressing information, the second message being an update of the first message, wherein the second port number in the second addressing information is updated to the first port number of the first port.

[0007] In the above technical solution, the first device receives a first message through a first port. The first addressing information of the first message includes at least one port number in the forwarding list. The first device can update the first addressing information to second addressing information. For example, it can update the second port number of the second port of the first device in the at least one port number of the first addressing information to the first port number of the first port, and then send a second message including the second addressing information through the second port. In this way, when the target device of the first message receives the message, the addressing information of the message includes the port number of each device in the forwarding path that receives the message. Thus, the target device can obtain the addressing information of the response message based on the addressing information of the message, thereby realizing low-cost and high-efficiency addressing of the message forwarding path.

[0008] In one possible implementation of the first aspect, the first addressing information or the second addressing information further includes a forwarding list length, which indicates the number of the at least one port number, or the total hierarchy of the forwarding list, or the total number of the at least one device. And / or, the first addressing information further includes a first level indication (or the forwarding list hierarchy), which indicates the level at which the first device is located in the forwarding list. In the above possible implementations, the first device can determine whether it is an intermediate device or a target device based on the forwarding list length and the first level indication.

[0009] In one possible implementation of the first aspect, the domain segment containing the forwarding list length can occupy 8 bits, and the domain segment containing the first-level indicator can also occupy 8 bits. The above possible implementations can support up to 127 levels of forwarding, thus meeting the needs of more layered networking.

[0010] In one possible implementation of the first aspect, the second addressing information further includes a second level indication, which is obtained by updating the first level indication. In the above possible implementations, each receiving device in the packet forwarding path can determine its level in a low-cost and high-efficiency manner.

[0011] In one possible implementation of the first aspect, the first message further includes type information indicating the message type of the first message, which is either a request message or a response message. For example, a value of 0 indicates a request message, and a value of 1 indicates a response message. The above possible implementations provide a simple and effective way to indicate message types.

[0012] In one possible implementation of the first aspect, the type of information is a request message, and the second-level indicator is the first-level indicator plus 1; the type of information is a response message, and the second-level indicator is the first-level indicator minus 1. In the above possible implementations, by updating the message's level indicator, each receiving device in the message forwarding path can determine its level in a low-cost and high-efficiency manner.

[0013] In one possible implementation of the first aspect, if the first-level indicator is greater than 0 and not greater than the forwarding list length (i.e., less than or equal to the forwarding list length), the first device is an intermediate device. In the above possible implementation, when the first-level indicator in the first message received by the first device is greater than 0 and less than or equal to the forwarding list length, the first device can be identified as an intermediate device, and thus update the first addressing information of the first message before sending it.

[0014] Secondly, a message addressing device is provided, applied in a first device, the first device being an intermediate device for forwarding the first message. The device includes: a receiving unit, configured to receive the first message through a first port, the first message including first addressing information, the first addressing information including at least one port number in a forwarding list, the at least one port number including the port number of each of at least one intermediate device, the at least one port number including the second port number of a second port of the first device; and a sending unit, configured to send a second message through the second port, the second message including second addressing information, the second addressing information being obtained by updating the first addressing information, the second message being obtained by updating the first message, wherein the second port number in the second addressing information is updated to the first port number of the first port.

[0015] In one possible implementation of the second aspect, the first addressing information or the second addressing information further includes a forwarding list length, which is used to indicate the number of the at least one port number.

[0016] In one possible implementation of the second aspect, the first addressing information further includes a first level indication, which indicates the level at which the first device is located in the forwarding list.

[0017] In one possible implementation of the second aspect, the second addressing information further includes a second-level indicator, which is obtained by updating the first-level indicator.

[0018] In one possible implementation of the second aspect, the first message further includes type information indicating the message type of the first message, which is one of the following: a request message or a response message.

[0019] In one possible implementation of the second aspect, the type of information is a request message, and the second-level indicator is the first-level indicator plus 1.

[0020] In one possible implementation of the second aspect, the information type is a response message, and the second-level indicator is the first-level indicator minus 1.

[0021] In one possible implementation of the second aspect, the first level indicator is greater than 0 and not greater than the length of the forwarding list, and the first device is an intermediate device.

[0022] Thirdly, a message addressing apparatus is provided, which may be a device or a chip applied to a device. The apparatus includes a processing circuit and a transceiver, the processing circuit and the transceiver being configured to support the apparatus in performing the message addressing method provided by the first aspect or any possible implementation thereof.

[0023] Fourthly, a message addressing device is provided. The device may be a device or a chip applied to a device. The device includes a processor and a memory, the memory storing instructions. When the processor executes the instructions in the memory, the device performs the message addressing method provided by the first aspect or any possible implementation of the first aspect.

[0024] In another aspect of this application, a computer-readable storage medium is provided, which stores a computer program or instructions that, when executed, implement a message addressing method as provided in the first aspect or any possible implementation thereof.

[0025] In another aspect of this application, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when executed, causes a computer to perform a message addressing method provided by the first aspect or any possible implementation thereof.

[0026] It is understood that the beneficial effects achieved by any of the message addressing devices, computer-readable storage media, and computer program products provided above can be referred to in accordance with the beneficial effects of the message addressing methods provided above, and will not be repeated here. Attached Figure Description

[0027] Figure 1 This is a schematic diagram of the structure of a data transmission system provided in an embodiment of this application;

[0028] Figure 2 This is a schematic diagram of another data transmission system provided in an embodiment of this application;

[0029] Figure 3 A schematic diagram of the basic components of an electronic device provided in an embodiment of this application;

[0030] Figure 4 A schematic diagram of a data transmission system for multi-device networking provided in an embodiment of this application;

[0031] Figure 5 This is a schematic diagram of routing information in a message provided in an embodiment of this application;

[0032] Figure 6 A flowchart illustrating a message addressing method provided in an embodiment of this application;

[0033] Figure 7 A schematic diagram of addressing information in a message provided in an embodiment of this application;

[0034] Figure 8 A schematic diagram illustrating message transmission between devices, provided as an embodiment of this application;

[0035] Figure 9 A flowchart illustrating another message addressing method provided in an embodiment of this application;

[0036] Figure 10 A schematic diagram of a message addressing device provided in an embodiment of this application;

[0037] Figure 11 This is a schematic diagram of another message addressing device provided in an embodiment of this application. Detailed Implementation

[0038] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, a, b, and c; where a, b, and c can be single or multiple.

[0039] The embodiments of this application use terms such as "first" and "second" to distinguish objects with similar names, functions, or effects. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or order of execution. The term "coupling" is used to indicate an electrical connection, including direct connection via wires or terminals or indirect connection via other devices. Therefore, "coupling" should be considered as a broad type of electronic communication connection.

[0040] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0041] The technical solution provided in this application can be applied to a data transmission system, which may include multiple transmission devices, such as equipment, chips applied to the equipment, or interface devices. In this data transmission system, the multiple transmission devices can be directly connected or indirectly connected. In this application, the multiple transmission devices can transmit signals (e.g., send and receive) via wired means or wireless means. Furthermore, when transmitting signals between the multiple transmission devices, signal transmission can be direct or through an interface device (or receiving device), and then transmitted via a bus to the processing unit inside each device.

[0042] When the transmission device is a chip within a device, the chips in this data transmission system can be interconnected via wired or wireless means. This chip can be a chip within the device, a chip in a docking station, or a chip in an adapter, etc. The docking station can connect to gigabit Ethernet ports, video graphics arrays (VGA), HDMI, trans flash (TF) cards, secure digital cards (SD) cards, charging ports, and USB ports, etc.

[0043] Optionally, when the transmission device is a chip, the chip may further include an interface module, meaning this application can be applied to an interface module for chip-to-chip interconnection. This interface module can be understood as an intellectual property (IP) module integrated within the chip. Alternatively, the interface module can also be sold independently as an IP module. For example, the chip can be a system-on-chip (SoC), a central processing unit (CPU), or a graphics processing unit (GPU), etc., and the aforementioned interface module can be an interface module within the SoC, CPU, or GPU, etc. Optionally, the interface module can be a transmitting circuit and / or a receiving circuit.

[0044] The following example illustrates the structure of a data transmission system, which includes multiple devices.

[0045] Figure 1 This is a schematic diagram of a data transmission system provided in an embodiment of this application. The data transmission system includes multiple devices. Taking a source device (or starting device) 110, at least one intermediate device 120, and a destination device (or target device) 130 as an example, the source device 110 and at least one intermediate device 120, as well as the at least one intermediate device 120 and the destination device 130, can be connected via wired or wireless means, such as through a cable. Signal transmission, such as audio / video data transmission or charging signal transmission, can occur between the source device 110 and at least one intermediate device 120, and between the at least one intermediate device 120 and the destination device 130. Optionally, the at least one intermediate device 120 may include a routing device.

[0046] In one example, the source device 110 can be a television, at least one intermediate device 120 can include a set-top box, and the destination device 130 can be an audio player. The television and the audio player can both be connected to the set-top box via cables. The television can transmit audio data to the set-top box via cables, and the set-top box can transmit audio data to the audio player via cables.

[0047] Furthermore, the at least one intermediate device 120 may include multiple intermediate devices 120, which may be connected according to a network topology. For example, the source device 110, the multiple intermediate devices 120, and the destination device 130 may be connected in a mesh topology, such as a ring topology or a star topology, etc., and this application embodiment does not impose specific limitations in this regard.

[0048] Optionally, taking the at least one intermediate device 120 as an example, the source device 110 may include interface A, the intermediate device 120 may include interface B and interface C, and the destination device 130 may include interface D. The interface A of the source device 110 and the interface B of the intermediate device 120 are connected by a cable, and the interface C of the intermediate device 120 and the interface D of the destination device 130 can also be connected by a cable.

[0049] Figure 2 This is a schematic diagram of another data transmission system provided in an embodiment of this application. The data transmission system includes multiple devices connected via wired or wireless means. These devices can transmit signals, such as audio / video data or charging signals. For example, the multiple devices may include a display 210, a set-top box 220, an audio player (e.g., MP3 player) 230, and a router 240. The display 210, set-top box 220, and audio player 230 can all be connected to the router 240 via cables, and the router 240 can be used for audio / video data transmission or charging signal transmission. In one example, the set-top box 220 can transmit audio / video data to the display 210 via the router 240, and the set-top box 220 can also transmit audio data to the audio player 230 via the router 240. Additionally, two devices may be interconnected among the multiple devices. For example, the multiple devices may also include a game controller 250, which can be connected to the display 210 and transmit control information to the display 210.

[0050] Optionally, each of the multiple devices may include one or more interfaces, and the multiple devices can be connected to each other through the interfaces. For example, the display 210, the set-top box 220, and the audio player 230 may each include one interface, the router 240 may include a first interface to a third interface, the interface of the display 210 is connected to the first interface of the router 240 through a cable, the interface of the set-top box 220 is connected to the second interface of the router 240 through a cable, and the interface of the audio player 230 is connected to the third interface of the router 240 through a cable.

[0051] The devices in the aforementioned system with data transmission capabilities can be called electronic devices. These electronic devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted. They can also be deployed on water (such as on ships) and in the air (such as on airplanes, balloons, and satellites), and can be applied to various scenarios. For example, the electronic device may include, but is not limited to: mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), camera, wearable device (e.g., smartwatch, smart bracelet, pedometer, etc.), audio equipment, audio and video player, set-top box, game console, printer, mouse, keyboard, in-vehicle equipment (e.g., equipment on vehicles such as cars, bicycles, electric vehicles, airplanes, ships, trains, and high-speed trains), virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, smart home device (e.g., refrigerator, television, air conditioner, electricity meter, etc.), smart robot, workshop equipment, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, or smart home. Wireless terminals in the home, flying equipment (e.g., intelligent robots, hot air balloons, drones, airplanes), etc. Optionally, the signals transmitted between the above electronic devices may include, but are not limited to: audio and video signals, radio frequency signals, Internet of Things data, and charging signals.

[0052] In this application, the interface specifications used for signal transmission between devices in the data transmission system may include, but are not limited to: Universal Serial Bus (USB) interface specifications, High Definition Multimedia Interface (HDMI) specifications, DisplayPort (DP) specifications, Unified Multimedia Interconnection (UMI) interface specifications, and Peripheral Component Interconnect Express (PCI-Express) interface specifications. Correspondingly, the interface may be HDMI, miniHDMI, micro HDMI, Type-A, Type-B, Micro-B, or Type-C, etc.

[0053] For example, in the above example, the interface connection between the set-top box and the monitor, or the interface connection between the game console and the monitor, can be via a USB cable, following the USB interface standard, or the connection can be via an HDMI cable, following the HDMI interface standard.

[0054] It is understood that the interface specifications used for signal transmission between the above-mentioned devices are merely exemplary. In practical applications, the interface specifications may also include other or any interface specifications that may appear in the future, such as the Unified Media Interconnection (UMI) interface, etc. This application embodiment does not impose specific limitations on this.

[0055] In this application, when the aforementioned transmission device is an electronic device, such as Figure 3The diagram illustrates the basic components of an electronic device. The electronic device includes an interface chip 300 (e.g., a UMI interface), which includes one or more adapters 301, a management control adapter 302, and one or more ports 303; alternatively, if the electronic device is a routing device, the interface chip 300 may only include one or more ports 303. Each of the one or more adapters 301 may be coupled to an external component of the interface chip 300. The management control adapter 302 may be coupled to a management control component outside the interface chip 300. Ports 303 may be coupled to a connector 304 of the electronic device, which is used to couple external devices of the electronic device. The one or more adapters 301 may include a transmitting adapter and / or a receiving adapter. For example, when adapter 301 is used for audio / video format adaptation, adapter 301 may be an audio / video transmitting adapter or a receiving adapter. When adapter 301 is used for third-party protocol adaptation, adapter 301 may be a third-party protocol adapter.

[0056] For example, when one or more ports 303 include downlink ports, the transmitting adapter can be used to adapt the service information to be transmitted into service information that can be transmitted on port 303 of the interface chip, and then transmit the service information through port 303. When one or more ports 303 include uplink ports, the receiving adapter 301 can be used to adapt the service information received from port 303 into service information that can be processed internally by the electronic device for internal processing. The management and control adapter 302 can be used to adapt control information.

[0057] Different electronic devices can be combined with their basic components to form various device types. For example, an electronic device may be a source device including at least one downlink port and at least one audio / video transmission adapter; or, an electronic device may be a source device including at least one uplink port and at least one audio / video reception adapter; or, an electronic device may be a docking station device including at least one uplink port, at least one audio / video reception adapter, and at least one conventional audio / video interface; or, an electronic device may be a routing device including at least one downlink port and at least one uplink port, but without audio / video transmission adapters and audio / video reception adapters; or, an electronic device may be a composite device including both uplink and downlink ports, and including transmission adapters and audio / video reception adapters.

[0058] The aforementioned interface chip can also be called a switch.

[0059] Figure 4This is a schematic diagram of a data transmission system with multiple devices in a network, provided in an embodiment of this application. The multiple devices include multiple source devices (e.g., source device 1 and source device 2), at least one routing device (e.g., routing device 1), and multiple destination devices (e.g., destination device 1, destination device 2, and destination device 3).

[0060] Taking source devices 1 and 2 as examples, each with downlink ports, and destination devices 1 to 3 as examples, each with uplink ports, as an example, data from source device 1 can be sent to destination devices 1 and 2 via routing device 1, and data from source device 2 can be sent to destination device 3 via routing device 1. For instance, source device 1's downlink port 405 sends data 1 to routing device 1's uplink port 406. Routing device 1's uplink port 406 then sends a portion of data 11 (data 11) to destination device 1's uplink port 408 via routing device 1's downlink port 407, where destination device 1 processes data 11. Similarly, routing device 1's uplink port 406 sends another portion of data 1 (data 12) to destination device 2's uplink port 410 via routing device 1's downlink port 409, where destination device 2 processes data 12. The source device 2 sends data 2 from its downlink port 411 to the uplink port 412 of the routing device 1. The uplink port 412 of the routing device 1 then sends data 2 to the uplink port 414 of the destination device 3 via its downlink port 413. The destination device 3 then processes the data 2.

[0061] Optionally, source device 1 and source device 2 may further include uplink ports, and destination devices 1 to 3 may further include downlink ports. That is, source device 1, source device 2, and destination devices 1 to 3 may also be composite devices. For example, source device 1 may be a speaker, and destination device 1 may be a monitor. When the speaker sends audio / video data to the monitor, it can send the data to the monitor's uplink port through the speaker's downlink port, with switching occurring through routing device 1. The monitor can also transmit data back through its downlink port, and then transmit the data back to the speaker's uplink port through routing device 1. The uplink ports of source device 1 and source device 2, and the downlink ports of destination devices 1 to 3 are not shown in the figure.

[0062] It is understood that the structures of the source device, routing device and destination device shown in the above figures are merely exemplary. In practical applications, the above devices may include more or fewer components than shown in the figures, or combine certain components, or have different component arrangements. The above examples do not constitute a limitation on the embodiments of this application.

[0063] In high-speed interconnect interfaces, after receiving a message, the target device often needs to reply with an acknowledgment message to the source device to confirm successful reception. Therefore, any device in the network needs to obtain the message's path information upon receiving it. In some network topologies (e.g., ring topologies), any two devices can exchange messages, and the source device and path length of a received message are uncertain. Therefore, devices in the network cannot statically configure message paths. Furthermore, network loops may exist; retrieving the acknowledgment message path by querying locally stored information could lead to inconsistencies between the request and response message paths.

[0064] In related technologies, such as Figure 5 As shown, the routing information in the message typically includes the following fields: total link count (LCT), remaining link count (LCR), and relative address (RA). LCT is 4 bits long and represents the total number of links traversed from the source device to the destination device. LCR is also 4 bits long and represents the remaining link count before the message reaches the destination device. It is initialized to the LCT value by the source device, and each device decrements the LCR value by one before forwarding the message along its transmission path. RA is an array containing LCT-1 elements (represented as RA[0] to RA[LCT-1]). Each element (occupying 4 bits) specifies the port number from which the message originates from each intermediate device. It is initialized by the source device and modified by the intermediate devices. Each intermediate device uses RA[0] as the port number from which the message originates.

[0065] Specifically, the method by which the source device, intermediate device, and destination device of this message address each other based on the aforementioned routing information is as follows:

[0066] Source device: Step 1. Initialize LCT, LCR, and RA; Step 2. Decrement LCR by 1 and send the packet out through the DPTX port;

[0067] Intermediate device: Step 1. Record the sending port of the message as RA[0]; Step 2. Update RA; Step 3. Decrement LCR by 1; Step 4: Send the message out from the sending port recorded in Step 1. The specific process of updating RA is as follows:

[0068]

[0069]

[0070] RA[LCR] = Input Port Number (the physical port number that will receive this message);

[0071] Target device: If LCR equals 0 when a message is received, then the current device is the target device for that message. After updates from all intermediate devices along the path, RA is already the path of the source device for that message. The target device, as the source device for the response message, can generate the routing information for the response message through the following steps: Step 1. Assign both LCR and LCT to the LCT value from the received message; Step 2. Assign the RA value to the RA value from the received message.

[0072] The above is based on Figure 5 In the routing information packet addressing scheme shown, the length of LCT and LCR is 4 bits, which can address up to 16 levels of links, and cannot meet the needs of more levels (e.g., 127 levels) of networking. In addition, each intermediate device needs to perform a shift operation on RA, which will significantly increase the forwarding delay as the distance between devices increases.

[0073] Based on this, embodiments of this application provide a message addressing method. The message in this method includes addressing information, which includes at least one port number from a forwarding list. After the source device sends the message, each intermediate device receiving the message can update the port number used to send the message in the addressing information to the port number used to receive the message. Thus, when the target device receives the message, the addressing information of the message includes the port number of each device in the forwarding path that received the message. Therefore, the target device can obtain the addressing information of the response message based on the addressing information of the message, thereby achieving low-cost and high-efficiency addressing of the message forwarding path.

[0074] Figure 6 This is a flowchart illustrating a message addressing method provided in an embodiment of this application. The method can be applied to the data transmission system described above, and includes the following steps.

[0075] S601: The source device sends a first message, which includes first addressing information, including at least one port number in the forwarding list.

[0076] The forwarding path corresponding to the forwarding list of the first message may include at least one device, which may be at least one intermediate device, or at least one level intermediate device. The at least one port number in the first addressing information may include the port number of each of the at least one device. When the at least one device includes only one device, the at least one port number includes only one port number, and that port number is the port number of that single device; when the at least one device includes multiple devices, the at least one device includes one port number of each of the multiple devices.

[0077] For example, taking the case where the at least one device includes F devices (i.e., corresponding to F levels or tiers), the at least one port number includes F port numbers, which can be used to indicate the port number of each level in the F levels. For example, such as Figure 7 As shown, the port numbers of each of the F levels can be represented sequentially as L1 PortID, L2 PortID, L3 PortID, ..., LF PortID, where L in L1 to LF represents Level. The i-th level device in the at least one device can use the port corresponding to the port number Li PortID of the i-th level among the at least one port number to send the first message. Figure 7 The numbers 0 to 31 in the code represent 32 bits.

[0078] Furthermore, such as Figure 7 As shown, the first addressing information also includes: forwarding list length (FL length), and / or, a first-level indicator. This first-level indicator can also be referred to as the forwarding list level (FL level). Figure 7 The arrangement order and bit positions of the F port numbers, forwarding list length, and forwarding list hierarchy shown in the first addressing information are merely exemplary and do not constitute a limitation on the embodiments of this application.

[0079] The forwarding list length indicates the number of the at least one port number, or the total number of levels in the forwarding list, or the total number of the at least one device. For example, when the at least one port number includes port numbers at F levels, the forwarding list length indicates the number of the at least one port number as F.

[0080] Additionally, the first-level indicator (or the forwarding list level) is used to indicate the level of the current device in the forwarding list. For example, the level indicator is used to indicate the level of the current device with the source device as the origin, and the current device can refer to the device that currently receives the message. The forwarding list level in the first message sent by the source device can be used to indicate the level of the intermediate device that receives the first message sent by the source device.

[0081] Optionally, the first-level indicator segment may occupy multiple bits, and the forwarding list length segment may also occupy multiple bits. The number of these multiple bits can be set according to actual needs, and this application embodiment does not impose specific limitations on this.

[0082] In one example, the segment containing the forwarding list length can occupy 8 bits, meaning that 8 bits are used to transmit the forwarding list length. For instance, to support up to 127 forwarding levels, the forwarding list length can be represented by 7 bits, with a value range of 1 to 127, and the highest-order bit can be reserved; or, to support up to 255 forwarding levels, the forwarding list length can be represented by 8 bits, with a value range of 1 to 255; or, to support 63 forwarding levels, the forwarding list length can be represented by 8 bits, with the remaining 2 highest-order bits reserved.

[0083] In one example, the number of bits occupied by the segment containing the first-level indicator can be the same as the number of bits occupied by the segment containing the forwarding list length. For example, the segment containing the first-level indicator can occupy 8 bits, with a maximum value of 127, and the segment containing the forwarding list length can also occupy 8 bits, with a maximum value of 127-1.

[0084] Optionally, the total number of bits occupied by the addressing information can be required to be an integer multiple of W bytes, where W is a positive integer, such as W equals 4. When the actual total number of bits occupied by the addressing information is less than an integer multiple of W bytes, the addressing information can be padded to an integer multiple of W bytes; that is, the addressing information can also include padding data. For example, the length of the padding data can also be 0 to 28 bits.

[0085] Furthermore, the first message may also include type information, which can be used to indicate the message type of the message, which is one of the following: a request message or a response message. For example, this type information may occupy 1 bit; when the value of this 1 bit is 0, the type information can be used to indicate a request message; when the value of this 1 bit is 1, the type information can be used to indicate a response message.

[0086] It is understood that the above explanation uses the example of this type of information occupying 1 bit, with the value of 1 bit being 0 to indicate a request message and the value of 1 bit being 1 to indicate a response message. In practical applications, the value of 1 bit can also be 1 to indicate a request message, and the value of 1 bit can be 0 to indicate a response message, or this type of information can occupy multiple bits, etc. The above examples do not constitute a limitation on the embodiments of this application, and the embodiments of this application do not specifically limit the number of bits occupied by this type of information or the meaning indicated by the corresponding bit values.

[0087] Optionally, the first message mentioned above can be a management message or a business message, and this application embodiment does not impose specific restrictions on it.

[0088] S602: The first device receives a first message through a first port. The first message includes first addressing information, which includes at least one port number in a forwarding list. This at least one port number includes the second port number of the first device's second port. The second port is the current sending port of the first device.

[0089] The first message received by the first device can be sent by the source device or by an upstream intermediate device. If the first message received by the first device is sent by the source device, the first addressing information in the first message is the same as the first addressing information in the first message sent by the source device. If the first message received by the first device is sent by an upstream intermediate device, the first addressing information in the first message is obtained by updating the first addressing information in the first message sent by the source device by the intermediate device between the first device and the source device. Figure 6 The following example illustrates the situation where the first message received by the first device is sent by the source device.

[0090] In some possible embodiments, for any of the at least one devices, taking the first device as an example, when the first device receives the first message, the first device can update the first addressing information in the first message. The updated first addressing information can be called the second addressing information, and the first message after updating the first addressing information can be called the second message, that is, the second message includes the second addressing information.

[0091] Optionally, the first device may update at least one port number in the first addressing information. For example, the first device may update the second port number in the first addressing information to the first port number of the first port.

[0092] Optionally, the first device may also update the first-level indication in the first addressing information. The updated first-level indication may be referred to as the second-level indication in the second message, that is, the second-level indication is obtained by updating the first-level indication. For example, if the type information of the first message is a request message, the second-level indication is the first-level indication plus 1; if the type information of the first message is a response message, the second-level indication is the first-level indication minus 1.

[0093] In one possible embodiment, for any device in at least one of the devices in the forwarding path of the first message, taking the i-th level device as an example, when the i-th level device receives the first message, it can determine whether it is an intermediate device based on the first addressing information of the first message. If it is determined to be an intermediate device, the i-th level device can record the i-th level port number among the at least one port number, update the first addressing information according to the above description, and then execute the following step S603. If it is determined to be a target device, the steps corresponding to the target device below are executed.

[0094] Specifically, for the i-th level device, if the first level indication in the first addressing information of the first message received by the i-th level device is greater than 0 and not greater than the length of the forwarding list, then the i-th level device is an intermediate device. If the information type of the first message is a request message and the first level indication is equal to the length of the forwarding list + 1 (i.e., FL level = FL length + 1), then the i-th level device is the target device. If the information type of the first message is a response message and the first level is equal to 0, then the i-th level device is the source device, that is, the target device of the response message sent from the target device.

[0095] S603: The first device sends a second message through the second port. The second message includes second addressing information, which is obtained by updating the first addressing information. The second port number is updated to the first port number of the first port.

[0096] In one possible embodiment, as described above, after the first device updates the first addressing information of the first message—for example, after updating at least one port number and the first level indication in the first addressing information—the first device can send a second message through the second port. The second addressing information in the second message is obtained by updating the first addressing information. For example, the second port number (the port number of the sending port) in the at least one port number is updated to the first port number of the first port (the receiving port), and the first level indication is updated to the second level indication.

[0097] It is understood that the specific structure of the second message may be similar to that of the first message. For example, the second message may include second addressing information and type information. The type information of the second message may be consistent with the type information of the first message. For a detailed description of the specific structure of the second message, please refer to the relevant description of the first message. This application embodiment will not repeat this description.

[0098] S604: The second device receives the second message. The second device can be the target device or an intermediate device between the first device and the target device. When the second device is an intermediate device between the first device and the target device, the second device updates the addressing information according to the methods described in steps S602-S603. Figure 6 The following explanation uses the second device as an example.

[0099] In one possible embodiment, if the information type of the second message is a request message, when the target device receives the second message and determines that the second-level indicator in the second message is equal to the forwarding list length + 1 (i.e., FL level = FLlength + 1), the target device can identify itself as the target device. At this time, the target device can determine the forwarding path of the message based on the second addressing information of the second message. For example, the target device can subtract 1 from the second-level indicator in the second addressing information and use the subtracted second addressing information as the addressing information for the response message, and then send the response message. If the information type of the second message is a response message, when the target device receives the second message and determines that the second-level indicator in the second message is equal to 0, the target device can identify itself as the source device of this response message, and the process ends.

[0100] It is understood that when the target device sends the above response message, the target device can be the source device of the response message, the response device can be the first message in S601 above, and the response message as the first message can be sent by the method provided above. The embodiments of this application will not be described again here.

[0101] To facilitate understanding, the following example illustrates how device A sends a request message to device B through three devices (represented as device C1, device C2, and device C3), and how each of these three devices updates the addressing information of the received request message and transmits the request message. Figure 8 This diagram illustrates how device A sends request messages to device B sequentially through devices C1, C2, and C3. The diagram also includes other devices in the network topology. The numbers in the small boxes within each device represent the port numbers corresponding to those ports.

[0102] For example, as shown in Table 1 below, device A sends a request message to device C1. Device C1 receives the request message through port PortID=2. At this time, device C1 is a first-level intermediate device. The addressing information of the request message includes: L3PortID=3, L2PortID=6, L1PortID=4, FL length=3, FL level=1. Device C1 updates L1 PortID from its sending port 4 to its receiving port 2 and updates FL level from 1 to 2. Device C1 sends a request message to device C2 through port PortID=4. Device C2 receives the request message through port PortID=2. At this time, device C2 is a second-level intermediate device. The addressing information of the request message includes: L3 PortID=3, L2PortID=6, L1 PortID=2, FLlength=3, FL level=2. Device C2 updates L2 PortID from its sending port 6 to its receiving port 2 and updates FL level from 2 to 3. Device C2 sends a request message to device C3 through port PortID=6, and device C3 receives the request message through port PortID=2. At this time, device C3 is a third-level intermediate device. The addressing information of the request message includes: L3PortID=3, L2 PortID=2, L1 PortID=2, FL length=3, FL level=3. Device C3 updates its L3 PortID from its sending port 3 to its receiving port 2, and updates its FL level from 3 to 4. Device C3 sends a request message to device B through port PortID=3, and device B receives the request message.

[0103] Table 1

[0104] L3 PortID L2 PortID L1 PortID FL length FL level Messages received by device C1 3 6 4 3 1 Messages received by device C2 3 6 2 3 2 Messages received by device C3 3 2 2 3 3 Message received by device B 2 2 2 3 4

[0105] Similarly, the following example illustrates how device C sends a response message to device A through three devices (represented as device C3, device C2, and device C1), and how each of these three devices updates the addressing information of the received response message and transmits the response message.

[0106] For example, as shown in Table 2 below, device B sends a response message to device C3. Device C3 receives the response message through port PortID=3. At this time, device C3 is a third-level intermediate device. The addressing information of this response message includes: L3PortID=2, L2 PortID=2, L1PortID=2, FL length=3, FL level=3. Device C3 updates L3 PortID from its sending port 2 to its receiving port 3 and updates FL level from 3 to 2. Device C3 sends a response message to device C2 through port PortID=2. Device C2 receives the response message through port PortID=6. At this time, device C2 is a second-level intermediate device. The addressing information of this response message includes: L3 PortID=3, L2PortID=2, L1 PortID=2, FLlength=3, FL level=2. Device C2 updates L2 PortID from its sending port 2 to its receiving port 6 and updates FL level from 2 to 1. Device C2 sends a response message to device C1 through port PortID=2, and device C1 receives the response message through port PortID=4. At this time, device C1 is a first-level intermediate device. The addressing information of the response message includes: L3PortID=3, L2 PortID=6, L1 PortID=2, FL length=3, FL level=1. Device C3 updates its L3 PortID from its sending port 2 to its receiving port 4, and updates its FL level from 1 to 0. Device C1 sends a response message to device A through port PortID=2, and device A receives the response message.

[0107] Table 2

[0108] L3 PortID L2 PortID L1 PortID FL length FL level Messages received by device C3 2 2 2 3 3 Messages received by device C2 3 2 2 3 2 Messages received by device C1 3 6 2 3 1 Message received by device A 3 6 4 3 0

[0109] In the embodiments of this application, the two devices communicate using ports with the same port number. For example, device C1 uses port ID=2 to send a message to or receive a message from device A. Similarly, device C1 uses port ID=4 to send a message to or receive a message from device C2. That is, the order of the sending ports for the entire response signal is the reverse of the order of the sending ports for the request signal. This is equivalent to the entire signal link being used in reverse, and the transmission path of the response signal is the opposite of the transmission path of the request signal.

[0110] It is understandable that the above description uses the forwarding list level in the addressing information to indicate the level of the current device as an example. In practical applications, the forwarding list level can also be used to indicate other levels, as long as the device can determine its position in the forwarding list based on the addressing information. For example, the forwarding list level can also be used to indicate the remaining levels to reach the target device. This application does not impose specific limitations on this.

[0111] Furthermore, the above description of updating the forwarding list level corresponding to the request and response messages is merely exemplary. In practical applications, the method for updating the forwarding list level corresponding to the request and response messages can be consistent. For example, when the target device returns a response message, the level of the next-level device can be the first level, the level of the next-next-level device can be the second level, and so on. In this case, the intermediate device can update the forwarding list level in the response message by incrementing the forwarding list level by 1. As another example, when the source device sends a request message, the level of the next-level device can be the FL length level, the level of the next-next-level device can be the FL length-1 level, and so on. In this case, the intermediate device can update the forwarding list level in the request message by decrementing the forwarding list level by 1. This application does not impose specific limitations on this.

[0112] The following is through Figure 9 Examples are given regarding any device involved in receiving messages in the technical solutions provided in the embodiments of this application. For instance... Figure 9 As shown, the method includes:

[0113] S1. Receive a message, which includes type information Rsp and addressing information. The addressing information includes forwarding list length FL length, forwarding list level FL level (hereinafter FL lev) and F port numbers;

[0114] S2. Determine whether it is an intermediate device based on the addressing information. If not, execute S31; if so, execute S32.

[0115] S31. Determine whether it is the target device. If not, it indicates that it is the source device, and the addressing process ends. If it is, execute S4.

[0116] S4. Determine if the type information Rsp = 0. In this implementation, Rsp = 0 indicates a request message. If not, end; otherwise, execute S5.

[0117] S5. Change FL lev to FL lev-1 to end the addressing process. After the response message is generated, Rsp can be set to 1 to send the response message to the source device step by step;

[0118] S32. Record the FL lev-th port number as the sending port number of the message, and execute S6;

[0119] S6. Update the FL lev-th port number to the port number that will receive the message;

[0120] S7. Determine if the type information Rsp = 0. If yes, execute S81; otherwise, execute S82.

[0121] S81. Update FL level to FL lev+1, then execute S9;

[0122] S82. Update FL lev to FL lev-1, then execute S9;

[0123] S9. Send the updated message from the recorded sending port.

[0124] In this embodiment, a first device receives a first message through a first port. The first addressing information of the first message includes at least one port number in the forwarding list. The first device can update the first addressing information to second addressing information. For example, it can update the second port number of the second port of the first device in the at least one port number of the first addressing information to the first port number of the first port, update the first level indication of the first addressing information to the second level indication, and send a second message including the second addressing information through the second port. In this way, when the target device of the first message receives the message, the addressing information of the message includes the port number of each device in the forwarding path that receives the message. Thus, the target device can obtain the addressing information of the response message based on the addressing information of the message, thereby realizing low-cost and high-efficiency addressing of the message forwarding path.

[0125] In another possible embodiment of this application, a message addressing method is provided, which is based on a forwarding list addressing method, and the message includes addressing information. The relevant content of this method is described in detail below.

[0126] Forwarding list:

[0127] A forwarding list is a list containing multiple elements, each specifying the physical port number from which the packet originated. For example, the first element is the port number used by directly connected devices when forwarding the packet, and so on. Each element in the forwarding list occupies 4 bits, ranging from 0 to 15, with 0 representing unused. The initial value is determined by the originating device. The length of the forwarding list is determined by the originating device, ranging from 0 to 126. When the forwarding list length is N, it means the distance between the device to be accessed and the device itself is N+1. Therefore, a UMI device can access devices at a maximum distance of 127 using the forwarding list. Distance can be considered as the number of hops in the link.

[0128] For example, in Figure 8 In the topology shown, when a message is sent from device A to device B, each link level has an updated forwarding list. The forwarding list carried by the message when it is sent from device A is shown in Table 3.

[0129] Table 3

[0130] L3 PortID L2 PortID L1 PortID 3 6 4

[0131] Addressing information:

[0132] For packets addressed to a forwarding list, the addressing information format is as follows: Figure 7 As shown in Table 4, the descriptions of each domain segment are as follows.

[0133] Table 4

[0134]

[0135] Explanation 1: N = FLOOR((FL Length×4+16) / 32), the length of the addressing information is ((N+1)×4) bytes.

[0136] Note 2: If N equals 0, then M does not exist; if N > 0, M = ((FL Length – 4) MOD 8) × 4.

[0137] FL Level indicates the current level of the device relative to the source device. When a device on the path receives a packet, if the FL Level is 0 or FL Length+1, then this device is the target device for this packet; otherwise, this device is an intermediate device for this packet. Each intermediate device on the path should use the FL Level element of the forwarding list as the sending port number of the packet when forwarding it. The target device does not need to forward the packet again.

[0138] FL Length is the length of the forwarding list.

[0139] When a device on the path receives a message, regardless of whether it is the destination device of the message, it should decide whether to process the message data according to the requirements of the message type.

[0140] After processing the message data, if it is an intermediate device, it will forward the message. Before forwarding, the addressing information needs to be updated according to the following process: record the FL Level element of the forwarding list as the sending port number of the message; rewrite the FL Level element of the forwarding list as the receiving port number of this message; if Rsp in the message header is 0, rewrite the FL Level field as FL Level plus 1, otherwise rewrite the FL Level field as FL Level minus 1; send the updated message out from the previously recorded sending port.

[0141] If the device itself is the target device and the Rsp value in the message header is 0, then simply rewriting the FL Level field to FL Level minus 1 will allow it to use the addressing information of this message as the addressing information of a response message with Rsp of 1. This response message can then be sent out through the port that received the request message. Afterward, this device becomes the source device for the response message. Accordingly, the target device receiving the request message becomes the source device sending the response message. Using this scheme, this conversion from request message reception to response message transmission is simple and easy to implement.

[0142] Furthermore, this message can be a management message (or management data message). This message may also include type information, which can be located in the message header, for example, occupying the 23rd bit of the header. The field corresponding to this type information can be represented as Response(Rsp). The description of this type information is shown in Table 5 below.

[0143] Table 5

[0144]

[0145] The above mainly describes the solutions provided by the embodiments of this application from the perspective of interaction between various devices. It is understood that, as data transmitting and receiving devices, in order to achieve the above functions, they include corresponding hardware structures and / or software modules for performing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0146] This application embodiment can divide each device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the division of functional modules according to each function as an example.

[0147] When using integrated units, Figure 10 A schematic diagram of a message addressing device according to the above embodiments is shown. This device can be an intermediate device or a chip applied to an intermediate device. The device includes: a receiving unit 1001, a processing unit 1002, and a sending unit 1003. It should be understood that any of the above units can be implemented in software, hardware, or a combination of both; this embodiment is not limited in this respect.

[0148] In one possible embodiment, the receiving unit 1001 can be used to support the device in receiving S602 of the above method embodiment; the processing unit 1002 can be used to support the device in executing the steps of determining whether it is a device, updating the first addressing information, and / or other technical processes described herein in the above method embodiment; the sending unit 1003 can be used to support the device in executing S603 of the above method embodiment. All relevant content of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

[0149] Based on hardware implementation, the processing unit 1002 in this application can be the processor of the device, the receiving unit 1001 can be the receiver (or receiving port) of the device, and the transmitting unit 1003 can be the transmitter (or transmitting port). Optionally, the receiver can usually be integrated with the transmitter as a transceiver, and the specific transceiver can also be called a communication interface.

[0150] like Figure 11The diagram shows a schematic of another message addressing device provided in an embodiment of this application. This device can be an intermediate device or a chip applied to an intermediate device. The device includes a communication interface 1011 and a processor 1012. In one possible embodiment, the processor 1012 is used to support the device in performing the steps described in the method embodiments above—determining whether it is a device, updating the first addressing information, and / or other technical processes described herein. Furthermore, the communication interface 1011 can be used to support the device in communication, for example, supporting communication between the device and a source device, a target device, or other intermediate devices. Optionally, the device also includes a memory 1013 for storing programs, instructions, and data required by the device. The processor 1012 implements the above functions by reading and executing programs in the memory 1013.

[0151] In another embodiment of this application, a message addressing device is also provided. The device may be a chip or a device. The device includes a memory and a processor. The memory stores instructions, and the processor executes the instructions in the memory to cause the device to perform the steps of the first device in the above method embodiment.

[0152] In another embodiment of this application, a data transmission system is provided, comprising: a source device, at least one intermediate device, and a target device, wherein the at least one intermediate device is as described above. Figure 10 or Figure 11 The provided apparatus is used to perform the steps of the first device in the method embodiments provided above.

[0153] It is understood that all relevant content of each step involved in the above method embodiments can be referenced in the embodiments of the message addressing device, the chip, and the data transmission system, and will not be repeated here.

[0154] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed.

[0155] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0156] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. This readable storage medium may include various media capable of storing program code, such as a USB flash drive, external hard drive, read-only memory, random access memory, magnetic disk, or optical disk. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product.

[0157] In another embodiment of this application, a readable storage medium is also provided, which stores computer-executable instructions that are executed by a device (which may be a microcontroller, chip, etc.) or a processor when executing the steps of the first device in the above method embodiment.

[0158] In another embodiment of this application, a computer program product is also provided, the computer program product including computer instructions stored in a readable storage medium; at least one processor of the device can read the computer instructions from the readable storage medium, and the at least one processor executes the computer instructions to cause the device to perform the steps of the first device in the above method embodiment.

[0159] Finally, it should be noted that the above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of addressing a message, characterized by, The method comprises: The first device receives a first message through a first port, the first message comprising first addressing information, the first addressing information comprising at least one level of port numbers in a forwarding list, the at least one level of port numbers comprising a level of port numbers corresponding to the first device, the level of port numbers corresponding to the first device comprising a second port number of a second port of the first device; The first device sends a second message through the second port, the second message comprising second addressing information, the second addressing information being updated from the first addressing information, wherein, in the level of port numbers corresponding to the first device, the second port number is updated to a first port number of the first port; The first message further comprises type information, the type information being used to indicate a message type of the first message, the message type being one of a request message or a response message; When the message type of the first message is the request message, the first port number is used to determine a sending port number of a response message corresponding to the first message.

2. The method of claim 1, wherein, The first addressing information or the second addressing information further comprises a forwarding list length, the forwarding list length being used to indicate a number of the at least one port number.

3. The method according to claim 1 or 2, characterized in that, The first addressing information further comprises a first level indication, the first level indication being used to indicate a level in which the first device is located in the forwarding list.

4. The method of claim 3, wherein, The second addressing information further comprises a second level indication, the second level indication being updated from the first level indication.

5. The method of claim 4, wherein, The type information is the request message, and the second level indication is the first level indication plus 1.

6. The method of claim 4, wherein, The type information is the response message, and the second level indication is the first level indication minus 1.

7. The method of claim 3, wherein, The first level indication is greater than 0 and not greater than the forwarding list length, and the first device is an intermediate device.

8. An apparatus for addressing a message, characterized by The apparatus is applied to a first device, and the apparatus comprises: A receiving unit, configured to receive a first message through a first port, the first message comprising first addressing information, the first addressing information comprising at least one level of port numbers in a forwarding list, the at least one level of port numbers comprising a level of port numbers corresponding to the first device, the level of port numbers corresponding to the first device comprising a second port number of a second port of the first device; A sending unit, configured to send a second message through the second port, the second message comprising second addressing information, the second addressing information being updated from the first addressing information, wherein, in the level of port numbers corresponding to the first device, the second port number is updated to a first port number of the first port; The first message further comprises type information, the type information being used to indicate a message type of the first message, the message type being one of a request message or a response message; When the message type of the first message is the request message, the first port number is used to determine a sending port number of a response message corresponding to the first message.

9. The apparatus of claim 8, wherein, The first addressing information or the second addressing information further comprises a forwarding list length, the forwarding list length being used to indicate a number of the at least one port number.

10. The apparatus of claim 8 or 9, wherein, The first addressing information further comprises a first level indication, the first level indication being used to indicate a level where the first device is located in the forwarding list.

11. The apparatus of claim 10, wherein, The second addressing information further comprises a second level indication, the second level indication being updated from the first level indication.

12. The apparatus of claim 11, wherein, The type information is a request message, and the second level indication is the first level indication plus 1.

13. The apparatus of claim 11, wherein, The type information is a response message, and the second level indication is the first level indication minus 1.

14. The apparatus of claim 10, wherein, The first level indication is greater than 0 and is not greater than the forwarding list length, and the first device is an intermediate device.

15. An apparatus for addressing a message, characterized by Comprise: A processing circuit and a transceiver, the processing circuit and the transceiver being used to support the apparatus to perform the packet addressing method as claimed in any one of claims 1-7.

16. A readable storage medium, characterized by, The readable storage medium has instructions stored therein, when the instructions run on a device, make the device perform the packet addressing method as claimed in any one of claims 1-7.

Images