A routing method and apparatus

Abstract

This application discloses a routing method and apparatus, which can be applied to multi-hop communication scenarios, but also to other scenarios. Specifically, the method and apparatus are used to implement routing between an AN device and a remote UE in a multi-hop communication scenario. In this method, a relay terminal in the communication link can determine the transmission target by using routing indication information of the data packet, or the routing indication information of the data packet and the target device identifier, thereby transmitting the data carried in the data packet to the transmission target. Clearly, this method can guide the routing transmission of data packets through routing guidance information, thus ensuring routing between the AN device and the remote UE in a multi-hop communication scenario.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a routing method and apparatus. Background Technology

[0002] UE-to-network relay (U2N) technology is a technique that can effectively improve cell coverage. A U2N system includes access network (AN) equipment and two types of terminal equipment: relay UEs and remote UEs. A relay UE can help a remote UE access the AN equipment to obtain services. For example, in the downlink direction, the relay UE can obtain downlink data from the remote UE from the AN equipment and forward it to the remote UE; in the uplink direction, the relay UE obtains uplink data from the remote UE and forwards it to the AN equipment.

[0003] Currently, considering that a relay UE can provide relay services to multiple remote UEs simultaneously, in order to enable the relay UE to clearly distinguish each remote UE during data transmission, a local identifier (local ID) can be assigned to each remote UE. The local identifier can uniquely identify a remote UE within the relay UE's scope. In this way, the UE-to-network relay system can add the remote UE's local identifier to the data packets to be transmitted, thereby achieving routing between the AN device and the remote UE. Taking the downlink transmission direction as an example, the AN device can add the target remote UE's local identifier to the data packets to be sent to the target remote UE. After the relay UE obtains the data packet from the AN device, it can determine the destination device of the data packet as the target remote UE based on the target remote UE's local identifier, and then send the data packet to the target remote UE.

[0004] However, in complex multi-hop U2N systems, how to complete the routing between the AN device and these remote UEs connected to the base station through multi-hop relay UEs is an urgent problem to be solved. Summary of the Invention

[0005] This application provides a routing method and apparatus, which can be applied to multi-hop communication scenarios, but can also be used in other scenarios. In particular, the method and apparatus are used to implement routing between an AN device and a remote UE in a multi-hop communication scenario.

[0006] Firstly, embodiments of this application provide a routing method applied to a first relay terminal. This method can be executed by the first relay terminal, or by components such as chips, processors, or chip systems within the first relay terminal. The following describes the method in detail using the execution of the first relay terminal as an example. The method includes the following steps:

[0007] After receiving the first data packet, the first relay terminal obtains the first routing indication information and the target device identifier of the first data packet, wherein the first routing indication information is used to indicate the transmission route of the first data packet; the target device indicated by the target device identifier is the destination device or the source device of the first data packet; the first relay terminal determines the first device according to the first routing indication information, or according to the first routing indication information and the target device identifier; the first relay terminal transmits a second data packet to the first device, wherein the data carried by the second data packet is the same as the data carried by the first data packet.

[0008] Using this method, the first relay terminal can determine the transmission target based on the first routing indication information of the received first data packet and the target device identifier of the first data packet, thereby transmitting the data in the first data packet to the transmission target. Clearly, this method can guide the routing transmission of data packets using routing indication information, or routing indication information and target device identifier, thus ensuring routing between the AN device and the remote UE in multi-hop communication scenarios.

[0009] In one possible design, the first relay terminal can obtain the first routing indication information and the target device identifier in the following way:

[0010] Method 1: The first data packet has a first protocol layer header, which contains the first routing indication information and the target device identifier; the first routing indication information and the target device identifier are obtained from the first protocol layer header of the first data packet;

[0011] Method 2: When the first data packet is received from the first remote terminal, the first data packet does not have a first protocol layer header; the first routing indication information is determined to be the saved routing indication information corresponding to the first remote terminal, and the target device identifier is determined to be the device identifier of the first remote terminal;

[0012] Method 3: When the first data packet is received from the first remote terminal, the first data packet has a first protocol layer, and the first protocol layer header does not contain the first routing indication information and the target device identifier; the first routing indication information is determined to be the saved routing indication information corresponding to the first remote terminal, and the target device identifier is determined to be the device identifier of the first remote terminal.

[0013] In Method 1, when the first data packet has a first protocol layer header, the first relay terminal can directly obtain the first routing indication information and the target device identifier from the first protocol layer header of the first data packet. In Method 2 or Method 3, when the first relay terminal is a trailing relay terminal receiving the first data packet from a first remote terminal, the first relay terminal can determine the first routing indication information and the target device identifier based on the first remote terminal. Through this design, the first relay terminal can obtain the first routing indication information and the target device identifier in various situations and scenarios.

[0014] In one possible design, the first relay terminal can also obtain routing indication information corresponding to the first remote terminal from the access network device; wherein, the routing indication information corresponding to the first remote terminal is dedicated routing indication information or default routing indication information for the first remote terminal. Thus, when the first relay terminal receives a data packet from the first remote terminal, it can obtain the routing indication information for that data packet.

[0015] In one possible design, the routing indication information corresponding to the first remote terminal contains multiple routing indication information that correspond to different bearers; in this case, the first relay terminal can determine that the first routing indication information is the routing indication information corresponding to the first remote terminal through the following steps:

[0016] Determine the target bearer used to transmit the first data packet; determine the first routing indication information as: the routing indication information in the routing indication information corresponding to the first remote terminal that has a corresponding relationship with the target bearer.

[0017] Through this design, the communication system can allocate multiple routing indication information to the first remote terminal at the bearer level; and determine the first routing indication information based on the bearer used to transmit the first data packet to the first remote terminal.

[0018] In one possible design, the first routing indication information includes a destination address; the first data packet has a first protocol layer header; in this case, the first relay terminal can determine the first device in the following way:

[0019] Method 1: When the destination address is different from the address of the first relay terminal, determine the next-hop node address corresponding to the first routing indication information; determine that the first device is the next-hop node indicated by the next-hop node address;

[0020] Method 2: When the destination address is the same as the address of the first relay terminal, the device indicated by the target device identifier is determined to be the first device;

[0021] Method 3: When the destination address is the same as the address of the first relay terminal, and the first relay terminal is the first relay terminal connected to the access network device, determine the interface used to receive the first data packet; when the interface is a Uu interface, determine that the device indicated by the target device identifier is the first device; when the interface is a PC5 interface, determine that the first device is the access network device.

[0022] In the method provided in this design, the address of the relay terminal can be used as routing indication information to guide the routing of data packets, thereby ensuring routing between the AN device and the remote UE in multi-hop communication scenarios.

[0023] In one possible design, when the first device is the next-hop node or the access network device, the second data packet is the same as the first data packet.

[0024] With this design, the first relay device can transmit the first data packet to the determined transmission object when it is determined that the transmission object is a next-hop node or an access network device.

[0025] In one possible design, the first routing indication information also includes a target path identifier.

[0026] In one possible design, the first routing indication information includes a destination path identifier; the first data packet has the first protocol layer header; in this case, the first relay terminal can determine the first device in the following way:

[0027] Method 1: When the first routing indication information has a corresponding next-hop node device identifier, the first device is determined based on the next-hop node device identifier;

[0028] Method 2: When the first routing indication information does not have a corresponding next-hop node device identifier, the device indicated by the target device identifier is determined to be the first device.

[0029] Through this design, the first relay terminal can determine the transmission object in different ways depending on whether the first routing indication information has a corresponding next-hop node device identifier.

[0030] In one possible design, the first relay terminal can determine the first device based on the next-hop node device identifier in the following way:

[0031] Method 1: When the next-hop node device identifier indicates that the first relay terminal is connected to the second relay terminal, the first device is determined to be the second relay terminal;

[0032] Method 2: When the next-hop node device identifier indicates an access network device, the first device is determined to be the access network device;

[0033] Method 3: When the next-hop node device identifier indicates the first relay terminal, the device indicated by the target device identifier is determined to be the first device.

[0034] Through this design, the first relay terminal can identify different transmission objects when the next-hop node device identifier indicates different communication devices.

[0035] In one possible design, when the next-hop node device identifier is a first default device identifier, the next-hop node device identifier indicates the first relay terminal; when the next-hop node device identifier is a second default device identifier, the next-hop node device identifier indicates the access network device.

[0036] In one possible design, when the first device is the second relay terminal or the access network device, the second data packet is the same as the first data packet.

[0037] With this design, the first relay device can transmit the first data packet to the determined transmission object when it determines that the transmission object is a second relay terminal or access network device to which it is connected.

[0038] In one possible design, the first routing indication information may further include a transmission direction indication, which indicates whether the transmission is uplink or downlink.

[0039] In one possible design, the first relay device can determine that the device indicated by the target device identifier is the first device by the following steps: when the target device identifier indicates a first remote terminal connected to the first relay terminal, the first device is determined to be the first remote terminal. In this case, the first relay terminal can transmit the second data packet to the first device by the following steps:

[0040] The first data packet is decapsulated to obtain the second data packet, wherein the second data packet does not have a first protocol layer header; the second data packet is then transmitted to the first remote terminal.

[0041] With this design, the first relay terminal can transmit data packets without a protocol header to the first remote terminal.

[0042] In one possible design, the first protocol layer header further includes a bearer identifier, which indicates the target bearer used to transmit the first data packet. The first relay device can determine that the device indicated by the target device identifier is the first device by the following steps: when the target device identifier indicates a first remote terminal accessing the first relay terminal, the first device is determined to be the first remote terminal. In this case, the first relay terminal can transmit the second data packet to the first device in the following manner:

[0043] Method 1: Delete the first routing indication information and the target device identifier contained in the first protocol layer of the first data packet to obtain the second data packet, wherein the first protocol layer header of the second data packet contains the bearer identifier; transmit the second data packet to the first device;

[0044] Method 2: Decapsulate the first data packet to obtain a target data packet; wherein the target data packet does not have a first protocol layer header; add a first protocol layer header to the target data packet to generate a second data packet, wherein the first protocol layer header of the second data packet contains the bearer identifier; transmit the second data packet to the first device;

[0045] Method 3: Transmit the second data packet, which is the same as the first data packet, to the first device.

[0046] Using methods one and two, the first relay terminal can transmit a second data packet to the first device whose first protocol layer header contains only a bearer identifier. Using method three, the first relay terminal can transmit the first data packet to the first device.

[0047] In one possible design, when the target device identifier indicates the first relay terminal, the first relay terminal can also determine that the data carried in the first data packet is the data of the first relay terminal.

[0048] In one possible design, when the target device identifier is a third default device identifier, the target device identifier indicates the first relay terminal.

[0049] In one possible design, when the first data packet does not have a first protocol layer header, the first relay terminal can transmit the second data packet to the first device through the following steps:

[0050] A first protocol layer header is added to the first data packet to generate the second data packet; wherein the first protocol layer header of the second data packet contains the first routing indication information and the target device identifier; the second data packet is transmitted to the first device.

[0051] With this design, the first relay terminal can transmit a second data packet carrying a first protocol layer header to the first device.

[0052] In one possible design, when the first relay terminal is connected to the access network device through the second relay terminal, the first relay terminal can also generate a third data packet, wherein the third data packet does not contain a first protocol layer header; and transmit the third data packet to the second relay terminal; or generate a fourth data packet and transmit the fourth data packet to the second relay terminal through the following steps:

[0053] Determine the second routing indication information of the third data packet; add a first protocol layer header to the third data packet to generate a fourth data packet; wherein the first protocol layer header of the fourth data packet contains the second routing indication information and the device identifier of the first relay terminal.

[0054] With this design, the first relay terminal can transmit its own data packets carrying the first protocol layer header, or data packets without the first protocol layer header, to the second relay terminal.

[0055] In one possible design, the device identifier of the first relay terminal is assigned to the first relay terminal by the second relay terminal; or, the device identifier of the first relay terminal is assigned to the second relay terminal by the first relay terminal; or the device identifier of the first relay terminal is a first default device identifier.

[0056] In one possible design, the first relay terminal may use a first logical channel to transmit the second data packet to the first device; the first relay device may use a second logical channel to transmit the third data packet to the second relay terminal; wherein the first logical channel is different from the second logical channel.

[0057] With this design, the first relay terminal can use different logical channels to transmit data packets carrying the first protocol layer header and data packets without the first protocol layer header, respectively, so as to distinguish the type of data packets through the logical channels, thereby enabling the transmission object to perform differentiated processing on the received data packets according to the logical channels.

[0058] In one possible design, when the first data packet has a first protocol layer header, and the first protocol layer header contains a bearer identifier but does not contain the first routing indication information and the target device identifier, the first relay terminal can obtain the second data packet in the following way:

[0059] Method 1: Add the first routing indication information and the target device identifier to the first protocol layer header of the first data packet to obtain the second data packet. The first protocol layer header of the second data packet contains the bearer identifier, the first routing indication information, and the target device identifier.

[0060] Method 2: Decapsulate the first data packet to obtain the target data packet; wherein the target data packet does not have a first protocol layer header; add a first protocol layer header to the target data packet to generate the second data packet, wherein the first protocol layer header of the second data packet contains the bearer identifier, the first routing indication information and the target device identifier.

[0061] With this design, the first relay terminal can transmit a second data packet containing first routing indication information and a target device identifier in the header of the first protocol layer to the first device, so that the first device can continue to transmit the second data packet according to the first routing indication information and the target device identifier.

[0062] In one possible design, the first relay terminal can determine the next-hop node address corresponding to the first routing indication information through the following steps:

[0063] Among the at least one saved routing information, target routing information containing the first routing indication information is determined; wherein the target routing information contains the first routing indication information and the next-hop node address corresponding to the first routing indication information; the next-hop node address corresponding to the first routing indication information is determined in the target routing information.

[0064] With this design, the first relay terminal can determine the next-hop node address corresponding to the first routing indication information based on the saved routing information.

[0065] In one possible design, when the first relay terminal determines that the first routing indication information has a corresponding next-hop node device identifier when it determines that the target routing information includes the first routing indication information, the target routing information includes the first routing indication information and the next-hop node device identifier corresponding to the first routing indication information; or when the first relay terminal determines that the first routing indication information does not have a corresponding next-hop node device identifier when it does not find the target routing information, the first relay terminal may be among the at least one saved routing information.

[0066] With this design, the first relay terminal can determine whether the first routing indication information has a next-hop node device identifier based on whether the target routing information is found.

[0067] In one possible design, the first relay terminal can obtain the at least one routing information in the following way:

[0068] Method 1: Obtain at least one routing information from the access network device;

[0069] Method 2: When the first relay terminal is connected to the access network device through the second relay terminal, the at least one routing information is obtained from the second relay terminal.

[0070] This design allows the communication system to flexibly configure the routing information of the first relay terminal.

[0071] In one possible design, the target device is identified as either a local ID or a Layer 2 ID.

[0072] Secondly, embodiments of this application provide a routing method applied in an access network device. This method can be executed by the access network device itself, or by components such as chips, processors, or chip systems within the access network device. The following describes the method in detail using an example of execution by an access network device, comprising the following steps:

[0073] The access network device acquires a first data packet, which does not have a first protocol layer header. The access network device determines first routing indication information and a first target device identifier for the first data packet, wherein the first target device indicated by the first target device identifier is the destination device of the first data packet, and the first routing indication information is used to indicate the transmission route of the first data packet. The access network device adds a first protocol layer header to the first data packet to generate a second data packet. The first protocol layer header of the second data packet contains the first routing indication information and the first target device identifier. The access network device determines a relay terminal based on the first routing indication information and transmits the second data packet to the relay terminal.

[0074] Using this method, the access network device can determine the transmission target based on the first routing indication information of the first data packet, and thus transmit the data in the first data packet to the transmission target. Clearly, the access network device can use routing indication information to guide the routing of data packets, thereby ensuring routing between the AN device and the remote UE in multi-hop communication scenarios.

[0075] In one possible design, the access network device can also receive a third data packet sent by the relay terminal; wherein the third data packet has a first protocol layer header, and the first protocol layer header of the third data packet contains second routing indication information and a second target device identifier; the second target device indicated by the second target device identifier is the source device of the third data packet, and the second routing indication information is used to indicate the transmission route of the third data packet; the access network device decapsulates the third data packet to obtain a fourth data packet, and the fourth data packet does not have a first protocol layer header.

[0076] In one possible design, the access network device may further determine a first bearer identifier for the first data packet; wherein the first bearer identifier is used to indicate a first bearer used to transmit the first data packet; and the first protocol layer header of the second data packet further includes the first bearer identifier.

[0077] In this design, the first protocol layer header of the second data packet transmitted by the access network device also includes a first bearer identifier.

[0078] In one possible design, the first protocol layer header of the third data packet also includes a second bearer identifier, which is used to indicate the second bearer used to transmit the third data packet.

[0079] Thirdly, embodiments of this application provide a routing method applied in a remote terminal. This method can be executed by the remote terminal itself, or by components such as chips, processors, or chip systems within the remote terminal. The following describes the method in detail using an example of execution by a remote terminal. The method includes the following steps:

[0080] After the remote terminal obtains the first data packet, it determines the first routing indication information and the target device identifier of the first data packet. The first routing indication information of the first data packet is used to indicate the transmission route of the first data packet. The target device identifier is the device identifier of the remote terminal. The remote terminal adds a first protocol layer header to the first data packet to generate a second data packet. The first protocol layer header of the second data packet contains the first routing indication information and the first target device identifier. The remote terminal sends the second data packet to the relay terminal.

[0081] Using this method, the remote terminal can transmit a second data packet containing a first routing indication information and a target device identifier in the protocol layer header to the relay terminal, enabling the relay terminal to determine the transmission target based on the first routing indication information and the target device identifier. Clearly, the remote terminal can use the routing indication information to guide the routing of data packets, thereby ensuring routing between the remote UE and the AN device in multi-hop communication scenarios.

[0082] In one possible design, the remote terminal can also receive a third data packet from the relay terminal, wherein the third data packet has a first protocol layer header, the first protocol layer header of the third data packet includes second routing indication information and the target device identifier; the second routing indication information is used to indicate the transmission route of the second data packet; the remote terminal decapsulates the third data packet to obtain a fourth data packet, the fourth data packet not having a first protocol layer header.

[0083] In one possible design, the remote terminal may further determine a first bearer identifier for the first data packet; wherein the first bearer identifier is used to indicate a first bearer used to transmit the first data packet; and the first protocol layer header of the second data packet also contains the first bearer identifier.

[0084] With this design, the first protocol layer header of the second data packet transmitted by the remote terminal also includes a first bearer identifier.

[0085] In one possible design, the first protocol layer header of the third data packet also includes a second bearer identifier, which is used to indicate the second bearer used to transmit the third data packet.

[0086] In one possible design, the remote terminal can determine that the first routing indication information is the saved routing indication information corresponding to the first remote terminal.

[0087] In one possible design, the remote terminal may receive routing indication information corresponding to the first remote terminal from the access network device or the relay terminal. The routing indication information corresponding to the first remote terminal may be dedicated routing indication information for the first remote terminal or default routing indication information.

[0088] Fourthly, this application provides a routing method applied to a first relay terminal. This method can be executed by the first relay terminal, or by components such as chips, processors, or chip systems within the first relay terminal. The following describes the method in detail using the execution of the first relay terminal as an example. The method includes the following steps:

[0089] A first relay terminal receives a first data packet, wherein the first data packet has a first protocol layer header, the first protocol layer header includes first routing indication information and a target device identifier, the first routing indication information is used to indicate the transmission route of the first data packet; the target device indicated by the target device identifier is the destination device or the source device of the first data packet; the first relay terminal obtains the first routing indication information and the target device identifier from the first data packet; and determines a first device based on the first routing indication information, or based on the first routing indication information and the target device identifier; the first relay terminal transmits the first data packet to the first device.

[0090] Using this method, the first relay terminal can determine the transmission target based on the first routing indication information of the received first data packet and the target device identifier of the first data packet, thereby transmitting the first data packet to the transmission target. Clearly, this method can guide the routing transmission of data packets using routing indication information, or routing indication and target device identifier, thus ensuring routing between the AN device and the remote UE in multi-hop communication scenarios.

[0091] In one possible design, the first routing indication information includes the destination node address; in this case, the first relay terminal can determine the first device in the following way:

[0092] Method 1: When the target node address is different from the address of the first relay terminal, determine the next-hop node address corresponding to the first routing indication information; determine that the first device is the next-hop node indicated by the next-hop node address;

[0093] Method 2: When the target node address is the same as the address of the first relay terminal, the device indicated by the target device identifier is determined to be the first device;

[0094] Method 3: When the target node address is the same as the address of the first relay terminal, and the first relay terminal is the first relay terminal connected to the access network device, the first relay terminal determines the interface used to receive the first data packet; when the interface is a Uu interface, the device indicated by the target device identifier is determined to be the first device; when the interface is a PC5 interface, the first device is determined to be the access network device.

[0095] In the method provided in this design, the address of the relay terminal can be used as routing indication information to guide the routing of data packets, thereby ensuring routing between the AN device and the remote UE in multi-hop communication scenarios.

[0096] In one possible design, the first routing indication information also includes a target path identifier.

[0097] In one possible design, when the target device identifier indicates a first remote terminal connected to the first relay terminal, the first relay terminal can identify the first device as the first remote terminal.

[0098] In one possible design, when the target device identifier indicates the first relay terminal, the first relay terminal can also determine that the data carried in the first data packet is the data of the first relay terminal.

[0099] In one possible design, when the target device identifier is the default device identifier, the target device identifier indicates the first relay terminal.

[0100] In one possible design, the first relay terminal can determine the next-hop node address corresponding to the first routing indication information through the following steps:

[0101] Among the at least one saved routing information, target routing information containing the first routing indication information is determined; wherein the target routing information contains the first routing indication information and the next-hop node address corresponding to the first routing indication information; the next-hop node address corresponding to the first routing indication information is determined in the target routing information.

[0102] With this design, the first relay terminal can determine the next-hop node address corresponding to the first routing indication information based on the saved routing information.

[0103] In one possible design, the first relay terminal can obtain the at least one routing information in the following way:

[0104] Method 1: Obtain at least one routing information from the access network device;

[0105] Method 2: When the first relay terminal is connected to the access network device through the second relay terminal, the at least one routing information is obtained from the second relay terminal.

[0106] This design allows the communication system to flexibly configure the routing information of the first relay terminal.

[0107] In one possible design, the target device is identified as the target device's local ID.

[0108] In one possible design, the first protocol layer header of the first data packet also includes a bearer identifier; the bearer identifier is used to indicate the first bearer used to transmit the first data packet.

[0109] Fifthly, embodiments of this application provide a communication device including a unit for performing the steps in any of the above aspects.

[0110] In a sixth aspect, embodiments of this application provide a communication device including at least one processing element and at least one storage element, wherein the at least one storage element is used to store programs and data, and the at least one processing element is used to read and execute the programs and data stored in the storage element, so that the methods provided in any of the above aspects of this application are implemented.

[0111] In a seventh aspect, embodiments of this application provide a communication system, including a first relay terminal capable of implementing the method provided in the first aspect, and an access network device capable of implementing the method provided in the second aspect. Optionally, the communication system may further include a remote terminal capable of implementing the method provided in the third aspect.

[0112] Eighthly, embodiments of this application provide a communication system, including a first relay terminal capable of implementing the method provided in the fourth aspect, an access network device capable of implementing the method provided in the second aspect, and a remote terminal capable of implementing the method provided in the third aspect.

[0113] Ninthly, embodiments of this application also provide a computer program that, when run on a computer, causes the computer to perform the method provided in any of the above aspects.

[0114] In a tenth aspect, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a computer, causes the computer to perform the method provided in any of the above aspects.

[0115] Eleventhly, embodiments of this application also provide a chip for reading a computer program stored in a memory and executing the method provided in any of the above aspects.

[0116] In a twelfth aspect, embodiments of this application also provide a chip system including a processor for supporting a computer device in implementing the methods provided in any of the foregoing aspects. In one possible design, the chip system further includes a memory for storing programs and data necessary for the computer device. The chip system may be composed of chips or may include chips and other discrete devices. Attached Figure Description

[0117] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0118] Figure 2 A flowchart illustrating a routing method provided in an embodiment of this application;

[0119] Figure 3 This application provides a flowchart illustrating how an AN device notifies each other of their addresses between two adjacent UEs in a communication link.

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

[0121] Figure 5 This application provides a schematic diagram of a protocol stack for a communication system.

[0122] Figure 6 A schematic diagram illustrating a routing mechanism provided in an embodiment of this application;

[0123] Figure 7 A schematic diagram illustrating a routing mechanism provided in an embodiment of this application;

[0124] Figure 8 A schematic diagram illustrating a routing mechanism provided in an embodiment of this application;

[0125] Figure 9 A flowchart illustrating a routing method provided in an embodiment of this application;

[0126] Figure 10 A flowchart illustrating the configuration of default routing indication information for an AN device, as provided in this application embodiment;

[0127] Figure 11 This application provides a schematic diagram of a protocol stack for a communication system.

