Methods, apparatus and computer program products for wireless communication

Abstract

A wireless communication method is disclosed. The method includes: transmitting multi-hop sidelink configuration information from a wireless communication node to two or more relay wireless communication terminals and a remote wireless communication terminal, wherein the remote wireless communication terminal communicates with the wireless communication node via two or more relay wireless communication terminals.

Description

Technical Field

[0001] This document generally deals with wireless communication, and in particular with 5G or 6G communication. Background Technology

[0002] In 5G communications, U2N (User Equipment (UE) to Network) relay is widely used. U2N relay allows the network to extend its coverage to remote UEs. A U2N relay UE is a UE that provides network connectivity for one or more U2N remote UEs. However, the application of U2N relay remains a topic for further discussion. Summary of the Invention

[0003] This document relates to methods, systems, and computer program products for wireless communication.

[0004] One aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: transmitting multi-hop sidelink configuration information from a wireless communication node to two or more relay wireless communication terminals and a remote wireless communication terminal, wherein the remote wireless communication terminal communicates with the wireless communication node via two or more relay wireless communication terminals.

[0005] Various embodiments may preferably implement the following features:

[0006] Preferably, the multi-hop side link configuration information includes at least one of the following:

[0007] The local identifier of a remote wireless communication terminal;

[0008] The parent relay identifier of the parent relay wireless communication terminal;

[0009] The local identifier of the intermediate relay wireless communication terminal;

[0010] Bearer mapping; or

[0011] The identifier of the next-hop relay wireless communication terminal.

[0012] Preferably, the bearer mapping includes at least one of the following:

[0013] Bearer mapping configuration for remote wireless communication terminals includes at least one of the following:

[0014] Radio bearer RB identifier; or

[0015] Export PC5 RLC channel identifier;

[0016] The bearer mapping configuration for intermediate relay wireless communication terminals includes at least one of the following:

[0017] RB identifier;

[0018] The egress PC5 RLC channel identifier used for uplink transmission; or

[0019] Egress PC5 RLC channel identifier for downlink transmission;

[0020] The bearer mapping configuration used for acting as an intermediate relay wireless communication terminal to a UE-to-network U2N relay wireless communication terminal includes at least one of the following:

[0021] RB identifier;

[0022] The Uu Radio Link Control (RLC) channel identifier of the intermediate relay wireless communication terminal being served;

[0023] The egress Uu RLC channel identifier used for uplink transmission; or

[0024] Egress PC5 RLC channel identifier for downlink transmission;

[0025] The bearer mapping configuration for an intermediate relay wireless communication terminal acting as a U2N remote wireless communication terminal includes at least one of the following:

[0026] Uu RLC channel identifier of intermediate relay wireless communication terminal; or

[0027] Export PC5 RLC channel identifier;

[0028] or

[0029] The bearer mapping configuration for the root relay wireless communication terminal includes at least one of the following:

[0030] RB identifier;

[0031] The Uu RLC channel identifier of the intermediate relay wireless communication terminal being served;

[0032] The egress Uu RLC channel identifier used for uplink transmission; or

[0033] Egress PC5 RLC channel identifier for downlink transmission.

[0034] Preferably, the RB identifier is an end-to-end radio bearer between the remote wireless communication terminal and the wireless communication node.

[0035] Preferably, at least one of the following applies:

[0036] The local identifier of a remote wireless communication terminal is uniquely assigned under the wireless communication node, under the root relay wireless communication terminal, or under the parent relay wireless communication terminal.

[0037] The parent relay identifier is uniquely assigned to each wireless communication node;

[0038] The local identifier of an intermediate relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal.

[0039] The identifier of the next-hop relay wireless communication terminal includes at least one of the next-hop relay wireless communication terminal's local identifier or the next-hop relay wireless communication terminal's Layer 2 (L2) identifier, wherein the next-hop relay wireless communication terminal's local identifier is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal; or

[0040] The parent relay wireless communication terminal is directly connected to the remote wireless communication terminal to provide U2N functionality to support connections from the remote wireless communication terminal to the wireless communication node.

[0041] Preferably, the wireless communication method further includes at least one of the following:

[0042] The sidelink relay adaptation protocol data unit (PDU) received by the wireless communication node from the root relay wireless communication terminal from the remote wireless communication terminal or the relay wireless communication terminal it serves; or

[0043] The wireless communication node transmits the SRAP PDU of the remote wireless communication terminal or the relay wireless communication terminal it serves to the root relay wireless communication terminal.

[0044] The SRAP header of the SRAP PDU includes at least one of the following:

[0045] The identifier of the relay wireless communication terminal being served.

[0046] Identifier of a remote wireless communication terminal

[0047] RB identifier, or

[0048] The Uu RLC channel identifier of the relay wireless communication terminal being served.

[0049] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a relay wireless communication terminal performing packet forwarding between a wireless communication node and a remote wireless communication terminal based on multi-hop sidelink configuration information received from a wireless communication node, to allow the remote wireless communication terminal and the wireless communication node to communicate via two or more relay wireless communication terminals.

[0050] Various embodiments may preferably implement the following features:

[0051] Preferably, the multi-hop side link configuration information includes at least one of the following:

[0052] The local identifier of a remote wireless communication terminal;

[0053] The parent relay identifier of the parent relay wireless communication terminal;

[0054] The local identifier of the intermediate relay wireless communication terminal;

[0055] Bearer mapping; or

[0056] The identifier of the next-hop relay wireless communication terminal.

[0057] Preferably, the bearer mapping includes at least one of the following:

[0058] The bearer mapping configuration for intermediate relay wireless communication terminals includes at least one of the following:

[0059] RB identifier;

[0060] The egress PC5 RLC channel identifier used for uplink transmission; or

[0061] Egress PC5 RLC channel identifier for downlink transmission;

[0062] The bearer mapping configuration used for acting as an intermediate relay wireless communication terminal to a UE-to-network U2N relay wireless communication terminal includes at least one of the following:

[0063] RB identifier;

[0064] The Uu Radio Link Control (RLC) channel identifier of the intermediate relay wireless communication terminal being served;

[0065] The egress Uu RLC channel identifier used for uplink transmission; or

[0066] Egress PC5 RLC channel identifier for downlink transmission;

[0067] The bearer mapping configuration for an intermediate relay wireless communication terminal acting as a U2N remote wireless communication terminal includes at least one of the following:

[0068] Uu RLC channel identifier of intermediate relay wireless communication terminal; or

[0069] Export PC5 RLC channel identifier;

[0070] or

[0071] The bearer mapping configuration for the root relay wireless communication terminal includes at least one of the following:

[0072] RB identifier;

[0073] The Uu RLC channel identifier of the intermediate relay wireless communication terminal being served;

[0074] The egress Uu RLC channel identifier used for uplink transmission; or

[0075] Egress PC5 RLC channel identifier for downlink transmission.

[0076] Preferably, at least one of the following applies:

[0077] The local identifier of a remote wireless communication terminal is uniquely assigned under the wireless communication node, under the root relay wireless communication terminal, or under the parent relay wireless communication terminal.

[0078] The parent relay identifier is uniquely assigned to each wireless communication node;

[0079] The local identifier of an intermediate relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal.

[0080] The identifier of the next-hop relay wireless communication terminal includes at least one of the next-hop relay wireless communication terminal's local identifier or the next-hop relay wireless communication terminal's Layer 2 (L2) identifier, wherein the next-hop relay wireless communication terminal's local identifier is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal; or

[0081] The parent relay wireless communication terminal is directly connected to the remote wireless communication terminal to provide U2N functionality to support connections from the remote wireless communication terminal to the wireless communication node.

[0082] Preferably, the wireless communication method further includes at least one of the following:

[0083] The relay wireless communication terminal receives the Side Link Relay Adaptation Protocol (SRAP) protocol data unit (PDU) from the remote wireless communication terminal or the intermediate relay wireless communication terminal.

[0084] By mapping the SRAP PDU to the egress PC5 RLC channel for uplink transmission based on the bearer mapping received from the wireless communication node, the SRAP protocol data unit PDU of the remote wireless communication terminal is transmitted from the relay wireless communication terminal to the intermediate relay wireless communication terminal or the root relay wireless communication terminal.

