Relay adaptation protocol layer configuration

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a relay user equipment can establish a sidelink unicast link with a remote UE via a sidelink signaling interface; receive configuration information from a network entity, the configuration information including at least one of: remote UE link identifier information associated with the sidelink unicast link for a relay service, an RLC channel mapping between the sidelink unicast link and one or more RLC channels of a link with the network entity, or data routing information associated with the relay service; configure the one or more RLC channels for the sidelink unicast link and the link with the network entity based at least in part on the configuration information; and relay communications between the remote UE and the network entity based at least in part on the configuration information. Numerous other aspects are provided.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 023,212, filed May 11, 2020, entitled “Relay Adaptor Protocol Layer Configuration”, and U.S. Non-Provisional Patent Application No. 17 / 302,677, filed May 10, 2021, entitled “Relay Adaptor Protocol Layer Configuration”, which are hereby expressly incorporated by reference. Technical Field

[0003] Various aspects of this disclosure generally relate to wireless communications and techniques and apparatus for configuring Relay Adaptation Protocol (RAP) layers. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard released by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include multiple base stations (BSs) capable of supporting communication for many user equipments (UEs). UEs can communicate with the BS via downlinks and uplinks. A "downlink" (or "forward link") refers to the communication link from the BS to the UE, and an "uplink" (or "backlink") refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Head, Transmit / Receive Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0006] Various telecommunications standards have adopted the aforementioned multiple access technologies to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global levels. NR, also known as 5G, is a set of enhancements to the LTE mobile standard released by 3GPP. NR is designed to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards. These open standards use Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM)) on the uplink (UL), and support beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation. With the continued growth in demand for mobile broadband access, further improvements to LTE, NR, and other radio access technologies remain highly valuable. Summary of the Invention

[0007] In some aspects, a method of wireless communication performed by a relay user equipment (UE) includes: establishing a connection with a remote UE for relay communication; receiving configuration information from a network entity, the configuration information including at least one of: remote UE connection identifier information associated with a connection between the remote UE and the relay UE for relay service, including configuration of relay channel identifier information, wherein the configuration is for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity; configuring one or more relay channels of the connection and one or more relay channels of the link with the network entity based at least in part on the configuration information; and relaying communication between the remote UE and the network entity based at least in part on the configuration information.

[0008] In some aspects, a method of wireless communication performed by a network entity includes sending configuration information to a relay user equipment (UE), the configuration information including at least one of the following: remote UE connection identifier information associated with a connection between the remote UE and the relay UE for relay services; configuration including relay channel identifier information, wherein the configuration is for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity; and communicating with the remote UE via the relay UE based at least in part on the configuration information.

[0009] In some aspects, a method of wireless communication performed by a remote user equipment (UE) includes: establishing a connection with a relay UE; configuring one or more relay channels for the connection based at least in part on configuration information, wherein the configuration information includes at least one of: remote UE connection identifier information associated with the connection between the remote UE and the relay UE for relay service, or configuration of one or more relay channels for the connection between the remote UE and the relay UE; and communicating with a network entity via the relay UE based at least in part on the configuration information.

[0010] In some aspects, an apparatus for wireless communication at a relay user equipment (UE) includes: a memory; and one or more processors coupled to the memory, the processors being configured to: establish a connection with a remote UE for relay communication; receive configuration information from a network entity, the configuration information including at least one of: remote UE connection identifier information associated with a connection between the remote UE and the relay UE for relay service, including configuration of relay channel identifier information, wherein the configuration is for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity; configure one or more relay channels of the connection and one or more relay channels of the link with the network entity based at least in part on the configuration information; and relay communication between the remote UE and the network entity based at least in part on the configuration information.

[0011] In some aspects, an apparatus for wireless communication at a network entity includes: a memory; and one or more processors coupled to the memory, configured to: send configuration information to a relay user equipment (UE), the configuration information including at least one of: remote UE connection identifier information associated with a connection between the remote UE and the relay UE for relay service; configuration including relay channel identifier information, wherein the configuration is for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity; and communicate with the remote UE via the relay UE at least in part based on the configuration information.

[0012] In some aspects, an apparatus for wireless communication at a remote user equipment (UE) includes: a memory; and one or more processors coupled to the memory, the processors being configured to: establish a connection with a relay UE; configure one or more relay channels for the connection based at least in part on configuration information, wherein the configuration information includes at least one of: remote UE connection identifier information associated with the connection between the remote UE and the relay UE for relay service, or configuration of one or more relay channels for the connection between the remote UE and the relay UE; and communicate with a network entity via the relay UE based at least in part on the configuration information.

[0013] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a relay user equipment (UE), cause the UE to: establish a connection with a remote UE for relay communication; receive configuration information from a network entity, the configuration information including at least one of: remote UE connection identifier information associated with the connection between the remote UE and the relay UE for relay service, including configuration of relay channel identifier information, wherein the configuration is for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity; configure one or more relay channels of the connection and one or more relay channels of the link with the network entity, at least in part based on the configuration information; and relay communication between the remote UE and the network entity, at least in part based on the configuration information.

[0014] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network entity, cause the network entity to: send configuration information to a relay user equipment (UE), the configuration information including at least one of: remote UE connection identifier information associated with a connection between the remote UE and the relay UE for relay service; configuration including relay channel identifier information, wherein the configuration is for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity; and communicate with the remote UE via the relay UE at least in part based on the configuration information.

[0015] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a remote user equipment (UE), cause the UE to: establish a connection with a relay UE; configure one or more relay channels for the connection, at least in part based on configuration information, wherein the configuration information includes at least one of: remote UE connection identifier information associated with the connection between the remote UE and the relay UE for relay service, or configuration of one or more relay channels for the connection between the remote UE and the relay UE; and communicate with a network entity via the relay UE, at least in part based on the configuration information.

[0016] In some aspects, an apparatus for wireless communication includes: a module for establishing a connection with a remote user equipment (UE) for relay communication; a module for receiving configuration information from a network entity, the configuration information including at least one of: remote UE connection identifier information associated with a connection between a remote UE and an apparatus for relay service, including configuration of relay channel identifier information, wherein the connection between the remote UE and the apparatus and the link with the network entity are configured, wherein a relay channel mapping indicating one or more relay channels of the connection and one or more relay channels of the link with the network entity is configured; a module for configuring one or more relay channels of the connection and one or more relay channels of the link with the network entity, at least in part, based on the configuration information; and a module for relaying communication between the remote UE and the network entity, at least in part, based on the configuration information.

[0017] In some aspects, an apparatus for wireless communication includes a module for sending configuration information to a relay user equipment (UE), the configuration information including at least one of the following: remote UE connection identifier information associated with a connection between the remote UE and the relay UE for relay services; configuration including relay channel identifier information, wherein the connection between the remote UE and the relay UE and the link with the apparatus are configured, wherein a relay channel mapping indicating one or more relay channels of the connection and one or more relay channels of the link with the apparatus is configured; and a module for communicating with the remote UE via the relay UE based at least in part on the configuration information.

[0018] In some aspects, an apparatus for wireless communication includes: a module for establishing a connection with a relay user equipment (UE); a module for configuring one or more relay channels for the connection, at least in part based on configuration information, wherein the configuration information includes at least one of: remote UE connection identifier information associated with the connection between the apparatus for relay service and the relay UE, or the configuration of one or more relay channels for the connection between the apparatus and the relay UE; and a module for communicating with a network entity via the relay UE, at least in part based on the configuration information.

[0019] In some aspects, a wireless communication method performed by a relay user equipment (UE) may include: establishing a sidelink unicast link with a remote UE via a sidelink signaling interface; receiving configuration information from a network entity, the configuration information including at least one of the following: remote UE link identifier information associated with the sidelink unicast link between the remote UE and the relay UE for relay services, an RLC channel mapping between the sidelink unicast link and one or more RLC channels of the link with the network entity, or data routing information associated with the relay services; configuring one or more RLC channels for the sidelink unicast link and the link with the network entity, at least in part based on the configuration information; and relaying communication between the remote UE and the network entity, at least in part based on the configuration information.

[0020] In some aspects, a method of wireless communication performed by a network entity may include sending configuration information to a relay user equipment (UE), the configuration information including at least one of the following: remote UE link identifier information associated with a sidelink unicast link between a remote UE and a relay UE for relay services, an RLC channel mapping between the sidelink unicast link and one or more RLC channels of the link with the network entity, or data routing information associated with relay services; and communicating with a remote UE via the relay UE at least in part based on the configuration information.

[0021] In some aspects, a wireless communication method performed by a remote user equipment may include: establishing a sidelink unicast link with a relay UE via a sidelink signaling interface; configuring one or more radio link control (RLC) channels of the sidelink unicast link based at least in part on configuration information, wherein the configuration information includes at least one of the following: remote UE link identifier information associated with the sidelink unicast link between the remote UE and the relay UE for relay service, or communicating with a network entity via the relay UE based at least in part on the configuration information.

[0022] In some aspects, a relay user equipment for wireless communication may include a memory and one or more processors coupled to the memory. The memory and one or more processors may be configured to establish a sidelink unicast link with a remote UE via a sidelink signaling interface; receive configuration information from a network entity, the configuration information including at least one of the following: remote UE link identifier information associated with the sidelink unicast link between the remote UE and the relay UE for relay service; RLC channel mapping between the sidelink unicast link and one or more RLC channels of the link with the network entity; or data routing information associated with the relay service; configure one or more RLC channels for the sidelink unicast link and the link with the network entity, at least in part based on the configuration information; and relay communication between the remote UE and the network entity, at least in part based on the configuration information.

[0023] In some aspects, a network entity for wireless communication may include a memory and one or more processors coupled to the memory. The memory and one or more processors may be configured to send configuration information to a relay user equipment (UE), the configuration information including at least one of the following: remote UE link identifier information associated with a sidelink unicast link between a remote UE and a relay UE for relay services; an RLC channel mapping between the sidelink unicast link and one or more RLC channels of the link with the network entity; or data routing information associated with relay services; and communication between the relay UE and the remote UE, at least in part, based on the configuration information.

[0024] In some aspects, a remote user equipment for wireless communication may include a memory and one or more processors coupled to the memory. The memory and one or more processors may be configured to establish a sidelink unicast link with a relay UE via a sidelink signaling interface; configure one or more radio link control (RLC) channels of the sidelink unicast link at least in part based on configuration information, wherein the configuration information includes at least one of the following: remote UE link identifier information associated with the sidelink unicast link between the remote UE and the relay UE for relay service, or configuration of one or more RLC channels including RLC channel identifier information, wherein the configuration of the one or more RLC channels is for the sidelink unicast link between the remote UE and the relay UE; and communicate with network entities via the relay UE at least in part based on the configuration information.

[0025] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a relay UE, the one or more instructions may cause the one or more processors to establish a sidelink unicast link with a remote UE via a sidelink signaling interface; receive configuration information from a network entity, the configuration information including at least one of the following: remote UE link identifier information associated with the sidelink unicast link between the remote UE and the relay UE for relay service; an RLC channel mapping between the sidelink unicast link and one or more RLC channels of the link with the network entity; or data routing information associated with the relay service; configure the sidelink unicast link and one or more RLC channels of the link with the network entity based at least in part on the configuration information; and relay communication between the remote UE and the network entity based at least in part on the configuration information.

[0026] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a network entity, the one or more instructions may cause the one or more processors to send configuration information to a relay user equipment (UE), the configuration information including at least one of the following: remote UE link identifier information associated with a sidelink unicast link between a remote UE and the relay UE for relay services; an RLC channel mapping between the sidelink unicast link and one or more RLC channels of the link with the network entity; or data routing information associated with relay services; and communication between the relay UE and the remote UE, at least in part, based on the configuration information.

[0027] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a remote UE, the one or more instructions may cause the one or more processors to establish a sidelink unicast link with a relay UE via a sidelink signaling interface; configure one or more radio link control (RLC) channels of the sidelink unicast link at least in part based on configuration information, wherein the configuration information includes at least one of: remote UE link identifier information associated with the sidelink unicast link between the remote UE and the relay UE for relay service, or configuration of one or more RLC channels including RLC channel identifier information, wherein the configuration of the one or more RLC channels is for the sidelink unicast link between the remote UE and the relay UE; and communicate with a network entity via the relay UE at least in part based on the configuration information.

[0028] In some aspects, an apparatus for wireless communication may include: a module for establishing a sidelink unicast link with a remote UE via a sidelink signaling interface; a module for receiving configuration information from a network entity, the configuration information including at least one of the following: remote UE link identifier information associated with the sidelink unicast link between the remote UE and the apparatus for relay services, an RLC channel mapping between the sidelink unicast link and one or more RLC channels of the link with the network entity, or data routing information associated with the relay services; a module for configuring the sidelink unicast link and one or more RLC channels of the link with the network entity based at least in part on the configuration information; and a module for relaying communication between the remote UE and the network entity based at least in part on the configuration information.

[0029] In some aspects, an apparatus for wireless communication may include a module for sending configuration information to a relay user equipment (UE), the configuration information including at least one of the following: remote UE link identifier information associated with a sidelink unicast link between a remote UE and a relay UE for relay services, an RLC channel mapping between the sidelink unicast link and one or more RLC channels of a link with a network entity, or data routing information associated with relay services; and a module for communicating with a remote UE via the relay UE, at least in part, based on the configuration information.

[0030] In some aspects, an apparatus for wireless communication may include: a module for establishing a sidelink unicast link with a relay UE via a sidelink signaling interface; a module for configuring one or more radio link control (RLC) channels for the sidelink unicast link based at least in part on configuration information, wherein the configuration information includes at least one of: remote UE link identifier information associated with the sidelink unicast link between the apparatus for relay service and the relay UE, or a configuration of one or more RLC channels including RLC channel identifier information, wherein the configuration of the one or more RLC channels is for the sidelink unicast link between the remote UE and the relay UE; and a module for communicating with a network entity via the relay UE based at least in part on the configuration information.

[0031] The terms generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems, which are basically described herein with reference to the accompanying drawings and description.

[0032] The features and technical advantages of the examples according to this disclosure have been outlined rather broadly above to facilitate a better understanding of the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, their structure and operation, and related advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and is not intended to define limitations of the claims.

[0033] While aspects have been described in this disclosure by way of example, those skilled in the art will understand that these aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip embodiments or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / purchasing equipment, medical devices, or AI-enabled devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the aspects claimed and described. For example, the transmission and reception of wireless signals may include numerous components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors(multiple), interleavers, adders, or summers). The aspects described herein are intended to be practiced in devices, components, systems, distributed arrangements, or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0034] To gain a more detailed understanding of the features of this disclosure, reference can be made to several aspects for a more specific description of the above brief overview, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as the description may acknowledge other equally valid aspects. The same reference numerals in different drawings may denote the same or similar elements.

[0035] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.

[0036] Figure 2 This is a diagram illustrating an example of a base station communicating with a UE in a wireless network according to this disclosure.

[0037] Figure 3 This is a diagram illustrating an example of a control plane protocol architecture for a Layer 2 UE-to-network relay according to this disclosure.

[0038] Figure 4 This is a diagram illustrating an example of a user plane protocol architecture for Layer 2 UE-to-network relay according to this disclosure.

[0039] Figure 5 This is a diagram illustrating example 500 of configuring the RAP layer for a Layer 2 relay service according to this disclosure.

[0040] Figure 6 These are examples 600, 610, and 620 illustrating the mapping from a sidelink RLC channel to a radio access RLC channel according to this disclosure.

[0041] Figure 7 This is a diagram illustrating an example of a RAP header according to this disclosure.

[0042] Figure 8 This is a diagram illustrating an example of signaling associated with SRB configuration for service triggering of out-of-coverage (OOC), idle, or inactive UEs, according to this disclosure.

[0043] Figure 9 This is a diagram illustrating an example of signaling associated with an SRB configuration triggered by a UE, an OOC, an idle, or an inactive remote UE, according to this disclosure.

[0044] Figure 10 Examples of signaling associated with DRB configuration of an OOC, idle, or inactive remote UE according to this disclosure are shown.

[0045] Figure 11 and 12 An example of the configuration of SRB and / or DRB for a remote UE in connection mode according to this disclosure is shown.

[0046] Figure 13 This is a diagram illustrating an example of a base station-triggered RAP layer mapping identifier update according to this disclosure.

[0047] Figure 14 This is a diagram illustrating an example of a RAP layer mapping identifier update triggered by a remote UE according to this disclosure.

[0048] Figure 15 and Figure 16 An example is shown of the configuration of a sidelink unicast link associated with a Layer 2 relay service according to this disclosure, which releases associated signaling.

[0049] Figure 17 This is a diagram illustrating an example process performed, for example, by a relay user equipment, according to this disclosure.

[0050] Figure 18 This is a diagram illustrating an example process performed, for example, by a network entity according to this disclosure.