[0128] Figure 12 A schematic diagram illustrating a routing mechanism provided in an embodiment of this application;

[0129] Figure 13 A schematic diagram illustrating a routing mechanism provided in an embodiment of this application;

[0130] Figure 14 A schematic diagram illustrating a routing mechanism provided in an embodiment of this application;

[0131] Figure 15 A flowchart illustrating a routing method provided in an embodiment of this application;

[0132] Figure 16 A flowchart illustrating a routing mechanism provided in an embodiment of this application;

[0133] Figure 17 This application provides a schematic diagram of a protocol stack for a communication system.

[0134] Figure 18 This application provides a schematic diagram of a protocol stack for a communication system.

[0135] Figure 19A This is a schematic diagram of a BAP header processing procedure provided in an embodiment of this application;

[0136] Figure 19B This is a schematic diagram of a BAP header processing procedure provided in an embodiment of this application;

[0137] Figure 20 A structural diagram of a communication device provided in an embodiment of this application;

[0138] Figure 21 This is a structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0139] This application provides a routing method and apparatus for routing between an AN device and a remote UE in a multi-hop communication scenario. The method and apparatus are based on the same technical concept. Since the methods and apparatus solve problems based on similar principles, their implementations can be mutually referenced, and repeated details will not be elaborated further.

[0140] The following explanations of some terms used in this application are provided to facilitate understanding by those skilled in the art.

[0141] 1) Access network (AN) equipment is a device in a mobile communication system that connects terminal devices to a wireless network. The AN device, as a node in the radio access network, can also be called a base station, or a radio access network (RAN) node (or device).

[0142] Currently, some examples of AN equipment include: next-generation node B (gNB), transmission reception point (TRP), evolved node B (eNB), radio network controller (RNC), node B (NB), access point (AP), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), or base band unit (BBU), enterprise LTE discrete narrowband aggregation (eLTE-DSA) base station, etc.

[0143] In another network architecture, the AN device may include centralized unit (CU) nodes and distributed unit (DU) nodes. This architecture separates the protocol layers of the network device, with some protocol layer functions centrally controlled by the CU, and the remaining part or all of the protocol layer functions distributed in the DU, which are centrally controlled by the CU.

[0144] 2) A terminal is a device that provides voice and / or data connectivity to a user. A terminal can also be called a terminal device, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. In the embodiments and accompanying drawings of this application, only the UE is used as an example for illustration.

[0145] For example, the terminal can be a handheld device with wireless connectivity, various vehicle-mounted devices, roadside units, etc. Currently, examples of terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), point-of-sale (POS) terminals, wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, head-mounted displays (HMDs), wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, various smart meters (smart water meters, smart electricity meters, smart gas meters), eLTE-DSA UEs, devices with integrated access and backhaul (IAB) capabilities, electronic control units (ECUs), in-vehicle computers, in-vehicle cruise control systems, and telematics systems. (box, T-BOX, etc.)

[0146] 3) The first protocol layer header is a header that differs from existing protocol layer headers (MAC layer, RLC layer, PDCP layer, etc.). For example, the first protocol layer can be an adaptation layer, such as the backhaul adaptation protocol (BAP). The first protocol layer header is an adaptation layer header, such as the BAP header. The following embodiments will only use the BAP header as an example for illustration.

[0147] 4) Transmission direction: The link formed between the terminal side and the network side includes uplink transmission direction and downlink transmission direction. The uplink transmission direction indicates uplink transmission, that is, the terminal side transmits data or messages to the network side; the downlink transmission direction indicates downlink transmission, that is, the network side transmits data or messages to the terminal side.

[0148] 5) Routing indication information, used to indicate the transmission route of data packets (the data carried in the data packets), that is, to guide the transmission / forwarding of data packets, or to guide the transmission of data packets from one device to another. For a single relay UE or AN device, the routing indication information contained in the data packet is used to determine the transmission target, so that the data packet can be transmitted to that transmission target.

[0149] In the uplink transmission direction, in some embodiments provided in this application, routing indication information can guide data packets from a remote UE to an AN device; in other embodiments, routing indication information can guide data packets from the end relay UE in the link to the AN device; in still other embodiments, routing indication information can also guide data packets from the end relay UE in the link to the head relay UE.

[0150] In the downlink transmission direction, in some embodiments provided in this application, routing indication information can guide data packets from the AN device to the remote UE; in other embodiments, routing indication information can guide data packets from the head relay UE / AN device in the link to the tail relay UE. It should be noted that, when the routing indication information can guide transmission to the tail relay UE, if a relay UE in the link determines through the routing indication information that it is not the tail relay UE, it can also combine the target device identifier in the data packet to determine the transmission target, so as to transmit the data packet to the remote UE.

[0151] 6) "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the related objects before and after it are in an "or" relationship.

[0152] It should be noted that "multiple" in this application refers to two or more. "At least one" refers to one or more.

[0153] In addition, it should be understood that in the description of this application, the words "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance or order.

[0154] The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0155] Figure 1 The architecture of a communication system to which the routing method provided in the embodiments of this application is applicable is illustrated. See also... Figure 1 As shown, the system includes: an AN device, and multiple UEs (such as...). Figure 1 (UE1-UE11 in the text).

[0156] The AN device is an entity on the network side that can receive and transmit radio signals. It is responsible for providing radio access-related services to UEs within the cells it manages, and implements physical layer functions, resource scheduling and radio resource management, Quality of Service (QoS) management, radio access control, and mobility management functions.

[0157] The UE is an entity on the user side capable of receiving and transmitting wireless signals, and needs to connect to the AN device to ultimately access the network. The UE can be various devices that provide voice and / or data connectivity to the user.

[0158] To effectively improve the cell coverage of AN equipment, U2N technology is introduced, which allows UEs in the system to access AN equipment through at least one UE, forming single-hop or multi-hop communication. To functionally differentiate UEs, this application introduces the concepts of relay UE and remote UE.

[0159] As a bridging device for remote UEs, a relay UE can establish a connection between one device (remote UE or relay UE) and another device (relay UE or AN device), enabling the two to communicate.

[0160] The remote UE is the initiating device of the service and the destination device that ultimately receives user data or the source device that generates user data. In other words, the remote UE is one endpoint of the communication link (e.g., an RRC connection), and the other endpoint is the AN device.

[0161] In multi-hop communication scenarios, based on the location of the relay UE between the AN device and the remote UE, the multiple relay UEs between the AN device and the remote UE can be divided into three categories:

[0162] Header relay UE, which is a relay UE directly connected to the AN device.

[0163] End-of-line relay UE, which is a relay UE that is directly connected to the remote UE.

[0164] A regular relay UE is a UE between the first relay UE and the last relay UE.

[0165] It should be noted that when the number of relay UEs between the AN device and the remote UE is 2, one of these 2 relay UEs is the head relay UE and the other is the tail relay UE; only when the number of relay UEs between the AN device and the remote UE is greater than or equal to 3, these relay UEs include the above three types of relay UEs.

[0166] For example, in the communication link (link 1) between UE1-UE2-UE3-UE4-AN device, UE1 is the remote UE, UE4 is the head relay UE, UE3 is the ordinary relay UE, and UE2 is the tail relay UE.

[0167] Of course, some UEs can act as relay UEs for other remote UEs on the one hand, and on the other hand, they can act as remote UEs connecting to the AN device through at least one relay UE. For example, although UE2 acts as a relay UE in the above link 1, UE2 is a remote UE in the communication link UE2-UE3-UE4-AN device.

[0168] It should be noted that in the above communication system, the AN device and UE are connected via mobile communication technology. They can connect through an air interface (i.e., the Uu interface) to achieve communication between the UE and the AN device (this communication connection can be called a Uu communication connection or a cellular network communication connection). For example, the AN device is connected to UE4, UE7, and UE8 respectively via the Uu interface.

[0169] Two UEs located close to each other are connected through sidelink (SL) communication technology. They can establish a direct link through the ProSe communication 5 (PC5) interface to communicate with each other (this communication connection can be called SL communication connection).

[0170] Sidelink communication technology is a near-field communication technology that enables direct connection between UEs, also known as proximity services (ProSe) communication technology or device-to-device (D2D) communication technology. In this communication system, two UEs located close to each other and supporting sidelink communication can communicate via a direct link. Sidelink communication technology supports broadcast, multicast, and unicast transmission in scenarios including within cell coverage, outside cell coverage, and partial cell coverage.

[0171] Both the Uu and PC5 interfaces include control plane and user plane protocol stacks. The user plane protocol stacks each contain at least the following protocol layers: physical (PHY) layer, MAC layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, and service data adaptation protocol (SDAP) layer. The control plane protocol stacks each contain at least the following protocol layers: physical layer, MAC layer, RLC layer, PDCP layer, and radio resource control (RRC) layer.

[0172] It should also be pointed out that, such as Figure 1 The communication system shown is an example and does not limit the communication systems to which the methods provided in this application are applicable. In summary, the methods provided in this application are applicable to various communication systems that support multi-hop communication technologies, such as end-to-end (UE to UE, U2U) systems. This application can also be applied to various types and standards of communication systems, such as: 5G communication systems, Long Term Evolution (LTE) communication systems, vehicle to everything (V2X), LTE-vehicle (LTE-V), vehicle to vehicle (V2V), vehicle-to-everything (V2X), machine-type communications (MTC), internet of things (IoT), LTE-machine to machine (LTE-M), machine to machine (M2M), enterprise LTE discrete spectrum aggregation (eLTE-DSA) systems, etc., and are not limited by this application.

[0173] In order to Figure 1 In the multi-hop communication scenario within the communication system shown, routing between the AN device and the remote UE is implemented. This application provides a routing method. Because... Figure 1The communication link (link 1) between UE1-UE2-UE3-UE4-AN devices in the illustrated communication system involves three types of UEs (one head relay UE, one ordinary relay UE, and one tail relay UE). The following embodiments primarily use link 1 as an example for explanation. It is worth noting that the embodiments of this application are not limited to designing only these three types of links, but can also be applied to various other types of links.

[0174] Example 1: The method provided in this application embodiment can also be applied to other links having a head relay UE, multiple ordinary relay UEs, and a tail relay UE. In these links, the steps performed by each ordinary relay UE can refer to the steps performed by UE3 in the following embodiments of this application; the head relay UE can refer to the steps performed by UE4 in the following embodiments of this application; and the tail relay UE can refer to the steps performed by UE2 in the following embodiments of this application.

[0175] Example 2: The method provided in this application embodiment can also be applied to a link having a head relay UE and a tail relay UE. Similar to Example 1, the head relay UE can refer to the steps performed by UE4 in the following embodiments of this application; while the tail relay UE can refer to the steps performed by UE2 in the following embodiments of this application.

[0176] Example 3: The method provided in this application embodiment can also be applied to single-hop communication links, that is, links where the terminal UE accesses the AN device through a relay UE. In these links, the relay UE is both the head relay UE and the tail relay UE, so the steps performed by the relay UE can refer to the steps performed by UE2 and UE4 in the following embodiments.

[0177] Furthermore, it should be noted that each step in the following embodiments can be executed by the corresponding device, or by components such as chips, processors, or chip systems within that device. This application does not limit the scope of these steps. The following embodiments are only illustrated by examples of execution by the corresponding device.

[0178] Example 1:

[0179] This embodiment uses the address of the relay UE as routing indication information to guide the routing and transmission of data packets. See below for further details. Figure 2 The flowchart of the routing method shown below provides a detailed explanation of the method provided in this embodiment.

[0180] S200: The AN device configures an address (hereinafter abbreviated as add.) and at least one routing information for each relay UE in the communication system, and sends default route indication information to each relay UE. Since this embodiment takes the above-mentioned link 1 as an example, the figure only schematically shows the AN device configuring the address and routing information for UE2, UE3, and UE4, as well as the default route indication information.

[0181] It is worth noting that sending default route indication information to each relay UE is an optional step for the AN device. In some implementations, the default route indication information is specified by the communication protocol or preset within the relay UE. In this case, the AN device may not need to send default route indication information to each relay UE.

[0182] In this embodiment, the AN device assigns an address to each relay UE to uniquely identify each relay UE within the coverage area of ​​the AN device or within a cell managed by the AN device. The address of the relay UE can be a dedicated identifier, or it can also be called a relay identifier, relay address, etc., and this application does not limit this.

[0183] Optionally, after a UE becomes a relay UE, it can obtain an address assigned to it from the AN device. For example, after a UE becomes a relay UE, it can send an indication message to the AN device, indicating that it has become a relay UE; upon receiving the indication message, the AN device can assign an address to the UE. It should be noted that the UE can be a UE directly connected to the AN device via the Uu interface, or a UE connected to the AN device via another relay UE; this application does not limit this.

[0184] In the embodiments of this application, the example is that the AN device assigns addresses add.UE2, add.UE3, and add.UE4 to UE2, UE3, and UE4 respectively.

[0185] To implement the routing function, the AN device also needs to provide at least one routing information for each relay UE. Each routing information includes a routing indication and the address of the next-hop node corresponding to that routing indication.

[0186] The routing information includes the destination address. The destination address can be understood as the address of the destination relay UE.

[0187] It should be noted that the AN device provides at least one routing information for each relay UE, which includes downlink routing information and uplink routing information. The downlink routing information and uplink routing information may not be distinguished in form, or they may be distinguished by transmission direction indication.

[0188] It is worth noting that the AN device itself is not configured with an address, nor is an address configured for the remote UE in the link. Therefore, for downlink transmission, the last relay UE in each link has no next-hop node, and thus the AN device will not allocate downlink routing information to it. Similarly, for uplink transmission, the first relay UE in each link also has no next-hop node, and therefore the AN device will not allocate corresponding uplink routing information to it.

[0189] In addition, to ensure that each relay UE can perform route transmission for newly accessed remote UEs, the AN device also needs to provide default route indication information for each relay UE. The relay UE can then transmit the first data packet of the newly accessed remote UE based on this default indication information.

[0190] For example, assume that the routing information provided by the AN device for UE2 is shown in Table 1, the routing information provided for UE3 is shown in Table 2, and the routing information provided for UE4 is shown in Table 3. The default route indication information includes add.xxx as an example.

[0191] Table 1: Routing Information for UE2

[0192]

[0193] Since UE2 is the last relay UE in link 1, the AN device will not allocate downlink routing information to it. Therefore, in Table 1 above, both routing information are uplink routing information.

[0194] Table 2: Routing Information for UE3

[0195]

[0196] In Table 2 above, the first and second routing information entries are uplink routing information, and the third entry is downlink routing information.

[0197] Table 3: Routing Information for UE4

[0198]

[0199] Since UE4 is a head relay UE in link 1, the AN device will not allocate uplink routing information to it. Therefore, in Table 3 above, the two routing information entries are both downlink routing information.

[0200] It should also be noted that the AN device can configure the address, routing information, and default route indication information of any relay UE separately through different messages; it can also configure the above three items of the relay UE simultaneously through the same message, and this application does not limit this. In addition, the AN device can perform the above steps to update the routing information of the relay UE when the topology relationship of the relay UE in the communication system changes; or the AN device can perform the above steps periodically or at regular intervals, and this application does not limit this.

[0201] S201: UE1 and UE2 establish an SL communication connection. UE2 assigns a local identifier (Local ID) to UE1. The local identifier of UE1 will be referred to as LID-UE1 below.

[0202] It should be noted that since the local identifier is used within the scope of a relay UE to identify other UEs that access the relay UE through the established SL direct link, different relay UEs can assign the same local identifier to accessing UEs. For example, UE2 assigns a local identifier of 1 to UE1, UE3 assigns a local identifier of 1 to UE2, and UE3 assigns a local identifier of 2 to UE6. The local identifier can also be understood as a local index within the scope of a relay UE.

[0203] S202: To establish a Uu communication connection between UE1 and the AN device, UE1 generates a first data packet containing a first message sent by UE1 to the network side. For example, the first data packet contains an RRC connection establishment request. UE1 sends the first data packet to UE2, with which it has established an SL communication connection, wherein the first data packet does not contain a BAP header. UE2 receives the first data packet from UE1.

[0204] S203: Since UE1 is a newly accessed remote UE, the AN device has not yet allocated downlink dedicated routing indication information to it. Therefore, UE2 uses the default routing indication information (i.e., add.xxx) as the target routing indication information for the first data packet. When UE2 determines that the destination address (add.xxx) contained in the target routing indication information is different from its own address (add.UE2), it determines the target routing information containing the target routing indication information from at least one saved routing information (e.g., item 2 in Table 1), determines the next-hop node address corresponding to the target routing indication information (i.e., add.UE3) in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE3 indicated by add.UE3). As the last relay UE of UE1, UE2 determines that the target device local identifier of the first data packet is the local identifier of the source device of the first data packet (i.e., the local identifier of UE1: LID-UE1); and adds a BAP header to the first data packet to generate a second data packet, wherein the BAP header of the second data packet contains the target routing indication information add.xxx and the target device local identifier LID-UE1. UE2 sends the second data packet to UE3. UE3 receives the second data packet from UE2.

[0205] To implement routing functionality, adjacent relay UEs need to obtain each other's addresses so that during routing transmission, the relay UE can accurately determine the transmission target indicated by the next-hop node address based on the next-hop node address. In this embodiment, adjacent relay UEs can determine each other's addresses in, but are not limited to, the following two methods:

[0206] Method 1: After two adjacent relay UEs obtain their own addresses from the AN device, they exchange their addresses through the SL communication connection between them. Taking UE2 and UE3 as an example, after UE2 becomes a relay UE and obtains the address add.UE2, it sends its own address add.UE2 to UE3; after receiving UE2's address, UE3 sends its own address add.UE3 to UE2.

[0207] Method 2: The AN device can provide each relay UE with the addresses of its neighboring relay UEs. It should be noted that when the AN device provides the address of its neighboring second relay UE to the first relay UE, it also needs to carry the indication information of the second relay UE, so that the first relay UE can determine that the address of the received second relay UE belongs to the second relay UE based on the indication information of the second relay UE.

[0208] Continuing with UE2 and UE3 as examples, in Figure 1As shown in the communication system topology, UE3 is the parent relay of UE2. UE3 provides UE2 with a local identifier (LID-UE2). Therefore, the first message sent by the AN device to UE3 includes not only UE2's address but also the local identifier (LID-UE2) assigned to UE2 by UE3. Similarly, UE2 is a child relay of UE3. UE2 can recognize UE3's Layer 2 identifier (i.e., L2ID-UE3) / cell-radio network temporary identifier (C-RNTI) (i.e., C-RNTI-UE3). Therefore, the second message sent by the AN device to UE2 includes not only UE3's address but also UE3's Layer 2 identifier or C-RNTI (i.e., L2ID-UE3 / C-RNTI-UE3).

[0209] It should be noted that the Layer 2 identifier of UE3 is the identifier used by UE2 and UE3 for SL communication. If the AN device also carries the Layer 2 identifier L2ID-UE3 of UE3 when notifying UE2 of UE3's address, then UE3 needs to report its own Layer 2 identifier to the AN device in advance.

[0210] For example, when the AN device notifies UE2 and UE3 of each other's addresses, it can refer to... Figure 3 The process shown has the following specific steps:

[0211] S301: AN assigns the address add.UE3 to UE3, which has previously established a Uu communication connection.

[0212] S302: When UE2 establishes an SL communication connection with UE3, UE3 assigns a local identifier LID-UE2 to UE2.

[0213] S303: UE2 establishes a Uu communication connection with the AN device, and during the process of establishing the Uu communication connection, UE2 or UE3 sends the local identifier LID-UE2 of UE2 to the AN device.

[0214] S304: After UE2 becomes a relay UE, the AN device assigns the address add.UE2 to UE2.

[0215] S305: The AN device sends a first message to UE3, which carries the address of UE2, add.UE2, and the local identifier of UE2, LID-UE2.

[0216] S306: UE3 sends its own Layer 2 identifier (L2 ID-UE2) to the AN device.

[0217] It should be noted that the implementation of this application does not limit the time when UE3 executes S306. S306 can be executed at any time after S301 and before S307.

[0218] S307: The AN device sends a second message to UE2, which contains the address of UE3, add.UE3, and the Layer 2 identifier or C-RNTI of UE3 (i.e., L2 ID-UE2 / C-RNTI-UE3).

[0219] It should be noted that the steps of the AN device to allocate an address to UE2 and to provide UE2 with the address of UE3 can be achieved through this one message, that is, S304 and S307 can be executed simultaneously, and this application does not limit this.

[0220] In summary, UE2 and UE3 can determine each other's addresses and indication information. Therefore, when UE2 subsequently determines the next-hop node address as UE3's address `add.UE3`, it can identify the transmission target as UE3 based on the L2 ID -UE2 / C-RNTI-UE3 corresponding to `add.UE3`, and can transmit data packets to UE3 according to L2 ID -UE2 / C-RNTI-UE3. Similarly, when UE3 subsequently determines the next-hop node address as UE2's address `add.UE2`, it can identify the transmission target as UE2 based on the LID -UE2 corresponding to `add.UE2`, and can transmit data packets to UE2 according to LID -UE2.

[0221] Additionally, it should be noted that the above explanation only uses UE2 and UE3 as examples. In reality, the AN device can also provide the addresses of neighboring relay UEs to other relay UEs using the same method. For example, the AN device can also notify UE3 and UE4 of each other's addresses separately. Furthermore, if UE1, which subsequently accesses UE2, also becomes a relay UE, the AN device can also notify UE1 and UE2 of each other's addresses using the same method.

[0222] S204: After receiving the second data packet, UE3 obtains the target routing indication information (i.e., the default routing indication information add.xxx) from the BAP header of the second data packet. When it is determined that the destination address (add.xxx) contained in the target routing indication information is different from its own address (add.UE3), it determines the target routing information containing the target routing indication information from at least one stored routing information (e.g., item 2 in Table 2), determines the next-hop node address (i.e., add.UE4) corresponding to the target routing indication information in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE4 indicated by add.UE4). UE3 sends the second data packet to UE4. UE4 receives the second data packet from UE3.

[0223] S205: After receiving the second data packet, UE4, acting as a header relay UE, can obtain the destination routing indication information (i.e., default routing indication information add.xxx) of the second data packet from its BAP header. When UE4 determines that the destination address (add.xxx) contained in the destination routing indication information is different from its own address (add.UE3), UE4 determines that the transmission target is the AN device based on the destination routing indication information. UE4 then sends the second data packet to the AN device. The AN device receives the second data packet from UE4.

[0224] As described above, UE4 is a head relay UE. Therefore, the routing information configured for it by the AN device does not contain uplink routing information. Thus, UE4 needs to determine the transmission target through methods other than matching routing information.

[0225] Since UE4 is a head relay UE, its next hop in the uplink direction is the AN device. Based on this, in one implementation, when UE4 determines that the destination address (add.xxx) contained in the target routing indication information is different from its own address (add.UE4), and the target routing indication information of the second data packet is the default routing indication information add.xxx (i.e., it is determined that the target routing indication information of the second data packet contains the default address), it can be determined that the second data packet is a data packet in the uplink transmission direction, that is, the transmission object is determined to be the next hop in the uplink direction—the AN device.

[0226] Due to the unique nature of UE4 as a head relay UE, it can communicate through two interfaces, while other relay UEs can only communicate through the PC5 interface. Therefore, in another implementation, UE4 can determine the transmission direction and target by the interface used to receive the second data packet. In this step, when UE4 determines that the destination address (add.xxx) contained in the target routing indication information is different from its own address (add.UE4), and the interface used to receive the second data packet is the PC5 interface, it can determine that the second data packet is a data packet in the uplink transmission direction, that is, the transmission target is determined to be the next hop in the uplink direction—the AN device.

[0227] S206: After receiving the second data packet, the AN device decapsulates it to obtain a first data packet without a BAP header. The AN device can then perform subsequent processing based on the data carried in the first data packet, such as initiating the process of establishing a Uu communication connection between the AN device and UE1.

[0228] S207: The AN device establishes a Uu communication connection with UE1.

[0229] S208: The AN device determines the uplink dedicated route indication information (hereinafter referred to as UL route indication information-UE1) and downlink dedicated route indication information (hereinafter referred to as DL route indication information-UE1) of UE1, and sends / configures the UL route indication information-UE1 to UE2 so that UE2 can use the UL route indication information-UE1 to realize the uplink transmission of UE1.

[0230] To enable uplink transmission for UE1, the AN device sends the uplink dedicated routing indication information (UL routing indication information - UE1) of UE1 to UE2 via S208. Furthermore, to enable downlink transmission for UE1, the AN device stores the downlink dedicated routing indication information (DL routing indication information - UE1) of UE1.

[0231] The UL routing indication information - UE1 contains the address of the destination relay UE (the last relay UE in the uplink transmission direction). In this embodiment, the UL routing indication information - UE1 contains the address of UE4, add.UE4.

[0232] The DL routing indication information - UE1 contains the address of the destination relay UE (the last relay UE in the downlink transmission direction). In this embodiment, the DL routing indication information - UE1 contains the address of UE2, add.UE2.

[0233] In one implementation, the number of uplink dedicated routing indication information for UE1 can be one, and the number of downlink dedicated routing indication information for UE1 can also be one.