[0085] The relay wireless communication terminal receives the SRAP PDU from the root relay wireless communication terminal or the intermediate relay wireless communication terminal; or

[0086] The relay wireless communication terminal transmits the SRAPPDU of the remote wireless communication terminal to the next-hop relay wireless communication terminal, specifically by mapping the SPAPPDU to the exit PC5 RLC channel toward the next-hop relay wireless communication terminal based on the identifier of the next-hop relay wireless communication terminal configured by the wireless communication node or the uplink routing information recorded by the relay wireless communication terminal, and the bearer mapping received from the wireless communication node.

[0087] Preferably, the SRAP header of the SRAP PDU includes at least one of the following:

[0088] The identifier of the relay wireless communication terminal being served.

[0089] Identifier of a remote wireless communication terminal

[0090] The parent relay identifier of the parent relay wireless communication terminal;

[0091] RB identifier, or

[0092] The Uu RLC channel identifier of the relay wireless communication terminal being served.

[0093] Preferably, the identifier of the next-hop relay wireless communication terminal configured by the wireless communication node includes at least one of the following:

[0094] The L2 identifier of the next-hop relay wireless communication terminal; or

[0095] The local identifier of the next-hop relay wireless communication terminal, wherein, in particular, the local identifier of the next-hop relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal.

[0096] Preferably, the wireless communication method further includes at least one of the following:

[0097] The uplink routing information is recorded by the relay wireless communication terminal, wherein the uplink routing information includes information about a relay wireless communication terminal from which uplink data is received from a remote wireless communication terminal; or

[0098] Based on the uplink routing information recorded by the relay wireless communication terminal, the relay wireless communication terminal identifies the next-hop relay wireless communication terminal to which the downlink data of the remote wireless communication terminal is transmitted.

[0099] Preferably, the wireless communication method further includes at least one of the following:

[0100] A relay wireless communication terminal receives a first uplink SRAP PDU from a remote wireless communication terminal or a served intermediate relay wireless communication terminal, wherein the first uplink SRAP header of the first uplink SRAP PDU includes at least one of the following:

[0101] The local identifier of a remote wireless communication terminal;

[0102] The local identifier of the relay wireless communication terminal being served;

[0103] RB identifier; or

[0104] The Uu RLC channel identifier of the relay wireless communication terminal being served;

[0105] A second uplink SRAP PDU is constructed by a relay wireless communication terminal by adding an SRAP header to a first uplink SRAP PDU, wherein the SRAP header of the second uplink SRAP PDU includes at least one of the following:

[0106] The local identifier of the relay wireless communication terminal; or

[0107] Uu RLC channel identifier for relay wireless communication terminals;

[0108] or

[0109] The second uplink SRAP PDU is mapped to the egress PC5 RLC channel based on the bearer mapping received from the wireless communication node, and then transmitted from the relay wireless communication terminal to the intermediate relay wireless communication terminal or the root relay wireless communication terminal.

[0110] Preferably, the wireless communication method further includes at least one of the following:

[0111] The relay wireless communication terminal receives a first downlink SRAP PDU, wherein the outermost SRAP header of the first downlink SRAP PDU includes at least one of the following: the identifier of the relay wireless communication terminal being served, the identifier of the remote wireless communication terminal, the RB identifier, or the Uu RLC channel identifier of the relay wireless communication terminal being served.

[0112] The outermost SRAP header of the first downlink SRAP PDU is removed by the relay wireless communication terminal; or

[0113] The second downlink SRAP PDU is mapped to the egress PC5 RLC channel toward the served relay wireless communication terminal by a bearer mapping received from the wireless communication node, and the relay wireless communication terminal transmits the second downlink SRAP PDU to the served relay wireless communication terminal.

[0114] Preferably, the wireless communication method further includes:

[0115] The relay wireless communication terminal transmits information about one or more remote wireless communication terminals for paging monitoring to the intermediate relay wireless communication terminal or the root relay wireless communication terminal via PC5 messages.

[0116] Preferably, the wireless communication method further includes at least one of the following:

[0117] A PC5 message for paging is transmitted from a relay wireless communication terminal to an intermediate relay wireless communication terminal. The PC5 message includes information about one or more remote wireless communication terminals that are being paged.

[0118] Preferably, the information of one or more remote wireless communication terminals used for paging monitoring, or the information of one or more remote wireless communication terminals being paged, includes at least one of the following:

[0119] One or more L2 identifiers for one or more remote wireless communication terminals;

[0120] One or more local identifiers of one or more remote wireless communication terminals; or

[0121] One or more identifiers of one or more remote wireless communication terminals.

[0122] Preferably, the RB identifier is an end-to-end radio bearer between the remote wireless communication terminal and the wireless communication node.

[0123] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: communication from a remote wireless communication terminal to a wireless communication node via two or more relay wireless communication terminals by receiving a multi-hop sidelink configuration transmitted by the wireless communication node, wherein the multi-hop sidelink configuration is transmitted to the remote wireless communication terminal and the two or more relay wireless communication terminals.

[0124] Various embodiments may preferably implement the following features:

[0125] Preferably, the multi-hop side link configuration information includes at least one of the following:

[0126] The local identifier of a remote wireless communication terminal;

[0127] The parent relay identifier of the parent relay wireless communication terminal;

[0128] The local identifier of the intermediate relay wireless communication terminal;

[0129] Bearer mapping; or

[0130] The identifier of the next-hop relay wireless communication terminal.

[0131] Preferably, the bearer mapping includes at least one of the following:

[0132] Bearer mapping configuration for remote wireless communication terminals includes at least one of the following:

[0133] Radio bearer RB identifier; or

[0134] Export PC5 RLC channel identifier;

[0135] The bearer mapping configuration for intermediate relay wireless communication terminals includes at least one of the following:

[0136] RB identifier;

[0137] The egress PC5 RLC channel identifier used for uplink transmission; or

[0138] Egress PC5 RLC channel identifier for downlink transmission;

[0139] The bearer mapping configuration used for acting as an intermediate relay wireless communication terminal to a UE-to-network U2N relay wireless communication terminal includes at least one of the following:

[0140] RB identifier;

[0141] The Uu Radio Link Control (RLC) channel identifier of the intermediate relay wireless communication terminal being served;

[0142] The egress Uu RLC channel identifier used for uplink transmission; or

[0143] Egress PC5 RLC channel identifier for downlink transmission;

[0144] The bearer mapping configuration for an intermediate relay wireless communication terminal acting as a U2N remote wireless communication terminal includes at least one of the following:

[0145] Uu RLC channel identifier of intermediate relay wireless communication terminal; or

[0146] Export PC5 RLC channel identifier;

[0147] or

[0148] The bearer mapping configuration for the root relay wireless communication terminal includes at least one of the following:

[0149] RB identifier;

[0150] The Uu RLC channel identifier of the intermediate relay wireless communication terminal being served;

[0151] The egress Uu RLC channel identifier used for uplink transmission; or

[0152] Egress PC5 RLC channel identifier for downlink transmission.

[0153] Preferably, at least one of the following applies:

[0154] The local identifier of a remote wireless communication terminal is uniquely assigned under the wireless communication node, under the root relay wireless communication terminal, or under the parent relay wireless communication terminal.

[0155] The parent relay identifier is uniquely assigned to each wireless communication node;

[0156] The local identifier of an intermediate relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal.

[0157] The identifier of the next-hop relay wireless communication terminal includes at least one of the next-hop relay wireless communication terminal's local identifier or the next-hop relay wireless communication terminal's Layer 2 (L2) identifier, wherein the next-hop relay wireless communication terminal's local identifier is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal; or

[0158] The parent relay wireless communication terminal is directly connected to the remote wireless communication terminal to provide U2N functionality to support connections from the remote wireless communication terminal to the wireless communication node.

[0159] Preferably, the wireless communication method further includes at least one of the following:

[0160] By mapping SRAP PDUs to the egress PC5 RLC channel based on bearer mapping configured by the wireless communication nodes, the uplink-side SRAP protocol data units (PDUs) of the remote wireless communication terminal are transmitted from the remote wireless communication terminal to the relay wireless communication terminal; or

[0161] The remote wireless communication terminal receives the downlink SRAP PDU from the relay wireless communication terminal.

[0162] Preferably, the uplink SRAP header of the uplink SRAP PDU includes at least one of the following:

[0163] The local identifier of a remote wireless communication terminal;

[0164] RB identifier; or

[0165] The parent relay identifier of the parent relay wireless communication terminal.

[0166] Preferably, the RB identifier is an end-to-end radio bearer between the remote wireless communication terminal and the wireless communication node.

[0167] Another aspect of this disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to transmit multi-hop sidelink configuration information via the communication unit to two or more relay wireless communication terminals and a remote wireless communication terminal, wherein the remote wireless communication terminal communicates with the wireless communication node via two or more relay wireless communication terminals.

[0168] Another aspect of this disclosure relates to a relay wireless communication terminal. In one embodiment, the relay wireless communication terminal includes a communication unit and a processor. The processor is configured to perform packet forwarding between a wireless communication node and a remote wireless communication terminal via the communication unit based on multi-hop sidelink configuration information received from the wireless communication node, thereby allowing the remote wireless communication terminal and the wireless communication node to communicate via two or more relay wireless communication terminals.

[0169] Another aspect of this disclosure relates to a remote wireless communication terminal. In one embodiment, the remote wireless communication terminal includes a communication unit and a processor. The processor is configured to: perform communication to the wireless communication node via the communication unit by receiving a multi-hop sidelink configuration transmitted by the wireless communication node, via two or more relay wireless communication terminals, wherein the multi-hop sidelink configuration is transmitted to the remote wireless communication terminal and the two or more relay wireless communication terminals.

[0170] This disclosure relates to a computer program product including computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the preceding methods of wireless communication.

[0171] The exemplary embodiments disclosed herein are intended to provide features that will become apparent from the following description taken in conjunction with the accompanying drawings. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure, as will be apparent to those skilled in the art upon reading this disclosure.

[0172] Therefore, this disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps or operations in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps or operations in the disclosed methods or processes may be rearranged while remaining within the scope of this disclosure. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or operations in a sample order, and unless otherwise expressly stated, this disclosure is not limited to the specific order or hierarchy presented.

[0173] The above and other aspects and their embodiments will be described in more detail in the accompanying drawings, specification and claims. Attached Figure Description

[0174] Figure 1 A scenario of multi-hop SL relay according to an embodiment of the present disclosure is illustrated.

[0175] Figure 2 A tree topology for multi-hop SL relay is shown according to an embodiment of the present disclosure.

[0176] Figure 3 An architecture for a multi-hop SL relay according to an embodiment of the present disclosure is shown.

[0177] Figure 4 The control plane and user plane protocol stacks of two SL relays in a U2N relay according to an embodiment of the present disclosure are shown.

[0178] Figure 5A and Figure 5B The gNB configuration for a remote UE and each relay UE according to an embodiment of the present disclosure is shown.

[0179] Figure 6 A protocol stack for multi-hop SL U2N relay is shown according to an embodiment of the present disclosure.

[0180] Figure 7A and Figure 7B The gNB configuration for a remote UE and each relay UE according to an embodiment of the present disclosure is shown.

[0181] Figure 8A and Figure 8B A flowchart of an embodiment according to this disclosure is shown.

[0182] Figure 9 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown.

[0183] Figure 10 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown.

[0184] Figures 11 to 13 A flowchart of a method according to some embodiments of the present disclosure is shown. Detailed Implementation

[0185] In some embodiments, U2N relays can allow a network to extend its coverage to remote UEs via a single in-coverage relay UE. This can be limited by the relatively short range available for sidelinks (SLs). Using multi-hops can allow for range extension of U2N relays. Several new use cases can benefit from the multi-hop extension of U2N relays. For example, in factory sensor and smart metering scenarios, it allows access to Internet of Things (IoT) devices in disadvantageous deployment locations. Additionally, wearable devices can benefit from links to a companion smartphone, even when the smartphone is out of coverage and reaches the network via another UE.

[0186] Figure 1 A scenario of multi-hop SL relay according to an embodiment of this disclosure is illustrated. Relay UE1 can be a U2N relay UE that is directly connected to the gNode B (gNB) via Uu (e.g., a Uu interface) and provides U2N relay services to downstream relay UEs / remote UEs. The remote UE can be a U2N remote UE. The remote UE can establish its own one or more Protocol Data Unit (PDU) sessions / one or more Data Radio Bearers (DRBs) with the network. Data from the remote UE to the gNB can be relayed by the multi-hop relay UE.

[0187] In some embodiments, extending multi-hop U2N relays may require enhancements to discovery and relay (re)selection. Additionally, adaptation layer protocols and control plane procedures may need to be enhanced to support multi-hop. Depending on service requirements, Quality of Service (QoS) may be critical for multi-hop U2N to ensure latency requirements are met even in the presence of relay-related latency. Furthermore, enhancements may be needed to ensure robust mobility and service continuity can be maintained despite the increased hop count and to support not only the mobility of remote UEs but also the mobility of any relay UEs serving them.

[0188] Figure 2A tree topology for multi-hop SL trunking according to embodiments of this disclosure is illustrated. In some embodiments, a trunk UE may be directly connected to a gNB via a Uu. A trunk UE may be referred to as a root trunk or root U2N trunk UE (such as trunk UE1 or trunk UE4). In some embodiments, for a remote UE, its first-hop trunk UE may be its access trunk UE. For example, the access trunk (access U2N trunk) of remote UE1 may be trunk UE2, and the access trunk of remote UE2 may be trunk UE3. Trunk UEs other than the root trunk may be referred to as intermediate trunk UEs (e.g., trunk UE5 / 6 / 2 / 3). A trunk UE (e.g., trunk UE5) may be an access trunk UE of a remote UE (e.g., remote UE3) and an intermediate trunk UE of other downstream UEs.

[0189] Some aspects of this disclosure are provided in the following paragraphs, but this disclosure is not limited thereto. Furthermore, unless expressly stated otherwise, the different aspects described below may be combined. In particular, any aspect in any of the “aspects” described below (e.g., aspect 1) may be combined with any other aspect described below (e.g., aspect 2), and vice versa.

[0190] Aspect 1:

[0191] Figure 3 An architecture for a multi-hop SL relay according to embodiments of the present disclosure is illustrated. In some embodiments, the access U2N relay for a remote UE may be SL relay node 1. SL relay node 1 may also act as a U2N remote device to access SL relay node 2. SL relay node 2 may also act as a U2N remote device to access a U2N relay UE, and the U2N relay UE (which may be referred to as the root U2N relay UE) may provide access to the gNB. Both SL relay node 1 and SL relay node 2 may have U2N relay and U2N remote operation capabilities. In some embodiments, each SL relay node may act as a U2N remote UE of its upstream node (e.g., a U2N relay UE or another SL relay node) and may act as a U2N relay UE of its downstream node (e.g., a U2N remote UE or an SL relay node). SL relay node 1 and / or SL relay node 2 may be referred to as intermediate SL relay nodes.

[0192] Figure 4The control plane and user plane protocol stacks for two SL relays for U2N relays according to embodiments of this disclosure are illustrated. The Uu Radio Resource Control (RRC) / Serving Data Adaptation Protocol (SDAP) / Packet Data Convergence Protocol (PDCP) can terminate between the remote UE and the gNB, while the Side Link Relay Adaptation Protocol (SRAP) / Radio Link Control (RLC) / Media Access Control (MAC) / Physical Layer (PHY) can terminate at each hop. Both the PC5 and Uu SRAP headers can consist of a remote UE local ID and a bearer ID, which, according to one embodiment, can be identical to a single U2N relay SRAP header, where the local ID is 8 bits and the bearer ID is 5 bits.

