State transition in sidelink layer 2 relay system

Abstract

Certain aspects of this disclosure provide techniques for paging in a sidelink L2 relay scenario. An example method typically includes receiving an indication from one of the network entities to which the remote UE is connected or from one of the relay UEs to transition from a connected state to an idle or inactive state; and transitioning to an idle or inactive state in response to receiving the indication.

Description

Technical Field

[0001] Various aspects of this disclosure relate to wireless communication, and more specifically, to techniques for performing state transitions in a side link layer 2 (L2) relay system. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. These wireless communication systems can employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include, to name a few, 3GPP Long Term Evolution (LTE) systems, LTE-A Advanced systems, 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] In some examples, a wireless multiple access communication system may include multiple base stations (BSs), each capable of simultaneously supporting communication with multiple communication devices (or user equipments (UEs)). In LTE or LTE-A networks, a group of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in next-generation, new radio (NR) or 5G networks), a wireless multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit receiver points (TRPs), etc.) communicating with multiple central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a group of one or more DUs communicating with the CUs may define access nodes (e.g., which may be referred to as BSs, 5G NBs, next-generation NodeBs (gNBs or gNodeBs), transmit receiver points (TRPs), etc.). A BS or DU may communicate with a group of UEs on downlink channels (e.g., for transmissions from the BS or DU to the UE) and uplink channels (e.g., for transmissions from the UE to the BS or DU).

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. NR (e.g., New Radio or 5G) is an example of an emerging telecommunications standard. NR is a set of enhancements to the LTE mobile standard issued by 3GPP. NR aims to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and using OFDMA with a cyclic prefix (CP) on both the downlink (DL) and uplink (UL) to better integrate with other open standards. To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0005] Sidelink communication is communication from one UE to another. With the continued increase in demand for mobile broadband access, there is a need for further improvements to NR and LTE technologies, including improvements to sidelink communication. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0006] The systems, methods, and apparatus of this disclosure each have several aspects, and no single aspect is solely responsible for its desired properties. Without limiting the scope of this disclosure as set forth in the appended claims, some features will now be briefly discussed. After considering this discussion, and especially after reading the section entitled "Detailed Description," one will understand how the features of this disclosure provide advantages including improved communication between access points and stations in a wireless network.

[0007] Some aspects provide a method for wireless communication by a remote user equipment (UE). The method typically includes receiving an indication from one of the network entities to which the remote UE is connected or a relay UE to transition from a connected state to an idle or inactive state; and transitioning to the idle or inactive state in response to receiving the indication.

[0008] Some aspects provide a method for wireless communication by a relay node. This method typically includes, when in a connected state, determining that the relay UE will enter an idle or inactive state based on the detection of one of the following: signaling from a network entity to which the relay UE is connected, or the detection of a radio link failure event; and entering the idle or inactive state such that a remote UE connected to the relay UE also transitions from a connected state to an idle or inactive state.

[0009] Some aspects provide a method for wireless communication by a network entity. The method typically includes determining that a remote user equipment (UE) connected to the network entity via a relay UE will enter an idle or inactive state; sending a signaling message to the remote UE to trigger the remote UE to enter the idle or inactive state; and, after sending the signaling message to trigger the remote UE to enter the idle or inactive state, sending a signaling message to the relay UE to trigger the relay UE to enter the idle or inactive state.

[0010] The aspects generally include methods, apparatus, systems, computer-readable media, and processing systems, as generally described herein with reference to the accompanying drawings, which are also shown in the drawings.

[0011] To achieve the foregoing and related results, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings illustrate certain illustrative features of one or more aspects in detail. However, these features only indicate a few of the various ways in which the principles of each aspect can be employed. Attached Figure Description

[0012] Therefore, the aforementioned features of this disclosure can be understood in detail by referring to various aspects for a more specific description briefly outlined above, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should therefore not be considered as limiting its scope, as the description may allow for other equivalent aspects.

[0013] Figure 1 This is a block diagram conceptually illustrating an example telecommunications system according to certain aspects of this disclosure.

[0014] Figure 2 This is a block diagram illustrating an example logical architecture of a distributed radio access network (RAN) according to certain aspects of this disclosure.

[0015] Figure 3 This is a diagram illustrating an example physical architecture of a distributed RAN according to certain aspects of this disclosure.

[0016] Figure 4 This is a block diagram conceptually illustrating the design of an example base station (BS) and user equipment (UE) according to certain aspects of this disclosure.

[0017] Figure 5 This is a high-level path diagram illustrating example connection paths of remote user equipment (UE) according to certain aspects of this disclosure.

[0018] Figure 6 This is an example block diagram illustrating the control plane protocol stack on L3 when there is no direct connection path between the remote UE and the network node, according to certain aspects of this disclosure.

[0019] Figure 7 This is an example block diagram illustrating the control plane protocol stack on L2 when there is a direct connection path between a remote UE and a network node, according to certain aspects of this disclosure.

[0020] Figure 8 An example layer 3 (L3) relay procedure according to certain aspects of this disclosure is shown.

[0021] Figure 9 An example layer 2 (L2) relay procedure according to certain aspects of this disclosure is shown.

[0022] Figure 10A and Figure 10B An example relay discovery procedure is shown.

[0023] Figure 11 An example communication environment is shown where a relay UE serves one or more remote UEs.

[0024] Figure 12A and Figure 12B This illustrates an example scenario where a remote UE receives paging and system information blocks based on whether the remote UE is within or outside the coverage area of ​​a network entity.

[0025] Figure 13 An example connection path for a remote UE is shown, along with paging before connecting to a relay.

[0026] Figure 14 An example connection path between the remote UE and the relay is shown after the remote UE connects to the relay.

[0027] Figure 15 A flowchart illustrating example operations that can be performed by a remote UE according to certain aspects of this disclosure is shown.

[0028] Figure 16 This is a flowchart illustrating example operations that can be performed by a relay UE according to certain aspects of this disclosure.

[0029] Figure 17 A flowchart illustrating example operations that can be performed by a network entity according to certain aspects of this disclosure is shown.

[0030] Figure 18 Different combinations of remote UE and relay UE states are shown according to certain aspects of this disclosure.

[0031] Figure 19 This is a call flow diagram illustrating example messages that can be transmitted between a remote UE, a relay UE, and a network entity, according to certain aspects of this disclosure, for transitioning a remote UE from a connected state to an idle or inactive state.

[0032] Figure 20 This is a call flow diagram illustrating example messages that can be transmitted between a remote UE, a relay UE, and a network UE, based on certain aspects of this disclosure, for transitioning a remote UE from a connected state to an idle or inactive state based on a radio link failure at the relay UE.