[0234] In another implementation, the AN device can determine the uplink dedicated routing indication information (containing multiple UL routing indication information - UE1) and / or downlink dedicated routing indication information (containing multiple DL routing indication information - UE1) of UE1 at the bearer level. Different UL routing indication information - UE1 / DL routing indication information - UE1 correspond to different bearers.

[0235] Following S208, each device in Link 1 can utilize the UL routing indication information -UE1 and DL routing indication information -UE1 to achieve uplink and downlink transmission for UE1. Specifically, S209-S213 correspond to the uplink transmission process of UE1, and S214-S217 correspond to the downlink transmission process of UE1. It should be noted that this application does not limit the execution order of the uplink and downlink transmission processes.

[0236] The uplink transmission process of UE1 will be explained below.

[0237] S209: UE1 generates a third data packet, which does not contain a BAP header. Furthermore, the third data packet may carry UE1's user plane data or control plane data (e.g., signaling), and this application does not limit this. UE1 sends the third data packet to UE2, and UE2 receives the third data packet from UE1.

[0238] S210: After receiving the third data packet, UE2 uses the uplink dedicated routing indication information of UE1 (UL routing indication information - UE1, including add.UE4) as the destination routing indication information of the third data packet. When UE2 determines that the destination address (add.UE4) contained in the destination routing indication information is different from its own address (add.UE2), it determines the destination routing information containing the destination routing indication information from at least one saved routing information (e.g., the first item in Table 1), determines the next-hop node address corresponding to the destination routing indication information (i.e., add.UE3) in the destination routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE3 indicated by add.UE3). As the last relay UE of UE1, UE2 determines that the destination device local identifier of the third data packet is the local identifier of the source device of the third data packet (i.e., the local identifier of UE1: LID-UE1), and adds a BAP header to the third data packet to generate a fourth data packet, wherein the BAP header of the fourth data packet contains the destination routing indication information add.UE4 and the destination device local identifier LID-UE1. UE2 sends the fourth data packet to UE3. UE3 receives the fourth data packet from UE2.

[0239] In one implementation, when the uplink dedicated routing indication information stored by UE2 contains multiple UL routing indication information - UE1 that correspond to different bearers, UE2, in determining the target routing indication information of the third data packet, specifically includes the following steps:

[0240] UE2 determines the target bearer used to transmit the third data packet;

[0241] UE2 determines the target routing indication information as: among multiple UL routing indication information -UE1, the target UL routing indication information -UE1 that has a corresponding relationship with the target bearer.

[0242] S211: After receiving the fourth data packet, UE3 obtains the target routing indication information (i.e., UL routing indication information - UE1 - add.UE4) from the BAP header of the fourth data packet. When it is determined that the destination address (add.UE4) contained in the target routing indication information is different from its own address (add.UE3), it determines the target routing information containing the target routing indication information from at least one stored routing information (e.g., item 1 in Table 2), determines the next-hop node address (i.e., add.UE4) corresponding to the target routing indication information in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE4 indicated by add.UE4). UE3 sends the fourth data packet to UE4. UE4 receives the fourth data packet from UE3.

[0243] S212: After receiving the fourth data packet, UE4, acting as a header relay UE, can obtain the destination routing indication information (i.e., UL routing indication information - UE1 - add.UE4) of the fourth data packet from its BAP header. When UE4 determines that the destination address (add.UE4) contained in the destination routing indication information is the same as its own address (add.UE4), and the interface used to receive the second data packet is the PC5 interface, it can determine that the second data packet is a data packet in the uplink transmission direction, that is, it determines that the transmission target is the next hop in the uplink direction - the AN device. UE4 sends the fourth data packet to the AN device. The AN device receives the fourth data packet from UE4.

[0244] As can be seen from the specific description in S205 above, the routing information configured by the AN device for UE4 does not contain uplink routing information. Therefore, UE4 needs to determine the transmission object through other means besides matching routing information (such as through the interface of the fourth data packet).

[0245] S213: After receiving the fourth data packet, the AN device decapsulates it to obtain a third data packet without a BAP header. The AN device can then perform subsequent processing based on the data carried in the third data packet (e.g., user plane data or control plane data), such as sending user plane data to the core network equipment or performing corresponding operations based on the control plane data.

[0246] The downlink transmission process of UE1 will be explained below.

[0247] S214: The AN device receives the fifth data packet, which does not have a BAP header. Additionally, the fifth data packet may carry user plane data or control plane data (e.g., signaling) of UE1; this application does not limit this. Optionally, the fifth data packet can be generated by the AN device itself or received from the core network device. The AN device uses the stored downlink dedicated routing indication information of UE1 (DL routing indication information - UE1, including add.UE2) as the destination routing indication information of the fifth data packet, and determines the local identifier of the destination device (UE1) of the fifth data packet as the local identifier of the destination device (UE1) (i.e., the local identifier of UE1: LID-UE1). The AN device adds a BAP header to the fifth data packet, generating a sixth data packet, wherein the BAP header of the sixth data packet contains the destination routing indication information add.UE2 and the local identifier of the destination device LID-UE1. The AN device sends the sixth data packet to UE4. UE4 receives the sixth data packet from the AN device.

[0248] In this application embodiment, the AN device may, but is not limited to, determine the transmission target as UE4 through the following implementation methods:

[0249] In one implementation, the AN device can determine the head relay UE—UE4—in the communication link where UE1 is located based on the topology of the communication system.

[0250] In another implementation, after determining the downlink dedicated routing indication information (DL routing indication information - UE1) of UE1 in S208, the AN device can also determine the head relay UE corresponding to the downlink dedicated routing indication information of UE1 (i.e., UE4 corresponding to DL routing indication information - UE1). In this way, when the AN device determines that the destination routing indication information of the fifth data packet is DL routing indication information - UE1, it can also determine that the transmission object is UE4 corresponding to DL routing indication information - UE1.

[0251] In another implementation, the AN device can maintain at least one routing information (all of which are downlink routing information). Thus, after determining the downlink dedicated route indication information (DL route indication information - UE1) of UE1 in S208, a routing information can be generated as follows:

[0252] Routing information: add.UE2, next hop node address: add.UE4.

[0253] Optionally, if the downlink dedicated routing indication information of UE1 stored in the AN device contains multiple DL routing indication information corresponding to different bearers - UE1, the AN device shall, when determining the target routing indication information of the fifth data packet, specifically include the following steps:

[0254] The AN device determines the target bearer used to transmit the fifth data packet;

[0255] The AN device determines the target routing indication information as: among multiple DL routing indication information -UE1, the target DL routing indication information -UE1 that has a corresponding relationship with the target bearer.

[0256] S215: After receiving the sixth data packet, UE4, acting as a header relay UE, can obtain the destination routing indication information (i.e., DL routing indication information - UE1, containing add.UE2) of the sixth data packet from its BAP header. When UE4 determines that the destination address (add.UE2) contained in the destination routing indication information is different from its own address (add.UE4), it determines the destination routing information containing the destination routing indication information from at least one stored routing information (e.g., item 1 in Table 3), determines the next-hop node address (i.e., add.UE3) corresponding to the destination routing indication information in the destination routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE3 indicated by add.UE3). UE4 sends the sixth data packet to UE3. UE3 receives the sixth data packet from UE4.

[0257] S216: After receiving the sixth data packet, UE3 obtains the target routing indication information (i.e., DL routing indication information - UE1 - add.UE2) from the BAP header of the sixth data packet. When it is determined that the destination address (add.UE2) contained in the target routing indication information is different from its own address (add.UE3), it determines the target routing information containing the target routing indication information from at least one stored routing information (e.g., item 3 in Table 2), determines the next-hop node address (i.e., add.UE2) corresponding to the target routing indication information in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE2 indicated by add.UE2). UE3 sends the sixth data packet to UE2, and UE2 receives the sixth data packet from UE3.

[0258] S217: After receiving the sixth data packet, UE2, acting as the last relay UE, can obtain the destination routing indication information (i.e., DL routing indication information - UE1 - add.UE2) of the sixth data packet from its BAP header. When the UE determines that the destination address (add.UE2) contained in the destination routing indication information is the same as its own address (add.UE2), it obtains the destination device local identifier (LID - UE1) of the sixth data packet from its BAP header and determines that the transmission target is the remote UE indicated by the destination device local identifier (i.e., UE1 indicated by LID UE1). UE2 decapsulates the sixth data packet to obtain a fifth data packet without a BAP header. UE2 sends the fifth data packet to UE1, and UE1 receives the fifth data packet from UE2.

[0259] Afterwards, UE1 can perform subsequent processing based on the data carried in the fifth data packet.

[0260] This application provides a routing method that uses the address of a relay UE as routing indication information to guide the routing of data packets, thereby enabling routing between an AN device and a remote UE in a multi-hop communication scenario.

[0261] It should be noted that the routing method provided in this embodiment can also be used to achieve routing transmission in single-hop communication scenarios. The following example uses the communication link between the UE5-UE4-AN device (referred to as link 2) as a reference. Figure 4 The flowchart shown is used for illustration.

[0262] S401: UE5 establishes an SL communication connection with UE4, and UE4 assigns a local identifier (LID-UE5) to UE5.

[0263] S402: To establish a Uu communication connection between UE5 and the AN device, UE5 generates a seventh data packet containing the first message sent by UE5 to the network side. UE5 sends the seventh data packet to UE4, where the seventh data packet does not have a BAP header. UE4 receives the seventh data packet from UE5.

[0264] S403: Since UE5 is a newly accessed remote UE, the AN device has not yet allocated downlink dedicated routing indication information to it. Therefore, UE4 uses the default routing indication information (add.xxx) as the destination routing indication information for the seventh data packet. When UE4 determines that the destination address (add.xxx) contained in the destination routing indication information is different from its own address (add.UE4), it determines the transmission target to the AN device based on the destination routing indication information. As the last relay UE of UE5, UE4 determines that the local identifier of the destination device for the seventh data packet is the local identifier of the source device of the seventh data packet (i.e., the local identifier of UE5: LID-UE5), and adds a BAP header to the seventh data packet to generate the eighth data packet. The BAP header of the eighth data packet contains the destination routing indication information and the destination device local identifier. UE4 sends the eighth data packet to the AN device. The AN device receives the eighth data packet from UE4.

[0265] Similar to S205, UE4 can determine that the seventh data packet is a data packet in the uplink transmission direction when the target routing indication information is the default routing indication information, that is, determine that the transmission object is the next hop in the uplink direction - AN device; or when UE4 determines that the interface used to receive the seventh data packet is the PC5 interface, it can determine that the seventh data packet is a data packet in the uplink transmission direction, that is, determine that the transmission object is the next hop in the uplink direction - AN device.

[0266] S404: Similar to S206, after receiving the eighth data packet, the AN device decapsulates it to obtain a seventh data packet without a BAP header. The AN device can then perform post-processing based on the data carried in the seventh data packet, for example, initiating the process of establishing a Uu communication connection between the AN device and UE5.

[0267] S405: The AN device establishes a Uu communication connection with UE5.

[0268] S406: The AN device determines the uplink dedicated route indication information (hereinafter referred to as UL route indication information-UE5) and downlink dedicated route indication information (hereinafter referred to as DL route indication information-UE5) of UE5, and sends / configures the UL route indication information-UE5 to UE4 so that UE5 can use the UL route indication information-UE5 to realize the uplink transmission of UE5.

[0269] The UL routing indication information -UE5 contains the address of UE4, add.UE4; the DL routing indication information -UE5 contains the address of UE4, add.UE4.

[0270] It should also be noted that, in one implementation, the number of uplink dedicated routing indication information for UE5 can be one, and the number of downlink dedicated routing indication information for UE5 can also be one.

[0271] In another implementation, the AN device can determine the uplink dedicated routing indication information (containing multiple UL routing indication information - UE5) and / or downlink dedicated routing indication information (containing multiple DL routing indication information - UE5) of UE5 at the bearer level. Different UL routing indication information - UE5 / DL routing indication information - UE5 correspond to different bearers.

[0272] Following S406, each device in Link 2 can utilize the UL routing indication information -UE5 and the DL routing indication information -UE5 to achieve uplink and downlink transmission of UE5. Specifically, S407-S409 correspond to the uplink transmission process, and S410-S411 correspond to the downlink transmission process.

[0273] The uplink transmission process of UE5 will be explained below.

[0274] S407: UE5 generates a ninth data packet, which does not contain a BAP header. Furthermore, the ninth data packet may carry user plane data or control plane data from UE5; this application does not limit this. UE5 sends the ninth data packet to UE4, and UE4 receives the ninth data packet from UE5.

[0275] S408: After receiving the ninth data packet, UE4, acting as both the tail relay UE and the head relay UE, uses the uplink dedicated routing indication information (UL routing indication information - UE5, including add.UE4) of UE5 as the destination routing indication information of the ninth data packet. UE4 determines that the destination address (add.UE4) contained in the destination routing indication information is the same as its own address (add.UE4), and that the interface used to receive the ninth data packet is the PC5 interface. Therefore, it can determine that the ninth data packet is a data packet in the uplink transmission direction, i.e., the transmission target is the next hop in the uplink direction—the AN device. As the tail relay UE of UE5, UE4 determines that the local identifier of the destination device for the ninth data packet is the local identifier of the source device of the ninth data packet (i.e., the local identifier of UE5: LID-UE5), and adds a BAP header to the ninth data packet to generate the tenth data packet. The BAP header of the tenth data packet contains the destination routing indication information and the destination device local identifier. UE4 sends the tenth data packet to the AN device. The AN device receives the tenth data packet from UE4.

[0276] Similar to S210, when UE4 stores multiple UL routing indication information entries for UE5 that correspond to different bearers, UE4, in determining the target routing indication information for the ninth data packet, specifically includes the following steps:

[0277] UE4 determines the target bearer used to transmit the ninth data packet;

[0278] UE2 determines the target routing indication information as: among multiple UL routing indication information - UE5, the target UL routing indication information - UE5 that has a corresponding relationship with the target bearer.

[0279] S409: After receiving the tenth data packet, the AN device decapsulates it to obtain a ninth data packet without a BAP header. The AN device can then perform subsequent processing based on the data carried in the ninth data packet (e.g., user plane data or control plane data), such as sending user plane data to the core network equipment or performing corresponding operations based on the control plane data.

[0280] The downlink transmission process of UE5 will be explained below.

[0281] S410: The AN device receives the eleventh data packet, which does not have a BAP header. The eleventh data packet can carry user plane data or control plane data for UE5. The AN device uses the stored downlink dedicated routing indication information (DL routing indication information - UE5, including add.UE4) of UE5 as the destination routing indication information for the eleventh data packet, and determines the destination device local identifier of the eleventh data packet as the local identifier of the destination device (UE5) (i.e., UE5's local identifier LID-UE5). The AN device adds a BAP header to the eleventh data packet, generating a twelfth data packet, where the BAP header of the twelfth data packet contains the destination routing indication information add.UE4 and the destination device local identifier LID-UE5. The AN device sends the twelfth data packet to UE4. UE4 receives the twelfth data packet from the AN device.

[0282] Similar to S214, the AN device can determine the transmission object as UE4 based on the topology of the communication system or the correspondence between UE5 and UE4 in the DL routing indication information.

[0283] S411: After receiving the twelfth data packet, UE4, acting as a header relay UE, can obtain the destination routing indication information (i.e., DL routing indication information - UE5, containing add.UE4) of the twelfth data packet from its BAP header. When UE4 determines that the destination address (add.UE4) contained in the destination routing indication information is the same as its own address (add.UE4), and the interface used to receive the twelfth data packet is the Uu interface, it can determine that the twelfth data packet is a data packet in the downlink transmission direction, that is, it determines that the transmission object is the next hop in the downlink direction—UE4's remote UE. UE4 can obtain the destination device local identifier (LID-UE5) of the twelfth data packet from its BAP header and determine that the transmission object is the remote UE indicated by the destination device local identifier (i.e., UE5 indicated by LID UE5). UE4 decapsulates the twelfth data packet to obtain the eleventh data packet without a BAP header. UE4 sends the eleventh data packet to UE5, and UE5 receives the eleventh data packet from UE4.

[0284] Afterwards, UE5 can perform further processing based on the data carried in the eleventh data packet.

[0285] In conjunction with this embodiment one Figure 2 and Figure 4 The routing process shown in this embodiment provides a routing mechanism 1, which includes:

[0286] Downward direction:

[0287] When an AN device sends data packet 1 to a remote UE, it needs to add a BAP header to the data packet to generate data packet 2. The BAP header of data packet 2 contains destination routing indication information and destination device local identifier. The destination routing indication information is the downlink dedicated routing indication information of the remote UE (including the destination address, i.e., the address of the destination relay UE), and the destination device local identifier is the local identifier of the remote UE.

[0288] After receiving data packet 2, any relay UE first determines whether the destination address contained in the target routing indication information is the same as its own address;

[0289] If the two are determined to be the same, the remote UE indicated by the target device local identifier contained in the BAP header of data packet 2 is determined within the range of the relay UE. After decapsulating data packet 2, the decapsulated data packet 1 is sent to the remote UE.

[0290] If the two are determined to be different, then in at least one of the routing information stored locally, the target routing information containing the target routing indication information is searched, and the next-hop node address corresponding to the target routing indication information is determined in the target routing information, and the relay UE indicated by the next-hop node address is determined; data packet 2 is sent to the determined relay UE.

[0291] Upward direction:

[0292] The working mechanism is similar to that of the aforementioned downward direction.

[0293] The difference lies in the fact that after receiving data packet 1 (without a BAP header) from the remote UE, the relay UE determines the destination routing indication information and the destination device local identifier of data packet 1. The destination routing indication information is either the uplink dedicated routing indication information (containing the destination address, i.e., the address of the destination relay UE) or the default routing indication information of the remote UE, and the destination device local identifier is the local identifier of the remote UE. The relay UE adds a BAP header to data packet 1, generating data packet 2. Then, following the above mechanism, it determines the transmission target and sends data packet 2.

[0294] As described above, the head relay UE connects to the AN device via the Uu interface and to other relay UEs via the PC5 interface. Therefore, when the AN device has not configured uplink routing information for the head relay UE, the head relay UE can determine subsequent actions based on the interface. After receiving data packet 2, the head relay UE determines that the destination address contained in the destination routing indication information in the BAP header of data packet 2 is the same as its own address, and then determines the interface used to receive data packet 2. If the interface is the Uu interface, it further determines the transmission target through the local identifier of the target device of data packet 2; if the interface is the PC5 interface, it determines that the AN device is the transmission target.

[0295] As described in Embodiment 1 above, in the multi-hop communication scenario shown in Embodiment 1 (continuing to take link 1 as an example), the final protocol stack can be formed as follows: Figure 5 As shown.

[0296] from Figure 5 As shown in the protocol stack, the data packets sent by the remote UE to the relay UE do not need to carry the BAP header. For example, the data packets sent by UE1 to UE2 in the figure do not carry the BAP header, while the data packets sent by UE2 to UE3 need to carry the BAP header.

[0297] Considering that the relay UE itself may also communicate with the AN device as a remote UE. For example, the communication link UE2-UE3-UE4-AN device (referred to as link 3). In link 3, UE2 is the remote UE, UE3 is the last relay UE, and UE4 is the first relay UE.

[0298] In one implementation, in link 3, UE2, acting as the remote UE, can also perform uplink and downlink transmissions through the above process. The data packets sent by UE2 to UE3 do not need to carry a BAP header.

[0299] Therefore, from UE3's perspective, in the uplink direction, in some cases, it will receive data packets without BAP headers from UE2 (when UE2 is a remote UE, such as the scenario of link 3 mentioned above), and in other cases, it will receive data packets with BAP headers from UE2 (when UE2 is a relay UE, such as the scenario of link 1 mentioned above).

[0300] Similarly, in the downlink direction, in some cases, the data packets sent by UE3 to UE2 do not have a BAP header (when UE2 is a remote UE, such as the scenario of link 3 mentioned above), while in other cases, the data packets sent by UE3 to UE2 have a BAP header (when UE2 is a relay UE, such as the scenario of link 1 mentioned above).

[0301] In this complex scenario where Link 1 and Link 3 coexist, if no distinction is made between data packets under different circumstances, UE3 will be unable to determine how to parse the received data packets: whether to parse them according to the data packet format with a BAP header or the format without a BAP header.

[0302] Based on this, the embodiments of this application can solve the above problems through, but are not limited to, the following implementation methods:

[0303] In the first implementation, the distinction is made through different logical channels. That is, the logical channel used by a UE when communicating with a relay UE as a remote UE is different from the logical channel used by the same UE when communicating with a neighboring relay UE as a relay UE.

[0304] In the second implementation, when a UE acting as a relay UE in another link sends a data packet to an adjacent relay UE as a remote UE in another link, the data packet carries a BAP header. This BAP header also carries target routing indication information and a target device local identifier. The target device local identifier is a default local identifier used to indicate itself. For example, the default local identifier is LID-000.

[0305] Thus, when the UE receives a data packet, if the destination address in the target routing indication information of the data packet is the same as its own address, and the target device local identifier in the data packet is the default local identifier, then the UE determines that the data packet belongs to itself. The UE will parse the data packet and submit the resulting data packet without a BAP header to its upper layer (e.g., the PDCP layer).

[0306] It should also be noted that, in the second embodiment, the AN device also needs to configure its uplink dedicated routing indication information (including the address of the head relay UE in the link where the relay UE is located) for each relay UE in each communication system, and send the uplink dedicated routing indication information to the corresponding relay UE so that the relay UE can perform uplink transmission according to the uplink dedicated routing indication information.

[0307] In this embodiment, the head relay UE can also achieve uplink and downlink transmission of its own data packets using the above method. In this case, the addresses contained in the uplink dedicated route indication information and downlink dedicated route indication information allocated to it by the AN device are both addresses of the head relay UE. The head relay UE determines its own local identifier to be the aforementioned default local identifier (e.g., LID-000). After receiving a data packet, the head relay UE determines that the destination address contained in the destination route indication information of the data packet is the same as its own address, the interface receiving the data packet is the Uu interface, and the destination device local identifier in the data packet is the default local identifier; therefore, it determines that the data packet belongs to itself.

[0308] Based on the routing method provided in Implementation Example 1, Figure 1 In the communication system shown, the address assigned to each UE by the AN device, and the content of the BAP header in the data packet sent by the AN device with each UE as the destination device, can be found in [reference needed]. Figure 6 As shown.

[0309] Example 2:

[0310] Based on the routing method provided in Embodiment 1 above, this application also provides another routing method. This method uses the address of the relay UE or the address of the AN device as routing indication information to guide the routing and transmission of data packets. It should be noted that the method provided in this application can also be applied to... Figure 2 The routing method flowchart shown below illustrates this. Therefore, we will continue to use link 1 as an example below, and refer to... Figure 2 The methods provided in the embodiments of this application will be described in detail.

[0311] S200: The AN device configures an address, at least one routing information, and sends a default routing indication message to each relay UE in the communication system.

[0312] This step is similar to the corresponding step in Example 1, except that:

[0313] 1. In the embodiments of this application, the AN device itself is also configured with an address (hereinafter referred to as add.AN). The AN device can send its own address to the head relay UE in each link so that the head relay UE can subsequently determine the AN device indicated by the address of the AN device, thereby determining the transmission object and realizing the transmission of data packets to the AN device.

[0314] In this application, add.AN can be the default AN address, an address assigned by the AN device itself, or a user-configured address; no such limitation applies.

[0315] 2. Default route indication information assigned by the AN device to each relay UE. Since at least one relay UE can transmit data packets to the AN device according to the default route indication information, and the AN device has an address, the address add.xxx included in the default route indication information can be the address add.AN of the AN device, or another default address indicating the AN device. This application does not limit this.

[0316] It is worth noting that sending default route indication information to each relay UE is an optional step for the AN device. In some implementations, the default route indication information is specified by the communication protocol or preset within the relay UE. In this case, the AN device may not need to send default route indication information to each relay UE.

[0317] 3. The routing information configured by the AN device for each relay UE is different from that in Example 1.

[0318] Since the AN device has an address, for uplink transmission, the next-hop node of the head relay UE in each link is the AN device. Therefore, the AN device can configure uplink routing information for each relay UE, and this uplink routing information is different from that in Embodiment 1. (It should be noted that the downlink routing information configured by the AN device for each relay UE in this embodiment is the same as that in Embodiment 1).

[0319] To compare with the routing information of UE2, UE3, and UE4 in Embodiment 1, the routing information provided by the AN device for UE2, UE3, and UE4 in this embodiment can be found in Tables 4-6 below. It should be noted that in Tables 4-6 below, the default address add.xxx included in the default route indication information differs from the address add.AN of the AN device, for example.

[0320] Table 4: Routing Information for UE2

[0321]

[0322]

[0323] Since UE2 is the last relay UE in link 1, the AN device will not allocate downlink routing information to it. Therefore, in Table 4 above, both routing information are uplink routing information.

[0324] Table 5: Routing Information for UE3

[0325]

[0326] In Table 5 above, the first and second routing information entries are uplink routing information, and the third entry is downlink routing information.

[0327] Table 6: Routing Information for UE4

[0328]

[0329] In Table 6 above, the first and second routing information entries are uplink routing information, and the third and fourth entries are downlink routing information.

[0330] S201: UE1 and UE2 establish an SL communication connection, and UE2 assigns a local identifier (hereinafter referred to as LID-UE1) to UE1.

[0331] S202: To establish a Uu communication connection between UE1 and the AN device, UE1 generates a first data packet containing the first message sent by UE1 to the network side. This first data packet does not contain a BAP header. UE1 sends the first data packet to UE2. UE2 receives the first data packet from UE1.

[0332] S203: Since UE1 is a newly accessed remote UE, the AN device has not yet allocated downlink dedicated routing indication information to it. Therefore, UE2 uses the default routing indication information (i.e., add.xxx) as the target routing indication information for the first data packet. When UE2 determines that the destination address (add.xxx) contained in the target routing indication information is different from its own address (add.UE2), it determines the target routing information containing the target routing indication information from at least one saved routing information (e.g., item 2 in Table 4), determines the next-hop node address corresponding to the target routing indication information (i.e., add.UE3) in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE3 indicated by add.UE3). As the last relay UE of UE1, UE2 determines that the target device local identifier of the first data packet is the local identifier of the source device of the first data packet (i.e., the local identifier of UE1: LID-UE1); and adds a BAP header to the first data packet to generate a second data packet, wherein the BAP header of the second data packet contains the target routing indication information add.xxx and the target device local identifier LID-UE1. UE2 sends the second data packet to UE3. UE3 receives the second data packet from UE2.

