Handling end-to-end PC5 connections in U2U trunks

By setting a channel quality threshold in UE-to-UE relays to trigger relay selection or reselection, the problem of degraded UE-to-UE relay communication link quality in existing technologies is solved, achieving a more stable and efficient end-to-end PC5 connection.

CN123077262APending Publication Date: 2026-11-10LENOVO (BEIJING) LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090736.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-04-10
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In existing technologies, there is a lack of effective threshold mechanisms to trigger relay selection or reselection in UE-to-UE relay scenarios, which leads to a decline in communication link quality and affects the stability and efficiency of end-to-end PC5 connections.

Method used

By setting a channel quality threshold between the first UE and the second UE, relay selection or reselection is triggered based on channel quality falling below the threshold, and associated operations such as releasing the radio link or adjusting the communication configuration are performed to ensure the stability of the end-to-end PC5 connection.

Benefits of technology

It improves the link quality and stability of UE-UE relay communication, ensures the reliability and efficiency of end-to-end PC5 connections, and adapts to changes in dynamic network environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123077262A_ABST
    Figure CN123077262A_ABST
Patent Text Reader

Abstract

This disclosure relates to exemplary embodiments of a first UE, a second UE, a method, apparatus, and a computer-readable medium for processing an end-to-end PC5 connection in a U2U relay. In this solution, a first UE, acting as a remote UE in a U2U relay scenario, can determine the channel quality of the link between the first UE and a second UE (e.g., a relay UE), and if the channel quality is below a threshold used to trigger relay selection or reselection, at least one operation associated with the end-to-end connection can be further performed. Thus, the threshold can be used as a condition for at least one operation associated with the end-to-end connection.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically, to network elements, methods, apparatus, and computer-readable media for processing end-to-end proximity communication 5 (PC5) connections in UE-UE (U2U) relays. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] The UE-to-UE (U2U) relay scenario has been discussed in the 3rd Generation Partnership Project (3GPP). A remote UE (also known as a source UE) can communicate with another remote UE (also known as a peer remote UE or target UE) via a relay UE. At least one threshold for triggering relay selection or reselection has been configured; however, more aspects of the threshold can be considered further. Summary of the Invention

[0004] This disclosure relates to a first UE, a second UE, a method, an apparatus, and a computer-readable medium for processing end-to-end PC5 connections in a U2U trunk. According to the proposed solution, a threshold used to trigger trunk selection or reselection can be used as a condition for other operations associated with the end-to-end PC5 connection.

[0005] In some implementations, a first UE is provided. The first UE includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the first UE: determines the channel quality of a link between the first UE and a second UE, wherein an end-to-end PC5 connection has been established between the first UE and a third UE via the second UE; triggers relay selection or reselection for the end-to-end PC5 connection based on the determination that the channel quality is below a threshold; and performs at least one operation associated with the end-to-end PC5 connection based on the determination that the channel quality is below the threshold.

[0006] In some implementations, a second UE is provided. The second UE includes at least one memory; and at least one processor coupled to the at least one memory, and configured such that the second UE: determines that a release condition for the link between the second UE and the third UE is met or a sidelink radio link failure (RLF) occurs, wherein an end-to-end PC5 connection has been established between the first UE and the third UE via the second UE; and sends a message to the first UE, which is a release message or a notification message.

[0007] In some implementations, a first UE is provided. The first UE includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the first UE: receives a message from a second UE, the message being a release message or a notification message, wherein an end-to-end PC5 connection has been established between the first UE and a third UE via the second UE; and performs at least one operation associated with the end-to-end PC5 connection based on the message.

[0008] In some implementations, a method is provided performed by a first UE. The method includes: determining the channel quality of a link between the first UE and a second UE, wherein an end-to-end PC5 connection has been established between the first UE and a third UE via the second UE; triggering relay selection or reselection for the end-to-end PC5 connection based on the determination that the channel quality is below a threshold; and performing at least one operation associated with the end-to-end PC5 connection based on the determination that the channel quality is below the threshold.

[0009] In some implementations, a method is provided that is executed by a second UE. The method includes: determining that a release condition for the link between the second UE and a third UE is met or a sidelink RLF occurs, wherein an end-to-end PC5 connection has been established between the first UE and the third UE via the second UE; and sending a message to the first UE, which is either a release message or a notification message.

[0010] In some implementations, a method is provided performed by a first UE. The method includes: receiving a message from a second UE, the message being a release message or a notification message, wherein an end-to-end PC5 connection has been established between the first UE and a third UE via the second UE; and performing at least one operation associated with the end-to-end PC5 connection based on the message.

[0011] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured to: determine the channel quality of a link between a first UE and a second UE, wherein an end-to-end PC5 connection has been established between the first UE and a third UE via the second UE; trigger relay selection or reselection for the end-to-end PC5 connection based on the determination that the channel quality is below a threshold; and perform at least one operation associated with the end-to-end PC5 connection based on the determination that the channel quality is below the threshold.

[0012] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured to: determine that a release condition for a link between a second UE and a third UE is satisfied or a sidelink RLF occurs, wherein an end-to-end PC5 connection has been established between the first UE and the third UE via the second UE; and send a message to the first UE, the message being a release message or a notification message.

[0013] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured to: receive a message from a second UE, the message being a release message or notification message, wherein an end-to-end PC5 connection has been established between a first UE and a third UE via the second UE; and perform at least one operation associated with the end-to-end PC5 connection based on the message.

[0014] The methods described herein and some implementations of the first UE also include: maintaining the U2U relay configuration after initiating the RRC connection reconstruction process, wherein the U2U relay configuration is received from the serving base station after the end-to-end PC5 connection has been established; and reporting the UE to the UE relay configuration to the reconstructed gNB after the reconstruction process is completed.

[0015] The methods described herein and some implementations of the first UE also include: releasing the U2U relay configuration after initiating the RRC connection reconstruction process, wherein the U2U configuration is received from the serving base station after the end-to-end PC5 connection has been established; and using additional U2U relay configurations from system information while a timer associated with cell selection or reselection is running, or another timer associated with the reconstruction request is running.

[0016] In the methods described herein, and in some implementations of the first UE and the second UE, channel quality is determined based on measurements of communication data, and the thresholds include the side link reference signal received power (SL-RSRP) threshold.

