Notifying network node of signaling of user equipment-to-user equipment link between remote user equipment and relay user equipment

Abstract

A user equipment (UE) transmits UE-UE link information indicating a UE-to-UE (UE-UE) link type between a remote UE and a relay UE, the first UE being one of the remote UE or the relay UE. The UE also receives a configuration corresponding to the transmitted UE-UE link information.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to wireless communications utilizing multipath relaying. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0004] A simplified overview of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0005] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include: a memory; and at least one processor, the at least one processor coupled to the memory and configured to: send UE-UE link information indicating a user equipment (UE) to UE (UE-UE) link type between a remote user equipment (UE) and a relay UE, the first UE being one of the remote UE or the relay UE; and receive a configuration corresponding to the sent UE-UE link information.

[0006] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0008] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0009] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0010] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0011] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0012] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0013] Figure 4A is a diagram illustrating a first configuration of multipath relay.

[0014] Figure 4B is a diagram illustrating a second configuration of multipath relay.

[0015] Figure 5A is a diagram illustrating a control plane for a layer 2 UE-to-network relay protocol stack.

[0016] Figure 5B is a diagram illustrating a user plane for a layer 2 UE to network relay protocol stack.

[0017] Fig. 6A is a diagram illustrating a first user plane architecture configuration.

[0018] Figure 6B is a diagram illustrating a second user plane architecture configuration.

[0019] Figure 7 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure.

[0020] Figure 8is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure.

[0021] Fig. 9 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure.

[0022] Fig.10 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure.

[0023] Fig.11 is a flow chart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure.

[0024] Fig.12 is a flow chart illustrating a method of wireless communication at a network node according to various aspects of the present disclosure.

[0025] Fig.13 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0026] Fig.14 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0027] Multipath (MP) relay enables a UE (e.g., a remote UE) to connect to the same network node via multiple paths (e.g., via a direct path to the network node and an indirect path from the relay UE to the network node). By doing so, the reliability and throughput of the connection to the network node can be enhanced (e.g., by switching between multiple paths or utilizing multiple paths simultaneously). However, the effectiveness of MP relay depends on the way the UE is configured, because the UE can be configured differently according to the link type by which the UE is connected to another UE. Various aspects presented herein provide methods and apparatus for a remote UE or a relay UE to notify a network node of a UE-UE link type being utilized between the remote UE and the relay UE. Using the UE-UE link type, the network node determines a configuration corresponding to the UE-UE link type for the remote UE and the relay UE, and provides the determined configuration to the remote UE and the relay UE. The remote UE and the relay UE apply the configuration received from the network node. In some aspects, the UE may send UE-UE link information indicating the UE-UE link type between the remote UE and the relay UE, the first UE being one of the remote UE or the relay UE. The UE may also receive a configuration corresponding to the transmitted UE-UE link information.The method and apparatus advantageously enable a network node to correctly configure a remote UE and a relay UE for MP relaying, thereby enhancing the reliability and throughput of the connection between the UE and the network node.

[0028] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0029] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0031] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0032] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The various techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0033] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0034] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0035] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0036] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0037] Each of these units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0038] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0039] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by 3GPP. In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0040] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0041] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0042] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0043] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0044] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0045] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0046] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, e.g., in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0047] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0048] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0049] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" or the like is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0050] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the optimal receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0051] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0052] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the positioning of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0053] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term "UE" may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0054] Reference again Figure 1 In some aspects, the UE 104 may be configured to include a UE-to-UE (UE-UE) link information determination component 198, which is configured to send UE-UE link information indicating a UE-UE link type between a remote UE and a relay UE, the first UE being one of the remote UE or the relay UE. The UE-UE link information determination component 198 may also be configured to receive a configuration corresponding to the sent UE-UE link information. In some aspects, the base station 102 may be configured to include a UE configuration determination component 199, which is configured to receive UE-UE link information indicating a UE-UE link type between a remote UE and a relay UE. The UE configuration determination component 199 may also be configured to send a configuration corresponding to the received UE-UE link information to the remote UE and the relay UE. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0055] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2 to 61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5GNR frame structure as TDD.

[0056] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled using 1 / SCS.

[0057]

[0058] Table 1: Parameter set, SCS and CP

[0059] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0060] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0061] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0062] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at larger and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

[0063] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0064] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may be used to carry, among other things, buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0065] Figure 3 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 functionality and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0066] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0067] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be merged into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to a controller / processor 359, which implements layer 3 functionality and layer 2 functionality.

[0068] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0069] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0070] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via corresponding transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0071] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0072] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0073] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform the Figure 1 The UE configuration determination component 199 combines various aspects.

[0074] MP relay enables a UE to connect to the same network node via multiple paths. By doing so, the reliability and throughput of the connection to the network node can be enhanced (eg, by switching between multiple paths or utilizing multiple paths simultaneously). Figure 4A and Figure 4B Various configurations of MP relay are illustrated. In particular, Figure 4A A first configuration 400 of MP relay is shown, where a remote UE 402a is connected to the same network node 404a using a direct path and an indirect path via a layer 2 (L2) UE to network relay. In this example, the remote UE 402a is connected to the network node 404a via a direct path using a UE-UTRAN (Uu) interface and is indirectly connected to the network node 404a via a relay UE 406a. Figure 4A As shown, remote UE 402a is connected to relay UE 406a via a sidelink interface (eg, PC5), and relay UE 406a is connected to network node 404a via a Uu interface.

[0075] Figure 4B A second configuration 410 of MP relay is shown, where a remote UE 402b is connected to the same network node 404b using a direct path and an indirect path via another UE (where UE-UE interconnection is assumed to be ideal). In this example, the remote UE 402b is connected to the network node 404b via a direct path using a Uu interface and is indirectly connected to the network node 404b via a relay UE 406b. Figure 4B As shown, remote UE 402b is connected to relay UE 406a via an ideal link (e.g., a link outside the scope of (or not defined by) 3GPP), and relay UE 406b is connected to network node 404b via a Uu interface. The relationship between remote UE 402b and relay UE 406b may be preconfigured or static, and how the relationship is preconfigured or static is outside the scope of 3GPP.

[0076] Figure 5A and Figure 5B is a diagram illustrating a layer 2 UE to network relay protocol stack. In particular, Figure 5A is a diagram 500 illustrating a control plane for layer 2 UE to network relay. Figure 5B 5 is a diagram illustrating a user plane for layer 2 UE to network relay. Figure 5A and Figure 5B As shown, a PC5 adaptation layer 502 is introduced. It should be noted that a PC5-S / PC5-RRC connection (not shown) may exist between the remote UE and the relay UE.

[0077] The user plane architecture for the UE may vary depending on the UE-UE link type. For example, Fig. 6A is a diagram 600 illustrating a first user plane architecture configuration in which a remote UE is indirectly connected to a network node via a layer 2 UE-to-network relay, wherein the UE-UE connection is a sidelink connection (as described above with reference to Figure 4A described). Figure 6B is a diagram 610 illustrating a second user plane architecture configuration in which a remote UE is indirectly connected to a network node via another UE, wherein the UE-UE connection is an ideal link (as described above with reference to Figure 4B described).