[0033] Figure 21 This is a call flowchart illustrating example messages that can be exchanged between a remote UE, a relay UE, and a network entity, according to certain aspects of this disclosure, for transitioning a remote UE from an idle or inactive state to a connected state.

[0034] Figure 22 A communication device according to certain aspects of this disclosure is shown, the communication device may include being configured to perform Figure 15 The various components of the operation shown.

[0035] Figure 23 A communication device according to certain aspects of this disclosure is shown, the communication device may include being configured to perform Figure 16 The various components of the operation shown.

[0036] Figure 24 A communication device according to certain aspects of this disclosure is shown, the communication device may include being configured to perform Figure 17 The various components of the operation shown.

[0037] For ease of understanding, the same reference numerals are used where possible to denote the same elements common in the figures. Elements disclosed in one aspect are intended to be usefully applied in other aspects without specific description. Detailed Implementation

[0038] This disclosure provides apparatus, methods, processing systems, and computer-readable media for switching between idle or inactive and connected states in a sidelink layer 2 (L2) relay system for remote and relay user equipment (UE).

[0039] A connection between a relay and a network entity can be referred to as a Uu connection or via a Uu path. A connection between a remote UE and a relay (e.g., another UE or "relay UE") can be referred to as a PC5 connection or via a PC5 path. A PC5 connection is a device-to-device connection that can take advantage of the relative proximity between the remote UE and the relay UE (e.g., when the remote UE is closer to the relay UE than the nearest base station). A relay UE can connect to an infrastructure node (e.g., a gNB) via a Uu connection and relay the Uu connection to a remote UE via a PC5 connection.

[0040] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various examples may be appropriately omitted, substituted, or added to various procedures or components. For example, a method may be performed in a different order than that described herein, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For instance, any number of aspects set forth herein may be used to implement an apparatus or practice a method. Additionally, the scope of this disclosure is intended to cover apparatuses or methods that are practiced using structures, functions, or structures and functions other than or different from the aspects set forth herein. It should be understood that any aspect of what is disclosed herein may be embodied by one or more elements of the claims. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0041] The technologies described in this article can be used in various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other CDMA variants. Cdma2000 covers the IS-2000, IS-95, and IS-856 standards. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS).

[0042] New Radio (NR) is an emerging wireless communication technology being developed in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). Cdma2000 and UMB are described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used in the aforementioned wireless network and radio technologies, as well as other wireless network and radio technologies. For clarity, although terms commonly associated with 3G and / or 4G wireless technologies may be used to describe aspects herein, aspects of this disclosure can be applied to other generation-based communication systems, such as 5G and later technologies, including NR technology.

[0043] New radio (NR) access (e.g., 5G technology) can support a variety of wireless communication services, such as enhanced mobile broadband (eMBB) for wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmW) for high carrier frequencies (e.g., 25 GHz or higher), massive machine-type communication (mMTC) for non-backward-compatible MTC technologies, and / or mission-critical ultra-reliable low-latency communication (URLLC). These services may have latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet their respective quality of service (QoS) requirements. Furthermore, these services may coexist in the same subframe.

[0044] Figure 1 An example wireless communication network 100 in which various aspects of this disclosure can be implemented is shown. For example, Figure 1 UE120a and / or BS 110a can be configured to perform the following reference Figure 15 , Figure 16 and Figure 17 Operations 1100, 1200, and 1300 are described to switch between a remote UE and a relay UE in a side-link layer 2 relay system, between an idle or inactive state and a connected state.

[0045] like Figure 1As shown, the wireless communication network 100 may include multiple base stations (BSs) 110a-z (each also individually referred to herein as BS 110 or collectively as BS 110) and other network entities. In various aspects of this disclosure, a roadside service unit (RSU) may be considered a type of BS, and BS 110 may be referred to as an RSU. BS 110 may provide communication coverage for a specific geographic area, sometimes referred to as a "cell," and may be stationary or mobile depending on the location of the mobile BS 110. In some examples, BS 110 may interconnect with each other and / or with one or more other BSs or network nodes (not shown) in the wireless communication network 100 via various types of backhaul interfaces, such as direct physical connections, wireless connections, virtual networks, etc., using any suitable delivery network. Figure 1 In the example shown, BS 110a, 110b, and 110c can be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x can be a pico BS for pico cell 102x. BS 110y and 110z can be femto BSs for femto cells 102y and 102z, respectively. A BS can support one or more cells. BS 110 communicates with user equipment (UEs) 120a-y (each also individually referred to herein as UE 120 or collectively as UE 120) in the wireless communication network 100. UEs 120 (e.g., 120x, 120y, etc.) can be distributed throughout the wireless communication network 100, and each UE 120 can be fixed or mobile.

[0046] The wireless communication network 100 may also include a relay UE (e.g., relay UE 110r), also referred to as a relay, which receives data and / or other information transmissions from an upstream station (e.g., BS 110a or UE 120r) and sends data and / or other information transmissions to a downstream station (e.g., UE 120 or BS 110), or relays transmissions between UEs 120 to facilitate communication between devices.