[0017] In the methods described herein, and in some implementations of the first UE and the second UE, channel quality is determined based on measurements of discovery messages, and the thresholds include the sidelink discovery reference signal received power (SD-RSRP) threshold.

[0018] In the methods described herein, and in some implementations of the first UE and the second UE, at least one operation includes one of the following: releasing the Radio Link Control (RLC) entity, or releasing a logical channel associated with an RLC channel identity (ID) for a specific destination.

[0019] In the methods described herein, and in some implementations of the first UE and the second UE, at least one operation includes: sending a release message or a notification message to the second UE.

[0020] In the methods described herein, and in some implementations of the first UE and the second UE, the release condition includes: an indication from the upper layer to the Radio Resource Control (RRC) layer for releasing the RRC connection between the second UE and the third UE.

[0021] In the methods described herein, and in some implementations of the first UE and the second UE, the release condition includes: receiving an additional release message or an additional notification message from the third UE.

[0022] In the methods described herein, and in some implementations of the first UE and the second UE, the notification message includes an indication type, and the indication type indicates the release reason.

[0023] In the methods described herein, and in some implementations of the first UE and the second UE, the message indicates the side link RLF of the link between the second UE and the third UE.

[0024] In some implementations of the methods described herein, the first UE, and the second UE, at least one operation includes one of the following: determining a failure of the end-to-end PC5 connection, releasing the end-to-end data radio bearer (DRB) for the end-to-end PC5 connection, releasing the end-to-end signaling radio bearer (SRB) for the end-to-end PC5 connection, or discarding the end-to-end side link communication-related configuration for the end-to-end PC5 connection.

[0025] In the methods described herein, and in some implementations of the first UE and the second UE, at least one operation includes determining that the RRC connection is released for the end-to-end PC5 connection, or indicating the release of the RRC connection from the RRC layer to the upper layer.

[0026] In the methods described herein, and in some implementations of the first UE and the second UE, the release message includes a PC5-S (Proximity Communication 5) signaling layer release message, and the notification message includes an RRC layer notification message. Attached Figure Description

[0027] Figure 1 Examples of wireless communication systems in which some embodiments of the present disclosure may be implemented are illustrated;

[0028] Figure 2A The illustration shows a schematic diagram of an example communication network in which some embodiments of the present disclosure may be implemented;

[0029] Figure 2B The diagram illustrates the example RRC reconfiguration process on the traverse side;

[0030] Figure 2C The diagram illustrates an example procedure for establishing an L2 U2U remote UE connection;

[0031] Figure 2D The illustration shows a schematic diagram of an example communication network in which some embodiments of the present disclosure may be implemented;

[0032] Figure 3 The diagram illustrates a signaling process according to some example embodiments of the present disclosure;

[0033] Figure 4 The diagram illustrates a signaling process according to some example embodiments of the present disclosure;

[0034] Figure 5 Examples of devices suitable for implementing embodiments of the present disclosure are illustrated;

[0035] Figure 6 Examples of processors suitable for implementing some embodiments of the present disclosure are illustrated;

[0036] Figure 7The illustration shows a flowchart of an example method implemented at a first UE according to various aspects of this disclosure;

[0037] Figure 8 The diagram illustrates a flowchart of an example method implemented at a second UE according to various aspects of this disclosure; and

[0038] Figure 9 A flowchart illustrating an example method implemented at a first UE according to various aspects of this disclosure is shown.

[0039] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0040] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not impose any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0041] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the described embodiments(s) may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same(s) embodiments(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that in conjunction with other embodiments (whether explicitly described or not) affecting such a feature, structure, or characteristic is within the scope of their knowledge.

[0042] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, processes, or apparatus are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a choice can be made among many functional alternatives used, and that such a choice need not be better, smaller, higher, or more desirable than other choices.

[0043] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein also include the plural forms. Furthermore, it should be understood that the terms “comprising,” “including,” “having,” “having,” “including,” and / or “containing” as used herein specify the presence of the stated features, elements, components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can mean “A only” or “B only” or “both A and B.” Other explicit and implicit definitions may be included below.

[0044] Figure 1 Examples of wireless communication systems 100 that may be implemented in some embodiments of this disclosure are illustrated. Wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. Wireless communication system 100 may support various radio access technologies. In some implementations, wireless communication system 100 may be a 4G network, such as a Long Term Evolution (LTE) network or an Advanced LTE (LTE-A) network. In some other implementations, wireless communication system 100 may be a 5G network, such as a New Radio (NR) network. In other implementations, wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. Wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0045] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. The network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RAN), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0046] Network entity 102 may provide a geographic coverage area 112 for which it may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned in the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0047] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0048] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1 It is shown in the middle. For example... Figure 1 As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UE 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Alternatively or additionally, UE 104 can support communication with other network entities 102 or UE 104, which can act as relays in the wireless communication system 100.

[0049] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidelink (SL). For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0050] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0051] In some implementations, network entity 102 can be configured in a decomposed architecture that can utilize a protocol stack physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0052] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in the decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in the decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0053] The functional division among CU, DU, and RU can be flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU. For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, while the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC), Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0054] Alternatively, or alternatively, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, while RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU or between DU and RU can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of CU, DU, or RU, while other functions of the protocol layer are performed by a different one of CU, DU, or RU).

[0055] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1c, F1-u), while the DUs can be connected to one or more RUs via front-end communication links (e.g., open front-end (FH) interfaces). In some implementations, the mid-range or front-end communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack, supported by corresponding network entities 102 communicating via such communication links.

[0056] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core network (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Functions (AMF)) and user plane entities that route or interconnect packets to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Functions (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0057] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 can communicate with application server 118. UE 104 can establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session can be one example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0058] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more parameter sets.

