A communication method and apparatus

By establishing a logical transmission channel in the Internet Protocol network and using QoS parameters and the SLNA and L2ID of neighboring nodes for network layer communication, the problem that traditional IP packets cannot provide quality of service guarantees is solved, and the reliability and reachability of data transmission are achieved.

CN119547385BActive Publication Date: 2026-11-10HUAWEI TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202280097438.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-07-29
Publication Date
2026-11-10
Estimated Expiration
2042-07-29

AI Technical Summary

Technical Problem

In traditional Internet Protocol (IP) networks, when IP packets are forwarded based on ARP entries, Quality of Service (QoS) cannot be guaranteed, leading to reliability and reachability issues in packet transmission.

Method used

By acquiring the logical channel information corresponding to the preset QoS parameters, a logical transmission channel is established between the first node and the neighboring nodes. The logical channel information, the SLNA and L2ID of the neighboring nodes are used for network layer communication to provide QoS guarantee.

Benefits of technology

It achieves reliable and reachable message transmission, improves data transmission reliability, and meets the QoS parameter configuration requirements of different services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119547385B_ABST
    Figure CN119547385B_ABST
Patent Text Reader

Abstract

This application provides a communication method and apparatus. The method includes: a first node acquiring logical channel information corresponding to preset QoS parameters, the logical channel information being used to establish a logical transmission channel between the first node and a second node, the second node being a neighbor node of the first node, and the logical transmission channel being used to provide QoS guarantees for messages corresponding to the preset QoS parameters; the first node receiving a first message sent by the second node, the first message including at least one of the following: the second node's SLNA and the second node's interface L2ID; the first node performing network layer communication with the second node based on the logical channel information, the second node's SLNA, and the second node's interface L2ID. Implementing the embodiments of this application can provide QoS guarantees for messages. Furthermore, this method can be applied to vehicle-to-everything (V2X) communication, such as vehicle-to-everything (V2V) communication, LTE-V (Long Term Evolution Technology) for vehicle-to-vehicle communication, and vehicle-to-vehicle (V2V) communication.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the fields of vehicle networking and communication technology, and in particular to a communication method and device. Background Technology

[0002] In traditional Internet Protocol (IP) networks, adjacent devices establish a mapping table between IP addresses and Media Access Control (MAC) addresses through Address Resolution Protocol (ARP) learning mechanisms or static ARP configuration to support single-hop forwarding of IP packets between adjacent devices. Specifically, a Layer 2 header containing the MAC address of the next-hop adjacent device can be encapsulated in the IP packet header, enabling one-hop forwarding of the encapsulated IP packet within the subnet between adjacent devices. However, when IP packets are forwarded based on ARP entries, only the reachability problem is solved; the Quality of Service (QoS) guarantee cannot be provided. Therefore, how to provide QoS guarantees for packets has become a pressing technical problem to be solved. Summary of the Invention

[0003] This application provides a communication method and apparatus that can provide QoS guarantees for messages.

[0004] In a first aspect, a communication method is provided, comprising: a first node acquiring logical channel information corresponding to a preset quality of service (QoS) parameter, the logical channel information being used to establish a logical transmission channel between the first node and a second node, the second node being a neighbor node of the first node, and the logical transmission channel being used to provide QoS guarantees for packets corresponding to the preset QoS parameter; the first node receiving a first packet sent by the second node, the first packet including at least one of the following: the second node's spark link network address (SLNA) and the second node's interface layer 2 identification (L2ID); and the first node performing network layer communication with the second node based on the logical channel information, the second node's SLNA, and the second node's interface layer 2 identification (L2ID).

[0005] As can be seen, the first node can obtain the logical channel information corresponding to the preset QoS parameters. This logical channel information is used to establish a logical transmission channel between the first node and its neighboring nodes, enabling the first node to receive the first packets sent by its neighboring nodes. Furthermore, based on the logical channel information, the neighboring node's SLNA, and the Layer 2 identifier (L2ID) of the neighboring node's interface, the first node can conduct network layer communication with its neighboring nodes. Because this logical transmission channel can provide QoS guarantees for packets corresponding to the preset QoS parameters, the first node can provide QoS guarantees for packets during network layer communication with its neighboring nodes, solve the reachability problem of packet forwarding, and improve the reliability of data transmission.

[0006] The QoS parameters can be predefined by the first node based on service requirements, and therefore can also be called preset QoS parameters. It should be understood that in this application, different logical channel information can be used to establish different logical transmission channels, thereby enabling the transmission of different services. That is, for different service requirements, the first node can use different logical channel information to establish different logical transmission channels to transmit different services. Therefore, the QoS parameters correspond to the logical channel information.

[0007] Optionally, the logical channel information includes at least one of the following: transport channel identifier (TCID) and logical channel identifier (LCID). Preset QoS parameters may correspond to the TCID. The TCID can be generated by the first node based on the QoS parameters, or it can be predefined; this is not limited here. Furthermore, the TCID corresponds to the LCID. The LCID can be generated by the first node based on the TCID, or it can be predefined; this is not limited here.

[0008] The first message can be a Hello message.

[0009] Optionally, the network layer can be used to implement the transmission of data packets or control packets between two nodes, with specific functions including addressing and routing, connection establishment, maintenance, and termination. Furthermore, in this application, the network layer can be, for example, a star-shaped network layer.

[0010] In this context, "neighbor node" refers to the term used by two directly connected nodes to each other. A directly connected node is a node that can establish a direct connection link, or it can be understood as a node that can establish a neighbor relationship.

[0011] For example, an end node can establish a direct link with an intermediate node. Therefore, the intermediate node is a neighbor node of the end node, and the end node is a neighbor node of the intermediate node.

[0012] For example, an intermediate node can establish a direct link with another intermediate node. Therefore, the intermediate node is a neighbor node of the other intermediate node, and the other intermediate node is a neighbor node of the intermediate node.

[0013] It should be understood that the L2ID of a node's interface is a unique identifier assigned to that node as a network address for communication within the StarSpark network, totaling 6 bytes.

[0014] Optionally, in conjunction with the first aspect, the first node communicates with the second node at the network layer based on the logical channel information, the second node's SLNA, and the second node's interface L2ID, including: the first node establishing a forwarding table based on the logical channel information, the second node's SLNA, and the second node's interface L2ID; wherein the forwarding table includes at least one of the following: logical channel information, the second node's SLNA, and the second node's interface L2ID, and the logical channel information, the second node's SLNA, and the second node's interface L2ID correspond one-to-one.

[0015] This forwarding table is used for direct transmission between the first node and its neighboring nodes.

[0016] As can be seen, the first node can establish a forwarding table based on logical channel information, the SLNA of neighboring nodes, and the L2ID of the interfaces of neighboring nodes. Since this logical transmission channel can be used to provide QoS guarantees for packets corresponding to preset QoS parameters, the first node can provide QoS guarantees for packets when using the forwarding table to achieve network layer communication with neighboring nodes. It can also solve the reachability problem of packet forwarding and improve the reliability of data transmission.

[0017] Optionally, in conjunction with the first aspect, the forwarding table may also include a link quality level in the transmission direction from the first node to the second node, the link quality level being used to indicate the link quality in the transmission direction from the first node to the second node.

[0018] The link quality level can be calculated by the second node based on one or more of the following: bit error rate, latency, signal-to-noise ratio, and transmit / receive rate.

[0019] As can be seen, the forwarding table also includes the link quality level in the transmission direction from the first node to the second node, so that the first node can know the link quality level and then select the link with high link quality to transmit data, thereby improving the reliability of data transmission.

[0020] Optionally, in conjunction with the first aspect, the link quality level is included in the first message.

[0021] As can be seen, the first message also includes the link quality level in the transmission direction from the first node to the second node, so that the first node can know the link quality level and then select the link with high link quality to transmit data, thereby improving the reliability of data transmission.

[0022] Optionally, in conjunction with the first aspect, the first message also includes the area address of the second node, the second node being an intermediate node, and the area address of the second node being used to indicate that the area where the second node is located is a level 1 area and / or a level 2 area; wherein, the level 2 area is used to connect to the level 1 area.

[0023] For example, Level 1 regions are non-backbone regions, and Level 2 regions are backbone regions.

[0024] As can be seen, the area address of the second node can be used to indicate that the area where the second node is located is a level 1 area and / or a level 2 area, avoiding the need for multiple pieces of information to jointly indicate that the area where the second node is located is a level 1 area and / or a level 2 area, thus saving overhead.

[0025] Optionally, in conjunction with the first aspect, if the area address of the second node belongs to the address range of a level 1 area, the area address of the second node is used to indicate that the area where the second node is located is a level 1 area; if the area address of the second node belongs to the address range of a level 2 area, the area address of the second node is used to indicate that the area where the second node is located is a level 2 area; if the area address of the second node belongs to the address range of both level 1 and level 2 areas, the area address of the second node is used to indicate that the area where the second node is located is an overlapping area of ​​level 1 and level 2 areas.

[0026] The address range for Level 1 zones can be 1-30000, and the address range for Level 2 zones can be 30001-60000. Alternatively, the address range for Level 1 zones can be 30001-60000, and the address range for Level 2 zones can be 1-30000.

[0027] For example, the area address of the second node is 2. The address range of a level 1 area is 1-30000. Therefore, 2 belongs to the address range of a level 1 area, and thus it can be known that the area where the second node is located is a level 1 area.

[0028] For example, the area address of the second node is 32561. The address range of a level 2 area is 30001-60000. Therefore, 32561 belongs to the address range of a level 2 area, and thus it can be known that the area where the second node is located is a level 2 area.