[0047] Network controller 130 can be coupled to a group of BSs 110 and can provide coordination and control for these BSs 110. Network controller 130 can communicate with BSs 110 via backhaul. BSs 110 can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0048] UE 120 (e.g., 120x, 120y, etc.) may be distributed throughout the wireless communication network 100, and each UE may be fixed or mobile. UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical equipment, biosensor / device, wearable device (such as smartwatch, smart clothing, smart glasses, smart bracelet), smart jewelry (e.g., smart ring, smart bracelet, etc.), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media. Some UEs may be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTCUE include devices such as robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with the BS, another device (e.g., a remote device), or other entities. Wireless nodes can provide connectivity to networks (e.g., wide area networks like the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices; they can be narrowband IoT (NB-IoT) devices.

[0049] Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, often referred to as tones, bins, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing could be 15 kHz, and the minimum resource allocation (called a "resource block" (RB)) could be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal Fast Fourier Transform (FFT) size could be 128, 256, 512, 1024, or 2048, respectively. System bandwidth can also be divided into subbands. For example, a subband can cover 1.08MHz (i.e., 6 resource blocks), and there can be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20MHz, respectively.

[0050] While the aspects of the examples described herein can be associated with LTE technology, aspects of this disclosure can be applied to other wireless communication systems, such as NR. NR can use OFDM with CP on both the uplink and downlink, and includes support for half-duplex operation using TDD. Beamforming can be supported, and beam direction can be dynamically configured. MIMO transmission with pre-decoding can also be supported. MIMO configuration in DL can support up to 8 transmit antennas, up to 8 streams in multi-layer DL transmission, and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE can be supported. Aggregation of multiple cells with up to 8 serving cells can be supported.

[0051] In some examples, access to the air interface can be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication between some or all devices and apparatuses within its service area or cell. The scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize the resources allocated by the scheduling entity. A base station is not the only entity that can be used as a scheduling entity. In some examples, a UE can be used as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs can utilize the resources scheduled by the UE for wireless communication. In some examples, a UE can be used as a scheduling entity in a point-to-point (P2P) network and / or a mesh network. In the mesh network example, UEs can communicate directly with each other in addition to communicating with a scheduling entity.

[0052] exist Figure 1 In the diagram, a solid line with a double arrowhead indicates a desired transmission between the UE and the serving BS, which is the BS designated to serve the UE on the downlink and / or uplink. A thin dashed line with a double arrowhead indicates interference transmission between the UE and the BS.

[0053] Figure 2 It shows that it can be used Figure 1 The example logical architecture of the distributed radio access network (RAN) 200 implemented in the wireless communication network 100 shown is illustrated. The 5G access node 206 may include an access node controller (ANC) 202. The ANC 202 may be the central unit (CU) of the distributed RAN 200. The backhaul interface to the next-generation core network (NG-CN) 204 may terminate at the ANC 202. The backhaul interface to the adjacent next-generation access node (NG-AN) 210 may terminate at the ANC 202. The ANC 202 may include one or more TRPs 208 (e.g., cell, BS, gNB, etc.).

[0054] TRP 208 can be a distributed unit (DU). TRP 208 can be connected to a single ANC (e.g., ANC 202) or more ANCs (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific AND deployments, TRP 208 can be connected to more than one ANC. TRP 208 can each include one or more antenna ports. TRP 208 can be configured to serve the UE's traffic individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0055] The logical architecture of this distributed RAN 200 can support fronthaul solutions across different deployment types. For example, the logical architecture can be based on transmit network capabilities (e.g., bandwidth, latency, and / or jitter).

[0056] The logical architecture of this distributed RAN 200 can share features and / or components with LTE. For example, the next-generation access node (NG-AN) 210 can support dual connectivity with NR and can share common fronthaul for LTE and NR.

[0057] The logical architecture of distributed RAN 200 enables cooperation between TRPs 208, for example, within a TRP and / or across TRPs via ANC 202. Inter-TRP interfaces can be omitted.

[0058] Logical functions can be dynamically distributed within the logical architecture of the distributed RAN 200. The Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer can be adaptably placed at the DU (e.g., TRP 208) or CU (e.g., ANC 202).

[0059] Figure 3 An example physical architecture of a distributed RAN 300 according to various aspects of this disclosure is shown. A centralized core network unit (C-CU) 302 can host core network functions. The C-CU 302 can be deployed centrally. Functions of the C-CU 302 may be offloaded (e.g., to Advanced Wireless Services (AWS)) to handle peak capacity.

[0060] The centralized RAN unit (C-RU) 304 can host one or more ANC functions. Optionally, the C-RU 304 can host core network functions locally. The C-RU 304 can be deployed in a distributed manner. The C-RU 304 can be located close to the network edge.

[0061] The DU 306 can host one or more TRPs (Edge Nodes (EN), Edge Units (EU), Radio Headers (RH), Smart Radio Headers (SRH), etc.). The DU can be located at the edge of a network with radio frequency (RF) capabilities.

[0062] Figure 4 The BS 110a and UE 120a shown are examples of various aspects of this disclosure that can be used to implement the present disclosure. Figure 1 Example components described herein. For example, antenna 452, processors 466, 458, 464 and / or controller / processor 480 of UE 120a, and / or antenna 434, processors 420, 430, 438 and / or controller / processor 440 of BS 110a can be used to perform the functions described herein. Figure 15 , Figure 16 and Figure 17 The various techniques and methods described.

[0063] In BS 110a, the transmit processor 420 can receive data from data source 412 and control information from controller / processor 440. This control information can be used for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), etc. The data can be used for the Physical Downlink Shared Channel (PDSCH), etc. The processor 420 can process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor 420 can also generate reference symbols, for example, for the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Cell-Specific Reference Signal (CRS). The transmit (TX) Multiple-Input Multiple-Output (MIMO) processor 430 can perform spatial processing (e.g., pre-decoding) on ​​the data symbols, control symbols, and / or reference symbols (if applicable), and can provide an output symbol stream to modulators (MODs) 432a to 432t. Each modulator 432 can process its own output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from modulators 432a to 432t can be transmitted via antennas 434a to 434t, respectively.

[0064] At UE 120a, antennas 452a to 452r can receive downlink signals from base station 110a and can provide the received signals to demodulators (DEMODs) in transceivers 454a to 454r respectively. Each demodulator 454 can adjust (e.g., filter, amplify, downconvert, and digitize) the received signal individually to obtain input samples. Each demodulator can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 456 can obtain the received symbols from all demodulators 454a to 454r, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. Receiver processor 458 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120a to data sink 460, and provide decoding control information to controller / processor 480.

[0065] On the uplink, at UE 120a, the transmitting processor 464 can receive and process data from data source 462 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from the controller / processor 480 (e.g., for the Physical Uplink Control Channel (PUCCH)). The transmitting processor 464 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signals (SRS)). Symbols from the transmitting processor 464 can be pre-decoded (if applicable) by the TX MIMO processor 466, then further processed by demodulators in transceivers 454a to 454r (e.g., SC-FDM, etc.), and transmitted to base station 110a. At BS 110a, uplink signals from UE 120a can be received by antenna 434, processed by modulator 432, detected by MIMO detector 436 (if applicable), and further processed by receiving processor 438 to obtain decoded data and control information transmitted by UE 120a. The receiver processor 438 can provide the decoded data to the data sink 439 and the decoded control information to the controller / processor 440.

[0066] Controllers / processors 440 and 480 can direct operations at BS 110a and UE 120a, respectively. Processor 440 and / or other processors and modules at BS 110a can perform or direct operations as described herein. Figure 15 , Figure 16 and Figure 17 The execution of the process described in the technology.

[0067] In some cases, two or more subordinate entities (e.g., UEs) can communicate with each other using sidelink signaling. Real-world applications of such sidelink communication may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Things (IoE) communication, IoT communication, mission-critical meshes, and / or various other suitable applications. Typically, sidelink signaling can refer to a signal transmitted from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even if the scheduling entity is available for scheduling and / or control purposes. In some examples, licensed spectrum can be used to transmit sidelink signals (unlike wireless local area networks (WLANs) which typically use unlicensed spectrum).

[0068] Example UE to NW relay

[0069] This disclosure relates to various aspects of remote UEs, relay UEs, and networks, such as Figure 5 As shown, Figure 5This is a high-level path diagram illustrating example connection paths: the Uu path (cellular link) between the relay UE and the network gNB, and the PC5 path (D2D link) between the remote UE and the relay UE. The remote UE and the relay UE can be in Radio Resource Control (RRC) connection mode.