[0078] like Fig. 6A As shown, the first user plane architecture includes an adaptation layer based on the Sidelink Relay Adaptation Protocol (SRAP), which is used to identify which remote UE, bearer and / or logical channel should be used. When the UE-UE connection is a side link layer, the network node configures the SRAP layer to enable communication via the Uu interface and the side link (e.g., PC5) interface. When the UE-UE connection is an ideal link, the network node does not provide and / or configure the SRAP adaptation layer for the remote UE and the relay UE via the Uu interface or the ideal link. Instead, the network node may assume that the relay UE serves one remote UE, and the bearer to logical channel mapping is a one-to-one mapping (i.e., one logical channel is mapped to and used to identify one radio bearer). Therefore, there are differences in network node behavior based on the UE-UE link type between the remote UE and the relay UE. However, there is no conventional mechanism for making the network node aware of the UE-UE link type.

[0079] Various aspects of the present disclosure provide methods and apparatus for a remote UE or a relay UE to notify a network node of a UE-UE link type being utilized between the remote UE and the relay UE. Using the UE-UE link type, the network node may determine a configuration corresponding to the UE-UE link type for the remote UE and the relay UE, and may provide the determined configuration to the remote UE and the relay UE. The remote UE and the relay UE may apply the configuration received from the network node. The methods and apparatus of various aspects of the present disclosure may advantageously enable the network node to correctly configure the remote UE and the relay UE for MP relaying, thereby enhancing the reliability and throughput of the connection between the UE and the network node.

[0080] In one aspect, the remote UE may use an RRC message to notify the network node of the UE-UE link type, and the network node may provide appropriate configuration to the remote UE and the relay UE. According to such an aspect, the remote UE may use a sidelink UE information NR message (e.g., SidelinkUEInformationNR) or a measurement report (also referred to as MeasurementReport), or a message 5 (MSG5) message (also referred to as msg5 or message 5) to notify the network node of the UE-UE link type information. The sidelink UE information NR message may be an RRC message. The MSG5 message may be an RRCSetupComplete message, an RRCResumeComplete message, or an RRCReconfigurationComplete message. Utilizing the MSG5 message allows the network node to provide appropriate configuration after an RRC establishment, RRC recovery, or handover procedure. UE-UE link type information may include at least one of the following information (for example, associated with the connection between the remote UE and the relay UE): side link connection information, PC5 interface information, 3GPP connection information, non-3GPP connection information, ideal link information, UE aggregation information, L2 relay connection information, WLAN connection information, Bluetooth connection information, etc.

[0081] The remote UE can determine the UE-UE link type based on the following information: whether the remote UE supports the corresponding UE-UE link type, whether the remote UE supports MP relay for the corresponding UE-UE link type, whether the remote UE is subscribed to and / or authorized for the corresponding UE-UE link type, whether the remote UE is subscribed to and / or authorized for MP relay for the corresponding UE-UE link type, whether the remote UE discovers or is pre-configured with the corresponding UE-UE link type, or uses the corresponding UE-UE link type to connect to a relay UE, etc.

[0082] When the remote UE detects that the UE-UE link is available for connection with the network node, the remote UE may include the UE-UE link type in an RRC message (e.g., a sidelink UE information NR message) or a measurement report. The remote UE may detect that the UE-UE link is available based on: the UE-UE link quality meets the criteria configured by the network for single path relay; the UE-UE link quality meets the criteria configured by the network for MP relay; the UE-UE link is available based on the UE specific implementation (e.g., the capabilities of the UE), etc.

[0083] On the other hand, the relay UE may use an RRC message to notify the network node of the UE-UE link type, and the network node may provide appropriate configuration to the remote UE and the relay UE. According to such an aspect, the relay UE may use a sidelink UE information NR message (e.g., SidelinkUEInformationNR), a measurement report (also referred to as MeasurementReport), or a MSG5 message (also referred to as msg5 or message 5) to notify the network node of the UE-UE link type information. The sidelink UE information NR message may be an RRC message. The MSG5 message may be an RRCSetupComplete message, an RRCResumeComplete message, or an RRCReconfigurationComplete message. Utilizing the MSG5 message allows the network node to provide appropriate configuration after an RRC establishment, RRC recovery, or handover procedure. UE-UE link type information may include at least one of the following information (for example, associated with the connection between the remote UE and the relay UE): side link connection information, PC5 interface information, 3GPP connection information, non-3GPP connection information, ideal link information, UE aggregation information, L2 relay connection information, WLAN connection information, Bluetooth connection information, etc.

[0084] The relay UE can determine the UE-UE link type based on the following information: whether the relay UE supports the corresponding UE-UE link type, whether the relay UE is subscribed to and / or authorized for the corresponding UE-UE link type, whether the relay UE discovers or is pre-configured with the corresponding UE-UE link type, or uses the corresponding UE-UE link type to connect to a remote UE, etc.

