Message addressing method and apparatus, and readable storage medium

Abstract

A message addressing method and apparatus, and a readable storage medium, which relate to the technical field of communications and are used for realizing low-cost and efficient addressing of a message forwarding path. The method comprises: a first device receiving a first message by means of a first port, wherein the first message comprises first addressing information, the first addressing information comprises at least one port number in a forwarding list, and the at least one port number comprises a second port number of a second port of the first device; and the first device sending a second message by means of the second port, wherein the second message comprises second addressing information, the second addressing information is obtained by updating the first addressing information, and the second port number in the second addressing information is updated to a first port number of the first port.

Description

A message addressing method, device and readable storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 21, 2023, with application number 202311563704.5 and application name “A message addressing method, device and readable storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a message addressing method, device and readable storage medium. Background Art

[0003] In high-speed internet networks, after receiving a message, the destination device often needs to send a reply message to the message's source device to confirm successful receipt. Therefore, any device on the network needs to obtain information about the message's path when it receives a message. In some network topologies, the source device and path length of a message received by a device are uncertain, making it impossible for network devices to statically configure the message path. Therefore, a low-cost, efficient addressing method that supports obtaining message forwarding paths is urgently needed.

[0004] Summary of the Invention

[0005] The present application provides a message addressing method, device and readable storage medium, which are used to achieve low-cost and high-efficiency addressing of message forwarding paths.

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

[0007] In a first aspect, a message addressing method is provided, the method comprising: a first device receives a first message through a first port (or called a receiving port), the first device may be an intermediate device that forwards the first message, the first message includes first addressing information, the first addressing information includes at least one port number in a forwarding list, the at least one port number may include the port number of each device in at least one intermediate device, the at least one port number includes the second port number of the second port (or called a sending port) of the first device; the first device sends a second message through the second port, the second message includes second addressing information, the second addressing information is obtained by updating the first addressing information, the second message may be obtained by updating the first message, wherein in the second addressing information, the second port number is updated to the first port number of the first port.

[0008] In the above technical solution, 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 a forwarding list. The first device can update the first addressing information to second addressing information. For example, the first device updates the second port number of the second port of the first device in the at least one port number in the first addressing information to the first port number of the first port, and sends 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. The target device can then obtain the addressing information of the reply message based on the addressing information of the message, thereby achieving low-cost and high-efficiency addressing of the message forwarding path.

[0009] In a possible implementation of the first aspect, the first addressing information or the second addressing information further includes a forwarding list length, where the forwarding list length is used to indicate the number of the at least one port number, or is referred to as being used to indicate the total number of levels of the forwarding list, or is used to indicate 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 level), where the first level indication is used to indicate the level at which the first device is located in the forwarding list. In the above possible implementation, the first device can determine whether the first device is an intermediate device or a target device based on the forwarding list length and the first level indication.

[0010] In a possible implementation of the first aspect, the forwarding list length field may occupy 8 bits, and the first level indication field may also occupy 8 bits. In the above possible implementation, up to 127 levels of forwarding may be supported, thereby meeting the needs of multi-level networking.

[0011] In one possible implementation of the first aspect, the second addressing information further includes a second layer indication, where the second layer indication is an update of the first layer indication. In this possible implementation, each device receiving a message in a message forwarding path can determine the layer of the device in a low-cost, high-efficiency manner.

[0012] In one possible implementation of the first aspect, the first message further includes type information, where the type information is used to indicate a message type of the first message. The message type is one of the following: a request message or a response message. For example, a value of 0 for the type information indicates a request message, and a value of 1 for the type information indicates a response message. This possible implementation provides a simple and effective method for indicating the message type.

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

[0014] In a possible implementation of the first aspect, 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), and 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 may determine that it is an intermediate device, and thus update the first addressing information of the first message before sending it.

[0015] In a second aspect, a message addressing device is provided, which is applied to a first device, and the first device can be an intermediate device for forwarding the first message. The device includes: a receiving unit, used to receive 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 can include the port number of each device in at least one intermediate device, and the at least one port number includes the second port number of the second port of the first device; a sending unit, used to send a second message through a second port, the second message including second addressing information, the second addressing information is updated from the first addressing information, the second message can be 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.

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

[0017] In a possible implementation manner of the second aspect, the first addressing information further includes a first layer indication, where the first layer indication is used to indicate a layer at which the first device is located in the forwarding list.

[0018] In a possible implementation manner of the second aspect, the second addressing information further includes a second-level indication, where the second-level indication is obtained by updating the first-level indication.

[0019] In a possible implementation manner of the second aspect, the first message further includes type information, where the type information is used to indicate a message type of the first message, and the message type is one of the following: a request message or a response message.

[0020] In a possible implementation manner of the second aspect, the type information is a request message, and the second-level indication is the first-level indication plus 1.

[0021] In a possible implementation manner of the second aspect, the type information is a response message, and the second-level indication is the first-level indication minus 1.

[0022] In a possible implementation manner of the second aspect, the first-level indication is greater than 0 and not greater than the forwarding list length, and the first device is an intermediate device.