[0051] Figure 19 This is a diagram illustrating an example process performed, for example, by a remote user device, according to this disclosure.

[0052] Figure 20 This is a diagram illustrating an example process performed, for example, by a relay user equipment, according to this disclosure.

[0053] Figure 21 This is a diagram illustrating an example process performed, for example, by a network entity according to this disclosure.

[0054] Figure 22 This is a diagram illustrating an example process performed, for example, by a remote user device, according to this disclosure. Detailed Implementation

[0055] Various aspects of this disclosure will be described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided to make this disclosure comprehensive and complete, and to fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art should understand that the scope of this disclosure is intended to cover any aspect disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover an apparatus or method practiced using a structure, function, or structure and function other than or different from the aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0056] Several aspects of a telecommunications system will now be described with reference to various devices and technologies. These devices and technologies will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented in hardware or software depends on the specific application and the design constraints on the overall system.

[0057] It should be noted that although the terms commonly associated with 5G or NR radio access technology (RAT) may be used to describe the aspects herein, the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0058] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to this disclosure. Wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network, etc. Wireless network 100 may include multiple base stations 110 (shown as BS110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, Transmit / Receive Point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used. Generally, "BS" is used here interchangeably with Next Generation Radio Access Network (NG-RAN). Unless otherwise explicitly stated, references to BS herein should be understood to refer to either a network entity or NG-RAN.

[0059] A Base Station (BS) can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and can allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and can allow restricted access for UEs associated with that femtocell (e.g., UEs in a Closed User Group (CSG)). A BS for a macrocell can be referred to as a macro BS. A BS for a picocell can be referred to as a pico BS. A BS for a femtocell can be referred to as a femtocell BS or a home BS. Figure 1 In the example shown, BS 110a can be a macro BS of macro cell 102a, BS 110b can be a pico BS of pico cell 102b, and BS 110c can be a femto BS of femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” are used interchangeably herein.

[0060] In some respects, the cell is not necessarily stationary, and the geographical area of ​​the cell can move depending on the location of the mobile BS. In some respects, BSs can use any suitable transport network to interconnect with each other and / or interconnect to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0061] The wireless network 100 may also include relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and send data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay BS 110d can communicate with macro BS 110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, relay station, etc.

[0062] Wireless network 100 can be a heterogeneous network, including different types of base stations (BSs), such as macro BSs, pico BSs, femto BSs, and relay BSs. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0063] Network controller 130 can be coupled to a group of base stations (BSs) and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via backhaul. Base stations can also communicate with each other directly or indirectly via wireless or wired backhaul.

[0064] UEs 120 (e.g., 120a, 120b, 120c) may be distributed across the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or apparatus, a biosensor / device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0065] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, instruments, monitors, and / or location tags, which can communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity to or from a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing housing the components of UE 120, such as processor components and / or memory components. In some aspects, the processor components and memory components can be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) can be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0066] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific Radio Access Platform (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0067] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as a medium for communication with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh network communication. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations performed by base station 110 as described elsewhere herein.

[0068] Devices of wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices of wireless network 100 may communicate using an operating band having a first frequency range (FR1) spanning from 410 MHz to 7.125 GHz, and / or may communicate using an operating band having a second frequency range (FR2) spanning from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as midband frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is generally referred to as the “below 6 GHz” band. Similarly, FR2 is often referred to as the “millimeter wave” band, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU). Therefore, unless specifically stated otherwise, it should be understood that the terms “below 6 GHz”, etc., if used herein, may broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or midband frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise stated, it should be understood that the terms "millimeter wave," etc., if used herein, can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or midband frequencies (e.g., less than 24.25 GHz). It is anticipated that the frequencies included in FR1 and FR2 may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0069] As mentioned above, Figure 1 This is provided as an example. Other examples may differ from those provided. Figure 1 As described.

[0070] Figure 2 This is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein typically T ≥ 1 and R ≥ 1.

[0071] At base station 110, transmitting processor 220 can receive data from one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from the UE, process (e.g., encode and modulate) the UE data based at least in part on the selected (multiple) MCSs for each UE, and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., information for semi-static resource allocation (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively.

[0072] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 can obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data of UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Received Power (RSRP) parameter, the Received Signal Strength Indicator (RSSI) parameter, the Reference Received Quality (RSRQ) parameter, and / or the Channel Quality Indicator (CQI) parameter. In some respects, one or more components of the UE 120 may be included in the housing 284.

[0073] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0074] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included in one or more antenna panels, antenna groups, antenna element groups, and / or antenna arrays. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include coplanar antenna element groups and / or non-coplanar antenna element groups. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include antenna elements within a single housing and / or multiple antenna elements within housings. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include antenna elements coupled to one or more transmitting and / or receiving components (e.g., antennas 234a to 234t and / or antennas 252a to 252r). Figure 2 One or more antenna elements (one or more components).

[0075] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting RSRP, RSSI, RSRQ, and / or CQI). The transmitting processor 264 can also generate reference symbols for one or more reference signals. If applicable, the symbols from the transmitting processor 264 can be pre-encoded by TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, the modulator and demodulator of UE 120 (e.g., MOD / DEMOD 254) can be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The processor (e.g., controller / processor 280) and memory 282 may be used with the transceiver to perform aspects of any of the methods described herein (e.g., as referenced). Figures 3-20 (As described).

[0076] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide decoded data to data sink 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 for scheduling UE 120 for downlink and / or uplink communication. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some aspects, base station 110 includes transceivers. The transceiver may include any combination of antenna(s) 234, modulator and / or demodulator 232, MIMO detector 236, receiver processor 238, transmitter processor 220, and / or TX MIMO processor 230. The processor (e.g., controller / processor 240) and memory 242 may be used with the transceiver to perform aspects of any of the methods described herein (e.g., as referenced). Figures 3-20 (As described).

[0077] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2 Any other component(s) may perform one or more techniques associated with the Relay Adaptation Protocol (RAP) layer configuration, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component(s) can perform or direct, for example Figure 17 Process 1700 Figure 18 Process 1800, Figure 19 The process 1900, Figure 20 The process 2000, Figure 21 Process 2100 Figure 22 The operation of process 2200 and / or other processes described herein. Memory 242 and 282 may store data and program code of base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly or after compilation, transformation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 17 Process 1700 Figure 18 Process 1800, Figure 19 The process 1900, Figure 20 The process 2000, Figure 21 Process 2100 Figure 22 The process 2200 involves operations. In some respects, the executed instructions may include run instructions, conversion instructions, compilation instructions, and / or interpretation instructions.

[0078] In some aspects, UE 120 may include a module for establishing a sidelink unicast link with a remote UE via a sidelink signaling interface; means for receiving configuration information from a network entity, the configuration information including at least one of the following: remote UE link identifier information associated with the sidelink unicast link between the remote UE and the relay UE for relay services, RLC channel mapping between the sidelink unicast link and one or more RLC channels of the link with the network entity, or data routing information associated with the relay service; a module for configuring the sidelink unicast link and one or more RLC channels of the link with the network entity, at least in part based on the configuration information; and means for establishing a sidelink unicast link between the remote UE and the network entity, at least in part based on the configuration information. The module includes: a module for communication; a module for establishing a sidelink unicast link with a relay UE via a sidelink signaling interface; a module for configuring one or more Radio Link Control (RLC) channels for the sidelink unicast link, at least in part based on configuration information, wherein the configuration information includes at least one of the following: remote UE link identifier information associated with the sidelink unicast link between the remote UE and the relay UE for relay service, or a configuration of one or more RLC channels including RLC channel identifier information, wherein the configuration of the one or more RLC channels is for the sidelink unicast link between the remote UE and the relay UE; and a module for communicating with a network entity via the relay UE, at least in part based on the configuration information, etc. In some aspects, these modules may include a combination of... Figure 2 The UE 120 described includes one or more components such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.

[0079] In some aspects, base station 110 may include modules for sending configuration information to relay user equipment (UE), the configuration information including at least one of the following: remote UE link identifier information associated with a sidelink unicast link for relay service between a remote UE and a relay UE; RLC channel mapping between the sidelink unicast link and one or more RLC channels of a link to a network entity; or data routing information associated with relay service; modules for communicating with the remote UE via the relay UE at least in part based on the configuration information; and so on. In some aspects, these modules may include combinations of Figure 2 One or more components of the described base station 110, such as antenna 234, demodulator 232, MIMO detector 236, receiver processor 238, controller / processor 240, transmitter processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.

[0080] Although Figure 2The blocks are shown as different components, but the functions described above for the blocks can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described for the transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be executed by or under the control of the controller / processor 280.

[0081] As mentioned above, Figure 2 This is provided as an example. Other examples may differ from those provided. Figure 2 As described.

[0082] Figure 3 This is a diagram illustrating an example of a control plane protocol architecture 300 for a Layer 2 UE-to-network relay according to this disclosure. Figure 4 This is a diagram illustrating an example of a user plane protocol architecture 400 for a Layer 2 UE-to-network relay according to the present disclosure. For example, the control plane protocol architecture 300 and the user plane protocol architecture 400 may correspond to a remote UE (e.g., UE 120) shown by reference numerals 305 and 405 and a relay UE (e.g., UE 120) shown by reference numerals 310 and 410.

[0083] like Figure 3 As shown, in the control plane, there may be a PC5 interface (e.g., a sidelink interface) between the remote UE and the relay UE, a Uu interface between the relay UE and the next-generation radio access network (NG-RAN) (also referred to herein as the 5G access network (5G-AN)), an N2 interface between the NG-RAN and the access and mobility management function (AMF) of the control plane protocol architecture 300, and an N11 interface between the AMF and the session management function (SMF).

[0084] like Figure 4 As shown, there can be an N3 interface between the NG-RAN and the User Plane Function (UPF) of the User Plane Protocol Architecture 400, and an N6 interface between the UPF and the Core Network (CNW).

[0085] As further illustrated, remote UEs and relay UEs can be associated with corresponding PC5 protocol stacks 315 / 320 and 415 / 420, enabling communication on the PC5 interface between the remote UE and the relay UE. The PC5 protocol stack may include PC5 Radio Link Control (RLC) components, PC5 Media Access Control (MAC) components, PC5 Physical (PHY) components, etc. "PC5" is generally referred to herein as a "sidelink" (e.g., sidelink signaling interface, sidelink unicast link, sidelink RLC channel, etc.). Communication between remote UEs and relay UEs using the PC5 interface can be referred to as sidelink communication. The corresponding PC5 protocol stack may be associated with one or more of a PC5-S entity, a PC5-Radio Resource Control (RRC) entity, or a PC5-PDCP entity (as indicated by reference numeral 325 in the figures). The PC5-S entity can manage the sidelink signaling interface, such as the PC5-S interface. A UE including a PC5-S entity and / or a PC5-RRC entity can handle control signaling and configuration for sidelink connections with another UE, such as connections used for relaying between a remote UE and a trunk UE. In some respects, PC5 protocol stacks 315 / 320 and 415 / 420 may not include a PC5-S entity or a PC5-RRC entity. Furthermore, in certain cases, NG-RAN can handle control signaling and configuration for sidelink connections.

[0086] like Figure 3 As shown by reference numeral 330 in the accompanying drawings, the remote UE is associated with a Non-Access Stratum (NAS) stack, which includes a NAS Session Management (NAS-SM) component, a NAS Session Management (NAS-SM) component, and one or more radio access components (e.g., an NR-RRC component and an NR-PDCP component). Figure 3 As shown by reference numeral 335 in the attached figure, the relay UE is associated with the radio access stack, which includes the NR-RLC component, the NR-MAC component, and the NR-PHY component. Furthermore, the NG-RAN is associated with the radio access interface stack shown by reference numeral 340, which includes the NR-RLC component, the NR-MAC component, the NR-PHY component, the NR-RRC entity, and the NR-PDCP entity.

[0087] The adaptation layer entity of the relay UE shown in Figure 345 can handle relaying from a remote UE to the network or from the network to a remote UE. As used herein, "network" can refer to any one or more of NG-RAN, AMF, SMF, UPF, or core network (CNW). CNW can be referred to as 5G core (5GC). In some aspects, the adaptation layer is referred to as an adaptation layer entity. In some aspects, the adaptation layer entity can be a separate entity between the radio link control (RLC) entity and the packet data aggregation entity. In some aspects, the adaptation layer entity can logically be part of the packet data aggregation entity or the radio link control entity.

[0088] Communication between stacks of remote UEs is indicated by the lines shown in reference numeral 350. The line between the NR-PDCP entity and the PC5-RLC entity indicates how messages not encapsulated in a side-link signaling container such as a PC5-S container (e.g., NR RRC messages generated by the radio access protocol stack) can be communicated from the radio access stack to the PC5 stack for transmission via the side-link interface, or how messages not encapsulated in a PC5-S container can be communicated from the PC5 stack to the radio access stack after being received via the side-link interface. Note that the line between the NR-PDCP entity and the PC5-RLC entity does not involve the PC5-S or PC5-PDCP entities, meaning that the PC5-S and PC5-PDCP entities do not process such messages. Similar lines are shown to indicate communication between the adaptation layer and the PC5-RLC entity, which bypasses the PC5-S and PC5-PDCP entities of the relay UE.

[0089] The line between the NR-PDCP entity and the PC5-S or PC5-RRC entity indicates how messages encapsulated in a PC5-S container (e.g., NR RRC messages generated by the radio access protocol stack) can communicate from the radio access stack to the PC5 stack for transmission via the sidelink interface, or how messages encapsulated in a PC5-S container can communicate from the PC5 stack to the radio access stack after being received via the sidelink interface. Note that the line between the NR-PDCP entity and the PC5-RLC entity involves the PC5-S entity, meaning that the PC5-S entity can process such messages.

[0090] like Figure 4 As shown by reference numeral 425, the remote UE is associated with the user plane protocol stack, which may include application (APP) components, protocol data unit (PDU) components, NR-SDAP components, and NR-PDCP components. Furthermore, the NG-RAN is associated with the user plane components shown by reference numeral 430, which include NR-SDAP components and NR-PDCP components. The NR-SDAP components and NR-PDCP components may be referred to herein as radio access entities.

[0091] NR user plane services (shown as indicated by the line labeled "NR UP") can be transmitted between the NR-PDCP entity and the PC5-RLC component, as shown by reference numeral 435. These NR user plane services can be transmitted to the relay UE via one or more bearers, such as data radio bearers (DRBs) or signaling radio bearers (SRBs). DRBs and SRBs may also be referred to as radio bearers or radio access bearers. As shown by reference numeral 440, NR user plane services can be provided from the relay UE's PC5 stack to the adaptation component, and from the adaptation component to the relay UE's radio access stack. The relay UE's radio access stack can provide NR user plane services to the NG-RAN (not shown).

[0092] The physical layer can provide transport channels to the MAC sublayer. The MAC sublayer can provide logical channels to the RLC sublayer. The RLC sublayer can provide RLC channels to the PDCP sublayer. The PDCP sublayer can provide radio bearers to the SDAP sublayer. The SDAP sublayer can provide QoS flows to the CNW. The RAP layer can handle the mapping between these types of flows, channels, and bearers to facilitate Layer 2 relay services (as described elsewhere in this document). In some respects, the RAP layer can be referred to as the adaptation layer, relay adaptation layer, etc. Radio access bearers can include SRBs, DRBs, etc. RLC channels can also be referred to as RLC bearers. In this case, the RLC channel identifier associated with the RLC channel can be referred to as the RLC bearer identifier.

[0093] As mentioned above, Figure 3 and Figure 4 This is provided as an example. Other examples may differ from those provided. Figure 3 and Figure 4 As described.

[0094] A UE (here referred to as a relay user equipment or relay UE) can relay communication from another UE (here referred to as a remote user equipment or remote UE) to the network, or from the network to a remote UE. In some aspects, a relay UE can perform Layer 2 UE-to-network relay, where the adaptation layer in the relay UE's Layer 2 stack performs the forwarding of the remote UE's communication, compared to Layer 3 relay that may occur at the Internet Protocol (IP) layer. Communication between the relay UE and the remote UE can be referred to here as sidelink communication. In some Layer 2 UE-to-network relay applications, Non-Access Stratum (NAS) and RRC messages can be transparently transmitted between the remote UE and the network using a Packet Data Convergence Protocol (PDCP) end-to-end connection.

[0095] The ProSe sidelink (PC5) interface can provide a sidelink interface between UEs. For example, Vehicle-to-Everything (V2X) communication according to NR Release 16 can be performed using the PC5 unicast control plane stack, which may include a PC5 signaling (PC5-S) interface and a PC5 access stratum (AS) (PC5-AS) interface (such as the PC5-RRC interface). UEs communicating using the PC5 interface can configure a sidelink unicast link context and exchange AS information using the PC5-S and PC5-RRC interfaces. UEs can be associated with a PC5 user plane stack, which may include, for example, PC5 Service Data Adaptation Protocol (SDAP) entities, PC5 PDCP entities, etc.