[0085] When the relay UE detects that the UE-UE link is available for connection with the network node, the relay UE may include the UE-UE link type in an RRC message (e.g., a sidelink UE information NR message) or a measurement (e.g., a measurement report). The relay UE may detect that the UE-UE link is available based on: the UE-UE link quality meets the criteria configured by the network, the UE-UE link is available based on the UE specific implementation (e.g., the UE's capabilities), etc.

[0086] In another aspect, a core network (CN) may use a Next Generation Application Protocol (NGAP) message to notify a network node of a UE-UE link type, and the network node may provide appropriate configurations to the remote UE and the relay UE. According to such an aspect, the CN may use a UE initial context (e.g., an authorized UE-UE link type) in NGAP to notify the network node of the UE-UE link type information. The CN may obtain the UE-UE link type information based on subscription information of the remote UE and / or the relay UE (e.g., whether the remote and / or the relay UE is subscribed to have a corresponding UE-UE link type) or notified by the remote UE and / or the relay UE to the CN via a non-access stratum (NAS) message.

[0087] Figure 7 700 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure. In particular, the call flow diagram 700 illustrates a remote UE 706 notifying a network node 704 of information associated with a UE-UE link 708 between the remote UE 706 and a relay UE 702. The relay UE 702 may be a UE that relays data from the network node 704 to another UE (e.g., a UE outside the coverage area of ​​the network node 704). The remote UE 706 may be a UE that receives data from another UE (e.g., the relay UE 702) and / or the network node 704 (depending on whether the remote UE 706 is within the coverage area of ​​the network node 704). Although various aspects are described with respect to the network node 704, these aspects may be performed by the network node in an aggregation and / or by one or more components of the network node 704 (e.g., such as the CU 110, the DU 130, and / or the RU 140). As shown in FIG. Figure 7 As shown, the remote UE 706 may determine UE-UE link information indicating a type of UE-UE link (e.g., UE-UE link 708) between the remote UE 706 and the relay UE 702 at 710. The UE-UE link information may indicate various information associated with the link between the relay UE 702 and the remote UE 706. For example, the UE-UE link information may indicate the type of UE-UE link established between the relay UE 702 and the remote UE 706.

[0088] In one aspect, the remote UE 706 may determine the UE-UE link type based on at least one of the following: whether the remote UE 706 supports the corresponding UE-UE link type; whether the remote UE 706 supports MP relay for the corresponding UE-UE link type; whether the remote UE 706 is subscribed to or authorized for the corresponding UE-UE link type; whether the remote UE 706 is subscribed to or authorized for MP relay for the corresponding UE-UE link type; or whether the remote UE 706 discovers, is pre-configured with, or is connected to the relay UE 702 via the corresponding UE-UE link type.

[0089] In one aspect, the remote UE 706 may detect the UE-UE link type available between the remote UE 706 and the relay UE 702 based on at least one of the following: whether the UE-UE link quality for the UE-UE link type meets the criteria configured for single-path relay; whether the UE-UE link quality for the UE-UE link type meets the criteria configured for MP relay; or whether the UE-UE link for the UE-UE link type is available based on the capabilities of the remote UE 706.

[0090] At 712, the remote UE 706 provides the UE-UE link information to the network node 704. In one aspect, the UE-UE link information is sent via an RRC message. In another aspect, the UE-UE link information is sent in a sidelink UE NR message, a measurement report, or a MSG5 message.

[0091] In one aspect, at 712 , the detected UE-UE link type is indicated in UE-UE link information sent to the network node 704 .

[0092] In one aspect, the UE-UE link information sent at 712 may include information associated with at least one of the following: a side link connection between the remote UE 706 and the relay UE 702, a PC5 interface, a 3GPP connection, a non-3GPP connection, an ideal link, a UE aggregation connection, an L2 relay connection, a WLAN connection, or a Bluetooth connection.

[0093] At 714, the network node 704 determines a configuration for the remote UE 706 and the relay UE 702 based on (e.g., corresponding to) the UE-UE link information received at 712. For example, the configuration may be according to the user plane architecture configuration described above with reference to 6A or the user plane architecture configuration described above with reference to 6B, depending on the UE-UE link type of the determined UE-UE link 708.

[0094] At 716, the network node may provide (e.g., send) the determined configuration for the relay UE 702 to the relay UE 702. At 718, the network node 704 may provide the determined configuration for the remote UE 706 to the remote UE 706. Note that the network node 704 may send the configuration for the relay UE 702 before, after, or simultaneously with sending the configuration for the remote UE 706.

[0095] Figure 8 800 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure. In particular, the call flow diagram 800 illustrates a relay UE 802 notifying a network node 804 of information associated with a UE-UE link 808 between a remote UE 806 and the relay UE 802. The relay UE 802 may be a UE that relays data from the network node 804 to another UE (e.g., a UE outside the coverage area of ​​the network node 804). The remote UE 806 may be a UE that receives data from another UE (e.g., the relay UE 802) and / or the network node 804 (depending on whether the remote UE 806 is within the coverage area of ​​the network node 804). Although various aspects are described with respect to the network node 804, these aspects may be performed by a network node in an aggregation and / or by one or more components of the network node 804 (e.g., such as the CU 110, the DU 130, and / or the RU 140). As shown in FIG. Figure 8 As shown, the relay UE 802 may determine, at 810, UE-UE link information indicating a type of a UE-UE link (e.g., UE-UE link 808) between the remote UE 806 and the relay UE 802. The UE-UE link information may indicate various information associated with a link between the relay UE 802 and the remote UE 806. For example, the UE-UE link information may indicate a type of a UE-UE link established between the relay UE 802 and the remote UE 806.

[0096] In one aspect, the relay UE 802 may determine the UE-UE link type based on at least one of the following: whether the relay UE 802 supports the corresponding UE-UE link type; whether the relay UE 802 is subscribed to or authorized for the corresponding UE-UE link type; or whether the relay UE 802 discovers, is pre-configured with, or is connected to the remote UE 806 via the corresponding UE-UE link type.

[0097] In one aspect, the relay UE 802 may detect the UE-UE link type available between the remote UE 806 and the relay UE 802 based on at least one of the following: whether the UE-UE link quality for the UE-UE link type meets the criteria; or whether the UE-UE link for the UE-UE link type is available based on the capabilities of the relay UE 802.

[0098] At 812, UE 802 may provide UE-UE link information to network node 804. In one aspect, the UE-UE link information is sent via an RRC message. In another aspect, the UE-UE link information is sent in a sidelink UE NR message, a measurement report, or a MSG5 message.

[0099] In one aspect, at 812 , the detected UE-UE link type is indicated in UE-UE link information sent to the network node 804 .

[0100] In one aspect, the UE-UE link information sent at 812 may include information associated with at least one of the following: a side link connection between the remote UE 806 and the relay UE 802, a PC5 interface, a 3GPP connection, a non-3GPP connection, an ideal link, a UE aggregation connection, an L2 relay connection, a WLAN connection, or a Bluetooth connection.

[0101] At 814, the network node 804 may determine a configuration for the remote UE 806 and the relay UE 804 based on (e.g., corresponding to) the UE-UE link information received at 812. For example, the configuration may be according to the user plane architecture configuration described above with reference to 6A or the user plane architecture configuration described above with reference to 6B, depending on the UE-UE link type of the determined UE-UE link 808.

[0102] At 816, the network node may provide (e.g., send) the determined configuration for the relay UE 802 to the relay UE 802. At 818, the network node 804 may provide the determined configuration for the remote UE 806 to the remote UE 806. Note that the network node 804 may send the configuration for the relay UE 802 before, after, or simultaneously with sending the configuration for the remote UE 806.

[0103] Fig. 9900 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure. In particular, call flow diagram 900 illustrates a core network 908 notifying a network node 904 of information associated with a UE-UE link 910 between a remote UE 906 and a relay UE 902. The relay UE 902 may be a UE that relays data from the network node 904 to another UE (e.g., a UE outside the coverage area of ​​the network node 904). The remote UE 906 may be a UE that receives data from another UE (e.g., the relay UE 902) and / or the network node 904 (depending on whether the remote UE 906 is within the coverage area of ​​the network node 904). Although various aspects are described with respect to the network node 904, these aspects may be performed by the network node in an aggregation and / or by one or more components of the network node 904 (e.g., such as the CU 110, the DU 130, and / or the RU 140). As Fig. 9 As shown, the remote UE 906 may be able to determine UE-UE link information indicating a type of UE-UE link (e.g., UE-UE link 910) between the remote UE 906 and the relay UE 902 at 912. The UE-UE link information may indicate various information associated with a link between the relay UE 902 and the remote UE 906. For example, the UE-UE link information may indicate a type of UE-UE link established between the relay UE 902 and the remote UE 906.

[0104] In one aspect, the remote UE 906 may determine the UE-UE link type based on at least one of the following: whether the remote UE 906 supports the corresponding UE-UE link type; whether the remote UE 906 supports MP relay for the corresponding UE-UE link type; whether the remote UE 906 is subscribed to or authorized for the corresponding UE-UE link type; whether the remote UE 906 is subscribed to or authorized for MP relay for the corresponding UE-UE link type; or whether the remote UE 906 discovers, is preconfigured with, or is connected to the relay UE 904 via the corresponding UE-UE link type.

[0105] In one aspect, the remote UE 906 may detect the UE-UE link type available between the remote UE 906 and the relay UE 902 based on at least one of the following: whether the UE-UE link quality for the UE-UE link type meets the criteria configured for single-path relay; whether the UE-UE link quality for the UE-UE link type meets the criteria configured for MP relay; or whether the UE-UE link for the UE-UE link type is available based on the capabilities of the remote UE 906.

[0106] At 914, the remote UE 906 may send a NAS message including the UE-UE link information, which is received by the network node 904. At 916, the network node 904 may forward the NAS message to the core network 908.

[0107] In one aspect, the detected UE-UE link type is indicated in the UE-UE link information sent to the core network 908 .

[0108] In one aspect, the UE-UE link information sent at 914 may include information associated with at least one of the following: a side link connection between the remote UE 906 and the relay UE 904, a PC5 interface, a 3GPP connection, a non-3GPP connection, an ideal link, a UE aggregation connection, an L2 relay connection, a WLAN connection, or a Bluetooth connection.

[0109] At 918, the core network 908 may determine the UE-UE link information from the NAS message received at 916. Note that in other aspects, rather than obtaining the UE-UE link information via a NAS message (as described above), the core network 908 may receive the UE-UE link information based on subscription information (e.g., maintained by the core network 908) of each of the remote UE 906 and the relay UE 902.

[0110] At 920, the core network 908 may provide the UE-UE link information to the network node 904. In one aspect, the core network 908 may provide the UE-UE link information to the network node 904 via an NGAP message (eg, via a UE initial context in an NGAP message).

[0111] At 922, the network node 904 may determine a configuration for the remote UE 906 and the relay UE 902 based on (e.g., corresponding to) the UE-UE link information received at 920. For example, the configuration may be according to the user plane architecture configuration described above with reference to 6A or the user plane architecture configuration described above with reference to 6B, depending on the UE-UE link type of the determined UE-UE link 910.

[0112] At 924, the network node 904 may provide (e.g., send) the determined configuration for the relay UE 902 to the relay UE 902. At 926, the network node 904 may provide the determined configuration for the remote UE 906 to the remote UE 906. Note that the network node 904 may send the configuration for the relay UE 902 before, after, or simultaneously with sending the configuration for the remote UE 906.

[0113] Fig.101000 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure. In particular, call flow diagram 1000 illustrates that a core network 1008 notifies a network node 1004 of information associated with a UE-UE link 1010 between a remote UE 1006 and a relay UE 1002. Relay UE 1002 may be a UE that relays data from the network node 1004 to another UE (e.g., a UE outside the coverage area of ​​the network node 1004). Remote UE 1006 may be a UE that receives data from another UE (e.g., relay UE 1002) and / or network node 1004 (depending on whether remote UE 1006 is within the coverage area of ​​the network node 1004). Although various aspects are described with respect to network node 1004, these aspects may be performed by a network node in an aggregation and / or by one or more components of network node 1004 (e.g., such as CU 110, DU 130, and / or RU 140). As shown in FIG. Fig.10 As shown, the relay UE 1002 may determine UE-UE link information indicating a type of a UE-UE link (e.g., UE-UE link 1010) between the remote UE 1006 and the relay UE 1002 at 1012. The UE-UE link information may indicate various information associated with a link between the relay UE 1002 and the remote UE 1006. For example, the UE-UE link information may indicate a type of a UE-UE link established between the relay UE 1002 and the remote UE 1006.

[0114] In one aspect, the relay UE 1002 may determine the UE-UE link type based on at least one of the following: whether the relay UE 1002 supports the corresponding UE-UE link type; whether the relay UE 1002 is subscribed to or authorized for the corresponding UE-UE link type; or whether the relay UE 1002 discovers, is pre-configured with the corresponding UE-UE link type, or is connected to the remote UE 1006 via the corresponding UE-UE link type.

[0115] In one aspect, the relay UE 1002 may detect the UE-UE link type available between the remote UE 1006 and the relay UE 1002 based on at least one of the following: whether the UE-UE link quality for the UE-UE link type meets the criteria; or whether the UE-UE link for the UE-UE link type is available based on the capabilities of the relay UE 1002.

[0116] At 1014, relay UE 1002 may send a NAS message including UE-UE link information, which is received by network node 1004. At 1016, network node 1004 may forward the NAS message to core network 1008.

[0117] In one aspect, the detected UE-UE link type is indicated in the UE-UE link information sent to the core network 1008 .

[0118] In one aspect, the UE-UE link information sent at 1014 may include information associated with at least one of the following: a side link connection between the remote UE 906 and the relay UE 904, a PC5 interface, a 3GPP connection, a non-3GPP connection, an ideal link, a UE aggregation connection, an L2 relay connection, a WLAN connection, or a Bluetooth connection.

[0119] At 1018, the core network 1008 may determine the UE-UE link information from the NAS message received at 1016. Note that in other aspects, rather than obtaining the UE-UE link information via a NAS message (as described above), the core network 1008 may receive the UE-UE link information based on subscription information (e.g., maintained by the core network 1008) of each of the remote UE 1006 and the relay UE 1002.

[0120] At 1020, the core network 1008 may provide the UE-UE link information to the network node 1004. In one aspect, the core network 1008 may provide the UE-UE link information to the network node 1004 via an NGAP message (eg, via a UE initial context in a NGAP message).

[0121] At 1022, the network node 1004 may determine a configuration for the remote UE 1006 and the relay UE 1002 based on (e.g., corresponding to) the UE-UE link information received at 1020. For example, the configuration may be according to the user plane architecture configuration described above with reference to 6A or the user plane architecture configuration described above with reference to 6B, depending on the UE-UE link type of the determined UE-UE link 1010.

[0122] At 1024, the network node 1004 may provide (e.g., send) the determined configuration for the relay UE 1002 to the relay UE 1002. At 1026, the network node 1004 may provide the determined configuration for the remote UE 1006 to the remote UE 1006. Note that the network node 1004 may provide the configuration for the relay UE 1002 before, after, or simultaneously with sending the configuration for the remote UE 1006.

[0123] Fig.11 1100 is a flowchart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure. The method may be performed by a UE. The UE may be Fig.13UE 104, 350, 702, 706, 802, 806, 902, 906, 1002, 1006 or device 1304 in a hardware specific implementation of.

[0124] like Fig.11 As shown, at 1102, the UE may send UE-UE link information indicating a UE-UE link type between a remote UE and a relay UE, the first UE being one of the remote UE or the relay UE. In some aspects, the first UE is a remote UE. For example, referring to Figure 7 , the remote UE 706 may send UE-UE link information indicating a UE-UE link type (e.g., UE-UE link 708) between the remote UE 706 and the relay UE 702 at 712. In some aspects, 1102 may be performed by the UE-UE link information determining component 198. In other aspects, the first UE is a relay UE. For example, referring to Figure 8 , the relay UE 802 may send UE-UE link information at 812 indicating a UE-UE link type (eg, UE-UE link 808 ) between the remote UE 806 and the relay UE 802 .

[0125] In some aspects, the UE-UE link information is sent via an RRC message. For example, refer to Figure 7 and Figure 8 , the UE-UE link information sent at 712 or 812 can be sent via an RRC message.

[0126] In some aspects, the UE-UE link information is sent in a sidelink UE information NR message, a measurement report, or a MSG5 message. Figure 7 and Figure 8 , the UE-UE link information sent at 712 or 812 can be sent in a side link UE information NR message, a measurement report or a MSG5 message.

[0127] In some aspects, the transmitted UE-UE link information includes information associated with at least one of: a side link connection between a remote UE and a relay UE, a PC5 interface, a third generation partnership project (3GPP) connection, a non-3GPP connection, an ideal link, a UE aggregation connection, a layer 2 (L2) relay connection, a wireless local area network (WLAN) connection, or a Bluetooth connection. For example, referring to Figure 7 and Figure 8, the UE-UE link information sent at 712 or 812 includes information associated with at least one of the following: a side link connection between a remote UE (e.g., remote UE 706 or 806) and a relay UE (e.g., relay UE 702 or 802), a PC5 interface, a Third Generation Partnership Project (3GPP) connection, a non-3GPP connection, an ideal link, a UE aggregation connection, a layer 2 (L2) relay connection, a wireless local area network (WLAN) connection, or a Bluetooth connection.

[0128] In some aspects where the first UE is a remote UE, the remote UE may determine the UE-UE link type based on at least one of: whether the remote UE supports the corresponding UE-UE link type; whether the remote UE supports multipath (MP) relay for the corresponding UE-UE link type; whether the remote UE is subscribed to or authorized for the corresponding UE-UE link type; whether the remote UE is subscribed to or authorized for MP relay for the corresponding UE-UE link type; or whether the remote UE discovers, is preconfigured with, or is connected to a relay UE via the corresponding UE-UE link type. For example, referring to Figure 7 , the remote UE 706 may determine the UE-UE link type based on at least one of the following: whether the remote UE 706 supports the corresponding UE-UE link type; whether the remote UE 706 supports multipath (MP) relay for the corresponding UE-UE link type; whether the remote UE 706 is subscribed to or authorized for the corresponding UE-UE link type; whether the remote UE 706 is subscribed to or authorized for MP relay for the corresponding UE-UE link type; or whether the remote UE 706 discovers, is preconfigured with, or is connected to the relay UE 702 via the corresponding UE-UE link type. The UE-UE link type indicated in the UE-UE link information may be the determined UE-UE link type. For example, referring to Figure 7 , the UE-UE link type indicated in the UE-UE link information sent at 712 may be the determined UE-UE link type.

[0129] In some aspects where the first UE is a remote UE, the remote UE may detect one or more UE-UE link types available between the first UE and the relay UE based on at least one of: whether the UE-UE link quality for the UE-UE link type meets the criteria configured for single-path relay; whether the UE-UE link quality for the UE-UE link type meets the criteria configured for MP relay; or whether the UE-UE link for the UE-UE link type is available based on the capabilities of the first UE. For example, referring to Figure 7, the remote UE 706 may detect the available UE-UE link type between the remote UE 706 and the relay UE 702 based on at least one of the following: whether the UE-UE link quality for the UE-UE link type satisfies the criteria configured for single-path relay; whether the UE-UE link quality for the UE-UE link type satisfies the criteria configured for MP relay; or whether the UE-UE link for the UE-UE link type is available based on the capabilities of the first UE. The UE-UE link type indicated in the UE-UE link information may be the detected UE-UE link type. For example, referring to Figure 7 The UE-UE link type indicated in the UE-UE link information sent at 712 may be a detected UE-UE link type.

[0130] In some aspects where the first UE is a relay UE, the relay UE may determine the UE-UE link type based on at least one of: whether the relay UE supports the corresponding UE-UE link type; whether the relay UE is subscribed to or authorized for the corresponding UE-UE link type; or whether the relay UE discovers, is pre-configured with, or is connected to the remote UE via the corresponding UE-UE link type. For example, referring to Figure 8 , the relay UE 802 may determine the UE-UE link type based on at least one of the following: whether the relay UE 802 supports the corresponding UE-UE link type; whether the relay UE 802 is subscribed to or authorized for the corresponding UE-UE link type; or whether the relay UE 802 discovers, is pre-configured with the corresponding UE-UE link type, or is connected to the remote UE 806 through the corresponding UE-UE link type. The UE-UE link type indicated in the UE-UE link information may be the determined UE-UE link type. For example, referring to Figure 8 , the UE-UE link type indicated in the UE-UE link information sent at 812 may be the determined UE-UE link type.

[0131] In some aspects where the first UE is a relay UE, the relay UE may detect one or more UE-UE link types available between the first UE and the remote UE based on at least one of: whether the UE-UE link quality for the UE-UE link type meets the configured criteria; or whether the UE-UE link for the UE-UE link type is available based on the capabilities of the first UE. For example, referring to Figure 8, the relay UE 802 may detect the available UE-UE link type between the remote UE 806 and the relay UE 802 based on at least one of the following: whether the UE-UE link quality for the UE-UE link type meets the configured criteria; or whether the UE-UE link for the UE-UE link type is available based on the capabilities of the first UE. The UE-UE link type indicated in the UE-UE link information may be the detected UE-UE link type. For example, referring to Figure 8 , the UE-UE link type indicated in the UE-UE link information sent at 812 may be the detected UE-UE link type.

[0132] In some aspects, UE-UE link information may be sent to the CN via a NAS message. Fig. 9 , in an aspect where the first UE is a remote UE, the remote UE 906 may send UE-UE link information to the network node 904 via a NAS message, and at 916, the network node 904 may forward the NAS message to the core network 908. In another example, referring to Fig.10 In an aspect where the first UE is a relay UE, the relay UE 1002 may send the UE-UE link information to the network node 1004 via a NAS message, and at 1016 , the network node 1004 may forward the NAS message to the core network 1008 .

[0133] At 1104, the UE may receive a configuration corresponding to the transmitted UE-UE link information. Figure 7 and Fig. 9 , in aspects where the first UE is remote UE 706 or remote UE 906, remote UE 706 or remote UE 906 receives its configuration from network node 704 at 718 or from network node 904 at 926. In some aspects, 1104 may be performed by UE-UE link information determining component 198. In another example, reference Figure 8 and Fig.10 In aspects where the first UE is relay UE 802 or relay UE 1002 , relay UE 802 or relay UE 1002 receives its configuration from network node 804 at 816 or from network node 1004 at 1024 .

[0134] Fig.12 1200 is a flowchart illustrating a method of wireless communication at a network node according to various aspects of the present disclosure. The method may be performed by a network node. The network node may be Figure 1A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; CU 110, DU 130; RU 140; network node 704, 804, 904, or 1004; or Fig.14 Network entity 1402 in a hardware specific implementation).