[0023] In a third aspect, a message addressing device is provided, which may be a device or a chip applied to a device, and the device includes: a processing circuit and a transceiver, and the processing circuit and the transceiver are used to support the device in executing the message addressing method provided by the first aspect or any possible implementation of the first aspect.

[0024] In a fourth aspect, a message addressing device is provided, which may be a device or a chip applied to a device. The device includes: a processor and a memory, wherein instructions are stored in the memory. When the processor executes the instructions in the memory, the device executes the message addressing method provided by the first aspect or any possible implementation of the first aspect.

[0025] In another aspect of the present application, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer program or instruction is executed, the addressing method of the message provided by the first aspect or any possible implementation of the first aspect is implemented.

[0026] In another aspect of the present application, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute the message addressing method provided in the first aspect or any possible implementation of the first aspect.

[0027] It can be understood that the beneficial effects that can be achieved by any of the message addressing devices, computer-readable storage media and computer program products provided above can correspond to the beneficial effects of the message addressing method provided above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG1 is a schematic structural diagram of a data transmission system provided in an embodiment of the present application;

[0029] FIG2 is a schematic diagram of the structure of another data transmission system provided in an embodiment of the present application;

[0030] FIG3 is a schematic diagram of basic components of an electronic device provided in an embodiment of the present application;

[0031] FIG4 is a schematic structural diagram of a multi-device networking data transmission system provided in an embodiment of the present application;

[0032] FIG5 is a schematic diagram of routing information in a message provided in an embodiment of the present application;

[0033] FIG6 is a flow chart of a message addressing method provided in an embodiment of the present application;

[0034] FIG7 is a schematic diagram of addressing information in a message provided in an embodiment of the present application;

[0035] FIG8 is a schematic diagram of a message transmission between devices provided in an embodiment of the present application;

[0036] FIG9 is a flow chart of another message addressing method provided in an embodiment of the present application;

[0037] FIG10 is a schematic structural diagram of a message addressing device provided in an embodiment of the present application;

[0038] FIG11 is a schematic structural diagram of another message addressing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers 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 represent: 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.

[0040] 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 terms such as "first" and "second" do not limit the quantity or order of execution. The term "coupled" is used to indicate an electrical connection, including direct connection via wires or connectors or indirect connection via other devices. Therefore, "coupling" should be considered a broadly defined electronic communication connection.

[0041] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0042] The technical solution provided in this application can be applied to a data transmission system, which may include multiple transmission devices, which may be devices, chips applied to devices, or interface devices, etc. In this data transmission system, the multiple transmission devices may be directly connected or indirectly connected. In this application, the multiple transmission devices may transmit signals (for example, sending and receiving) by wired means or by wireless means (for example, sending and receiving). In addition, when transmitting signals between the multiple transmission devices, the signals may be transmitted directly or through an interface device (or receiving device), and then transmitted to the processing units inside the respective devices through a bus.

[0043] When the transmission device is a chip in a device, the chips in the data transmission system can be interconnected via wired or wireless means. The chip can be a chip in the device, a chip in a docking station, or a chip in an adapter, etc. The docking station can be connected to a gigabit network port, a video graphics array (VGA), an HDMI port, a flash memory (TF) card, a secure digital (SD) card, a charging port, and a USB port, etc.

[0044] Optionally, when the transmission device is a chip, the chip may further include an interface module, that is, the present application may be applied to an interface module for interconnecting chips. The interface module may be understood as an intellectual property (IP) module integrated inside the chip. Alternatively, the interface module may also be sold separately as an IP module. For example, the chip may be a system on chip (SoC), a central processing unit (CPU), or a graphics processing unit (GPU), etc., and the interface module may be an interface module in the SoC, CPU, or GPU, etc. Optionally, the interface module may be a transmitting circuit and / or a receiving circuit.

[0045] The structure of the data transmission system is described below by taking the data transmission system including multiple devices as an example.

[0046] Figure 1 is a structural diagram of a data transmission system provided in an embodiment of the present application. The data transmission system includes multiple devices. Taking the multiple devices including a source device (or called a starting device) 110, at least one intermediate device 120 and a host device (or called a target device) 130 as an example, the source device 110 and the at least one intermediate device 120, and the at least one intermediate device 120 and the host device 130 can be connected in a wired or wireless manner, for example, by a cable connection. Among them, signals can be transmitted between the source device 110 and the at least one intermediate device 120, and between the at least one intermediate device 120 and the host device 130, for example, audio and video data transmission or charging signal transmission. Optionally, the at least one intermediate device 120 may include a routing device.

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

[0048] Furthermore, the at least one intermediate device 120 may include multiple intermediate devices 120, and the multiple intermediate devices 120 may be connected according to a network topology. For example, the source device 110, the multiple intermediate devices 120, and the sink device 130 may be connected according to a mesh topology, such as a ring topology or a star topology, which is not specifically limited in this embodiment of the present application.