[0029] For example, the area addresses of the second node are 2 and 32561. The address range of the level 1 area is 1-30000, and the address range of the level 2 area is 30001-60000. 2 belongs to the address range of the level 1 area, and 32561 belongs to the address range of the level 2 area. Therefore, the second node is in both the first area and the second area, that is, the area where the second node is located is the overlapping area of ​​the level 1 area and the level 2 area.

[0030] As can be seen, the area address of the second node can be used to indicate that the area where the second node is located is a level 1 area and / or a level 2 area, avoiding the need for multiple pieces of information to jointly indicate that the area where the second node is located is a level 1 area and / or a level 2 area, thus saving overhead.

[0031] Optionally, in conjunction with the first aspect, the first message is also used to indicate the type of the second node.

[0032] As can be seen, because the first message can also indicate the type of the second node, the first node can know the type of the second node, which allows the end node to discard the Hello message sent by the end node.

[0033] Optionally, in conjunction with the first aspect, the first message includes a first type length value (TLV) field, the first TLV field including at least one of the following: the SLNA of the second node, the L2ID of the interface of the second node.

[0034] The second node can have one or more SLNAs. In one possible implementation, one or more SLNAs of the second node correspond to the L2ID of one interface of the second node.

[0035] It can be seen that the first TLV field includes at least one of the following: the SLNA of the second node and the L2ID of the interface of the second node, so that the first node can communicate with the second node at the network layer based on the logical channel information, the SLNA of the second node and the L2ID of the interface of the second node.

[0036] Optionally, in conjunction with the first aspect, the first message may also include a second TLV field, which includes the link quality level.

[0037] As can be seen, the first message also includes a second TLV field, which includes the link quality level. This allows the first node to know the link quality level and select a link with high link quality to transmit data, thus improving the reliability of data transmission.

[0038] Optionally, in conjunction with the first aspect, the first message also includes a third TLV field, which includes a length field and at least one area address field corresponding to the length field. The length field is used to indicate the total length of at least one area address field, and the area address field is used to indicate an area address of the second node.

[0039] For example, the second node is configured with two region addresses, 1 and 30001. The third TLV field includes a length field and two corresponding region address fields. Each region address field is 2 bytes long, therefore the total length of the two region address fields is 4 bytes, meaning the length field is 4 bytes long. Furthermore, the two region address fields indicate region addresses 1 and 30001, respectively.

[0040] As can be seen, the third TLV field includes a length field and at least one region address field corresponding to the length field. The length field is used to indicate the total length of at least one region address field, which avoids the need to configure multiple length fields to indicate the length of the corresponding region address fields, thus saving overhead.

[0041] Optionally, in conjunction with the first aspect, the first message also includes a fourth TLV field, which indicates the authentication algorithm used by the second node, or the fourth TLV field indicates the authentication algorithm and authentication key used by the second node.

[0042] Authentication algorithms can include, for example, hash-based message authentication code (HMAC), secure hash algorithm 256 (SHA-256), HMAC-MD5, HMAC-SHA1-12, or HMAC-SHA1-20. The authentication key can be understood as an encrypted string.

[0043] As can be seen, the first message includes a fourth TLV field, which is used to indicate the authentication algorithm used by the second node, or the fourth TLV field is used to indicate the authentication algorithm and authentication key used by the second node. This avoids the need for different authentication TLV fields to indicate non-keychain and keychain classes separately, thus saving overhead.

[0044] Optionally, the first node is an end node and the second node is an intermediate node. The method further includes: the first node adds default routing information to the routing table of the first node. The default routing information includes at least one of the following: default destination address, the outgoing interface of the first node, the L2ID of the interface of the next hop node, and logical channel information; wherein the next hop node is the second node.

[0045] Optionally, the default destination address, the outgoing interface of the first node, the L2ID of the interface of the next hop node, and the logical channel information are in a one-to-one correspondence. This can also be understood as: the default routing information includes the one-to-one correspondence between the default destination address, the outgoing interface of the first node, the L2ID of the interface of the next hop node, and the logical channel information.

[0046] The default destination address can be, for example, 0.0. The outgoing interface of the first node can be understood as the interface within the first node that connects to the second node. The next-hop node is the second node.

[0047] As can be seen, because the first node adds default route information to its routing table, if it cannot find a corresponding route in its routing table when forwarding a packet, it can send the packet to the default destination address. This allows the first node to maintain fewer routes, saving memory and energy, and also facilitates its movement between different intermediate nodes. Furthermore, it avoids packet loss and improves the reliability of data transmission.

[0048] Secondly, a communication device is provided, comprising a first node and a transceiver unit, which is configured to: acquire logical channel information corresponding to preset Quality of Service (QoS) parameters, wherein the logical channel information is used to establish a logical transmission channel between the first node and a second node, wherein the second node is a neighbor node of the first node, and the logical transmission channel is used to provide QoS guarantees for packets corresponding to the preset QoS parameters; receive a first packet sent by the second node, wherein the first packet includes at least one of the following: the second node's StarNetwork Address (SLNA) and the second node's Interface Layer 2 Identifier (L2ID); and perform network layer communication with the second node based on the logical channel information, the second node's SLNA, and the second node's Interface L2ID.

[0049] Optionally, in conjunction with the second aspect, the logical channel information includes at least one of the following: Transmission Channel Identifier (TCID) and Logical Channel Identifier (LCID).

[0050] Optionally, in conjunction with the second aspect, the transceiver unit is used to perform network layer communication with the second node based on logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node, including: the transceiver unit is used to establish a forwarding table based on logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node; wherein the forwarding table includes at least one of the following: logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node, and the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node correspond one-to-one.

[0051] Optionally, in conjunction with the second aspect, the forwarding table may also include a link quality level in the transmission direction from the first node to the second node, the link quality level being used to indicate the link quality in the transmission direction from the first node to the second node.

[0052] Optionally, in conjunction with the second aspect, the link quality level is included in the first message.

[0053] Optionally, in conjunction with the second aspect, the first message also includes the area address of the second node, where the second node is an intermediate node, and the area address of the second node is used to indicate that the area where the second node is located is a level 1 area and / or a level 2 area; wherein, the level 2 area is used to connect to the level 1 area.

[0054] Optionally, in conjunction with the second aspect, Level 1 regions are non-core regions, and Level 2 regions are core regions.

[0055] Optionally, in conjunction with the second aspect, if the area address of the second node belongs to the address range of a level 1 area, the area address of the second node is used to indicate that the area where the second node is located is a level 1 area; if the area address of the second node belongs to the address range of a level 2 area, the area address of the second node is used to indicate that the area where the second node is located is a level 2 area; if the area address of the second node belongs to the address range of both level 1 and level 2 areas, the area address of the second node is used to indicate that the area where the second node is located is an overlapping area of ​​level 1 and level 2 areas.

[0056] Optionally, in conjunction with the second aspect, the first message is also used to indicate the type of the second node.

[0057] Optionally, in conjunction with the second aspect, the first message includes a first type length value (TLV) field, the first TLV field including at least one of the following: the SLNA of the second node, the L2ID of the interface of the second node.

[0058] Optionally, in conjunction with the second aspect, one or more SLNAs of the second node correspond to the L2ID of an interface of the second node.

[0059] Optionally, in conjunction with the second aspect, the first message may also include a second TLV field, which includes the link quality level.

[0060] Optionally, in conjunction with the second aspect, the first message also includes a third TLV field, which includes a length field and at least one area address field corresponding to the length field. The length field is used to indicate the total length of at least one area address field, and the area address field is used to indicate an area address of the second node.

[0061] Optionally, in conjunction with the second aspect, the first message also includes a fourth TLV field, which indicates the authentication algorithm used by the second node, or the fourth TLV field indicates the authentication algorithm and authentication key used by the second node.

[0062] Optionally, in conjunction with the second aspect, the first node is an end node, the second node is an intermediate node, and the communication device further includes a processing unit, which is used to add default routing information to the routing table of the first node. The default routing information includes at least one of the following: default destination address, the outgoing interface of the first node, the L2ID of the interface of the next hop node, and logical channel information; wherein, the next hop node is the second node.

[0063] Thirdly, a communication device is provided, characterized in that it comprises: a processor and a memory; the memory is used to store one or more programs, the one or more programs including computer-executable instructions, wherein when the device is running, the processor executes the one or more programs stored in the memory to cause the device to perform the method as described in any one of the first aspects.

[0064] Fourthly, a computer storage medium is provided, on which a computer program is stored, which, when run on a computer, causes the computer to perform the method as described in any one of the first aspects.

[0065] Fifthly, a chip is provided, the chip including a processor and a communication interface, the processor being used to call and execute instructions from the communication interface, and when the processor executes the instructions, implementing the method as described in any one of the first aspects.

[0066] In a sixth aspect, a computer program product is provided, comprising a computer program that, when run on a computer, causes the computer to perform the method as described in any one of the first aspects.

[0067] In a seventh aspect, a communication system is provided, including the aforementioned first node and / or the aforementioned second node. Attached Figure Description

[0068] The accompanying drawings used in the description of the embodiments or prior art will be briefly introduced below.

[0069] Figure 1 This application provides a schematic diagram illustrating a connection via an interface.

[0070] Figure 2 This is a schematic diagram of a wireless network area division provided in an embodiment of this application;

[0071] Figure 3 A schematic diagram of the system architecture provided in this application embodiment;

[0072] Figure 4 A flowchart illustrating a communication method provided in an embodiment of this application;

[0073] Figure 5 A schematic diagram of a forwarding table construction provided in an embodiment of this application;