[0135] At 1202, the network node may receive UE-UE link information indicating a UE-UE link type between a remote UE and a relay UE. Figure 7 At 712, the network node 704 may receive UE-UE link information from the remote UE 706 via an RRC message. In some aspects, 1202 may be performed by the UE configuration determining component 199. In another aspect, reference Figure 8 At 812, the network node may receive the UE-UE link information from the relay UE 802 via an RRC message. In yet another aspect, the UE-UE link information may be received in a sidelink UE information new radio (NR) message, a measurement report, or a MSG5 message (e.g., received from the remote UE 706 at 712 or from the relay UE 802 at 812).

[0136] In some aspects, the received UE-UE link information includes information associated with at least one of: a side link connection between a remote UE and a relay UE, a PC5 interface, a third generation partnership project (3GPP) connection, a non-3GPP connection, an ideal link, a UE aggregation connection, a layer 2 (L2) relay connection, a wireless local area network (WLAN) connection, or a Bluetooth connection. For example, referring to Figure 7 and Figure 8 , the UE-UE link information received at 712 or 812 includes information associated with at least one of the following: a side link connection between a remote UE (e.g., remote UE 706 or 806) and a relay UE (e.g., relay UE 702 or 802), a PC5 interface, a Third Generation Partnership Project (3GPP) connection, a non-3GPP connection, an ideal link, a UE aggregation connection, a layer 2 (L2) relay connection, a wireless local area network (WLAN) connection, or a Bluetooth connection.