[0096] Traffic flows can be associated with various Quality of Service (QoS) requirements, relay services, and security settings. Furthermore, a relay UE can provide Layer 2 relay services to one or more remote UEs, which can be associated with corresponding traffic flows, RLC channels, bearers, etc. Therefore, challenges may arise in relaying communication between one or more remote UEs and the network, such as how to handle traffic with varying QoS requirements, how to map radio access RLC channels to sidelink RLC channels, how to handle radio access bearers such as signaling radio bearers and data radio bearers, how to handle relaying multiple remote UEs, etc., which can complicate Layer 2 relay services. In addition, remote UEs may transition between connected / idle / inactive states and / or between in-coverage and out-of-coverage states, or may switch from radio access links to sidelink unicast links and vice versa, which can further complicate Layer 2 relay services.

[0097] The technologies and apparatus described herein provide configuration of the Relay Adaptation Protocol (RAP) layer to support Layer 2 relaying for relay UEs. The RAP layer can be between the RLC layer and the PDCP layer, or it can be part of either the PDCP layer or the RLC layer. The RAP layer can support data delivery, bearer mapping, and data routing associated with Layer 2 relay services. The RAP layer can be configured by the BS (because the relay UE may be within the BS's coverage area). The technologies and apparatus described herein provide signaling for RAP layer configuration, radio bearer mapping configuration, privacy and security support, and traffic routing. Therefore, Layer 2 relay services are configured to handle QoS requirements, one or more remote UEs, various service coverage and connection states, and radio bearer, RLC channel mapping, etc. In this way, the efficiency of Layer 2 relaying is improved, and consistency with QoS requirements is enhanced.

[0098] Figure 5This is a diagram illustrating an example 500 configured with the RAP layer for Layer 2 relay services according to this disclosure. As shown, example 500 includes a relay UE 120, a remote UE 120, and a BS 110. "BS 110" can be used to refer to a base station, gNB, NG-RAN, or network entity.

[0099] Figures 5-16 The example is described in the context of a sidelink unicast link being the connection between remote UE 120 and relay UE 120. However, Figures 5-16 Examples can be implemented using other forms of connectivity, such as peer-to-peer (P2P) communication, device-to-device (D2D) communication, and vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols). Furthermore, Figures 5-16 Examples can be achieved using Bluetooth connections, WiFi connections, etc.

[0100] As shown by reference numeral 510 in the attached figure, the relay UE 120 and the remote UE 120 can establish a sidelink unicast link via a sidelink signaling interface (e.g., a PC5-S interface). In some respects, the sidelink unicast link can be associated with an identifier. For example, the sidelink unicast link can be identified by a combination of a source Layer 2 identifier and a destination Layer 2 identifier. One of the source Layer 2 identifier and the destination Layer 2 identifier can identify the remote UE 120, while the other can identify the relay UE 120. As described elsewhere herein, this identifier can be used to route traffic via a Layer 2 relay. In some respects, the identifier can be referred to as a unique index.

[0101] In some aspects, sidelink unicast links can be configured for specific Layer 2 or Layer 3 trunk services. Layer 2 or Layer 3 trunk services can be associated with identifiers called trunk service codes. Sidelink unicast links used for specific Layer 2 or Layer 3 trunk services can be configured with corresponding security settings associated with the specific trunk service and / or trunk service code. In some aspects, sidelink control plane (e.g., PC5-CP) signaling can use corresponding security settings for control plane signaling specific to a specific trunk service. In some aspects, all services associated with a trunk service code (e.g., data radio bearers (DRBs) and / or signaling radio bearers (SRBs)) can use the same security settings.

[0102] In some respects, a sidelink unicast link can support multiple sidelink RLC channels (e.g., N sidelink RLC channels, where N is an integer) for Radio Access Protocol Data Units (PDU) and / or DRBs. In some respects, a sidelink unicast link can support multiple Radio Access Protocol Data Unit (PDU) sessions on a single link. In some respects, a sidelink unicast link can support multiple sidelink RLC channels configured with the same QoS.

[0103] As shown by reference numeral 520 in the attached figure, relay UE 120 can receive configuration information to support the relay of services of remote UE 120, including the configuration of the RAP layer of relay UE 120. Relay UE 120 and BS 110 can be associated with their respective RAP layers. The RAP layer of the relay UE or BS can handle bearer / RLC channel mapping (e.g., allocation of remote UE indexes, determination of radio access RLC channels corresponding to the sidelink RLC channels of the remote UE, determination of the DRB of the remote UE, determination of the unicast links and corresponding RLC channels of the remote UE, etc.). Additionally or optionally, the RAP layer can handle data transmission between remote UE 120 and the network. Additionally or optionally, the RAP layer can handle data routing, such as in multi-hop scenarios. In some aspects, the configuration information can indicate the mapping of sidelink RLC channels to radio access RLC channels, for example, on a one-to-one basis or on an N-to-1 basis, where N is variable and an integer.

[0104] In some aspects, configuration information may include the configuration of one or more RLC channels. This configuration information may include RLC channel identifier information, such as information elements identifying a set of RLC channels associated with the relay service (e.g., sidelink RLC channels and / or radio access RLC channels). Additionally or optionally, this information may include a set of parameters to configure corresponding RLC and MAC entities for the RLC channels.

[0105] The radio access link between relay UE 120 and BS 110 can be referred to as the link with BS 110. Side links, unicast links, and radio access links can be collectively referred to as relay connections.

[0106] In some respects, the relay UE 120 may receive configuration information via RRC signaling (e.g., NR RRC signaling). For example, an NR RRC message may include information associated with the RAP layer configuration settings, modifications, and / or releases of each remote UE connected to the relay UE for relay services. In one example, an NR RRC setting message may include remote UE index configuration (e.g., for identifying remote UEs connected to the relay UE), SRB / DRB mapping configuration (e.g., bearer mapping), etc. As another example, an NR RRC modification message may include identifier updates to support privacy settings (as described elsewhere in this document). As yet another example, an NR RRC release message (described elsewhere in this document) may indicate the release of the association between the remote UE and the relay UE.

[0107] In some respects, as previously described, configuration information can identify bearer mappings. Bearer mappings can identify mappings between radio bearers (e.g., DRBs or SRBs) and one or more RLC channels, radio access RLC channels, and / or remote UEs. For example, bearer mappings can be provided via a pre-configured relay SRB configuration. As another example, bearer mappings can be provided by BS 110 at least in part based on a relay UE 120 indicating support for Layer 2 relay services. In this case, relay UE 120 can send information indicating support for Layer 2 relay services. As yet another example, BS 110 can provide DRB bearer mappings at least in part based on a request from relay UE 120 (e.g., for a remote UE 120 in an out-of-coverage (OOC) or radio access idle or inactive mode) or at least in part based on a handover from remote UE 120 to a sidelink unicast link (e.g., from a radio access link to a sidelink unicast link).

[0108] In some aspects, the relay UE 120 can be configured with unicast links to multiple remote UEs 120 (e.g., M remote UEs 120, where M is an integer). In some aspects, the relay UE 120 can support multiple radio access RLC channels for relaying services to the multiple remote UEs 120. In some aspects, a single radio access RLC channel can be mapped to multiple sidelink RLC channels with the same QoS level. In some aspects, a single radio access RLC channel can be mapped to multiple sidelink RLC channels with different QoS levels. In this case, in some aspects, the highest QoS level among the different QoS levels can be assigned to the radio access RLC channels. In other aspects, when scheduling and relaying communications, the scheduling of BS 110 and the Link Control Protocol (LCP) operation at the relay UE 120 can take into account each QoS level associated with the multiple sidelink RLC channels.

[0109] In some respects, configuration information can indicate the mapping from sidelink RLC channels to radio access RLC channels. This configuration information is referred to herein as RLC channel mapping. As described elsewhere in this document, RLC channel mapping can be used to determine which RLC channel should be used for transmitting or relaying services. Figure 6 These are diagrams illustrating examples 600, 610, and 620 of the mapping from sidelink RLC channels to radio access RLC channels. In example 600, a one-to-one mapping is configured between the remote UE, the sidelink RLC channel, and the radio access RLC channel. Therefore, example 600 can provide a dedicated radio access RLC channel for each remote UE and provide a one-to-one mapping between the remote UE's sidelink RLC channel and the radio access RLC channel. In example 610, a one-to-N-to-one mapping is configured between the remote UE, the sidelink RLC channel, and the radio access RLC channel, where N is an integer. Therefore, example 610 can provide a dedicated radio access RLC channel for each remote UE and provide an N-to-1 mapping between the remote UE's sidelink RLC channel and the radio access RLC channel. In example 620, an M-to-N-to-1 mapping is configured between the remote UE, the sidelink RLC channel, and the radio access RLC channel, where M and N are integers and can be equal to or unequal to each other. Therefore, Example 620 provides a radio access RLC channel shared among multiple remote UEs, wherein there is an N-to-one mapping between the sidelink RLC channels and radio access RLC channels of the remote UEs. In some aspects, Options 610 and 620 may use an enhanced logical channel identifier (eLCHID) at the relay UE 120 to improve scalability.

[0110] Back Figure 5 As shown by reference numeral 530 in the attached figure, relay UE 120 and BS 110, along with the corresponding RAP layer, can relay communication between remote UE 120 and BS 110 based on configuration information. For example, the RAP layer can determine the sidelink RLC channel or radio bearer associated with a service received via a radio access RLC channel, and vice versa, and can relay the service accordingly. As another example, the RAP layer can determine data routing and / or data transmission information for the service flow.

[0111] In some respects, the RAP layer can use the header associated with the communication to relay the communication. Figure 7This is a diagram illustrating an example 700 of a RAP header according to this disclosure. The RAP header (e.g., one or more fields of the RAP header) can support data routing and mapping of RLC channels to bearers associated with the remote UE 120. For example, the RAP header may include a first field 710 identifying an identifier (e.g., a remote UE index) associated with the remote UE 120, which may be a unique index identifying the unicast link between the remote UE 120 and the relay UE 120. In some aspects, the unique index may include a sidelink unicast link identifier described in conjunction with reference numeral 510. As another example, the RAP header may include a second field 720 identifying a sidelink RLC channel identifier corresponding to the radio access bearer of the remote UE 120. As yet another example, the RAP header may include a third field 730 indicating the route of communications to be relayed thereon. For single-hop relays or single-relay connections, the third field 730 may be absent, or may be set to a value indicating a single-hop relay or single-relay connection (e.g., 1). As shown in the figure, the RAP header can be appended by the relay UE 120 to the NR-PDCP PDU generated by the remote UE 120, or by the BS 110 to the NR-PDCP PDU generated for the remote UE 120.

[0112] refer to Figure 6 The example mapping shown, Figure 7Table 740 shows the mapping configuration and header fields for a single-hop relay. In Table 740, the RemoteUE index refers to the identifier associated with the remote UE 120, the PC5RLCCH ID refers to the identifier associated with the sidelink RLC channel, the UuRLCCH ID refers to the identifier associated with the radio access RLC channel, the PC5LCH ID refers to the identifier associated with the sidelink logical channel, and the RemoteUE RBID refers to the radio bearer identifier associated with the remote UE 120. As shown in Table 740, for options 610, 620, and 630, the configuration information of the RAP layer of the relay UE 120 can identify the mapping of the remote UE index and sidelink RLC channel identifier to the radio access RLC channel identifier, as well as the mapping of the sidelink RLC channel identifier to the sidelink logical channel identifier. For option 610, the configuration information of the RAP layer of the BS 110 can identify the mapping of the radio access RLC channel identifier to the radio bearer identifier of the remote UE 120. For option 620, the configuration information of the RAP layer of BS 110 can identify the mapping of the sidelink RLC channel identifier and radio access RLC channel identifier to the radio bearer identifier of the remote UE 120. For option 630, the configuration information of the RAP layer of BS 110 can identify the mapping of the remote UE index, sidelink RLC channel identifier, and radio access RLC channel identifier to the radio bearer identifier of the remote UE 120. In option 620, the RAP header can identify the sidelink RLC channel identifier, and in option 630, the RAP header can identify the sidelink RLC channel identifier and the remote UE index of the remote UE 120. As described below, BS 110 and relay UE 120 can use these mappings to relay uplink or downlink data.

[0113] For data transmission from remote UE 120 to the network, the RAP layer of relay UE 120 can use configuration information to perform various functions, such as determining the remote UE index associated with the sidelink unicast link of remote UE 120, determining the radio access RLC channel corresponding to the sidelink RLC channel of remote UE 120, adding a RAP header including at least one of the remote UE index, sidelink RLC channel identifier or path identifier to the NR PDCP protocol data unit (PDU) received from remote UE 120, and transmitting the RAP layer PDU to the lower radio access layer for transmission. The RAP layer of BS 110 can perform various functions, including determining the SRB / DRB of remote UE 120 based at least in part on information in the RAP header of the received RAP PDU (e.g., the radio access RLC channel on which the PDU is received, determining the remote UE index of the remote UE 120 associated with the PDU, determining the sidelink RLC channel identifier of the radio access bearer of the remote UE 120, etc.), removing the RAP header, and transmitting NR PDCP PDUs to the upper layer.

[0114] For data transmission from the network to the remote UE 120, the RAP layer of BS 110 can perform various functions, including determining the remote UE index associated with the sidelink unicast link of the remote UE 120, determining the sidelink RLC channel of the remote UE 120 corresponding to the radio access bearer of the remote UE 120, determining the radio access RLC channel corresponding to the sidelink RLC channel of the remote UE 120 on which data is transmitted, adding a RAP header including at least one of the remote UE index, the sidelink RLC channel identifier, or the path identifier to the NR PDCP PDU received from the remote UE 120, and transmitting the RAP layer PDU to the lower radio access layer for transmission on the determined radio access RLC channel. The RAP layer of relay UE 120 can perform various functions, including determining, at least in part, the unicast link of remote UE 120 and the corresponding sidelink RLC channel on which relay data is relayed (e.g., the radio access RLC channel on which PDUs are received, the remote UE index that determines which remote UE 120 unicast link is associated with the PDU, and the sidelink RLC channel identifier for determining the sidelink logical channel identifier of the sidelink unicast link), removing the RAP header, and transmitting the NR PDCP PDU to the lower sidelink layer for transmission on the determined sidelink logical channel.

[0115] In some respects, the relay UE 120 can be part of a multi-hop relay. In the case of a multi-hop relay, the RAP layer of the relay UE 120 and / or the RAP layer of the BS 110 can determine the path for routing data based at least in part on the routing configuration, determine the next-hop destination based at least in part on the routing configuration, and add a path identifier to the RAP header based at least in part on the next-hop determination.

[0116] Back Figure 5 In some respects, the relay UE 120 can relay SRB or DRB services on the relay path. For example, sidelink SRBs can be used for sidelink control plane signaling. One or more access stratum SRBs can be established for NR connections, such as SRB0 (which can be used for RRC messages using the common control channel), SRB1 (which can be used for RRC messages and NAS messages before the establishment of SRB2), SRB2 (which can be used for RRC messages including recorded measurement information and NAS messages after security activation), and / or SRB3 (which can be used for RRC messages such as those in dual connectivity via radio access and sidelink links). One or more access stratum DRB and / or PDU sessions can be established to meet the QoS levels associated with Layer 2 relay services.

[0117] In some aspects, a separate sidelink RLC channel can be configured for each radio access SRB. For example, a UE may have six logical channels corresponding to six SRBs—two sidelink signaling interface logical channels, a sidelink RRC logical channel, and radio access SRB0, SRB1, and SRB2. Additionally or optionally, multiple radio access SRBs can be multiplexed on a single sidelink RLC channel, which can reduce the number of sidelink channels configured for the remote UE 120. In this case, the RAP layer on the remote UE 120 can indicate the radio access SRB index associated with one or more radio access SRBs of the remote UE 120. In some aspects, a separate sidelink RLC channel can be configured for each radio access DRB.

[0118] In some respects, if a relay UE 120 performs Layer 2 relay services for multiple remote UEs 120, the relay UE 120 can be configured with separate Radio Access (RLC) channels to multiplex SRB traffic from the multiple remote UEs 120 (e.g., as in...). Figure 6 (as in Example 620). In some respects, the DRB's radio access RLC channel can be as follows: Figure 6 Any one or more of Examples 600, 610, and 620 are configured as shown.

[0119] In some aspects, configuration information can support radio backhaul at least in part based on the Backhaul Adaptation Protocol (BAP). For example, the relay UE 120 can be considered a radio relay node or an integrated access backhaul node. In this case, the remote UE index and the relay node BAP address can be provided via RRC signaling. In some aspects, multi-hop relay routing configuration can be provided via RRC signaling. In some aspects, additional backhaul routing configuration can be provided via RRC signaling. In some aspects, bearer mapping, such as sidelink RLC channel to radio access RLC channel mapping configuration, can be provided via RRC signaling. In some aspects, the relay UE 120 can indicate flow control feedback to the BS 110 via BAP CONTROLPDU, at least in part based on polling or buffer load that meets a threshold. In this case, the relay UE 120 can include a radio access RLC channel identifier and a route identifier for providing feedback. In some aspects, in the case of multi-hop relay, the relay UE 120 can send a BAP CONTROL PDU to a child node (e.g., a remote UE 120 or another relay UE 120) to indicate a radio link failure (RLF) notification.