[0333] Similar to Embodiment 1, to implement the routing function, adjacent relay UEs also need to obtain each other's addresses so that during the routing transmission process, the relay UE can accurately determine the transmission object indicated by the next-hop node address based on the next-hop node address. The specific process can be found in the description in Embodiment 1 and will not be repeated here.

[0334] S204: After receiving the second data packet, UE3 obtains the destination routing indication information (i.e., the default routing indication information add.xxx) of the second data packet from its BAP header. When it is determined that the destination address (add.xxx) contained in the destination routing indication information is different from its own address (add.UE3), it determines the destination routing information containing the destination routing indication information from at least one stored routing information (e.g., item 2 in Table 5), determines the next-hop node address (i.e., add.UE4) corresponding to the destination routing indication information in the destination routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE4 indicated by add.UE4). UE3 sends the second data packet to UE4. UE4 receives the second data packet from UE3.

[0335] S205: After receiving the second data packet, UE4 can obtain the destination routing indication information (i.e., the default routing indication information add.xxx) of the second data packet from its BAP header. When UE4 determines that the destination address (add.xxx) contained in the destination routing indication information is different from its own address (add.UE4), it determines the destination routing information containing the destination routing indication information from at least one stored routing information (e.g., item 2 in Table 6), determines the next-hop node address (i.e., add.AN) corresponding to the destination routing indication information in the destination routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., the AN device indicated by add.AN). UE4 sends the second data packet to the AN device. The AN device receives the second data packet from UE4.

[0336] Steps S206-S208 are the same as the corresponding steps in Embodiment 1, and the specific processes can be referred to each other, so they will not be repeated here. That is, after the AN device establishes a Uu communication connection with UE1, it determines the uplink dedicated routing indication information (hereinafter referred to as UL routing indication information-UE1) and downlink dedicated routing indication information (hereinafter referred to as DL routing indication information-UE1) of UE1, and configures the UL routing indication information-UE1 to UE2, so that UE2 can use the UL routing indication information-UE1 to realize the uplink transmission of UE1.

[0337] Unlike Embodiment 1, the UL routing indication information - UE1 contains the address of the destination device in the uplink transmission direction. Since the destination device is an AN device in this case, the UL routing indication information - UE1 contains add.AN.

[0338] Similar to Embodiment 1, the DL routing indication information - UE1 contains the address of the destination relay UE (the last relay UE in the downlink transmission direction). In this embodiment, the DL routing indication information - UE1 contains the address of UE2, add.UE2.

[0339] Following S208, each device in Link 1 can utilize the UL routing indication information -UE1 and the DL routing indication information -UE1 to achieve uplink and downlink transmission of UE1. Specifically, S209-S213 correspond to the uplink transmission process of UE1, and S214-S217 correspond to the downlink transmission process of UE1.

[0340] It should be noted that since the DL routing indication information -UE1 determined by the AN device is the same as that in Embodiment 1, each device in Link 1 can adopt the same process as in Embodiment 1 to implement the downlink transmission process according to the DL routing indication information -UE1. Based on this, the downlink transmission process of S214-S217 in this embodiment will not be described again, and the specific process can be referred to the description in Embodiment 1 above.

[0341] Since the UL routing indication information -UE1 determined by the AN device is different from that in Embodiment 1, the following describes in detail the uplink transmission process S209-S213 implemented by each device in Link 1 according to the UL routing indication information -UE1.

[0342] S209: UE1 generates a third data packet, which does not contain a BAP header. UE1 sends the third data packet to UE2, and UE2 receives the third data packet from UE1.

[0343] S210: After receiving the third data packet, UE2 uses the uplink dedicated routing indication information of UE1 (UL routing indication information-UE1, containing add.AN) as the destination routing indication information of the third data packet. When UE2 determines that the destination address (add.AN) contained in the destination routing indication information is different from its own address (add.UE2), it determines the destination routing information containing the destination routing indication information from at least one saved routing information (e.g., item 1 in Table 4), determines the next-hop node address corresponding to the destination routing indication information (i.e., add.UE3) in the destination routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE3 indicated by add.UE3). As the last relay UE of UE1, UE2 determines that the destination device local identifier of the third data packet is the local identifier of the source device of the third data packet (i.e., the local identifier of UE1: LID-UE1), and adds a BAP header to the third data packet to generate a fourth data packet, wherein the BAP header of the fourth data packet contains the destination routing indication information add.UE4 and the destination device local identifier LID-UE1. UE2 sends the fourth data packet to UE3. UE3 receives the fourth data packet from UE2.

[0344] In one implementation, when the uplink dedicated routing indication information stored by UE2 contains multiple UL routing indication information - UE1 that correspond to different bearers, UE2, in determining the target routing indication information of the third data packet, specifically includes the following steps:

[0345] UE2 determines the target bearer used to transmit the third data packet;

[0346] UE2 determines the target routing indication information as: among multiple UL routing indication information -UE1, the target UL routing indication information -UE1 that has a corresponding relationship with the target bearer.

[0347] S211: After receiving the fourth data packet, UE3 obtains the destination routing indication information (i.e., UL routing indication information - UE1 - add.AN) from the BAP header of the fourth data packet. When it is determined that the destination address (add.AN) contained in the destination routing indication information is different from its own address (add.UE3), it determines the destination routing information containing the destination routing indication information from at least one stored routing information (e.g., item 1 in Table 5), determines the next-hop node address (i.e., add.UE4) corresponding to the destination routing indication information in the destination routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE4 indicated by add.UE4). UE3 sends the fourth data packet to UE4. UE4 receives the fourth data packet from UE3.

[0348] S212: After receiving the fourth data packet, UE4 can obtain the destination routing indication information (i.e., UL routing indication information - UE1 - add.AN) from the BAP header of the fourth data packet. When UE4 determines that the destination address (add.AN) contained in the destination routing indication information is different from its own address (add.UE4), it determines the destination routing information containing the destination routing indication information from at least one stored routing information (e.g., item 1 in Table 6), determines the next-hop node address (i.e., add.AN) corresponding to the destination routing indication information in the destination routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., the AN device indicated by add.AN). UE4 sends the fourth data packet to the AN device. The AN device receives the fourth data packet from UE4.

[0349] S213: After receiving the fourth data packet, the AN device decapsulates it to obtain a third data packet without a BAP header. The AN device can then perform subsequent processing based on the data carried in the third data packet (e.g., user plane data or control plane data), such as sending user plane data to the core network equipment or performing corresponding operations based on the control plane data.

[0350] This application provides a routing method that uses the address of a relay UE or the address of an AN device as routing indication information to guide the routing of data packets, thereby enabling routing between the AN device and the remote UE in a multi-hop communication scenario.

[0351] Similarly, based on the routing method provided in this embodiment, routing transmission in a single-hop communication scenario can also be realized, such as the communication link between UE5 and UE4 and AN devices (referred to as link 2). Each device in link 2 can use the same method as described above to realize the uplink and downlink transmission of UE5. The specific process can be referred to the description in the above embodiments, and will not be repeated here.

[0352] Based on the routing process in Embodiment 2, this application provides a routing mechanism 2, which includes:

[0353] The downward direction is the same as in Mechanism 1.

[0354] Upward direction:

[0355] The difference lies in the fact that after receiving data packet 1 (without a BAP header) from the remote UE, the relay UE determines the destination routing indication information and the destination device local identifier of data packet 1. The destination routing indication information is either the uplink dedicated routing indication information (containing the destination address, i.e., the address of the AN device) or the default routing indication information of the remote UE, and the destination device local identifier is the local identifier of the remote UE. The relay UE adds a BAP header to data packet 1, generating data packet 2. Then, following the above mechanism, it determines the transmission target and sends data packet 2 until it is transmitted to the AN device.

[0356] Based on the description in Embodiment 2 above, in the multi-hop communication scenario shown in Embodiment 1 (continuing to take link 1 as an example), the final complete protocol stack can be as follows: Figure 5 As shown.

[0357] Similarly, when the relay UE communicates with the AN device as a remote UE, such as when UE2 in link 3 mentioned in Embodiment 1 is a remote UE, it can also be implemented using the two implementation methods in Embodiment 1. For details, please refer to the description of the corresponding process in Embodiment 1, which will not be repeated here.

[0358] In the routing method provided in Embodiment 2, Figure 1 In the communication system shown, the address assigned to each UE by the AN device, and the content of the BAP header in the data packet sent by the AN device with each UE as the destination device, can be found in [reference needed]. Figure 7 As shown.

[0359] Example 3:

[0360] Based on Embodiments 1 and 2 above, this application also provides another routing method. In this method, the device address and path ID are used together as routing indication information to guide the routing and transmission of data packets.

[0361] In this method, the AN device can assign a path ID to each communication link. For example, the AN device can assign a path ID to each communication link based on the topology of the communication system.

[0362] It should be noted that the path ID assigned by the AN device to each link can distinguish the transmission direction. That is, for the same communication link, the AN device assigns a path ID for the uplink transmission direction and a path ID for the downlink transmission direction; or the AN device does not distinguish the transmission direction when assigning path IDs, that is, it assigns a path ID for each communication link.

[0363] The following example illustrates how AN devices assign a path ID to each communication link without distinguishing the transmission direction.

[0364] For example, in conjunction with the routing method provided in Embodiment 1, the AN device also assigns path ID-1 to the following communication links: UE4-AN device, UE3-UE4-AN device, UE5-UE4-AN device; assigns path ID-2 to the communication link UE7-AN device; assigns path ID-3 to the following communication links: UE8-AN device, UE9-UE8-AN device, UE11-UE8-AN device; assigns path ID-4 to the following communication links: UE2-UE3-UE4-AN device, UE6-UE3-UE4-AN device; assigns path ID-5 to the communication link UE1-UE2-UE3-UE4-AN device; and assigns path ID-6 to the communication link UE10-UE9-UE8-AN device. Additionally, the AN device assigns path ID-yyy to the default routing indication information.

[0365] Based on this example, the routing information assigned by the AN device to the relay UE in link 1 is shown in Tables 7-9.

[0366] Table 7: Routing Information for UE2

[0367]

[0368] In Table 7 above, both of these routing information entries are uplink routing information.

[0369] Table 8: Routing Information for UE3

[0370]

[0371]

[0372] In Table 8 above, the first to third routing information items are uplink routing information, and the fourth item is downlink routing information.

[0373] Table 9: Routing Information for UE4

[0374]

[0375] In Table 9 above, both of these routing information entries are downlink routing information.

[0376] It should be noted that after each remote UE establishes a Uu communication connection with the AN device, the AN device assigns uplink dedicated routing indication information and downlink dedicated routing indication information to the remote UE. This routing indication information includes not only the corresponding address but also the path ID assigned by the AN device to the communication link where the remote UE resides.

[0377] The routing mechanism 3 provided in this application embodiment can refer to mechanism 1 provided in embodiment 1 or mechanism 2 provided in embodiment 2. For details, please refer to the above detailed description of mechanism 1 or mechanism 2, which will not be repeated here. It is worth noting that in this mechanism 3, the path identifier and device address in the routing indication information included in the target routing information found by the relay UE are the same as the target path identifier and destination address in the target routing indication information.

[0378] Based on the routing method provided in Embodiment 3, Figure 1 In the communication system shown, when the AN device sends a data packet with each UE as the destination device, the content of the BAP header in that data packet can be referenced. Figure 8 As shown.

[0379] Example 4:

[0380] The method provided in this embodiment uses the UE's address as routing indication information to guide the routing and transmission of data packets. See below. Figure 9 The routing method flowchart shown illustrates the method provided in this embodiment in detail. It should be noted that in this embodiment, the AN device does not have the address used for routing as described above. Furthermore, as described in embodiments one through three above, the BAP header of the data packet in the above embodiments includes not only target route indication information but also the target device local identifier. This embodiment differs from the above embodiments in that the BAP header of the data packet includes target route indication information but does not need to include the target device local identifier.

[0381] S900: The AN device configures an address and at least one routing information for each UE in the communication system.

[0382] In this embodiment of the application, the AN device assigns an address to each UE to uniquely identify each relay UE within the coverage area of ​​the AN device or within a cell managed by the AN device.

[0383] It should be noted that after the AN device configures an address for a UE, it also configures new routing information for the relay UEs in the link where the UE is located. The routing indication information in these updated routing information includes the address of the UE. In this way, these relay UEs can perform downlink transmission based on these updated routing information.

[0384] It should be noted that the AN device provides at least one routing information for each relay UE, including downlink routing information and uplink routing information. The downlink and uplink routing information may not be distinguishable in form, or they can be distinguished by transmission direction indication. Each routing information includes a routing indication and the address of the corresponding next-hop node. The routing indication contains the destination address. In the uplink routing information, the destination address in the routing indication can be understood as the address of the destination relay UE. In the downlink routing information, the destination address in the routing indication can be the address of the destination device (the remote UE in the link).

[0385] Unlike Example 1, the AN device itself does not have a configured address, but it can configure addresses for remote UEs in the link. Therefore, for downlink transmission, the last relay UE in each link has a next-hop node, so the AN device will allocate downlink routing information to it. Conversely, for uplink transmission, the first relay UE in each link does not have a next-hop node, so the AN device will not allocate corresponding uplink routing information to it.

[0386] In addition, to enable uplink transmission for newly accessed remote UEs, this embodiment introduces a default route indication information. This default route indication information is used to transmit the first data packet of the newly accessed remote UE to the AN device. The following embodiments of this application will be described using an example where the default route indication information includes add.xxx.

[0387] Correspondingly, the routing information configured by the AN device for the UE that has been connected to the system contains a routing information that includes the default route indication information.

[0388] Continuing with link 1 as an example, the uplink routing information containing the default route indication information configured by the AN device for UE2 and UE3 is shown in Table 10 and Table 11, respectively:

[0389] Table 10: Routing Information for UE2

[0390]

[0391] Table 11: Routing Information for UE3

[0392]

[0393] S901: UE1 and UE2 establish an SL communication connection.

[0394] S902: To establish a Uu communication connection between UE1 and the AN device, UE1 generates a first data packet containing a first message sent by UE1 to the network side. For example, the first data packet contains an RRC connection establishment request. UE1 uses the default route indication information (including add.xxx) as the destination route indication information in the first data packet and adds a BAP header to the first data packet to generate a second data packet. The BAP header of the second data packet contains the destination route indication information (add.xxx). UE1 sends the second data packet to UE2. UE2 receives the second data packet from UE1.

[0395] In this step, UE1 can determine the default route indication information through the following two implementation methods:

[0396] The first implementation method: the default route indication information can be predefined and stored in the UE.

[0397] The second implementation method is to obtain the default route indication information from UE2 by UE1.

[0398] In the second embodiment, UE1 can refer to Figure 10 The process shown involves obtaining default route indication information, including the following steps:

[0399] S1001a: After UE2 establishes a Uu communication connection with the AN device, UE2 obtains the default route indication information from the AN device.

[0400] S1001b: After UE2 establishes an SL communication connection with other UEs (e.g., UE3), it obtains the default route indication information from the other UEs.

[0401] S1001a and S1001b are parallel schemes, and UE2 can use either scheme to obtain the default route indication information.

[0402] S1002: UE1 and UE2 establish SL communication connection.

[0403] S1003: UE2 sends a default route indication message to UE1.

[0404] In addition, UE1 can determine the transmission target as UE2 through the following two implementation methods.

[0405] First implementation method:

[0406] UE1 identifies UE2 with which it has an SL communication connection.

[0407] Second implementation method:

[0408] When UE2 performs the above S1003, UE2 can also send UE2 indication information to UE1 so that UE1 can determine that the default route indication information corresponds to UE2 based on the indication information. Thus, when the target route indication information of the first data packet is determined to be the default route indication information, the transmission object of the first data packet is determined to be UE2.

[0409] Optionally, UE2 may also send routing information containing default route indication information and the corresponding next-hop node address (add.UE2) to UE1, so that when UE1 determines that the target route indication information of the first data packet is the default route indication information, it can determine the routing information containing the default route indication information, and determine the next-hop node address (add.UE2) corresponding to the default route indication information in the routing information, and finally determine that the transmission object is the next-hop node of the next-hop node address (i.e., UE2 indicated by add.UE2).

[0410] In this application, to implement the routing function, adjacent UEs also need to obtain each other's addresses so that, during the routing transmission process, the object indicated by the next-hop node address can be accurately determined based on the next-hop node address. The process of determining the address of adjacent relay UEs can be referred to the specific description in Implementation 1, and will not be repeated here.

[0411] S903: After receiving the second data packet, UE2 obtains the target routing indication information (i.e., the default routing indication information add.xxx) from the BAP header of the second data packet. When it is determined that the destination address (add.xxx) contained in the target routing indication information is different from its own address (add.UE2), it determines the target routing information containing the target routing indication information (e.g., the routing indication information in Table 10) from at least one stored routing information. It then determines the next-hop node address (i.e., add.UE3) corresponding to the target routing indication information in this target routing information and determines that the transmission object is the next-hop node indicated by this next-hop node address (i.e., UE3 indicated by add.UE3). UE2 sends the second data packet to UE3. UE3 receives the second data packet from UE2.

[0412] S904: After receiving the second data packet, UE3 obtains the destination routing indication information (i.e., the default routing indication information add.xxx) of the second data packet from its BAP header. When it is determined that the destination address (add.xxx) contained in the destination routing indication information is different from its own address (add.UE3), it determines the destination routing information containing the destination routing indication information (e.g., the routing indication information in Table 11) from at least one stored routing information. It then determines the next-hop node address (i.e., add.UE4) corresponding to the destination routing indication information in this destination routing information and determines that the transmission object is the next-hop node indicated by this next-hop node address (i.e., UE4 indicated by add.UE4). UE3 sends the second data packet to UE4. UE4 receives the second data packet from UE3.

[0413] S905: Similar to S205 in Embodiment 1, after receiving the second data packet, UE4 can obtain the target routing indication information (i.e., default routing indication information add.xxx) of the second data packet from its BAP header, and determine the transmission target as the AN device according to the implementation method described in S205 based on the target routing indication information. UE4 sends the second data packet to the AN device. The AN device receives the second data packet from UE4.

[0414] S906-S907 are the same as S206-S207 in Embodiment 1, and will not be described again here.

[0415] S908a: The AN device assigns an address (i.e., add.UE1) to UE1, determines the uplink dedicated routing indication information (hereinafter referred to as UL routing indication information-UE1) and downlink dedicated routing indication information (hereinafter referred to as UL routing indication information-UE1) of UE1, and sends / configures UL routing indication information-UE1 and add.UE1 to UE1 so that UE1 can use UL routing indication information-UE1 to realize uplink transmission of UE1.

[0416] Optionally, when configuring UL routing indication information - UE1 and add.UE1 to UE1, the AN device can send the above information to UE2, and UE2 can then send it to UE1 via SL RRC message. To enable downlink transmission for UE1, the AN device stores UE1's downlink dedicated routing indication information (UL routing indication information - UE1).

[0417] The UL routing indication information - UE1 contains the address of the destination relay UE (the last relay UE in the uplink transmission direction). In this embodiment, the UL routing indication information - UE1 contains the address of UE4, add.UE4.

[0418] The DL routing indication information - UE1 contains the destination device address (i.e., add.UE1) for the downlink transmission direction.

[0419] In one implementation, the number of UL routing indication information - UE1 can be one, and the number of DL routing indication information - UE1 can also be one.

[0420] In another implementation, the AN device can determine the uplink dedicated routing indication information (containing multiple UL routing indication information - UE1) and / or downlink dedicated routing indication information (containing multiple DL routing indication information - UE1) of UE1 at the bearer level. Different UL routing indication information - UE1 / DL routing indication information - UE1 correspond to different bearers.

[0421] S908b: The AN device configures new routing information for each relay UE in the link based on the UL routing indication information -UE1 and the DL routing indication information -UE1, so that each relay UE can realize the uplink and downlink transmission of UE1 according to the routing information.

[0422] The new routing information allocated by the AN device to UE2, UE3, and UE4 is shown in Tables 12-14, respectively:

[0423] Table 12: Routing Information for UE2

[0424]

[0425] Table 13: Routing Information for UE3

[0426]

[0427] Table 14: Routing Information for UE4

[0428]

[0429] Following S908b, each device in Link 1 can utilize the UL routing indication information -UE1 and the DL routing indication information -UE1 to achieve uplink and downlink transmission of UE1. Specifically, S909-S913 correspond to the uplink transmission process of UE1, and S914-S918 correspond to the downlink transmission process of UE1.

[0430] The uplink transmission process of UE1 will be explained below.

[0431] S909: UE1 generates a third data packet, which does not have a BAP header. Optionally, the third data packet may carry user plane data or control plane data of UE1, which is not limited in this application. UE1 uses the UL routing indication information -UE1 as the destination routing indication information of the third data packet, and adds a BAP header to the third data packet to generate a fourth data packet, wherein the BAP header of the fourth data packet contains the destination routing indication information (UL routing indication information -UE1, including add.UE4). UE1 sends the fourth data packet to UE2. UE2 receives the fourth data packet from UE1.

[0432] Similar to S902 above, UE1 can also determine the transmission target as UE2 through the following two implementation methods.

[0433] First implementation method:

[0434] UE1 identifies UE2 with which it has an SL communication connection.

[0435] Second implementation method:

[0436] When UE2 executes the above S908a, UE2 can also send UE2 indication information to UE1 so that UE1 can determine the correspondence between UL routing indication information -UE1 and UE2 based on the indication information. Thus, when the target routing indication information of the third data packet is determined to be UL routing indication information -UE1, the transmission object of the third data packet is determined to be UE2.

[0437] Optionally, the AN device can also send routing information containing the correspondence between UL routing indication information -UE1 and the corresponding next-hop node address (add.UE2) to UE1, so that when UE1 determines that the target routing indication information of the third data packet is UL routing indication information -UE1, it can determine the routing information containing UL routing indication information -UE1, and determine the next-hop node address (add.UE2) corresponding to UL routing indication information -UE1 in the routing information, and finally determine that the transmission object is the next-hop node of the next-hop node address pair (i.e., UE2 indicated by add.UE2).

[0438] In this application, to implement the routing function, adjacent UEs also need to obtain each other's addresses so that, during the routing transmission process, the object indicated by the next-hop node address can be accurately determined based on the next-hop node address. The process of determining the address of adjacent relay UEs can be referred to the specific description in Implementation 1, and will not be repeated here.

[0439] S910: After receiving the fourth data packet, UE2 obtains the target routing indication information (i.e., UL routing indication information - UE1, containing add.UE4) from the BAP header of the fourth data packet. When it is determined that the destination address (add.UE4) contained in the target routing indication information is different from its own address (add.UE2), it determines the target routing information containing the target routing indication information (e.g., the first routing indication information in Table 12) from at least one stored routing information. It then determines the next-hop node address (i.e., add.UE3) corresponding to the target routing indication information in that target routing information and determines that the transmission object is the next-hop node indicated by that next-hop node address (i.e., UE3 indicated by add.UE3). UE2 sends the fourth data packet to UE3. UE3 receives the fourth data packet from UE2.

[0440] S911: After receiving the fourth data packet, UE3 obtains the target routing indication information (i.e., UL routing indication information - UE1, containing add.UE4) from the BAP header of the fourth data packet. When it is determined that the destination address (add.UE4) contained in the target routing indication information is different from its own address (add.UE3), it determines the target routing information containing the target routing indication information from at least one stored routing information (e.g., the first routing indication information in Table 13), determines the next-hop node address (i.e., add.UE4) corresponding to the target routing indication information in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE4 indicated by add.UE4). UE3 sends the fourth data packet to UE4. UE4 receives the fourth data packet from UE3.