[0074] Figure 6 This is a schematic diagram of the structure of a communication device 60 provided in an embodiment of this application;

[0075] Figure 7 This is a schematic diagram of the structure of a communication device 70 provided in an embodiment of this application. Detailed Implementation

[0076] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. The terms "system" and "network" in the embodiments of this application can be used interchangeably. Unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship; for example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "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 represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be one or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0077] In the embodiments described in this application, references to "one embodiment" or "some embodiments" mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The following detailed description further illustrates the purpose, technical solution, and beneficial effects of this application. It should be understood that the following are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made based on the technical solution of this application should be included within the scope of protection of this application.

[0078] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0079] The following is an explanation of some of the terms used in this application.

[0080] 1. Node

[0081] In this application, a node is an electronic device with communication capabilities, also known as a communication node. Nodes can be divided into end nodes and intermediate nodes.

[0082] The end node can be referred to as a wireless end system (WES). For a definition of WES, please refer to the definition of an end system in ITU-T Rec.X.2001 ISO / IEC 7498-1. It should be understood that in this application, the end node is movable; for example, an end node can migrate from one intermediate node to another, or it can be understood as an end node connecting to one intermediate node at one time and connecting to another intermediate node at another time. Furthermore, the end node does not have routing capabilities and may not have continuous power; that is, the end node does not have a continuous power supply and requires battery power, or it may be powered by various forms such as solar, wind, thermal, or capacitor power.

[0083] The intermediate node can be referred to as a wireless intermediate system (WIS). For a definition of WIS, please refer to the International Organization for Standardization (ISO). It should be understood that, in this application, the intermediate node generally does not move frequently. Furthermore, the intermediate node possesses routing and forwarding capabilities.

[0084] It should be understood that in this application, end nodes and intermediate nodes can be connected through an interface to form a logical link (hereinafter referred to as a link), and intermediate nodes can also be connected through an interface to form a logical link. The interface in this application embodiment can be called an air interface or other names, which are not limited here. The interface can be implemented using short-range connection technologies, such as Bluetooth, Zigbee, Wireless Fidelity (WiFi), and vehicular short-range wireless communication technologies. Alternatively, the interface in this application embodiment can also be implemented using long-range connection technologies, such as Long Term Evolution (LTE), 5th Generation Mobile Networks (or 5th Generation Wireless Systems, 5th Generation, 5G or 5G technology), and vehicular wireless communication technologies.

[0085] A node may include one or more interfaces. For example, an end node may include one or more interfaces, and an intermediate node may also include one or more interfaces. Different interfaces of a node can be implemented using different technologies; that is, the types of multiple interfaces of a node can be different. For example, an end node includes three interfaces, implemented via Bluetooth, ZigBee, and Wi-Fi respectively. It should be understood that different interface identifiers can be used to distinguish the interface types. In one possible implementation, interfaces of the same type on different nodes may use the same or different interface identifiers, which is not limited here.

[0086] Generally speaking, different types of interfaces cannot communicate with each other at the underlying level due to differences in the physical layer and the link layer. Therefore, different nodes need to be connected through the same type of interface to form a link, and then data can be transmitted on the link.

[0087] For example, see Figure 1 , Figure 1 This is a schematic diagram illustrating a connection via an interface, provided as an embodiment of this application. Figure 1 In this context, A, B, and C each represent an intermediate node, and ID is the interface identifier of the intermediate node. Figure 1 In link 1-1, the interface with identifier 1 in A is connected to the interface with identifier 1 in B, forming link 1. That is, the interface with identifier 1 in A and the interface with identifier 1 in B are of the same type. Figure 1 In steps 1-2, the interface with identifier 1 in A is connected to the interface with identifier 1 in B, forming link 1. The interface with identifier 1 in A is connected to the interface with identifier 1 in C, forming link 2. That is, the interface with identifier 1 in A is of the same type as the interface with identifier 1 in B, and the interface with identifier 1 in A is of the same type as the interface with identifier 1 in C. Figure 1 In steps 1-3, the interface with identifier 1 in A is connected to the interface with identifier 1 in B, forming link 1; the interface with identifier 2 in A is connected to the interface with identifier 2 in B, forming link 2. That is, the interface with identifier 1 in A and the interface with identifier 1 in B are of the same type, and the interface with identifier 2 in A and the interface with identifier 2 in B are of the same type. Figure 1 In sections 1-4, the interface with identifier 1 in section A is connected to the interface with identifier 1 in section B, forming link 1; the interface with identifier 2 in section A is connected to the interface with identifier 1 in section C, forming link 2. That is, the interface with identifier 1 in section A and the interface with identifier 1 in section B are of the same type, and the interface with identifier 2 in section A and the interface with identifier 1 in section C are of the same type. Furthermore, combined with... Figure 1 From 1-1 and 1-2, it can be seen that one interface of the same node can be connected to one or more interfaces of the same type on another node. Combined with... Figure 1 As can be seen from 1-3 and 1-4, multiple interfaces of the same node can be connected to the same type of interfaces of multiple nodes respectively.

[0088] Considering the scalability of large networks, embodiments of this application can divide and conquer the wireless network. That is, the wireless network can be divided into one or more level-1 areas and one level-2 area. The level-1 area can be a non-backbone area, and the level-2 area can be a backbone area.

[0089] It should be noted that in this application, a Level 1 region may include one or more end nodes and intermediate nodes, and a Level 2 region may include intermediate nodes. The number of nodes in any given region is not limited.

[0090] For example, see Figure 2 , Figure 2This is a schematic diagram illustrating the area division of a wireless network according to an embodiment of this application. Figure 2 The system comprises three level 1 regions and one level 2 region. End nodes can be located in any level 1 region, but level 2 regions do not include end nodes.

[0091] It should be understood that in this application, a Level 2 region can be used to connect one or more Level 1 regions, thereby enabling data exchange between different Level 1 regions.

[0092] To achieve functions such as uniquely identifying an entity in a wireless network, a network entity title (NET) can be defined. See Table 1, which shows one NET format provided in an embodiment of this application. It can be seen that a NET can include a 2-byte area address and a 6-byte system ID. One byte is 8 bits.

[0093] Table 1

[0094]

[0095] In this application, the area address can be called an area ID, or any other name, which is not limited here. The area address of a node can be used to indicate whether the node is located in a Level 1 or / or Level 2 area. This avoids the need for multiple pieces of information to jointly indicate whether the node is located in a Level 1 or / or Level 2 area, thus saving overhead.

[0096] Zone addresses can be divided into four categories: 0, 1-30000, 30001-60000, and 60001-65535. 0 and 60001-65535 are reserved zone addresses. 1-30000 is the address range for Level 1 zones, and 30001-60000 is the address range for Level 2 zones; alternatively, 1-30000 is the address range for Level 2 zones, and 30001-60000 is the address range for Level 1 zones. This allows a node to be identified as belonging to a Level 1 or / or Level 2 zone simply by its zone address, avoiding the need for multiple pieces of information to jointly indicate whether a node belongs to a Level 1 or / or Level 2 zone, thus saving overhead.

[0097] End nodes are not configured with a zone address; they are only configured with a system identifier. In this case, the zone address in the end node's NET is 0. The end node's system identifier is used to uniquely identify the end node.

[0098] An intermediate node can be configured with one or more region addresses. It should be understood that when an intermediate node is located in an overlapping area of ​​Level 1 and Level 2 regions, the intermediate node can be configured with multiple region addresses. In one possible implementation, an intermediate node can be configured with a maximum of three region addresses. Optionally, the region addresses of different intermediate nodes can be all the same, partially the same, or completely different. For example, one intermediate node's region address can be 1, and another intermediate node's region address can also be 1, meaning these two intermediate nodes have the same region address. As another example, one intermediate node's region address can include 1 and 30001, and another intermediate node's region address can be 1, meaning these two intermediate nodes have partially the same region address. As yet another example, one intermediate node's region address can be 1, and another intermediate node's region address can be 30001, meaning these two intermediate nodes have completely different region addresses.

[0099] Intermediate nodes can also be configured with a system identifier. The system identifier of an intermediate node is used to uniquely identify the intermediate node.

[0100] For example, the NET of the intermediate node is 0001.1234.5678.0123 (hexadecimal), where the area address of the intermediate node is 0001 and the system identifier of the intermediate node is 1234.5678.0123.

[0101] To reduce configuration errors, in this application, the system identifier of an end node can reuse the layer 2 identification (L2ID) of its interface. Similarly, the system identifier of an intermediate node can reuse the L2ID of its interface. Optionally, in this application, the system identifier of a node can reuse the largest or smallest L2ID among multiple interfaces of that node.

[0102] It should be understood that the L2ID of a node's interface is a unique identifier assigned to that node as a network address for communication within the StarSpark network, totaling 6 bytes.

[0103] 2. Neighboring nodes

[0104] Neighbor nodes are the terms two directly connected nodes use to refer to each other. Directly connected nodes are nodes that can establish a direct link, or nodes that can establish a neighbor relationship.

[0105] For example, an end node can establish a direct link with an intermediate node. Therefore, the intermediate node is a neighbor node of the end node, and the end node is a neighbor node of the intermediate node.

[0106] For example, an intermediate node can establish a direct link with another intermediate node. Therefore, the intermediate node is a neighbor node of the other intermediate node, and the other intermediate node is a neighbor node of the intermediate node.

[0107] In this application, end nodes have no area address, and the neighboring nodes of end nodes are intermediate nodes. End nodes can be connected to intermediate nodes, and the area address of the intermediate node belongs to the address range of level 1 areas, or the area address of the intermediate node belongs to the address range of both level 1 and level 2 areas. Therefore, the neighbor type between end nodes and intermediate nodes can be called the first neighbor type.