[0137] In some aspects, the UE-UE link information is received from the CN via an NGAP message. Fig. 9 and Fig.10 , the network node 904 or 1004 may receive UE-UE link information from the core network 908 or 1008 at 920 or 1020 .

[0138] In some aspects, the UE-UE link information is received from the CN via the UE initial context in the NGAP message. Fig. 9and Fig.10 , UE-UE link information received by the network node 904 or 1004 from the core network 908 or 1008 can be received via the UE initial context in the NGAP message.

[0139] In some aspects, the received UE-UE link information is based on subscription information of each of the remote UE and the relay UE. Fig. 9 and Fig.10 , the core network 908 or 1008 may receive UE-UE link information based on subscription information of each of the remote UE 906 or 1006 and the relay UE 902 or 1002.

[0140] In some aspects, the UE-UE link information may be received via a NAS message, and the UE-UE link information received via the NAS message may be forwarded to the CN. Fig. 9 and Fig.10 , the network node 904 or 1004 may receive the UE-UE link information via a NAS message at 914 or 1014 , and the network node 904 may forward the NAS message to the core network 908 or 1008 at 916 or 1016 .

[0141] At 1204, the network node may send a configuration corresponding to the received UE-UE link information to the remote UE and the relay UE. Figure 7 , the network node 704 may send a configuration corresponding to the received UE-UE link information to the remote UE and the relay UE. In some aspects, 1204 may be performed by the UE configuration determining component 199.