[0441] S912: Similar to S205 in Embodiment 1, after receiving the fourth data packet, UE4 can obtain the target routing indication information (i.e., UL routing indication information - UE1, including add.UE4) of the fourth data packet from its BAP header, and determine the transmission target as the AN device according to the implementation method described in S212 based on the target routing indication information. UE4 sends the fourth data packet to the AN device. The AN device receives the fourth data packet from UE4.

[0442] S913: Same as S213, will not be repeated here.

[0443] The downlink transmission process of UE1 will be explained below.

[0444] S914: The AN device receives the fifth data packet, which does not have a BAP header. Additionally, the fifth data packet may carry user plane data or control plane data (e.g., signaling) of UE1; this application does not limit this. Optionally, the fifth data packet can be generated by the AN device itself or received from the core network device. The AN device uses the stored downlink dedicated routing indication information of UE1 (DL routing indication information - UE1, including add.UE1) as the destination routing indication information of the fifth data packet. The AN device adds a BAP header to the fifth data packet, generating a sixth data packet, wherein the BAP header of the sixth data packet contains the destination routing indication information add.UE1. The AN device sends the sixth data packet to UE4. UE4 receives the sixth data packet from the AN device.

[0445] In one implementation, the AN device can determine the head relay UE—UE4—in the communication link where UE1 is located based on the topology of the communication system.

[0446] In another implementation, after determining the downlink dedicated routing indication information (DL routing indication information - UE1) of UE1 in S908, the AN device can also determine the head relay UE corresponding to the downlink dedicated routing indication information of UE1 (i.e., DL routing indication information - UE1 corresponds to UE4). In this way, when the AN device determines that the destination routing indication information of the fifth data packet is DL routing indication information - UE1, it can also determine that the transmission object is UE4 corresponding to DL routing indication information - UE1.

[0447] In another implementation, the AN device can maintain at least one routing information (all of which are downlink routing information). Thus, after determining the downlink dedicated route indication information (DL route indication information - UE1) of UE1 in S908, a routing information can be generated as follows:

[0448] Routing information: add.UE1, next hop node address: add.UE4.

[0449] Optionally, if the downlink dedicated routing indication information of UE1 stored in the AN device contains multiple DL routing indication information corresponding to different bearers - UE1, the AN device shall, when determining the target routing indication information of the fifth data packet, specifically include the following steps:

[0450] The AN device determines the target bearer used to transmit the fifth data packet;

[0451] The AN device determines the target routing indication information as: among multiple DL routing indication information -UE1, the target DL routing indication information -UE1 that has a corresponding relationship with the target bearer.

[0452] S915: After receiving the sixth data packet, UE4 can obtain the target routing indication information (i.e., DL routing indication information - UE1, containing add.UE1) of the sixth data packet from its BAP header. When UE4 determines that the destination address (add.UE1) contained in the target routing indication information is different from its own address (add.UE4), it determines the target routing information containing the target routing indication information from at least one stored routing information (e.g., item 1 in Table 14), determines the next-hop node address (i.e., add.UE3) corresponding to the target routing indication information in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE3 indicated by add.UE3). UE4 sends the sixth data packet to UE3. UE3 receives the sixth data packet from UE4.

[0453] S916: After receiving the sixth data packet, UE3 obtains the target routing indication information (i.e., DL routing indication information - UE1 - add.UE1) from the BAP header of the sixth data packet. When it is determined that the destination address (add.UE1) contained in the target routing indication information is different from its own address (add.UE3), it determines the target routing information containing the target routing indication information from at least one stored routing information (e.g., item 2 in Table 13), determines the next-hop node address (i.e., add.UE2) corresponding to the target routing indication information in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., UE2 indicated by add.UE2). UE3 sends the sixth data packet to UE2, and UE2 receives the sixth data packet from UE3.

[0454] S917: After receiving the sixth data packet, UE2 can obtain the target routing indication information (i.e., DL routing indication information - UE1 - add.UE1) of the sixth data packet from its BAP header. When the UE determines that the destination address (add.UE1) contained in the target routing indication information is different from its own address (add.UE2), it determines the target routing information containing the target routing indication information from at least one stored routing information (e.g., item 2 in Table 12). Within this target routing information, it determines the next-hop node address (i.e., add.UE1) corresponding to the target routing indication information and identifies the transmission object as the next-hop node indicated by that next-hop node address (i.e., UE1 indicated by add.UE1). UE2 sends the sixth data packet to UE1, and UE1 receives the sixth data packet from UE2.

[0455] S918: After receiving the sixth data packet, UE1 can obtain the destination routing indication information (i.e., DL routing indication information - UE1 - add.UE1) from the BAP header of the sixth data packet. When the UE determines that the destination address (add.UE1) contained in the destination routing indication information is the same as its own address (add.UE1), it decapsulates the sixth data packet to obtain the fifth data packet without a BAP header. Finally, UE1 can perform subsequent processing based on the data carried in the fifth data packet.

[0456] This application provides a routing method that uses the UE's address as routing indication information to guide the routing of data packets, thereby enabling routing between the AN device and the remote UE in a multi-hop communication scenario.

[0457] It should be noted that the routing method provided in the embodiments of this application can also realize routing transmission in single-hop communication scenarios. The specific process can be referred to the process in the multi-hop communication scenario above, which will not be repeated here.

[0458] Based on the routing process in Embodiment 4, this embodiment provides a routing mechanism 4, which includes:

[0459] After generating data packet 1, the UE adds a BAP header to it, generating data packet 2. The BAP header of data packet 2 contains destination routing indication information, which is the UE's uplink dedicated routing indication information (indicating the address of the target relay UE). The UE then transmits data packet 2 to the relay UE it is connected to.

[0460] After receiving packet 3, any UE first determines whether the destination address contained in the target routing indication information in the BAP header of packet 3 is the same as its own address;

[0461] If the two are determined to be the same, then data packet 3 is determined to be its own data packet. Data packet 3 is decapsulated to obtain data packet 4 without a BAP header. Then, subsequent processing is performed based on the data carried in data packet 4.

[0462] If the two are determined to be different, then in at least one of the routing information stored locally, the target routing information containing the target routing indication information is searched, and the next-hop node address corresponding to the target routing indication information is determined in the target routing information, and the next hop indicated by the next-hop node address is determined; and data packet 3 is sent to the determined next hop.

[0463] It should also be noted that, since the head relay UE does not have uplink routing information in this embodiment, the strategy executed by the head relay UE is similar to that in Mechanism 1, that is, the head relay UE can determine subsequent actions by combining the interface. Specifically, after the head relay UE receives data packet 2, if it determines that the destination address contained in the target routing indication information in the BAP header of data packet 2 is the same as its own address, it then determines the interface used to receive data packet 2; if the interface is the Uu interface, it further determines that data packet 2 is its own data packet; if the interface is the PC5 interface, it determines that the AN device is the transmission target.

[0464] Based on the descriptions of the four embodiments above, it can be seen that in the multi-hop communication scenario shown in the fourth embodiment (continuing to take link 1 as an example), the final complete protocol stack can be as follows: Figure 11 As shown, the data packets transmitted by each device in link 1 all carry a BAP header.

[0465] Based on the routing method provided in Implementation Example 4, Figure 1 In the communication system shown, when the AN device sends a data packet with each UE as the destination device, the content of the BAP header in that data packet can be referenced. Figure 12 As shown.

[0466] Example 5:

[0467] The method provided in this embodiment uses the address of the UE or the address of the AN device as routing indication information to guide the routing and transmission of data packets. The method provided in this embodiment can also be applied to... Figure 9 The routing method flowchart shown below will continue using link 1 as an example, and will be referenced in the following text. Figure 9 The method provided in this application embodiment will be described in detail below. Similar to Embodiment 4, in this application embodiment, the BAP header of the data packet includes target routing indication information and does not need to include the target device local identifier.

[0468] S900: The AN device configures an address and at least one routing information for each UE in the communication system.

[0469] This step is similar to that in Example 4, except that:

[0470] 1. In the embodiments of this application, the AN device itself is also configured with an address (i.e., add.AN). The AN device can send its own address to the head relay UE in each link so that the head relay UE can subsequently determine the AN device indicated by the address of the AN device, thereby determining the transmission object and realizing the transmission of data packets to the AN device.

[0471] In this application, add.AN can be the default AN address, an address assigned by the AN device itself, or a user-configured address; no such limitation applies.

[0472] 2. In the embodiments of this application, the default route indication information add.xxx can be the address of the AN device, add.AN, or another default address indicating the AN device. This application does not limit this. The following embodiments are described with the addition.xxx being different from the addition.AN.

[0473] 3. Since the AN device has an address, the routing information configured by the AN device for each UE is also different from the routing information in Embodiment 4.

[0474] Since the AN device has an address, for uplink transmission, the next-hop node of the head relay UE in each link is the AN device. Therefore, the AN device can configure uplink routing information for each UE, and this uplink routing information is different from that in Embodiment 4. (It should be noted that the downlink routing information configured by the AN device for each relay UE in this embodiment is the same as that in Embodiment 4).

[0475] To compare with the routing information of UE2 and UE3 in Implementation 4, this embodiment continues to take Link 1 as an example. The uplink routing information containing the default routing indication information configured by the AN device for UE2, UE3 and UE4 are shown in Tables 15-17 respectively:

[0476] Table 15: Routing Information for UE2

[0477]

[0478] Table 16: Routing Information for UE3

[0479]

[0480] Table 17: Routing Information for UE4

[0481]

[0482] S901-S904 are the same as S901-S904 in Embodiment 4, and will not be described again here.

[0483] S905: After receiving the second data packet, UE4 can obtain the destination routing indication information (i.e., the default routing indication information add.xxx) of the second data packet from its BAP header. When UE4 determines that the destination address (add.xxx) contained in the destination routing indication information is different from its own address (add.UE4), it determines the destination routing information containing the destination routing indication information (e.g., the routing information in Table 17) from at least one stored routing information. It then determines the next-hop node address (i.e., add.AN) corresponding to the destination routing indication information in this destination routing information and identifies the transmission target as the next-hop node indicated by that next-hop node address (i.e., the AN device indicated by add.AN). UE4 sends the second data packet to the AN device. The AN device receives the second data packet from UE4.

[0484] S906-S907 are the same as S906-S907 in Embodiment 4, and will not be described again here.

[0485] S908a: The AN device assigns an address (i.e., add.UE1) to UE1, determines the uplink dedicated routing indication information (hereinafter referred to as UL routing indication information-UE1) and downlink dedicated routing indication information (hereinafter referred to as DL routing indication information-UE1) of UE1, and sends / configures UL routing indication information-UE1 and add.UE1 to UE1 so that UE1 can use UL routing indication information-UE1 to realize uplink transmission of UE1.

[0486] Optionally, when configuring UL routing indication information -UE1 and add.UE1 to UE1, the AN device can send the above information to UE2, and UE2 can then send it to UE1 via SL RRC message.

[0487] The UL routing indication information - UE1 contains the address of the destination device in the uplink transmission direction. In this embodiment, the destination device is an AN device; therefore, the UL routing indication information - UE1 contains the address of the AN device, add.AN.

[0488] The DL routing indication information - UE1 contains the destination device address (i.e., add.UE1) for the downlink transmission direction.

[0489] In one implementation, the number of UL routing indication information - UE1 can be one, and the number of DL routing indication information - UE1 can also be one.

[0490] In another implementation, the AN device can determine the uplink dedicated routing indication information (containing multiple UL routing indication information - UE1) and / or downlink dedicated routing indication information (containing multiple DL routing indication information - UE1) of UE1 at the bearer level. Different UL routing indication information - UE1 / DL routing indication information - UE1 correspond to different bearers.

[0491] S908b: The AN device configures new routing information for each relay UE in the link based on the UL routing indication information of UE1 (UE1) and the DL routing indication information of UE2 (UE2), so that each relay UE can realize the uplink and downlink transmission of UE1 according to the routing information.

[0492] The new routing information allocated by the AN device to UE2, UE3, and UE4 is shown in Tables 18-20, respectively:

[0493] Table 18: Routing Information for UE2

[0494]

[0495] Table 19: Routing Information for UE3

[0496]

[0497] Table 20: Routing Information for UE4

[0498]

[0499] Following S908b, each device in Link 1 can utilize the UL routing indication information -UE1 and the DL routing indication information -UE1 to achieve uplink and downlink transmission of UE1. Specifically, S909-S913 correspond to the uplink transmission process of UE1, and S914-S918 correspond to the downlink transmission process of UE1.

[0500] It should be noted that since the DL routing indication information configured by the AN device for UE1 is the same as that in Embodiment 4, each device in Link 1 can adopt the same process as in Embodiment 4 to implement the downlink transmission process according to the DL routing indication information for UE1. Based on this, the downlink transmission process of S214-S217 in this embodiment will not be described again, and the specific process can be referred to the description in Embodiment 1 above.

[0501] Since the UL routing indication information configured by the AN device for UE1 is different from that in Embodiment 4, the uplink transmission process S909-S913 implemented by each device in Link 1 according to the UL routing indication information for UE1 is described in detail below.

[0502] S909: UE1 generates a third data packet, which does not have a BAP header. Optionally, the third data packet may carry user plane data or control plane data of UE1, which is not limited in this application. UE1 uses the UL routing indication information -UE1 as the destination routing indication information of the third data packet, and adds a BAP header to the third data packet to generate a fourth data packet, wherein the BAP header of the fourth data packet contains the destination routing indication information (UL routing indication information -UE1, including add.AN). UE1 sends the fourth data packet to UE2. UE2 receives the fourth data packet from UE1.

[0503] In this embodiment, UE1 can also determine the transmission object as UE2 through two implementation methods. The specific process can be referred to the corresponding description in S909 of Embodiment 4, which will not be repeated here.

[0504] S910: After receiving the fourth data packet, UE2 obtains the target routing indication information (i.e., UL routing indication information - UE1, containing add.AN) from the BAP header of the fourth data packet. When it is determined that the destination address (add.AN) contained in the target routing indication information is different from its own address (add.UE2), it determines the target routing information containing the target routing indication information (e.g., the first routing indication information in Table 18) from at least one stored routing information. It then determines the next-hop node address (i.e., add.UE3) corresponding to the target routing indication information in the target routing information and determines that the transmission object is the next-hop node indicated by that next-hop node address (i.e., UE3 indicated by add.UE3). UE2 sends the fourth data packet to UE3. UE3 receives the fourth data packet from UE2.

[0505] S911: After receiving the fourth data packet, UE3 obtains the destination routing indication information (i.e., UL routing indication information - UE1, containing add.AN) from the BAP header of the fourth data packet. When it is determined that the destination address (add.AN) contained in the destination routing indication information is different from its own address (add.UE3), it determines the destination routing information containing the destination routing indication information (e.g., the first routing indication information in Table 19) from at least one stored routing information. It then determines the next-hop node address (i.e., add.UE4) corresponding to the destination routing indication information in the destination routing information and determines that the transmission object is the next-hop node indicated by that next-hop node address (i.e., UE4 indicated by add.UE4). UE3 sends the fourth data packet to UE4. UE4 receives the fourth data packet from UE3.

[0506] S912: After receiving the fourth data packet, UE4 obtains the target routing indication information (i.e., UL routing indication information - UE1, containing add.AN) from the BAP header of the fourth data packet. When it is determined that the destination address (add.AN) contained in the target routing indication information is different from its own address (add.UE4), it determines the target routing information containing the target routing indication information from at least one stored routing information (e.g., the first routing indication information in Table 20), determines the next-hop node address (i.e., add.AN) corresponding to the target routing indication information in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node address (i.e., the AN device indicated by add.AN). UE4 sends the fourth data packet to the AN device. The AN device receives the fourth data packet from UE4.

[0507] S913: Same as S213, will not be repeated here.

[0508] This application provides a routing method that uses the address of the UE or the address of the AN device as routing indication information to guide the routing of data packets, thereby enabling routing between the AN device and the remote UE in a multi-hop communication scenario.

[0509] Similarly, the routing method provided in this embodiment can also be used to realize routing transmission in single-hop communication scenarios. The specific process can be referred to the description in the above embodiments, and will not be repeated here.

[0510] In conjunction with the routing process in Embodiment 5, this application provides a routing mechanism 5, which includes:

[0511] After generating data packet 1, the UE adds a BAP header to it, generating data packet 2. The BAP header of data packet 2 contains destination routing indication information, which is the UE's uplink dedicated routing indication information (indicating the address of the target relay UE). The UE then transmits data packet 2 to the relay UE it is connected to.

[0512] After receiving packet 3, any UE first determines whether the destination address contained in the target routing indication information in the BAP header of packet 3 is the same as its own address;

[0513] If the two are determined to be the same, then data packet 3 is determined to be its own data packet. Data packet 3 is decapsulated to obtain data packet 4 without a BAP header. Then, subsequent processing is performed based on the data carried in data packet 4.

[0514] If the two are determined to be different, then in at least one of the routing information stored locally, the target routing information containing the target routing indication information is searched, and the next-hop node address corresponding to the target routing indication information is determined in the target routing information, and the next hop indicated by the next-hop node address is determined; and data packet 3 is sent to the determined next hop.

[0515] As can be seen from the description in Embodiment 5 above, in the multi-hop communication scenario shown in Embodiment 5 (continuing to take link 1 as an example), the final complete protocol stack can be as follows: Figure 11 As shown.

[0516] Based on the routing method provided in Embodiment 5, Figure 1 In the communication system shown, when the AN device sends a data packet with each UE as the destination device, the content of the BAP header in that data packet can be referenced. Figure 13 As shown.

[0517] Example 6:

[0518] Based on embodiments four and five above, this application also provides another routing method. In this method, the device address and path ID are used together as routing indication information to guide the routing and transmission of data packets.

[0519] Similar to the description of path ID in Embodiment 3, in this embodiment of the application, the path ID assigned by the AN device to each link may or may not distinguish the transmission direction.

[0520] The following example illustrates how AN devices assign a path ID to each communication link without distinguishing the transmission direction.

[0521] For example, using the routing method provided in Embodiment 4, the AN device assigns corresponding path IDs to the following communication links:

[0522] UE4-AN device — path ID-1;

[0523] UE7-AN device — path ID-2;

[0524] UE8-AN device — path ID-3;

[0525] UE3-UE4-AN device — path ID-4;

[0526] UE5-UE4-AN device — path ID-5;

[0527] UE9-UE8-AN device — path ID-6;

[0528] UE11-UE8-AN device — path ID-7;

[0529] UE2-UE3-UE4-AN device — path ID-8;

[0530] UE6-UE3-UE4-AN device — path ID-9;

[0531] UE10-UE9-UE8-AN device — path ID-10;

[0532] UE1-UE2-UE3-UE4-AN device——path ID-11.

[0533] Additionally, the AN device assigns a path ID -yyy for the default route indication information.

[0534] Based on this example, the routing information assigned by the AN device to the UE in Link 1 in an S908b implementation is shown in Tables 21-23.

[0535] Table 21: Routing Information for UE2

[0536]

[0537]

[0538] Table 22: Routing Information for UE3

[0539]

[0540] Table 23: Routing Information for UE4

[0541]

[0542] It should be noted that after each remote UE establishes a Uu communication connection with the AN device, the AN device assigns uplink dedicated routing indication information and downlink dedicated routing indication information to the remote UE. This routing indication information includes not only the corresponding address but also the path ID assigned by the AN device to the communication link where the remote UE resides.

[0543] The routing mechanism 6 provided in this application embodiment can refer to mechanism 4 provided in embodiment 4 or mechanism 5 provided in embodiment 5. For details, please refer to the above detailed description of mechanism 4 or mechanism 5, which will not be repeated here. It is worth noting that in mechanism 5, the path identifier and device address in the routing indication information included in the target routing information found by the UE are the same as the target path identifier and destination address in the target routing indication information.

[0544] Based on the routing method provided in Implementation Example 6, Figure 1 In the communication system shown, when the AN device sends a data packet with each UE as the destination device, the content of the BAP header in that data packet can be referenced. Figure 14 As shown.

[0545] Example 7:

[0546] This embodiment uses path identifiers as routing information to guide the routing and transmission of data packets. See below for further details. Figure 15 The flowchart of the routing method shown below provides a detailed explanation of the method provided in this embodiment.

[0547] S1501: UE1 establishes an SL communication connection with UE2, and establishes a Uu communication connection with the AN device through UE2 and other relay UEs. UE1 may assign a device identifier (hereinafter abbreviated as EID-UE1) to itself during or after establishing an SL communication connection with UE2; or UE2 may assign a device identifier EID-UE1 to UE1 during or after establishing an SL communication connection with UE1; or the AN device may assign a device identifier EID-UE1 to UE1 during or after establishing a Uu communication connection with UE1.

[0548] The device identifier involved in the embodiments of this application can be used to identify other UEs accessing the relay UE within the scope of the relay UE. Optionally, the device identifier can be a local identifier (LID) or a layer 2 identifier (L2ID), and this application does not limit it in this regard.

[0549] S1502: UE2 or UE1 notifies the AN device of UE1's device identifier EID-UE1. The AN device determines the uplink dedicated routing indication information (UL routing indication information-UE1) and downlink dedicated routing indication information (DL routing indication information-UE1) of UE1; and configures new routing information for each relay UE in link 1 according to the UL routing indication information-UE1 and the DL routing indication information-UE1, so that each relay UE can realize UE1's uplink and downlink transmission according to the routing information.

[0550] Both the UL routing indication information - UE1 and the DL routing indication information - UE1 contain the path identifier (path ID - UE1) assigned to UE1 by the AN device. To distinguish between the UL routing indication information - UE1 and the DL routing indication information - UE1, and to ensure that the relay UE can find the correct routing information to transmit data packets, this application embodiment can be implemented through the following two methods:

[0551] In the first implementation, the path identifier (path ID-UE1) of UE1 includes two parts: the path identifier of UE1 in the uplink transmission direction (abbreviated as UL path ID-UE1) and the path identifier of UE1 in the downlink transmission direction (abbreviated as DL path ID-UE1).

[0552] In the second implementation, UE1 has a single path ID (path ID-UE1), but the dedicated routing indication information for different directions also includes corresponding transmission direction indications. That is, the UL routing indication information-UE1 also includes UL indications, and the DL routing indication information-UE1 also includes DL indications.

[0553] To enable routing transmission for UE1, the AN device also needs to provide at least one routing information for each relay UE. Each routing information includes a routing indication and the identifier of the next-hop node device corresponding to that routing indication.

[0554] It should be noted that the AN device provides at least one routing information for each relay UE, which includes downlink routing information and uplink routing information. The downlink routing information and uplink routing information can be indistinguishable in form, but the downlink routing information includes DL routing indication information - UE1, while the uplink routing information includes UL routing indication information - UE1.

[0555] The following description uses only the first implementation method as an example.

[0556] For example, the new routing information assigned by the AN device to UE2, UE3 and UE4 is shown in Tables 24-26 respectively.

[0557] Table 24: Routing Information for UE2

[0558]

[0559] The second routing information in Table 24 is optional. In one implementation, the AN device allocates both routing information entries from Table 24 to UE2; in another implementation, the AN device allocates only the first routing information entry from Table 24 to UE2. Here, `default EID-UE` can be the default device identifier of the UE. When UE2 determines that the next-hop node device identifier corresponding to the destination routing indication information of a data packet is `default EID-UE`, it indicates that there is no next-hop node and the data packet needs to be forwarded to the remote UE of UE2, or that the data packet is its own data packet. The device identifier of the AN device can be a second default device identifier, such as EID-111.

[0560] Table 25: Routing Information for UE3

[0561]

[0562] Table 26: Routing Information for UE4

[0563]

[0564] Currently, when two UEs establish an SL communication connection, each UE assigns an L2 ID to that SL communication connection. For example, after UE1 and UE2 establish an SL communication connection, UE1 assigns L2 ID-UE1 to the communication connection, and UE2 assigns L2 ID-UE2 to the communication connection. UE1 and UE2 then notify each other of their respective L2 IDs. Thus, when UE1 sends a data packet to UE2, it adds L2 ID-UE1 as the source device identifier and L2 ID-UE2 as the destination device identifier to the data packet; similarly, when UE2 sends a data packet to UE2, it adds L2 ID-UE2 as the source device identifier and L2 ID-UE1 as the destination device identifier to the data packet.

[0565] In scenarios where a relay UE assigns device identifiers (e.g., local identifiers) to other UEs accessing it, these other UEs are the next-hop nodes of the relay UE in the downlink transmission direction. Therefore, the relay UE can identify the next-hop node indicated by the next-hop node device identifier (the local identifier of the next-hop node), thereby enabling downlink data packet transmission. However, in the uplink transmission direction, a relay UE generally cannot directly identify the next-hop node indicated by the next-hop node device identifier. Therefore, this application can solve this problem using the SL communication connection identifier (i.e., L2 ID) through the following implementation method:

[0566] First implementation method:

[0567] The AN device sends the following two pieces of information to each relay UE: the device identifier of the next-hop node in its uplink transmission direction, and the L2 ID of the next-hop node (i.e., the L2 ID assigned by the next-hop node for the SL communication connection between the relay UE and the next-hop node).

[0568] For example, in Link 1, the AN device sends the device identifier and L2 ID of UE3 to UE2 (EID-UE3 (i.e., LID-UE3), L2 ID-UE3); the AN device sends the device identifier and L2 ID of UE4 to UE3 (EID-UE4 (LID-UE4), L2 ID-UE4). EID-UE3 can be assigned by UE4 to UE3, and EID-UE4 can be assigned by either the AN device or UE4.

[0569] In addition, the AN device sends its device identifier (EID-AN) to the head relay UEs in each communication link so that these head relay UEs can determine that the device identifier of the AN device indicates the AN device. The device identifier of the AN device can be a first default device identifier, such as EID-000.

[0570] Second implementation method:

[0571] After any UE accesses the AN device through another UE with which it has established an SL communication connection, the UE can assign a device identifier (e.g., a local identifier) ​​to the other UE with which it has established an SL communication connection, and report the device identifier of the other UE and the L2 ID of the other UE (assigned by the other UE for the SL communication connection between the UE and the other UE) to the AN device. In this way, the AN device can generate the above routing information based on the received device identifiers.

[0572] For example, after UE3 establishes an SL communication connection with UE4, UE4 assigns a device identifier (EID-UE3, i.e., LID-UE3) to UE3, and UE3 also assigns a dedicated device identifier (EID-UE4-UL, distinct from UE4's local identifier LID-UE4) to UE4. UE3 then sends UE4's dedicated device identifier and the L2 ID-UE4 assigned by UE4 for this SL communication connection to the AN device. At this point, the AN device assigns uplink routing information to UE3 based on EID-UE4-UL, meaning that the EID-UE4 included in the first routing information entry in Table 25 is actually EID-UE4-UL in this example; while the AN device assigns downlink routing information to UE4 based on EID-UE3, meaning that the EID-UE3 included in the second routing information entry in Table 26 is the EID-UE3 (LID-UE3) assigned by UE4 to UE3 in this example.

[0573] For example, after UE2 establishes an SL communication connection with UE3, UE3 assigns a device identifier (EID-UE2, i.e., LID-UE2) to UE2, and UE2 also assigns a dedicated device identifier (EID-UE3-UL, distinct from UE3's local identifier LID-UE3) to UE3. UE2 then sends UE4's dedicated device identifier and the L2 ID-UE4 assigned by UE4 for this SL communication connection to the AN device. At this point, the AN device assigns uplink routing information to UE2 based on EID-UE3-UL, meaning that EID-UE3 included in the first routing information entry in Table 24 is actually EID-UE3-UL in this example. Meanwhile, the AN device assigns downlink routing information to UE3 based on EID-UE2, meaning that EID-UE3 included in the second routing information entry in Table 25 is the EID-UE3 (LID-UE3) assigned by UE3 to UE3 in this example.

[0574] In addition, each head relay UE in the communication link of the communication system also assigns a device identifier (i.e., EID-AN) to the connected AN device so that these head relay UEs can determine the device identifier of the AN device. Any head relay UE can send the device identifier it assigned to the AN device to the AN device, so that the AN device can allocate uplink routing information to the head relay UE based on the device identifier of the AN device. For example, the EID-AN included in the routing information in Table 26 is assigned by UE4 to the AN device. Alternatively, the communication system can default the device identifier of the AN device to the first default device identifier, such as EID-000; in this way, the head relay UEs in each communication link do not need to assign a device identifier to the AN device. The following explanation only uses the device identifier of the AN device as the first default device identifier as an example.

[0575] Following S1502, each device in Link 1 can utilize the UL routing indication information -UE1 and the DL routing indication information -UE1 to achieve uplink and downlink transmission of UE1. Specifically, S1503-S1507 correspond to the uplink transmission process of UE1, and S1508-S1511 correspond to the downlink transmission process of UE1.

[0576] The uplink transmission process of UE1 will be explained below.

[0577] S1503: UE1 generates a first data packet, which does not contain a BAP header. Furthermore, the first data packet may carry user plane data or control plane data of UE1; this application does not implicitly limit this. UE1 sends the first data packet to UE2, and UE2 receives the first data packet from UE1.

[0578] S1504: After receiving the first data packet, UE2 uses the uplink dedicated routing indication information of UE1 (UL routing indication information-UE1, UL path ID-UE1) as the destination routing indication information of the first data packet. When UE2 determines, from at least one stored routing information, a destination routing information containing this destination routing indication information (e.g., item 1 in Table 24), it determines the next-hop node device identifier (i.e., EID-UE3) corresponding to the destination routing indication information in the destination routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node device identifier (i.e., UE3 indicated by EID-UE3). As the last relay UE of UE1, UE2 determines that the destination device identifier of the first data packet is the device identifier of the source device of the first data packet (i.e., the device identifier of UE1: EID-UE1), and adds a BAP header to the first data packet to generate a second data packet, wherein the BAP header of the second data packet contains the destination routing indication information UL path ID-UE1 and the destination device identifier EID-UE1. UE2 sends the second data packet to UE3. UE3 receives the second data packet from UE2.

[0579] S1505: After receiving the second data packet, UE3 obtains the target routing indication information (i.e., UL routing indication information-UE1, UL path ID-UE1) from the BAP header of the second data packet. When at least one stored routing information determines target routing information containing this target routing indication information (e.g., item 1 in Table 25), UE3 determines the next-hop node device identifier (i.e., EID-UE4) corresponding to the target routing indication information in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node device identifier (i.e., UE4 indicated by EID-UE4). UE3 sends the second data packet to UE4. UE4 receives the second data packet from UE3.

[0580] S1506: After receiving the second data packet, UE4 obtains the target routing indication information (i.e., UL routing indication information-UE1, UL path ID-UE1) of the second data packet from its BAP header. When at least one stored routing information determines target routing information containing this target routing indication information (e.g., item 1 in Table 26), UE4 determines the next-hop node device identifier (i.e., EID-AN) corresponding to the target routing indication information in that target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node device identifier (i.e., the AN device indicated by EID-AN). UE4 sends the second data packet to the AN device. The AN device receives the second data packet from UE4.

[0581] S1507: After receiving the second data packet, the AN device decapsulates it to obtain a first data packet without a BAP header. The AN device can then perform subsequent processing based on the data carried in the first data packet (e.g., user plane data or control plane data), such as sending user plane data to the core network equipment or performing corresponding operations based on the control plane data.

[0582] The downlink transmission process of UE1 will be explained below.

[0583] S1508: The AN device receives a third data packet, which does not have a BAP header. Additionally, the third data packet may carry user plane data or control plane data (e.g., signaling) of UE1; this application does not limit this. Optionally, the third data packet can be generated by the AN device itself or received from the core network device. The AN device uses the stored downlink dedicated routing indication information (DL routing indication information-UE1, DL path ID-UE1) of UE1 as the destination routing indication information of the third data packet, and determines the destination device identifier of the third data packet as the device identifier of the destination device (UE1) of the third data packet (i.e., EID-UE1, for example, the local identifier LID-UE1 assigned to UE1 by UE2). The AN device adds a BAP header to the third data packet, generating a fourth data packet, wherein the BAP header of the fourth data packet contains the destination routing indication information DL path ID-UE1 and the destination device identifier EID-UE1. The AN device sends the fourth data packet to UE4. UE4 receives the fourth data packet from the AN device.

[0584] In this application embodiment, the AN device may, but is not limited to, determine the transmission target as UE4 through the following implementation methods:

[0585] In one implementation, the AN device can determine the head relay UE—UE4—in the communication link where UE1 is located based on the topology of the communication system.

[0586] In another implementation, after the AN device allocates downlink dedicated routing indication information (DL routing indication information-UE1) to UE1 in S1502, it can also determine the head relay UE corresponding to the downlink dedicated routing indication information of UE1 (i.e., DL routing indication information-UE1 corresponds to UE4). In this way, when the AN device determines that the destination routing indication information of the third data packet is DL routing indication information-UE1, it can also determine that the transmission object is UE4 corresponding to DL routing indication information-UE1.

[0587] In another implementation, the AN device can maintain at least one routing information (all downlink routing information). Thus, after allocating downlink dedicated route indication information (DL route indication information - UE1) to UE1 in S1502, a routing information can be generated as follows:

[0588] Routing indication information: DL routing indication information - UE1, next hop node device identifier: EID.UE4.

[0589] In this way, when the AN device determines that the destination routing indication information of the third data packet is DL routing indication information-UE1, it can also determine that the transmission object is the next-hop node device identifier corresponding to DL routing indication information-UE1, and determine the next-hop node indicated by the next-hop node device identifier (UE4 indicated by EID.UE4). Among them, the device identifier of UE4 (EID-UE4) can be assigned to it by the AN device.

[0590] S1509: After receiving the fourth data packet, UE4 obtains the target routing indication information (i.e., DL routing indication information-UE1, DL path ID-UE1) from the BAP header of the fourth data packet. When at least one stored routing information determines target routing information containing this target routing indication information (e.g., item 2 in Table 26), UE4 determines the next-hop node device identifier (i.e., EID-UE3) corresponding to the target routing indication information in the target routing information, and determines that the transmission object is the next-hop node indicated by the next-hop node device identifier (i.e., UE3 indicated by EID-UE3). UE4 sends the fourth data packet to UE3. UE3 receives the fourth data packet from UE4.

[0591] S1510: After receiving the fourth data packet, UE3 obtains the target routing indication information (i.e., DL routing indication information-UE1, DL path ID-UE1) of the fourth data packet from its BAP header. When at least one stored routing information determines target routing information containing this target routing indication information (e.g., item 2 in Table 25), UE3 determines the next-hop node device identifier (i.e., EID-UE2) corresponding to the target routing indication information in that target routing information, and determines that the transmission object is the next-hop node indicated by that next-hop node device identifier (i.e., UE2 indicated by EID-UE2). UE3 sends the fourth data packet to UE2. UE2 receives the fourth data packet from UE3.

[0592] S1511: After receiving the fourth data packet, UE2 obtains the target routing indication information (i.e., DL routing indication information-UE1, DL path ID-UE1) of the fourth data packet from its BAP header. If UE2 has routing information containing the target routing indication information (such as the second routing information in Table 24), and at least one of the stored routing information determines that the target routing information contains the target routing indication information (e.g., the second item in Table 24), the next-hop node device identifier (i.e., default EID-UE) corresponding to the target routing indication information is determined in the target routing information, and the next-hop node indicated by the next-hop node device identifier is determined to be UE2. UE2 obtains the target device identifier (EID-UE1) of the fourth data packet from its BAP header. Alternatively, if UE2 determines that it does not have routing information containing the target routing indication information, it obtains the target device identifier (EID-UE1) of the fourth data packet from its BAP header. UE2 determines that the transmission target is the remote UE indicated by the target device identifier (i.e., UE1 indicated by EID-UE1). UE2 decapsulates the fourth data packet, obtaining a third data packet without a BAP header. UE2 sends the third data packet to UE1. UE1 receives the third data packet from UE2.

[0593] Afterwards, UE1 can perform subsequent processing based on the data carried in the first data packet.

[0594] This application provides a routing method that uses the UE's device identifier as routing indication information to guide the routing of data packets, thereby enabling routing between the AN device and the remote UE in a multi-hop communication scenario.

[0595] Based on the routing method provided in this embodiment, routing transmission in single-hop communication scenarios can also be realized. For the specific process, please refer to the description in the above embodiments, which will not be repeated here.

[0596] In conjunction with the routing process in Embodiment 7, this application provides a routing mechanism 7, which includes:

[0597] Downward direction:

[0598] When the AN device sends data packet 1 to a remote UE, it needs to add a BAP header to the data packet to generate data packet 2. The BAP header of data packet 2 contains target route indication information and target device identifier. The target route indication information is the downlink dedicated route indication information of the remote UE (including the path identifier assigned to the remote UE by the AN device), and the target device identifier is the identifier of the remote UE.

[0599] After receiving data packet 2, any relay UE searches for target routing information containing target routing indication information in at least one locally stored routing information. If the next-hop node device identifier corresponding to the target routing indication information contained in the target routing information is the second default device identifier, data packet 2 is transmitted to the remote device indicated by the target device identifier in data packet 2; or if it is determined that the target routing information does not exist in at least one locally stored routing information, data packet 2 is transmitted to the remote device indicated by the target device identifier in data packet 2. If the target routing information is found in at least one locally stored routing information and the next-hop node device identifier corresponding to the target routing information is not the second default device identifier, the next-hop node indicated by the next-hop node device identifier is determined, and data packet 2 is sent to the next-hop node.

[0600] Upward direction:

[0601] The working mechanism is similar to that of the aforementioned downward direction.

[0602] The difference lies in the fact that after receiving data packet 1 (without a BAP header) from the remote UE, the relay UE determines the target routing indication information and target device identifier of data packet 1. The target routing indication information is the uplink dedicated routing indication information of the remote UE (containing the path identifier assigned to the remote UE by the AN device), and the target device identifier is the local identifier of the remote UE. The relay UE adds a BAP header to data packet 1, generating data packet 2, whose BAP header contains the target routing indication information and target device identifier. Then, following the above mechanism, it determines the transmission target and sends data packet 2.

[0603] Based on the description in Embodiment 7 above, in the multi-hop communication scenario shown in Embodiment 7 (continuing to take link 1 as an example), the final complete protocol stack can be as follows: Figure 5 As shown.

[0604] Based on the routing method provided in Embodiment 7 above, Figure 1 In the communication system shown, the content of the BAP header in the data packet when the AN device sends data packets with each UE as the destination device can be referred to... Figure 16 As shown.

[0605] Example 8:

[0606] In some embodiments, an adaptation layer is introduced into the protocol stack to carry information such as bearer ID (BID) to support bearer mapping. The bearer connection enables IP connectivity, transmitting service data streams between the UE and the network side, and achieving more granular Quality of Service (QoS) control. For example, the bearer ID can be distinguished by function: Default Bearer, Dedicated Bearer; or by sequence number: Bearer 1, Bearer 2, etc.

[0607] In multi-hop communication scenarios, there is a BAP layer in the protocol stack between the remote UE and the relay UE, and the data packet contains a BAP header, which needs to carry BID, so that multiple data resource bearers (DRBs) of the remote UE can be transmitted through a single SL-DRB between the remote UE and the relay UE, that is, to realize the N:1 mapping between DRB and SL-DRB.

[0608] In these embodiments, the multi-hop scenario protocol stack is as follows: Figure 17 Or as shown in 18. Wherein, in Figure 17 and Figure 18 In this example, we will use BAP as the adaptation layer.

[0609] in, Figure 17 and Figure 18 The difference lies in whether the relay UE is implemented as two BAP entities or as a single BAP entity to relay between the remote UE and the AN device.

[0610] In situations where a BAP layer is introduced to support bearer mapping in multiple communication scenarios, and the protocol stack in such scenarios is as follows: Figure 17 As shown, the routing method provided in the above embodiments needs to be adjusted as follows:

[0611] Let's continue with link 1 as an example.

[0612] The following A1 to A3 are modifications to an embodiment where data packets transmitted by a remote UE do not have a BAP header.

[0613] A1. In the method provided in the above embodiments, when UE1 sends data packet 1 without a BAP header to UE2, after receiving data packet 1, UE2 adds a BAP header to data packet 1 to generate data packet 2.

[0614] In this embodiment, UE1 sends data packet 1 with a BAP header to UE2. However, this BAP header does not contain target routing information or target device identifier; it only contains bearer identifier. After receiving data packet 1, UE2 first decapsulates data packet 1 to obtain a data packet without a BAP header. Then, it adds a BAP header to this data packet to generate data packet 2. The BAP header of data packet 2 contains target routing information, target device identifier, and bearer identifier.

[0615] A2. In the method provided in the above embodiments, the AN device sends a data packet 3 with a BAP header to the UE4. The BAP header of the data packet 3 contains target routing indication information and target device identifier.

[0616] In this embodiment, the AN device sends data packet 3 with a BAP header to UE4. The BAP header of data packet 3 contains target routing indication information and target device identifier, as well as bearer identifier.

[0617] A3. In the method provided in the above embodiments, UE2, acting as the last relay UE of UE1, receives data packet 4, wherein the BAP header of data packet 4 contains target routing indication information and target device identifier. UE2 decapsulates data packet 4 to obtain data packet 5 without a BAP header, and sends data packet 5 to UE1.

[0618] In this embodiment, UE2, acting as the last relay UE of UE1, receives data packet 4. The BAP header of data packet 4 contains target routing indication information, a target device identifier, and a bearer identifier. UE2 decapsulates data packet 4 to obtain a data packet without a BAP header; it then adds a BAP header to this data packet to generate data packet 5, and sends data packet 5 to UE1. The BAP header of data packet 5 only contains the bearer identifier.

[0619] The following B1 to B3 are modifications to an embodiment for data packets transmitted by a remote UE that have a BAP header.

[0620] B1. In the method provided in the above embodiments, UE1 sends data packet 1 with a BAP header to UE2, wherein the BAP header of data packet 1 contains target routing indication information and target device identifier.

[0621] In this embodiment, UE1 sends data packet 1 with a BAP header to UE2. The BAP header of data packet 1 contains not only target routing indication information and target device identifier, but also bearer identifier.

[0622] B2. In the method provided in the above embodiments, the AN device sends data packet 2 with a BAP header to the UE4. The BAP header of data packet 2 contains target routing indication information and target device identifier.

[0623] In this embodiment, the AN device sends data packet 2 with a BAP header to UE4. The BAP header of data packet 2 contains target routing indication information and target device identifier, as well as bearer identifier.

[0624] B3. In the method provided in the above embodiments, UE2 sends data packet 3 with a BAP header to UE1. The BAP header of data packet 3 contains target routing indication information and target device identifier.

[0625] In this embodiment, UE2 sends data packet 3 with a BAP header to UE1. The BAP header of data packet 3 contains target routing indication information, target device identifier, and bearer identifier. That is, UE2 does not process the received data packet 3 and forwards it directly to UE1.

[0626] In multi-hop communication scenarios, a BAP layer is introduced to support bearer mapping, and the protocol stack in this scenario is as follows: Figure 18 As shown, the routing method provided in the above embodiments needs to be adjusted as follows:

[0627] Let's continue with link 1 as an example.

[0628] The following C1 to C3 are modifications to an embodiment where data packets transmitted by a remote UE do not have a BAP header.

[0629] C1. In the method provided in the above embodiments, when UE1 sends data packet 1 without a BAP header to UE2, after receiving data packet 1, UE2 adds a BAP header to data packet 1 to generate data packet 2.

[0630] In this embodiment, UE1 sends data packet 1 with a BAP header to UE2. However, this BAP header does not contain target routing indication information and target device identifier; it only contains bearer identifier. After receiving data packet 1, UE2 adds the target routing indication information and target device identifier to the BAP header of data packet 1, thus obtaining data packet 2.

[0631] C2. In the method provided in the above embodiments, the AN device sends a data packet 3 with a BAP header to the UE4. The BAP header of the data packet 3 contains target routing indication information and target device identifier.

[0632] In this embodiment, the AN device sends data packet 3 with a BAP header to UE4. The BAP header of data packet 3 contains target routing indication information and target device identifier, as well as bearer identifier.

[0633] C3. In the method provided in the above embodiments, UE2, acting as the last relay UE of UE1, receives data packet 4, wherein the BAP header of data packet 4 contains target routing indication information and target device identifier. UE2 decapsulates data packet 4 to obtain data packet 5 without a BAP header, and sends data packet 5 to UE1.

[0634] In this embodiment, UE2, acting as the last relay UE of UE1, receives data packet 4. The BAP header of data packet 4 contains target routing indication information and a target device identifier, as well as a bearer identifier. UE2 deletes the target routing indication information and the target device identifier from the BAP header of data packet 4, obtaining data packet 5, and sends data packet 5 to UE1. The BAP header of data packet 5 only contains the bearer identifier.

[0635] For modifications to the implementation of data packets with BAP headers transmitted by remote UEs, please refer to 2-1 to 2-3 above, which will not be repeated here.

[0636] In summary, in link 1, the processing of the BAP header of the data packet conforms to... Figure 19A or Figure 19B As shown. Among them, the above... Figure 19A and Figure 19B The routing-related information includes target route indication information and target device identifier.

[0637] Example 9:

[0638] In the above embodiments, the AN device sends at least one routing information to each relay UE. The following description continues using link 1 as an example. This embodiment provides a routing information configuration method, which can be implemented, but is not limited to, through the following methods:

[0639] In the first implementation: Each relay UE in link 1 has a Uu communication connection (or RRC connection) with the AN device. Therefore, the AN device can use the Uu communication connection with each relay UE to send the routing information configured for that relay UE.

[0640] For example, the AN device can use the Uu communication connection with UE4 to send the routing information configured for UE4; use the Uu communication connection with UE3 to send the routing information configured for UE3; and use the Uu communication connection with UE2 to send the routing information configured for UE2.

[0641] The second implementation method: Some relay UEs may not establish a Uu communication connection with the AN device. These relay UEs refer to other relay UEs besides those that communicate with the AN device via Uu communication; they will be referred to as dedicated relay UEs. For example, if some UEs do not need to establish a Uu communication connection with the AN device themselves, but only provide relay services to other UEs, then these UEs may not need to establish a Uu communication connection with the AN device.

[0642] In this scenario, a dedicated trunk UE can obtain routing information from its parent trunk UE, as shown in the diagram below. That is, the parent trunk UE can provide routing information to the child trunk UE, and optionally, it can also provide the child trunk UE with an address.

[0643] For example, in link 1, UE4 can send UE3's routing information to UE3, and UE3 can send UE2's routing information to UE2. When the AN device initially configures routing information for the head relay UE (UE4), the sent information includes UE4's routing information and at least one first extension information. Each first extension information includes indication information (e.g., local identifier or index) of UE4's sub-relay UE (hereinafter referred to as the first sub-relay UE), as well as the routing information of that first sub-relay UE. Optionally, if a first sub-relay UE of UE4 also has a sub-relay UE (hereinafter referred to as the second sub-relay UE), the first extension information may further include at least one second extension information. Each second extension information includes at least one indication information of the second sub-relay UE and the routing information of that second sub-relay UE.

[0644] UE4 will send the routing information of the first sub-relay UE and the second extended information contained in the first extended information to the first sub-relay UE according to the indication information of the first sub-relay UE in each first extended information.

[0645] The following section continues using Link 1 as an example to illustrate the routing information configuration process for each relay UE in Link 1. In this example, it is assumed that UE2 and UE3 are both dedicated relay UEs.

[0646] S1: The AN device sends the first message to UE4.

[0647] The first message contains: routing information for UE4; first extended information (local identifier of UE3, routing information for UE3, and second extended information (local identifier of UE2, routing information for UE2)).

[0648] S2: UE4 sends a second message to UE3.

[0649] The second message contains: routing information for UE3; and second extended information (local identifier of UE2, routing information for UE2).

[0650] S3: UE3 sends a third message to UE2.

[0651] The third message contains: UE2's routing information.

[0652] Through the second implementation method described above, even when there is no Uu communication connection between some relay UEs and AN devices, the communication system can still complete the routing information configuration for these relay UEs, thereby realizing the routing for communication between remote UEs and AN devices through multiple relay UEs.

[0653] It should also be noted that the above embodiments one to nine do not constitute a limitation on the routing method provided in this application. Routing methods obtained by improvements and adjustments based on the above embodiments are also within the scope of this application. Furthermore, while embodiments one to nine are all described using a U2N system as an example, the methods provided in the above embodiments can also be applied to a U2U system. In a U2U system, end-to-end communication occurs between two UEs, and there is at least one relay UE between the two UEs. When applying the routing method provided in the embodiments of this application to a U2U system, one of the UEs can be configured to perform the behavior of the AN device in the above embodiments.

[0654] Note that in the above embodiments, the SL communication connection established by the two UEs is an SL unicast communication connection.

[0655] Based on the same technical concept, this application also provides a communication device, the structure of which is as follows: Figure 20 As shown, it includes a communication unit 2001 and a processing unit 2002. The communication device 2000 can be applied to, for example... Figure 1 The multi-hop communication system shown can implement the routing method provided in the above embodiments. Optionally, the physical manifestation of the communication device 2000 can be a communication device, such as an AN device or a UE; or the communication device can be other devices capable of implementing the functions of a communication device, such as a processor or chip inside the communication device. Specifically, the communication device 2000 can be a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC), or some other programmable chips.

[0656] The functions of each unit in the device 2000 are described below.

[0657] The communication unit 2001 is used to receive and send data. Optionally, the communication unit 2001 can be implemented by a transceiver, such as a mobile communication module.

[0658] The mobile communication module can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the UE. The mobile communication module may include at least one antenna, at least one filter, a switch, a power amplifier, a low-noise amplifier (LNA), etc. The communication device can interact with other devices in the communication system through the mobile communication module.

[0659] Optionally, the communication device 2000 can be applied to a relay terminal. The specific functions of the processing unit 2002 will be described below using the application of the communication device 2000 to a first relay terminal as an example.

[0660] In one embodiment, the processing unit 2002 is configured to:

[0661] The first data packet is received through the communication unit 2001;

[0662] Obtain first routing indication information and target device identifier of the first data packet, wherein the first routing indication information is used to indicate the transmission route of the first data packet; the target device indicated by the target device identifier is the destination device or source device of the first data packet; determine the first device based on the first routing indication information, or based on the first routing indication information and the target device identifier;

[0663] The second data packet is transmitted to the first device through the communication unit 2001, wherein the data carried by the second data packet is the same as the data carried by the first data packet.

[0664] It should be noted that the second data packet carries the same data as the first data packet, which has two different meanings: First, the first and second data packets are completely identical, and the communication device 2000 did not perform encapsulation or decapsulation processing on the first data packet; Second, the second data packet and the first data packet only carry the same data, but there are differences between them (e.g., different protocol layers; or, for example, the same protocol layer but different information carried in a certain protocol layer header). The communication device 2000 performs encapsulation or decapsulation processing on the first data packet to obtain the second data packet. In the different designs below, specific explanations can be given for different situations.

[0665] In one possible design, the processing unit 2002, when acquiring the first routing indication information and the target device identifier, is specifically used for:

[0666] Method 1: If the first data packet has a first protocol layer header, and the first protocol layer header contains the first routing indication information and the target device identifier, obtain the first routing indication information and the target device identifier from the first protocol layer header of the first data packet;

[0667] Method 2: When the communication unit 2001 receives the first data packet from the first remote terminal, the first data packet does not have a first protocol layer header; the first routing indication information is determined to be the saved routing indication information corresponding to the first remote terminal, and the target device identifier is determined to be the device identifier of the first remote terminal;

[0668] Method 3: When the communication unit 2001 receives the first data packet from the first remote terminal, the first data packet has a first protocol layer, and the first protocol layer header does not contain the first routing indication information and the target device identifier; the first routing indication information is determined to be the routing indication information corresponding to the first remote terminal that is stored, and the target device identifier is determined to be the device identifier of the first remote terminal.

[0669] In one possible design, the processing unit 2002 is further configured to:

[0670] The routing indication information corresponding to the first remote terminal is obtained from the access network device through the communication unit 2001; wherein, the routing indication information corresponding to the first remote terminal is the dedicated routing indication information of the first remote terminal or the default routing indication information.

[0671] In one possible design, the routing indication information corresponding to the first remote terminal includes multiple routing indication information items that correspond to different bearers; the processing unit 2002, when determining that the first routing indication information is the routing indication information corresponding to the first remote terminal, is specifically used for:

[0672] Determine the target bearer used to transmit the first data packet;

[0673] The first routing indication information is determined to be: the routing indication information in the routing indication information corresponding to the first remote terminal that has a corresponding relationship with the target bearer.

[0674] In one possible design, the first routing indication information includes a destination address; the first data packet has a first protocol layer header;

[0675] When the processing unit 2002 determines the first device based on the first routing indication information, or based on the first routing indication information and the target device identifier, it is specifically used for:

[0676] Method 1: When the destination address is different from the address of the first relay terminal, determine the next-hop node address corresponding to the first routing indication information; determine that the first device is the next-hop node indicated by the next-hop node address;

[0677] Method 2: When the destination address is the same as the address of the first relay terminal, the device indicated by the target device identifier is determined to be the first device;

[0678] Method 3: When the destination address is the same as the address of the first relay terminal, and the first relay terminal is the first relay terminal connected to the access network device, determine the interface used to receive the first data packet; when the interface is a Uu interface, determine that the device indicated by the target device identifier is the first device; when the interface is a PC5 interface, determine that the first device is the access network device.

[0679] In one possible design, when the first device is the next-hop node or the access network device, the second data packet is the same as the first data packet. In this design, the processing unit 2002 does not actually encapsulate or decapsulate the first data packet, but directly forwards it.

[0680] In one possible design, the first routing indication information also includes a target path identifier.

[0681] In one possible design, the first routing indication information includes a destination path identifier; the first data packet has the first protocol layer header;

[0682] When the processing unit 2002 determines the first device based on the first routing indication information, or based on the first routing indication information and the target device identifier, it is specifically used for:

[0683] Method 1: When the first routing indication information has a corresponding next-hop node device identifier, the first device is determined based on the next-hop node device identifier;

[0684] Method 2: When the first routing indication information does not have a corresponding next-hop node device identifier, the device indicated by the target device identifier is determined to be the first device.

[0685] In one possible design, when the processing unit 2002 determines the first device based on the next-hop node device identifier, it is specifically used for:

[0686] Method 1: When the next-hop node device identifier indicates that the first relay terminal is connected to the second relay terminal, the first device is determined to be the second relay terminal;

[0687] Method 2: When the next-hop node device identifier indicates an access network device, the first device is determined to be the access network device;

[0688] Method 3: When the next-hop node device identifier indicates the first relay terminal, the device indicated by the target device identifier is determined to be the first device.

[0689] In one possible design, when the next-hop node device identifier is a first default device identifier, the next-hop node device identifier indicates the first relay terminal;

[0690] When the next-hop node device identifier is the second default device identifier, the next-hop node device identifier indicates the access network device.

[0691] In one possible design, when the first device is the second relay terminal or the access network device, the second data packet is the same as the first data packet. In this design, the processing unit 2002 does not actually encapsulate or decapsulate the first data packet, but directly forwards the first data packet.

[0692] In one possible design, the first routing indication information may further include a transmission direction indication, which indicates whether the transmission is uplink or downlink.

[0693] In one possible design, when the processing unit 2002 determines that the device indicated by the target device identifier is the first device, it is specifically configured to:

[0694] When the target device identifier indicates a first remote terminal connected to the first relay terminal, the first device is determined to be the first remote terminal.

[0695] When the processing unit 2002 transmits the second data packet to the first device through the communication unit 2001, it is specifically used for:

[0696] The first data packet is decapsulated to obtain the second data packet, wherein the second data packet does not have the first protocol layer header;

[0697] The second data packet is transmitted to the first remote terminal through the communication unit 2001.

[0698] In one possible design, the first protocol layer header further includes a bearer identifier, which indicates the target bearer used to transmit the first data packet; the processing unit 2002, upon determining that the device indicated by the target device identifier is the first device, specifically performs the following:

[0699] When the target device identifier indicates a first remote terminal connected to the first relay terminal, the first device is determined to be the first remote terminal.

[0700] When the processing unit 2002 transmits the second data packet to the first device through the communication unit 2001, it is specifically used for:

[0701] Method 1: Delete the first routing indication information and the target device identifier contained in the first protocol layer of the first data packet to obtain the second data packet, wherein the first protocol layer header of the second data packet contains the bearer identifier; transmit the second data packet to the first device through the communication unit 2001;

[0702] Method 2: Decapsulate the first data packet to obtain a target data packet; wherein the target data packet does not have a first protocol layer header; add a first protocol layer header to the target data packet to generate a second data packet, wherein the first protocol layer header of the second data packet contains the bearer identifier; transmit the second data packet to the first device through the communication unit 2001;

[0703] Method 3: The second data packet, identical to the first data packet, is transmitted to the first device via the communication unit 2001. That is, the processing unit 2002 does not encapsulate or decapsulate the first data packet, but directly forwards it.

[0704] In one possible design, the processing unit 2002 is further configured to:

[0705] When the target device identifier indicates the first relay terminal, the data carried in the first data packet is determined to be the data of the first relay terminal.

[0706] In one possible design, when the target device identifier is a third default device identifier, the target device identifier indicates the first relay terminal.

[0707] In one possible design, when the first data packet does not have a first protocol layer header, the processing unit 2002, when transmitting the second data packet to the first device through the communication unit 2001, specifically performs the following:

[0708] A first protocol layer header is added to the first data packet to generate the second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the target device identifier;

[0709] The second data packet is transmitted to the first device through the communication unit 2001.

[0710] In one possible design, when the first relay terminal is connected to the access network equipment via the second relay terminal, the processing unit 2002 is further configured to:

[0711] Generate a third data packet, wherein the third data packet does not contain a first protocol layer header;

[0712] Method 1: Transmit the third data packet to the second relay terminal through the communication unit 2001;

[0713] Method 2: Determine the second routing indication information of the third data packet; add a first protocol layer header to the third data packet to generate a fourth data packet; and transmit the fourth data packet to the second relay terminal through the communication unit 2001; wherein, the first protocol layer header of the fourth data packet contains the second routing indication information and the device identifier of the first relay terminal.

[0714] In one possible design, the device identifier of the first relay terminal is assigned to the first relay terminal by the second relay terminal; or, the device identifier of the first relay terminal is assigned to the second relay terminal by the first relay terminal; or the device identifier of the first relay terminal is a first default device identifier.

[0715] In one possible design, the processing unit 2002, when transmitting the second data packet to the first device via the communication unit 2001, is specifically used for:

[0716] The second data packet is transmitted to the first device via the communication unit 2001 using the first logical channel;

[0717] When the processing unit 2002 transmits the third data packet to the second relay terminal through the communication unit 2001, it is specifically used for:

[0718] The third data packet is transmitted to the second relay terminal via the communication unit 2001 using the second logical channel.

[0719] The first logical channel is different from the second logical channel.

[0720] In one possible design, when the first data packet has a first protocol layer header, and the first protocol layer header contains a bearer identifier but does not contain the first routing indication information and the target device identifier, the processing unit 2002, when transmitting the second data packet to the first device through the communication unit 2001, is specifically used for:

[0721] The second data packet is obtained in the following two ways:

[0722] Method 1: Add the first routing indication information and the target device identifier to the first protocol layer header of the first data packet to obtain the second data packet. The first protocol layer header of the second data packet contains the bearer identifier, the first routing indication information, and the target device identifier.

[0723] Method 2: Decapsulate the first data packet to obtain the target data packet; wherein the target data packet does not have a first protocol layer header; add a first protocol layer header to the target data packet to generate the second data packet, wherein the first protocol layer header of the second data packet contains the bearer identifier, the first routing indication information and the target device identifier;

[0724] The second data packet is transmitted to the first device through the communication unit 2001.

[0725] In one possible design, the processing unit 2002, when determining the next-hop node address corresponding to the first routing indication information, is specifically used for:

[0726] From at least one saved routing information, target routing information containing the first routing indication information is determined; wherein, the target routing information contains the first routing indication information and the next-hop node address corresponding to the first routing indication information;

[0727] The next-hop node address corresponding to the first routing indication information is determined from the target routing information.

[0728] In one possible design, the processing unit 2002 is further configured to:

[0729] When a target route containing the first route indication information is determined from at least one saved route information, it is determined that the first route indication information has a corresponding next-hop node device identifier; wherein, the target route information includes the first route indication information and the next-hop node device identifier corresponding to the first route indication information;

[0730] If the target route information is not found in the at least one saved route information, it is determined that the first route indication information does not have a corresponding next-hop node device identifier.

[0731] In one possible design, the processing unit 2002 is further configured to:

[0732] The communication unit 2001 is used to obtain at least one routing information from the access network device; or, when the first relay terminal is connected to the access network device through the second relay terminal, the communication unit 2001 is used to obtain at least one routing information from the second relay terminal.

[0733] In one possible design, the target device identifier is the target device's local ID or Layer 2 ID.

[0734] In another embodiment, the processing unit 2002 is configured to:

[0735] The communication unit 2001 receives a first data packet, wherein the first data packet has a first protocol layer header, the first protocol layer header includes first routing indication information and a target device identifier, the first routing indication information is used to indicate the transmission route of the first data packet; the target device indicated by the target device identifier is the destination device or the source device of the first data packet;

[0736] Obtain the first routing indication information and the target device identifier from the first data packet;

[0737] The first device is determined based on the first routing indication information, or based on the first routing indication information and the target device identifier;

[0738] The first data packet is transmitted to the first device through the communication unit 2001.

[0739] In one possible design, the first routing indication information includes the target node address; the processing unit 2002, when determining the first device based on the first routing indication information, or based on the first routing indication information and the target device identifier, is specifically used for:

[0740] Method 1: When the target node address is different from the address of the first relay terminal, determine the next-hop node address corresponding to the first routing indication information; determine that the first device is the next-hop node indicated by the next-hop node address;

[0741] Method 2: When the target node address is the same as the address of the first relay terminal, the device indicated by the target device identifier is determined to be the first device;

[0742] Method 3: When the target node address is the same as the address of the first relay terminal, and the first relay terminal is the first relay terminal connected to the access network device, the first relay terminal determines the interface used to receive the first data packet; when the interface is a Uu interface, the device indicated by the target device identifier is determined to be the first device; when the interface is a PC5 interface, the first device is determined to be the access network device.

[0743] In one possible design, the first routing indication information also includes a target path identifier.

[0744] In one possible design, when the processing unit 2002 determines that the device indicated by the target device identifier is the first device, it is specifically configured to:

[0745] When the target device identifier indicates a first remote terminal connected to the first relay terminal, the first device is determined to be the first remote terminal.

[0746] In one possible design, the processing unit 2002 is further configured to determine that the data carried in the first data packet is the data of the first relay terminal when the target device identifier indicates the first relay terminal.

[0747] In one possible design, when the target device identifier is the default device identifier, the target device identifier indicates the first relay terminal.

[0748] In one possible design, the processing unit 2002, when determining the next-hop node address corresponding to the first routing indication information, is specifically used for:

[0749] From at least one saved routing information, target routing information containing the first routing indication information is determined; wherein, the target routing information contains the first routing indication information and the next-hop node address corresponding to the first routing indication information;

[0750] The next-hop node address corresponding to the first routing indication information is determined from the target routing information.

[0751] In one possible design, the processing unit 2002 is further configured to:

[0752] The communication unit 2001 is used to obtain at least one routing information from the access network device; or, when the first relay terminal is connected to the access network device through the second relay terminal, the communication unit 2001 is used to obtain at least one routing information from the second relay terminal.

[0753] In one possible design, the target device identifier is the target device's local ID.

[0754] In one possible design, the first protocol layer header of the first data packet also includes a bearer identifier; the bearer identifier is used to indicate the first bearer used to transmit the first data packet.

[0755] Optionally, the communication device 2000 can also be applied to an AN device. The specific functions of the processing unit 2002 are described below.

[0756] Processing unit 2002 is used for:

[0757] Obtain the first data packet, which does not have a first protocol layer header;

[0758] The first routing indication information and the first target device identifier of the first data packet are determined, wherein the first target device indicated by the first target device identifier is the destination device of the first data packet, and the first routing indication information is used to indicate the transmission route of the first data packet;

[0759] A first protocol layer header is added to the first data packet to generate a second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the first target device identifier;

[0760] The relay terminal is determined based on the first routing indication information;

[0761] The second data packet is transmitted to the relay terminal through the communication unit 2001.

[0762] In one possible design, the processing unit 2002 is further configured to:

[0763] The communication unit 2001 receives a third data packet sent by the relay terminal; wherein the third data packet has a first protocol layer header, and the first protocol layer header of the third data packet contains second routing indication information and a second target device identifier; the second target device indicated by the second target device identifier is the source device of the third data packet, and the second routing indication information is used to indicate the transmission route of the third data packet;

[0764] The third data packet is decapsulated to obtain a fourth data packet, which does not have a first protocol layer header.

[0765] In one possible design, the processing unit 2002 is further configured to:

[0766] Determine a first bearer identifier for the first data packet; wherein the first bearer identifier is used to indicate the first bearer used to transmit the first data packet;

[0767] The first protocol layer header of the second data packet also contains the first bearer identifier.

[0768] In one possible design, the first protocol layer header of the third data packet also includes a second bearer identifier, which is used to indicate the second bearer used to transmit the third data packet.

[0769] Optionally, the communication device 2000 can also be used in a remote terminal. The specific functions of the processing unit 2002 are described below.

[0770] Processing unit 2002 is used for:

[0771] Obtain the first data packet;

[0772] The first routing indication information and the target device identifier of the first data packet are determined. The first routing indication information of the first data packet is used to indicate the transmission route of the first data packet. The target device identifier is the device identifier of the remote terminal.

[0773] A first protocol layer header is added to the first data packet to generate a second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the first target device identifier;

[0774] The second data packet is sent to the relay terminal through the communication unit 2001.

[0775] In one possible design, the processing unit 2002 is further configured to:

[0776] The communication unit 2001 receives a third data packet from the relay terminal, wherein the third data packet has a first protocol layer header, and the first protocol layer header of the third data packet includes second routing indication information and the target device identifier; the second routing indication information is used to indicate the transmission route of the second data packet;

[0777] The third data packet is decapsulated to obtain a fourth data packet, which does not have a first protocol layer header.

[0778] In one possible design, the processing unit 2002 is further configured to:

[0779] Determine a first bearer identifier for the first data packet; wherein the first bearer identifier is used to indicate the first bearer used to transmit the first data packet;

[0780] The first protocol layer header of the second data packet also contains the first bearer identifier.

[0781] In one possible design, the first protocol layer header of the third data packet also includes a second bearer identifier, which is used to indicate the second bearer used to transmit the third data packet.

[0782] In one possible design, the processing unit 2002, when determining the first routing indication information of the first data packet, is specifically used for:

[0783] The first routing indication information is determined to be the routing indication information corresponding to the first remote terminal that is saved.

[0784] In one possible design, the processing unit 2002 is further configured to:

[0785] The communication unit 2001 receives routing indication information corresponding to the first remote terminal from the access network device or the relay terminal. The routing indication information corresponding to the first remote terminal is either dedicated routing indication information for the first remote terminal or default routing indication information.

[0786] It should be noted that the module division in the above embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical entities, or have two or more units integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0787] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0788] Based on the same technical concept, this application also provides a communication device, which can be applied to, for example... Figure 1 The multi-hop communication system shown can implement the routing method provided in the above embodiments, and has the following characteristics: Figure 20 The functions of the communication device 2000 shown are illustrated. (See also...) Figure 21 As shown, the communication device 2100 includes a transceiver 2101, a processor 2102, and a memory 2103. The transceiver 2101, the processor 2102, and the memory 2103 are interconnected.