[0059] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. The first parameter set (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the normal cyclic prefix. In some implementations, the first set of parameters (e.g., ) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. The second parameter set (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. The third parameter set (e.g., μ =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. The fourth parameter set (e.g., μ =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth parameter set (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0060] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0061] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the parameter set. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the parameter set. It should be understood that for a first parameter set (e.g., quantity) associated with a first subcarrier spacing (e.g., 15 kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.

[0062] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for short-range, high data rate capabilities.

[0063] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the following: the first parameter set (e.g., μ =0), which includes a 15 kHz subcarrier spacing; the second parameter set (e.g., μ =1), which includes a 30 kHz subcarrier spacing; the third parameter set (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with the following: a third parameter set (e.g., μ =2), which includes a 60 kHz subcarrier spacing; the fourth parameter set (e.g., μ =3), which includes a subcarrier spacing of 120 kHz.

[0064] In the context of this disclosure, the term "Proximity Communication 5 (PC5) link" is interchangeable with PC5 interface, side link (SL), PC5 unicast link, SL unicast link, device-to-device (D2D) link, user-to-user link, UE-to-UE (U2U) link, etc. The term "relay UE" is interchangeable with U2U relay UE, Layer 2 (L2) relay UE, L2 U2U relay UE, etc. The term "relay UE ID" is interchangeable with link ID, path ID, L2 relay UE ID, etc. The term "remote UE" is interchangeable with U2U remote UE, L2 remote UE, L2 U2U remote UE, etc.

[0065] A wireless communication system may include one or more devices, such as one or more base stations and / or one or more UEs. In some implementations, two different UEs may communicate with each other via a PC5 link (PC5 interface), two different base stations may communicate with each other via an Xn link (Xn interface), and UEs and base stations may communicate with each other via a Uu link (Uu interface).

[0066] Figure 2A The illustration shows a schematic diagram of an example communication network 210 in which some embodiments of this disclosure can be implemented. For example... Figure 2A As shown, UE 211 can communicate with the base station via a relay UE. The base station can be gNB 212 or NG-eNB 213, and the relay UE can be relay UE 214 or relay UE 215. For example, NG-eNB 213 can be an evolved LTE (eLTE) base station supporting the NG interface. In some embodiments, sidelink transmission and reception on the PC5 link are supported when UE 211 is within the coverage area of ​​the Next Generation Radio Access Network (NG-RAN), regardless of the UE's RRC state, and are also supported when UE 211 is outside the NG-RAN coverage area.

[0067] For PC5 communication between two different UEs, the control plane protocol stack can include multiple layers, such as the access layer (AS), PC5 signaling (PC5-S), and RRC layer.

[0068] Figure 2B The diagram illustrates example RRC reconfiguration on the traverse side, procedure 220. (As shown...) Figure 2B As shown, UE 221 can send a reconfiguration message for the side link to UE 222 (e.g., RRCReconfigurationSidelink Message), and UE 222 can send a reconfiguration complete message to UE 221 (e.g., RRCReconfigurationCompleteSidelink information).

[0069] The purpose of procedure 220 is to modify the PC5-RRC connection, for example, to establish / modify / release the side-link data radio bearer (DRB), configure NR side-link measurements and reporting, and configure side-link channel state indicator (CSI) reference signal resources.

[0070] A UE (such as UE 221) can initiate a sidelink RRC reconfiguration procedure and perform operations on the corresponding PC5-RRC connection in the following situations: - Release of sidelink DRBs associated with peer UEs (such as UE 222), - Establishment of the side-link DRB associated with the peer UE, - Modifications to parameters included in the sidelink radio bearer configuration (SLRB-Config) of the sidelink DRB associated with the peer UE. - Configuration used to perform NR-side link link measurements and reporting for peer UEs. - Configuration of side link CSI reference signal resources.

[0071] L2 U2U remote UEs need to establish an end-to-end SL-SRB / DRB with their peer L2 U2U remote UEs before transmitting data in the user plane. Figure 2C The illustration shows an example procedure 230 for establishing an L2 U2U remote UE connection, which is applicable to both L2 U2U relay UEs and L2 U2U remote UEs.

[0072] Step 1. The L2 U2U remote UE, L2 U2U relay UE, and peer L2 U2U remote UE perform a discovery procedure or an integrated discovery procedure.

[0073] Step 2a. L2 U2U remote UE establishes / modifies PC5-RRC connection with the selected L2 U2U trunk UE.

[0074] Step 2b. The L2 U2U relay UE establishes / modifies the PC5-RRC connection with the peer L2 U2U remote UE.

[0075] Step 3. The L2 U2U relay UE is assigned two local IDs, which are delivered to each of the L2 U2U remote UEs via an RRCReconfigurationSidelink message: one local ID identifies the L2 U2U remote UE, and the other local ID identifies the peer L2 U2U remote UE. When the local IDs are delivered, the L2 IDs of the peer L2 U2U remote UEs are also delivered to the U2U remote UEs for association between the local IDs and the L2 IDs of the peer U2U remote UEs.

[0076] Step 4. The L2 U2U remote UE establishes an end-to-end PC5-RRC connection with its peer L2 U2U remote UE via the L2 U2U relay UE. For end-to-end connection establishment, fixed indices (i.e., 0 / 1 / 2 / 3) are defined separately for end-to-end SL-SRB 0 / 1 / 2 / 3, and the PC5 relay RLC channel configuration is specified to be used on each hop. Sidelink UE capabilities are exchanged between the L2 U2U remote UEs via PC5-RRC (e.g., SL-SRB3) messages.

[0077] Step 5. The L2 U2U remote UE sends all QoS profiles for the end-to-end QoS flow to the L2 U2U relay UE via PC5-RRC.

[0078] Step 6. L2 U2U relay UEs perform QoS splitting only for PDBs.

[0079] Step 7. The L2 U2U relay UE sends the split QoS value (i.e., PDB) to the L2 U2U remote UE via a PC5-RRC message. Step 8. The L2 U2U remote UE or its serving gNB derives the PDCP and SDAP configuration for the end-to-end SL-DRB and provides the receiving-related configuration portion to the peer L2 U2U remote UE using an end-to-end RRCReconfigurationSidelink message. The end-to-end bearer ID for the SL-SRB and SL-DRB is used as input for L2 U2U relay encryption and decryption at the PDCP.

[0080] Step 9a. The L2 U2U remote UE or the serving gNB of the L2 U2U remote UE derives the first-hop configuration for the SL-DRB (e.g., PC5 relay RLC channel configuration) and provides the L2 U2U relay UE with the configuration related to reception on the first hop (i.e., Rx performed by the relay UE) using a per-hop RRCReconfigurationSidelink message.

[0081] Step 9b. The L2 U2U relay UE or the serving gNB of the L2 U2U relay UE derives the second-hop configuration for each SL-DRB (e.g., PC5 relay RLC channel configuration) and provides the peer L2 U2U remote UE with the configuration related to receiving data packets on the second hop (i.e., RX performed by the peer remote UE) using the per-hop RRCReconfigurationSidelink message.

[0082] Step 10. The L2 U2U remote UE and the peer L2 U2U remote UE send or receive data via the L2 U2U relay UE.

[0083] Embodiments of this disclosure provide a communication solution. In this solution, a first UE, acting as a remote UE in a U2U relay scenario, can determine the channel quality of the link between the first UE and a second UE (e.g., a relay UE). If the channel quality is lower than a threshold used to trigger relay selection or reselection, at least one operation associated with the end-to-end connection can be further performed. Thus, the threshold can be used as a condition for at least one operation associated with the end-to-end connection. Therefore, communication of the remote UE can be guaranteed. The principles and implementation of this disclosure will now be described in detail with reference to the accompanying drawings.

[0084] Figure 2D The illustration shows a schematic diagram of an example communication network 240 in which some embodiments of this disclosure can be implemented. For example... Figure 2D As shown, the communication network 240 may include a first UE 241, a second UE 242, and a third UE 243.

[0085] The first UE 241 and the third UE 243 can communicate with each other via the second UE 242. For example, the first UE 241 and the third UE 243 are remote UEs, and the second UE 242 is a relay UE.

[0086] exist Figure 2D The diagram also illustrates a BS 250, such as a gNB. For example, the BS 250 could be the serving gNB of the first UE 241. For example, the BS 250 could communicate with the first UE 241 via a Uu link. It should be understood that [the following is unclear and likely refers to a different BS 250]. Figure 2D The third UE 243 service gNB is not shown in the image.

[0087] In some cases, such as Figure 2D As shown, there may be a candidate relay UE 245. For example, relay reselection can be performed, and the candidate relay UE 245 will be used as the relay UE for communication between the first UE 241 and the second UE 242.

[0088] It should be understood that Figure 2D The number of devices is given for illustrative purposes and does not imply any limitation on this disclosure.

[0089] In this disclosure, the release message can be generated by the PC5-S layer of the UE, and can also be referred to as PC5-S release message, PC5-S layer release message, PC5 unicast link release message, etc., but this disclosure is not limited to this aspect.

[0090] In this disclosure, the notification message can be generated by the UE's RRC layer and can also be referred to as an RRC layer notification message, such as... NotificationMessageSidelink This disclosure is not limited to this aspect.

[0091] Now for reference Figure 3 The diagram illustrates a signaling process 300 according to some example embodiments of the present disclosure. Process 300 may involve, for example... Figure 2D The first UE 241, the second UE 242, and the third UE 243 are shown. It should be understood that process 300 can also be applied to... Figure 2D This disclosure does not limit this aspect to other different scenarios shown.

[0092] For ease of description, the first UE 241 is also referred to as the first remote UE, source remote UE, U2U remote UE, etc.; the second UE 242 is also referred to as the relay UE, U2U relay UE, etc.; and the third UE 243 is also referred to as the second remote UE, target remote UE, destination remote UE, peer U2U remote UE, etc.

[0093] An end-to-end PC5 connection can be established at 310. In some implementations, a first PC5 RRC connection for the first hop between the first UE 241 and the second UE 242 can be established, and a second PC5 RRC connection for the second hop between the second UE 242 and the third UE 243 can be established. In some example embodiments, the end-to-end connection for unicast mode communication is established in the PC5-S layer.

[0094] In some implementations, the first UE 241 and / or the third UE 243 may receive configuration from their serving gNB. (See reference) Figure 2D The first UE 241 can receive configuration from BS 250. In some example embodiments, the configuration (e.g., sl-RemoteUE-ConfigU2U) can be sent via system information or dedicated RRC signaling.

[0095] In some embodiments, the configuration may include a first threshold (e.g., sl-RSRP-ThreshU2U) and / or a second threshold (e.g., sd-RSRP-ThreshU2U) for triggering relay UE selection / reselection. In some embodiments, the configuration may include a first coefficient (e.g., sl-FilterCoefficientU2U) and / or a second coefficient (e.g., sd-FilterCoefficientU2U).

[0096] In some examples, the first threshold (sl-RSRP-ThreshU2U) indicates the threshold for the SL-RSRP used by the U2U remote UE to perform trunk UE selection / reselection. The U2U remote UE applies the value of this field to evaluate AS layer conditions on the direct PC5 link with the peer U2U remote UE to trigger trunk selection, and to evaluate AS layer conditions on the U2U trunk link with the U2U trunk UE to trigger trunk reselection.

[0097] In some examples, the first coefficient (sl-FilterCoefficientU2U) specifies the L3 filter coefficient used for SL-RSRP measurements from the L1 filter.

[0098] In some examples, the second threshold (sd-RSRP-ThreshU2U) indicates the SD-RSRP threshold used by the U2U remote UE to perform discovery and relay UE selection / reselection. For discovery, the U2U remote UE applies the value of this field to evaluate AS layer conditions to determine whether to respond to the discovery message when performing U2U relay discovery using Model B. For relay selection and reselection, the U2U remote UE applies the value of this field to evaluate AS layer conditions on the direct PC5 link to trigger relay selection, and evaluates AS layer conditions on the U2U relay link to trigger relay reselection. The target U2U remote UE applies the value of this field to evaluate AS layer conditions that trigger relay selection when performing U2U relay communication using integrated discovery.

[0099] In some examples, the second coefficient (sd-FilterCoefficientU2U) specifies the L3 filter coefficient from the L1 filter for the SD-RSRP measurement results.

[0100] In some implementations, an end-to-end (e2e) PC5 RRC connection is established between the first UE 241 and the third UE 243. In some embodiments, for each unicast e2e PC5-RRC connection, before e2e PC5-S security has been established, an e2e-side crosslink SRB (i.e., e2e SL-SRB0) is used to send e2e PC5-S messages(s). An e2e-side crosslink SRB (i.e., e2e SL-SRB1) is used to send e2e PC5-S messages to establish e2e PC5-S security. An e2e-side crosslink SRB (i.e., SL-SRB2) is used to send e2e PC5-S messages after e2e PC5-S security has been established, and this e2e-side crosslink SRB is protected. An e2e sidelink SRB (i.e., e2e SL-SRB3) is used to send e2e PC5-RRC signaling, which is protected and sent only after e2e PC5-S security has been established.

[0101] Alternatively or concurrently, after the end-to-end PC5 RRC connection between the first UE 241 and the third UE 243 is established (at 310), some configurations may be exchanged between the first UE 241 and the third UE 243. For example, the first UE 241 may send a configuration for receiving data to the third UE 243 via the second UE 242.

[0102] In some embodiments, after an end-to-end PC5 connection has been established, U2U configurations, such as Sidelink Trunk Adaptor Protocol (SRAP) configurations, can be configured. In some examples, U2U configurations can be configured via sl-L2RelayUE-Config or sl-L2RemoteUE-Config included in the RRC reconfiguration message. For example, sl-L2RelayUE-Config or sl-L2RemoteUE-Config may include configurations associated with the second UE 242 (i.e., the U2U trunk).

[0103] In process 300, the first UE 241 determines the channel quality of the link between the first UE 241 and the second UE 242. For example... Figure 3 As shown, at 320, the first UE 241 can determine that the channel quality of the link between the first UE 241 and the second UE 242 is lower than a pre-configured threshold. For example, the pre-configured threshold could be a threshold used to trigger relay UE selection or reselection. For example, the AS layer of the first UE 241 can evaluate whether the threshold is met. For example, the pre-configured threshold could be the first threshold or the second threshold discussed above. For example, the channel quality could be the RSRP of the link.

[0104] In some examples, the SL-RSRP of the link between the first UE 241 and the second UE 242 (e.g., the currently selected NR-side crosslink U2U relay UE) is available and is lower than the threshold (i.e., the first threshold sl-RSRP-ThreshU2U) for the relay UE selection / reselection performed by the first UE 241 (U2U remote UE) through the L3 filter coefficients (e.g., the first coefficient sl-FilterCoefficientU2U) within sl-RemoteUE-ConfigU2U. For example, the SL-RSRP of the link is based on measurements of the data used for communication.

[0105] In some examples, the SD-RSRP of the link between the first UE 241 and the second UE 242 (e.g., the currently selected NR-side crosslink U2U relay UE) is available and is lower than the threshold (i.e., the second threshold sd-RSRP-ThreshU2U) for the SD-RSRP used by the first UE 241 (U2U remote UE) to perform discovery and relay UE selection / reselection via the L3 filter coefficients (e.g., the second coefficient sd-FilterCoefficientU2U) (if configured) within sl-RemoteUE-ConfigU2U. For example, the SD-RSRP of the link is based on the measurement results of the discovery message.

[0106] Alternatively, if the channel quality degrades below a threshold, the first UE 241 may trigger relay selection or reselection at 325. In some examples, candidate relay UE 245 may be selected as a new relay for communication between the first UE 241 and the third UE 243.

[0107] Alternatively or concurrently, if the channel quality is below a threshold, the first UE 241 performs at least one operation associated with the end-to-end PC5 connection at 330. For example... Figure 3 As shown, at least one operation may include one or more of operations 331-337.

[0108] At point 331, the first UE 241 can release the RLC entity and / or corresponding logical channel associated with the RLC channel ID of a specific destination. For example, the RLC entity between the first UE 241 and the second UE 242 can be released. Therefore, a threshold for triggering relay selection / reselection can be added as a condition for releasing the RLC entity. For example, the RLC channel ID associated with a specific destination (e.g., the third UE 243) (e.g., SL-RLC-ChannelID The associated logical channel can be released.

[0109] At 332, the first UE 241 can release the end-to-end DRB and / or SRB for the end-to-end PC5 connection. For example, the end-to-end DRB for the end-to-end PC5 connection can be released. For example, the end-to-end SRB for the end-to-end PC5 connection can be released.

[0110] At 333, the first UE 241 can discard end-to-end side link communication-related configurations for end-to-end PC5 connections. For example, end-to-end NR side link communication-related configurations for end-to-end PC5 connections can be released.

[0111] At 334, the first UE 241 can determine a failure in the end-to-end PC5 connection. For example, the first UE 241 can consider an end-to-end PC5 connection failure.

[0112] At 335, the first UE 241 can determine that the RRC connection has been released for use as an end-to-end PC5 connection. For example, the first UE 241 can assume that the end-to-end PC5-RRC connection has been released for use as an end-to-end PC5 connection.

[0113] At 336, the first UE 241 can indicate the release of the RRC connection to the upper layer. For example, the indication can be provided from the RRC layer to the upper layer of the first UE 241 (e.g., the PC5-S layer), and the indication can indicate the release of an end-to-end PC5-RRC connection.

[0114] At point 337, the first UE 241 may send a release message or a notification message to the second UE 242. For example, a threshold used to trigger relay UE selection or reselection may be used as a condition for triggering the transmission of a release message or notification message to the second UE 242 (i.e., the currently connected relay UE). In some examples, upper-layer messages (such as release messages, i.e., PC5-S release messages) may be sent to the second UE 242. In some examples, the upper layer (e.g., the PC5-S layer) may provide an indication to a lower layer (e.g., the RRC layer) that indicates the release of the PC5 unicast link, and the lower layer (RRC layer) may then send a lower-layer message, such as a notification message (i.e., an RRC notification message), to the second UE 242.

[0115] It should be noted that, although in Figure 3 The diagram illustrates operations 331-337, but the operations performed by the first UE 241 are not limited in this disclosure. For example, some operations may not be performed, some operations may be combined, and some additional operations may be included.

[0116] Therefore, the threshold used to trigger relay selection / reselection can be added as a condition for releasing an RLC entity, or it can be added as a condition for declaring an end-to-end PC5 connection failure.

[0117] From a relay perspective, the second UE 242 may perform operation 341 and / or operation 342. In some implementations, operation 341 and / or operation 342 may be performed by the second UE 242 if the second UE 242 determines that the channel quality of the link between the first UE 241 and the second UE 242 is below a threshold, or if a release / notification message is received from the first UE 241 (e.g., at 337).

[0118] At 341, the second UE 242 can release the RLC channel ID with a specific destination (e.g., SL-RLC- ChannelID The associated RLC entity and / or corresponding logical channel. At 342, the second UE 242 may send an additional release message or an additional notification message to the third UE 243.

[0119] According to the reference Figure 3In some embodiments, when the channel quality between the remote UE and the relay UE is below a threshold (e.g., a threshold used to trigger relay selection / reselection), at least one operation associated with an end-to-end PC5 connection between the remote UE and another remote UE via the relay UE can be performed. Therefore, a threshold can be used as a condition for at least one operation associated with an end-to-end PC5 connection. Thus, an end-to-end PC5 connection can be used for communication between two remote UEs.

[0120] Further reference Figure 4 The diagram illustrates a signaling process 400 according to some example embodiments of the present disclosure. Process 400 may involve, for example... Figure 2D The first UE 241, the second UE 242, and the third UE 243 are shown. It should be understood that process 400 can also be applied to... Figure 2D This disclosure does not limit this aspect to another scenario that differs from the one shown.

[0121] An end-to-end PC5 connection can be established at 410. In some implementations, a first PC5 RRC connection for the first hop between the first UE 241 and the second UE 242 can be established, and a second PC5 RRC connection for the second hop between the second UE 242 and the third UE 243 can be established. Alternatively or additionally, after the end-to-end PC5 RRC connection between the first UE 241 and the third UE 243 is established (at 410), some configurations can be exchanged between the first UE 241 and the third UE 243. For example, the first UE 241 can send a configuration for receiving data to the third UE 243 via the second UE 242. In some example embodiments, operation 410 can be similar to reference... Figure 3 Operation 310, which was discussed, will not be repeated in detail in this article.

[0122] In process 400, the second UE 242 may determine at 420 that the release condition has been met or a sidelink RLF has occurred. In some example embodiments, the release condition and / or the sidelink RLF are used for the link between the second UE 242 and the third UE 243.

[0123] In some implementations, the second UE 242 can determine that the release condition for the link between the second UE 242 and the third UE 243 has been met. In some examples, the upper layer (i.e., the PC5-S layer) of the second UE 242 can provide an indication to the lower layer (i.e., the RRC layer) of the second UE 242, where the indication indicates the release of the RRC connection between the second UE 242 and the third UE 243. For example, the upper layer can provide information associated with the release of the PC5-RRC connection between the second UE 242 and the third UE 243. In some examples, the RRC layer of the second UE 242 can determine that the release condition has been met, for example, based on an indication from the upper layer. In some examples, the second UE 242 can receive an additional release / notification message from the third UE 243, and then the second UE 242 can determine that the release condition has been met upon receiving the additional release / notification message from the third UE 243. For example, the additional release / notification message can be associated with the release of the link between the second UE 242 and the third UE 243.

[0124] In some implementations, the second UE 242 can determine that a sidelink RLF has occurred between the second UE 242 and the third UE 243. In some examples, the second UE 242 can detect the link quality of the link between the second UE 242 and the third UE 243, and then determine that an SL RLF has occurred.

[0125] In process 400, the second UE 242 sends a release message or notification message to the first UE 241 at 430, for example, based on the determination at 420.

[0126] In some examples, upper-layer messages (such as release messages (i.e., PC5-S release messages)) can be sent to the first UE 241. For example, the PC5-S layer of the second UE 242 can generate a PC5 unicast link release message.

[0127] In some examples, lower-layer messages such as notification messages (i.e., RRC notification messages) may be sent to the first UE 241. For example, the notification message may include an indication type indicating the reason for the release. For example, the indication type may be set to one of the following: release per hop, release by upper layer, or other fault.

[0128] Alternatively or concurrently, the second UE 242 may, for example, consider an end-to-end PC5 connection failure for each end-to-end PC5 connection established with the first UE 241 on the determination at 420.

[0129] On the other side of the communication, at 440, the first UE 241 can, for example, perform at least one operation associated with the end-to-end PC5 connection based on a release / notification message from the second UE 242. Figure 4 As shown, at least one operation may include one or more of operations 441-445.

[0130] At 441, the first UE 241 can release the end-to-end DRB and / or SRB for the end-to-end PC5 connection. For example, the end-to-end DRB for the end-to-end PC5 connection can be released. For example, the end-to-end SRB for the end-to-end PC5 connection can be released.

[0131] At 442, the first UE 241 can discard end-to-end side link communication-related configurations for the end-to-end PC5 connection. For example, end-to-end NR side link communication-related configurations for the end-to-end PC5 connection can be released.

[0132] At 443, the first UE 241 can determine a failure in the end-to-end PC5 connection. For example, the first UE 241 can consider an end-to-end PC5 connection failure.

[0133] At 444, the first UE 241 can determine that the RRC connection has been released for use as an end-to-end PC5 connection. For example, the first UE 241 can consider that the end-to-end PC5-RRC connection has been released for use as an end-to-end PC5 connection.

[0134] At 445, the first UE 241 can indicate the release of the RRC connection to the upper layer. For example, the indication can be provided from the RRC layer to the upper layer of the first UE 241 (e.g., the PC5-S layer), and the indication can indicate the release of an end-to-end PC5-RRC connection.

[0135] According to the reference Figure 4 Some embodiments discussed propose that after the relay UE detects an SL RLF to another remote UE (third UE) or when the upper layer requests a release, the relay UE can send a release or notification message to the remote UE (first UE). Therefore, (multiple) corresponding operations can be further performed for an end-to-end PC5 connection.

[0136] It should be understood that, despite Figures 3-4 Processes 300 and 400 are described separately, but in some embodiments they can be combined. For example, Figure 3 The third UE 243 can receive additional release / notification messages from the second UE 242 at point 342, and can further perform operations related to... Figure 4 Similar to operations 441-445 in the text.

[0137] It should be understood, for reference Figures 3-4 The embodiments described are for illustrative purposes only and are not limiting in any way. For example, some steps(s) may be omitted, reordered, modified, or combined, and some other steps(s) may be included. This disclosure is not limited to this aspect. It should be understood that, based on Figures 3 to 4 Some additional embodiments are still within the scope of this disclosure.

[0138] In some implementations, as described above, after an end-to-end PC5 connection has been established, U2U configuration (such as SRAP configuration) can be configured, for example, via sl-L2RelayUE-Config or sl-L2RemoteUE-Config included in the RRC reconfiguration message. For example, sl-L2RelayUE-Config or sl-L2RemoteUE-Config may include configuration related to the second UE 242 (i.e., the U2U relay). In some instances, the configuration related to the U2U relay will be released during the RRC connection reconstruction process.

[0139] In some examples, the U2U configuration may not be released (e.g., it may be maintained) after the first UE 241 (or the third UE 243) initiates the reconstruction process. The first UE 241 (or the third UE 243) may report the configuration to the reconstructed gNB after the reconstruction process is completed. Furthermore, the reconstructed gNB may further update the configuration.

[0140] In some examples, while timer T301 or T311 is running, another U2U configuration from system information can be used by the first UE 241 (or the third UE 243). For example, regarding the rebuild process, after the first UE 241 (or the third UE 243) releases its dedicated configuration when initiating the rebuild process, the first UE 241 (or the third UE 243) can perform cell selection / reselection and start a timer for cell selection / reselection, such as T301. After cell selection / reselection is complete, for example, after a suitable cell or a suitable relay UE is selected, timer T301 can be stopped. Alternatively, the first UE 241 (or the third UE 243) can send an RRC rebuild request and start timer T311. The first UE 241 can receive additional U2U configurations from system information (e.g., SIB12). The first UE 241 can use another U2U configuration from system information while a timer associated with cell selection or reselection is running, or when another timer associated with a rebuild request is running.

[0141] Figure 5An example of a device 500 suitable for implementing embodiments of the present disclosure is illustrated. Device 500 may be an example of a UE as described herein. Device 500 may support wireless communication with a first UE 241, a second UE 242, a third UE 243, or any combination thereof. Device 500 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 502, a memory 504, a transceiver 506, and an optional I / O controller 508. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., a bus).

[0142] Processor 502, memory 504, transceiver 506, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 502, memory 504, transceiver 506, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0143] In some implementations, processor 502, memory 504, transceiver 506, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 502 and memory 504 coupled to processor 502 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 504 by processor 502).

[0144] For example, according to the examples disclosed herein, processor 502 can support wireless communication at device 500. Processor 502 can be configured to be operable as a component to support the aforementioned actions.

[0145] Processor 502 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 502 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory (e.g., memory 504) to cause device 500 to perform various functions of this disclosure.

[0146] Memory 504 may include random access memory (RAM) and read-only memory (ROM). Memory 504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 502, cause device 500 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 502, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 504 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0147] I / O controller 508 can manage input and output signals for device 500. I / O controller 508 can also manage peripheral devices not integrated into device M02. In some implementations, I / O controller 508 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 508 can utilize an operating system such as iOS®, ANDROID®, MS WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 508 can be implemented as part of a processor, such as processor 502. In some implementations, a user can interact with device 500 via I / O controller 508 or via hardware components controlled by I / O controller 508.

[0148] In some implementations, device 500 may include a single antenna 510. However, in other implementations, device 500 may have more than one antenna 510 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to transmit or receive multiple wireless transmissions concurrently. Transceiver 506 may communicate bidirectionally via one or more antennas 510, wired or wireless links, as described herein. For example, transceiver 506 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 506 may also include a modem for modulating packets, providing modulated packets to one or more antennas 510 for transmission, and demodulating packets received from one or more antennas 510. Transceiver 506 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0149] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 510 for transmitting the amplified signal into the air or wireless medium.

[0150] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 510 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0151] Figure 6 An example of a processor 600 suitable for implementing some embodiments of the present disclosure is illustrated. Processor 600 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 600 may include a controller 602 configured to perform various operations according to the examples described herein. Processor 600 may optionally include at least one memory 604, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 600 may optionally include one or more arithmetic logic units (ALUs) 606. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0152] Processor 600 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., processor chipset-local or included memory (e.g., processor 600)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0153] Controller 602 can be configured to manage and coordinate various operations of processor 600 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 600 to support various operations according to the examples described herein. For example, controller 602 can operate as a control unit of processor 600, generating control signals that manage the operation of various components of processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0154] Controller 602 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 604 and determine subsequent instructions(s) to be executed, such that processor 600 supports various operations according to the examples described herein. Controller 602 may be configured to track the memory addresses of instructions associated with memory 604. Controller 602 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 602 may be configured to interpret instructions and determine control signals to be output to other components of processor 600, such that processor 600 supports various operations according to the examples described herein. Additionally or alternatively, controller 602 may be configured to manage data flow within processor 600. Controller 602 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 600.