[0142] Fig.131300 is a diagram illustrating an example of a hardware implementation for an apparatus 1304. The apparatus 1304 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1304 may include a cellular baseband processor 1324 (also referred to as a modem) coupled to one or more transceivers 1322 (e.g., a cellular RF transceiver). The cellular baseband processor 1324 may include on-chip memory 1324'. In some aspects, the apparatus 1304 may also include one or more subscriber identity module (SIM) cards 1320 and an application processor 1306 coupled to a secure digital (SD) card 1308 and a screen 1310. The application processor 1306 may include on-chip memory 1306'. In some aspects, the device 1304 may also include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., a GNSS module), one or more sensor modules 1318 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1326, a power source 1330, and / or a camera 1332. The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include their own dedicated antennas and / or communicate using an antenna 1380. The cellular baseband processor 1324 communicates with the UE 104 and / or the RU associated with the network entity 1302 through the transceiver 1322 via one or more antennas 1380. The cellular baseband processor 1324 and the application processor 1306 may each include a computer-readable medium / memory 1324', 1306', respectively. The additional memory module 1326 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1324', 1306', 1326 may be non-transitory. The cellular baseband processor 1324 and the application processor 1306 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1324 / application processor 1306, enables the cellular baseband processor 1324 / application processor 1306 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1324 / application processor 1306 when executing the software.The cellular baseband processor 1324 / application processor 1306 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1304 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1324 and / or the application processor 1306, while in another configuration, the device 1304 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1304.

[0143] As discussed above, component 198 is configured to send UE-UE link information indicating a UE-UE link type between a remote UE and a relay UE, the first UE being one of the remote UE or the relay UE, and receive a configuration corresponding to the sent UE-UE link information. Component 198 may also be configured to perform a combination Fig.13 The various aspects described in the flowchart in and / or by the remote UE or the relay UE in Figures 7 to 10 Any of the various aspects performed in the communication process of . Component 198 may be within the cellular baseband processor 1324, the application processor 1306, or both the cellular baseband processor 1324 and the application processor 1306. Component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1304 may include multiple components configured for various functions. In one configuration, the device 1304 (and in particular, the cellular baseband processor 1324 and / or the application processor 1306) includes: a component for sending UE-UE link information indicating a UE-UE link type between a remote UE and a relay UE, the first UE being one of the remote UE or the relay UE; and a component for receiving a configuration corresponding to the sent UE-UE link information. The device may also include a component for performing a combination Fig.13 The various aspects described in the flowchart and / or by the remote UE or the relay UE in Figures 7 to 10 The components may be components 198 of the apparatus 1304 configured to perform the functions recited by the components. As described above, the apparatus 1304 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the components may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the components.

[0144] Fig.141400 is a diagram illustrating an example of a hardware implementation for a network entity 1402. The network entity 1402 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1402 may include at least one of a CU 1410, a DU 1430, or a RU 1440. For example, depending on the layer functionality handled by the component 199, the network entity 1402 may include a CU 1410; both a CU 1410 and a DU 1430; each of the CU 1410, the DU 1430, and the RU 1440; the DU 1430; both a DU 1430 and a RU 1440; or the RU 1440. The CU 1410 may include a CU processor 1412. The CU processor 1412 may include an on-chip memory 1412'. In some aspects, the CU 1410 may also include an additional memory module 1414 and a communication interface 1418. CU 1410 communicates with DU 1430 via a midhaul link, such as an F1 interface. DU 1430 may include a DU processor 1432. DU processor 1432 may include on-chip memory 1432'. In some aspects, DU 1430 may also include an additional memory module 1434 and a communication interface 1438. DU 1430 communicates with RU 1440 via a fronthaul link. RU 1440 may include a RU processor 1442. RU processor 1442 may include on-chip memory 1442'. In some aspects, RU 1440 may also include an additional memory module 1444, one or more transceivers 1446, an antenna 1480, and a communication interface 1448. RU 1440 communicates with UE 104. On-chip memory 1412', 1432', 1442' and additional memory modules 1414, 1434, 1444 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1412, 1432, 1442 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0145] As discussed above, component 199 is configured to receive UE-UE link information indicating a UE-UE link type between a remote UE and a relay UE, and to send a configuration corresponding to the received UE-UE link information to the remote UE and the relay UE. Component 199 may also be configured to perform a combined Fig.12 The various aspects described in the flowchart in and / or by the network node in Figures 7 to 10Any of the aspects performed in the communication process of . Component 199 may be within one or more processors of one or more of CU 1410, DU 1430, and RU 1440. Component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1402 may include a variety of components configured for various functions. In one configuration, network entity 1402 includes a component for receiving user equipment UE-UE link information indicating a UE-UE link type between a remote UE and a relay UE; and a component for sending a configuration corresponding to the received UE-UE link information to the remote UE and the relay UE. Component 199 may also include a component for performing a combined Fig.12 The various aspects described in the flowchart in and / or by the network node in Figures 7 to 10 The components may be components 199 of the network entity 1402 configured to perform the functions recited by the components. As described above, the network entity 1402 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the components may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the components.