[0193] In some embodiments, the remote UE local ID can be assigned by the gNB. The remote UE local ID can uniquely identify a remote UE under the gNB or a remote UE under a root U2N relay UE under the gNB. If the remote UE local ID uniquely identifies a remote UE under a root U2N relay UE under the gNB, then remote UEs under different root U2N relay UEs under the gNB can have the same local ID. Upon receiving a UL SRAP PDU, the gNB can jointly identify the remote UE using the local ID in the SRAP header and the root U2N relay UE from which it received the SRAP PDU.

[0194] In some embodiments, in the uplink, the Uu SRB0 of the remote UE can be transmitted to the relay UE2 (i.e., the access U2N relay of the remote UE) via a designated SL-RLC0 without an SRAP header (because the remote UE does not have its local ID). For an SRAP packet received from SL-RLC0, the relay UE2 can identify the packet as being for the remote UE's SRB0 and then add an SRAP header to the packet (e.g., by including the remote UE's local ID and bearer ID (0)) and construct an SRAPPDU. In some embodiments, the relay UE2 can map the SRAP PDU to the egress PC5 relay RLC channel based on the bearer mapping configured by the gNB for transmission to the relay UE1. The relay UE1 can identify the remote UE and the resource block (RB) of the remote UE to which the SPAP PDU belongs based on the SRAP header in the SRAP PDU. The relay UE1 can map the SRAPPDU to the egress Uu relay RLC channel based on the bearer mapping configured by the gNB.

[0195] In one embodiment, in the downlink, for the remote UE's Uu SRB0, the gNB can encapsulate the SRAP PDU with an SRAP header including the remote UE's local ID and RB ID, and send it to relay UE1 via the Uu relay RLC channel. Relay UE1 can identify the remote UE and the resource block (RB) of the remote UE to which the SPAP PDU belongs based on the SRAP header in the SRAP PDU. Relay UE1 can map the SRAP PDU to the egress PC5 relay RLC channel for transmission to relay UE2 based on routing information and bearer mapping configured by the gNB. In some embodiments, relay UE2 can identify that the SRAP PDU belongs to the remote UE's SRB0 based on the SRAP header in the SRAP PDU. Relay UE2 can remove the SRAP header and can send SRAP packets to the remote UE via SL-RLC0.

[0196] In some embodiments, after the remote UE obtains its local ID from the gNB, for DRBs and SRBs other than SRB0, the remote UE can send an SRAP PDU with an SRAP header to the relay UE via the mapped PC5 relay RLC channel based on the bearer mapping configured by the gNB. All relay UEs can directly forward the SRAP PDU to the upstream node without modifying the SRAP header. In some embodiments, in the downlink, all relay UEs can directly forward the SRAP PDU to the downstream node (including the remote UE) without modifying the SRAP header.

[0197] Figure 5A and Figure 5B The gNB configuration for a remote UE and each relay UE according to an embodiment of the present disclosure is shown.

[0198] In some embodiments, for each intermediate SL relay node (e.g., SL relay node 1 / 2), the gNB can configure a local ID and bearer mapping for each remote UE (identified by an L2 ID). The bearer mapping can include at least one of the following: RBID, UL egress PC5 RLC channel, or DL ​​egress PC5 RLC channel. For the determination of the downlink egress PC5 relay RLC channel, in addition to the bearer mapping, each relay UE can know which next-hop / downstream node the remote UE's SRAP PDU can be forwarded to next. Figure 2 As shown, when relay UE1 receives a service from remote UE1 from gNB, relay UE1 knows that the remote UE1 service can be transmitted / forwarded to relay UE2 or relay UE3. Therefore, at least two methods can be considered:

[0199] 1) The gNB can configure routing information along with bearer mappings to each relay UE. In some embodiments, access U2N relay UEs for remote UEs may not be configured. The routing information may indicate the identifier of the next-hop / downstream node for the bearer mapping of the remote UE (i.e., the egress PC5 relay RLC channel in the bearer mapping can be applied toward that node). The identifier of the next-hop node may include at least one of the following: the L2 ID of the next hop or the local ID of the next-hop node. Figure 5A and Figure 5B As shown, U2N relay UE and SL relay node 2 can be configured with routing information.

[0200] 2) Assuming each relay UE has the ability to autonomously learn and / or record routes, when receiving data packets from a remote UE (identified by the local ID in the SRAP header) from an intermediate relay node in the uplink, the relay UE can record intermediate relay node information used for routing the remote UE's data. In some embodiments, when receiving data from a remote UE in the downlink, the relay UE can identify the next-hop node based on the recorded uplink routing information of the remote UE. For example, in the uplink, SL relay node 2 can record that data from remote UE1 is relayed by SL relay node 1 and data from remote UE2 is relayed by SL relay node 1a. Then, in the downlink, SL relay node 2 can send data from remote UE1 to SL relay node 1 and simultaneously send data from remote UE2 to SL relay node 1a.

[0201] exist Figure 4 In this context, for the signaling of Relay UE2 itself, Relay UE2's SRB0 can be transmitted to Relay UE1 via the designated SL-RLC0. Relay UE1 can add an SRAP header and can send the SRAP PDU to the gNB via the UuRLC channel based on the bearer mapping configured by the gNB. The gNB can assign a local ID to Relay UE2. Relay UE2 can use the local ID for its own signaling and data transmission / reception. That is, data from remote UEs and data from Relay UE2 itself can be distinguished by different local IDs.

[0202] Aspect 2:

[0203] In some embodiments, for Figure 4The protocol stack in the code can be modified to include a new SRAP header. The SRAP header of the SRAP PDU on the PC5 and Uu interfaces can include at least one of the following: the remote UE's local ID, parent relay ID, and / or bearer ID. The remote UE's local ID can be assigned by the gNB and can be unique under the remote UE's parent / access relay node. The parent relay ID can be the ID of the remote UE's parent / access node, which can be assigned by the gNB and is unique under the gNB. The local ID and parent relay ID can be used together by the gNB to identify the remote UE.

[0204] In some embodiments, the SRAP header of the SRAP PDU may include at least one of the following: the local ID, bearer ID, and / or destination ID of the remote UE. The destination ID may be the L2 ID or local ID of the root trunk UE (assigned by the gNB). Alternatively, the destination ID may be the ID of the gNB DU or the ID of the gNB. The gNB configures the destination ID to the remote UE and each trunk UE along the (selected) trunk path.

[0205] In some embodiments, the gNB can send the parent relay ID of the remote UE's parent / access node to the remote UE. During uplink data transmission, the remote UE can construct an SRAP PDU with an SRAP header, which includes the parent relay ID (as well as the remote UE's local ID and bearer ID). In some embodiments, the gNB can send the parent relay ID of the remote UE's parent / access node to the remote UE's parent / access node.

[0206] In some embodiments, when configuring the bearer mapping from a remote UE to each relay UE (in addition to the parent / access relay node of the remote UE), the parent relay ID of the parent / access relay node of the remote UE may be included in addition to the bearer mapping and the local ID of the remote UE.

[0207] Aspect 3:

[0208] Figure 6 A protocol stack for multi-hop SL U2N relay according to embodiments of this disclosure is illustrated. Uu RRC / SDAP / PDCP can terminate at the remote UE and gNB. SRAP for the remote UE can terminate on PC5 between the remote UE and relay UE2, and on Uu between relay UE2 and gNB. SRAP for relay UE2 can terminate on PC5 between relay UE2 and relay UE1, and on Uu between relay UE1 and gNB. In some embodiments, for each remote UE and each intermediate relay node, PC5 SRAP can terminate between the remote UE / intermediate relay node and its access U2N relay UE. Uu SRAP can terminate between the access U2N relay UE and gNB.

[0209] In some embodiments, for a remote UE's SRAP PDU (including PC5 and Uu), the SRAP header (third line from top to bottom) may include the remote UE's local ID and bearer ID. For an intermediate relay node's SRAP PDU, the SRAP header (fourth line from top to bottom) may include the intermediate relay node's local ID and bearer ID / Uu RLC channel ID. The remote UE's (or intermediate relay node's) SRAP PDU may be encapsulated within the SRAP PDU of its access U2N relay UE. In some embodiments, the local ID of each remote UE / intermediate relay node may be unique under the gNB, or unique under the root U2N relay UE of the gNB, or unique under its access U2N relay UEs within the gNB.