[0108] In this application, the neighbor type between an intermediate node and its neighbor node (which is another intermediate node) can be one of the following: first neighbor type, second neighbor type, or third neighbor type. Specifically:

[0109] If the address range of the intermediate node belonging to the level 1 region intersects with the address range of the neighboring node belonging to the level 1 region, and the address range of the intermediate node belonging to the level 2 region does not intersect with the address range of the neighboring node belonging to the level 2 region, then the neighbor type of the intermediate node and the neighboring node is the first neighbor type.

[0110] If the address range of the intermediate node belonging to the level 1 region has no intersection with the address range of the neighboring node belonging to the level 1 region, but the address range of the intermediate node belonging to the level 2 region has an intersection with the address range of the neighboring node belonging to the level 2 region, then the neighbor type of the intermediate node and the neighboring node is the second neighbor type.

[0111] If there is an intersection between the address range of the intermediate node belonging to the level 1 region and the address range of the neighboring node belonging to the level 1 region, and there is also an intersection between the address range of the intermediate node belonging to the level 2 region and the address range of the neighboring node belonging to the level 2 region, then the neighbor type of the intermediate node and the neighboring node is the third neighbor type.

[0112] For example, the area address of intermediate node #A is 1, and the area addresses of intermediate node #B are 1 and 30002. The address range of a level 1 area is 1-30000, and the address range of a level 2 area is 30001-60000. The intersection of the area addresses of intermediate node #A and intermediate node #B is 1, and 30002 is not the intersection of the area addresses of intermediate node #A and intermediate node #B. 1 belongs to the address range of a level 1 area, and 30002 belongs to the address range of a level 2 area. Therefore, the neighbor type of intermediate node #A and intermediate node #B is the first neighbor type.

[0113] For example, the area address of intermediate node #C is 30002, and the area addresses of intermediate node #D are 1 and 30002. The address range of a level 1 area is 1-30000, and the address range of a level 2 area is 30001-60000. The intersection of the area addresses of intermediate nodes #C and #D is 30002, and 1 is not the intersection of the area addresses of intermediate nodes #A and #B. 1 belongs to the address range of a level 1 area, and 30002 belongs to the address range of a level 2 area. Therefore, the neighbor type of intermediate nodes #C and #D is the second neighbor type.

[0114] For example, the area addresses of intermediate node #E are 1 and 30002, and the area addresses of intermediate node #F are 1 and 30002. The address range of level 1 areas is 1-30000, and the address range of level 2 areas is 30001-60000. The intersection of the area addresses of intermediate nodes #E and #F is 1 and 30002. 1 belongs to the address range of level 1 areas, and 30002 belongs to the address range of level 2 areas. Therefore, the neighbor type of intermediate nodes #E and #F is the third neighbor type.

[0115] 3. Quality of Service (QoS) parameters

[0116] In this application, QoS parameters are parameters predefined by end nodes or intermediate nodes according to service requirements, and therefore can also be called preset QoS parameters.

[0117] For example, QoS parameters may include one or more of the following: default priority value, latency, packet loss rate, burst data size, average window, etc.

[0118] QoS parameters correspond to TCIDs. TCIDs can be generated by end nodes or intermediate nodes based on QoS parameters, or they can be predefined; this is not limited here. Furthermore, TCIDs correspond to LCIDs. LCIDs can be generated by end nodes or intermediate nodes based on TCIDs, or they can be predefined; this is not limited here.

[0119] Optionally, one or more of TCID and LCID can be used to establish a logical transmission channel between an end node or intermediate node and its neighboring nodes. This logical transmission channel can be used to provide QoS guarantees for packets corresponding to QoS parameters.

[0120] 4. Hello message

[0121] In this application, an end node or an intermediate node can establish a neighbor relationship with one or more neighboring nodes through Hello messages to exchange one or more of the following: Spark Link Network Address (SLNA), Layer 2 identifier of the interface, etc., thereby enabling network layer communication with neighboring nodes. It is understood that different end nodes cannot establish a neighbor relationship; that is, an end node does not receive Hello messages from other end nodes.

[0122] The network layer can be used to transmit data or control messages between two nodes, and its specific functions include addressing and routing, connection establishment, maintenance, and termination. Furthermore, in this application, the network layer can be, for example, a star-shaped network layer.

[0123] The Hello message may include a header and one or more typelength values ​​(TLVs). The header may be called the Hello protocol data unit (PDU) header, or other names may be used, which are not limited here.

[0124] The following table illustrates the format of the Hello message.

[0125] Refer to Table 2, which shows the format of a Hello message header provided in an embodiment of this application. As shown in Table 2, the meaning and length of each field in the header are as follows:

[0126] Network layer protocol identifier: A routing protocol constant used to identify Hello packets; its value is to be determined (TBD). This field is 1 byte long.

[0127] Version: 1. This field is 1 byte long.

[0128] PDU Type: The type of the Hello message. It should be understood that Hello messages generated by end nodes are abbreviated as WEH messages; Hello messages generated by intermediate nodes are abbreviated as WIH messages. Therefore, this field determines the type of the node that generated the Hello message. This field is 1 byte long. It should be understood that this field allows the receiving node to know the type of the node that sent the Hello message, enabling the end node to discard the Hello message sent by the end node.

[0129] Source system ID: The system identifier of the node that sent the Hello message. This field is 6 bytes long.

[0130] Source interface ID: The identifier of the interface on the node that sends the Hello message. This field is 1 byte long.

[0131] Holding time: If no Hello message is received from a neighbor node within this holding time, the established neighbor relationship is terminated. The unit can be seconds. This field is 2 bytes long.

[0132] PDU length: The length of the Hello message. The unit can be bytes. This field is 2 bytes long.

[0133] Checksum: The checksum of the Hello message, used to verify the integrity of the Hello message. This field is 2 bytes long.

[0134] Serial number: Used to prevent replay attacks. A replay attack refers to an attacker sending a data packet that a node has already received to deceive the system, primarily used in the authentication process to compromise its integrity. This field is 4 bytes long.

[0135] Variable-length fields: These can be used to carry newly added TLV fields. The length of a variable-length field is variable.

[0136] Table 2

[0137]

[0138] Refer to Table 3, which shows the format of a TLV field in the Hello message provided in this application embodiment. As shown in Table 3, the meaning and length of each field in this TLV field are as follows:

[0139] Type: The type used for this TLV field, with a value of TBD. The type field is 1 byte long.

[0140] Length: The total length of the region address field, which has one instance. A region address field is 2 bytes long. An intermediate node can configure one or more region addresses, so the length of the length field is variable. Optionally, an intermediate node can configure up to three region addresses, so the length of the length field can be 2 bytes, 4 bytes, or 6 bytes. For example, when the TLV field includes one region address field, the length of the length field can be 2 bytes; when the TLV field includes two region address fields, the length of the length field can be 4 bytes; and when the TLV field includes three region address fields, the length of the length field can be 6 bytes. This avoids the need to configure multiple length fields to indicate the length of the corresponding region address fields, saving overhead.

[0141] Area address: This field can contain one or more area addresses. Optionally, if an intermediate node can be configured with a maximum of three area addresses, then this field can contain a maximum of three entries.

[0142] Table 3

[0143]

[0144] In this application, the TLV field shown in Table 3 can be called the area address TLV field, or other names can be used, which are not limited here.

[0145] It should be understood that a Hello message may include one area address TLV field. Furthermore, a Hello message sent by an intermediate node must contain exactly one area address TLV field; a Hello message sent by an end node cannot include an area address TLV field. If an intermediate node receives a Hello message from another intermediate node and that Hello message contains no area address TLV field or contains multiple area address TLV fields, the Hello message is discarded. Similarly, if an intermediate node receives a Hello message from an end node and that Hello message contains an area address TLV field, the Hello message is discarded. Finally, if an end node receives a Hello message from an intermediate node and that Hello message contains no area address TLV field or contains multiple area address TLV fields, the Hello message is discarded.

[0146] Refer to Table 4, which shows another TLV field format for the Hello message provided in the embodiments of this application. As shown in Table 4, the meaning and length of each field in this TLV field are as follows:

[0147] type: The type used for this TLV field, with a value of TBD. The type field is 1 byte long.

[0148] length: The length of this TLV field. The length of this TLV field can be 6-254 bytes, meaning the length of this TLV field is variable. The length field can be 1 byte.

[0149] Authentication Type: A value of 0 indicates a reserved field. A value of 1-200 indicates a non-keychain class, used to indicate the authentication algorithm. Authentication algorithms can include, for example, hash-based message authentication code (HMAC), secure hash algorithm 256 (SHA-256), HMAC-MD5, HMAC-SHA1-12, or HMAC-SHA1-20. A value of 201-60000 indicates a keychain class, used to indicate the authentication algorithm and authentication key. Optionally, a security association (SA) identifier can be used to indicate the authentication algorithm and authentication key. The authentication key can be understood as an encrypted string. A value of 60001-65535 indicates a reserved field. This avoids the need for separate authentication TLV fields to indicate non-keychain and keychain classes, saving overhead.

[0150] Authentication value: This field provides summary information about the authentication process. This summary information can be calculated by the node sending the Hello message using an authentication algorithm, combining the Hello message and the authentication key. The length of this field is variable.

[0151] Table 4

[0152]

[0153]

[0154] In this application, the TLV field shown in Table 4 may be called the authentication TLV field, or may be called by other names, which are not limited here.