[0789] Optionally, the transceiver 2101, the processor 2102, and the memory 2103 are interconnected via a bus 2104. The bus 2104 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 21 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0790] The transceiver 2101 is used to receive and send data, enabling communication and interaction with other devices.

[0791] Optionally, the communication device 2100 can be used in a relay terminal. The specific functions of the processor 2102 will be described below using the communication device 2100 applied to a first relay terminal as an example.

[0792] In one embodiment, the processor 2102 is configured to:

[0793] The first data packet is received via the transceiver 2101;

[0794] Obtain first routing indication information and target device identifier of the first data packet, wherein the first routing indication information is used to indicate the transmission route of the first data packet; the target device indicated by the target device identifier is the destination device or source device of the first data packet; determine the first device based on the first routing indication information, or based on the first routing indication information and the target device identifier;

[0795] The transceiver 2101 transmits a second data packet to the first device, wherein the data carried by the second data packet is the same as the data carried by the first data packet.

[0796] In another embodiment, the processor 2102 is configured to:

[0797] The transceiver 2101 receives a first data packet, wherein the first data packet has a first protocol layer header, the first protocol layer header includes first routing indication information and a target device identifier, the first routing indication information is used to indicate the transmission route of the first data packet; the target device indicated by the target device identifier is the destination device or the source device of the first data packet;

[0798] Obtain the first routing indication information and the target device identifier from the first data packet;

[0799] The first device is determined based on the first routing indication information, or based on the first routing indication information and the target device identifier;

[0800] The first data packet is transmitted to the first device via the transceiver 2101.

[0801] Optionally, the communication device 2100 can also be used in an AN device. The specific functions of the processor 2102 are described below.

[0802] Processor 2102, used for:

[0803] Obtain the first data packet, which does not have a first protocol layer header;

[0804] The first routing indication information and the first target device identifier of the first data packet are determined, wherein the first target device indicated by the first target device identifier is the destination device of the first data packet, and the first routing indication information is used to indicate the transmission route of the first data packet;

[0805] A first protocol layer header is added to the first data packet to generate a second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the first target device identifier;

[0806] The relay terminal is determined based on the first routing indication information;

[0807] The second data packet is transmitted to the relay terminal via the transceiver 2101.

[0808] Optionally, the communication device 2100 can also be used in a remote terminal. The specific functions of the processor 2102 are described below.

[0809] Processor 2102, used for:

[0810] Obtain the first data packet;

[0811] The first routing indication information and the target device identifier of the first data packet are determined. The first routing indication information of the first data packet is used to indicate the transmission route of the first data packet. The target device identifier is the device identifier of the remote terminal.

[0812] A first protocol layer header is added to the first data packet to generate a second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the first target device identifier;

[0813] The second data packet is sent to the relay terminal via the transceiver 2101.

[0814] It should be noted that this embodiment does not provide a detailed description of the specific functions of the processor 2102. The specific functions of the processor 2102 can be found in the descriptions of the routing methods provided in the above embodiments and examples. Figure 20 The specific functional description of the communication device 2000 in the illustrated embodiment will not be repeated here.

[0815] The memory 2103 is used to store program instructions and data. Specifically, the program instructions may include program code, which includes computer operation instructions. The memory 2103 may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. The processor 2102 executes the program instructions stored in the memory 2103 and uses the data stored in the memory 2103 to implement the above functions, thereby implementing the routing method provided in the above embodiments.

[0816] It is understood that this application Figure 21The memory 2103 can be volatile memory or non-volatile memory, or may include both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0817] Based on the above embodiments, this application also provides a computer program that, when run on a computer, causes the computer to execute the routing method provided in the above embodiments.

[0818] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, causes the computer to perform the routing method provided in the above embodiments.

[0819] The storage medium can be any available medium that a computer can access. For example, but not limited to, a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0820] Based on the above embodiments, this application also provides a chip for reading a computer program stored in a memory to implement the routing method provided in the above embodiments.

[0821] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the functions involved in the communication devices in the above embodiments. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete components.

[0822] In summary, the embodiments of this application provide a routing method and apparatus. This method can use the address of the relay UE, the address of the remote UE, the address of the AN device, or the routing identifier as routing indication information to guide the routing transmission of data packets, thereby ensuring routing between the AN device and the remote UE in multi-hop communication scenarios.

[0823] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0824] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0825] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0826] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0827] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A routing method applied in a first relay terminal, characterized in that, include: Receive the first data packet; Obtain first routing indication information and target device identifier of the first data packet, wherein the first routing indication information is used to indicate the transmission route of the first data packet; the target device indicated by the target device identifier is the destination device or the source device of the first data packet; The first device is determined based on at least one routing information of the first relay terminal, the first routing indication information, and the target device identifier, wherein any of the routing information includes a routing indication information and the next-hop node address corresponding to the routing indication information; A second data packet is transmitted to the first device, wherein the data carried by the second data packet is the same as the data carried by the first data packet.

2. The method as described in claim 1, characterized in that, Obtaining the first routing indication information and the target device identifier includes: The first data packet has a first protocol layer header, which includes the first routing indication information and the target device identifier; the first routing indication information and the target device identifier are obtained from the first protocol layer header of the first data packet; or When the first data packet is received from the first remote terminal, the first data packet does not have a first protocol layer header; the first routing indication information is determined to be the saved routing indication information corresponding to the first remote terminal, and the target device identifier is determined to be the device identifier of the first remote terminal; or When the first data packet is received from the first remote terminal, the first data packet has a first protocol layer, and the first protocol layer header does not contain the first routing indication information and the target device identifier; the first routing indication information is determined to be the saved routing indication information corresponding to the first remote terminal, and the target device identifier is determined to be the device identifier of the first remote terminal.

3. The method as described in claim 2, characterized in that, The method further includes: Obtain the routing indication information corresponding to the first remote terminal from the access network device; wherein, the routing indication information corresponding to the first remote terminal is the dedicated routing indication information of the first remote terminal or the default routing indication information.

4. The method as described in claim 2 or 3, characterized in that, The routing indication information corresponding to the first remote terminal contains multiple routing indication information that correspond to different bearers; Determining that the first routing indication information is the routing indication information corresponding to the first remote terminal includes: Determine the target bearer used to transmit the first data packet; The first routing indication information is determined to be: the routing indication information in the routing indication information corresponding to the first remote terminal that has a corresponding relationship with the target bearer.

5. The method according to any one of claims 2-4, characterized in that, The first routing indication information includes a destination address; the first data packet has a first protocol layer header; Determining the first device based on the first routing indication information and the target device identifier includes: When the destination address is the same as the address of the first relay terminal, the device indicated by the target device identifier is determined to be the first device; or When the destination address is the same as the address of the first relay terminal, and the first relay terminal is the first relay terminal connected to the access network device, the interface used to receive the first data packet is determined; when the interface is a Uu interface, the device indicated by the target device identifier is determined to be the first device; when the interface is a PC5 interface, the first device is determined to be the access network device.

6. The method as described in claim 5, characterized in that, When the first device is the access network device, the second data packet is the same as the first data packet.

7. The method as described in claim 5 or 6, characterized in that, The first routing indication information also includes a target path identifier.