[0049] Optionally, taking the at least one intermediate device 120 including an 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 host device 130 may include interface D. Interface A of the source device 110 and interface B of the intermediate device 120 are connected via a cable, and interface C of the intermediate device 120 and interface D of the host device 130 may also be connected via a cable.

[0050] Figure 2 is a schematic diagram of the structure of another data transmission system provided in an embodiment of the present application. The data transmission system includes multiple devices connected by wired or wireless means, and signals can be transmitted between the multiple devices, such as the transmission of audio and video data or the transmission of charging signals. For example, the multiple devices may include a display 210, a set-top box 220, an audio player (e.g., MP3) 230 and a router 240. The display 210, the set-top box 220 and the audio player 230 can all be connected to the router 240 via a cable, and the transmission of audio and video data or the transmission of charging signals can be performed through the router 240. In one example, the set-top box 220 can transmit audio and video data to the display 210 through the router 240, and the set-top box 220 can also transmit audio data to the audio player 230 through the router 240. In addition, there may be two devices connected to each other in 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.

[0051] Optionally, each of the multiple devices may include one or more interfaces, and the multiple devices may be connected via interfaces. For example, the display 210, the set-top box 220, and the audio player 230 may each include an interface, and 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 via a cable, the interface of the set-top box 220 is connected to the second interface of the router 240 via a cable, and the interface of the audio player 230 is connected to the third interface of the router 240 via a cable.