[0070] like Figure 6 and Figure 7 As shown, a remote UE can typically connect to a relay UE via a Layer 3 (L3) connection that has no Uu connection to the network (and is not visible to the network) or via a Layer 2 (L2) connection (the UE supports both Uu access layer (AS) and non-AS (NAS) connections to the network).

[0071] Figure 6 This is an example block diagram illustrating the control plane protocol stack on L3 when there is no direct connection path (Uu connection) between the remote UE and the network node. In this case, the remote UE does not have a Uu connection to the network and is connected to the relay UE only via a PC5 connection (e.g., Layer 3 UE to NW). In some implementations, the relay UE may require a PC5 unicast link setup to serve the remote UE. The remote UE may not have a Uu application server (AS) connection to the radio access network (RAN) via a relay path. In other cases, the remote UE may not have a direct no-access stratum (NAS) connection to the 5G core network (5GC). The relay UE can report the presence of the remote UE to the 5GC. Alternatively and optionally, the remote UE may be visible to the 5GC via a non-3GPP network interoperability function (N3IWF).

[0072] Figure 7 This is an example block diagram illustrating the control plane protocol stack on L2 when there is a direct connection path between the remote UE and the network node. This control plane protocol stack refers to the L2 relay option based on NR-V2X connectivity. Both the PC5 control plane (C plane) and the NR Uu C plane are on the remote UE, similar to... Figure 6 The PC5 C plane is shown. A unicast link can be established before the relay. Remote UEs can support NR Uu AS and NAS connections over PC5 Radio Link Control (RLC). NG-RAN can control the PC5 link of the remote UE via NR Radio Resource Control (RRC). In some embodiments, an adaptation layer may be required to support multiplexing of multiple UE traffic over the Uu connection of the relay UE.

[0073] Some systems (such as NR) can support standalone (SA) capabilities for sidelink-based UE-to-network and UE-to-UE relay communication, for example, by utilizing Layer 3 (L3) and Layer 2 (L2) relays as described above.

[0074] The specific relay procedure may depend on whether the relay is an L3 or an L2 relay. Figure 8 An example dedicated PDU session for L3 trunking is shown. In the scenario depicted, the remote UE establishes a PC5-S unicast link setup and obtains an IP address. PC5-RRC is used to manage the PC5 unicast link AS configuration. The trunk UE and the remote UE coordinate on the AS configuration. The trunk UE can consider information from the RAN when configuring the PC5 link. Authentication / authorization for the remote UE to access the trunk can be completed during PC5 link establishment. In the example shown, the trunk UE performs L3 trunking.

[0075] Figure 9 An example dedicated PDU session for L2 trunking is shown. In the scenario depicted, there is no PC5 unicast link setup prior to the trunking. The remote UE sends NRRRC messages on the PC5 signaling radio bearer (SRB) via the sidelink broadcast control channel (SBCCH). The RAN can independently indicate the PC5 AS configuration to both the remote UE and the trunking UE via NR RRC messages. Changes can be made to the NRV2X PC5 stack operations to support radio bearer processing in NR RRC / PDCP but also to support the corresponding logical channels in the PC5 link. In L2 trunking, the PC5 RLC may need to support direct interaction with NR PDCP.

[0076] Various issues need to be addressed in sidelink relay DRX scenarios. One issue involves support for relay discovery in remote UE sidelink DRX. In some cases, a common assumption for relay discovery is that the relay UE is only in connected mode, not idle / inactive mode. Remote UEs can be in connected, idle / inactive, or out-of-coverage (OOC) mode.

[0077] It can support relay selection and reselection for discovery. It may support different types of discovery models. For example, Figure 10A The first model (referred to as Model A discovery) is shown. In this case, the UE transmits a discovery message (notification), while other UEs perform monitoring. According to... Figure 10B The second model shown (referred to as Model B discovery) involves the UE (discoverer) sending a solicitation message and waiting for a response from the monitoring UE (discovery target). This discovery message can be transmitted over a PC5 communication channel (e.g., instead of a separate discovery channel). The discovery message can be carried within the same Layer 2 frame used for other direct communications, including, for example, a destination Layer 2 ID that can be set as a unicast, multicast, or broadcast identifier, a source Layer 2 ID that is always set as the sender's unicast identifier, and a frame type indicating that it is a ProSe direct discovery message.

[0078] As mentioned above, for relay selection, the remote UE is not connected to any relay node (i.e., no PC5 unicast link is established between the remote UE and the relay node). In this case, it may be desirable to design a DRX mode to reduce the power consumption of the remote UE when monitoring relay discovery messages for relay selection.

[0079] As described above, for trunk reselection, the remote UE is already connected to at least one trunk node (e.g., a PC5 unicast is established between the remote UE and the trunk node). For trunk reselection, it may be desirable to design a DRX configuration that helps reduce the power consumption of the remote UE while monitoring trunk reselection and PC5 data transmission trunk discovery messages.

[0080] Figure 11 An example environment is illustrated where a network entity serves a remote UE via a network relay (e.g., a relay UE). To communicate via a relay UE, a remote UE not yet connected to a relay node can discover the relay node and select one or more relay nodes as its relay. For example, a remote UE can discover all relay nodes whose sidelink discovery reference received signal power (SD-RSRP) is higher than a first threshold (e.g., higher than minHyst of q-Rx-LevMin). When a remote UE is already connected to a relay node, it can also reselect a relay. To do this, the remote UE can determine that its sidelink RSRP (SL-RSRP) is lower than a second threshold (e.g., lower than minHyst of q-Rx-LevMin) and, based on this determination, discover relay nodes whose SD-RSRP is higher than the first threshold.

[0081] Example state transitions in a sidelink layer 2 relay system

[0082] This disclosure provides apparatus, methods, processing systems, and computer-readable media for switching between idle or inactive states and connected states in a sidelink L2 relay system for remote and relay UEs. As will be described, these techniques enable remote UEs to switch between states while using a Layer 2 relay connection with a relay UE.

[0083] Figure 12A and Figure 12B An example scenario is shown where a UE communicates with a network entity (e.g., a gNB). Figure 12A and Figure 12B In both scenarios shown, the relay UE is within coverage area and is in one of the following states: RRC idle, inactive, or connected. Figure 12AIn the scenario shown, the remote UE is within the coverage area of ​​the network entity. Because the remote UE is within the coverage area, it can directly receive paging and System Information Blocks (SIBs) from the network entity via the Uu link. However, in Figure 12B In the scenario shown, the remote UE can be outside the coverage area of ​​the network entity. Because the remote UE is outside the coverage area and the relay UE is within the coverage area, the remote UE can connect to the relay UE and receive paging and SIBs from the network entity via the relay UE.