8. The method according to any one of claims 2-4, characterized in that, The first routing indication information includes a destination path identifier; the first data packet has the first protocol layer header; Determining the first device based on the first routing indication information and the target device identifier includes: When the first routing indication information does not have a corresponding next-hop node device identifier, the device indicated by the target device identifier is determined to be the first device.

9. The method as described in claim 8, characterized in that, The first routing indication information also includes a transmission direction indication, which is used to indicate uplink or downlink transmission.

10. The method according to any one of claims 5-9, characterized in that, Determining that the device indicated by the target device identifier is the first device includes: When the target device identifier indicates a first remote terminal connected to the first relay terminal, the first device is determined to be the first remote terminal. Transmitting the second data packet to the first device includes: The first data packet is decapsulated to obtain the second data packet, wherein the second data packet does not have the first protocol layer header; The second data packet is transmitted to the first remote terminal.

11. The method according to any one of claims 5-9, characterized in that, The first protocol layer header further includes a bearer identifier, which indicates the target bearer used to transmit the first data packet; determining that the device indicated by the target device identifier is the first device includes: When the target device identifier indicates a first remote terminal connected to the first relay terminal, the first device is determined to be the first remote terminal. Transmitting the second data packet to the first device includes: The first routing indication information and the target device identifier contained in the first protocol layer of the first data packet are deleted to obtain the second data packet, wherein the first protocol layer header of the second data packet contains the bearer identifier; the second data packet is then transmitted to the first device; or The first data packet is decapsulated to obtain a target data packet; wherein the target data packet does not have a first protocol layer header; a first protocol layer header is added to the target data packet to generate a second data packet, wherein the first protocol layer header of the second data packet contains the bearer identifier; the second data packet is transmitted to the first device; or The second data packet, identical to the first data packet, is transmitted to the first device.

12. The method as described in claim 10 or 11, characterized in that, The method further includes: When the target device identifier indicates the first relay terminal, the data carried in the first data packet is determined to be the data of the first relay terminal.

13. The method as described in claim 12, characterized in that, When the target device identifier is the default device identifier, the target device identifier indicates the first relay terminal.

14. The method according to any one of claims 5-10, characterized in that, When the first data packet does not have a first protocol layer header, the second data packet is transmitted to the first device, including: A first protocol layer header is added to the first data packet to generate the second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the target device identifier; The second data packet is transmitted to the first device.

15. The method as described in claim 14, characterized in that, When the first relay terminal is connected to the access network device through the second relay terminal, the method further includes: Generate a third data packet, wherein the third data packet does not contain a first protocol layer header; Transmit the third data packet to the second relay terminal; or The second routing indication information of the third data packet is determined; a first protocol layer header is added to the third data packet to generate a fourth data packet; and the fourth data packet is transmitted to the second relay terminal; wherein the first protocol layer header of the fourth data packet contains the second routing indication information and the device identifier of the first relay terminal.

16. The method as described in claim 15, characterized in that, The device identifier of the first relay terminal is assigned to the first relay terminal by the second relay terminal; or, the device identifier of the first relay terminal is assigned to the second relay terminal by the first relay terminal; or the device identifier of the first relay terminal is the first default device identifier.

17. The method as described in claim 15 or 16, characterized in that, Transmitting the second data packet to the first device includes: The second data packet is transmitted to the first device using the first logical channel; Transmitting the third data packet to the second relay terminal includes: The third data packet is transmitted to the second relay terminal using the second logical channel; The first logical channel is different from the second logical channel.

18. The method according to any one of claims 5-9, or 11, characterized in that, When the first data packet has a first protocol layer header, and the first protocol layer header contains a bearer identifier but does not contain the first routing indication information and the target device identifier, the second data packet is transmitted to the first device, including: Add the first routing indication information and the target device identifier to the first protocol layer header of the first data packet to obtain the second data packet. The first protocol layer header of the second data packet contains the bearer identifier, the first routing indication information, and the target device identifier; or The first data packet is decapsulated to obtain a target data packet; wherein the target data packet does not have a first protocol layer header; a first protocol layer header is added to the target data packet to generate a second data packet, wherein the first protocol layer header of the second data packet includes the bearer identifier, the first routing indication information, and the target device identifier; or The second data packet is transmitted to the first device.

19. The method as described in claim 8 or 9, characterized in that, The method further includes: When no target routing information is found in the at least one saved routing information, it is determined that the first routing indication information does not have a corresponding next-hop node device identifier; wherein, the target routing information includes the first routing indication information and the next-hop node device identifier corresponding to the first routing indication information.

20. The method as described in claim 19, characterized in that, The method further includes: Obtain the at least one routing information from the access network device; or When the first relay terminal is connected to the access network device through the second relay terminal, the at least one routing information is obtained from the second relay terminal.

21. The method according to any one of claims 1-20, characterized in that, The target device identifier is either the local ID or the L2 ID of the target device.

22. A routing method applied in access network equipment, characterized in that, include: Obtain the first data packet, which does not have a first protocol layer header; The first routing indication information and the first target device identifier of the first data packet are determined, wherein the first target device indicated by the first target device identifier is the destination device of the first data packet, and the first routing indication information is used to indicate the transmission route of the first data packet; A first protocol layer header is added to the first data packet to generate a second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the first target device identifier; A relay terminal is determined based on at least one routing information of the access network device and the first routing indication information, wherein any of the routing information includes a routing indication information and the next-hop node address corresponding to the routing indication information; The second data packet is transmitted to the relay terminal.

23. The method as described in claim 22, characterized in that, The method further includes: The relay terminal sends a third data packet; wherein the third data packet has a first protocol layer header, and the first protocol layer header of the third data packet contains second routing indication information and a second target device identifier; the second target device indicated by the second target device identifier is the source device of the third data packet, and the second routing indication information is used to indicate the transmission route of the third data packet; The third data packet is decapsulated to obtain a fourth data packet, which does not have a first protocol layer header.

24. The method as described in claim 22, characterized in that, The method further includes: Determine a first bearer identifier for the first data packet; wherein the first bearer identifier is used to indicate the first bearer used to transmit the first data packet; The first protocol layer header of the second data packet also contains the first bearer identifier.

25. The method as described in claim 23, characterized in that, The first protocol layer header of the third data packet also includes a second bearer identifier, which is used to indicate the second bearer used to transmit the third data packet.

26. A routing method applied in a first remote terminal, characterized in that, include: Obtain the first data packet; The first routing indication information and the target device identifier of the first data packet are determined. The first routing indication information of the first data packet is used to indicate the transmission route of the first data packet. The target device identifier is the device identifier of the first remote terminal; the first routing indication information is used by the relay terminal to determine the next-hop node address; A first protocol layer header is added to the first data packet to generate a second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the target device identifier; The second data packet is sent to the relay terminal.

27. The method as described in claim 26, characterized in that, The method further includes: A third data packet is received from the relay terminal, wherein the third data packet has a first protocol layer header, and the first protocol layer header of the third data packet contains second routing indication information and the target device identifier; the second routing indication information is used to indicate the transmission route of the second data packet; The third data packet is decapsulated to obtain a fourth data packet, which does not have a first protocol layer header.

28. The method as described in claim 26, characterized in that, The method further includes: Determine a first bearer identifier for the first data packet; wherein the first bearer identifier is used to indicate the first bearer used to transmit the first data packet; The first protocol layer header of the second data packet also contains the first bearer identifier.

29. The method as described in claim 27, characterized in that, The first protocol layer header of the third data packet also includes a second bearer identifier, which is used to indicate the second bearer used to transmit the third data packet.

30. The method according to any one of claims 26-29, characterized in that, Determining the first routing indication information of the first data packet includes: The first routing indication information is determined to be the routing indication information corresponding to the first remote terminal that has been saved.

31. The method as described in claim 30, characterized in that, The method further includes: The system receives routing indication information corresponding to the first remote terminal from the access network device or the relay terminal. The routing indication information corresponding to the first remote terminal is either dedicated routing indication information for the first remote terminal or default routing indication information.

32. A routing method applied in a first relay terminal, characterized in that, include: A first data packet is received, wherein the first data packet has a first protocol layer header, the first protocol layer header includes first routing indication information and a target device identifier, the first routing indication information is used to indicate the transmission route of the first data packet; the target device indicated by the target device identifier is the destination device or the source device of the first data packet; Obtain the first routing indication information and the target device identifier from the first data packet; The first device is determined based on at least one routing information of the first relay terminal, the first routing indication information, and the target device identifier, wherein any of the routing information includes a routing indication information and the next-hop node address corresponding to the routing indication information; The first data packet is transmitted to the first device.

33. The method as described in claim 32, characterized in that, The first routing indication information includes the target node address; determining the first device based on the first routing indication information and the target device identifier includes: When the target node address is the same as the address of the first relay terminal, the device indicated by the target device identifier is determined to be the first device; or When the target node address is the same as the address of the first relay terminal, and the first relay terminal is the first relay terminal connected to the access network device, the first relay terminal determines the interface used to receive the first data packet; when the interface is a Uu interface, the device indicated by the target device identifier is determined to be the first device; when the interface is a PC5 interface, the first device is determined to be the access network device.

34. The method as described in claim 33, characterized in that, The first routing indication information also includes a target path identifier.

35. The method as described in claim 33 or 34, characterized in that, Determining that the device indicated by the target device identifier is the first device includes: When the target device identifier indicates a first remote terminal connected to the first relay terminal, the first device is determined to be the first remote terminal.

36. The method as described in claim 35, characterized in that, The method further includes: When the target device identifier indicates the first relay terminal, the data carried in the first data packet is determined to be the data of the first relay terminal.

37. The method as described in claim 36, characterized in that, When the target device identifier is the default device identifier, the target device identifier indicates the first relay terminal.

38. The method according to any one of claims 32-37, characterized in that, The target device identifier is the local identifier (local ID) of the target device.

39. The method according to any one of claims 32-38, characterized in that, The first protocol layer header of the first data packet also includes a bearer identifier; the bearer identifier is used to indicate the first bearer used to transmit the first data packet.

40. A communication device, used in a first relay terminal, characterized in that, include: The communication unit is used to receive and send data; Processing unit, used for: The first data packet is received through the communication unit; Obtain first routing indication information and target device identifier of the first data packet, wherein the first routing indication information is used to indicate the transmission route of the first data packet; the target device indicated by the target device identifier is the destination device or source device of the first data packet; determine the first device based on at least one routing information of the first relay terminal, the first routing indication information and the target device identifier, wherein any of the routing information includes a routing indication information and the next-hop node address corresponding to the routing indication information; The second data packet is transmitted to the first device through the communication unit, wherein the data carried by the second data packet is the same as the data carried by the first data packet.

41. The apparatus as claimed in claim 40, characterized in that, The processing unit, when acquiring the first routing indication information and the target device identifier, is specifically used for: If the first data packet has a first protocol layer header, and the first protocol layer header contains the first routing indication information and the target device identifier, the first routing indication information and the target device identifier are obtained from the first protocol layer header of the first data packet; or When the communication unit receives the first data packet from the first remote terminal, the first data packet does not have a first protocol layer header; the first routing indication information is determined to be the stored routing indication information corresponding to the first remote terminal, and the target device identifier is determined to be the device identifier of the first remote terminal; or When the communication unit receives the first data packet from the first remote terminal, the first data packet has a first protocol layer, and the first protocol layer header does not contain the first routing indication information and the target device identifier; the first routing indication information is determined to be the saved routing indication information corresponding to the first remote terminal, and the target device identifier is determined to be the device identifier of the first remote terminal.

42. The apparatus as claimed in claim 41, characterized in that, The processing unit is further configured to: The routing indication information corresponding to the first remote terminal is obtained from the access network device through the communication unit; wherein, the routing indication information corresponding to the first remote terminal is the dedicated routing indication information of the first remote terminal or the default routing indication information.

43. The apparatus as claimed in claim 41 or 42, characterized in that, The routing indication information corresponding to the first remote terminal includes multiple routing indication information that correspond to different bearers; the processing unit, when determining that the first routing indication information is the routing indication information corresponding to the first remote terminal, is specifically used for: Determine the target bearer used to transmit the first data packet; The first routing indication information is determined to be: the routing indication information in the routing indication information corresponding to the first remote terminal that has a corresponding relationship with the target bearer.

44. The apparatus according to any one of claims 41-43, characterized in that, The first routing indication information includes a destination address; the first data packet has a first protocol layer header; When the processing unit determines the first device based on the first routing indication information and the target device identifier, it is specifically used for: When the destination address is the same as the address of the first relay terminal, the device indicated by the target device identifier is determined to be the first device; or When the destination address is the same as the address of the first relay terminal, and the first relay terminal is the first relay terminal connected to the access network device, the interface used to receive the first data packet is determined; when the interface is a Uu interface, the device indicated by the target device identifier is determined to be the first device; when the interface is a PC5 interface, the first device is determined to be the access network device.

45. The apparatus as claimed in claim 44, characterized in that, When the first device is the access network device, the second data packet is the same as the first data packet.

46. ​​The apparatus as claimed in claim 44 or 45, characterized in that, The first routing indication information also includes a target path identifier.

47. The apparatus according to any one of claims 41-43, characterized in that, The first routing indication information includes a destination path identifier; the first data packet has the first protocol layer header; When the processing unit determines the first device based on the first routing indication information and the target device identifier, it is specifically used for: When the first routing indication information does not have a corresponding next-hop node device identifier, the device indicated by the target device identifier is determined to be the first device.

48. The apparatus as claimed in claim 47, characterized in that, The first routing indication information also includes a transmission direction indication, which is used to indicate uplink or downlink transmission.

49. The apparatus as claimed in any one of claims 44-48, characterized in that, When the processing unit determines that the device indicated by the target device identifier is the first device, it is specifically used for: When the target device identifier indicates a first remote terminal connected to the first relay terminal, the first device is determined to be the first remote terminal. When the processing unit transmits the second data packet to the first device through the communication unit, it is specifically used for: The first data packet is decapsulated to obtain the second data packet, wherein the second data packet does not have the first protocol layer header; The second data packet is transmitted to the first remote terminal through the communication unit.

50. The apparatus according to any one of claims 44-48, characterized in that, The first protocol layer header also includes a bearer identifier, which is used to indicate the target bearer used to transmit the first data packet; the processing unit, when determining that the device indicated by the target device identifier is the first device, is specifically used to: When the target device identifier indicates a first remote terminal connected to the first relay terminal, the first device is determined to be the first remote terminal. When the processing unit transmits the second data packet to the first device through the communication unit, it is specifically used for: The first routing indication information and the target device identifier contained in the first protocol layer of the first data packet are deleted to obtain the second data packet, wherein the bearer identifier is contained in the first protocol layer header of the second data packet; the second data packet is transmitted to the first device through the communication unit; or The first data packet is decapsulated to obtain a target data packet; wherein the target data packet does not have a first protocol layer header; a first protocol layer header is added to the target data packet to generate a second data packet, wherein the first protocol layer header of the second data packet contains the bearer identifier; the second data packet is transmitted to the first device through the communication unit; or The second data packet, identical to the first data packet, is transmitted to the first device through the communication unit.

51. The apparatus as claimed in claim 49 or 50, characterized in that, The processing unit is also used for: When the target device identifier indicates the first relay terminal, the data carried in the first data packet is determined to be the data of the first relay terminal.

52. The apparatus as claimed in claim 51, characterized in that, When the target device identifier is the default device identifier, the target device identifier indicates the first relay terminal.

53. The apparatus according to any one of claims 44-49, characterized in that, When the first data packet does not have a first protocol layer header, the processing unit, when transmitting the second data packet to the first device through the communication unit, specifically performs the following: A first protocol layer header is added to the first data packet to generate the second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the target device identifier; The second data packet is transmitted to the first device through the communication unit.

54. The apparatus as claimed in claim 53, characterized in that, When the first relay terminal is connected to the access network equipment through the second relay terminal, the processing unit is further configured to: Generate a third data packet, wherein the third data packet does not contain a first protocol layer header; The third data packet is transmitted to the second relay terminal via the communication unit; or The second routing indication information of the third data packet is determined; a first protocol layer header is added to the third data packet to generate a fourth data packet; and the fourth data packet is transmitted to the second relay terminal through the communication unit; wherein the first protocol layer header of the fourth data packet contains the second routing indication information and the device identifier of the first relay terminal.

55. The apparatus as claimed in claim 54, characterized in that, The device identifier of the first relay terminal is assigned to the first relay terminal by the second relay terminal; or, the device identifier of the first relay terminal is assigned to the second relay terminal by the first relay terminal; or the device identifier of the first relay terminal is the first default device identifier.

56. The apparatus as claimed in claim 54 or 55, characterized in that, When the processing unit transmits the second data packet to the first device through the communication unit, it is specifically used for: The second data packet is transmitted to the first device via the communication unit using the first logical channel; When the processing unit transmits the third data packet to the second relay terminal through the communication unit, it is specifically used for: The third data packet is transmitted to the second relay terminal via the second logical channel through the communication unit. The first logical channel is different from the second logical channel.

57. The apparatus as claimed in any one of claims 44-48, or 50, characterized in that, When the first data packet has a first protocol layer header, and the first protocol layer header contains a bearer identifier but does not contain the first routing indication information and the target device identifier, the processing unit, when transmitting the second data packet to the first device through the communication unit, specifically performs the following: Add the first routing indication information and the target device identifier to the first protocol layer header of the first data packet to obtain the second data packet. The first protocol layer header of the second data packet contains the bearer identifier, the first routing indication information, and the target device identifier; or The first data packet is decapsulated to obtain a target data packet; wherein the target data packet does not have a first protocol layer header; a first protocol layer header is added to the target data packet to generate a second data packet, wherein the first protocol layer header of the second data packet includes the bearer identifier, the first routing indication information, and the target device identifier; or The second data packet is transmitted to the first device through the communication unit.

58. The apparatus as claimed in claim 47 or 48, characterized in that, The processing unit is further configured to: When no target routing information is found in the at least one saved routing information, it is determined that the first routing indication information does not have a corresponding next-hop node device identifier; wherein, the target routing information includes the first routing indication information and the next-hop node device identifier corresponding to the first routing indication information.

59. The apparatus as claimed in claim 58, characterized in that, The processing unit is further configured to: The at least one routing information is obtained from the access network device through the communication unit; or When the first relay terminal is connected to the access network device through the second relay terminal, the at least one routing information is obtained from the second relay terminal through the communication unit.

60. The apparatus according to any one of claims 40-59, characterized in that, The target device identifier is either the local ID or the L2 ID of the target device.

61. A communication device, used in access network equipment, characterized in that, include: The communication unit is used to receive and send data; Processing unit, used for: Obtain the first data packet, which does not have a first protocol layer header; The first routing indication information and the first target device identifier of the first data packet are determined, wherein the first target device indicated by the first target device identifier is the destination device of the first data packet, and the first routing indication information is used to indicate the transmission route of the first data packet; A first protocol layer header is added to the first data packet to generate a second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the first target device identifier; A relay terminal is determined based on at least one routing information of the access network device and the first routing indication information, wherein any of the routing information includes a routing indication information and the next-hop node address corresponding to the routing indication information; The second data packet is transmitted to the relay terminal through the communication unit.

62. The apparatus as claimed in claim 61, characterized in that, The processing unit is also used for: The communication unit receives a third data packet sent by the relay terminal; wherein the third data packet has a first protocol layer header, and the first protocol layer header of the third data packet contains second routing indication information and a second target device identifier; the second target device indicated by the second target device identifier is the source device of the third data packet, and the second routing indication information is used to indicate the transmission route of the third data packet; The third data packet is decapsulated to obtain a fourth data packet, which does not have a first protocol layer header.

63. The apparatus as claimed in claim 61, characterized in that, The processing unit is further configured to: Determine a first bearer identifier for the first data packet; wherein the first bearer identifier is used to indicate the first bearer used to transmit the first data packet; The first protocol layer header of the second data packet also contains the first bearer identifier.

64. The apparatus as claimed in claim 62, characterized in that, The first protocol layer header of the third data packet also includes a second bearer identifier, which is used to indicate the second bearer used to transmit the third data packet.

65. A communication device, used in a first remote terminal, characterized in that, include: The communication unit is used to receive and send data; Processing unit, used for: Obtain the first data packet; The first routing indication information and the target device identifier of the first data packet are determined. The first routing indication information of the first data packet is used to indicate the transmission route of the first data packet. The target device identifier is the device identifier of the first remote terminal; the first routing indication information is used by the relay terminal to determine the next-hop node address; A first protocol layer header is added to the first data packet to generate a second data packet; wherein, the first protocol layer header of the second data packet contains the first routing indication information and the target device identifier; The second data packet is sent to the relay terminal through the communication unit.

66. The apparatus as claimed in claim 65, characterized in that, The processing unit is also used for: The communication unit receives a third data packet from the relay terminal, wherein the third data packet has a first protocol layer header, and the first protocol layer header of the third data packet contains second routing indication information and the target device identifier; the second routing indication information is used to indicate the transmission route of the second data packet; The third data packet is decapsulated to obtain a fourth data packet, which does not have a first protocol layer header.

67. The apparatus as claimed in claim 65, characterized in that, The processing unit is also used for: Determine a first bearer identifier for the first data packet; wherein the first bearer identifier is used to indicate the first bearer used to transmit the first data packet; The first protocol layer header of the second data packet also contains the first bearer identifier.

68. The apparatus as claimed in claim 66, characterized in that, The first protocol layer header of the third data packet also includes a second bearer identifier, which is used to indicate the second bearer used to transmit the third data packet.

69. The apparatus according to any one of claims 65-68, characterized in that, The processing unit, when determining the first routing indication information of the first data packet, is specifically used for: The first routing indication information is determined to be the routing indication information corresponding to the first remote terminal that has been saved.

70. The apparatus as claimed in claim 69, characterized in that, The processing unit is also used for: The communication unit receives routing indication information corresponding to the first remote terminal from the access network device or the relay terminal. The routing indication information corresponding to the first remote terminal is either dedicated routing indication information for the first remote terminal or default routing indication information.

71. A communication device, used in a first relay terminal, characterized in that, include: The communication unit is used to receive and send data; Processing unit, used for: The communication unit receives a first data packet, wherein the first data packet has a first protocol layer header, the first protocol layer header includes first routing indication information and a target device identifier, the first routing indication information is used to indicate the transmission route of the first data packet; the target device indicated by the target device identifier is the destination device or the source device of the first data packet; Obtain the first routing indication information and the target device identifier from the first data packet; The first device is determined based on at least one routing information of the first relay terminal, the first routing indication information, and the target device identifier, wherein any of the routing information includes a routing indication information and the next-hop node address corresponding to the routing indication information; The first data packet is transmitted to the first device through the communication unit.

72. The apparatus as claimed in claim 71, characterized in that, The first routing indication information includes the target node address; the processing unit, when determining the first device based on the first routing indication information and the target device identifier, is specifically used for: When the target node address is the same as the address of the first relay terminal, the device indicated by the target device identifier is determined to be the first device; or When the target node address is the same as the address of the first relay terminal, and the first relay terminal is the first relay terminal connected to the access network device, the first relay terminal determines the interface used to receive the first data packet; when the interface is a Uu interface, the device indicated by the target device identifier is determined to be the first device; when the interface is a PC5 interface, the first device is determined to be the access network device.

73. The apparatus as claimed in claim 72, characterized in that, The first routing indication information also includes a target path identifier.

74. The apparatus as claimed in claim 72 or 73, characterized in that, When the processing unit determines that the device indicated by the target device identifier is the first device, it is specifically used for: When the target device identifier indicates a first remote terminal connected to the first relay terminal, the first device is determined to be the first remote terminal.

75. The apparatus as claimed in claim 74, characterized in that, The processing unit is further configured to determine that the data carried in the first data packet is the data of the first relay terminal when the target device identifier indicates the first relay terminal.

76. The apparatus as claimed in claim 75, characterized in that, When the target device identifier is the default device identifier, the target device identifier indicates the first relay terminal.

77. The apparatus according to any one of claims 71-76, characterized in that, The target device identifier is the local identifier (local ID) of the target device.

78. The apparatus according to any one of claims 71-77, characterized in that, The first protocol layer header of the first data packet also includes a bearer identifier; the bearer identifier is used to indicate the first bearer used to transmit the first data packet.

79. A communication device, characterized in that, include: A transceiver is used to receive and send data; A processor for implementing the method of any one of claims 1-39 via the transceiver.

80. A communication system, characterized in that, include: A first relay terminal is configured to implement the method described in any one of claims 1-21; An access network device for implementing the method described in any one of claims 22-25.

81. The communication system as described in claim 80, characterized in that, The communication system also includes: A remote terminal for implementing the method described in any one of claims 26-31.

82. A communication system, characterized in that, include: A remote terminal for implementing the method according to any one of claims 26-31; The first relay terminal is used to implement the method described in any one of claims 32-39; An access network device for implementing the method described in any one of claims 22-25.

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

84. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method according to any one of claims 1-39.

85. A chip, characterized in that, The chip is coupled to a memory, and the chip reads a computer program stored in the memory to execute the method described in any one of claims 1-39.

Images