[0052] The devices in the above-mentioned system with data transmission capabilities can be referred to as electronic devices. The electronic devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted. The electronic devices can also be deployed on water (such as ships) or in the air (such as aircraft, balloons, and satellites), and can be applied in different scenarios. Exemplarily, the electronic device may include, but is not limited to: a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a camera, a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), an audio device, an audio and video player, a set-top box, a game console, a printer, a mouse, a keyboard, a vehicle-mounted device (such as a car, a bicycle, an electric car, an airplane, a ship, a train, a high-speed train, etc.), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a smart home device (such as a refrigerator, a television, an air conditioner, an electric meter, etc.), an intelligent robot, a workshop device, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a smart home. Wireless terminals in homes, flying devices (e.g., smart 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.

[0053] In the present application, the interface specifications used for signal transmission between devices in a data transmission system may include, but are not limited to: universal serial bus (USB) interface specifications, high definition multimedia interface (HDMI) interface specifications, display port (DP) interface specifications, unified multimedia interconnection (UMI) interface specifications, and peripheral component interconnect express (PCI-Express) interface specifications, etc. Accordingly, the interface may be HDMI, miniHDMI, micro HDMI, type-A interface, type-B interface, Micro-B, and type-C interface, etc.

[0054] For example, in the above example, the interface connection method between the set-top box and the display, or the interface connection method between the game console and the display can be connected through a USB cable, and the interface standard followed is the USB interface specification, or the connection method can be connected through an HDMI cable, and the interface standard followed is the HDMI interface specification.

[0055] It will be understood that the interface specifications used for signal transmission between the above-mentioned devices are merely exemplary. In actual applications, the interface specifications may also include other or any interface specifications that may appear in the future, such as a unified media interconnection (UMI) interface, etc., and the embodiments of the present application are not specifically limited to this.

[0056] In this application, when the transmission device is an electronic device, FIG3 shows a schematic diagram of the basic components of the electronic device. The electronic device includes an interface chip 300 (e.g., a UMI interface), which includes one or more adapters 301, a management and control adapter 302, and one or more ports 303. Alternatively, when the electronic device is a routing device, the interface chip 300 includes only one or more ports 303. Each of the one or more adapters 301 can be coupled to an external component of the interface chip 300. The management and control adapter 302 can be coupled to a component outside the interface chip 300 for management and control. The port 303 can be coupled to a connector 304 of the electronic device, which is used to couple to external devices of the electronic device. The one or more adapters 301 can include a transmitting adapter and / or a receiving adapter. For example, when the adapter 301 is used to adapt audio and video formats, the adapter 301 can be a transmitting adapter or a receiving adapter. When the adapter 301 is used to adapt a third-party protocol, the adapter 301 can be a third-party protocol adapter.

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

[0058] The basic components of different electronic devices can be combined to form a variety of different device types. For example, the electronic device is a source device that includes at least one downstream port and at least one audio and video transmitter adapter; or, the electronic device is a source device that includes at least one upstream port and at least one audio and video receiver adapter; or, the electronic device is a docking station device that includes at least one upstream port, at least one audio and video receiver adapter, and at least one traditional audio and video interface; or, the electronic device is a routing device that includes at least one downstream port and at least one upstream port, but does not have an audio and video transmitter adapter or an audio and video receiver adapter; or, the electronic device is a composite device that includes both an upstream port and a downstream port, and includes a transmitter adapter and an audio and video receiver adapter.

[0059] The above interface chip can also be called a switch.

[0060] FIG4 is a schematic diagram of a multi-device networked data transmission system according to an embodiment of the present application. The multi-device system includes multiple source devices (e.g., source device 1 and source device 2), at least one routing device (e.g., routing device 1), and multiple sink devices (e.g., sink device 1, sink device 2, and sink device 3).

[0061] For example, in the case where source device 1 and source device 2 include downlink ports, and sink devices 1 through 3 include uplink ports, data from source device 1 can be transmitted to sink devices 1 and 2 via routing device 1, and data from source device 2 can be transmitted to sink device 3 via routing device 1. For example, downlink port 405 of source device 1 transmits data 1 to uplink port 406 of routing device 1. Uplink port 406 of routing device 1 transmits a portion of data 1, data 11, to uplink port 408 of sink device 1 via downlink port 407 of routing device 1. Sink device 1 processes data 11. Uplink port 406 of routing device 1 transmits another portion of data 1, data 12, to uplink port 410 of sink device 2 via downlink port 409 of routing device 1. Sink device 2 processes data 12. Downlink port 411 of source device 2 sends data 2 to uplink port 412 of routing device 1. Uplink port 412 of routing device 1 sends data 2 to uplink port 414 of sink device 3 through downlink port 413 of routing device 1. Sink device 3 processes data 2.

[0062] Optionally, source device 1 and source device 2 may further include upstream ports, and sink devices 1 through 3 may further include downstream ports. That is, source device 1 and source device 2, as well as sink devices 1 through 3, may also be composite devices. For example, if source device 1 is a speaker and sink device 2 is a display, when the speaker sends audio or video data to the display, the data can be sent via the speaker's downstream port to the display's upstream port, with routing device 1 intervening. The display can also transmit data back via its downstream port, with routing device 1 returning the data to the speaker's upstream port. The upstream ports of source device 1 and source device 2, and the downstream ports of sink devices 1 through 3, are not shown in the figure.

[0063] It will be understood that the structures of the source device, routing device, and sink device shown in the above figures are merely exemplary. In actual applications, the above devices may include more or fewer components than shown in the figures, or combine certain components, or arrange the components differently. The above examples do not limit the embodiments of the present application.

[0064] In a high-speed interconnect interface, after receiving a message, the target device often needs to reply with a response message to the source device of the message to confirm that the message has been successfully received. Therefore, when any device in the network receives a message, it needs to obtain the message's path information. In some network topologies (for example, a ring topology), any two devices can send messages to each other, and the source device and path length of the message received by a certain device are uncertain. Therefore, the devices in the network cannot statically configure the message path. In addition, there may be loops in the network. If the path of the response message is obtained by querying the locally stored information, it may cause the problem of inconsistent paths between the request message and the response message.

[0065] In the related art, as shown in Figure 5, the routing information in the message usually includes the following fields: link count total (LCT), link count remaining (LCR), and relative address (RA). Among them, the length of LCT is 4 bits and refers to the total number of links passed from the source device of the message to the target device. The length of LCR is 4 bits and refers to the number of links remaining for the message to reach the target device. It is initialized to the LCT value by the source device. Along the transmission path of the message, each device subtracts the LCR value by one before forwarding the message. 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 is sent from each intermediate device. It is initialized by the source device of the message and modified by the intermediate device. Each intermediate device uses RA[0] as the port number from which the message is sent.

[0066] Specifically, the method for addressing the source device, intermediate device, and destination device of the message based on the above routing information is:

[0067] Source device: Step 1. Initialize LCT, LCR, and RA; Step 2. Decrease LCR by 1 and send the message through the DPTX port;

[0068] Intermediate device: Step 1. Record the sending port of the message as RA[0]; Step 2. Update RA; Step 3. Decrease 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:

[0069] Destination device: If LCR equals 0 upon receiving a message, the current device is the destination device of the message. After all intermediate devices along the path have updated their RA, it is now the path to the source device of the message. The destination device, acting as the source device of the reply message, generates routing information for the reply message through the following steps: Step 1: Assign both LCR and LCT to the LCT in the received message; Step 2: Assign RA to the RA in the received message.

[0070] In the above-mentioned scheme for message addressing based on routing information shown in Figure 5, the length of LCT and LCR is 4 bits, and a maximum of 16 levels of links can be addressed, which cannot meet the needs of networking at more levels (for example, 127 levels). 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.

[0071] Based on this, an embodiment of the present application provides a message addressing method, in which a message includes addressing information, and the addressing information includes at least one port number in a forwarding list. After a source device sends a message, each intermediate device that receives 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. In this way, when the target device of the 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, so that the target device can obtain the addressing information of the reply message based on the addressing information of the message, thereby achieving low-cost and high-efficiency addressing of the message forwarding path.

[0072] FIG6 is a flow chart of a message addressing method provided in an embodiment of the present application. The method can be applied to the data transmission system provided above, and the method includes the following steps.

[0073] S601: A source device sends a first message, where the first message includes first addressing information, and the first addressing information includes at least one port number in a forwarding list.

[0074] The forwarding path corresponding to the forwarding list of the first message may include at least one device, and the at least one device may be at least one intermediate device, or at least one first-level intermediate device. The at least one port number in the first addressing information may include the port number of each device in 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 the port number is the port number of the one device; when the at least one device includes multiple devices, the at least one device includes a port number for each of the multiple devices.

[0075] Exemplarily, taking the example that the at least one device includes F devices (i.e., corresponding to F layers or levels), the at least one port number includes F port numbers, and the F port numbers can be used to indicate the port numbers of each layer in the F layers. For example, as shown in Figure 7, the port numbers of each layer in the F layers can be represented in sequence as L1 PortID, L2 PortID, L3 PortID, ..., LF PortID, where L in L1 to LF represents Level. Among them, 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 layer in the at least one port number to send the first message. The numbers 0 to 31 in Figure 7 represent 32 bits.

[0076] Furthermore, as shown in FIG7 , the first addressing information further includes: a forwarding list length (FL length) and / or a first level indication. The first level indication may also be referred to as a forwarding list level (FL level). The order and bit positions occupied by the F port numbers, forwarding list lengths, and forwarding list levels shown in FIG7 in the first addressing information are merely exemplary and do not limit the embodiments of the present application.

[0077] The forwarding list length is used to indicate the number of the at least one port number, or is called the total number of levels of 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 of F levels, the forwarding list length is used to indicate that the number of the at least one port number is F.

[0078] In addition, the first level indication (or the forwarding list level) is used to indicate the level of the current device in the forwarding list. For example, the level indication is used to indicate the level of the current device when the source device is used as the origin. The current device may refer to the device currently receiving the message. The forwarding list level in the first message sent by the source device may be used to indicate the level of the intermediate device that receives the first message sent by the source device.

[0079] Optionally, the domain segment where the first-level indication is located can occupy multiple bits, and the domain segment where the forwarding list length is located can also occupy multiple bits. The number of these multiple bits can be set according to actual needs, and the embodiments of the present application do not impose specific restrictions on this.

[0080] In one example, the forwarding list length field may occupy 8 bits, i.e., 8 bits are used to transmit the forwarding list length. For example, to support up to 127 levels of forwarding, the forwarding list length may be represented by 7 bits, with a corresponding value range of 1 to 127, and the high-order bit may be a reserved bit; or, to support up to 255 levels of forwarding, the forwarding list length may be represented by 8 bits, with a corresponding value range of 1 to 255; or, to support 63 levels of forwarding, the forwarding list length may be represented by 8 bits, and the remaining high-order bits may be reserved bits.

[0081] In one example, the number of bits occupied by the first-level indication field and the number of bits occupied by the forwarding list length field may be the same. For example, the first-level indication field may occupy 8 bits, corresponding to a maximum value of 127, and the forwarding list length field may also occupy 8 bits, corresponding to a maximum value of 127-1.

[0082] Optionally, the total number of bits occupied by the addressing information may be required to be an integer multiple of W bytes, where W is a positive integer, such as 4. When the total number of bits actually occupied by the addressing information is less than an integer multiple of W bytes, the addressing information may be padded to an integer multiple of W bytes, i.e., the addressing information may further include padding data. Exemplarily, the length of the padding data may be 0 to 28 bits.

[0083] Furthermore, the first message may further include type information, where the type information may be used to indicate a message type of the message, where the message type is one of the following: a request message or a response message. Exemplarily, the type information may occupy one bit. When the value of the one bit is 0, the type information may be used to indicate a request message. When the value of the one bit is 1, the type information may be used to indicate a response message.

[0084] It is understood that the above description uses the example that the type information occupies 1 bit, and the value of this 1 bit is 0 to indicate a request message, and the value of this 1 bit is 1 to indicate a response message. In actual applications, the value of this 1 bit can also be used to indicate a request message, and the value of this 1 bit can be used to indicate a response message, or the type information can also occupy multiple bits, etc. The above example does not limit the embodiments of the present application. The embodiments of the present application do not specifically limit the number of bits occupied by the type information and the meaning indicated by the values ​​of the corresponding bits.

[0085] Optionally, the first message may be a management message or a service message, and the embodiment of the present application does not impose any specific restrictions on this.

[0086] S602: A first device receives a first message through a first port. The first message includes first addressing information. The first addressing information includes at least one port number in a forwarding list. The at least one port number includes a second port number of a second port of the first device. The second port is the current sending port of the first device.

[0087] The first message received by the first device may be sent by the source device or by an intermediate device at the previous level of the first 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 intermediate device at the previous level of the first 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. FIG6 illustrates the first message received by the first device as sent by the source device.

[0088] In some possible embodiments, for any device among the at least one device, 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, and the updated first addressing information can be called the second addressing information. The first message after the first addressing information is updated can be called the second message, that is, the second message includes the second addressing information.

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

[0090] Optionally, the first device may further 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, i.e., the second-level indication is an update of 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.

[0091] In one possible embodiment, for any device in the at least one device in the forwarding path of the first message, taking the i-th level device as an example, upon receiving the first message, the i-th level device may 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 may record the i-th level port number of the at least one port number, update the first addressing information as described above, and then execute step S603. If it is determined to be a target device, the steps corresponding to the target device described below are executed.

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

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

[0094] 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 may send a second message through the second port, where 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.

[0095] It can be understood that the specific structure of the second message may be similar to the specific structure 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. The embodiments of the present application will not go into details about this.

[0096] S604: The second device receives the second message. The second device can be the target device or an intermediate device between the first and target devices. If the second device is an intermediate device between the first and target devices, the second device updates the addressing information according to the method described in steps S602-S603. Figure 6 illustrates this using the second device as the target device as an example.

[0097] In a 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 indication in the second message is equal to the forwarding list length + 1 (i.e., FL level = FL length + 1), the target device can determine that it is 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 indication in the second addressing information, and determine the second addressing information after subtracting 1 as the addressing information of the response message, and 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 indication in the second message is equal to 0, the target device can determine that it is the source device of the response message, and the process ends at this time.

[0098] It can be understood that when the target device sends the above-mentioned response message, the target device can be the source device of the response message, the response device can serve as the first message in the above-mentioned S601, and the response message serving as the first message can be sent through the method provided above, and the embodiments of the present application will not be repeated here.

[0099] For ease of understanding, the following example illustrates the process of device A sending a request message to device B via three devices (denoted as device C1, device C2, and device C3). The process of each of these three devices updating the addressing information of the request message it receives and transmitting the request message is explained. Figure 8 shows a schematic diagram of device A sending a request message to device B via devices C1, C2, and C3, sequentially. This is illustrated using the example of a network topology where these devices also include other devices. The numbers in the small boxes within each device in the figure represent the port numbers corresponding to the ports of that device.

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

[0101] Table 1

[0102] Similarly, the following takes the example of device C sending a response message to device A through three devices (represented as device C3, device C2 and device C1) to illustrate the process of each of the three devices updating the addressing information of the response message it receives and transmitting the response message.

[0103] For example, as shown in Table 2 below, device B sends a response message to device C3, which receives the response message through port ID=3. In this case, device C3 is a third-level intermediate device. The addressing information of the response message includes: L3 Port ID=2, L2 Port ID=2, L1 Port ID=2, FL length=3, and FL level=3. Device C3 updates its L3 Port ID from its sending port 2 to its receiving port 3, and updates its FL level from 3 to 2. Device C3 sends a response message to device C2 through port ID=2, which receives the response message through port ID=6. In this case, device C2 is a second-level intermediate device. The addressing information of the response message includes: L3 Port ID=3, L2 Port ID=2, L1 Port ID=2, FL length=3, and FL level=2. Device C2 updates its L2 Port ID from its sending port 2 to its receiving port 6, and updates its FL level from 2 to 1. Device C2 sends a response message to device C1 via port ID 2. Device C1 receives the response message via port ID 4. Device C1 is a first-level intermediate device. The addressing information in the response message includes: L3 Port ID 3, L2 Port ID 6, L1 Port ID 2, FL length 3, and FL level 1. Device C3 updates its L3 Port ID from its sending port 2 to its receiving port 4 and its FL level from 1 to 0. Device C1 sends a response message to device A via port ID 2, and device A receives the response message.

[0104] Table 2

[0105] In the embodiments of the present application, two devices communicate using ports with the same port number. For example, device C1 uses port ID = 2 to send messages to device A or receive messages from device A. For another example, device C1 uses port ID = 4 to send messages to device C2 or receive messages from device C2. That is, the order of ports used to send the response signal is opposite to the order of ports used to send the request signal. This is equivalent to the entire signal chain being used in reverse, with the response signal's transmission path being the opposite of the request signal's transmission path.

[0106] It can be understood that the above is explained by taking the forwarding list level in the addressing information as an example to indicate the level of the current device. In actual applications, the forwarding list level can also be used to indicate other levels. It is only necessary to ensure that 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, etc. The embodiments of the present application do not impose specific restrictions on this.

[0107] In addition, the above description of updating the forwarding list level corresponding to the request message and the response message is only exemplary. In actual applications, the method of updating the forwarding list level corresponding to the request message and the response message may also be consistent. For example, when the target device returns a response message, the level of the target device's next-level device may be the first level, the level of the next-level device may be the second level, and so on; at this time, the intermediate device may update the forwarding list level in the response message by adding 1 to the forwarding list level. For another example, when the source device sends a request message, the level of the source device's next-level device may be the FL length level, the level of the next-level device may be the FL length-1 level, and so on; at this time, the intermediate device may update the forwarding list level in the request message by subtracting 1 from the forwarding list level. The embodiments of the present application do not impose specific restrictions on this.

[0108] The following uses FIG9 to illustrate the relevant content of any device receiving a message involved in the technical solution provided in the embodiment of the present application. As shown in FIG9, the method includes:

[0109] S1 receives a message, which includes type information Rsp and addressing information, the addressing information includes the forwarding list length FL length, the forwarding list level FL level (hereinafter FL lev) and F port numbers;

[0110] S2 determines whether it is an intermediate device based on the addressing information, if not, execute S31, if so, execute S32;

[0111] S31 determines whether it is the target device. If not, it indicates that it is the source device, then the addressing process ends. If so, execute S4;

[0112] S4 determines whether the type information Rsp = 0, in this implementation method, Rsp = 0 indicates a request message, if not, end, if so, execute S5;

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

[0114] S32 records the first FL lev port number as the sending port number of the message, execute S6;

[0115] S6. Update the FL lev port number to the port number that receives the message;

[0116] S7. Determine whether the type information Rsp = 0, if so, execute S81, if not, execute S82;

[0117] S81. Update FL level to FL lev+1 and execute S9.

[0118] S82. Update FL lev to FL lev-1 and execute S9;

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

[0120] In an embodiment of the present application, a first device receives a first message through a first port, and the first addressing information of the first message includes at least one port number in a forwarding list. The first device can update the first addressing information to second addressing information, for example, updating 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, updating the first level indication of the first addressing information to the second level indication, and sending 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, so that the target device can obtain the addressing information of the reply message based on the addressing information of the message, thereby realizing low-cost and high-efficiency addressing of the message forwarding path.

[0121] In another possible embodiment of the present application, a message addressing method is provided, wherein the message includes addressing information based on a forwarding list. The relevant contents of the method are described in detail below.

[0122] Forwarding list:

[0123] A forwarding list is a list containing multiple elements, each of which specifies the physical port number from which the message is sent from each device. For example, the first element is the port number used by the device directly connected to this device to forward this message, and so on. Each element of the forwarding list occupies 4 bits, ranging from 0 to 15, with 0 representing unused, and the initial value is determined by the starting device. The length of the forwarding list is determined by the starting device and ranges from 0 to 126. When the forwarding list length is N, it means that the distance between the device to be accessed and itself is N+1. Therefore, a UMI device can access a device that is at most 127 away from itself through the forwarding list. Distance can be considered to represent the number of hops in the link.

[0124] For example, in the topology shown in Figure 8, 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.

[0125] Table 3

[0126] Addressing information:

[0127] The addressing information format of the message with forwarding list addressing mode is shown in Figure 7, and the description of each field segment is shown in Table 4 below.

[0128] Table 4

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

[0130] Note 2: If N is 0, M does not exist. If N > 0, M = ((FL Length – 4) MOD 8) × 4.

[0131] The FL Level indicates the layer at which the current device resides, with the source device as the origin. When a device along the path receives a packet, if the FL Level is 0 or FL Length + 1, it is the destination device for the packet; otherwise, it is an intermediate device. When forwarding the packet, each intermediate device along the path uses the FL Level element in the forwarding list as the sending port number. The destination device does not need to forward the packet.

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

[0133] When each device on the path receives a message, regardless of whether it is the target device of the message, it should decide whether to process the message data based on the requirements of the message type.

[0134] After processing the message data, if it is an intermediate device, it will forward it. Before forwarding, it needs to update the addressing information 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 to the port number that receives this message; if the Rsp in the message header is 0, rewrite the FL Level field to FL Level plus 1, otherwise rewrite the FL Level field to FL Level minus 1; send the updated message from the previously recorded sending port.

[0135] If the device is the target and the Rsp field in the message header is 0, it simply rewrites the FL Level field to FL Level minus 1. This allows the addressing information in this message to be used as the addressing information for a response message with Rsp set to 1. The response message is then sent out through the port that received the request message. This device then becomes the source of the response message. This transition from the target device receiving the request message to the source device sending the response message is simple and easy to implement.

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

[0137] Table 5

[0138] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between various devices. It is understandable that, as a data sending device and a data receiving device, in order to realize the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0139] In the embodiment of the present application, each device can be divided into functional modules according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. The following is an example of dividing each functional module according to each function.