[0084] Figure 13 An example of a remote UE paging before connecting to a relay UE is shown. Before connecting to a relay UE, the UE may follow UE idle or inactive behavior, as it does when connecting to a network entity. For example, the UE may perform idle mode measurements and cell (re)selection. After receiving a Uu paging from the network entity, the UE may trigger Unified Access Control (UAC) and Radio Resource Configuration (RRC) setup or recovery, and may monitor the Uu connection for SIB updates. Remote UEs within the network entity's coverage area may receive paging from the network entity; however, remote UEs outside the network entity's coverage area that are not connected to a relay within the coverage area may not receive paging and SIBs from the network entity.

[0085] Figure 14 An example of a remote UE paging after establishing a trunk connection (e.g., after establishing a PC5 RRC connection) is shown. The remote UE can be configured by the gNB in ​​one of several paging modes. In direct paging, the remote UE can monitor Uu paging and SIB updates. Direct paging can be the default mode applied by the remote UE if no signaling indicating the paging mode to be used by the UE is received. Forwarded paging allows the remote UE to waive monitoring of Uu paging or SIB updates; instead, the trunk UE monitors the remote UE's paging and forwards the remote UE's paging to the remote UE. Adaptive paging allows switching between direct paging and forwarded paging based on the remote UE's request. Finally, the remote UE can be configured in a paging-free mode, in which neither the remote UE nor the trunk UE monitors the remote UE's Uu paging and / or SIB updates. Typically, the remote paging mode can be configured on a per-remote-UE basis, such as... Figure 14 As shown. For example, remote UE 3 can directly monitor Uu paging, while remote UEs 1 and 2 connected to the relay UE can rely on paging forwarding.

[0086] Various aspects of this disclosure may allow a remote UE to transition between an idle or inactive Radio Resource Control (RRC) state and a connected RRC state in a sidelink L2 relay system. Figure 15 , Figure 16 and Figure 17 Example operations for switching between idle or inactive states and connected states in a sidelink L2 relay system are shown from the perspectives of remote UE, relay UE, and network entity, respectively.

[0087] Figure 15 An example operation 1500 is shown that can be performed by a remote UE to receive a paging in a sidelink L2 relay system. As shown, operation 1500 begins at block 1502, where the remote UE receives an indication from one of the network entities or relay user equipments (UEs) to which the UE is connected to transition from a connected state to an idle or inactive state.

[0088] At box 1504, the remote UE transitions to an idle or inactive state in response to receiving the instruction.

[0089] Figure 16 Example operation 1600 is shown, which can be performed by a relay UE to transition between an idle or inactive state and a connected state in a sidelink L2 relay system and to forward paging to a remote UE connected to the relay UE. As shown, operation 1600 can begin at block 1602, where the relay UE, while in a connected state, determines that it will enter an idle or inactive state. This determination can be based on one of the detections of signaling from the network entity to which the relay UE is connected or a radio link failure event.

[0090] At box 1604, the relay UE enters an idle or inactive state, causing the remote UE connected to the relay UE to also switch from a connected state to an idle or inactive state.

[0091] Figure 17 Example operations that can be performed by a network entity to switch between an idle or inactive state and a connected state in a sidelink L2 relay system are shown. As shown, operation 1700 can begin at block 1702, where the network entity determines that a remote user equipment (UE) connected to the network entity via a relay UE will enter an idle or inactive state.

[0092] At box 1704, the network entity sends a signaling message to the remote UE to trigger the remote UE to enter an idle or inactive state.

[0093] At box 1706, after the network entity sends the signaling to trigger the remote UE to enter an idle or inactive state, it sends a signaling to the relay UE to trigger the relay UE to enter an idle or inactive state.

[0094] In some embodiments, transitioning between idle or inactive states and connected states for remote and relay UEs may not require inheriting signaling and procedural changes for the relay UE. The relay UE can operate in any state: RRC idle, RRC inactive, or RRC connected. Furthermore, the relay UE can use mechanisms provided in conventional RRC state transition procedures to perform RRC state transitions.

[0095] Figure 18 This is a table displaying feasible combinations of relay UE and remote UE states. Different remote UEs connected to the same relay can have different RRC states. For example, a remote UE can be in any of the following states: RRC idle, RRC inactive, or RRC connected. After the RRC state transition procedure, the state of the remote UE can be managed separately from the state of the relay UE, such as... Figure 18 As shown. For example, if the remote UE is in an idle or inactive state, the relay UE can be in any of the idle, inactive, or connected states. However, if the remote UE is in a connected state, the relay may not be able to transition to or remain in an idle or inactive state because when the relay UE is in an idle or inactive state, the RRC connection and bearer may be released at the relay UE. Therefore, if the relay UE is in an idle or inactive state, the remote UE may not be able to maintain its RRC connection with the network entity.

[0096] Figure 19 This diagram illustrates an example transition from a connected state to an idle or inactive state for a relay UE and a remote UE connected to it, based on signaling from a network entity, according to some embodiments. As shown, to implement the transition of the remote UE and its transition to an idle or inactive state, the network entity can send an RRC release message to the remote UE to transition it to an idle or inactive state. Once the remote UE is transitioned to an inactive state, the relay UE previously connected to it can be transitioned to an idle or inactive state by transmitting an RRC release message to the relay UE. Subsequently, when the remote UE attempts to enter a connected state, the relay UE can transition to a connected state (as discussed in further detail below).

[0097] Figure 20 This illustrates, according to some embodiments, an example transition of a relay UE and a remote UE connected to it from a connected state to an idle or inactive state, based on the autonomous transition of the relay UE to an idle state. As shown in the figure, Figure 20 It begins with a relay UE and each remote UE connected to a relay UE in a connected state. At some point, a relay UE can autonomously transition to an idle state. For example, a relay UE can autonomously transition to an idle state based on the detection of a radio link failure (RLF) and failure to re-establish a connection with a network entity.

[0098] After the relay UE autonomously transitions to an idle state, it reconfigures the remote UEs to cause them to transition to an idle state. The relay UE can, for example, send an RRCReconfigurationSidelink message to each remote UE connected to it. Upon receiving the RRCReconfigurationSidelink message, the remote UE can transition to an idle state.

[0099] At the network entity level, an inactivity timer may expire for the connection between the relay UE and the network entity. When the inactivity timer expires, the network entity can release the context and connection of the relay UE and its associated remote UE.