[0155] Memory 604 may include one or more caches (e.g., memory local to processor 600 or included in processor 600) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 604 may reside within or on the processor chipset (e.g., locally on processor 600). In other implementations, memory 604 may reside outside the processor chipset (e.g., remotely from processor 600).

[0156] Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 600, cause processor 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 602 and / or processor 600 may be configured to execute computer-readable instructions stored in memory 604 to cause processor 600 to perform various functions. For example, processor 600 and / or controller 602 may be coupled to or coupled to memory 604, and processor 600, controller 602, and memory 604 may be configured to perform the various functions described herein. In some examples, processor 600 may include multiple processors, and memory 604 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0157] One or more ALU 606s can be configured to support various operations as described in the examples herein. In some implementations, one or more ALU 606s may reside within or on the processor chipset (e.g., processor 600). In other implementations, one or more ALU 606s may reside outside the processor chipset (e.g., processor 600). One or more ALU 606s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 606s can receive input operands and opcodes that determine the operation to be performed. One or more ALU 606s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU 606s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 606s to handle conditional operations, comparisons, and bitwise operations.

[0158] Based on the examples disclosed herein, processor 600 may support wireless communication. Processor 600 may be configured or operable to support components used in some embodiments of this disclosure.

[0159] Figure 7 A flowchart illustrating method 700 performed by a first UE according to various aspects of this disclosure is shown. Operation of method 700 may be implemented by the device or its components described herein. For example, operation of method 700 may be performed by… Figure 2D The first UE 241 in the process is executed. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0160] At 710, the method may include determining the channel quality of the link between the first UE and the second UE, wherein an end-to-end PC5 connection has been established between the first UE and the third UE via the second UE. The operation of 710 can be performed according to the examples described herein. In some implementations, aspects of the operation of 710 may be derived from references... Figure 2D The first UE241 described is executed.