[0140] In the case of an integrated unit, Figure 10 shows a schematic diagram of the structure of a message addressing device involved in the above embodiment. The device can be an intermediate device or a chip used in an intermediate device, and 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, and this embodiment is not limited to this.

[0141] In one possible embodiment, the receiving unit 1001 may be configured to support the apparatus in receiving S602 of the above-described method embodiment; the processing unit 1002 may be configured to support the apparatus in executing the step of determining whether the apparatus is a device, the step of updating the first addressing information, and / or other technical processes described herein in the above-described method embodiment; and the sending unit 1003 may be configured to support the apparatus in executing S603 of the above-described method embodiment. All relevant content of each step involved in the above-described method embodiment can be referenced in the functional description of the corresponding functional module and will not be further elaborated herein in this embodiment of the present application.

[0142] Based on the 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 sending unit 1003 can be the transmitter (or transmitting port). Optionally, the receiver can be integrated with the transmitter to serve as a transceiver, and the specific transceiver can also be called a communication interface.

[0143] As shown in Figure 11, a structural diagram of another message addressing device provided in an embodiment of the present application is provided. The device can be an intermediate device, or a chip applied to an intermediate device, and the device includes: a communication interface 1011 and a processor 1012. In a possible embodiment, the processor 1012 is used to support the device in executing the step of determining whether it is a device in the above-mentioned method embodiment, the step of updating the first addressing information, and / or other technical processes described herein. In addition, the communication interface 1011 can be used to support the device to communicate, for example, to support the device to communicate with a source device, a target device or other intermediate devices. Optionally, the device also includes a memory 1013 for storing programs, instructions, data, etc. required by the device, and the processor 1012 implements the above functions by reading and executing the programs in the memory 1013.