[0120] In some respects, the remote UE 120 may be in an OOC state, an idle state (e.g., RRC idle state), or an inactive state (e.g., RRC inactive state). Figure 8 This is a diagram illustrating example 800 of signaling associated with a service-triggered SRB configuration of an OOC, idle, or inactive UE according to this disclosure. Figure 8 As shown, in the first step, the remote UE 120 and the relay UE 120 can perform unicast link establishment (as described in conjunction with reference to reference numeral 510). In the second step (step 2a), the remote UE 120 can send an RRC setup message or an RRC recovery request to the NG-RAN via the relay UE 120. For example, the remote UE 120 can provide such a message on SRB0 at least in part based on the fact that the remote UE 120 has services to provide via the RRC connection.

[0121] As shown by reference numeral 810, BS 110 can provide RRC messages, such as RRC reconfiguration messages, to relay UE 120. Relay UE 120 can reply to the RRC reconfiguration message with an RRC reconfiguration complete message. As further shown, the RRC message may include configuration information from the RAP layer. For example, the RRC message may include configuration information based at least in part on an RRC setup request or RRC recovery request from remote UE 120. As shown by reference numeral 820, BS 110 can provide a RAP header (shown as RAPHDR) to the relay UE 120 associated with the RRC setup message or RRC recovery message. The RAP header may indicate the remote UE index of remote UE 120 and the sidelink RLC channel ID associated with remote UE 120. Therefore, relay UE 120 can forward the RRC setup message or RRC recovery message to remote UE 120. In some aspects, the message illustrated by reference numeral 810 may include RLC mapping configurations, such as mappings from sidelink RLC channels to radio access RLC channels for a specific remote UE index, routing configurations (e.g., if backhaul-based routing such as BAP is used), etc. In some aspects, BS 110 may provide radio access RLC channel configurations (e.g., radio access RLC channel identifier fields assigned via BS 110), sidelink RLC channel configurations (e.g., sidelink RLC channel identifier fields assigned via BS 110), etc., either in the same message 810 or in a separate message sent to the relay UE to set up inheritance.

[0122] Figure 9 This is a diagram illustrating example 900 of signaling associated with SRB configuration triggered by a UE of an OOC, idle, or inactive remote UE according to this disclosure. In example 900, as shown by reference numeral 910, relay UE 120 triggers SRB configuration (e.g., via a sidelink UE information NR message (SUI) sent to the NG-RAN or another RRC message such as UEAssistanceInformation). Relay UE 120 may assign a remote UE index and indicate the remote UE index in the RRC message sent to the NG-RAN. Therefore, as shown by reference numeral 920, the NG-RAN can provide configuration information associated with one or more SRBs. This information may include a combination of... Figure 8 Any information described.

[0123] Figure 10 Example 1000 of signaling associated with DRB configuration of an OOC, idle, or inactive remote UE according to this disclosure is shown. Figure 10 As shown and as indicated by reference numeral 1010 in the attached figure, the remote UE 120, the relay UE 120, the NG-RAN, and / or the 5GC can perform operations related to... Figure 8 The operations described in and / or 9. As shown by reference numeral 1020, NG-RAN can provide configuration information to remote UE 120, indicating bearer mappings of one or more DRBs associated with the remote UE, mappings of one or more sidelink RLC channels to one or more radio access RLC channels, routing configurations, etc. As shown by reference numeral 1030, NG-RAN can provide bearer mappings to remote UE 120 via relay UE 120, indicating radio access DRB configurations, sidelink RLC channel configurations (e.g., at least partially based on sidelink RLC channel configurations), indexes associated with remote UE 120 (e.g., for data relay or data forwarding of relay UE 120), etc. As shown by reference numeral 1040, relay UE 120 and remote UE 120 can exchange sidelink RLC channel identifiers via PC5-RRC messages to use the same configuration provided by BS for the associated sidelink logical channels. As shown by reference numeral 1050 in the attached figure, the relay UE 120 and the remote UE 120 can map the sidelink RLC channel identifier to the corresponding sidelink logical channel (e.g., at least in part based on the sidelink logical channel identifier) ​​to support the associated radio access bearer and data transmission on the RLC channel.

[0124] Figure 11 and 12 Examples 1100 and 1200 illustrate the configuration of SRB and / or DRB for a remote UE in a connected mode according to this disclosure. Example 1100 illustrates a handover-triggered SRB / DRB configuration, while example 1200 illustrates the execution of a handover. Figure 11As shown, a remote UE 120 can establish a radio access connection with a source NG-RAN. Further, the remote UE 120 can provide the source NG-RAN with information associated with the relay UE 120. As indicated by reference numeral 1110, the source NG-RAN and the target NG-RAN can perform handover preparation for the remote UE 120's handover from radio access connection to a sidelink connection (e.g., via a sidelink unicast link with the relay UE 120). Therefore, as indicated by reference numeral 1120, the target NG-RAN can perform RRC reconfiguration with the relay UE 120. For example, the target NG-RAN can provide configuration information for one or more relay radio access RLC bearers, including radio access RLC channel identifiers, sidelink RLC bearers including sidelink RLC channel identifiers corresponding to the remote UE's radio access bearers, RAP layers, etc. As shown by reference numeral 1130 in the attached figure, the source NG-RAN can provide configuration information to the remote UE 120, which indicates the relay UE identifier, the remote UE index of the remote UE 120, the configuration of the radio access bearer, and the configuration of the sidelink RLC bearer (e.g., including a sidelink RLC channel identifier) ​​for the purpose of switching to a sidelink connection.

[0125] like Figure 12 As indicated by reference numeral 1210, the remote UE 120 and the relay UE 120 can perform PC5 unicast link establishment (as described elsewhere herein). As indicated by reference numeral 1220, the remote UE 120 can provide the relay UE 120 with a remote UE index associated with the remote UE 120 (e.g., in a Direct Security Mode Complete (DSM Complete) message, etc.). As indicated by reference numeral 1230, the relay UE 120 can provide the remote UE index to the target NG-RAN. As indicated by reference numeral 1240, the relay UE 120 and the remote UE 120 can exchange sidelink RLC channel identifiers via PC5-RRC messages to use the same configuration provided by BS 110 for the associated sidelink logical channels. As indicated by reference numeral 1250, the relay UE 120 and the remote UE 120 can (e.g., at least in part based on the sidelink logical channel identifier) ​​map the sidelink RLC channel identifier to the corresponding sidelink logical channel. In some respects, the relay UE 120 can assign a remote UE index to the remote UE 120 that is different from the value assigned by the NG-RAN, and in addition to sending the remote UE index assigned by the NG-RAN to the target NG-RAN, it can also send information indicating the remote UE index.

[0126] Back Figure 5As shown by reference numeral 540 in the attached figure, remote UE 120 and relay UE 120 can perform identifier updates for privacy. For example, relay UE 120 can update the remote UE index and radio access RLC channel identifier associated with the relay connection. If the sidelink unicast link is configured as follows... Figure 6 As shown in option 610 or option 620, the NG-RAN can request the relay UE 120 to update the radio access RLC channel identifier associated with the remote UE 120. If the sidelink unicast link is as follows... Figure 6 If configured as shown in option 630, the NG-RAN can request the relay UE 120 to update the remote UE index associated with the unicast link of the remote UE 120 side link. In the first and second cases described above (as associated with options 610 and 620), the relay UE 102 can release and rebuild the corresponding radio access RLC bearer.

[0127] In some respects, BS 110 can trigger updates to the RAP layer mapping identifier, for example, to support the aforementioned privacy updates. Figure 13 This is a diagram illustrating example 1300 of a base station-triggered RAP layer mapping identifier update according to this disclosure. The BS 110 can maintain a timer that indicates the performance of a relay identifier update. The timer can be started when a remote UE index is configured. The timer expiration can trigger... Figure 13 The operations shown. In some respects, Figure 13The operation shown can be triggered by another condition, such as traffic transmitted via relay UE 120 on the radio access RLC bearer of a specific remote UE 120. As shown by reference numeral 1310, BS 110 can update the remote UE index and the corresponding radio access RLC channel identifier at least in part based on whether the sidelink unicast link is configured as shown in options 610, 620, or 630. As shown by reference numeral 1320, BS 110 can send the updated index and identifier to relay UE 120. As shown by reference numeral 1330, relay UE 120 can initiate a link identifier update (LIU) at least in part based on receiving the updated index and identifier from BS 110. As shown by reference numeral 1340, relay UE 120 can provide BS 110 with information indicating a successful unicast link update upon completion of the link identifier update. As shown by reference numeral 1350, in some aspects, BS 110 can provide remote UE 120 with information indicating an updated remote UE index via relay UE 120. In some respects, the remote UE 120 may include a remote UE index in communications related to resuming connection from an inactive state or during the RRC reconstruction process. In some cases, the NG-RAN may request an update based at least in part on a periodic timer maintained for privacy support. In other cases, the NG-RAN may request an update due to an indication from the relay UE 120 that the source Layer 2 or destination Layer 2 identifier corresponding to the sidelink unicast link between the remote UE 120 and the relay UE 120 will be updated.

[0128] Figure 14This is a diagram illustrating an example 1400 of a RAP layer mapping identifier update triggered by a remote UE according to this disclosure. For example, a remote UE 120 may maintain a timer associated with link identifier updates for sidelink unicast links. If the timer is set to a non-infinite value, the remote UE 120 may trigger a RAP layer mapping identifier update due to a link identifier update procedure triggered when the timer expires (as shown by reference numeral 1410). As shown by reference numeral 1420, a relay UE 120 may determine the updated remote UE index of the remote UE 120 based at least in part on receiving a Link Identifier Update Request (LIU Req) message from the remote UE 120. As shown by reference numeral 1430, the relay UE 120 may initiate an index update procedure and may provide the updated remote UE index to the BS 110. As shown by reference numeral 1440, the BS 110 may provide an RRC reconfiguration message indicating the updated remote UE index, may assign a different value to the remote UE index at least in part based on the received remote UE index, and may provide an updated Radio Access RLC channel identifier. As shown in reference numeral 1450, after successful RRC reconfiguration with BS 110, relay UE 120 can send a link identifier update response. In some aspects, BS 110 can determine to update the radio access RLC channel identifier and can perform the actions shown in reference numerals 1430 to 1450. In some aspects, Figure 14 The operation shown can be triggered by another condition, such as traffic transmitted on the sidelink unicast link or a conflict of L2 identifiers on the remote UE 120. In some aspects, the relay UE 120 can trigger the operation shown by reference numeral 1420 and perform the actions shown by reference numerals 1430 to 1450 due to a timer associated with the link identifier update of the sidelink unicast link maintained by the relay UE 120, traffic transmitted on the sidelink unicast link, or a conflict of L2 identifiers at the relay UE 120. In this case, where the operation shown by reference numeral 1420 is triggered by the relay UE 120, after receiving the RRC reconfiguration message shown by reference numeral 1440, the relay UE 120 can perform a RAP layer identifier update procedure, including, for example... Figure 13 The link identifier update procedure with the remote UE 120 is shown in Figures 1330 and 1340. The relay UE 120 may send an RRC reconfiguration complete message to the NG-RAN, at least in part, based on the receipt of the message shown in Figure 1440, to indicate successful reception of the message, and may send another RRC reconfiguration complete message after the successful update of the identifier shown in Figure 1340.

[0129] Back Figure 5As shown by reference numeral 550 in the attached figure, remote UE 120 and relay UE 120 can release the sidelink unicast link. For example, remote UE 120 and relay UE 120 can release the sidelink unicast link and / or the RAP layer configuration associated with the sidelink unicast link. Figure 15 and 16 Examples 1500 and 1600 illustrate the configuration release of associated signaling for a sidelink unicast link associated with a Layer 2 relay service according to this disclosure. Figure 15 In Example 1500, BS 110 uses the message shown in reference numeral 1510 to trigger a configuration release. For example, BS 10 may initiate the release of the unicast link of the remote UE 120 upon successful sidelink-to-radio access mobility operation, based at least in part on the load conditions at the relay UE 120, at least in part on QoS determination, etc. As shown in reference numeral 1520, the relay UE 120 may release the relay connection or sidelink unicast link of the remote UE 120, and may release relay support for the remote UE 120 via the radio access link. Figure 16 In Example 1600, as shown by reference numeral 1610, the configuration release is triggered by the relay UE 120. As shown by reference numeral 1620, when releasing the sidelink unicast link, the relay UE 120 may send an indication to the BS 110 to release the relay connection and / or remote UE index associated with the sidelink unicast link.

[0130] As mentioned above, Figures 5-16 This is provided as an example. Other examples may differ from those provided. Figures 5-16 As described.

[0131] Figure 17 This is a diagram illustrating an example procedure 1700 performed, for example, by a relay UE according to this disclosure. Example procedure 1700 is an example of an operation performed by a relay UE (e.g., UE 120, etc.) associated with a relay adaptation protocol layer configuration.

[0132] like Figure 17 As shown, in some aspects, process 1700 may include establishing a sidelink unicast link with a remote UE via a sidelink signaling interface (block 1710). For example, as described above, a relay UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may establish a sidelink unicast link with a remote UE via a sidelink signaling interface.