[0210] For each intermediate relay node (e.g., Figure 6 In the relay UE2, or Figure 3 (SL relay node 1 / 2 in the gNB), it can be configured in two parts:

[0211] Part 1: Configuration of the node acting as an access U2N relay UE for the served remote node (remote UE / SL relay node): Local ID of the served remote node (identified by L2 ID), bearer mapping (bearer ID (UuSRB / DRB ID of the remote UE, or Uu RLC channel ID of the SL relay node), egress Uu RLC channel ID, egress PC5 RLC channel ID).

[0212] Part 2: Configuration of the node acting as a U2N remote UE: Node's local ID (the node is identified by L2 ID), bearer mapping (Uu RLC channel ID of the node, egress PC5 RLC channel ID).

[0213] Figure 7A and Figure 7B The gNB configuration for a remote UE and each relay UE according to an embodiment of the present disclosure is shown.

[0214] In some embodiments, the remote UE may have its local ID from the gNB. Upon receiving a PDCPPDU from an upper-layer entity, the remote UE can add an SRAP header including its local ID and bearer ID (e.g., ...). Figure 7B The SRAP header 1) is used to construct the SRAP PDU, and the SRAP PDU can be mapped to the egress PC5 relay RLC channel based on the configured bearer mapping.

[0215] In some embodiments, upon receiving an SRAP PDU in the uplink, an intermediate relay node (e.g., relay UE2) can identify the remote UE (or the served remote node / SL relay node) and bearer ID (or UuRLC channel ID) based on the SRAP header, and can determine the egress Uu relay RLC channel (identified by the Uu RLC channel ID) based on the configured partial 1 bearer mapping. The intermediate relay node can add an SRAP header (e.g., ... Figure 7B The new SRAP PDU is constructed by SRAP 2 up to SRAP header N, which includes the local ID of the intermediate relay node and the identified Uu RLC channel ID. The new SRAP PDU can be mapped to the egress PC5 relay RLC channel based on the part 2 bearer mapping of the identified Uu RLC channel ID.

[0216] In some embodiments, when an SRAP PDU is received in the uplink, the root U2N relay UE (e.g., relay UE1) can identify the last hop node (acting as a U2N remote UE) and the Uu RLC channel ID based on the outermost SRAP header, and can map the SRAP PDU to the egress Uu relay RLC channel based on the configured bearer mapping. When an SRAPPDU is received in the uplink, the gNB can remove all SRAP headers, identify the remote UE and bearer ID based on the innermost SRAP header, and can pass the SRAP SDU to the corresponding upper-layer entity.

[0217] In some embodiments, for downlink data of a remote UE, when the gNB receives a PDCP PDU from an upper-layer entity, it can add an SRAP header including the remote UE's local ID and bearer ID (e.g., ...). Figure 7B The SRAP PDU is constructed using the SRAP header 1) and the egress Uu relay RLC channel can be determined (identified by the UuRLC channel ID of the serving relay / remote UE access / parent relay). Based on the relay path, the gNB can add the SRAP header (e.g., Figure 7B The new SRAP PDU is constructed using the SRAP header 2), which includes the local ID of the remote UE's access U2N relay node (upstream node) and the identified Uu RLC channel ID, and so on (up to SRAP header N).

[0218] In some embodiments, when an SRAP PDU is received in the downlink, the root U2N relay UE can determine the appropriate information based on the outermost SRAP header (e.g., ...). Figure 7BThe SRAP header (N) identifies the served remote node (remote UE or SL relay node) and bearer ID / Uu RLC channel ID. Root U2N relay UEs can remove the outermost SRAP header and can map the SRAP PDU to the egress PC5 relay RLC channel toward the identified served remote node based on the configured bearer mapping.

[0219] In some embodiments, when an SRAP PDU is received in the downlink, the intermediate relay node can identify the served remote node (remote UE or SL relay node) and bearer ID / Uu RLC channel ID based on the outermost SRAP header. The intermediate relay node can remove the outermost SRAP header and can map the SRAPPDU to the egress PC5 relay RLC channel toward the identified served remote node based on the configured bearer mapping (part 1).

[0220] In some embodiments, when an SRAP PDU is received in the downlink, the remote UE can identify the SRB / DRB based on the bearer ID in the SRAP header and can pass the corresponding SRAP SDU (e.g., after removing the SRAP header) to the corresponding upper-layer entity.

[0221] Aspect 4:

[0222] Figure 8A and Figure 8B A flowchart of an embodiment according to this disclosure is shown.

[0223] In some embodiments, a remote UE can send information required for paging monitoring (such as 5G-S-TMSI / I-RNTI, DRB cycle) to its access / parent relay UE (e.g., relay UE1) via PC5-RRC messages. The access / parent relay UE can send information about the remote UE to the gNB via sidelink UE information through a multi-hop SL relay. The gNB can send paging messages for the remote UE to the access / parent relay UE via dedicated RRC messages. This message may include the remote UE ID (5G-S-TMSI or I-RNTI). The access / parent relay UE can also send paging messages for the remote UE to the remote UE via PC5 RRC messages.

[0224] In some embodiments, when receiving information required for paging monitoring from a connected remote UE, a relay UE (e.g., relay UE1) can also act as a remote device to send information about multiple connected remote UEs / served relay nodes to its access / parent relay UE (e.g., relay UE2) via PC5-RRC messages. In some embodiments, the information about each remote UE / served relay node may also include the L2 ID or local ID of the remote UE / served relay node. Relay UE2 can also act as a remote device to send information about multiple remote UEs to its access / parent relay UE (e.g., root U2N relay UE) via PC5-RRC messages. The root U2N relay UE can send information about multiple remote UEs to the gNB via sidelink UE information messages. In one embodiment, the root U2N relay UE can know the information required for paging monitoring of multiple downstream remote UEs. If the active DL BWP is configured with a common search space including a paging search space, it can monitor the paging timing of these remote UEs. Alternatively, the gNB can send paging of remote UEs to the root U2N relay UE via dedicated RRC messages. Paging can be sent along with the L2 ID or local ID of the remote UE.

[0225] In some embodiments, upon detecting / receiving a paging message from a remote UE, the root U2N relay UE may send the paging message to the downstream intermediate relay UE via a PC5-RRC message based on routing information (as discussed above) or stored routing records (based on uplink transmissions). In the PC5-RRC message, for each remote UE paging message (including the remote UE ID (5G Serving Temporary Mobile Subscriber Identity (S-TMSI) or Inactive Radio Network Temporary Identifier (I-RNTI))), the remote UE's L2 ID or local ID may also be included for downlink routing. In one embodiment, a single PC5-RRC message may include paging messages for multiple remote UEs (including remote UE IDs (5G-S-TMSI or I-RNTI)), all relayed through downstream intermediate relay UEs.

[0226] Figure 9Figures relate to a wireless communication terminal 30 according to embodiments of the present disclosure. The wireless communication terminal 30 may be a tag, mobile phone, laptop computer, tablet computer, e-book reader, or portable computer system, and is not limited thereto. The wireless communication terminal 30 may be used to implement the UE described in this disclosure. The wireless communication terminal 30 may include a processor 300 (such as a microprocessor or application-specific integrated circuit (ASIC)), a storage unit 310, and a communication unit 320. The storage unit 310 may be any data storage device storing program code 312 accessed and executed by the processor 300. Embodiments of the storage unit 310 include, but are not limited to, a user identity module (SIM), read-only memory (ROM), flash memory, random access memory (RAM), hard disk, and optical data storage devices. The communication unit 320 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) based on the processing results of the processor 300. In one embodiment, the communication unit 320 transmits and receives signals via at least one antenna 322 or via wiring.

[0227] In one embodiment, storage unit 310 and program code 312 may be omitted, and processor 300 may include storage unit with the stored program code.

[0228] The processor 300 can, for example, execute program code 312 to implement any of the steps or operations in the exemplary embodiments on the wireless communication terminal 30.