[0144] In another embodiment of the present application, a message addressing device is also provided. The device can be a chip or a device. The device includes a memory and a processor. The memory stores instructions. The processor runs the instructions in the memory, so that the device executes the steps of the first device in the above method embodiment.

[0145] In another embodiment of the present application, a data transmission system is provided, which includes: a source device, at least one intermediate device and a target device, wherein the at least one intermediate device is the apparatus provided in FIG. 10 or FIG. 11 above, and is used to execute the steps of the first device in the method embodiment provided above.

[0146] It can be understood that all relevant contents of each step involved in the above method embodiment can be referred to the embodiment of the addressing device of the message, the embodiment of the chip and the embodiment of the data transmission system, and the embodiments of the present application will not be repeated here.

[0147] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is merely a logical functional division. In actual implementation, other division methods may be used, such as combining or integrating multiple units or components into another device, or ignoring or not implementing certain features.

[0148] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0149] 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. The readable storage medium may include: a USB flash drive, a mobile hard drive, a read-only memory, a random access memory, a magnetic disk, or an optical disk, etc., which can store program code. Based on this understanding, the technical solution of the embodiment of the present application, 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.

[0150] In another embodiment of the present application, a readable storage medium is also provided, which stores computer execution instructions. When a device (which can be a single-chip microcomputer, chip, etc.) or a processor executes the steps of the first device in the above method embodiment.