[0133] like Figure 17As further illustrated, in some aspects, process 1700 may include receiving configuration information from a network entity, the configuration information including at least one of the following: remote UE link identifier information associated with a sidelink unicast link between a remote UE and a relay UE for relay services, an RLC channel mapping between the sidelink unicast link and one or more RLC channels of the link with the network entity, or data routing information associated with relay services (box 1720). For example, as described above, a relay UE (e.g., using antenna 252, demodulator 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may receive configuration information from a network entity, the configuration information including at least one of the following: remote UE link identifier information associated with a sidelink unicast link between a remote UE and a relay UE for relay services, an RLC channel mapping between the sidelink unicast link and one or more RLC channels of the link with the network entity, or data routing information associated with relay services.

[0134] like Figure 17 As further illustrated, in some aspects, process 1700 may include configuring one or more RLC channels for the sidelink unicast link and the link with the network entity, at least in part, based on configuration information (block 1730). For example, as described above, a relay UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may configure one or more RLC channels for the sidelink unicast link and the link with the network entity, at least in part, based on configuration information.

[0135] like Figure 17 As further illustrated, in some aspects, process 1700 may include relaying communication between a remote UE and a network entity based at least in part on configuration information (block 1740). For example, as described above, the relaying UE (e.g., using antenna 252, demodulator 254, MIMO detector 256, receiver processor 258, controller / processor 280, etc.) may relay communication between the remote UE and the network entity based at least in part on the configuration information.

[0136] Process 1700 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or in conjunction with one or more other processes described elsewhere herein.

[0137] In the first aspect, the Relay Adaptation Protocol (RAP) layer of the relay UE uses at least some configuration information to relay communication.

[0138] In the second aspect, either alone or in combination with the first aspect, the configuration information indicates a mapping of one or more sidelink RLC channels to one or more radio access RLC channels, which uses one of a one-to-one basis or an N-to-1 basis, where N is variable.

[0139] In the third aspect, either alone or in combination with one or more of the first and second aspects, the remote UE link identifier information corresponds to the remote UE index, and the sidelink unicast link is uniquely associated with the assigned remote UE link identifier, based at least in part on the source Layer 2 identifier and the destination Layer 2 identifier associated with the sidelink unicast link.

[0140] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1700 includes assigning a unique index associated with a sidelink unicast link; and sending information indicating the unique index to a network entity via a radio resource control message.

[0141] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the relay service is identified by a relay service code, and the establishment of a sidelink unicast link is based at least in part on security settings corresponding to the relay service code.

[0142] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, a collection of one or more dedicated radio bearers or signaling radio bearers uses the same security settings at least in part based on sidelink unicast links associated with the relay service.

[0143] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the sidelink unicast link supports one or more of the following: multiple sidelink RLC channels for one or more radio access bearers of a remote UE, multiple radio access protocol data unit sessions on a single link, or multiple sidelink RLC channels with the same quality of service configuration.

[0144] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, a remote UE is one of a plurality of remote UEs associated with a corresponding relay service via a relay UE.

[0145] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the remote UE link identifier information corresponds to a unique index assigned to each of a plurality of remote UEs connected to the relay UE via the corresponding side link unicast link.

[0146] In the tenth aspect, communication is relayed via multiple radio access RLC channels associated with multiple remote UEs, either alone or in combination with one or more of the first to ninth aspects.

[0147] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the radio access RLC channel is mapped to multiple sidelink RLC channels associated with the same quality of service.

[0148] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the radio access RLC channel is mapped to multiple sidelink RLC channels associated with different quality of service.

[0149] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the configuration information indicates one or more mappings from the set of radio access RLC channels to the set of sidelink RLC channels and the set of remote UEs.

[0150] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the relay communication is based at least in part on a Relay Adaptation Protocol (RAP) header, the RAP header indicating at least in part on one or more of the following: a unique identifier of a remote UE based on a sidelink unicast link, a sidelink RLC channel associated with a radio access bearer associated with the remote UE, or a path identifier of a data route associated with the relay service.

[0151] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, process 1700 includes performing sidelink control plane signaling on a sidelink signaling radio bearer on a sidelink unicast link.

[0152] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 1700 includes performing radio access signaling via a radio access signaling radio bearer on a sidelink unicast link.

[0153] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, relay communication is based at least in part on a radio access data radio bearer or protocol data unit session configured to meet the quality of service associated with the relay service.

[0154] In the eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, the configuration information indicates one or more corresponding sidelink RLC channels corresponding to one or more radio access signaling radio bearers or one or more radio access data radio bearers.

[0155] In the nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, the configuration information indicates that multiple radio access signaling radio bearers are multiplexed onto a single sidelink RLC channel based at least in part on one or more indices of multiple radio access signaling radio bearers.

[0156] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the configuration information indicates that it is configured to multiplex radio access signaling radio bearers associated with a remote UE using radio access RLC channels.

[0157] In aspect 21, configuration information is received via radio resource control signaling, either alone or in combination with one or more of aspects 1 to 20.

[0158] In the twentieth aspect, either alone or in combination with one or more of the first to twenty-first aspects, the RLC channel mapping is associated with one or more data radio bearers and is received at least in part based on a request from a relay UE or a handover from a remote UE to a sidelink unicast link.

[0159] In aspect twenty-three, either alone or in combination with one or more of aspects one through twenty-two, relaying is performed by the Relay Adaptation Protocol (RAP) layer of the relay UE, which is at least partially based on the Backhaul Adaptation Protocol (BAP) associated with Integrated Access Backhaul Technology.

[0160] In the twenty-fourth aspect, either alone or in combination with one or more of the first to twenty-third aspects, the remote UE is associated with a radio access inactive state, a radio access idle state, or an out-of-coverage state, and at least in part based on an instruction from the relay UE regarding the setting of a sidelink unicast link for relaying with the remote UE, triggers the configuration of one or more RLC channels associated with the signaling radio bearers of one or more remote UEs.

[0161] In the twenty-fifth aspect, either alone or in combination with one or more of the first to twenty-fourth aspects, the remote UE is associated with a radio access inactive state, a radio access idle state, or a state outside coverage, and the configuration of one or more RLC channels associated with one or more remote UE data radio bearers is triggered at least in part based on the successful configuration of the connection with the remote UE.

[0162] In the twenty-sixth aspect, either alone or in combination with one or more of the first to twenty-fifth aspects, process 1700 includes exchanging and configuring one or more sidelink RLC channel identifiers with the remote UE in relation to the sidelink unicast link for relay services.

[0163] In the twentieth aspect, either alone or in combination with one or more of the first to twenty-sixth aspects, process 1700 includes maintaining a mapping between one or more sidelink RLC channel identifiers and one or more sidelink logical channel identifiers assigned to one or more logical channels associated with one or more sidelink RLC channels.

[0164] In the twentieth aspect, either alone or in combination with one or more of the first to twenty-seventh aspects, the remote UE is in a radio access connection mode and triggers the reception of configuration information at least in part based on the remote UE’s handover from radio access connection to relay connection via a sidelink unicast link, and the configuration information includes bearer configuration associated with one or more remote UE data radio bearers or remote UE signaling radio bearers.

[0165] In the twenty-ninth aspect, either alone or in combination with one or more of the first to twenty-eighth aspects, process 1700 includes receiving information indicating a sidelink unicast link index from a remote UE; associating the sidelink unicast link index with a sidelink unicast link between the remote UE and a relay UE; and sending the index to a network entity via a radio resource control message.

[0166] In the thirtieth aspect, alone or in combination with one or more of the first to twenty-ninth aspects, process 1700 includes allocating an index associated with a sidelink unicast link; and sending the index to a network entity via a radio resource control message.

[0167] In the thirty-first aspect, either alone or in combination with one or more of the first to thirtieth aspects, process 1700 includes configuring privacy settings for the relay service; determining at least one of a source Layer 2 (L2) identifier or a target L2 identifier for updating the sidelink unicast link; performing a sidelink unicast link identifier update process with the remote UE; updating one or more radio access RLC channel identifiers and the assigned remote UE index, at least in part based on the successful result of the sidelink unicast link identifier update process; and sending a response message to the network entity indicating the successful result of the sidelink unicast link identifier update process.

[0168] In the thirty-second aspect, either alone or in combination with one or more of the first to thirty-first aspects, at least one of the source L2 identifier or target L2 identifier for updating the sidelink unicast link is determined based on at least one of the following: receiving an indication from a network entity to update at least one of the source L2 identifier or target L2 identifier, one or more radio access RLC channel identifiers, or an assigned remote UE index, a configuration maintained for the sidelink unicast link, or receiving a link identifier update request from a remote UE.

[0169] In aspect thirty-three, either alone or in combination with one or more of aspects one through thirty-two, process 1700 includes sending a notification to the network entity before initiating the sidelink unicast link identifier update process.

[0170] In aspect thirty-four, either alone or in combination with one or more of aspects one through thirty-three, the relay UE triggers, at least in part, an update of the source L2 identifier or the target L2 identifier of the sidelink unicast link based on a timer.

[0171] In the thirty-fifth aspect, either alone or in combination with one or more of the first to thirty-fourth aspects, process 1700 includes releasing a sidelink unicast link based at least in part on a release instruction from a network entity, wherein the release instruction is based at least in part on at least one of the following: a handover from a remote UE to a radio access connection, a load associated with a relay UE, or a quality of service requirement.

[0172] In the thirty-sixth aspect, either alone or in combination with one or more of the first to thirty-fifth aspects, process 1700 includes releasing the sidelink unicast link; and sending an indication to the network entity that the sidelink unicast link has been released.

[0173] although Figure 17 An example box of process 1700 is shown, but in some respects, process 1700 may include more than Figure 17 The boxes depicted may be more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or optionally, two or more boxes in process 1700 may be executed in parallel.

[0174] Figure 18 This is a diagram illustrating an example process 1800 performed, for example, by a network entity according to this disclosure. Example process 1800 is an example of an operation performed by a network entity (e.g., BS 110, NG-RAN, gNB, etc.) associated with a relay adaptation protocol layer configuration.

[0175] like Figure 18As shown, in some aspects, process 1800 may include sending configuration information to a relay user equipment (UE), the configuration information including at least one of the following: remote UE link identifier information associated with a sidelink unicast link between a remote UE and a relay UE for relay service, an RLC channel mapping between the sidelink unicast link and one or more RLC channels of a link with a network entity, or data routing information associated with the relay service (block 1810). For example, as described above, a network entity (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.) may send configuration information to the relay user equipment (UE), the configuration information including at least one of the following: remote UE link identifier information associated with a sidelink unicast link between a remote UE and a relay UE for relay service, an RLC channel mapping between the sidelink unicast link and one or more RLC channels of a link with a network entity, or data routing information associated with the relay service.

[0176] like Figure 18 As further illustrated, in some aspects, process 1800 may include communication with a remote UE via a relay UE, at least in part, based on configuration information (block 1820). For example, as described above, network entities (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.) may communicate with a remote UE via a relay UE, at least in part, based on configuration information.

[0177] Process 1800 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or in conjunction with one or more other processes described elsewhere herein.

[0178] In the first aspect, the configuration information is used for the Relay Adaptation Protocol (RAP) layer of the relay UE.

[0179] In the second aspect, either alone or in combination with the first aspect, the configuration information indicates a mapping of one or more sidelink RLC channels to one or more radio access RLC channels, which uses one of a one-to-one basis or an N-to-1 basis, where N is variable.

[0180] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1800 includes receiving information via radio resource control messages indicating a unique index associated with a sidelink unicast link, wherein the communication is at least in part based on the information indicating the unique index.

[0181] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1800 includes configuring a radio access data radio bearer or protocol data unit session to meet the quality of service associated with the relay service.

[0182] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the configuration information indicates one or more corresponding sidelink RLC channels corresponding to one or more radio access signaling radio bearers or one or more radio access data radio bearers.

[0183] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the configuration information indicates that multiple radio access signaling radio bearers are multiplexed onto a single sidelink RLC channel based at least in part on one or more indices of multiple radio access signaling radio bearers.

[0184] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the configuration information indicates that it is configured to multiplex radio access signaling radio bearers associated with a remote UE using radio access RLC channels.

[0185] In the eighth aspect, configuration information is transmitted via radio resource control signaling, either alone or in combination with one or more of the first to seventh aspects.

[0186] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the RLC channel mapping is associated with one or more data radio bearers and is transmitted at least in part based on a request received from a relay UE or a remote UE switching to a sidelink unicast link.

[0187] In the tenth aspect, communication is performed by a Relay Adaptation Protocol (RAP) layer of a network entity, either alone or in combination with one or more of the first to ninth aspects, the Relay Adaptation Protocol (RAP) layer being at least partially based on a Backhaul Adaptation Protocol (BAP) associated with Integrated Access Backhaul Technology.

[0188] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the remote UE is associated with a radio access inactive state, a radio access idle state, or an out-of-coverage state, and the transmission of configuration information further includes: transmitting configuration information at least in part based on an instruction received by the relay UE regarding the setting of a sidelink unicast link for relaying with the remote UE, wherein the configuration information configures one or more RLC channels associated with the signaling radio bearers of one or more remote UEs.

[0189] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the method further includes: transmitting information indicating a sidelink RLC channel identifier of the remote UE to the remote UE via the relay UE.

[0190] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the remote UE is associated with a radio access inactive state, a radio access idle state, or a state outside coverage, and the transmission of configuration information further includes: transmitting configuration information at least in part based on the successful configuration of the connection with the remote UE, the configuration information configuring one or more RLC channels associated with one or more remote UE data radio bearers.

[0191] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 1800 includes sending to the remote UE information indicating a remote UE index, one or more remote UE data radio bearers, and one or more sidelink RLC channel identifiers associated with one or more RLC channels.

[0192] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, process 1800 includes receiving information indicating one or more sidelink RLC channel identifiers associated with configuring a sidelink unicast link for relay services.

[0193] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the remote UE is in a radio access connection mode, and the transmission of configuration information further includes: transmitting configuration information at least in part based on the remote UE's handover from radio access connection to a relay connection via a sidelink unicast link, the configuration information including bearer configuration associated with one or more remote UE data radio bearers or remote UE signaling radio bearers.

[0194] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 1800 includes sending information indicating a remote UE index associated with the remote UE to the remote UE in a handover command.

[0195] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, process 1800 includes receiving a sidelink unicast link index determined by the relay UE via a radio resource control message.

[0196] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, process 1800 includes: determining at least one of a source Layer 2 (L2) identifier or a target L2 identifier for updating the sidelink unicast link; triggering a sidelink unicast link identifier update process for the relay UE and the remote UE, at least in part based on determining at least one of the source L2 identifier or the target L2 identifier; and receiving from the relay UE a response message indicating a successful result of the link identifier update process.

[0197] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, a sidelink unicast link identifier update procedure is triggered based at least in part on an indication to update at least one of the following: a source L2 identifier, a destination L2 identifier, one or more radio access RLC channel identifiers, or an assigned remote UE index.

[0198] In the twenty-first aspect, updates are triggered individually or in combination with one or more of the first to twentieth aspects, based at least in part on a timer associated with a sidelink unicast link identifier.

[0199] In aspect twenty-two, either alone or in combination with one or more of aspects one through twenty-one, the timer is one of a plurality of timers associated with the corresponding sidelink unicast link identifier.

[0200] In the twenty-third aspect, either alone or in combination with one or more of the first to twenty-two aspects, a timer is associated with a plurality of sidelink unicast link identifiers, and a sidelink unicast link identifier update process is triggered for the plurality of sidelink unicast link identifiers when the timer expires.

[0201] In aspect 24, a timer is started, either alone or in combination with one or more of aspects 1 to 23, when a sidelink unicast link identifier is set.

[0202] In the twenty-fifth aspect, alone or in combination with one or more of the first to twenty-fourth aspects, process 1800 includes sending information to the remote UE indicating the assigned remote UE index.

[0203] In the twenty-sixth aspect, either alone or in combination with one or more of the first to twenty-fifth aspects, process 1800 includes receiving a notification from a relay UE indicating that a sidelink unicast link identifier update process will be performed to update at least one of a source Layer 2 (L2) identifier or a target L2 identifier, wherein the update of the source L2 identifier or target L2 identifier of the sidelink unicast link is triggered by the relay UE at least in part based on a timer.

[0204] In the twenty-seventh aspect, alone or in combination with one or more of the first to twenty-sixth aspects, process 1800 includes sending to the relay UE information indicating at least one of an updated Radio Access RLC Channel Identifier or an assigned Remote UE Index associated with a sidelink unicast link.

[0205] In the twentieth aspect, alone or in combination with one or more of the first to twenty-seventh aspects, process 1800 includes sending an indication to release a side link unicast link, wherein the release indication is based at least in part on at least one of the following: a handover from a remote UE to a radio access connection, a load associated with a relay UE, or a quality of service requirement.

[0206] In the twenty-ninth aspect, either alone or in combination with one or more of the first to twenty-eighth aspects, process 1800 includes receiving a Relay Adaptation Protocol (RAP) Protocol Data Unit (PDU); determining, at least in part, a signaling radio bearer or data radio bearer associated with a remote UE based on the RAP header of the received RAPPDU; removing the RAP header; and transmitting a new Radio Packet Data Convergence Protocol (PDCP) PDU of the RAP PDU to the upper layer.

[0207] In the thirtieth aspect, either alone or in combination with one or more of the first to twenty-ninth aspects, process 1800 includes determining a remote UE index associated with a sidelink unicast link of a remote UE; determining a sidelink RLC channel of the remote UE corresponding to a radio access bearer of the remote UE, and determining a radio access RLC channel corresponding to the sidelink RLC channel of the remote UE; generating a relay adaptation protocol (RAP) header, which includes at least one of a remote UE index, a sidelink RLC channel identifier or a path identifier of the sidelink RLC channel of the remote UE; and transmitting a RAP layer protocol data unit (PDU) with the RAP header on the radio access RLC channel.

[0208] although Figure 18 An example box of process 1800 is shown, but in some respects, process 1800 may include more than Figure 18 The boxes depicted may be more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or optionally, two or more boxes in process 1800 may be executed in parallel.

[0209] Figure 19 This is a diagram illustrating an example procedure 1900 performed, for example, by a remote UE according to this disclosure. Example procedure 1900 is an example of a remote UE (e.g., UE 120, etc.) performing operations associated with a relay adaptation protocol layer configuration.

[0210] like Figure 19As shown, in some aspects, process 1900 may include establishing a sidelink unicast link with the relay UE via a sidelink signaling interface (block 1910). For example, as described above, a remote UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may establish a sidelink unicast link with the relay UE via a sidelink signaling interface.

[0211] like Figure 19 As further illustrated, in some aspects, process 1900 may include configuring one or more radio link control (RLC) channels for a sidelink unicast link at least partially based on configuration information, wherein the configuration information includes at least one of the following: remote UE link identifier information associated with the sidelink unicast link between the remote UE and the relay UE for relay service, or the configuration of one or more RLC channels, including RLC channel identifier information, wherein the configuration of one or more RLC channels is for the sidelink unicast link between the remote UE and the relay UE (block 1920). For example, as described above, a remote UE (e.g., using antenna 252, demodulator 254, MIMO detector 256, receiver processor 258, controller / processor 280, etc.) may configure one or more radio link control (RLC) channels for the sidelink unicast link at least partially based on the configuration information. In some aspects, the configuration information includes remote UE link identifier information associated with a sidelink unicast link between a remote UE and a relay UE for relay services, or at least one configuration of one or more RLC channels including RLC channel identifier information, wherein the configuration of one or more RLC channels is for a sidelink unicast link between a remote UE and a relay UE.

[0212] like Figure 19 As further illustrated, in some aspects, process 1900 may include communication with a network entity via a relay UE based at least in part on configuration information (block 1930). For example, as described above, a remote UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may communicate with a network entity via a relay UE based at least in part on configuration information.

[0213] Process 1900 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or in conjunction with one or more other processes described elsewhere herein.

[0214] In the first aspect, the relay service is identified by a relay service code, and the establishment of a sidelink unicast link is based at least in part on security settings corresponding to the relay service code.

[0215] In a second aspect, either alone or in combination with the first aspect, process 1900 includes the configuration of receiving one or more remote UE-dedicated radio bearers or a set of remote UE sidelink signaling radio bearers using security settings at least in part based on relay service codes.

[0216] In the third aspect, either alone or in combination with one or more of the first and second aspects, the remote UE link identifier information corresponds to a unique index assigned to the remote UE.

[0217] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1900 includes performing sidelink control plane signaling on a sidelink signaling radio bearer on a sidelink unicast link.

[0218] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1900 includes performing radio access signaling via a radio access signaling radio bearer on a sidelink unicast link.

[0219] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the RLC channel is associated with multiple radio access signaling radio bearers, and the relay adaptation protocol layer of the remote UE indicates the index of the selected radio access signaling radio bearer for communication via the RLC channel.

[0220] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the remote UE is associated with a radio access inactive state, a radio access idle state, or a state outside coverage, and the method further includes: receiving, in conjunction with configuring radio access signaling radio bearers, information indicating the remote UE and information including a sidelink RLC channel identifier for the sidelink RLC channel configuration.

[0221] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the remote UE is associated with a radio access inactive state, a radio access idle state, or an out-of-coverage state, and the method further includes: receiving information indicating the remote UE, the configuration of the radio access data radio bearer, and the sidelink RLC channel configuration including a sidelink RLC channel identifier, in conjunction with the configuration of the radio access data radio bearer.

[0222] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1900 includes exchanging one or more sidelink RLC channel identifiers with the relay UE in connection with configuring a sidelink unicast link for the relay service.

[0223] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the remote UE is in a radio access connection mode, and at least in part, the reception of configuration information is triggered based on the remote UE’s handover from radio access connection to relay connection via a sidelink unicast link, and the configuration information includes bearer configurations associated with one or more remote UE data radio bearers or remote UE signaling radio bearers.

[0224] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, process 1900 includes sending information to the relay UE indicating a sidelink unicast link index of the sidelink unicast link.

[0225] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 1900 includes receiving information indicating an updated remote UE index by incorporating a sidelink unicast link identifier update process.

[0226] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, process 1900 includes sending a link identifier update request to the relay UE at least in part based on a timer; and performing a sidelink unicast link identifier update process with the relay UE at least in part based on the link identifier update request.

[0227] although Figure 19 An example box of process 1900 is shown, but in some respects, process 1900 may include more than Figure 19 The boxes depicted may be more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or optionally, two or more boxes in process 1900 may be executed in parallel.

[0228] Figure 20 This is a diagram illustrating an example procedure 2000 performed, for example, by a relay UE according to this disclosure. Example procedure 2000 is an example of an operation performed by a relay UE (e.g., UE 120, relay UE 120, relay UE 310, relay UE 410) associated with a RAP layer configuration.

[0229] like Figure 20 As shown, in some aspects, process 2000 may include establishing a connection with a remote UE for relay communication (block 2010). For example, as described above, a relay UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may establish a connection with a remote UE for relay communication. The connection establishment is, for example, by... Figure 5 Reference numeral 510 and in Figure 8 , Figure 9 , Figure 12 , Figure 15 and Figure 16 This is illustrated (e.g., as "PC5 unicast link establishment" or "S1 L2 relay connection setup"). The connection can be a PC5 connection (e.g., a sidelink unicast link establishment using the sidelink signaling interface), a Bluetooth connection, a WiFi connection, a device-to-device connection, etc.

[0230] like Figure 20 As further illustrated, in some aspects, process 2000 may include receiving configuration information from a network entity. This configuration information includes at least one of the following: remote UE connection identifier information associated with a connection between the remote UE and the relay UE for relay service, or a configuration including relay channel identifier information, wherein the configuration is for the connection between the remote UE and the relay UE and the link with the network entity, and wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity (block 2020). For example, a relay UE (e.g., using antenna 252, demodulator 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may receive configuration information (e.g., configuration information 520) from a network entity. This configuration information includes at least one of the following: remote UE connection identifier information associated with a connection between the remote UE and the relay UE for relay service, or a configuration including relay channel identifier information. The configuration can be used for connections between remote UEs and relay UEs, as well as links with network entities (such as radio access links, which could be Uu links, between a relay UE and a network entity). As described above, the configuration indicates the relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity. For example, the relay channel mapping is... Figure 6 The figures are shown with reference numerals 610, 620, and 630. A relay channel may include, for example, an RLC channel. For example, combined with... Figure 5 The reference numeral 520 is used to describe the remote UE connection identifier information. The remote UE connection identifier may include remote UE index configuration, unique identifier, remote UE index associated with the remote UE, etc.

[0231] like Figure 20As further illustrated, in some aspects, process 2000 may include configuring one or more relay channels for the connection and one or more relay channels for the link with the network entity, at least in part, based on configuration information (block 2030). For example, as described above, a relay UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may configure one or more relay channels for the connection and one or more relay channels for the link with the network entity, at least in part, based on configuration information. For example, in Figure 5 In the figure, the configuration of one or more relay channels is shown at reference numerals 530 and 540.

[0232] like Figure 20 As further illustrated, in some aspects, process 2000 may include relaying communication between a remote UE and a network entity based at least in part on configuration information (block 2040). For example, as described above, a relay UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may relay communication between the remote UE and the network entity based at least in part on the configuration information. The relaying of communication is, for example, carried out by... Figure 5 The figure is shown with reference numeral 530.

[0233] Process 2000 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or in conjunction with one or more other processes described elsewhere herein.

[0234] In the first aspect, the connection is via the sidelink signaling interface.

[0235] In the second aspect, alone or in combination with the first aspect, the relay adaptation protocol (RAP) layer of the relay UE (such as...) Figure 3 The RAP layer 345 uses at least some configuration information to relay communication.

[0236] In the third aspect, either alone or in combination with one or more of the first and second aspects, relay channel mapping uses one of a one-to-one basis or an N-to-1 basis, where N is variable. Examples of such a basis include... Figure 6 As shown.

[0237] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the connection is at least one of sidelink unicast link establishment using a sidelink signaling interface, Bluetooth connection, WiFi connection, or device-to-device connection.

[0238] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the remote UE connection identifier information corresponds to a remote UE index, wherein the connection is uniquely associated with the assigned remote UE connection identifier identified by the remote UE connection identifier information. The remote UE index is a unique index identifying the connection between the remote UE 120 and the relay UE 120, such as... Figure 7 As shown by reference numeral 710 in the attached figure.

[0239] In the sixth aspect, either alone or in combination with one or more of the first to fourth aspects, for a sidelink unicast link, the remote UE connection identifier is based at least in part on the source Layer 2 identifier and the target Layer 2 identifier associated with the sidelink unicast link.

[0240] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 2000 includes assigning a unique index associated with the connection, wherein the unique index is an assigned remote UE connection identifier (e.g., remote UE connection identifier information) identified by remote UE connection identifier information. Figure 7 (As shown by reference numeral 710 in the attached figure), and sends information indicating the unique index to the network entity via a radio resource control message. For example, in combination with Figure 9 Reference numeral 910 in the accompanying figure illustrates the allocation of unique indexes and the transmission of radio resource control messages. Examples of radio resource control messages are also provided. Figure 12 The attached figures are labeled 1230 and Figure 14 The figure is shown with reference numeral 1430.

[0241] In the eighth aspect, individually or in combination with one or more of the first through seventh aspects, a collection of one or more sidelink-dedicated radio bearers or signaling radio bearers uses the same security settings, at least in part, based on the connection associated with the relay service. This will combine Figure 5 The accompanying figure 510 is described in more detail.

[0242] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the connection supports multiple relay channels for one or more radio access bearers for a remote UE, multiple radio access protocol data unit (PDU) sessions on a single link, or one or more relay channels with the same or different quality of service (QoS) configurations. Figure 5 Reference numeral 510 in the accompanying drawings describes multiple relay channels used for radio access bearers (i.e., bearers associated with the connection between a relay UE and a network entity). Combined with... Figure 5 Figure 510 illustrates multiple radio access PDU sessions on a single link. Combined with... Figure 5 Figure 510 describes multiple relay channels with the same QoS configuration. (Combined) Figure 5 The attached figure 520 describes multiple relay channels with different QoS configurations.

[0243] In the tenth aspect, communication is relayed individually or in combination with one or more of the first to ninth aspects via multiple radio access relay channels associated with multiple remote UEs. For example, the multiple radio access relay channels are provided by... Figure 6 The figure is shown with reference numeral 620.

[0244] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the radio access relay channel is mapped to multiple relay channels used for connection. Figure 6 The attached figure 610 provides an example of this mapping.

[0245] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, relay communication is at least partially based on a Relay Adaptation Protocol (RAP) header (such as...). Figure 7 The RAP header of Example 700 shown here indicates one or more identifiers of the remote UE, at least in part, based on a unique identifier of the connection (i.e., such as...). Figure 7 The reference numeral 710 indicates the remote UE index), and one or more relay channels (e.g., such as the one or more relay channels associated with the radio access bearer associated with the remote UE) for the connection. Figure 7 The PC5 RLC channel identifier shown by reference numeral 720 in the attached figure), or the path identifier used for data routing associated with relay services (such as... Figure 7 (The path identifier is shown in the attached figure 730). The identifier of the remote UE (i.e., the remote UE connection identifier) ​​may be based at least in part on the unique identifier of the connection. For example, the identifier of the remote UE may be the same as the unique identifier, may be a part of the unique identifier, may be a hash of the unique identifier, etc.

[0246] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, relay communication is at least partially based on a radio access data radio bearer (DRB) configured to satisfy the Quality of Service (QoS) associated with the relay service for Protocol Data Unit (PDU) sessions. Figure 5 An example is provided at reference numeral 530 in the attached figure.

[0247] In the fourteenth aspect, individually or in combination with one or more of the first to thirteenth aspects, the connected one or more relay channels correspond to one or more radio access signaling radio bearers (SRBs) or one or more radio access data radio bearers (DRBs). Figure 5 The attached figure 520 describes an example.

[0248] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the configuration information indicates that at least in part, one or more indices of multiple radio access signaling radio bearers (SRBs) are multiplexed onto a single connected relay channel. This is, for example, combined with... Figure 5 The figure is described by reference numeral 530.

[0249] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the configuration information indicates a radio access relay channel configured for multiplexing multiple radio access signaling radio bearers (SRBs) associated with a remote UE. This is, for example, combined with... Figure 5 The figure is described by reference numeral 530.

[0250] In the seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, relaying is performed by the Relay Adaptation Protocol (RAP) layer of the relay UE, which is at least partially based on the Backhaul Adaptation Protocol (BAP) associated with Integrated Access Backhaul Technology. Figure 5 The figure 530 is used to describe a RAP layer that is at least partially based on BAP.

[0251] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, process 2000 includes exchanging one or more relay channel identifiers of the connection with a remote UE when configuring a connection for relay service. Example provided by Figure 10 The attached figures 1040 and Figure 12 The figure is shown with reference numeral 1240.

[0252] In the nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, process 2000 includes maintaining a mapping between one or more relay channel identifiers used for connection and one or more logical channel identifiers assigned to one or more logical channels associated with the one or more relay channels used for connection. This mapping is, for example, provided by... Figure 10 The attached figures 1050 and Figure 7 Table 740 shows this.

[0253] In the twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the remote UE is in a radio access connection mode (e.g. Figure 11 (as shown), and wherein at least in part is based on the handover of the remote UE from the radio access connection to the trunk connection via the trunk UE (as shown). Figure 12 (As shown by reference numeral 1240) to trigger the reception of configuration information, wherein the configuration information includes bearer configurations associated with one or more radio access data radio bearers or signaling radio bearers (by... Figure 11(As shown by reference numeral 1120 in the attached figure).

[0254] In the twenty-first aspect, either alone or in combination with one or more of the first to twentieth aspects, process 2000 includes receiving information indicating a remote UE connection identifier from a remote UE, associating the remote UE connection identifier with a connection between the remote UE and a relay UE, and transmitting the remote UE connection identifier to a network entity via a radio resource control message. (Example provided) Figure 12 Appendix reference numeral 1220 Figure 13 The attached figures 1330 and Figure 14 The figure is shown with reference numeral 1420.

[0255] In the twenty-second aspect, either alone or in combination with one or more of the first to twenty-first aspects, process 2000 includes configuring privacy settings for the relay service, determining an identifier to update for connection, performing a connection identifier update with the remote UE, updating one or more radio access relay channel identifiers and the assigned remote UE index based at least in part on the success of the connection identifier update, and sending a response message to a network entity indicating the success of the connection identifier update. Figure 5 Appendix label 540 provides an example of a privacy update.

[0256] In the twenty-third aspect, either alone or in combination with one or more of the first to twenty-two aspects, process 2000 includes releasing the connection and sending an indication to the network entity that the connection has been released. Figure 16 An example is provided.

[0257] although Figure 20 An example box of process 2000 is shown, but in some respects, process 2000 can include more than Figure 20 The boxes depicted may be more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or optionally, two or more boxes in process 2000 may be executed in parallel.

[0258] Figure 21 This is a diagram illustrating an example process 2100 performed by a network entity, for example, according to this disclosure. Example process 2100 is an example of a network entity (e.g., BS 110, NG-RAN 340, source NG-RAN, target NG-RAN, CU, etc.) performing operations associated with RAP layer configuration.

[0259] like Figure 21As shown, in some aspects, process 2100 may include sending configuration information to a relay UE, the configuration information including at least one of the following: remote UE connection identifier information associated with the connection between the remote UE and the relay UE for relay service, including configuration of relay channel identifier information, wherein the configuration is for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity (box 2110). For example, as described above, a network entity (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.) may send configuration information to a relay user equipment (UE). The configuration information includes at least one of the following: remote UE connection identifier information associated with the connection between the remote UE and the relay UE for relay service; configuration including relay channel identifier information; wherein the configuration is for the connection between the remote UE and the relay UE and the link with the network entity; wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity.

[0260] like Figure 21 As further illustrated, in some aspects, process 2100 may include communication with a remote UE via a relay UE, at least in part, based on configuration information (block 2120). For example, as described above, network entities (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.) may communicate with a remote UE via a relay UE, at least in part, based on configuration information.

[0261] Process 2100 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or in conjunction with one or more other processes described elsewhere herein.

[0262] In the first aspect, the configuration information is used for the Relay Adaptation Protocol (RAP) layer of the relay UE.

[0263] In a second aspect, alone or in combination with the first aspect, process 2100 includes configuring a radio access data radio bearer or protocol data unit session to meet the quality of service associated with relay services.

[0264] In the third aspect, either alone or in combination with one or more of the first and second aspects, the configuration information indicates that one or more connected relay channels correspond to one or more radio access signaling radio bearers or one or more radio access data radio bearers.

[0265] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the remote UE is associated with a radio access inactive state, a radio access idle state, or a state outside coverage, and wherein the transmission of configuration information also includes transmitting configuration information at least in part based on an indication received by the relay UE regarding the setting of a connection for relaying with the remote UE, wherein the configuration information configures one or more relay channels of a connection associated with one or more signaling radio bearers of the remote UE.

[0266] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the method further includes transmitting information via the relay UE to the remote UE of a relay channel identifier of one or more relay channels indicating the connection of the remote UE.

[0267] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the remote UE is associated with a radio access inactive state, a radio access idle state, or a state outside coverage, and the transmission of configuration information further includes transmitting configuration information based at least in part on the successful configuration of the connection with the remote UE, wherein the configuration information configures one or more relay channels of the connection associated with one or more remote UE data radio bearers.

[0268] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 2100 includes sending to the remote UE information indicating a remote UE index, one or more remote UE data radio bearers, and one or more relay channel identifiers associated with one or more connected relay channels.

[0269] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 2100 includes receiving information indicating one or more relay channel identifiers associated with the configuration connection.

[0270] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the remote UE is in a radio access connection mode, and the transmission of configuration information further includes transmitting configuration information at least in part based on the remote UE’s handover from radio access connection to a relay connection via a connection, wherein the configuration information includes bearer configuration associated with one or more remote UE data radio bearers or remote UE signaling radio bearers.

[0271] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, process 2100 includes sending information indicating a remote UE index associated with the remote UE to the remote UE in a handover command.

[0272] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, process 2100 includes receiving a connection index determined by the relay UE from the relay UE via a radio resource control message.

[0273] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 2100 includes determining at least one of a source Layer 2 (L2) identifier or a target L2 identifier for an updated connection, wherein the connection is a sidelink unicast link, triggering a connection identifier update for the relay UE and the remote UE based at least in part on determining at least one of the source L2 identifier or the target L2 identifier for an updated connection identifier, and receiving a response message from the relay UE indicating a successful result of the connection identifier update.

[0274] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, a connection identifier update is triggered based at least in part on an indication of at least one of the source L2 identifier, the target L2 identifier, one or more radio access relay channel identifiers, or an assigned remote UE index.

[0275] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the connection identifier update is triggered at least in part based on a timer associated with the connection identifier.

[0276] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, process 2100 includes sending information to the remote UE indicating the assigned remote UE index.

[0277] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 2100 includes receiving a notification from a relay UE indicating that a connection identifier update process will be performed to update at least one of the source Layer 2 (L2) identifier or the target L2 identifier of the connection, wherein the update of the source L2 identifier or the target L2 identifier of the connection is triggered by the relay UE at least in part based on a timer.

[0278] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 2100 includes sending to the relay UE information indicating at least one of an updated radio access relay channel identifier or an assigned remote UE index associated with the connection.

[0279] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, process 2100 includes sending a release indication to release the connection, wherein the release indication is based at least in part on at least one of a remote UE switching to a radio access connection, a load or quality of service requirement associated with a relay UE.

[0280] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, process 2100 includes receiving a Relay Adaptation Protocol (RAP) Protocol Data Unit (PDU), determining, at least in part, a signaling radio bearer or data radio bearer associated with a remote UE based on the RAP header of the received RAP PDU, removing the RAP header, and transmitting a new Radio Packet Data Convergence Protocol (PDCP) PDU of the RAP PDU to the upper layer.

[0281] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, process 2100 includes determining a remote UE index associated with a connection to a remote UE, determining a relay channel for the connection to the remote UE corresponding to a radio access bearer of the remote UE, determining a radio access relay channel corresponding to the relay channel for the connection to the remote UE, generating a relay adaptation protocol (RAP) header including at least one of a remote UE index, a relay channel identifier or a path identifier for the relay channel for the connection to the remote UE, and transmitting a RAP layer protocol data unit (PDU) with the RAP header on the radio access relay channel.

[0282] although Figure 21 An example box of process 2100 is shown, but in some respects, process 2100 may include more than Figure 21 The boxes depicted may be more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or optionally, two or more boxes in process 2100 may be executed in parallel.

[0283] Figure 22 This is a diagram illustrating an example procedure 2200 performed, for example, by a remote UE according to this disclosure. Example procedure 2200 is an example of a remote UE (e.g., UE 120, remote UE 305, remote UE 405) performing operations associated with a relay adaptation protocol layer configuration.

[0284] like Figure 22 As shown, in some aspects, process 2200 may include establishing a connection with a relay UE (block 2210). For example, as described above, a remote UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may establish a connection with a relay UE.

[0285] like Figure 22As further illustrated, in some aspects, process 2200 may include configuring one or more relay channels for the connection at least in part based on configuration information, wherein the configuration information includes at least one of the following: remote UE connection identifier information associated with the connection between the remote UE and the relay UE for relay service, or configuration of one or more relay channels for the connection between the remote UE and the relay UE (block 2220). For example, as described above, a remote UE (e.g., using antenna 252, demodulator 254, MIMO detector 256, receiver processor 258, controller / processor 280, etc.) may configure one or more relay channels for the connection at least in part based on configuration information, wherein the configuration information includes at least one of the following: remote UE connection identifier information associated with the connection between the remote UE and the relay UE for relay service, or configuration of one or more relay channels for the connection between the remote UE and the relay UE.

[0286] like Figure 22 As further illustrated, in some aspects, process 2200 may include communication with a network entity via a relay UE based at least in part on configuration information (block 2230). For example, as described above, a remote UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may communicate with a network entity via a relay UE based at least in part on configuration information.

[0287] Process 2200 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or in conjunction with one or more other processes described elsewhere herein.

[0288] In the first aspect, the relay service is identified by a relay service code, and the establishment of a connection is based at least in part on security settings corresponding to the relay service code.

[0289] In a second aspect, either alone or in combination with the first aspect, process 2200 includes configuring, at least in part, to receive a set of one or more remote UE private radio bearers or one or more remote UE signaling radio bearers for connection using security settings based on a relay service code.

[0290] In the third aspect, either alone or in combination with one or more of the first and second aspects, a relay channel in one or more relay channels is associated with a plurality of radio access signaling radio bearers, and wherein the relay adaptation protocol layer of the remote UE indicates an index of the selected radio access signaling radio bearer for communication via the relay channel.

[0291] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the remote UE is associated with a radio access inactive state, a radio access idle state, or a state outside coverage, and the method further includes receiving information indicating the remote UE, the configuration of the radio access data radio bearer, and the trunk channel configuration, in conjunction with the configuration of the radio access data radio bearer, and the trunk channel configuration including the trunk channel identifiers of one or more trunk channels of the connection.

[0292] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 2200 includes sending information indicating a connection index to the relay UE.

[0293] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 2200 includes receiving information indicating an update of the remote UE index in conjunction with the connection identifier update process.

[0294] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 2200 includes sending a link identifier update request to the relay UE at least in part based on a timer, and performing a connection identifier update process with the relay UE at least in part based on the link identifier update request.

[0295] although Figure 22 An example box of process 2200 is shown, but in some respects, process 2200 may include more than Figure 22 The boxes depicted may include more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or optionally, two or more boxes in process 2200 may be executed in parallel.

[0296] The following provides an overview of some aspects of this disclosure:

[0297] Aspect 1: A method of wireless communication performed by a relay user equipment (UE), comprising: establishing a connection with a remote UE for relay communication; receiving configuration information from a network entity, the configuration information including at least one of: remote UE connection identifier information associated with a connection between the remote UE and the relay UE for relay service, including configuration of relay channel identifier information, wherein the configuration is for the connection between the remote UE and the relay UE and a link with the network entity, wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity; configuring one or more relay channels of the connection and one or more relay channels of the link with the network entity, at least in part based on the configuration information; and relaying communication between the remote UE and the network entity, at least in part based on the configuration information.

[0298] Aspect 2: According to the method of aspect 1, the connection is via a sidelink signaling interface.

[0299] Aspect 3: According to the method of aspect 1, at least a portion of the configuration information is used by the relay adaptation protocol (RAP) layer of the relay UE to relay the communication.

[0300] Aspect 4: According to the method described in aspect 1, the relay channel mapping uses one of a one-to-one basis or an N-to-1 basis, where N is variable.

[0301] Aspect 5: The method according to aspect 1, wherein the connection is at least one of the following: sidelink unicast link establishment using a sidelink signaling interface, Bluetooth connection, WiFi connection, or device-to-device connection.

[0302] Aspect 6: According to the method of aspect 1, wherein the remote UE connection identifier information corresponds to the remote UE index, wherein the connection is uniquely associated with the assigned remote UE connection identifier identified by the remote UE connection identifier information.

[0303] Aspect 7: According to the method of aspect 6, wherein for a sidelink unicast link, the remote UE connection identifier is based at least in part on the source Layer 2 identifier and the target Layer 2 identifier associated with the sidelink unicast link.

[0304] Aspect 8: The method according to aspect 1 further includes: allocating a unique index associated with the connection, wherein the unique index is an allocated remote UE connection identifier identified by remote UE connection identifier information; and sending information indicating the unique index to a network entity via a radio resource control message.

[0305] Aspect 9: According to the method of aspect 8, a set of one or more sidelink dedicated radio bearers or signaling radio bearers uses the same security settings at least in part based on the connection associated with the relay service.

[0306] Aspect 10: The method according to aspect 1, wherein the connection supports one or more of the following: multiple relay channels for one or more radio access bearers for a remote UE, multiple radio access protocol data element sessions on a single link, or multiple relay channels having the same or different quality of service configurations.

[0307] Aspect 11: The method according to aspect 1, wherein communication is relayed via a plurality of radio access relay channels associated with a plurality of remote UEs.

[0308] Aspect 12: According to the method of aspect 11, the radio access relay channel is mapped to a plurality of relay channels for connection.

[0309] Aspect 13: The method according to aspect 1, wherein the relay communication is based at least in part on a Relay Adaptation Protocol (RAP) header, wherein the RAP header indicates one or more of the following: an identifier of a remote UE based at least in part on a unique identifier of a connection, one or more relay channels for a connection associated with a radio access bearer associated with a remote UE, or a path identifier for data routing associated with a relay service.

[0310] Aspect 14: The method according to aspect 1, wherein the relay communication is based at least in part on a radio access data radio bearer configured to satisfy the quality of service associated with the relay service for a protocol data unit session.

[0311] Aspect 15: According to the method of aspect 1, wherein the connected one or more relay channels correspond to one or more radio access signaling radio bearers or one or more radio access data radio bearers.

[0312] Aspect 16: The method according to aspect 1, wherein the configuration information indicates that multiple radio access signaling radio bearers are multiplexed onto a single connected trunk channel based at least in part on one or more indices of multiple radio access signaling radio bearers.

[0313] Aspect 17: The method according to aspect 1, wherein the configuration information indicates a radio access relay channel configured for multiplexing multiple radio access signaling radio bearers associated with a remote UE.

[0314] Aspect 18: According to the method of aspect 1, the relay is performed by the relay adaptation protocol (RAP) layer of the relay UE, which is at least partially based on the backhaul adaptation protocol (BAP) associated with integrated access backhaul technology.

[0315] Aspect 19: The method according to aspect 18 further includes: exchanging one or more relay channel identifiers with a remote UE when configuring a connection for a relay service.

[0316] Aspect 20: The method according to aspect 19 further includes: maintaining a mapping between one or more relay channel identifiers of the connection and one or more logical channel identifiers assigned to one or more logical channels associated with the one or more relay channels of the connection.

[0317] Aspect 21: The method according to aspect 1, wherein the remote UE is in a radio access connection mode, and wherein receiving configuration information is triggered at least in part based on a handover of the remote UE from a radio access connection to a relay connection via a relay UE, and wherein the configuration information includes a bearer configuration associated with one or more radio access data radio bearers or signaling radio bearers.

[0318] Aspect 22: The method according to aspect 21 further includes: receiving information indicating a remote UE connection identifier from a remote UE; associating the remote UE connection identifier with a connection between the remote UE and a relay UE; and sending the remote UE connection identifier to a network entity via a radio resource control message.

[0319] Aspect 23: The method according to aspect 1 further includes: configuring privacy settings for the relay service; determining an identifier to be updated for connection; performing a connection identifier update with the remote UE; updating one or more radio access relay channel identifiers and an assigned remote UE index based at least in part on the successful result of the connection identifier update; and sending a response message to a network entity indicating the successful result of the connection identifier update.

[0320] Aspect 24: The method according to aspect 23, wherein determining the identifier for updating the connection is based at least in part on at least one of: receiving from a network entity an indication of updating at least one of a source Layer 2 identifier corresponding to a sidelink unicast link, a destination Layer 2 identifier corresponding to a sidelink unicast link, one or more radio access relay channel identifiers, or an assigned remote UE index, a configuration for connection maintenance, or receiving a link identifier update request from a remote UE.

[0321] Aspect 25: The method according to aspect 24 further includes: sending a notification to the network entity before initiating a connection identifier update.

[0322] Aspect 26: The method according to aspect 1 further includes: releasing the connection; and sending an indication to the network entity that the connection has been released.

[0323] Aspect 27: A method of wireless communication performed by a network entity, comprising: sending configuration information to a relay user equipment (UE), the configuration information including at least one of: remote UE connection identifier information for relay service associated with a connection between a remote UE and a relay UE, including configuration of relay channel identifier information, wherein the configuration is for the connection between the remote UE and the relay UE and a link with the network entity, wherein the configuration indicates a relay channel mapping between one or more relay channels of the connection and one or more relay channels of the link with the network entity; and communicating with the remote UE via the relay UE at least in part based on the configuration information.

[0324] Aspect 28: The method according to aspect 27, wherein the configuration information is used for the relay adaptation protocol (RAP) layer of the relay UE.

[0325] Aspect 29: The method according to aspect 27 further includes: configuring a radio access data radio bearer or protocol data unit session to meet the quality of service associated with the relay service.

[0326] Aspect 30: The method according to aspect 27, wherein the configuration information indicates that one or more relay channels connected correspond to one or more radio access signaling radio bearers or one or more radio access data radio bearers.

[0327] Aspect 31: The method according to aspect 27, wherein the remote UE is associated with a radio access inactive state, a radio access idle state, or an out-of-coverage state, and wherein sending configuration information further includes: sending configuration information at least in part based on an indication received by the relay UE regarding the setting of a connection for relaying with the remote UE, wherein the configuration information configures one or more relay channels of a connection associated with one or more signaling radio bearers of the remote UE.

[0328] Aspect 32: The method according to aspect 31, wherein the method further comprises: sending information via a relay UE to a remote UE, the information indicating a relay channel identifier of one or more relay channels connected to the remote UE.

[0329] Aspect 33: The method according to aspect 27, wherein the remote UE is associated with a radio access inactive state, a radio access idle state, or an out-of-coverage state, and wherein sending configuration information further includes: sending configuration information based at least in part on a successful configuration of a connection with the remote UE, wherein the configuration information configures one or more relay channels of a connection associated with one or more remote UE data radio bearers.

[0330] Aspect 34: The method according to aspect 33 further includes: sending to the remote UE information indicating a remote UE index, one or more remote UE data radio bearers, and one or more relay channel identifiers associated with one or more connected relay channels.

[0331] Aspect 35: The method according to aspect 33 further includes: receiving information indicating one or more relay channel identifiers associated with the configuration connection.

[0332] Aspect 36: The method according to aspect 27, wherein the remote UE is in a radio access connection mode, and wherein sending configuration information further includes: sending configuration information at least in part based on the remote UE’s handover from radio access connection to a relay connection via a connection, wherein the configuration information includes bearer configuration associated with one or more remote UE data radio bearers or remote UE signaling radio bearers.

[0333] Aspect 37: The method according to aspect 36 further includes: sending information indicating a remote UE index associated with the remote UE to the remote UE in the handover command.

[0334] Aspect 38: The method according to aspect 36 further includes: receiving a connection index determined by the relay UE from the relay UE via a radio resource control message.

[0335] Aspect 39: The method of aspect 27 further includes: determining at least one of a source Layer 2 (L2) identifier or a target L2 identifier for updating the connection, wherein the connection is a sidelink unicast link; triggering a connection identifier update for the relay UE and the remote UE, at least in part based on determining at least one of the source L2 identifier or the target L2 identifier for updating; and receiving a response message from the relay UE indicating a successful result of the connection identifier update.

[0336] Aspect 40: The method according to aspect 39, wherein triggering a connection identifier update is based at least in part on an indication to update at least one of the following: a source L2 identifier, a destination L2 identifier, one or more radio access relay channel identifiers, or an assigned remote UE index.

[0337] Aspect 41: The method of aspect 40, wherein triggering a connection identifier update is based at least in part on a timer associated with the connection identifier.

[0338] Aspect 42: The method according to aspect 40 further includes: sending information indicating the assigned remote UE index to the remote UE.

[0339] Aspect 43: The method according to aspect 27 further includes: receiving a notification from a relay UE indicating that a connection identifier update procedure will be performed to update at least one of a source Layer 2 (L2) identifier or a target L2 identifier of the connection, wherein the update of the source L2 identifier or the target L2 identifier of the connection is triggered by the relay UE at least in part based on a timer.

[0340] Aspect 44: The method according to aspect 43 further includes sending to the relay UE information indicating at least one of an updated radio access relay channel identifier or an assigned remote UE index associated with the connection.

[0341] Aspect 45: The method according to aspect 27 further includes: sending a release indication for releasing the connection, wherein the release indication is based at least in part on at least one of the following: a handover from a remote UE to a radio access connection, a load associated with a relay UE, or a quality of service requirement.

[0342] Aspect 46: The method according to aspect 27 further includes: receiving a Relay Adaptation Protocol (RAP) Protocol Data Unit (PDU); determining, at least in part, a signaling radio bearer or data radio bearer associated with a remote UE based on the RAP header of the received RAP PDU; removing the RAP header; and transmitting a new Radio Packet Data Convergence Protocol (PDCP) PDU of the RAP PDU to an upper layer.

[0343] Aspect 47: The method according to aspect 27 further includes: determining a remote UE index associated with the connection to the remote UE; determining a relay channel for the connection to the remote UE corresponding to a radio access bearer of the remote UE, and determining a radio access relay channel corresponding to the relay channel for the connection to the remote UE; generating a relay adaptation protocol (RAP) header, which includes at least one of a remote UE index, a relay channel identifier or a path identifier for the relay channel for the connection to the remote UE; and transmitting a RAP layer protocol data unit (PDU) having the RAP header on the radio access relay channel.

[0344] Aspect 48: A wireless communication method performed by a remote user equipment (UE), comprising: establishing a connection with a relay UE; configuring one or more relay channels for the connection based at least in part on configuration information, wherein the configuration information includes at least one of: remote UE connection identifier information associated with the connection between the remote UE and the relay UE for relay service, or configuration of one or more relay channels for the connection between the remote UE and the relay UE; and communicating with a network entity via the relay UE based at least in part on the configuration information.

[0345] Aspect 49: The method according to aspect 48, wherein the relay service is identified by a relay service code, and wherein the establishment of the connection is based at least in part on security settings corresponding to the relay service code.

[0346] Aspect 50: The method according to aspect 49 further includes: receiving, at least in part, a configuration of one or more remote UE private radio bearers or one or more remote UE signaling radio bearers for connection, using security settings based on a relay service code.

[0347] Aspect 51: The method according to aspect 48, wherein a relay channel in one or more relay channels is associated with a plurality of radio access signaling radio bearers, and wherein the relay adaptation protocol layer of the remote UE indicates an index of the radio access signaling radio bearer for communication via the relay channel.

[0348] Aspect 52: The method according to aspect 48, wherein the remote UE is associated with a radio access inactive state, a radio access idle state, or an out-of-coverage state, and wherein the method further comprises: receiving information indicating a remote UE index, a configuration of the radio access data radio bearer, and a relay channel configuration, the relay channel configuration including a relay channel identifier of one or more connected relay channels, in conjunction with a configured radio access data radio bearer.

[0349] Aspect 53: According to the method of aspect 52, the method further includes: sending information indicating the connection index of the connection to the relay UE.

[0350] Aspect 54: The method according to aspect 48 further includes: receiving information indicating an updated remote UE index for a remote UE in conjunction with the connection identifier update process.

[0351] Aspect 55: The method according to aspect 48 further includes: sending a link identifier update request to the relay UE at least in part based on a timer; and performing a connection identifier update procedure with the relay UE at least in part based on the link identifier update request.

[0352] Aspect 56: An apparatus for wireless communication at a device, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods of aspects 1-55.

[0353] Aspect 57: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the methods of one or more aspects of aspects 1-55.

[0354] Aspect 58: An apparatus for wireless communication, comprising at least one module for performing the methods of one or more aspects of aspects 1-55.

[0355] Aspect 59: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform methods of one or more aspects of aspects 1-55.

[0356] Aspect 60: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions, when executed by one or more processors of a device, causing the device to perform one or more of the methods of aspects 1-55.

[0357] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit these aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from practice in these aspects.

[0358] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, and / or functions. As used herein, a processor is implemented in hardware and / or a combination of hardware and software. Clearly, the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, this document describes the operation and behavior of systems and / or methods without reference to specific software code, and it should be understood that software and hardware can be designed to implement systems and / or methods, at least in part, based on the descriptions herein.

[0359] As used in this article, depending on the context, a threshold can refer to a value that is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0360] Even if a particular combination of features is stated in the claims and / or disclosed in the specification, such combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically stated in the claims and / or not disclosed in the specification. Although each of the following dependent claims may depend directly on only one claim, the disclosure of aspects includes combinations of each dependent claim with each other claim in the claim set. As used herein, the phrase “at least one of a series of items” refers to any combination of those items, including single members. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and cccc, or any other order of a, b, and c).

[0361] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the articles “a” and “one” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items associated with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more.” If referring to only one item, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “have,” “possess,” “having…,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless explicitly stated otherwise. Furthermore, as used herein, the term “or” is inclusive in a series of uses and may be used interchangeably with “and / or” unless explicitly stated otherwise (e.g., if used in conjunction with “any” or “only one”).

Claims

1. An apparatus for relaying wireless communication at a user equipment (UE), comprising: Memory; and One or more processors, coupled to the memory, are configured to: Establish a connection with a remote UE for relay communication; Receive configuration information from a network entity, the configuration information including: Remote UE connection identifier information associated with the connection between the remote UE used for relay service and the relay UE, and The configuration includes relay channel identifier information, wherein the configuration is used for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates relay channel mapping, wherein the relay channel mapping is between one or more relay channels of the connection and one or more relay channels of the link with the network entity, wherein the configuration is at least partially based on the Relay Adaptation Protocol (RAP) layer, the RAP layer supporting radio bearer mapping between one or more radio bearers associated with the remote UE and the one or more relay channels; Configure one or more relay channels for the connection and one or more relay channels for the link with the network entity, at least in part based on the configuration information; and The communication between the remote UE and the network entity is relayed at least in part based on the configuration information.

2. The apparatus of claim 1, wherein at least a portion of the configuration information is used by the RAP layer to relay the communication.

3. The apparatus of claim 1, wherein the relay channel mapping uses one of the following: One-on-one foundation, or The N-to-1 basis is used, where N is variable.

4. The apparatus of claim 1, wherein the connection is at least one of the following: Sidelink unicast link establishment using the sidelink signaling interface Bluetooth connection, WiFi connection, or Device-to-device connection.

5. The apparatus of claim 1, wherein the remote UE connection identifier information corresponds to a remote UE index, wherein the connection is uniquely associated with an assigned remote UE connection identifier identified by the remote UE connection identifier information.

6. The apparatus of claim 1, wherein the one or more processors are further configured to: Assign a unique index associated with the connection, wherein the unique index is the assigned remote UE connection identifier identified by the remote UE connection identifier information; and Information indicating the unique index is sent to the network entity via radio resource control messages.

7. The apparatus of claim 6, wherein the one or more radio bearers comprise a collection of one or more sidelink-dedicated radio bearers or signaling radio bearers, wherein the collection of one or more sidelink-dedicated radio bearers or signaling radio bearers uses the same security settings, at least in part based on the connection associated with the relay service.

8. The apparatus of claim 1, wherein the communication is relayed via a plurality of radio access relay channels mapped to a plurality of relay channels associated with a plurality of remote UEs.

9. The apparatus of claim 1, wherein relaying the communication is at least partially based on a RAP header, wherein the RAP header indicates one or more of the following: The identifier of the remote UE is based at least in part on the unique identifier of the connection. One or more relay channels associated with the one or more radio bearers associated with the remote UE, or The path identifier of the data route associated with the relay service.

10. The apparatus of claim 1, wherein the one or more radio bearers include a radio access data radio bearer of the remote UE, wherein relaying the communication is at least in part based on the radio access data radio bearer of a remote UE protocol data unit session configured to satisfy the quality of service associated with the relay service.

11. The apparatus of claim 1, wherein the one or more radio bearers include one or more radio access signaling radio bearers or one or more radio access data radio bearers of the remote UE, wherein the one or more relay channels connected correspond to the one or more radio access signaling radio bearers or the one or more radio access data radio bearers of the remote UE.

12. The apparatus of claim 1, wherein the one or more radio bearers comprise a plurality of remote UE radio access signaling radio bearers, wherein the configuration information indicates, at least in part, that the plurality of remote UE radio access signaling radio bearers are multiplexed onto a single relay channel for the connection based on one or more indices of the plurality of remote UE radio access signaling radio bearers.

13. The apparatus of claim 1, wherein the one or more radio bearers include a plurality of radio access signaling radio bearers associated with the remote UE, wherein the configuration information indicates a radio access relay channel configured to multiplex the plurality of radio access signaling radio bearers associated with the remote UE.

14. The apparatus of claim 1, wherein the relay is performed by the RAP layer at least in part based on the Backhaul Adaptation Protocol (BAP) associated with Integrated Access Backhaul Technology.

15. The apparatus of claim 14, wherein the one or more processors are further configured to: When configuring the connection for the relay service, one or more relay channel identifiers are exchanged with the remote UE for the connection.

16. The apparatus of claim 15, wherein the one or more processors are further configured to: Receive information indicating the remote UE connection identifier from the remote UE; Associate the remote UE connection identifier with the connection between the remote UE and the relay UE; and The remote UE connection identifier is sent to the network entity via a radio resource control message.

17. The apparatus of claim 1, wherein the one or more processors are further configured to: Configure privacy settings for the relay service; Determine and update the identifier used for the connection; Perform a connection identifier update with the remote UE; Based at least in part on the successful result of the connection identifier update, update one or more radio access relay channel identifiers and the assigned remote UE index; as well as Send a message to the network entity indicating a successful result of the connection identifier update, wherein the connection identifier update indication includes, at least in part, an updated remote UE index assigned to the connection based on the connection identifier update.

18. The apparatus of claim 1, wherein the one or more processors are further configured to: Release the connection; and Send an indication to the network entity that the connection has been released.

19. An apparatus for wireless communication at a network entity, comprising: Memory; and One or more processors, coupled to the memory, are configured to: Send configuration information to the relay user equipment (UE), the configuration information including: Remote UE connection identifier information associated with the connection between the remote UE used for relay service and the relay UE, and The configuration includes relay channel identifier information, wherein the configuration is used for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates relay channel mapping, wherein the relay channel mapping is between one or more relay channels of the connection and one or more relay channels of the link with the network entity, wherein the configuration is at least partially based on the Relay Adaptation Protocol (RAP) layer, the RAP layer supporting radio bearer mapping between one or more radio bearers associated with the remote UE and the one or more relay channels; as well as The relay UE communicates with the remote UE, at least in part, based on the configuration information.

20. The apparatus of claim 19, wherein the one or more radio bearers include one or more radio access signaling radio bearers or one or more radio access data radio bearers of the remote UE, wherein the configuration information indicates that one or more relay channels of the connection correspond to the one or more radio access signaling radio bearers or the one or more radio access data radio bearers of the remote UE.

21. The apparatus of claim 19, wherein the remote UE is associated with a radio access inactive state, a radio access idle state, or an out-of-coverage state, wherein the one or more radio bearers include one or more remote UE signaling radio bearers or remote UE data radio bearers, and wherein, in order to transmit the configuration information, the one or more processors are configured to: The configuration information is sent at least in part based on an instruction received by the relay UE regarding a connection configured for relaying with the remote UE; or The configuration information is sent at least in part based on the successful configuration of the connection with the remote UE, and The one or more processors are further configured to: Send to the remote UE information indicating the remote UE index, the one or more remote UE signaling radio bearers or remote UE data radio bearers, and one or more relay channel identifiers associated with the one or more relay channels of the connection.

22. The apparatus of claim 19, wherein the one or more radio bearers include one or more remote UE data radio bearers or remote UE signaling radio bearers, wherein the remote UE is in a radio access connection mode, and wherein, in order to transmit the configuration information, the one or more processors are further configured to: The configuration information is transmitted at least in part based on the handover of the remote UE from radio access to a relay connection via the connection, wherein the configuration information includes bearer configurations associated with the data radio bearer or signaling radio bearer of the one or more remote UEs.

23. The apparatus of claim 22, wherein the one or more processors are further configured to: The handover command sends information indicating the remote UE index associated with the remote UE to the remote UE.

24. The apparatus of claim 22, wherein the one or more processors are further configured to: The connection index determined by the relay UE is received from the relay UE via a radio resource control message.

25. The apparatus of claim 19, wherein the one or more processors are further configured to: The relay UE receives a notification indicating that the connection identifier update process was successful, wherein the notification includes a new remote UE index assigned to the connection.

26. The apparatus of claim 19, wherein the one or more processors are further configured to: Send an instruction to release the connection, wherein the release instruction is based at least in part on at least one of the following: The switching from remote UE to radio access connection The load associated with the relay UE, or Service quality requirements.

27. The apparatus of claim 19, wherein the one or more processors are further configured to: Receive RAP protocol data unit (PDU); The signaling radio bearer or data radio bearer associated with the remote UE is determined at least in part based on the RAP header of the received RAP PDU; Remove the RAP header; as well as The new radio packet data convergence protocol PDCP PDU of the RAP PDU is transmitted to the upper layer.

28. The apparatus of claim 19, wherein the one or more processors are further configured to: Determine the remote UE index associated with the connection to the remote UE; Determine the relay channel for the connection of the remote UE corresponding to the radio access bearer of the remote UE. Determine the radio access relay channel corresponding to the relay channel used for the connection of the remote UE; Generate a RAP header, the RAP header including at least one of the remote UE index, a relay channel identifier or a path identifier for the relay channel used for the connection of the remote UE; as well as Transmit RAP layer protocol data unit (PDU) with the RAP header on the radio access relay channel.

29. An apparatus for wireless communication at a remote user equipment (UE), comprising: Memory; as well as One or more processors, coupled to the memory, are configured to: Establish a connection with the relay UE; One or more relay channels for the connection are configured at least in part based on configuration information, wherein the configuration information includes: Remote UE connection identifier information associated with the connection between the remote UE used for relay service and the relay UE, and Configuration of one or more relay channels for a connection between the remote UE and the relay UE, wherein the configuration indicates relay channel mapping, wherein the relay channel mapping is between one or more relay channels of the connection and one or more relay channels of the link between the relay UE and a network entity, wherein the configuration is at least partially based on the Relay Adaptation Protocol (RAP) layer, the RAP layer supporting radio bearer mapping between one or more radio bearers associated with the remote UE and the one or more relay channels; as well as The relay UE communicates with the network entity, at least in part, based on the configuration information.

30. The apparatus of claim 29, wherein the relay service is identified by a relay service code, and wherein the establishment of the connection is based at least in part on security settings corresponding to the relay service code.

31. The apparatus of claim 29, wherein the one or more radio bearers include a plurality of radio access signaling radio bearers, wherein a relay channel in the one or more relay channels is associated with a plurality of radio access signaling radio bearers, and wherein the relay adaptation protocol layer of the remote UE indicates an index of a selected radio access signaling radio bearer of the plurality of radio access signaling radio bearers for communication via the relay channel.

32. The apparatus of claim 29, wherein the one or more radio bearers include a radio access signaling radio bearer or a radio access data radio bearer, wherein the remote UE is associated with a radio access inactive state, a radio access idle state, or an out-of-coverage state, and wherein the one or more processors are further configured to: In conjunction with configuring the radio access signaling radio bearer or radio access data radio bearer, information indicating the remote UE index, configuration of the radio access signaling radio bearer or radio access data radio bearer, and trunk channel configuration of the remote UE is received, wherein the trunk channel configuration includes a trunk channel identifier of one or more trunk channels in the connection.

33. The apparatus of claim 32, wherein the one or more processors are further configured to: Send information indicating the connection index to the relay UE.

34. The apparatus of claim 29, wherein the one or more processors are further configured to: In conjunction with the connection identifier update process, information indicating the update of the remote UE index is received.

35. The apparatus of claim 29, wherein the one or more processors are further configured to: Sending a link identifier update request to the relay UE, at least in part, based on a timer; and The connection identifier update process is performed with the relay UE at least in part based on the link identifier update request.

36. A method for wireless communication performed by a relay user equipment (UE), comprising: Establish a connection with a remote UE for relay communication; Receive configuration information from a network entity, the configuration information including: Remote UE connection identifier information associated with the connection between the remote UE used for relay service and the relay UE, and The configuration includes relay channel identifier information, wherein the configuration is used for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates relay channel mapping, wherein the relay channel mapping is between one or more relay channels of the connection and one or more relay channels of the link with the network entity, wherein the configuration is at least partially based on the Relay Adaptation Protocol (RAP) layer, the RAP layer supporting radio bearer mapping between one or more radio bearers associated with the remote UE and the one or more relay channels; Configure one or more relay channels for the connection and one or more relay channels for the link with the network entity, at least in part based on the configuration information; and The communication between the remote UE and the network entity is relayed at least in part based on the configuration information.

37. The method of claim 36, wherein at least a portion of the configuration information is used by the RAP layer to relay the communication.

38. The method of claim 36, wherein the relay channel mapping uses one of the following: One-on-one foundation, or The N-to-1 basis is used, where N is variable.

39. A method for wireless communication performed by a network entity, comprising: Send configuration information to the relay user equipment (UE), the configuration information including: Remote UE connection identifier information associated with the connection between the remote UE used for relay service and the relay UE, and The configuration includes relay channel identifier information, wherein the configuration is used for the connection between the remote UE and the relay UE and the link with the network entity, wherein the configuration indicates relay channel mapping, wherein the relay channel mapping is between one or more relay channels of the connection and one or more relay channels of the link with the network entity, wherein the configuration is at least partially based on the Relay Adaptation Protocol (RAP) layer, the RAP layer supporting radio bearer mapping between one or more radio bearers associated with the remote UE and the one or more relay channels; and The relay UE communicates with the remote UE, at least in part, based on the configuration information.

40. A method for wireless communication performed by a remote user equipment (UE), comprising: Establish a connection with the relay UE; One or more relay channels for the connection are configured at least in part based on configuration information, wherein the configuration information includes: Remote UE connection identifier information associated with the connection between the remote UE used for relay service and the relay UE, and Configuration of one or more relay channels for a connection between the remote UE and the relay UE, wherein the configuration indicates relay channel mapping, wherein the relay channel mapping is between one or more relay channels of the connection and one or more relay channels of the link between the relay UE and a network entity, wherein the configuration is at least partially based on the Relay Adaptation Protocol (RAP) layer, the RAP layer supporting radio bearer mapping between one or more radio bearers associated with the remote UE and the one or more relay channels; as well as The relay UE communicates with the network entity, at least in part, based on the configuration information.

41. An apparatus for wireless communication, comprising at least one module for performing the method of any one of claims 36 to 40.

Images