[0161] At 720, the method may include triggering relay selection or reselection for the end-to-end PC5 connection based on a determination that the channel quality is below a threshold. The operation of 720 can be performed according to the examples described herein. In some implementations, aspects of the operation of 720 may be provided by reference to [reference needed]. Figure 2D The first UE 241 described is executed.

[0162] At 730, the method may include performing at least one operation associated with the end-to-end PC5 connection based on determining that the channel quality is below a threshold. The operation at 730 can be performed according to examples as described herein. In some implementations, aspects of the operation at 730 may be derived from references... Figure 2D The first UE 241 described is executed.

[0163] Figure 8 A flowchart illustrating method 800 performed by a second UE according to various aspects of this disclosure is shown. Operation of method 800 may be implemented by a device or component thereof as described herein. For example, operation of method 800 may be performed by… Figure 2D The second UE 242 in the process is executed. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0164] At 810, the method may include determining that a release condition for the link between the second UE and the third UE is met, or that a sidelink RLF occurs, wherein an end-to-end connection has been established between the first UE and the third UE via the second UE. The operation of 810 can be performed according to the examples described herein. In some implementations, aspects of the operation of 810 may be derived from references... Figure 2D The second UE 242 described is executed.

[0165] At 820, the method may include sending a message to the first UE, which is a release message or a notification message. The operation of 820 can be performed according to the examples described herein. In some implementations, aspects of the operation of 820 may be derived from references... Figure 2D The second UE 242 described is executed.