[0100] Figure 21 An example transition from an idle or inactive state to a connected state for a remote UE and its associated relay UE, according to some embodiments, is illustrated. As shown, the remote UE and relay UE can begin in an idle or inactive state, and the remote UE can send a request to the relay UE to set up or restore an RRC connection. This request can be, for example, an RRCSetupRequest or an RRCResumeRequest.

[0101] Receiving a request to set up or restore a connection can trigger a relay UE to enter the connected state. To enter the connected state, the relay UE can send a first connection setting up or restoration request to the network entity to establish or re-establish a connection between the relay UE and the network entity. Subsequently, the relay UE can send a second connection setting up or restoration request to the network entity to establish or re-establish a connection between a remote UE and the network entity.

[0102] In response to receiving first and second connection setup or recovery request messages from the relay UE, the network entity establishes a connection with both the relay UE and the remote UE, sends a first setup or recovery message to the relay UE, and sends a second setup or recovery message to the remote UE. The second setup or recovery message can be sent to the relay UE, and the relay UE can forward the second setup or recovery message to the remote UE. Based on the first and second setup or recovery messages, the remote UE and the relay UE can enter a connected state, and subsequently, the remote UE can perform transmissions with the network entity.

[0103] In some embodiments, to support mobility at a remote UE, when a remote UE attempts to transition from an idle or inactive state to a connected state, the remote UE may determine if a suitable relay UE is available for connection. If the remote UE determines that no suitable relay UE exists, it may attempt to send a setup or recovery request to a network entity to which it has previously connected via a relay UE. When connecting to a network entity, the remote UE may apply default physical (PHY) layer and / or media access control (MAC) layer configurations. If the remote UE attempts to transition from an inactive state, and the network entity to which the UE attempts to establish a connection is one to which the remote UE has previously connected via a relay UE, a UE context retrieval procedure may not be necessary. Otherwise, if the remote UE attempts to establish a connection with a network entity different from one to which the remote UE has previously connected via a relay UE, the new network entity may perform a context retrieval procedure to retrieve UE context information from the network entity to which the remote UE has previously connected via a relay UE.

[0104] When the relay UE is in idle mode and the remote UE is in inactive mode, the relay UE can monitor radio access network (RAN) paging and support forwarding paging to the remote UE. In some embodiments, an inactive relay UE can be prevented from entering idle mode and perform network access layer (NAS) recovery upon receiving a core network (CN) paging.

[0105] Figure 22 A communication device 2200 is shown, which may include operations configured to perform the techniques disclosed herein (such as...). Figure 15 The communication device 2200 includes various components (e.g., corresponding to component plus functional components) shown in the diagram. The communication device 2200 includes a processing system 2202 coupled to a transceiver 2208. The transceiver 2208 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 2200 via an antenna 2210. The processing system 2202 can be configured to enable the communication device 2200 to perform processing functions, including processing signals received and / or to be transmitted by the communication device 2200.

[0106] The processing system 2202 includes a processor 2204 coupled to a computer-readable medium / memory 2212 via a bus 2206. In some aspects, the computer-readable medium / memory 2212 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 2204, cause the processor 2204 to perform... Figure 15The operations shown may be other operations for receiving paging in a sidelink L2 relay system. In some aspects, the computer-readable medium / memory 2212 stores code 2214 for receiving an indication from one of the network entities or relay UEs to which the remote UE is connected, indicating a transition from a connected state to an idle or inactive state; and code 2216 for transitioning to an idle or inactive state in response to receiving the indication. In some aspects, the processor 2204 has circuitry configured to implement the code stored in the computer-readable medium / memory 2212. The processor 2204 includes circuitry 2218 for receiving an indication from one of the network entities or relay UEs to which the remote UE is connected, indicating a transition from a connected state to an idle or inactive state; and circuitry 2220 for transitioning to an idle or inactive state in response to receiving the indication.

[0107] Figure 23 A communication device 2300 is shown, which may include operations configured to perform the techniques disclosed herein (such as...). Figure 16 The communication device 2300 includes various components (e.g., corresponding to component plus functional components) shown in the diagram. The communication device 2300 includes a processing system 2302 coupled to a transceiver 2308. The transceiver 2308 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 2300 via an antenna 2310. The processing system 2302 can be configured to enable the communication device 2300 to perform processing functions, including processing signals received and / or to be transmitted by the communication device 2300.

[0108] The processing system 2302 includes a processor 2304 coupled to a computer-readable medium / memory 2312 via a bus 2306. In some aspects, the computer-readable medium / memory 2312 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 2304, cause the processor 2304 to perform... Figure 16The operations shown may be used to configure a remote UE for paging in a sidelink L2 relay scenario and other operations for processing paging data at the relay UE in a sidelink L2 relay scenario. In some aspects, the computer-readable medium / memory 2312 stores code 2314 for determining, when in a connected state, that the relay UE will enter an idle or inactive state based on the detection of one of signaling or radio link failure events from the network entity to which the relay UE is connected; and code 2316 for entering an idle or inactive state such that a remote UE connected to the relay UE also transitions from a connected state to an idle state. In some aspects, the processor 2304 has circuitry configured to implement the code stored in the computer-readable medium / memory 2312. The processor 2304 includes circuitry 2318 for determining, based on the detection of one of the signaling or radio link failure events from the network entity to which the relay UE is connected, that the relay UE will enter an idle or inactive state; and circuitry 2324 for entering an idle or inactive state such that a remote UE connected to the relay UE also transitions from a connected state to an idle state.

[0109] Figure 24 A communication device 2400 is shown, which may include operations configured to perform the techniques disclosed herein (such as...). Figure 17 The communication device 2400 includes various components (e.g., corresponding to component plus functional components) shown in the diagram. The communication device 2400 includes a processing system 2402 coupled to a transceiver 2408. The transceiver 2408 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 2400 via an antenna 2410. The processing system 2402 can be configured to enable the communication device 2400 to perform processing functions, including processing signals received and / or to be transmitted by the communication device 2400.

[0110] Processing system 2402 includes processor 2404 coupled to computer-readable medium / memory 2412 via bus 2406. In some aspects, computer-readable medium / memory 2412 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 2404, cause processor 2404 to perform... Figure 17The operations shown may be used to configure a remote UE and other operations for paging a remote UE in a side-link L2 relay scenario. In some aspects, the computer-readable medium / memory 2412 stores code 2414 for determining that a remote user equipment (UE) connected to a network entity via a relay UE will enter an idle or inactive state; code 2416 for sending a signaling message to the remote UE to trigger it into an idle or inactive state; and code 2418 for sending a signaling message to the relay UE to trigger it into an idle or inactive state after sending the signaling message to trigger the remote UE into an idle or inactive state. In some aspects, the processor 2404 has circuitry configured to implement the code stored in the computer-readable medium / memory 2412. The processor 2404 includes circuitry 2420 for determining that a remote user equipment (UE) connected to a network entity via a relay UE will enter an idle or inactive state; circuitry 2422 for sending a signaling message to the remote UE to trigger the remote UE to enter an idle or inactive state; and circuitry 2424 for sending a signaling message to the relay UE to trigger the relay UE to enter an idle or inactive state after sending the signaling message to trigger the remote UE to enter an idle or inactive state.