[0229] The communication unit 320 may be a transceiver. Alternatively or as a supplement, the communication unit 320 may combine a transmitting unit and a receiving unit, which are configured to transmit signals to and receive signals from the wireless communication node, respectively.

[0230] In some embodiments, the wireless communication terminal 30 can be used to perform the operations of a remote UE, a U2N relay UE, or a U2N remote UE as described in this disclosure. In some embodiments, the processor 300 and the communication unit 320 cooperate to perform the operations described in this disclosure. For example, the processor 300 performs operations and transmits or receives signals, messages, and / or information through the communication unit 320.

[0231] Figure 10The diagram relates to a wireless communication node 40 according to an embodiment of the present disclosure. The wireless communication node 40 may be a satellite, base station (BS), gNB, network entity, Domain Name System (DNS) server, Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), Radio Access Network (RAN), Next Generation RAN (NG-RAN), data network, core network, a communication node in the core network, or Radio Network Controller (RNC), and is not limited thereto. Additionally, the wireless communication node 40 may include (perform) at least one network function, such as Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Application Function (AF), etc. The wireless communication node 40 may be used to implement the gNB described in this disclosure. The wireless communication node 40 may include a processor 400, such as a microprocessor or ASIC, a storage unit 410, and a communication unit 420. The storage unit 410 may be any data storage device storing program code 412 accessed and executed by the processor 400. Examples of storage unit 410 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. Communication unit 420 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) based on the processing results of processor 400. In one embodiment, communication unit 420 transmits and receives signals via at least one antenna 422 or via wiring.

[0232] In one embodiment, storage unit 410 and program code 412 may be omitted. Processor 400 may include storage unit containing the stored program code.

[0233] The processor 400 may, for example, implement any of the steps or operations described in the exemplary embodiments on the wireless communication node 40 via executing program code 412.

[0234] The communication unit 420 may be a transceiver. Alternatively or as a supplement, the communication unit 420 may combine a transmitting unit and a receiving unit, which are configured to transmit signals, messages, or information to a wireless communication node or wireless communication terminal and to receive signals, messages, or information from a wireless communication node or wireless communication terminal, respectively.

[0235] In some embodiments, the wireless communication node 40 may be used to perform the operations of the gNB described in this disclosure. In some embodiments, the processor 400 and the communication unit 420 cooperate to perform the operations described in this disclosure. For example, the processor 400 performs operations and transmits or receives signals through the communication unit 420.

[0236] According to embodiments of this disclosure, a wireless communication method is also provided. In one embodiment, the wireless communication method can be performed using a wireless communication terminal (e.g., a gNB). In one embodiment, the wireless communication terminal can be implemented using the wireless communication terminal 30 described in this disclosure, but is not limited thereto.

[0237] refer to Figure 11 In one embodiment, the wireless communication method includes: transmitting multi-hop sidelink configuration information from a wireless communication node to two or more relay wireless communication terminals and a remote wireless communication terminal, wherein the remote wireless communication terminal communicates with the wireless communication node via two or more relay wireless communication terminals.

[0238] For details on this matter, please refer to the paragraphs above; they will not be repeated here.

[0239] According to embodiments of this disclosure, a wireless communication method is also provided. In one embodiment, the wireless communication method can be performed using a wireless communication node (e.g., a U2N relay UE or a U2N remote UE). In one embodiment, the wireless communication terminal can be implemented using the wireless communication terminal 30 described in this disclosure, but is not limited thereto.

[0240] refer to Figure 12 In one embodiment, the wireless communication method includes: a relay wireless communication terminal performing packet forwarding between a wireless communication node and a remote wireless communication terminal based on multi-hop sidelink configuration information received from a wireless communication node, so as to allow the remote wireless communication terminal and the wireless communication node to communicate via two or more relay wireless communication terminals.

[0241] For details on this matter, please refer to the paragraphs above; they will not be repeated here.

[0242] According to embodiments of this disclosure, another wireless communication method is also provided. In one embodiment, the wireless communication method can be performed using a wireless communication node (e.g., a remote UE). In one embodiment, the wireless communication node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0243] refer to Figure 13 In one embodiment, the wireless communication method includes: a remote wireless communication terminal performing communication to a wireless communication node via two or more relay wireless communication terminals by receiving a multi-hop sidelink configuration transmitted by the wireless communication node, wherein the multi-hop sidelink configuration is transmitted to the remote wireless communication terminal and the two or more relay wireless communication terminals.

[0244] For details on this matter, please refer to the paragraphs above; they will not be repeated here.

[0245] In some embodiments, the wireless communication terminal used in this disclosure may indicate the aforementioned remote UE, U2N relay UE, or U2N remote UE.

[0246] In some embodiments, the wireless communication node used in this disclosure may refer to the aforementioned gNB.

[0247] Although various embodiments of this disclosure have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various figures may depict exemplary architectures or configurations, which are provided to enable those skilled in the art to understand the exemplary features and functionality of this disclosure. However, those skilled in the art will understand that this disclosure is not limited to the exemplary architectures or configurations shown, but can be implemented using a variety of alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0248] It should be understood that in this disclosure, the term "and / or" or the symbol " / " can include any and all combinations of one or more of the associated listed items. For example, A and / or B and / or C includes any and all combinations of one or more of A, B, and C, including A, B, C, A and B, A and C, B and C, and combinations of A and B and C. Similarly, A / B / C includes any and all combinations of one or more of A, B, and C, including A, B, C, A and B, A and C, B and C, and combinations of A and B and C.

[0249] It should also be understood that any reference to elements in this document using names such as "first," "second," etc., generally does not restrict the number or order of these elements. Rather, these names serve as a convenient means of distinguishing two or more elements or instances of elements. Therefore, a reference to the first element and the second element does not imply that only two elements can be used, or that the first element must precede the second element in some way.

[0250] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and processes. For example, data, instructions, commands, information, signals, bits, and symbols that can be referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0251] Those skilled in the art will further understand that any of the various illustrative logic blocks, units, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software unit"), or any combination of these technologies.

[0252] To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, circuits, operations, and steps have been generally described above in terms of their functionality. Whether such functionality is implemented in hardware, firmware, software, or a combination of these technologies depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions do not depart from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., may be configured to perform one or more of the functions described herein. The terms “configured to” or “configured for” as used herein with respect to a specified operation or function refer to processors, devices, components, circuits, structures, machines, units, etc., that are physically constructed, programmed, and / or arranged to perform a particular operation or function.

[0253] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, units, devices, components, and circuits described herein can be implemented within or executed by integrated circuits (ICs), which may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof. Logic blocks, units, and circuits may also include antennas and / or transceivers for communication with various components within a network or device. A general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps or operations of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium.

[0254] Computer-readable media include both computer storage media and communication media, wherein the communication media includes any medium that enables a computer program or code to be transferred from one place to another. The storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and that can be accessed by a computer.

[0255] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the relevant functions described herein. Furthermore, for ease of discussion, various units are described as discrete units; however, it will be apparent to those skilled in the art that, according to embodiments of this disclosure, two or more units may be combined to form a single unit performing the relevant functions.

[0256] Additionally, memory or other memory and communication components may be employed in the embodiments of this disclosure. It should be understood that, for clarity, the above description has referenced various functional units and processors in the embodiments of this disclosure. However, it will be apparent that any suitable functional distribution may be used among different functional units, processing logic elements, or domains without departing from this disclosure. For example, functions illustrated to be performed by different processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functions and not indications of a strict logical or physical structure or organization.

[0257] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of the claims. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be endowed with the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the claims.

Claims

1. A wireless communication method, the wireless communication method comprising: The wireless communication node transmits multi-hop sidelink configuration information to two or more relay wireless communication terminals and remote wireless communication terminals, wherein the remote wireless communication terminals communicate with the wireless communication node via the two or more relay wireless communication terminals.

2. The wireless communication method according to claim 1, wherein, The multi-hop side link configuration information includes at least one of the following: The local identifier of the remote wireless communication terminal; The parent relay identifier of the parent relay wireless communication terminal; The local identifier of the intermediate relay wireless communication terminal; Bearer mapping; or The identifier of the next-hop relay wireless communication terminal.