[0146] Various aspects of the present disclosure provide methods and apparatus for a remote UE or a relay UE to notify a network node of a UE-UE link type being utilized between the remote UE and the relay UE. Using the UE-UE link type, the network node determines a configuration corresponding to the UE-UE link type for the remote UE and the relay UE, and provides the determined configuration to the remote UE and the relay UE. The remote UE and the relay UE apply the configuration received from the network node. The method and apparatus advantageously enable the network node to correctly configure the remote UE and the relay UE for MP relaying, thereby enhancing the reliability and throughput of the connection between the UE and the network node.

[0147] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0148] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless specifically stated otherwise, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, wherein the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0149] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0150] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0151] Aspect 1 is a method for wireless communication at a UE, the method comprising: sending UE-UE link information indicating a UE-UE link type between a remote UE and a relay UE, the first UE being one of the remote UE or the relay UE.

[0152] Aspect 2 is a method according to aspect 1, wherein in order to send the UE-UE link, the UE-UE link information is sent through an RRC message.

[0153] Aspect 3 is a method according to any one of Aspect 1, wherein the UE-UE link information is sent in a sidelink UE information NR message, a measurement report or an MSG5 message.

[0154] Aspect 4 is a method according to any one of Aspects 1 to 3, wherein the UE-UE link information sent includes information associated with at least one of the following items: a side link connection between the remote UE and the relay UE, a PC5 interface, a 3GPP connection, a non-3GPP connection, an ideal link, a UE aggregation connection, an L2 relay connection, a WLAN connection, or a Bluetooth connection.

[0155] Aspect 5 is a method according to any one of aspects 1 to 4, wherein the first UE is the remote UE.

[0156] Aspect 6 is a method according to Aspect 5, and the method also includes: determining the UE-UE link type based on at least one of the following items: whether the remote UE supports the corresponding UE-UE link type; whether the remote UE supports MP relay for the corresponding UE-UE link type; whether the remote UE is subscribed to or authorized for the corresponding UE-UE link type; whether the remote UE is subscribed to or authorized for MP relay for the corresponding UE-UE link type; or whether the remote UE discovers, is pre-configured with the corresponding UE-UE link type, or is connected to the relay UE through the corresponding UE-UE link type, wherein the indicated UE-UE link type is the determined UE-UE link type.

[0157] Aspect 7 is a method according to any one of Aspects 5 or 6, the method further comprising: detecting one or more UE-UE link types available between the first UE and the relay UE based on at least one of the following: whether the UE-UE link quality for the UE-UE link type meets the criteria configured for a single-path relay; whether the UE-UE link quality for the UE-UE link type meets the criteria configured for a multi-path (MP) relay; or based on the capability of the first UE, whether the UE-UE link for the UE-UE link type is available, wherein the indicated UE-UE link type is one UE-UE link type among the one or more UE-UE link types detected.

[0158] Aspect 8 is a method according to any one of aspects 1 to 4, wherein the first UE is the relay UE.

[0159] Aspect 9 is a method according to Aspect 8, the method further comprising: determining the UE-UE link type based on at least one of the following items: whether the relay UE supports the corresponding UE-UE link type; whether the relay UE is subscribed to or authorized for the corresponding UE-UE link type; or whether the relay UE discovers, is pre-configured with the corresponding UE-UE link type, or is connected to the remote UE through the corresponding UE-UE link type, wherein the indicated UE-UE link type is the determined UE-UE link type.

[0160] Aspect 10 is a method according to any one of Aspects 8 or 9, the method further comprising: detecting one or more UE-UE link types available between the first UE and the remote UE based on at least one of the following: whether the UE-UE link quality for the UE-UE link type meets the configured criteria; or based on the capability of the first UE, whether the UE-UE link for the UE-UE link type is available, wherein the indicated UE-UE link type is one UE-UE link type among the one or more UE-UE link types detected.

[0161] Aspect 11 is a method according to aspect 1, the method further comprising: sending the UE-UE link information to a core network (CN) through a non-access stratum (NAS) message.

[0162] Aspect 12 is a method for performing wireless communication at a network entity, the method comprising: receiving UE-UE link information indicating a UE-UE link type between a remote UE and a relay UE; and sending a configuration corresponding to the received UE-UE link information to the remote UE and the relay UE.

[0163] Aspect 13 is a method according to aspect 12, wherein the UE-UE link information is received from the remote UE through an RRC message.

[0164] Aspect 14 is a method according to aspect 13, wherein the UE-UE link information is received from the relay UE through an RRC message.

[0165] Aspect 15 is a method according to aspect 13, wherein the UE-UE link information is received in a sidelink UE information NR message, a measurement report or a MSG5 message.

[0166] Aspect 16 is a method according to any one of Aspects 13 to 15, wherein the received UE-UE link information includes information associated with at least one of the following items: a side link connection between the remote UE and the relay UE, a PC5 interface, a 3GPP connection, a non-3GPP connection, an ideal link, a UE aggregation connection, an L2 relay connection, a WLAN connection, or a Bluetooth connection.

[0167] Aspect 17 is a method according to aspect 12 or 16, wherein the UE-UE link information is received from the CN via a NGAP message.

[0168] Aspect 18 is a method according to aspect 17, wherein the UE-UE link information is received from the CN through a UE initial context in the NGAP message.

[0169] Aspect 19 is a method according to aspect 17, wherein the received UE-UE link information is based on subscription information for each of the remote UE and the relay UE.

[0170] Aspect 20 is a method according to 12 and 17 to 19, the method further comprising: receiving the UE-UE link information through a NAS message; and forwarding the UE-UE link information received through the NAS message to the CN.

[0171] Aspect 21 is an apparatus for wireless communication at a UE. The apparatus includes: a memory; and at least one processor, the at least one processor is coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to implement any one of aspects 1 to 11.

[0172] Aspect 22 is the apparatus of aspect 21, further comprising: at least one of a transceiver or an antenna coupled to the at least one processor.

[0173] Aspect 23 is an apparatus for wireless communication at a network entity. The apparatus includes: a memory; and at least one processor, the at least one processor is coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to implement any one of aspects 12 to 20.

[0174] Aspect 24 is the apparatus of aspect 23, the apparatus further comprising: at least one of a transceiver or an antenna coupled to the at least one processor.

[0175] Aspect 25 is an apparatus for wireless communication, the apparatus comprising: a component for implementing any one of aspects 1 to 11.

[0176] Aspect 26 is an apparatus for wireless communication, the apparatus comprising: means for implementing any one of aspects 12 to 20.

[0177] Aspect 27 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, which, when executed by at least one processor, causes the at least one processor to implement any one of aspects 1 to 11.

[0178] Aspect 28 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, which, when executed by at least one processor, causes the at least one processor to implement any one of aspects 12 to 20.

Claims

1. A device for performing wireless communication at a first user equipment (UE), the device include: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: sending UE-UE link information indicating a UE-to-UE (UE-UE) link type between a remote UE and a relay UE, the first UE being one of the remote UE or the relay UE; as well as A configuration corresponding to the sent UE-UE link information is received.