[0151] In another embodiment of the present application, a computer program product is also provided, which includes 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 at least one processor executes the computer instructions so that the device performs the steps of the first device in the above method embodiment.

[0152] 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 changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A message addressing method, characterized in that: The method comprises: The first device receives a first message through a first port, the first message includes first addressing information, the first addressing information includes at least one port number in a forwarding list, and the at least one port number includes 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 includes second addressing information, the second addressing information is updated based on the first addressing information, wherein the second port number is updated to the first port number of the first port.

2. The method according to claim 1, characterized in that The first addressing information or the second addressing information further includes a forwarding list length, where the forwarding list length is used to indicate the 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 includes a first level indication, where the first level indication is used to indicate the level at which the first device is located in the forwarding list.

4. The method according to any one of claims 1 to 3, characterized in that: The second addressing information further includes a second layer indication, where the second layer indication is obtained by updating the first layer indication.

5. The method according to any one of claims 1 to 4, characterized in that: The first message also includes type information, where the type information is used to indicate a message type of the first message, and the message type is one of the following: a request message or a response message.

6. The method according to claim 4 or 5, characterized in that: The type information is a request message, and the second level indication is the first level indication plus 1.

7. The method according to claim 4 or 5, characterized in that: The type information is a response message, and the second layer indication is the first layer indication minus 1.