[0166] Figure 9 A flowchart illustrating a method 900 performed by a first UE according to various aspects of this disclosure is shown. Operation of method 900 can be implemented by a device or component thereof as described herein. For example, operation of method 900 can be performed by… Figure 2D The first UE 241 in the process is executed. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0167] At 910, the method may include receiving a message from the second UE, which is a release message or a notification message, wherein an end-to-end connection has been established between the first UE and the third UE via the second UE. The operation of 910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 910 may be derived from references... Figure 2D The first UE 241 described is executed.

[0168] At 920, the method may include performing at least one operation associated with the end-to-end PC5 connection based on the message. The operation at 920 can be performed according to the examples described herein. In some implementations, aspects of the operation at 920 may be derived from, as referenced... Figure 2D The first UE 241 described is executed.

[0169] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0170] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0171] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0172] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0173] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the word “or” used in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0174] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first user equipment (UE), comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the first UE: Determine the channel quality of the link between the first UE and the second UE, wherein the end-to-end proximity communication 5 (PC5) connection has been established between the first UE and the third UE via the second UE; Based on the determination that the channel quality is below a threshold, a relay selection or reselection is triggered for the end-to-end PC5 connection; as well as At least one operation associated with the end-to-end PC5 connection is performed based on the determination that the channel quality is below the threshold.