2. The apparatus according to claim 1, wherein, to send the UE-UE link information, the at least one processor is configured to send the UE-UE link information via a radio resource control (RRC) message.

3. The apparatus of claim 1, wherein, in order to send the UE-UE link information, the at least one processor is configured to send the UE-UE link information in a sidelink UE information new radio (NR) message, a measurement report, or a message 5 (MSG5) message.

4. The apparatus of claim 1 , wherein the transmitted UE-UE link information comprises first information associated with at least one of: a side link connection between the remote UE and the relay UE, a PC5 interface, a third generation partnership project (3GPP) connection, a non-3GPP connection, an ideal link, a UE aggregation connection, a layer 2 (L2) relay connection, a wireless local area network (WLAN) connection, or a Bluetooth connection. The apparatus of claim 1 , wherein the first UE is the remote UE.

6. The apparatus of claim 5, wherein the at least one processor is further configured to determine the UE-UE link type based on at least one of: Whether the remote UE supports the corresponding UE-UE link type; whether the remote UE supports multipath (MP) relay for the corresponding UE-UE link type; whether the remote UE is subscribed to or authorized for the corresponding UE-UE link type; whether the remote UE is subscribed or authorized for MP relay for the corresponding UE-UE link type; or whether the remote UE discovers, is pre-configured with, or is connected to the relay UE via the corresponding UE-UE link type, The indicated UE-UE link type is the determined UE-UE link type.

7. The apparatus of claim 5, wherein the at least one processor is further configured to detect one or more UE-UE link types available between the first UE and the relay UE based on at least one of: whether the UE-UE link quality for the UE-UE link type meets a first criterion configured for single-path relay; whether the UE-UE link quality for the UE-UE link type satisfies a second criterion configured for multipath (MP) relay; or whether a UE-UE link for the UE-UE link type is available based on capabilities of the first UE, The indicated UE-UE link type is one UE-UE link type among the one or more detected UE-UE link types. The apparatus of claim 1 , wherein the first UE is the relay UE.

9. The apparatus of claim 8, wherein the at least one processor is further configured to determine the UE-UE link type based on at least one of: Whether the relay UE supports the corresponding UE-UE link type; Whether the relay UE is subscribed to or authorized for the corresponding UE-UE link type; or whether the relay UE discovers, is pre-configured with, or is connected to the remote UE via the corresponding UE-UE link type, The indicated UE-UE link type is the determined UE-UE link type.

10. The apparatus of claim 8, wherein the at least one processor is further configured to detect one or more UE-UE link types available between the first UE and the remote UE based on at least one of: whether the UE-UE link quality for the UE-UE link type meets a configured criterion; or whether a UE-UE link for the UE-UE link type is available based on capabilities of the first UE, The indicated UE-UE link type is one UE-UE link type among the one or more detected UE-UE link types.

11. The device according to claim 1, further comprising: include: at least one of a transceiver or an antenna coupled to the at least one processor, wherein to send the UE-UE link information, the at least one processor is configured to send the UE-UE link information to a core network (CN) through a non-access stratum (NAS) message via at least one of the transceiver or the antenna.

12. A device for wireless communication at a network entity, the device include: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving UE-UE link information indicating a UE-to-UE (UE-UE) link type between a remote user equipment (UE) and a relay UE; as well as A configuration corresponding to the received UE-UE link information is sent to the remote UE and the relay UE.

13. The apparatus of claim 12, wherein to receive the UE-UE link information, the at least one processor is configured to receive the UE-UE link information from the remote UE via a radio resource control (RRC) message.

14. The apparatus of claim 12, wherein to receive the UE-UE link information, the at least one processor is configured to receive the UE-UE link information from the relay UE through a radio resource control (RRC) message.

15. The apparatus of claim 12, wherein to receive the UE-UE link information, the at least one processor is configured to receive the UE-UE link information in a sidelink UE information new radio (NR) message, a measurement report, or a message 5 (MSG5) message.

16. The apparatus of claim 12, wherein the received UE-UE link information comprises first information associated with at least one of: a side link connection between the remote UE and the relay UE, a PC5 interface, a third generation partnership project (3GPP) connection, a non-3GPP connection, an ideal link, a UE aggregation connection, a layer 2 (L2) relay connection, a wireless local area network (WLAN) connection, or a Bluetooth connection.

17. The device according to claim 12, further comprising: include: At least one of a transceiver or an antenna coupled to the at least one processor, wherein to receive the UE-UE link information, the at least one processor is configured to receive the UE-UE link information from a core network (CN) via at least one of the transceiver or the antenna through a Next Generation (NG) Application Protocol (NGAP) message.

18. The apparatus of claim 17, wherein to receive the UE-UE link information, the at least one processor is configured to receive the UE-UE link information from the CN through a UE initial context in the NGAP message.

19. The apparatus of claim 17, wherein the received UE-UE link information is based on subscription information for each of the remote UE and the relay UE.

20. The apparatus of claim 12, wherein the at least one processor is further configured to: receiving the UE-UE link information via a non-access stratum (NAS) message; and The UE-UE link information received through the NAS message is forwarded to a core network (CN).

21. A method for wireless communication at a first user equipment (UE), the method include: sending UE-UE link information indicating a UE-to-UE (UE-UE) link type between a remote UE and a relay UE, the first UE being one of the remote UE or the relay UE; as well as A configuration corresponding to the sent UE-UE link information is received.

22. The method of claim 21, wherein the UE-UE link information is sent via a radio resource control (RRC) message.

23. The method of claim 21, wherein the UE-UE link information is sent in a sidelink UE Information New Radio (NR) message, a measurement report, or a message 5 (MSG5) message.

24. The method of claim 21, wherein the sent UE-UE link information comprises information associated with at least one of: a side link connection between the remote UE and the relay UE, a PC5 interface, a Third Generation Partnership Project (3GPP) connection, a non-3GPP connection, an ideal link, a UE aggregation connection, a layer 2 (L2) relay connection, a wireless local area network (WLAN) connection, or a Bluetooth connection.

25. The method of claim 21, wherein the first UE is the remote UE.

26. A method for wireless communication at a network entity, the method include: receiving UE-UE link information indicating a UE-to-UE (UE-UE) link type between a remote user equipment (UE) and a relay UE; as well as A configuration corresponding to the received UE-UE link information is sent to the remote UE and the relay UE.

27. The method of claim 26, wherein the UE-UE link information is received from the remote UE via a radio resource control (RRC) message.

28. The method of claim 26, wherein the UE-UE link information is received from the relay UE through a radio resource control (RRC) message.

29. The method of claim 26, wherein the UE-UE link information is received in a sidelink UE Information New Radio (NR) message, a measurement report, or a message 5 (MSG5) message.

30. The method of claim 26, wherein the received UE-UE link information comprises information associated with at least one of: a side link connection between the remote UE and the relay UE, a PC5 interface, a Third Generation Partnership Project (3GPP) connection, a non-3GPP connection, an ideal link, a UE aggregation connection, a layer 2 (L2) relay connection, a wireless local area network (WLAN) connection, or a Bluetooth connection.

Images