3. The wireless communication method according to claim 2, wherein, The bearer mapping includes at least one of the following: The bearer mapping configuration for the remote wireless communication terminal includes at least one of the following: Radio bearer RB identifier; or Export PC5 RLC channel identifier; The bearer mapping configuration for intermediate relay wireless communication terminals includes at least one of the following: RB identifier; The egress PC5 RLC channel identifier used for uplink transmission; or Egress PC5 RLC channel identifier for downlink transmission; The bearer mapping configuration used for acting as an intermediate relay wireless communication terminal to a UE-to-network U2N relay wireless communication terminal includes at least one of the following: RB identifier; The Uu Radio Link Control (RLC) channel identifier of the intermediate relay wireless communication terminal being served; The egress Uu RLC channel identifier used for uplink transmission; or Egress PC5 RLC channel identifier for downlink transmission; The bearer mapping configuration for an intermediate relay wireless communication terminal acting as a U2N remote wireless communication terminal includes at least one of the following: The Uu RLC channel identifier of the intermediate relay wireless communication terminal; or Export PC5 RLC channel identifier; or The bearer mapping configuration for the root relay wireless communication terminal includes at least one of the following: RB identifier; The Uu RLC channel identifier of the intermediate relay wireless communication terminal being served; The egress Uu RLC channel identifier used for uplink transmission; or Egress PC5 RLC channel identifier for downlink transmission.

4. The wireless communication method according to claim 3, wherein, The RB identifier is an end-to-end radio bearer between the remote wireless communication terminal and the wireless communication node.

5. The wireless communication method according to any one of claims 2 to 4, wherein, At least one of the following applies: The local identifier of the remote wireless communication terminal is uniquely assigned under the wireless communication node, under the root relay wireless communication terminal, or under the parent relay wireless communication terminal. The parent relay identifier is uniquely assigned under the wireless communication node; The local identifier of the intermediate relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal. The identifier of the next-hop relay wireless communication terminal includes at least one of the local identifier of the next-hop relay wireless communication terminal or the Layer 2 (L2) identifier of the next-hop relay wireless communication terminal, wherein the local identifier of the next-hop relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal; or The parent relay wireless communication terminal is directly connected to the remote wireless communication terminal to provide U2N functionality to support the connection from the remote wireless communication terminal to the wireless communication node.

6. The wireless communication method according to any one of claims 1 to 5, further comprising at least one of the following: The wireless communication node receives the Sidelink Relay Adaptation Protocol (SRAP) Protocol Data Unit (PDU) from the root relay wireless communication terminal; or The wireless communication node transmits the SRAP PDU of the remote wireless communication terminal or the relay wireless communication terminal it serves to the root relay wireless communication terminal; in, The SRAP header of the SRAP PDU includes at least one of the following: The identifier of the relay wireless communication terminal being served. The identifier of the remote wireless communication terminal, RB identifier, or The Uu RLC channel identifier of the relay wireless communication terminal being served.

7. A wireless communication method, the wireless communication method comprising: The relay wireless communication terminal performs packet forwarding between the wireless communication node and the remote wireless communication terminal based on multi-hop sidelink configuration information received from the wireless communication node, so as to allow the remote wireless communication terminal and the wireless communication node to communicate via two or more relay wireless communication terminals.

8. The wireless communication method according to claim 7, wherein, The multi-hop side link configuration information includes at least one of the following: The local identifier of the remote wireless communication terminal; The parent relay identifier of the parent relay wireless communication terminal; The local identifier of the intermediate relay wireless communication terminal; Bearer mapping; or The identifier of the next-hop relay wireless communication terminal.

9. The wireless communication method according to claim 8, wherein, The bearer mapping includes at least one of the following: The bearer mapping configuration for intermediate relay wireless communication terminals includes at least one of the following: RB identifier; The egress PC5 RLC channel identifier used for uplink transmission; or Egress PC5 RLC channel identifier for downlink transmission; The bearer mapping configuration used for acting as an intermediate relay wireless communication terminal to a UE-to-network U2N relay wireless communication terminal includes at least one of the following: RB identifier; The Uu Radio Link Control (RLC) channel identifier of the intermediate relay wireless communication terminal being served; The egress Uu RLC channel identifier used for uplink transmission; or Egress PC5 RLC channel identifier for downlink transmission; The bearer mapping configuration for an intermediate relay wireless communication terminal acting as a U2N remote wireless communication terminal includes at least one of the following: The Uu RLC channel identifier of the intermediate relay wireless communication terminal; or Export PC5 RLC channel identifier; or The bearer mapping configuration for the root relay wireless communication terminal includes at least one of the following: RB identifier; The Uu RLC channel identifier of the intermediate relay wireless communication terminal being served; The egress Uu RLC channel identifier used for uplink transmission; or Egress PC5 RLC channel identifier for downlink transmission.

10. The wireless communication method according to claim 8 or 9, wherein, At least one of the following applies: The local identifier of the remote wireless communication terminal is uniquely assigned under the wireless communication node, under the root relay wireless communication terminal, or under the parent relay wireless communication terminal. The parent relay identifier is uniquely assigned under the wireless communication node; The local identifier of the intermediate relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal. The identifier of the next-hop relay wireless communication terminal includes at least one of the local identifier of the next-hop relay wireless communication terminal or the Layer 2 (L2) identifier of the next-hop relay wireless communication terminal, wherein the local identifier of the next-hop relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal; or The parent relay wireless communication terminal is directly connected to the remote wireless communication terminal to provide U2N functionality to support the connection from the remote wireless communication terminal to the wireless communication node.

11. The wireless communication method according to any one of claims 7 to 10, further comprising at least one of the following: The relay wireless communication terminal receives the Side Link Relay Adaptation Protocol (SRAP) Protocol Data Unit (PDU) from the remote wireless communication terminal or the intermediate relay wireless communication terminal. By mapping the SRAP PDU to the egress PC5 RLC channel for uplink transmission based on the bearer mapping received from the wireless communication node, the relay wireless communication terminal transmits the Side Link Relay Adaptation Protocol (SRAP) protocol data unit (PDU) of the remote wireless communication terminal to the intermediate relay wireless communication terminal or the root relay wireless communication terminal. The relay wireless communication terminal receives the SRAP PDU of the remote wireless communication terminal from the root relay wireless communication terminal or the intermediate relay wireless communication terminal; or The relay wireless communication terminal transmits the SRAP PDU of the remote wireless communication terminal to the next-hop relay wireless communication terminal, specifically by mapping the SPAP PDU to the egress PC5 RLC channel toward the next-hop relay wireless communication terminal based on the identifier of the next-hop relay wireless communication terminal configured by the wireless communication node or the uplink routing information recorded by the relay wireless communication terminal, and the bearer mapping received from the wireless communication node.

12. The wireless communication method according to claim 11, wherein, The SRAP header of the SRAP PDU includes at least one of the following: The identifier of the relay wireless communication terminal being served. The identifier of the remote wireless communication terminal, The parent relay identifier of the parent relay wireless communication terminal; RB identifier, or The Uu RLC channel identifier of the relay wireless communication terminal being served.

13. The wireless communication method according to claim 8 or 11, wherein, The identifier of the next-hop relay wireless communication terminal configured by the wireless communication node includes at least one of the following: The L2 identifier of the next-hop relay wireless communication terminal; or The local identifier of the next-hop relay wireless communication terminal, wherein the local identifier of the next-hop relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal.

14. The wireless communication method according to claim 11 or 12, further comprising at least one of the following: The uplink routing information is recorded by the relay wireless communication terminal, wherein, The uplink routing information includes information about a relay wireless communication terminal from which uplink data is received from the remote wireless communication terminal; or The relay wireless communication terminal identifies the next-hop relay wireless communication terminal to which the downlink data of the remote wireless communication terminal is transmitted, based on the uplink routing information recorded by the relay wireless communication terminal.