2. The first UE according to claim 1, wherein the channel quality is determined based on measurements of communication data, and wherein the threshold includes a side link reference signal received power (SL-RSRP) threshold.

3. The first UE according to claim 1, wherein the channel quality is determined based on the measurement results of the discovery message, and wherein the threshold includes a sidelink discovery reference signal received power (SD-RSRP) threshold.

4. The first UE according to claim 1, wherein the at least one operation includes one of the following: Release the Radio Link Control (RLC) entity, or Release the logical channel associated with the RLC channel identity (ID) for a specific destination.

5. The first UE according to claim 1, wherein the at least one operation includes one of the following: Determine the fault in the end-to-end PC5 connection. Release the end-to-end data radio bearer (DRB) for the end-to-end PC5 connection. Release the end-to-end signaling radio bearer (SRB) for the end-to-end PC5 connection, or Discard the end-to-end side link communication configurations for the end-to-end PC5 connection.

6. The first UE according to claim 1, wherein the at least one operation includes one of the following: Determine if the Radio Resource Control (RRC) connection for the end-to-end PC5 connection is released, or Indicate the release of the RRC connection from the RRC layer to the upper layer.

7. The first UE according to claim 1, wherein the at least one operation includes: Send a release message or notification message to the second UE.

8. The first UE according to claim 7, wherein the release message includes a Proximity Communication 5 Signaling (PC5-S) layer release message, and the notification message includes an RRC layer notification message.