[0155] It should be understood that a Hello message may include one authentication TLV field. If no authentication algorithm is configured, or if neither an authentication algorithm nor an authentication key is configured, the Hello message will not carry an authentication TLV field. A node can send a Hello message with at most one authentication TLV field. If a node receives a Hello message containing multiple authentication TLV fields, it will discard the message.

[0156] In addition, the relationship between the authentication TLV field and the checksum field in Table 1 is as follows: During the encoding of the Hello message, the node first sets the value of the checksum field to zero, then calculates the authentication summary information, and finally calculates the value of the checksum field after encoding the authentication TLV field; During the decoding of the Hello message, the node first checks whether the value of the checksum field is correct, then sets the value of the checksum field to zero, and finally performs authentication.

[0157] Refer to Table 5, which shows another TLV field format for the Hello message provided in the embodiments of this application. As shown in Table 5, the meaning and length of each field in this TLV field are as follows:

[0158] type: The type used for this TLV field, with a value of TBD. The type field is 1 byte long.

[0159] length: The length of this TLV field, which is 9 bytes. The length field can also be 1 byte long.

[0160] Neighborhood State (adjacency state): A value of 0 indicates a down neighbor status, meaning there is no neighbor relationship between adjacent nodes. A value of 1 indicates an initialization neighbor status, meaning only one node knows one or more of the SLNA, Layer 2 interface identifier, etc., of its neighboring node. A value of 2 indicates an up neighbor status, meaning both adjacent nodes know one or more of the SLNA, Layer 2 interface identifier, etc., of each other. This field is 1 byte long.

[0161] Neighbor ID: The system identifier of the neighboring node. This field is 6 bytes long.

[0162] Neighbor interface ID: The identifier of the neighbor node's interface. This field is 1 byte long.

[0163] Link Quality Level (LQL): The quality level of the link in the transmission direction from a neighboring node to the node sending the Hello message. The LQL indicates the link quality in the transmission direction from a neighboring node to this node. Generally, the LQL is calculated by the node based on one or more of the following: bit error rate, latency, signal-to-noise ratio, and transmit / receive rate. A value of 0 indicates that the node has not started link detection; a value of 1 indicates a high LQL; a value of 2 indicates a medium LQL; a value of 3 indicates a low LQL; values ​​5-254 are reserved; a value of 255 indicates that the neighboring node should not transmit on the link between this node and its neighboring nodes. This can also be understood as instructing the neighboring node to set a maximum cost (max metric) - 1 on the link between this node and its neighboring nodes, preventing the neighboring node from forwarding traffic to this node. The maximum cost is 65535. This allows nodes that receive Hello messages to know the link quality level, and thus select links with high link quality to transmit data, improving the reliability of data transmission.

[0164] Table 5

[0165]

[0166] In this application, the TLV field shown in Table 5 can be called the Neighbor Status TLV field, or other names can be used, which are not limited here.

[0167] It should be understood that a Hello message may include one Neighbor State TLV field. If a node receives a Hello message containing multiple Neighbor State TLV fields, it will discard the Hello message.

[0168] Refer to Table 6, which shows another TLV field format for the Hello message provided in the embodiments of this application. As shown in Table 6, the meaning and length of each field in this TLV field are as follows:

[0169] type: The type used for this TLV field, with a value of TBD. The type field is 1 byte long.

[0170] length: The length of this TLV field, which can be 0-255 bytes. The length field can be 1 byte long.

[0171] L2ID: The L2ID of the interface of the node that sent the Hello message. This field can be 6 bytes long. This allows the receiving node to know the L2ID of the interface of the node that sent the Hello message.

[0172] SLNA: This can be understood as the SLNA of the interface on the node that sends Hello messages. This field can be 2 bytes long. This allows the node receiving the Hello message to know the SLNA of the interface of the node that sent the Hello message.

[0173] Table 6

[0174]

[0175] In this application, the TLV field shown in Table 6 may be called the SLNA TLV field, or may be called by other names, which are not limited here.

[0176] It should be understood that a Hello message may include one or more SLNA TLV fields. Optionally, an interface through which a node sends Hello messages may be configured with one or more SLNAs. In one possible implementation, a Hello message may include one SLNA TLV field, and one SLNA TLV field may include one or more SLNAs. In another possible implementation, a Hello message may include multiple SLNA TLV fields, and one SLNA TLV field may include one SLNA. It should be noted that when a Hello message from a neighboring node includes multiple SLNAs of the neighboring node, the node may use the union of the multiple SLNAs as the SLNA for network layer communication with the neighboring node.

[0177] In addition, once a node obtains an SLNA, it must include the SLNA TLV field in its Hello message.

[0178] The above content briefly explains the meaning of some terms involved in the embodiments of this application. It is intended to help people better understand the technical solutions provided in the embodiments of this application and does not constitute a limitation on the technical solutions provided in the embodiments of this application.

[0179] It should be understood that the technical solutions of the embodiments of this application can be applied to Long Term Evolution (LTE), 5th generation mobile networks (5G), and wireless local area networks (WLAN) systems. The technical solutions of the embodiments of this application can also be applied to other future communication systems, such as 6G communication systems. In future communication systems, the functions may remain the same, but the names may change. Furthermore, the technical solutions of the embodiments of this application can also be applied to vehicle-to-everything (V2X) communication, such as vehicle-to-vehicle (V2V) communication, LTE-V (Long Term Evolution) technology for inter-vehicle communication, and vehicle-to-vehicle (V2V) communication.

[0180] See Figure 3 , Figure 3 This application provides a schematic diagram of a system architecture, which may include one or more end nodes and one or more intermediate nodes. An end node can be connected to one or more intermediate nodes, and an intermediate node can also be connected to one or more intermediate nodes, forming corresponding links. Of course, these nodes can also transmit data through these corresponding links. It should be understood that... Figure 3 This is merely an illustrative diagram and does not constitute a limitation on the applicable scenarios of the technical solutions provided in this application.

[0181] Optional, Figure 3The architecture shown can be applied to one or more scenarios, including mobile internet (MI), industrial control, self-driving, transportation safety, internet of things (IoT), smart city, smart home, and in-vehicle communication. For example, in the in-vehicle communication scenario, intermediate nodes could be gateways (GW), telematics boxes (Tboxes, or TCUs), etc. The GW is a core component of the vehicle's electronic and electrical architecture, serving as the data interaction hub for the vehicle network and routing network data from different networks, such as controller area networks (CAN), local interconnect networks (LIN), media-oriented system transport (MOST), and FlexRay. Tboxes are primarily used for communication with external vehicle systems, backend systems, and mobile applications (APPs). End nodes could be mobile data centers (MDCs), human-machine interfaces (HMIs), electronic control units (ECUs), etc. The MDC is the vehicle's intelligent in-vehicle computing platform. HMI stands for H-MI (Hydraulic Interface). ECU stands for ECU (Electronic Control Unit).

[0182] See Figure 4 , Figure 4 This is a flowchart illustrating a communication method provided in an embodiment of this application. Wherein, in Figure 4 In this context, the first node can be an end node, and the second node can be an intermediate node; or, the first node can be an intermediate node, and the second node can be an end node; or, both the first and second nodes can be intermediate nodes. For example... Figure 4 As shown, the method includes, but is not limited to, the following steps:

[0183] 401. The first node obtains the logical channel information corresponding to the preset QoS parameters. This logical channel information is used to establish a logical transmission channel between the first node and the second node, where the second node is a neighbor node of the first node. The logical transmission channel is used to provide QoS guarantees for the packets corresponding to the preset QoS parameters.

[0184] The information regarding preset QoS parameters and neighboring nodes can be found in the descriptions above and will not be repeated here. It should be understood that in this application, different logical channel information can be used to establish different logical transmission channels, thereby enabling the transmission of different services. That is, for different service requirements, the first node can use different logical channel information to establish different logical transmission channels to transmit different services. Therefore, the preset QoS parameters correspond to the logical channel information.

[0185] Optionally, logical channel information may include at least one of the following: TCID, LCID.

[0186] 402. The second node sends a first message to the first node. The first message includes at least one of the following: the SLNA of the second node and the L2ID of the interface of the second node.

[0187] Correspondingly, the first node receives the first message sent by the second node.

[0188] The first message can be, for example, a Hello message. For details about Hello messages, please refer to the above description, which will not be repeated here.

[0189] Optionally, the first message may include a first TLV field, which includes at least one of the following: the SLNA of the second node, and the L2ID of the interface of the second node. The number of SLNAs of the second node may be one or more. In one possible implementation, one or more SLNAs of the second node correspond to the L2ID of one interface of the second node.

[0190] It should be noted that the first TLV field can be the SLNA TLV field in Table 6. For details, please refer to the relevant descriptions above, which will not be repeated here.

[0191] It can be seen that the first TLV field includes at least one of the following: the SLNA of the second node and the L2ID of the interface of the second node, so that the first node can communicate with the second node at the network layer based on the logical channel information, the SLNA of the second node and the L2ID of the interface of the second node.

[0192] Optionally, the first message may also include a link quality level in the transmission direction from the first node to the second node. The link quality level indicates the link quality in the transmission direction from the first node to the second node. For details regarding the link quality level, please refer to the relevant description in Table 5, which will not be repeated here. It should be understood that the link quality level is calculated by the second node based on one or more of the following: bit error rate, latency, signal-to-noise ratio, and transmit / receive rate.

[0193] In one possible implementation, the first message may further include a second TLV field, which includes the link quality level. It should be noted that the second TLV field may be the neighbor status TLV field in Table 5; please refer to the relevant descriptions above for details, which will not be repeated here.