15. The wireless communication method according to any one of claims 7 to 14, further comprising at least one of the following: The relay wireless communication terminal receives a first uplink SRAP PDU from the remote wireless communication terminal or the intermediate relay wireless communication terminal it serves, wherein, The first uplink SRAP header of the first uplink SRAP PDU includes at least one of the following: The local identifier of the remote wireless communication terminal; The local identifier of the relay wireless communication terminal being served; RB identifier; or The Uu RLC channel identifier of the relay wireless communication terminal being served; The relay wireless communication terminal constructs a second uplink SRAP PDU by adding an SRAP header to the first uplink SRAP PDU, wherein the SRAP header of the second uplink SRAP PDU includes at least one of the following: The local identifier of the relay wireless communication terminal; or The Uu RLC channel identifier of the relay wireless communication terminal; or The second uplink SRAP PDU is mapped to the egress PC5 RLC channel based on the bearer mapping received from the wireless communication node, and then transmitted by the relay wireless communication terminal to the intermediate relay wireless communication terminal or the root relay wireless communication terminal.

16. The wireless communication method according to any one of claims 7 to 15, further comprising at least one of the following: The relay wireless communication terminal receives the first downlink SRAP PDU, wherein, The outermost SRAP header of the first downlink SRAPPDU includes at least one of the following: the identifier of the relay wireless communication terminal being served, the identifier of the remote wireless communication terminal, the RB identifier, or the Uu RLC channel identifier of the relay wireless communication terminal being served. The outermost SRAP header of the first downlink SRAP PDU is removed by the relay wireless communication terminal; or The second downlink SRAP PDU is mapped to the egress PC5 RLC channel toward the served relay wireless communication terminal by means of the bearer mapping received from the wireless communication node, and the second downlink SRAP PDU is transmitted from the relay wireless communication terminal to the served relay wireless communication terminal.

17. The wireless communication method according to any one of claims 7 to 16, further comprising: The relay wireless communication terminal transmits information about one or more remote wireless communication terminals for paging monitoring to the intermediate relay wireless communication terminal or the root relay wireless communication terminal via PC5 messages.

18. The wireless communication method according to any one of claims 7 to 17, further comprising at least one of the following: The relay wireless communication terminal transmits a PC5 message for paging to the intermediate relay wireless communication terminal, wherein... The PC5 message includes information about one or more remote wireless communication terminals that are being paged.

19. The wireless communication method according to claim 17 or 18, wherein, Information about one or more remote wireless communication terminals used for paging monitoring, or information about one or more remote wireless communication terminals being paged, includes at least one of the following: One or more L2 identifiers of the one or more remote wireless communication terminals; One or more local identifiers of the one or more remote wireless communication terminals; or One or more identifiers of the one or more remote wireless communication terminals.

20. The wireless communication method according to claim 9, 15, or 16, wherein, The RB identifier is an end-to-end radio bearer between the remote wireless communication terminal and the wireless communication node.

21. A wireless communication method, the wireless communication method comprising: By receiving a multi-hop sidelink configuration transmitted by a wireless communication node, a remote wireless communication terminal performs communication to the wireless communication node via two or more relay wireless communication terminals, wherein the multi-hop sidelink configuration is transmitted to the remote wireless communication terminal and the two or more relay wireless communication terminals.

22. The wireless communication method according to claim 21, wherein, The multi-hop side link configuration information includes at least one of the following: The local identifier of the remote wireless communication terminal; The parent relay identifier of the parent relay wireless communication terminal; The local identifier of the intermediate relay wireless communication terminal; Bearer mapping; or The identifier of the next-hop relay wireless communication terminal.

23. The wireless communication method according to claim 22, wherein, The bearer mapping includes at least one of the following: The bearer mapping configuration for the remote wireless communication terminal includes at least one of the following: Radio bearer RB identifier; or Export PC5 RLC channel identifier; The bearer mapping configuration for intermediate relay wireless communication terminals includes at least one of the following: RB identifier; The egress PC5 RLC channel identifier used for uplink transmission; or Egress PC5 RLC channel identifier for downlink transmission; The bearer mapping configuration used for acting as an intermediate relay wireless communication terminal to a UE-to-network U2N relay wireless communication terminal includes at least one of the following: RB identifier; The Uu Radio Link Control (RLC) channel identifier of the intermediate relay wireless communication terminal being served; The egress Uu RLC channel identifier used for uplink transmission; or Egress PC5 RLC channel identifier for downlink transmission; The bearer mapping configuration for an intermediate relay wireless communication terminal acting as a U2N remote wireless communication terminal includes at least one of the following: The Uu RLC channel identifier of the intermediate relay wireless communication terminal; or Export PC5 RLC channel identifier; or The bearer mapping configuration for the root relay wireless communication terminal includes at least one of the following: RB identifier; The Uu RLC channel identifier of the intermediate relay wireless communication terminal being served; The egress Uu RLC channel identifier used for uplink transmission; or Egress PC5 RLC channel identifier for downlink transmission.

24. The wireless communication method according to claim 22 or 23, wherein, At least one of the following applies: The local identifier of the remote wireless communication terminal is uniquely assigned under the wireless communication node, under the root relay wireless communication terminal, or under the parent relay wireless communication terminal. The parent relay identifier is uniquely assigned under the wireless communication node; The local identifier of the intermediate relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal. The identifier of the next-hop relay wireless communication terminal includes at least one of the local identifier of the next-hop relay wireless communication terminal or the Layer 2 (L2) identifier of the next-hop relay wireless communication terminal, wherein the local identifier of the next-hop relay wireless communication terminal is uniquely assigned under the wireless communication node or under the root relay wireless communication terminal; or The parent relay wireless communication terminal is directly connected to the remote wireless communication terminal to provide U2N functionality to support the connection from the remote wireless communication terminal to the wireless communication node.

25. The wireless communication method according to any one of claims 21 to 24, further comprising at least one of the following: By mapping the SRAP PDU to the egress PC5 RLC channel based on the bearer mapping configured by the wireless communication node, the remote wireless communication terminal transmits the uplink-side Link Relay Adaptation Protocol (SRAP) data unit (PDU) of the remote wireless communication terminal to the relay wireless communication terminal; or The remote wireless communication terminal receives the downlink SRAP PDU from the relay wireless communication terminal.

26. The wireless communication method according to claim 25, wherein, The uplink SRAP header of the uplink SRAP PDU includes at least one of the following: The local identifier of the remote wireless communication terminal; RB identifier; or The parent relay identifier of the parent relay wireless communication terminal.

27. The wireless communication method according to claim 23 or 26, wherein, The RB identifier is an end-to-end radio bearer between the remote wireless communication terminal and the wireless communication node.

28. A wireless communication node, the wireless communication node comprising: Communication unit; and Processor, the processor being configured to: The communication unit transmits multi-hop sidelink configuration information to two or more relay wireless communication terminals and remote wireless communication terminals, wherein the remote wireless communication terminals communicate with the wireless communication node via the two or more relay wireless communication terminals.

29. The wireless communication node according to claim 28, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 2 to 6.

30. A relay wireless communication terminal, the relay wireless communication terminal comprising: Communication unit; and Processor, the processor being configured to: Based on multi-hop sidelink configuration information received from the wireless communication node, the communication unit performs packet forwarding between the wireless communication node and the remote wireless communication terminal to allow the remote wireless communication terminal and the wireless communication node to communicate via two or more relay wireless communication terminals.

31. The wireless communication node according to claim 30, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 8 to 20.

32. A remote wireless communication terminal, the remote wireless communication terminal comprising: Communication unit; and Processor, the processor being configured to: The communication unit receives a multi-hop sidelink configuration transmitted by the wireless communication node and performs communication to the wireless communication node via two or more relay wireless communication terminals, wherein the multi-hop sidelink configuration is transmitted to the remote wireless communication terminal and the two or more relay wireless communication terminals.

33. The wireless communication node according to claim 32, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 22 to 27.

34. A computer program product comprising computer-readable program medium code stored thereon, the code, when executed by a processor, causing the processor to implement the wireless communication method according to any one of claims 1 to 27.

Images