9. The first UE according to claim 1, wherein the at least one processor is further configured such that the first UE: Maintaining the UE-to-UE (U2U) relay configuration after initiating the RRC connection re-establishment process, wherein the U2U relay configuration is received from the serving base station after the end-to-end PC5 connection has been established; and After the reconstruction process is completed, the UE-to-UE relay configuration is reported to the reconstructed gNB.

10. The first UE of claim 1, wherein the at least one processor is further configured such that the first UE: Release the U2U relay configuration after initiating the RRC connection re-establishment process, wherein the U2U configuration is received from the serving base station after the end-to-end PC5 connection has been established; and While a timer associated with cell selection or reselection is running, or while another timer associated with a rebuild request is running, use an additional U2U trunk configuration from system information.

11. A second user equipment (UE), comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the second UE: Determine that the release condition for the link between the second UE and the third UE is met, or that a sidelink radio link failure (RLF) occurs, wherein the end-to-end proximity communication 5 (PC5) connection has been established between the first UE and the third UE via the second UE; as well as A message is sent to the first UE, the message being a release message or a notification message.

12. The second UE according to claim 11, wherein the release condition includes: An instruction from the upper layer to the Radio Resource Control (RRC) layer for releasing the RRC connection between the second UE and the third UE.

13. The second UE according to claim 11, wherein the release condition includes: Received additional release messages or additional notification messages from the third UE.

14. The second UE of claim 11, wherein the notification message includes an indication type, and the indication type indicates a release reason.

15. The second UE according to claim 11, wherein the release message includes a proximity communication 5 signaling (PC5-S) layer release message, and the notification message includes an RRC layer notification message.

16. A first user equipment (UE), comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the first UE: Receive a message from the second UE, the message being a release message or a notification message, wherein an end-to-end proximity communication 5 (PC5) connection has been established between the first UE and the third UE via the second UE; as well as Perform at least one operation associated with the end-to-end PC5 connection based on the message.

17. The first UE according to claim 16, wherein the at least one operation comprises one of the following: Determine the fault in the end-to-end PC5 connection. Release the end-to-end data radio bearer (DRB) for the end-to-end PC5 connection. Release the end-to-end signaling radio bearer (SRB) for the end-to-end PC5 connection, or Discard the end-to-end side link communication configurations for the end-to-end PC5 connection.

18. The first UE of claim 16, wherein the at least one operation comprises one of the following: Determine if the Radio Resource Control (RRC) connection for the end-to-end PC5 connection is released, or Indicate the release of the RRC connection from the RRC layer to the upper layer.

19. The first UE of claim 16, wherein the message indicates a sidelink radio link failure (RLF) of the link between the second UE and the third UE.

20. The first UE according to claim 16, wherein the release message includes a Proximity Communication 5 Signaling (PC5-S) layer release message, and the notification message includes an RRC layer notification message.