[0194] As can be seen, the first message also includes the link quality level in the transmission direction from the first node to the second node, so that the first node can know the link quality level and then select the link with high link quality to transmit data, thereby improving the reliability of data transmission.

[0195] Optionally, the second node is an intermediate node. The first message also includes the area address of the second node. The area address of the second node is used to indicate whether the area where the second node is located is a Level 1 area and / or a Level 2 area. The number of area addresses of the second node can be one or more, and is not limited here. In addition, the relevant descriptions of Level 1 and Level 2 areas can be referred to above, and will not be repeated here.

[0196] In one possible implementation, the region address of the second node belongs to the address range of a Level 1 region. The region address of the second node is used to indicate that the region where the second node is located is a Level 1 region. For example, if the region address of the second node is 2, and the address range of a Level 1 region is 1-30000, then 2 belongs to the address range of a Level 1 region, and thus it can be determined that the region where the second node is located is a Level 1 region.

[0197] In another possible implementation, the region address of the second node belongs to the address range of a level 2 region. The region address of the second node is used to indicate that the region where the second node is located is a level 2 region. For example, if the region address of the second node is 32561, and the address range of a level 2 region is 30001-60000, then 32561 belongs to the address range of a level 2 region, and thus it can be determined that the region where the second node is located is a level 2 region.

[0198] In another possible implementation, the region address of the second node belongs to the address range of both Level 1 and Level 2 regions. The region address of the second node is used to indicate that the region where the second node is located is the overlapping area of ​​Level 1 and Level 2 regions. For example, the region addresses of the second node are 2 and 32561. The address range of Level 1 regions is 1-30000, and the address range of Level 2 regions is 30001-60000. 2 belongs to the address range of Level 1 regions, and 32561 belongs to the address range of Level 2 regions. Therefore, the second node is in both the first and second regions, that is, the region where the second node is located is the overlapping area of ​​Level 1 and Level 2 regions.

[0199] It should be noted that in this application, end nodes do not have area addresses. Therefore, when the second node is an end node, the first message does not include the area address of the second node. In this application, the area where the end node is located is a level 1 area. It should be understood that an end node can be connected to an intermediate node, the area where the intermediate node is located is a level 1 area, or the area where the intermediate node is located is an overlapping area of ​​level 1 and level 2 areas.

[0200] For example, in combination Figure 2 It can be seen that one-end nodes can be connected to the intermediate node with region address 1, and the other-end nodes can be connected to intermediate nodes with region addresses 2 and 30002 respectively. The intermediate node with region address 1 is located in a level 1 region; the intermediate nodes with region addresses 2 and 30002 are located in an overlapping area of ​​level 1 and level 2 regions. Furthermore, in Figure 2 In the context, the intermediate node with region address 30002 is located in a level 2 region.

[0201] Optionally, the first message also includes a third TLV field. The third TLV field includes a length field and at least one area address field corresponding to the length field. The length field indicates the total length of the at least one area address field, and the area address field indicates an area address of the second node. The third TLV field can be one of the area address TLV fields in Table 3; please refer to the relevant descriptions above for details, which will not be elaborated upon here.

[0202] For example, the second node is configured with two region addresses, 1 and 30001. The third TLV field includes a length field and two corresponding region address fields. Each region address field is 2 bytes long, therefore the total length of the two region address fields is 4 bytes, meaning the length field is 4 bytes long. Furthermore, the two region address fields indicate region addresses 1 and 30001, respectively.

[0203] As can be seen, the region address of the second node can be used to indicate that the region where the second node is located is a level 1 region and / or a level 2 region, avoiding the need for multiple pieces of information to jointly indicate that the region where the second node is located is a level 1 region and / or a level 2 region, thus saving overhead. At the same time, the third TLV field includes a length field and at least one region address field corresponding to the length field. The length field is used to indicate the total length of at least one region address field, avoiding the need to configure multiple length fields to indicate the length of the corresponding region address fields, thus saving overhead.

[0204] Optionally, the first message also includes a fourth TLV field, which indicates the authentication algorithm used by the second node, or, alternatively, indicates the authentication algorithm and authentication key used by the second node. The fourth TLV field can be one of the authentication TLV fields in Table 4, as detailed above. Similarly, the authentication algorithm and authentication key can be found in the above descriptions and will not be elaborated upon here.

[0205] As can be seen, the first message includes a fourth TLV field, which is used to indicate the authentication algorithm used by the second node, or the fourth TLV field is used to indicate the authentication algorithm and authentication key used by the second node. This avoids the need for different authentication TLV fields to indicate non-keychain and keychain classes separately, thus saving overhead.

[0206] Optionally, the first message may also indicate the type of the second node. It should be understood that the type of the second node can be an end node or an intermediate node.

[0207] In one possible implementation, the first message may include a PDU type field, which may indicate the type of the second node. The PDU type field may refer to... Figure 3 The relevant descriptions will not be repeated here.

[0208] As can be seen, because the first message can also indicate the type of the second node, the first node can know the type of the second node, which allows the end node to discard the Hello message sent by the end node.

[0209] The method may further include step 403 after step 402.

[0210] 403. The first node communicates with the second node at the network layer based on the logical channel information, the second node's SLNA, and the second node's interface L2ID.

[0211] The network layer can be referred to in Table 6 for relevant descriptions, and will not be elaborated further.

[0212] Optionally, step 403 may include: the first node establishing a forwarding table based on logical channel information, the second node's SLNA, and the L2ID of the second node's interface. This forwarding table is used for direct transmission between the first node and its neighboring nodes.

[0213] It should be understood that the forwarding table may include at least one of the following: logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node; there is a one-to-one correspondence between the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node. Alternatively, it can be understood that the forwarding table includes a one-to-one correspondence between the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node.

[0214] In one possible implementation, the forwarding table may further include at least one of the following: link quality level and interface identifier of the first node. The logical channel information, the SLNA of the second node, the L2ID of the second node's interface, the link quality level, and the interface identifier of the first node correspond one-to-one. Alternatively, it can be understood that the forwarding table includes a one-to-one correspondence between the logical channel information, the SLNA of the second node, the L2ID of the second node's interface, the link quality level, and the interface identifier of the first node.

[0215] For example, see Figure 5 , Figure 5 This is a schematic diagram illustrating the construction of a forwarding table as provided in an embodiment of this application. Figure 5 In the diagram, node A is an end node with an SLNA of 4.4, an L2ID of its interface of 4444.4444.4444, and an interface identifier of if1. Node B is an intermediate node with an SLNA of 2.2, an L2ID of its interface of 2222.2222.2222, and an interface identifier of if1. Node C is an intermediate node with an SLNA of 3.3, an L2ID of its interface of 3333.3333.3333, and an interface identifier of if1. Node H is an intermediate node with an SLNA of 5.5, an L2ID of its interface of 5555.5555.5555, and an interface identifier of if1. For example, node B can receive Hello messages from nodes A, C, and H respectively. Therefore, node B can obtain a forwarding table, which may include node B's interface identifier, the SLNA of neighboring nodes, the L2ID of the interface of neighboring nodes, node B's logical channel information, and the LQL in the transmission direction from node B to neighboring nodes. The interface identifier of node B, the SLNA of neighboring nodes, the L2ID of the interface of neighboring nodes, the logical channel information of node B, and the LQL correspond one-to-one, as detailed in Table 7. Combined with... Figure 5As can be seen, the SLNAs of neighboring nodes in Table 7 include the SLNAs of node A, node C, and node H. The L2IDs of the interfaces of neighboring nodes include the L2IDs of the interfaces of node A, node C, and node H. Secondly, the logical channel information of node B includes TCID and LCID. The TCIDs are 3030, 4020, and 5001, and the LCIDs are 10, 12, and 13. This means that node B has established different logical transmission channels with nodes A, C, and H. Furthermore, the LQLs in the transmission directions from node B to nodes A, C, and H are also different. It should be understood that Table 7 is only an example, and other forms are possible, which are not limited here.

[0216] Table 7

[0217]

[0218] As can be seen, the first node can obtain the logical channel information corresponding to the preset QoS parameters. This logical channel information is used to establish a logical transmission channel between the first node and its neighboring nodes, enabling the first node to receive the first packets sent by the neighboring nodes. Furthermore, based on the logical channel information, the neighboring node's SLNA, and the neighboring node's interface L2ID, the first node can conduct network layer communication with its neighboring nodes. Because this logical transmission channel can provide QoS guarantees for packets corresponding to the preset QoS parameters, the first node can provide QoS guarantees for packets during network layer communication with its neighboring nodes, solve the reachability problem of packet forwarding, and improve the reliability of data transmission.

[0219] Optionally, the first node is an end node and the second node is an intermediate node. The method may further include: the first node adding default routing information to its routing table. The default routing information may include at least one of the following: a default destination address, the outgoing interface of the first node, the L2ID of the interface of the next-hop node, and logical channel information. The default destination address, the outgoing interface of the first node, the L2ID of the interface of the next-hop node, and the logical channel information correspond one-to-one. This can also be understood as: the default routing information includes a one-to-one correspondence between the default destination address, the outgoing interface of the first node, the L2ID of the interface of the next-hop node, and the logical channel information.

[0220] The default destination address can be, for example, 0.0. The outgoing interface of the first node can be understood as the interface within the first node that connects to the second node. The next-hop node is the second node.

[0221] For example, the routing table of the first node can be found in Table 8. The default destination address in Table 8 is 0.0. The outgoing interface of the first node is the interface with the interface identifier if1. The L2ID of the interface of the next hop node is 2222.2222.2222. The logical channel information includes TCID and LCID, where TCID is 20 and LCID is 2.