8. The method according to any one of claims 3 to 7, characterized in that: The first level indication is greater than 0 and not greater than the forwarding list length, and the first device is an intermediate device.

9. A message addressing device, characterized in that: Applied in a first device, the apparatus comprises: a receiving unit, configured to receive a first message through a first port, wherein the first message includes first addressing information, the first addressing information includes at least one port number in a forwarding list, and the at least one port number includes a second port number of a second port of the first device; A sending unit is used to send a second message through the second port, the second message includes second addressing information, the second addressing information is updated by the first addressing information, wherein the second port number is updated to the first port number of the first port.

10. The device according to claim 9, characterized in that The first addressing information or the second addressing information further includes a forwarding list length, where the forwarding list length is used to indicate the number of the at least one port number.

11. The device according to claim 9 or 10, characterized in that The first addressing information further includes a first level indication, where the first level indication is used to indicate the level at which the first device is located in the forwarding list.

12. The device according to any one of claims 9 to 11, characterized in that: The second addressing information further includes a second layer indication, where the second layer indication is obtained by updating the first layer indication.

13. The device according to any one of claims 9 to 12, characterized in that: The first message also includes type information, where the type information is used to indicate a message type of the first message, and the message type is one of the following: a request message or a response message.

14. The device according to claim 12 or 13, characterized in that The type information is a request message, and the second level indication is the first level indication plus 1.

15. The device according to claim 12 or 13, characterized in that The type information is a response message, and the second layer indication is the first layer indication minus 1.

16. The device according to any one of claims 11 to 15, characterized in that: The first level indication is greater than 0 and not greater than the forwarding list length, and the first device is an intermediate device.

17. A message addressing device, characterized in that: include: A processing circuit and a transceiver, wherein the processing circuit and the transceiver are used to support the device to execute the message addressing method as described in any one of claims 1-8.

18. A readable storage medium, characterized in that: The readable storage medium stores instructions, and when the instructions are executed on a device, the device executes the message addressing method according to any one of claims 1 to 8.

Images