[0111] The methods disclosed herein include one or more steps or actions for implementing the methods. The method steps and / or actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of a particular step and / or action may be modified without departing from the scope of the claims.

[0112] As used herein, the phrase “at least one” in a list of items refers to any combination of those items containing a single member. As an example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).

[0113] As used herein, the term "determine" encompasses a variety of actions. For example, "determine" can include calculation, operation, processing, derivation, investigation, search (e.g., searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Additionally, "determine" can include parsing, selecting, picking, building, etc.

[0114] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various variations of these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be given the full scope consistent with the language of the claims, wherein, unless expressly stated otherwise, elements referred to in the singular are not intended to mean “one and only one,” but rather “one or more.” Unless expressly stated otherwise, the term “some” means one or more. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known or will be known hereafter by a person skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, whether or not the contents of this disclosure are expressly recited in the claims, they are not intended to be disclosed to the public. No claim element is to be construed under the provisions of 35 U.S.SC §112(f) unless the element is expressly stated using the phrase “component for…” or, in the case of a method claim, using the phrase “step for…”.

[0115] The various operations described above can be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or multiple software components and / or multiple modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. Typically, where operations as shown in the figures are performed, those operations may have corresponding components plus functional components. For example, Figure 15 , Figure 16 and Figure 17 The various operations shown can be performed by Figure 4 The various processors shown (such as processors 466, 458, 464 and / or controller / processor 480 of UE 120a) are used to perform this.

[0116] The various illustrative logic blocks, modules, and circuits disclosed herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, it may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors integrated with a DSP core, or any other such configuration.

[0117] If implemented in hardware, the example hardware configuration could include a processing system in a wireless node. This processing system could be implemented using a bus architecture. The bus could include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the processing system. The bus could link together various circuits, including a processor, machine-readable media, and a bus interface. The bus interface could be used to connect network adapters, etc., to the processing system via the bus. The network adapter could be used to implement signal processing functions at the PHY layer. In user terminal 120 (see...) Figure 1 In this case, a user interface (e.g., keyboard, display, mouse, joystick, etc.) can also be connected to the bus. This bus can also link various other circuits well known in the art, such as timing sources, peripherals, voltage regulators, power management circuits, etc., and therefore will not be described further. The processor can be implemented using one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Those skilled in the art will recognize how best to implement the described functions for the processing system based on the specific application and the overall design constraints imposed on the system as a whole.

[0118] If implemented in software, the functionality can be stored or transmitted as one or more instructions or code on or through a computer-readable medium. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, software should be broadly interpreted as instructions, data, or any combination thereof. Computer-readable media includes computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of a computer program from one location to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor, allowing the processor to read information from and write information to the storage medium. Alternatively, the storage medium may be integrated with the processor. For example, the machine-readable medium may include a transmission line, a carrier wave modulated by data, and / or a computer-readable storage medium on which instructions separate from the wireless node are stored, all of which may be accessible by the processor via a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, such as in cases where it may have a cache and / or a general-purpose register file. Examples of machine-readable storage media may include, for example, RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, disks, optical disks, hard disks, or any other suitable storage media, or any combination thereof. The machine-readable medium may be included in a computer program product.

[0119] A software module may include a single instruction or multiple instructions and may be distributed across several different code segments, different programs, and multiple storage media. The computer-readable medium may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause the processing system to perform various functions. The software module may include transfer modules and receive modules. Each software module may reside in a single storage device or be distributed across multiple storage devices. For example, when a trigger event occurs, a software module may be loaded from a hard disk drive into RAM. During the execution of a software module, the processor may load some instructions into a cache to improve access speed. One or more cache lines may then be loaded into a general-purpose register file for processor execution. When the functionality of a software module is mentioned below, it will be understood that this functionality is implemented by the processor when executing the instructions from that software module.

[0120] Furthermore, any connection is appropriately referred to as computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, the definition of medium includes coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave. The disks and optical discs used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and... Optical discs, where magnetic disks typically copy data magnetically, copy data optically using lasers. Therefore, in some aspects, computer-readable media can include non-transitory computer-readable media (e.g., tangible media). Furthermore, in other aspects, computer-readable media can include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0121] Therefore, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored thereon (and / or encoded thereon) that can be executed by one or more processors to perform the operations described herein. For example, for performing the operations described herein and in… Figure 15 , 16 The instructions for the operations described in section 17.

[0122] Furthermore, it should be understood that modules and / or other suitable components for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by the user terminal and / or base station where applicable. For example, such a device may be coupled to a server to facilitate the transfer of components for performing the methods described herein. Alternatively, the various methods described herein may be provided by storage components (e.g., RAM, ROM, physical storage media such as CDs or floppy disks, etc.), allowing the user terminal and / or base station to obtain the various methods by coupling or providing the storage components to the device. Furthermore, any other suitable techniques for providing the methods and techniques described herein to the device may be utilized.

[0123] It should be understood that the claims are not limited to the precise configuration and components described above. Various modifications, alterations, and variations may be made to the arrangement, operation, and details of the described methods and apparatus without departing from the scope of the claims.

Claims

1. A method for wireless communication by a remote user equipment (UE), comprising: Receive an indication from one of the network entities or relay UEs to which the remote UE is connected in a transition from a connected state to an idle or inactive state in sidelink communication; as well as In response to receiving the instruction, the remote UE transitions to an idle or inactive state, wherein, when the relay UE is in a connected state, the remote UE transitions from the connected state to an idle or inactive state.

2. The method according to claim 1, wherein, The indication of transitioning from a connected state to an idle or inactive state includes a Radio Resource Control (RRC) release message received from the network entity.

3. The method according to claim 2, wherein, When the relay UE is in a connected state, the RRC release message is received via the relay UE.

4. The method according to claim 1, wherein, The indication of transitioning from a connected state to an idle or inactive state includes a sidelink radio resource control (RRC) reconfiguration message received from the relay UE.

5. The method according to claim 4, wherein, When the sidelink RRC reconfiguration message is received, the relay UE is in a connected state.

6. The method according to claim 1, further comprising: When the remote UE is idle or inactive, a request to establish or restore a connection with the network entity is sent to the relay UE. as well as After sending the request, the relay UE receives a setting or recovery message from the network entity; and Upon receiving the setting or recovery message from the network entity via the relay UE, the system enters a connected state.