[0222] Table 8

[0223]

[0224] It should be understood that when the first node forwards a packet, if a corresponding route is not found in the first node's routing table, the packet can be sent to the default destination address. For example, combining... Figure 5 Node A needs to send a message to Node H, but since Node A's routing table does not contain a route to Node H (e.g., Node H's SLNA, L2ID of Node H's interface), Node A can obtain the default route information. Assuming the L2ID of the next-hop node's interface in the default route information is the L2ID of Node B's interface, then Node A can forward the message intended for Node H to Node B.

[0225] As can be seen, because the first node adds default route information to its routing table, if it cannot find a corresponding route in its routing table when forwarding a packet, it can send the packet to the default destination address. This allows the first node to maintain fewer routes, saving memory and energy, and also facilitates its movement between different intermediate nodes. Furthermore, it avoids packet loss and improves the reliability of data transmission.

[0226] The methods of the embodiments of this application have been described in detail above, and the apparatus of the embodiments of this application is provided below.

[0227] This application also provides an apparatus for implementing any of the above methods. For example, a communication apparatus is provided that includes a unit (or means) for implementing the steps performed by the first node in any of the above methods.

[0228] For example, see Figure 6 , Figure 6 This is a schematic diagram of the structure of a communication device 60 provided in an embodiment of this application. The communication device 60 includes a processing unit 601 and a transceiver unit 602, for example implementing... Figure 4 The communication method of any of the embodiments shown.

[0229] It should be understood that the division of units in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units in the device can be implemented by a processor calling software; for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of each unit in the device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units in the device can be implemented as hardware circuits. The functionality of some or all units can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the above units is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the above units. All units of the above device can be implemented entirely through processor-invoked software, entirely through hardware circuits, or partially through processor-invoked software with the remaining parts implemented through hardware circuits.

[0230] In this application embodiment, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a type of microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships of hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement some or all of the functions of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), Tensor Processing Unit (TPU), Deep Learning Processing Unit (DPU), etc.

[0231] As can be seen, each unit in the above device can be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0232] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together as a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the units in the device. The at least one processor may be of different types, such as CPU and FPGA, CPU and artificial intelligence processor, CPU and GPU, etc.

[0233] Regardless of whether these functional modules are subdivided or combined, the general flow executed by device 60 during communication remains the same. For example, the transceiver unit 602 in device 60 can also be called a communication unit. Typically, each unit corresponds to its own program code (or program instructions). When these program codes are run on the processor, they cause the unit to execute the corresponding flow to achieve the corresponding function. It should be noted that the implementation of each unit described below can be referred to accordingly. Figure 4 The corresponding description of the illustrated embodiment.

[0234] In one possible implementation, the communication device 60 can be Figure 4 The first node in the illustrated embodiment, or a module within the first node, such as a chip or integrated circuit, is used. The communication device includes a processing unit 601 and a transceiver unit 602, the details of which are as follows:

[0235] The transceiver unit 602 is configured to: acquire logical channel information corresponding to preset QoS parameters, wherein the logical channel information is used to establish a logical transmission channel between the first node and the second node, wherein the second node is a neighbor node of the first node, and the logical transmission channel is used to provide QoS guarantees for the packets corresponding to the preset QoS parameters; receive a first packet sent by the second node, wherein the first packet includes at least one of the following: the second node's StarNetwork Address (SLNA) and the second node's Interface Layer 2 Identifier (L2ID); and conduct network layer communication with the second node based on the logical channel information, the second node's SLNA, and the second node's Interface L2ID.

[0236] Optionally, the logical channel information includes at least one of the following: Transmission Channel Identifier (TCID) and Logical Channel Identifier (LCID).

[0237] Optionally, the transceiver unit 602 is used to communicate with the second node at the network layer based on logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node. The transceiver unit 602 is used to establish a forwarding table based on logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node. The forwarding table includes at least one of the following: logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node, and the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node correspond one-to-one.

[0238] Optionally, the forwarding table may also include the link quality level in the transmission direction from the first node to the second node, which indicates the link quality in the transmission direction from the first node to the second node.

[0239] Optionally, the link quality level is included in the first message.

[0240] Optionally, the first message may also include the area address of the second node, which is an intermediate node. The area address of the second node is used to indicate that the area where the second node is located is a level 1 area and / or a level 2 area; wherein, the level 2 area is used to connect to the level 1 area.

[0241] Optionally, Level 1 regions are non-backbone regions, and Level 2 regions are backbone regions.

[0242] Optionally, the area address of the second node belongs to the address range of a level 1 area, and the area address of the second node is used to indicate that the area where the second node is located is a level 1 area; the area address of the second node belongs to the address range of a level 2 area, and the area address of the second node is used to indicate that the area where the second node is located is a level 2 area; the area address of the second node belongs to the address range of both level 1 and level 2 areas, and the area address of the second node is used to indicate that the area where the second node is located is an overlapping area of ​​level 1 and level 2 areas.

[0243] Optionally, the first message may also be used to indicate the type of the second node.

[0244] Optionally, the first message includes a first type length value (TLV) field, which includes at least one of the following: the SLNA of the second node and the L2ID of the interface of the second node.

[0245] Optionally, one or more SLNAs of the second node correspond to the L2ID of an interface of the second node.

[0246] Optionally, the first message may also include a second TLV field, which includes the link quality level.

[0247] Optionally, the first message may also include a third TLV field, which includes a length field and at least one area address field corresponding to the length field. The length field is used to indicate the total length of at least one area address field, and the area address field is used to indicate an area address of the second node.

[0248] Optionally, the first message may also include a fourth TLV field, which indicates the authentication algorithm used by the second node, or the fourth TLV field indicates the authentication algorithm and authentication key used by the second node.

[0249] Optionally, the first node is an end node, the second node is an intermediate node, and the communication device 60 further includes a processing unit 601, which is used to add default routing information to the routing table of the first node. The default routing information includes at least one of the following: default destination address, the outgoing interface of the first node, the L2ID of the interface of the next hop node, and logical channel information; wherein, the next hop node is the second node.

[0250] See Figure 7 , Figure 7 This is a schematic diagram of the structure of a communication device 70 provided in an embodiment of this application. The device 70 may include at least one memory 701 and at least one processor 702. Optionally, it may also include a bus 703. Further optionally, it may also include a communication interface 704, wherein the memory 701, the processor 702 and the communication interface 704 are connected through the bus 703.

[0251] The memory 701 provides storage space, which can store data such as the operating system and computer programs. The memory 701 can be one or a combination of several of the following: random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0252] Processor 702 is a module that performs arithmetic and / or logical operations. Specifically, it can be one or a combination of processing modules such as a central processing unit (CPU), graphics processing unit (GPU), microprocessor unit (MPU), application specific integrated circuit (ASIC), field programmable gate array (FPGA), and complex programmable logic device (CPLD).

[0253] The communication interface 704 is used to receive and / or transmit data to external sources. It can be a wired link interface, such as an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission, etc.). Optionally, the communication interface 704 may also include a transmitter (such as an RF transmitter, antenna, etc.) or a receiver coupled to the interface.

[0254] The processor 702 in the device 70 is used to read the computer program stored in the memory 701 and to execute the aforementioned communication method, for example... Figure 4 The communication method described in any of the embodiments.

[0255] In some possible implementations, the communication device 70 can be Figure 4 The first node in the illustrated embodiment, or a module within the first node, such as a chip or integrated circuit, is used by the processor 702 in the device 70 to read a computer program stored in the memory 701 to perform the following operations:

[0256] Obtain logical channel information corresponding to preset QoS parameters. The logical channel information is used to establish a logical transmission channel between the first node and the second node. The second node is a neighbor node of the first node. The logical transmission channel is used to provide QoS guarantee for the packets corresponding to the preset QoS parameters. Receive a first packet sent by the second node. The first packet includes at least one of the following: the second node's StarNet address (SLNA) and the second node's interface layer 2 identifier (L2ID). Based on the logical channel information, the second node's SLNA, and the second node's interface layer 2 identifier (L2ID), conduct network layer communication with the second node.

[0257] Optionally, the logical channel information includes at least one of the following: Transmission Channel Identifier (TCID) and Logical Channel Identifier (LCID).

[0258] Optionally, the processor 1202 is specifically used to perform the following operations: establish a forwarding table based on logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node; wherein the forwarding table includes at least one of the following: logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node, and the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node correspond one-to-one.

[0259] Optionally, the forwarding table may also include the link quality level in the transmission direction from the first node to the second node, which indicates the link quality in the transmission direction from the first node to the second node.

[0260] Optionally, the link quality level is included in the first message.

[0261] Optionally, the first message may also include the area address of the second node, which is an intermediate node. The area address of the second node is used to indicate that the area where the second node is located is a level 1 area and / or a level 2 area; wherein, the level 2 area is used to connect to the level 1 area.

[0262] Optionally, Level 1 regions are non-backbone regions, and Level 2 regions are backbone regions.

[0263] Optionally, the area address of the second node belongs to the address range of a level 1 area, and the area address of the second node is used to indicate that the area where the second node is located is a level 1 area; the area address of the second node belongs to the address range of a level 2 area, and the area address of the second node is used to indicate that the area where the second node is located is a level 2 area; the area address of the second node belongs to the address range of both level 1 and level 2 areas, and the area address of the second node is used to indicate that the area where the second node is located is an overlapping area of ​​level 1 and level 2 areas.

[0264] Optionally, the first message may also be used to indicate the type of the second node.

[0265] Optionally, the first message includes a first type length value (TLV) field, which includes at least one of the following: the SLNA of the second node and the L2ID of the interface of the second node.