7. The method according to claim 6, wherein, The request to establish or restore a connection is sent to the network entity via the relay UE.

8. The method according to claim 1, further comprising: Attempt to transition from an idle state to a connected state; It has been determined that there is no suitable relay UE; as well as Use the default physical PHY layer or media access layer MAC layer configuration to directly send setup or recovery request messages to the network entity.

9. The method according to claim 1, further comprising: Attempt to transition from an idle state to a connected state; It has been determined that there is no suitable relay UE; as well as Send a setup or recovery request message to another network entity using the default physical PHY layer or media access layer MAC layer configuration.

10. A method for wireless communication by a relay user equipment (UE), comprising: After a remote UE connected to the relay UE enters an idle or inactive state, a signaling message triggering the relay UE to enter an idle or inactive state is received from the network entity connected to the relay UE. as well as In response to receiving the signaling, it enters an idle or inactive state.

11. The method according to claim 10, wherein, The signaling includes a Radio Resource Control (RRC) release message received from the network entity after an RRC release message has been sent to a remote UE connected to the relay UE.

12. The method of claim 10, further comprising: Based on the detection of a radio link failure event, an attempt is made to re-establish the connection with the network entity; The attempt to re-establish the connection with the network entity has failed; as well as Based on the determination that the attempt to re-establish the connection with the network entity has failed, a reconfiguration message is sent to the remote UE connected to the relay UE to put the remote UE into an idle state.

13. The method according to claim 12, wherein, The reconfiguration message includes a sidelink radio resource control (RRC) reconfiguration message transmitted to each of the remote UEs.

14. The method of claim 10, further comprising: When in a connected state, a request to set or restore the connection with the network entity is received from a remote UE that is in an idle or inactive state; Send a setting or recovery request to the remote UE to the network entity; In response to sending the setting or recovery request, the remote UE is received with a setting or recovery message.

15. The method of claim 10, further comprising: When in an idle or inactive state, a request to set or restore the connection with the network entity is received from a remote UE that is in an idle or inactive state. Send a setting or recovery request to the network entity for the relay UE and the remote UE; In response to sending the setting or recovery request, the system receives setting or recovery messages from the relay UE and the remote UE. as well as Upon receiving the setting or recovery message from the relay UE and the remote UE, the system enters a connection state.

16. The method of claim 15, further comprising: The remote UE is forwarded a setting or recovery message to the remote UE to trigger the remote UE to enter the connected state.

17. The method of claim 10, further comprising: When in an idle state, monitor the radio access network (RAN) paging of the remote UE; as well as Forward the RAN paging for the remote UE to the remote UE.

18. The method according to claim 1, further comprising: When inactive, monitor the paging of the remote UE's core network (CN). as well as It is determined that the relay UE does not enter an idle state; as well as Forward the CN paging for the remote UE to the remote UE.

19. A method for wireless communication by a network entity, comprising: It is determined that a remote user equipment (UE) connected to the network entity via a relay UE will enter an idle or inactive state; Send a signaling message to the remote UE to trigger the remote UE to enter an idle or inactive state; as well as After sending the signaling to trigger the remote UE to enter an idle or inactive state, a signaling is sent to the relay UE to trigger the relay UE to enter an idle or inactive state.

20. The method of claim 19, further comprising: Receive a first request from the relay UE to set or restore the connection between the relay UE and the network entity; Receive a second request from the relay UE to set or restore the connection between the network entity and the remote UE; In response to the first request, a first setting or recovery message is sent to the relay UE to establish a connection between the relay UE and the network entity; as well as In response to the first request, a second setup or recovery message is sent to the relay UE for forwarding to the remote UE to establish a connection between the remote UE and the network entity.

21. The method of claim 19, further comprising: A request to establish or restore a connection between a second remote UE and the network entity is received from a second remote UE that has not previously connected to the network entity via the relay UE; as well as A context retrieval procedure is performed with the second network entity of the second remote UE, wherein the second network entity includes the network entity to which the second remote UE was previously connected.

22. An apparatus for wireless communication by a remote user equipment (UE), comprising: The processor is configured as follows: Receive an indication from one of the network entities or relay UEs to which the remote UE is connected during sidelink communication, indicating a transition from a connected state to an idle or inactive state; and In response to receiving the indication, the remote UE transitions to an idle or inactive state, wherein, if the relay UE is in a connected state, the remote UE transitions from the connected state to an idle or inactive state; and Memory.

23. An apparatus for wireless communication by a relay user equipment (UE), comprising: The processor is configured as follows: After a remote UE connected to the relay UE enters an idle or inactive state, a signaling message triggering the relay UE to enter an idle or inactive state is received from the network entity connected to the relay UE. as well as In response to receiving the signaling, it enters an idle or inactive state; as well as Memory.

24. An apparatus for wireless communication by a network entity, comprising: The processor is configured as follows: It is determined that a remote user equipment (UE) connected to the network entity via a relay UE will enter an idle or inactive state; Send a signaling message to the remote UE to trigger the remote UE to enter an idle or inactive state; as well as After sending the signaling to trigger the remote UE to enter an idle or inactive state, a signaling is sent to the relay UE to trigger the relay UE to enter an idle or inactive state; as well as Memory.

25. An apparatus for wireless communication by a remote user equipment (UE), comprising: A component for receiving an indication from one of the network entities or relay UEs to which the remote UE is connected during sidelink communication that the UE has transitioned from a connected state to an idle or inactive state. as well as A component for switching to an idle or inactive state in response to receiving the instruction, wherein, when the relay UE is in a connected state, the remote UE switches from the connected state to an idle or inactive state.

26. An apparatus for wireless communication by a relay user equipment (UE), comprising: A component for receiving, from a network entity connected to a relay UE, signaling that triggers the relay UE to enter an idle or inactive state after the remote UE connected to the relay UE enters an idle or inactive state; as well as A component used to enter an idle or inactive state in response to receiving the signaling.

27. An apparatus for wireless communication by a network entity, comprising: A component used to determine whether a remote user equipment UE connected to the network entity via a relay UE will enter an idle or inactive state; A component for sending a signaling message to the remote UE to trigger the remote UE to enter an idle or inactive state; as well as A component for sending a signaling message to the relay UE to trigger the relay UE to enter an idle or inactive state after sending the signaling message to trigger the remote UE to enter an idle or inactive state.

28. A computer-readable medium having instructions stored thereon, the instructions being executable by a processor to implement the method of any one of claims 1 to 9.

29. A computer-readable medium having instructions stored thereon, the instructions being executable by a processor to implement the method of any one of claims 10 to 18.

30. A computer-readable medium having instructions stored thereon, the instructions being executable by a processor to implement the method of any one of claims 19 to 21.

Images