[0266] Optionally, one or more SLNAs of the second node correspond to the L2ID of an interface of the second node.

[0267] Optionally, the first message may also include a second TLV field, which includes the link quality level.

[0268] Optionally, the first message may also include a third TLV field, which includes a length field and at least one area address field corresponding to the length field. The length field is used to indicate the total length of at least one area address field, and the area address field is used to indicate an area address of the second node.

[0269] Optionally, the first message may also include a fourth TLV field, which indicates the authentication algorithm used by the second node, or the fourth TLV field indicates the authentication algorithm and authentication key used by the second node.

[0270] Optionally, the first node is an end node and the second node is an intermediate node. The processor 1202 is also used to perform the following operations: add default route information to the routing table of the first node. The default route information includes at least one of the following: default destination address, the outgoing interface of the first node, the L2ID of the interface of the next hop node, and logical channel information; wherein, the next hop node is the second node.

[0271] This application provides a computer storage medium storing a computer program. When the computer program is run on a computer, it causes the computer to perform actions such as... Figure 4 The method described in any one of the following statements.

[0272] This application provides a chip including a processor and a communication interface. The processor is used to call and execute instructions from the communication interface. When the processor executes the instructions, it implements, for example... Figure 4 The method described in any one of the following statements.

[0273] This application provides a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform actions such as... Figure 4 The method described in any one of the following statements.

[0274] When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application can be implemented. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted through a computer-readable storage medium. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. Available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks (SSDs)).

[0275] The steps in the method embodiments of this application can be adjusted, combined, or deleted according to actual needs.

[0276] The modules in the device embodiments of this application can be merged, divided, and deleted according to actual needs.

Claims

1. A communication method, characterized in that, include: The first node obtains logical channel information corresponding to the preset QoS parameters. The logical channel information is used to establish a logical transmission channel between the first node and the second node. The second node is a neighbor node of the first node. The logical transmission channel is used to provide QoS guarantee for the packets corresponding to the preset QoS parameters. The first node receives a first message sent by the second node, the first message including at least one of the following: the StarNet address (SLNA) of the second node, and the Layer 2 identifier (L2ID) of the interface of the second node; The first node communicates with the second node at the network layer based on the logical channel information, the second node's SLNA, and the L2ID of the second node's interface.

2. The method according to claim 1, characterized in that, The logical channel information includes at least one of the following: Transmission Channel Identifier (TCID) and Logical Channel Identifier (LCID).

3. The method according to claim 2, characterized in that, The first node communicates with the second node at the network layer based on the logical channel information, the second node's SLNA, and the L2ID of the second node's interface, including: The first node establishes a forwarding table based on the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node; The forwarding table includes at least one of the following: the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node, wherein the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node correspond one-to-one.

4. The method according to claim 3, characterized in that, The forwarding table also includes a link quality level in the transmission direction from the first node to the second node, the link quality level being used to indicate the link quality in the transmission direction from the first node to the second node.

5. The method according to claim 4, characterized in that, The link quality level is included in the first message.

6. The method according to any one of claims 1-5, characterized in that, The first message also includes the area address of the second node, where the second node is an intermediate node, and the area address of the second node is used to indicate that the area where the second node is located is a level 1 area and / or a level 2 area; The level 2 region is used to connect the level 1 region.

7. The method according to claim 6, characterized in that, The Level 1 region is a non-backbone region, and the Level 2 region is a backbone region.

8. The method according to claim 6, characterized in that, The area address of the second node belongs to the address range of the level 1 area, and the area address of the second node is used to indicate that the area where the second node is located is the level 1 area; The area address of the second node belongs to the address range of the level 2 area, and the area address of the second node is used to indicate that the area where the second node is located is the level 2 area; The area address of the second node belongs to the address range of the level 1 area and the level 2 area. The area address of the second node is used to indicate that the area where the second node is located is the overlapping area of ​​the level 1 area and the level 2 area.

9. The method according to claim 6, characterized in that, The first message is also used to indicate the type of the second node.

10. The method according to claim 1, characterized in that, The first message includes a first type length value (TLV) field, and the first TLV field includes at least one of the following: the SLNA of the second node and the L2ID of the interface of the second node.

11. The method according to claim 10, characterized in that, One or more SLNAs of the second node correspond to the L2ID of one interface of the second node.

12. The method according to claim 5, characterized in that, The first message also includes a second TLV field, which includes the link quality level.

13. The method according to claim 6, characterized in that, The first message also includes a third TLV field, which includes a length field and at least one area address field corresponding to the length field. The length field is used to indicate the total length of the at least one area address field, and the area address field is used to indicate an area address of the second node.

14. The method according to claim 10, 12, or 13, characterized in that, The first message also includes a fourth TLV field, which is used to indicate the authentication algorithm used by the second node, or the fourth TLV field is used to indicate the authentication algorithm and authentication key used by the second node.

15. The method according to any one of claims 1-5 and 7-13, characterized in that, The first node is an end node, the second node is an intermediate node, and the method further includes: The first node adds default route information to its routing table. The default route information includes at least one of the following: default destination address, the outgoing interface of the first node, the L2ID of the interface of the next hop node, and the logical channel information. The next hop node is the second node.

16. A communication device, characterized in that, The communication device is a first node, and the communication device includes a transceiver unit, which is used for: Obtain logical channel information corresponding to preset QoS parameters. The logical channel information is used to establish a logical transmission channel between the first node and the second node. The second node is a neighbor node of the first node. The logical transmission channel is used to provide QoS guarantee for the packets corresponding to the preset QoS parameters. Receive a first message sent by the second node, the first message including at least one of the following: the StarNet address (SLNA) of the second node, and the Layer 2 identifier (L2ID) of the interface of the second node; Based on the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node, network layer communication is performed with the second node.

17. The apparatus according to claim 16, characterized in that, The logical channel information includes at least one of the following: Transmission Channel Identifier (TCID) and Logical Channel Identifier (LCID).

18. The apparatus according to claim 17, characterized in that, The transceiver unit is used to perform network layer communication with the second node based on the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node, including: The transceiver unit is used to establish a forwarding table based on the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node; The forwarding table includes at least one of the following: the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node, wherein the logical channel information, the SLNA of the second node, and the L2ID of the interface of the second node correspond one-to-one.

19. The apparatus according to claim 18, characterized in that, The forwarding table also includes a link quality level in the transmission direction from the first node to the second node, the link quality level being used to indicate the link quality in the transmission direction from the first node to the second node.

20. The apparatus according to claim 19, characterized in that, The link quality level is included in the first message.

21. The apparatus according to any one of claims 16-20, characterized in that, The first message also includes the area address of the second node, where the second node is an intermediate node, and the area address of the second node is used to indicate that the area where the second node is located is a level 1 area and / or a level 2 area; The level 2 region is used to connect the level 1 region.

22. The apparatus according to claim 21, characterized in that, The Level 1 region is a non-backbone region, and the Level 2 region is a backbone region.

23. The apparatus according to claim 21, characterized in that, The area address of the second node belongs to the address range of the level 1 area, and the area address of the second node is used to indicate that the area where the second node is located is the level 1 area; The area address of the second node belongs to the address range of the level 2 area, and the area address of the second node is used to indicate that the area where the second node is located is the level 2 area; The area address of the second node belongs to the address range of the level 1 area and the level 2 area. The area address of the second node is used to indicate that the area where the second node is located is the overlapping area of ​​the level 1 area and the level 2 area.

24. The apparatus according to claim 21, characterized in that, The first message is also used to indicate the type of the second node.

25. The apparatus according to claim 16, characterized in that, The first message includes a first type length value (TLV) field, and the first TLV field includes at least one of the following: the SLNA of the second node and the L2ID of the interface of the second node.

26. The apparatus according to claim 25, characterized in that, One or more SLNAs of the second node correspond to the L2ID of one interface of the second node.

27. The apparatus according to claim 19, characterized in that, The first message also includes a second TLV field, which includes the link quality level.

28. The apparatus according to claim 21, characterized in that, The first message also includes a third TLV field, which includes a length field and at least one area address field corresponding to the length field. The length field is used to indicate the total length of the at least one area address field, and the area address field is used to indicate an area address of the second node.

29. The apparatus according to claim 25, 27, or 28, characterized in that, The first message also includes a fourth TLV field, which is used to indicate the authentication algorithm used by the second node, or the fourth TLV field is used to indicate the authentication algorithm and authentication key used by the second node.

30. The apparatus according to any one of claims 16-20 and 24-28, characterized in that, The first node is an end node, the second node is an intermediate node, and the communication device further includes a processing unit. The processing unit is used to add default routing information to the routing table of the first node. The default routing information includes at least one of the following: default destination address, the outgoing interface of the first node, the L2ID of the interface of the next hop node, and the logical channel information. The next hop node is the second node.

31. A communication device, characterized in that, include: Processor and memory; The memory is used to store one or more programs, the one or more programs including computer-executable instructions, wherein when the device is running, the processor executes the one or more programs stored in the memory to cause the device to perform the method as described in any one of claims 1-15.

32. A computer storage medium, characterized in that, The computer storage medium stores a computer program that, when run on the computer, causes the computer to perform the method as described in any one of claims 1-15.

33. A chip, characterized in that, The chip includes a processor and a communication interface. The processor is used to call and execute instructions from the communication interface. When the processor executes the instructions, it implements the method as described in any one of claims 1-15.

Citation Information

Patent Citations

  • Data packet transmission method based on network service quality and related equipment

    CN113630902A

  • Information flooding method and equipment

    CN114793208A