[go: up one dir, main page]

WO2024109164A1 - Dispositifs et procédés de communication - Google Patents

Dispositifs et procédés de communication Download PDF

Info

Publication number
WO2024109164A1
WO2024109164A1 PCT/CN2023/111506 CN2023111506W WO2024109164A1 WO 2024109164 A1 WO2024109164 A1 WO 2024109164A1 CN 2023111506 W CN2023111506 W CN 2023111506W WO 2024109164 A1 WO2024109164 A1 WO 2024109164A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
information
relay
base station
processor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/111506
Other languages
English (en)
Inventor
Lianhai WU
Le Yan
Mingzeng Dai
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2023/111506 priority Critical patent/WO2024109164A1/fr
Publication of WO2024109164A1 publication Critical patent/WO2024109164A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure

Definitions

  • the present disclosure relates to wireless communications, and more specifically to devices and methods of communication for mobility robustness optimization (MRO) in a user equipment (UE) -to-network (U2N) relay.
  • MRO mobility robustness optimization
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • Each network communication devices such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) .
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • MRO is an important component of network optimization.
  • a remote UE may communicate with a base station via a relay UE (i.e., in an indirect path) .
  • the remote UE may also communicate with the base station directly (i.e., in a direct path) .
  • MRO for U2N relay is still unclear and needs to be further developed.
  • the present disclosure relates to methods, apparatuses, and systems that supports MRO for U2N relay.
  • a communication device may facilitate MRO for U2N relay.
  • some implementations of the method and apparatuses described herein may include: determining that the first UE accesses a first base station via an indirect path; storing first information related to relay UE associated with the indirect path; and transmitting the first information to a second base station via a transceiver.
  • storing the first information comprises: in accordance with a determination that a connection failure occurs in a connection establishment or resume procedure initiated by the first UE via the indirect path, storing the first information.
  • the first information comprises at least one of the following: measurement results for a link between the first UE and the relay UE in which the connection failure occurs, an identity of the relay UE; measurement results for a link between the first UE and a candidate UE; or an identity of the candidate UE.
  • transmitting the first information comprises: accessing the second base station after the connection failure occurs, and transmitting the first information to the second base station.
  • Some implementations of the method and apparatuses described herein may further include: transmitting, to the second base station via the transceiver, second information.
  • the second information comprises at least one of the following: number of connection failures in a cell; an indication of whether the number of connection failures is related to a set of direct paths, a set of indirect paths or both; a set of identities of relay UE associated with the set of indirect paths; number of connection failures in one of the set of indirect paths; or an indication of whether the connection failure occurs in a link between the relay UE and the first base station, in a link between the first UE and the relay UE, or both.
  • the connection failure occurring in the link between the relay UE and the first base station comprises at least one of the following: a radio link failure of the relay UE, a handover of the relay UE, a cell reselection of the relay UE, a connection establishment failure of the relay UE, or a connection resume failure of the relay UE.
  • the connection failure occurring in the link between the first UE and the relay UE comprises at least one of the following: a radio link failure in sidelink, or a relay reselection of the first UE.
  • storing the first information comprises: in accordance with a determination that a cell reselection of the relay UE, a cell reselection of the first UE or a relay reselection of the first UE is performed, storing the first information.
  • the first information comprises at least one of the following: an identity of a reselected cell, a time duration in which the first UE stays in the reselected cell, an identity of a reselected relay UE, or a time duration in which the first UE stays in the reselected relay UE.
  • transmitting the first information comprises: in accordance with a determination that the first UE enters a connected state, transmitting the first information.
  • a direct path is established between the first UE and the first base station.
  • storing the first information comprises at least one of the following: in accordance with a determination that the direct path is changed, storing the first information; in accordance with a determination that the relay UE related to the indirect path is changed or released while the direct path is unchanged, storing the first information; or in accordance with a determination that a cell related to the indirect path is changed, storing the first information.
  • the first information comprises at least one of the following: an identity of a cell of the direct path, an identity of the relay UE related to the indirect path, a time duration in which the first UE stays in the relay UE, an identity of a cell serving the relay UE, or a time duration in which the first UE stays in the cell serving the relay UE.
  • transmitting the first information comprises: in accordance with a determination that the indirect path or the direct path is changed, transmitting the first information.
  • transmitting the first information comprises at least one of the following: transmitting, to the second base station via the transceiver, an indication that the first information is available; receiving, from the second base station via the transceiver, a request for reporting the first information; or transmitting, to the second base station via the transceiver, the first information based on the request.
  • some implementations of the method and apparatuses described herein may include: receiving, from first UE via a transceiver, an indication that first information related to a relay UE is available, the relay UE being associated with an indirect path between the first UE and a first base station; transmitting, to the first UE via the transceiver, a request for reporting the first information; and receiving the first information from the first UE via the transceiver.
  • the first information is stored by the first UE upon a connection failure in a connection establishment or resume procedure initiated by the first UE via the indirect path.
  • the first information comprises at least one of the following: measurement results for a link between the first UE and the relay UE in which the connection failure occurs; an identity of the relay UE; measurement results for a link between the first UE and a candidate UE; or an identity of the candidate UE.
  • receive the first information comprises: accessing the first UE after the connection failure occurs; and receiving the first information from the first UE.
  • Some implementations of the method and apparatuses described herein may further include: receiving, from the first UE via the transceiver, second information.
  • the second information comprises at least one of the following: number of connection failures in a cell; an indication of whether the number of connection failures is related to a set of direct paths, a set of indirect paths or both; a set of identities of relay UE associated with the set of indirect paths, number of connection failures in one of the set of indirect paths; or an indication of whether the connection failure occurs in a link between the relay UE and the first base station, in a link between the first UE and the relay UE, or both.
  • the connection failure occurring in the link between the relay UE and the first base station comprises at least one of the following: a radio link failure of the relay UE, a handover of the relay UE, a cell reselection of the relay UE, a connection establishment failure of the relay UE, or a connection resume failure of the relay UE.
  • the connection failure occurring in the link between the first UE and the relay UE comprises at least one of the following: a radio link failure in sidelink, or a relay reselection of the first UE.
  • the first information comprises at least one of the following: an identity of a reselected cell, a time duration in which the first UE stays in the reselected cell, an identity of a reselected relay UE, or a time duration in which the first UE stays in the reselected relay UE.
  • the first information is stored by the first UE upon a cell reselection of the relay UE, a cell reselection of the first UE or a relay reselection of the first UE.
  • receiving the first information comprises: in accordance with a determination that the first UE enters a connected state with the second base station, receiving the first information.
  • a direct path is established between the first UE and the first base station.
  • the first information is stored by the first UE upon at least one of the following: a change of the direct path; a change or release of the relay UE related to the indirect path while the direct path is unchanged; or a change of a cell related to the indirect path.
  • the first information comprises at least one of the following: an identity of a cell of the direct path, an identity of the relay UE related to the indirect path, a time duration in which the first UE stays in the relay UE, an identity of a cell serving the relay UE, or a time duration in which the first UE stays in the cell serving the relay UE.
  • receiving the first information comprises: in accordance with a determination that the indirect path or the direct path is changed, receiving the first information.
  • some implementations of the method and apparatuses described herein may include: storing third information of a first indirect path between a first UE and the first base station via a relay UE; and transmitting, to a third base station via the transceiver, a handover request comprising the third information of the first indirect path.
  • the third information of the first indirect path comprises at least one of the following: an identity of the relay UE associated with the first indirect path in case the first UE accesses the first base station via a single path comprising the first indirect path; a time duration in which the first UE stays in the relay UE in case the first UE accesses the first base station via the single path; an identity of the relay UE associated with the first indirect path in case the first UE accesses the first base station via multiple paths comprising the first indirect path and a first direct path between the first UE and the first base station; or a time duration in which the first UE stays in the relay UE in case the first UE accesses the first base station via the multiple paths.
  • the third information of the first indirect path is associated with a visited cell in a set of visited cells.
  • the handover request further comprises fourth information indicating the third base station to store fifth information.
  • the fifth information comprises at least one of the following: an identity of a relay UE associated with a second indirect path between the first UE and the third base station in case the first UE accesses the third base station via a single path comprising the second indirect path; a time duration in which the first UE stays in the relay UE associated with the second indirect path in case the first UE accesses the third base station via the single path; an identity of the relay UE associated with the second indirect path in case the first UE accesses the third base station via multiple paths comprising the second indirect path and a second direct path between the first UE and the third base station; or a time duration in which the first UE stays in the relay UE associated with the second indirect path in case the first UE accesses the third base station via the multiple paths.
  • some implementations of the method and apparatuses described herein may include: receiving, from a first base station via a transceiver, a handover request comprising third information of a first indirect path between a first UE and the first base station via a relay UE; and storing the third information.
  • the third information of the first indirect path comprises at least one of the following: an identity of the relay UE associated with the first indirect path in case the first UE accesses the first base station via a single path comprising the first indirect path; a time duration in which the first UE stays in the relay UE in case the first UE accesses the first base station via the single path; an identity of the relay UE associated with the first indirect path in case the first UE accesses the first base station via multiple paths comprising the first indirect path and a first direct path between the first UE and the first base station; or a time duration in which the first UE stays in the relay UE in case the first UE accesses the first base station via the multiple paths.
  • the third information of the first indirect path is associated with a visited cell in a set of visited cells.
  • the handover request further comprises fourth information indicating the third base station to store fifth information.
  • the fifth information comprises at least one of the following: an identity of a relay UE associated with a second indirect path between the first UE and the third base station in case the first UE accesses the third base station via a single path comprising the second indirect path; a time duration in which the first UE stays in the relay UE associated with the second indirect path in case the first UE accesses the third base station via the single path; an identity of the relay UE associated with the second indirect path in case the first UE accesses the third base station via multiple paths comprising the second indirect path and a second direct path between the first UE and the third base station; or a time duration in which the first UE stays in the relay UE associated with the second indirect path in case the first UE accesses the third base station via the multiple paths.
  • Some implementations of the method and apparatuses described herein may further include: storing the fifth information based on an indication of the fourth information.
  • FIG. 1 illustrates an example of a wireless communications system that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 2 illustrates an example of a process that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 3A illustrates another example of a process that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 3B illustrates another example of a process that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 3C illustrates another example of a process that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example of another process that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 5 illustrates an example of a device that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 6 illustrates an example of a processor that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 7 illustrates a flowchart of a method that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 8 illustrates a flowchart of another method that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 9 illustrates a flowchart of another method that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 10 illustrates a flowchart of another method that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • MRO aims at detecting and enabling correction of following problems: connection failure due to intra-system or inter-system mobility; inter-system unnecessary handover (HO) ; inter-system HO ping-pong; primary secondary cell (PSCell) change failure.
  • MRO provides means to distinguish the above problems from new radio (NR) coverage related problems and other problems unrelated to mobility. For detection of a sub-optimal successful handovers, MRO additionally enables observability of successful HO due to intra-NR mobility.
  • NR new radio
  • a remote UE accessing a network via a relay UE is allowed to enter an idle or inactive state.
  • the remote UE may transit to a connected state via the indirect path.
  • the remote UE may fail to perform connection establishment or connection resume.
  • the remote UE may be expected to report the failure information to the network for a network optimization purpose.
  • a network may need to log history information of a UE, e.g., including information about cells that the UE has been served by in an active state (i.e., a connected state) prior to a target cell.
  • the UE may need to store the history information for network optimization or HO preparation.
  • history information related to a relay UE is still unclear.
  • a source base station may inform a target base station to store information about cells that a UE has been served by in an active state.
  • U2N relay it is still unclear whether to indicate a storage of information related to a relay UE.
  • embodiments of the present disclosure provide a solution of communication for MRO in U2N relay.
  • the remote UE upon determination that remote UE accesses a first base station via an indirect path, stores information related to relay UE associated with the indirect path, and transmit the first information to a second base station. In this way, remote UE may collect and report U2N relay information for MRO purpose.
  • a base station stores information of a first indirect path between remote UE and the base station via relay UE, and transmits, to a further base station, a handover request comprising the information of the first indirect path.
  • the further base station stores the information of the first indirect path.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more network entities (e.g., network entities 102, 107, 109 and 119) (also referred to as network equipment (NE) ) , one or more UEs (e.g., UEs 101, 104, 105, 115 and 117) , a core network 106, and a packet data network 108.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network.
  • LTE-A LTE-Advanced
  • the wireless communications system 100 may be a 5G network, such as an NR network.
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 IEEE 802.20
  • the wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more network entities may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the network entities described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • a network entity e.g., the network entity 102 and a UE (e.g., the UE 104) may communicate via a communication link 110, which may be a wireless or wired connection.
  • the network entity and the UE may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • a network entity may provide a geographic coverage area (i.e., a cell, e.g., geographic coverage area 112, 113 or 111) for which the network entity may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs within the geographic coverage area.
  • the network entity 102 and the UE 105 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies.
  • a network entity may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different network entities.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology.
  • the UE may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT Internet-of-Things
  • IoE Internet-of-Everything
  • MTC machine-type communication
  • a UE may be stationary in the wireless communications system 100.
  • a UE may be mobile in the wireless communications system 100.
  • the one or more UEs may be devices in different forms or having different capabilities. Some examples of UEs are illustrated in FIG. 1.
  • a UE may be capable of communicating with various types of devices, such as the network entities, other UEs, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1.
  • a UE may support communication with other network entities or UEs, which may act as relays in the wireless communications system 100.
  • a UE may also be able to support wireless communication directly with other UEs over a communication link 114.
  • a UE may support wireless communication directly with another UE over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE may support wireless communication directly with another UE over a PC5 interface.
  • a network entity may support communications with the core network 106, or with another network entity, or both.
  • the network entity may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the network entities may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities may communicate with each other directly (e.g., between the network entities) .
  • the network entities may communicate with each other or indirectly (e.g., via the core network 106) .
  • one or more network entities may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) .
  • An ANC may communicate with the one or more UEs through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
  • TRPs transmission-reception points
  • a network entity may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities, 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) ) .
  • IAB integrated access backhaul
  • O-RAN open RAN
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.
  • CU central unit
  • DU distributed unit
  • RU radio unit
  • RIC RAN Intelligent Controller
  • RIC e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC)
  • SMO Service Management and Orchestration
  • An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • RRH remote radio head
  • RRU remote radio unit
  • TRP transmission reception point
  • One or more components of the network entities in a disaggregated RAN architecture may be co-located, or one or more components of the network entities may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack.
  • the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaption protocol
  • PDCP Packet Data Convergence Protocol
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control
  • a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack.
  • the DU may support one or multiple different cells (e.g., via one or more RUs) .
  • a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
  • a CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • a CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u)
  • a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface)
  • FH open fronthaul
  • a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective the network entities that are in communication via such communication links.
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs served by the one or more network entities associated with the core network 106.
  • NAS non-access stratum
  • the core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • one or more UEs may communicate with the application server 118.
  • a UE may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity.
  • the core network 106 may route traffic (e.g., control information, data, and the like) between the UE and the application server 118 using the established session (e.g., the established PDU session) .
  • the PDU session may be an example of a logical connection between the UE and the core network 106 (e.g., one or more network functions of the core network 106) .
  • the network entities and the UEs may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) .
  • the network entities and the UEs may support different resource structures.
  • the network entities and the UEs may support different frame structures.
  • the network entities and the UEs may support a single frame structure.
  • the network entities and the UEs may support various frame structures (i.e., multiple frame structures) .
  • the network entities and the UEs may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a first subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first numerology associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) .
  • FR1 410 MHz –7.125 GHz
  • FR2 24.25 GHz –52.6 GHz
  • FR3 7.125 GHz –24.25 GHz
  • FR4 (52.6 GHz –114.25 GHz)
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR5 114.25 GHz
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities and the UEs, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • a connected state may be interchangeably used with “an RRC_CONNECTED state”
  • the term “an idle state” may be interchangeably used with “an RRC_IDLE state”
  • the term “an inactive state” may be interchangeably used with “an RRC_INACTIVE state” .
  • the UE 101 may communicate with the network entity 102 via the UE 105.
  • the UE 101 serves as a remote UE and the UE 105 serves as a relay UE.
  • An indirect path is established between the UE 101 and the network entity 102 via the UE 105. For example, when the UE 101 is out of coverage of the network entity 102, or when the terminal device 101 is located at edge of the coverage of the network entity 102, the indirect path may be established by the UE 105.
  • the network entity 102 may add a direct path to the UE 101.
  • the direct path may be established so that the UE 101 is served by the cell 112. This procedure may be called as a direct path addition.
  • the network entity 102 may add an indirect path to the UE 101. This procedure may be called as an indirect path addition.
  • the UE 101 may be switched from the cell 112 of the network entity 102 to another cell (not shown) of the network entity 102. This procedure may be called as a cell reselection of a remote UE.
  • a relay UE may be switched from the UE 105 to the UE 104. This procedure may be called as a relay reselection of a remote UE.
  • the relay UE (e.g., the UE 105) may be switched from the cell 112 of the network entity 102 to another cell (not shown) of the network entity 102. This procedure may be called as a cell reselection of a relay UE.
  • the relay UE e.g., the UE 105
  • the relay UE may be switched from the network entity 102 to another network entity (e.g., the network entity 107) . This procedure may be called as a handover of a relay UE.
  • a remote UE may fail to perform connection establishment or connection resume.
  • the remote UE may be expected to report the failure information to the network for a network optimization purpose. Further, storage of history information related to a relay UE is still unclear.
  • Embodiments of the present disclosure provide solutions of communication for MRO in U2N relay. The solutions will be described in connection with FIGs. 2 to 4 below.
  • FIG. 2 illustrates an example of a process 200 that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • the process 200 will be described with reference to FIG. 1.
  • the process 200 may involve the UE 101 as remote UE, the UE 105 as relay UE, the network entity 102 as a first base station serving the remote UE at a first time duration and the network entity 107 as a second base station serving the remote UE at a second time duration as illustrated in FIG. 1.
  • the steps and the order of the steps in FIG. 2 are merely for illustration, and not for limitation.
  • remote UE may access 210 a first base station (e.g., the network entity 102) via relay UE (e.g., the UE 105) .
  • the UE 101 may determine that the UE 101 accesses the network entity 102 via an indirect path.
  • the remote UE 101 may be in an idle state.
  • the remote UE 101 may be in an inactive state.
  • the remote UE 101 may be in a connected state.
  • the UE 101 may store 220 information (for convenience, also referred to as first information herein) related to relay UE associated with the indirect path.
  • the UE 101 may roam among cells or base stations, and may store the first information during the roaming.
  • the UE 101 may store the first information periodically.
  • the UE 101 may store the first information when a condition for storing the information is met. In this way, U2N relay information may be collected.
  • the UE 101 may transmit 230 the first information to a second base station (e.g., the network entity 107) currently serving the UE 101 during the roaming.
  • the second base station is shown as a base station different from the first base station. It is to be understood that the first base station and the second base station may be the same base station (e.g., the second base station may be the network entity 102) .
  • the UE 101 may transmit 231, to the network entity 107, an indication that the first information is available.
  • the network entity 107 may transit 232, to the UE 101, a request (e.g., an UE information request message) for reporting the first information.
  • the request may be carried in a UE information request message.
  • the UE 101 may transmit 233 the first information to the network entity 107, e.g., in a UE information response message.
  • the UE 101 may transmit the first information to the network entity 107 without the request.
  • FIG. 3A illustrates another example of a process 300A that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 3A will be described in connection with the example of FIG. 1.
  • the process 300A may involve the UE 101 as remote UE, the UE 105 as relay UE, the network entity 102 as a first base station serving the remote UE at a first time duration and the network entity 107 as a second base station serving the remote UE at a second time duration as illustrated in FIG. 1.
  • the steps and the order of the steps in FIG. 3A are merely for illustration, and not for limitation.
  • the UE 101 stays in an idle or inactive state.
  • the UE 101 may be triggered to establish an RRC connection.
  • the UE 101 may initiate 310 an RRC connection establish or resume procedure via the UE 105.
  • the UE 101 may be in an idle state and may camp on a layer 2 (L2) U2N relay (e.g., the UE 105) .
  • the UE 101 may transmit an RRC setup request to the network entity 102 (i.e., the first base station) via the UE 105.
  • the UE 101 may start a timer (e.g., T300) upon transmission of the RRC setup request.
  • the UE 101 may be in an inactive state and may camp on a L2 U2N relay (e.g., the UE 105) .
  • the UE 101 may transmit an RRC resume request to the network entity 102 via the UE 105.
  • the UE 101 may start a timer (e.g., T319) upon transmission of the RRC resume request.
  • the UE 101 may determine 311 that a connection failure occurs in the connection establishment or resume procedure. In some embodiments, if the timer (e.g., T300 or T319) expires, the UE 101 may determine that the connection failure occurs.
  • the timer e.g., T300 or T319
  • the UE 101 may store 312 information related to relay UE (i.e., the first information) .
  • the first information may comprise information of measurements for the indirect path in which the connection failure occurs.
  • the information of measurements for the indirect path may comprise measurement results for a link (e.g., PC5 link) between the UE 101 and the UE 105.
  • the connection failure may occur in the link.
  • measurement results for the serving PC5 link related to the failed indirect path should be reported. This may refer to the last measurement results where a connection establishment failure or a connection resume failure happens.
  • the information of measurements for the indirect path may comprise an identity of the relay UE.
  • the first information may comprise information of measurements for a link (e.g., PC5 link related to candidate relay UE) between the UE 101 and candidate relay UE (e.g., the UE 104, the UE 117 or the UE 115) .
  • the information of measurements for the PC5 link related to candidate relay UE may comprise measurement results for the PC5 link related to candidate relay UE.
  • the information of measurements for the PC5 link related to candidate relay UE may comprise an identity of the candidate relay UE. It is to be understood that any combination of the above information may also be feasible.
  • the UE 101 may come back 313 to a connected state and attempt to access other cells.
  • the UE 101 may successfully access to one cell of the network entity 107 (i.e., the second base station) .
  • the UE 101 may transmit 314 the first information to the network entity 107.
  • the UE 101 may transmit an indication of assistant information available to the network entity 107.
  • the assistant information is associated with a failure report.
  • the network entity 107 may transmit a UE information request message to the UE 101 after receiving the indication from the UE 101.
  • the UE 101 may report the first information to the network entity 107 in a UE information response message.
  • the UE 101 may report more relay specific information (for convenience, also referred to as second information herein) together with the first information.
  • the UE 101 may use a connection establishment failure report information element (IE) (i.e., connEstFailReport) to carry the first and second information.
  • IE connection establishment failure report information element
  • the second information may comprise the number of connection failures in a cell.
  • the number of connection failures in a cell may refer to the latest number of consecutive failed RRC setup or RRC resume procedures in the same cell independent of RRC state transition.
  • the second information may comprise an indication of whether the number of connection failures is related to a set of direct paths, a set of indirect paths or both.
  • the second information may comprise a set of identities of relay UE associated with the set of indirect paths. For example, if the number of connection failures is related to the set of direct paths, or is related to both of the set of direct paths and the set of indirect paths, an identity of the corresponding relay UE should be included in the second information.
  • the second information may comprise the number of connection failures in one of the set of indirect paths. That is, the second information may comprise the number of connection failures in each relay of the cell.
  • the number of connection failures in one of the set of indirect paths may refer to the latest number of consecutive failed RRC setup or RRC resume procedures in the same relay independent of RRC state transition.
  • the second information may comprise an indication of whether the connection failure occurs in a link between the UE 105 and the network entity 102, in a link between the UE 101 and the UE 105, or both.
  • the second information may indicate that the connection failure is due to a Uu issue or a PC5 issue.
  • the connection failure occurs in the link between the UE 105 and the network entity 102 may comprise a radio link failure (RLF) of the relay UE.
  • RLF radio link failure
  • the connection failure occurs in the link between the UE 105 and the network entity 102 may comprise a handover of the relay UE.
  • the connection failure occurs in the link between the UE 105 and the network entity 102 may comprise a cell reselection of the relay UE.
  • the connection failure occurs in the link between the UE 105 and the network entity 102 may comprise a connection establishment failure of the relay UE.
  • the connection failure occurs in the link between the UE 105 and the network entity 102 may comprise a connection resume failure of the relay UE.
  • the connection failure occurs in the link between the UE 101 and the UE 105 may comprise an RLF in sidelink. In some embodiments, the connection failure occurs in the link between the UE 101 and the UE 105 may comprise a relay reselection of the UE 101.
  • the second information may indicate that the timer (e.g., T300) configured for the connection establishment procedure expires. It is to be understood that the second information may comprise any combination of the above information.
  • the network entity 107 may transmit 315 an Xn message to the network entity 102.
  • the report may be transmitted as a container.
  • the Xn message may comprise an indication of “establishment failure” .
  • the Xn message may be a failure indication message or any other suitable messages existing or to be developed in future.
  • MRO for a failure of a connection establishment or resume in the case of U2N relay may be enhanced.
  • FIG. 3B illustrates another example of a process 300B that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 3B will be described in connection with the example of FIG. 1.
  • the process 300B may involve the UE 101 as remote UE, the UE 105 as relay UE, the network entity 102 as a first base station serving the remote UE at a first time duration and the network entity 107 as a second base station serving the remote UE at a second time duration as illustrated in FIG. 1.
  • the steps and the order of the steps in FIG. 3B are merely for illustration, and not for limitation.
  • the UE 101 stays in an idle or inactive state.
  • the UE 101 may camp 320 on a serving cell of the network entity 102 via relay UE (e.g., the UE 105) .
  • the UE 101 may perform 321 a relay reselection or a cell reselection (e.g., a cell reselection of the UE 101 or a cell reselection of the UE 105) .
  • the UE 101 may store 322 information related to relay UE (i.e., the first information) .
  • the first information may comprise an identity of a reselected cell.
  • the first information may comprise a time duration in which the UE 101 stays in the reselected cell.
  • the first information may comprise an identity of reselected relay UE.
  • the first information may comprise a time duration in which the UE 101 stays in the reselected relay UE. It is to be understood that any combination of the above information may also be feasible.
  • relay UE (for convenience, taking the UE 105 as an example herein) associated with the indirect path may store 323 information related to the relay UE.
  • This information may comprise at least one of the following: a time duration of being a role of a relay; or an identity of the reselected cell.
  • the UE 101 may transmit 324 the first information to the network entity 107.
  • the UE 101 may transmit an indication of UE history information (e.g., mobility history information) available to the network entity 107.
  • the UE 101 may include the indication of mobility history information available in an RRC setup complete message.
  • the UE 101 may include the indication of UE history information available in an RRC resume complete message.
  • the network entity 107 may transmit a UE information request message to the UE 101 after receiving the indication of UE history information available from the UE 101.
  • the UE 101 may transmit the first information to the network entity 107 in a UE information response message.
  • MRO for UE history information in the case of UN2 relay with a single indirect path may be enhanced.
  • FIG. 3C illustrates another example of a process 300C that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • FIG. 3C will be described in connection with the example of FIG. 1.
  • the process 300C may involve the UE 101 as remote UE, the UE 105 as relay UE, the network entity 102 as a first base station serving the remote UE at a first time duration and the network entity 107 as a second base station serving the remote UE at a second time duration as illustrated in FIG. 1.
  • the steps and the order of the steps in FIG. 3C are merely for illustration, and not for limitation.
  • the UE 101 stays in a connected state.
  • the UE 101 may access the network entity 102 via a direct path (i.e., Uu interface) .
  • the network entity 102 may transmit 330, to the UE 101, an RRC configuration for multi-path. That is, the network entity 102 configures an indirect path addition.
  • the UE 101 may store information related to relay UE (i.e., the first information) .
  • the first information may comprise an identity of a cell serving the relay UE.
  • the first information may comprise an identity of the relay UE.
  • the first information may comprise an identity of a cell (e.g., primary cell (PCell) ) of the direct path.
  • the first information may comprise a time duration in which the UE 101 stays in the relay UE.
  • the first information may comprise a time duration in which the UE 101 stays in the cell serving the relay UE. It is to be understood that any combination of the above information may also be feasible.
  • the UE 101 may store 331 the first information. For example, if a serving cell of the UE 101 is changed to another cell of the network entity 102, the UE 101 may store the first information. In another example, if a handover of the UE 101 from the network entity 102 to another network entity (e.g., the network entity 107) , the UE 101 may store the first information.
  • the UE 101 may store 332 the first information. In some embodiments, if the cell related to the indirect path is changed, the UE 101 may store 333 the first information.
  • the UE 101 may transmit 334 the first information to a serving cell (e.g., the network entity 107) .
  • the UE 101 may transmit an indication of UE history available to the network entity 107. The indication may be included in an RRC setup complete message or an RRC resume complete message.
  • the network entity 107 may transmit a UE information request message to the UE 101 after receiving the indication. The UE 101 may transmit the first information to the network entity 107 in a UE information response message.
  • MRO for UE history information in the case of UN2 relay with multi-path may be enhanced.
  • Embodiments of the present disclosure also provide a solution of MRO for U2N relay at an Xn interface. The solution will be described in connection with FIG. 4.
  • FIG. 4 illustrates an example of another process 400 that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • the process 400 may involve a source base station (e.g., the network entity 102) and a target base station (e.g., the network entity 109) as illustrated in FIG. 1.
  • a source base station e.g., the network entity 102
  • a target base station e.g., the network entity 109
  • the steps and the order of the steps in FIG. 4 are merely for illustration, and not for limitation.
  • the source base station may also be referred to as a first base station
  • the target base station may also be referred to as a third base station herein. It is assumed that a remote UE accesses a serving cell of a source base station via a direct path or indirect path.
  • the network entity 102 may store 410 information (for convenience, also referred to as third information herein) of a first indirect path between remote UE (e.g., the UE 101) and the network entity 102 via a relay UE (e.g., the UE 105) .
  • the network entity 102 may receive the information of the first indirect path from the remote UE.
  • the network entity 102 receive the last visited cell information included in a UE History Information IE, and store the last visited cell information.
  • the network entity 102 may also store an identity of relay UE associated with the indirect path.
  • the information of the indirect path may comprise information related to a single indirect path.
  • the third information may comprise an identity of the relay UE in the case that the UE 101 accesses the network entity 102 via the single indirect path (e.g., via the UE 105) .
  • the third information may comprise a time duration in which the UE 101 stays in coverage of the relay UE in the case that the UE 101 accesses the network entity 102 via the single indirect path (e.g., via the UE 105) .
  • the information of the indirect path may comprise information related to multiple paths.
  • the third information may comprise an identity of the relay UE associated with the indirect path in the case that the UE 101 accesses the network entity 102 via multiple paths comprising the indirect path and the direct path.
  • the third information may comprise a time duration in which the UE 101 stays in coverage of the relay UE in the case that the UE 101 accesses the network entity 102 via the multiple paths.
  • the network entity 102 may transmit 420 a handover request to the network entity 109.
  • the handover request comprises the third information of the indirect path.
  • the handover request may comprise a target cell.
  • the handover request may comprise one or more target relay UEs.
  • a UE history information IE may be included in the handover request to carry the third information.
  • the third information may be associated with a visited cell in a set of visited cells. For illustration, example contents of the UE history information IE may be listed in Table 1 below.
  • the UE history information IE may contain information about cells and relay UEs that remote UE has been served by in an active state prior to the target cell.
  • the network entity 109 may store 430 the third information.
  • the handover request may comprise information (for convenience, also referred to as fourth information herein) indicating the network entity 109 to store information related to relay UE (for convenience, also referred to as fifth information herein) .
  • the network entity 109 may store 440 the incoming fifth information.
  • the fifth information may comprise an identity of relay UE (e.g., the UE 105) associated with a second indirect path between the UE 101 and the network entity 109 in case the UE 101 accesses the network entity 109 via a single indirect path (i.e., the second indirect path) .
  • the fifth information may comprise a time duration of the UE 101 staying in the relay UE (e.g., the UE 105) associated with the second indirect path in case the UE 101 accesses the network entity 109 via the single indirect path (i.e., the second indirect path) .
  • the fifth information may comprise an identity of the relay UE (e.g., the relay UE 105) associated with the single indirect path in case the UE 101 accesses the network entity 109 via multiple paths.
  • the multiple paths comprise the single indirect path, and a direct path (for convenience, also referred to as a second direct path herein) between the UE 101 and the network entity 109.
  • the fifth information may comprise a time duration of the UE 101 staying in the relay UE (e.g., the relay UE 105) associated with the single indirect path in case the UE 101 accesses the network entity 109 via the multiple paths.
  • the network entity 109 may collect information based on the UE history information IE.
  • the collected information may include both last visited cell and an identity of relay UE related to the visited cell.
  • U2N relay information may be collected at an Xn interface, and MRO for U2N relay may be enhanced at the Xn interface.
  • the U2N relay information as collected according to embodiments of the present disclosure may be used to avoid a ping-pong path switching, e.g., an indirect-to-direct or direct-to-indirect path switching, or an indirect-to-indirect path switching.
  • the network may predict an upcoming path switching based on the history information. Then, the network may optimize a measurement configuration and prepare a suitable candidate cell or relay.
  • FIG. 5 illustrates an example of a device 500 that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • the device 500 may be an example of a UE (e.g., a remote UE or a relay UE) or a network entity as described herein.
  • the device 500 may support wireless communication with one or more network entities, UEs, or any combination thereof.
  • the device 500 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 502, a memory 504, a transceiver 506, and, optionally, an I/O controller 508. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 502, the memory 504, the transceiver 506, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 502, the memory 504, the transceiver 506, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 502, the memory 504, the transceiver 506, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 502 and the memory 504 coupled with the processor 502 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504) .
  • the processor 502 may support wireless communication at the device 500 in accordance with examples as disclosed herein.
  • the processor 502 may be configured to operable to support a means for: determining that the first UE accesses a first base station via an indirect path; storing first information related to relay UE associated with the indirect path; and transmitting the first information to a second base station via the transceiver.
  • the processor 502 may be configured to operable to support a means for: receiving, from first UE via the transceiver, an indication that first information related to a relay UE is available, the relay UE being associated with an indirect path between the first UE and a first base station; transmitting, to the first UE via the transceiver, a request for reporting the first information; and receiving the first information from the first UE via the transceiver.
  • the processor 502 may be configured to operable to support a means for: storing third information of a first indirect path between a first UE and the first base station via a relay UE; and transmitting, to a third base station via the transceiver, a handover request comprising the third information of the first indirect path.
  • the processor 502 may be configured to operable to support a means for: receiving, from a first base station via the transceiver, a handover request comprising third information of a first indirect path between a first UE and the first base station via a relay UE; and storing the third information.
  • the processor 502 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 502 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 502.
  • the processor 502 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 504) to cause the device 500 to perform various functions of the present disclosure.
  • the memory 504 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 504 may store computer-readable, computer-executable code including instructions that, when executed by the processor 502 cause the device 500 to perform 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.
  • the code may not be directly executable by the processor 502 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 504 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 508 may manage input and output signals for the device 500.
  • the I/O controller 508 may also manage peripherals not integrated into the device 500.
  • the I/O controller 508 may represent a physical connection or port to an external peripheral.
  • the I/O controller 508 may utilize an operating system such as or another known operating system.
  • the I/O controller 508 may be implemented as part of a processor, such as the processor 506.
  • a user may interact with the device 500 via the I/O controller 508 or via hardware components controlled by the I/O controller 508.
  • the device 500 may include a single antenna 510. However, in some other implementations, the device 500 may have more than one antenna 510 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 506 may communicate bi-directionally, via the one or more antennas 510, wired, or wireless links as described herein.
  • the transceiver 506 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 506 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 510 for transmission, and to demodulate packets received from the one or more antennas 510.
  • the transceiver 506 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the 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 like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) .
  • the transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmit chain may also include one or more antennas 510 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 510 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • FIG. 6 illustrates an example of a processor 600 that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • the processor 600 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 600 may include a controller 602 configured to perform various operations in accordance with examples as described herein.
  • the processor 600 may optionally include at least one memory 604, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 600 may optionally include one or more arithmetic-logic units (ALUs) 606.
  • ALUs arithmetic-logic units
  • One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 600 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • the processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the 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) , and others) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 602 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein.
  • the controller 602 may operate as a control unit of the processor 600, generating control signals that manage the operation of various components of the processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 602 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 604 and determine subsequent instruction (s) to be executed to cause the processor 600 to support various operations in accordance with examples as described herein.
  • the controller 602 may be configured to track memory address of instructions associated with the memory 604.
  • the controller 602 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 602 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein.
  • the controller 602 may be configured to manage flow of data within the processor 600.
  • the controller 602 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 600.
  • ALUs arithmetic logic units
  • the memory 604 may include one or more caches (e.g., memory local to or included in the processor 600 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 604 may reside within or on a processor chipset (e.g., local to the processor 600) . In some other implementations, the memory 604 may reside external to the processor chipset (e.g., remote to the processor 600) .
  • caches e.g., memory local to or included in the processor 600 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 604 may reside within or on a processor chipset (e.g., local to the processor 600) . In some other implementations, the memory 604 may reside external to the processor chipset (e.g., remote to the processor 600) .
  • the memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 600, cause the processor 600 to perform 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.
  • the controller 602 and/or the processor 600 may be configured to execute computer-readable instructions stored in the memory 604 to cause the processor 600 to perform various functions.
  • the processor 600 and/or the controller 602 may be coupled with or to the memory 604, and the processor 600, the controller 602, and the memory 604 may be configured to perform various functions described herein.
  • the processor 600 may include multiple processors and the memory 604 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
  • the one or more ALUs 606 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 606 may reside within or on a processor chipset (e.g., the processor 600) .
  • the one or more ALUs 606 may reside external to the processor chipset (e.g., the processor 600) .
  • One or more ALUs 606 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 606 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 606 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 606 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 600 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 600 may be configured to operable to support a means for: determining that a first UE accesses a first base station via an indirect path; storing first information related to relay UE associated with the indirect path; and transmitting the first information to a second base station.
  • FIG. 7 illustrates a flowchart of a method 700 that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • the operations of the method 700 may be implemented by a device or its components as described herein.
  • the operations of the method 700 may be performed by first UE (i.e., remote UE; e.g., the UE 101) as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method 700 may include determining that first UE (e.g., the UE 101) accesses a first base station (e.g., the network entity 102) via an indirect path.
  • the operations of 701 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 701 may be performed by a device as described with reference to FIG. 1.
  • the method 700 may include storing first information related to relay UE 105 associated with the indirect path.
  • the operations of 702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 702 may be performed by a device as described with reference to FIG. 1.
  • the method 700 may include transmitting the first information to a second base station (e.g., the network entity 107) via a transceiver.
  • the operations of 702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 703 may be performed by a device as described with reference to FIG. 1.
  • transmitting the first information may comprise at least one of the following: transmitting, to the second base station via the transceiver, an indication that the first information is available; receiving, from the second base station via the transceiver, a request for reporting the first information; or transmitting, to the second base station via the transceiver, the first information based on the request.
  • storing the first information may comprise: in accordance with a determination that a connection failure occurs in a connection establishment or resume procedure initiated by the first UE via the indirect path, storing the first information.
  • the first information may comprise at least one of the following: measurement results for a link between the first UE and the relay UE in which the connection failure occurs; an identity of the relay UE; measurement results for a link between the first UE and a candidate UE; or an identity of the candidate UE.
  • transmitting the first information may comprise: accessing the second base station after the connection failure occurs, and transmitting the first information to the second base station.
  • the method 700 may further comprise: transmitting second information to the second base station via the transceiver.
  • the second information may comprise at least one of the following: number of connection failures in a cell; an indication of whether the number of connection failures is related to a set of direct paths, a set of indirect paths or both; a set of identities of relay UE associated with the set of indirect paths; number of connection failures in one of the set of indirect paths; or an indication of whether the connection failure occurs in a link between the relay UE and the first base station, in a link between the first UE and the relay UE, or both.
  • the connection failure occurring in the link between the relay UE and the first base station may comprise at least one of the following: a radio link failure of the relay UE, a handover of the relay UE, a cell reselection of the relay UE, a connection establishment failure of the relay UE, or a connection resume failure of the relay UE.
  • the connection failure occurring in the link between the first UE and the relay UE may comprise at least one of the following: a radio link failure in sidelink, or a relay reselection of the first UE.
  • storing the first information may comprise: in accordance with a determination that a cell reselection of the relay UE, a cell reselection of the first UE or a relay reselection of the first UE is performed, storing the first information.
  • the first information may comprise at least one of the following: an identity of a reselected cell, a time duration in which the first UE stays in the reselected cell, an identity of a reselected relay UE, or a time duration in which the first UE stays in the reselected relay UE.
  • transmitting the first information may comprise: in accordance with a determination that the first UE enters a connected state, transmitting the first information.
  • a direct path may be established between the first UE and the first base station.
  • storing the first information may comprise at least one of the following: in accordance with a determination that the direct path is changed, storing the first information; in accordance with a determination that the relay UE related to the indirect path is changed or released while the direct path is unchanged, storing the first information; or in accordance with a determination that a cell related to the indirect path is changed, storing the first information.
  • the first information may comprise at least one of the following: an identity of a cell of the direct path, an identity of the relay UE related to the indirect path, a time duration in which the first UE stays in the relay UE, an identity of a cell serving the relay UE, or a time duration in which the first UE stays in the cell serving the relay UE.
  • transmitting the first information may comprise: in accordance with a determination that the indirect path or the direct path is changed, transmitting the first information.
  • FIG. 8 illustrates a flowchart of a method 800 that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • the operations of the method 800 may be implemented by a device or its components as described herein.
  • the operations of the method 800 may be performed by a second base station (e.g., the network entity 107) serving first UE as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method 800 may include receiving, from first UE (e.g., the UE 101) via a transceiver, an indication that first information related to a relay UE is available, the relay UE being associated with an indirect path between the first UE and a first base station (e.g., the network entity 102) .
  • the operations of 801 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 801 may be performed by a device as described with reference to FIG. 1.
  • the method 800 may include transmitting, to first UE via the transceiver, a request for reporting the first information.
  • the operations of 802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a device as described with reference to FIG. 1.
  • the method 800 may include receiving the first information from the first UE via the transceiver.
  • the operations of 803 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 803 may be performed by a device as described with reference to FIG. 1.
  • the first information may be stored by the first UE upon a connection failure in a connection establishment or resume procedure initiated by the first UE via the indirect path.
  • the first information may comprise at least one of the following: measurement results for a link between the first UE and the relay UE in which the connection failure occurs; an identity of the relay UE; measurement results for a link between the first UE and a candidate UE; or an identity of the candidate UE.
  • receive the first information may comprise: accessing the first UE after the connection failure occurs; and receiving the first information from the first UE.
  • the method 800 may further include receiving second information from the first UE via the transceiver.
  • the second information may comprise at least one of the following: number of connection failures in a cell; an indication of whether the number of connection failures is related to a set of direct paths, a set of indirect paths or both; a set of identities of relay UE associated with the set of indirect paths, number of connection failures in one of the set of indirect paths; or an indication of whether the connection failure occurs in a link between the relay UE and the first base station, in a link between the first UE and the relay UE, or both.
  • the connection failure occurring in the link between the relay UE and the first base station may comprise at least one of the following: a radio link failure of the relay UE, a handover of the relay UE, a cell reselection of the relay UE, a connection establishment failure of the relay UE, or a connection resume failure of the relay UE.
  • the connection failure occurring in the link between the first UE and the relay UE may comprise at least one of the following: a radio link failure in sidelink, or a relay reselection of the first UE.
  • the first information may be stored by the first UE upon a cell reselection of the relay UE, a cell reselection of the first UE or a relay reselection of the first UE.
  • the first information may comprise at least one of the following: an identity of a reselected cell, a time duration in which the first UE stays in the reselected cell, an identity of a reselected relay UE, or a time duration in which the first UE stays in the reselected relay UE.
  • receiving the first information may comprise; in accordance with a determination that the first UE enters a connected state with the second base station, receiving the first information.
  • a direct path may be established between the first UE and the first base station.
  • the first information may be stored by the first UE upon at least one of the following: a change of the direct path; a change or release of the relay UE related to the indirect path while the direct path is unchanged; or a change of a cell related to the indirect path.
  • the first information may comprise at least one of the following: an identity of a cell of the direct path, an identity of the relay UE related to the indirect path, a time duration in which the first UE stays in the relay UE, an identity of a cell serving the relay UE, or a time duration in which the first UE stays in the cell serving the relay UE.
  • receiving the first information may comprise; in accordance with a determination that the indirect path or the direct path is changed, receiving the first information.
  • FIG. 9 illustrates a flowchart of a method 900 that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • the operations of the method 900 may be implemented by a device or its components as described herein.
  • the operations of the method 900 may be performed by a first base station (i.e., source base station; e.g., the network entity 102) as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method 900 may include storing third information of a first indirect path between a first UE (e.g., the UE 101) and the first base station (e.g., the network entity 102) via a relay UE (e.g., the UE 105) .
  • the operations of 901 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 901 may be performed by a device as described with reference to FIG. 1.
  • the third information of the first indirect path may comprise at least one of the following: an identity of the relay UE associated with the first indirect path in case the first UE accesses the first base station via a single path comprising the first indirect path; a time duration in which the first UE stays in the relay UE in case the first UE accesses the first base station via the single path; an identity of the relay UE associated with the first indirect path in case the first UE accesses the first base station via multiple paths comprising the first indirect path and a first direct path between the first UE and the first base station; or a time duration in which the first UE stays in the relay UE in case the first UE accesses the first base station via the multiple paths.
  • the third information of the first indirect path may be associated with a visited cell in a set of visited cells.
  • the method 900 may include transmitting, to a third base station (e.g., the network entity 107) via the transceiver, a handover request comprising the third information of the first indirect path.
  • a third base station e.g., the network entity 107
  • the transceiver may transmit a handover request comprising the third information of the first indirect path.
  • the operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a device as described with reference to FIG. 1.
  • the handover request may further comprise fourth information indicating the third base station to store fifth information.
  • the fifth information may comprise at least one of the following: an identity of a relay UE associated with a second indirect path between the first UE and the third base station in case the first UE accesses the third base station via a single path comprising the second indirect path; a time duration in which the first UE stays in the relay UE associated with the second indirect path in case the first UE accesses the third base station via the single path; an identity of the relay UE associated with the second indirect path in case the first UE accesses the third base station via multiple paths comprising the second indirect path and a second direct path between the first UE and the third base station; or a time duration in which the first UE stays in the relay UE associated with the second indirect path in case the first UE accesses the third base station via the multiple paths.
  • FIG. 10 illustrates a flowchart of another method 1000 that supports MRO for U2N relay in accordance with aspects of the present disclosure.
  • the operations of the method 1000 may be implemented by a device or its components as described herein.
  • the operations of the method 1000 may be performed by a third base station (i.e., target base station; e.g., the network entity 109) as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method 1000 may include receiving, from a first base station (e.g., the network entity 102) via a transceiver, a handover request comprising third information of a first indirect path between a first UE (e.g., the UE 101) and the first base station (e.g., the network entity 102) via a relay UE (e.g., the UE 105) .
  • the operations of 1001 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1001 may be performed by a device as described with reference to FIG. 1.
  • the third information of the first indirect path may comprise at least one of the following: an identity of the relay UE associated with the first indirect path in case the first UE accesses the first base station via a single path comprising the first indirect path; a time duration in which the first UE stays in the relay UE in case the first UE accesses the first base station via the single path; an identity of the relay UE associated with the first indirect path in case the first UE accesses the first base station via multiple paths comprising the first indirect path and a first direct path between the first UE and the first base station; or a time duration in which the first UE stays in the relay UE in case the first UE accesses the first base station via the multiple paths.
  • the third information of the first indirect path may be associated with a visited cell in a set of visited cells.
  • the handover request may further comprise fourth information indicating the third base station to store fifth information.
  • the fifth information may comprise at least one of the following: an identity of a relay UE associated with a second indirect path between the first UE and the third base station in case the first UE accesses the third base station via a single path comprising the second indirect path; a time duration in which the first UE stays in the relay UE associated with the second indirect path in case the first UE accesses the third base station via the single path; an identity of the relay UE associated with the second indirect path in case the first UE accesses the third base station via multiple paths comprising the second indirect path and a second direct path between the first UE and the third base station; or a time duration in which the first UE stays in the relay UE associated with the second indirect path in case the first UE accesses the third base station via the multiple paths.
  • the method 1000 may include storing the third information.
  • the operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by a device as described with reference to FIG. 1.
  • the method 1000 may further include store the fifth information based on an indication of the fourth information.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a 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 in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a list of items 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) .
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • a “set” may include one or more elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente invention concernent des dispositifs et des procédés de communication. Selon un aspect, lors de la détermination que l'UE distant accède à une première station de base par l'intermédiaire d'un trajet indirect, l'UE distant stocke des informations relatives à un UE relais associé au trajet indirect, les informations peuvent être associées à une défaillance d'établissement de connexion, à une défaillance de reprise ou à un UE relais visité. L'UE distant transmet les informations à une seconde station de base. De cette manière, un UE distant peut collecter et rapporter des informations de relais U2N pour un objectif MRO.
PCT/CN2023/111506 2023-08-07 2023-08-07 Dispositifs et procédés de communication Pending WO2024109164A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/111506 WO2024109164A1 (fr) 2023-08-07 2023-08-07 Dispositifs et procédés de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/111506 WO2024109164A1 (fr) 2023-08-07 2023-08-07 Dispositifs et procédés de communication

Publications (1)

Publication Number Publication Date
WO2024109164A1 true WO2024109164A1 (fr) 2024-05-30

Family

ID=91195147

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/111506 Pending WO2024109164A1 (fr) 2023-08-07 2023-08-07 Dispositifs et procédés de communication

Country Status (1)

Country Link
WO (1) WO2024109164A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018006253A1 (fr) * 2016-07-04 2018-01-11 华为技术有限公司 Procédé de traitement de défaillance de liaison radio, dispositif associé et système de communication
WO2022036501A1 (fr) * 2020-08-17 2022-02-24 Qualcomm Incorporated Rétablissement de rrc et rapport de défaillance de liaison radio dans des systèmes de relais de liaison latérale
WO2023014157A1 (fr) * 2021-08-05 2023-02-09 엘지전자 주식회사 Procédé pour faire fonctionner un équipement utilisateur à distance associé à une commutation de trajet et à un rapport de mesure dans un système de communication sans fil
CN116235541A (zh) * 2020-09-30 2023-06-06 联想(北京)有限公司 用于ue到网络中继场景中的中继重选及数据传输处置程序的方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018006253A1 (fr) * 2016-07-04 2018-01-11 华为技术有限公司 Procédé de traitement de défaillance de liaison radio, dispositif associé et système de communication
WO2022036501A1 (fr) * 2020-08-17 2022-02-24 Qualcomm Incorporated Rétablissement de rrc et rapport de défaillance de liaison radio dans des systèmes de relais de liaison latérale
CN116235541A (zh) * 2020-09-30 2023-06-06 联想(北京)有限公司 用于ue到网络中继场景中的中继重选及数据传输处置程序的方法及设备
WO2023014157A1 (fr) * 2021-08-05 2023-02-09 엘지전자 주식회사 Procédé pour faire fonctionner un équipement utilisateur à distance associé à une commutation de trajet et à un rapport de mesure dans un système de communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC.: "RRC relay handover procedure for remote UE", 3GPP DRAFT; R2-1701270 RRC RELAY HANDOVER PROCEDURE FOR REMOTE UE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Athens, Greece; 20170213 - 20170217, 12 February 2017 (2017-02-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051211936 *

Similar Documents

Publication Publication Date Title
WO2024183313A1 (fr) Ltm scg inter-sn
WO2024250686A1 (fr) Prédiction d'échec de transfert
WO2024093428A1 (fr) Mécanisme pour cho avec des scg candidats
WO2024109164A1 (fr) Dispositifs et procédés de communication
WO2025175830A1 (fr) Mobilité déclenchée par couche 1 ou couche 2 conditionnelle
WO2025145658A1 (fr) Contrôle d'accès d'une cellule ntn
WO2024098839A1 (fr) Ajout de trajet indirect pour communication u2n
WO2025222941A1 (fr) Collecte de données pendant des événements de mobilité
WO2024259991A1 (fr) Défaillance dans une communication par relais
WO2024109165A1 (fr) Services de diffusion dans un ntn
WO2024207740A1 (fr) Mobilité déclenchée de couche 1 ou de couche 2
WO2025148315A1 (fr) Prédiction de défaillance de liaison radio en double connexion
WO2025241592A1 (fr) Identification de la cause d'un problème lié à la mobilité
WO2024094228A1 (fr) Procédure de défaillance de trajet indirect en multi-trajet
WO2024109166A1 (fr) Changement de trajet indirect dans un trajet multiple
WO2024199052A1 (fr) Procédure de défaillance de trajet indirect due à ltm de l'ue relais dans un trajet multiple
WO2025251726A1 (fr) Mobilité déclenchée par couche 1 ou couche 2 conditionnelle
WO2024164606A1 (fr) Dispositifs et procédés de communication
WO2024093439A1 (fr) Ajout ou libération de trajet dans un trajet multiple inter-gnb
WO2025241602A1 (fr) Mobilité intra-rat et inter-rat
WO2024234727A1 (fr) Configuration simultanée pour changement de pcell et ajout/changement de pscell
WO2025107718A1 (fr) Prédiction de défaillance de liaison radio
WO2025097801A1 (fr) Dispositifs et procédés de communication
WO2025050684A1 (fr) Procédés et appareils pour une procédure de mobilité déclenchée par l1/l2 (ltm) et procédure de transfert conditionnel (cho)
WO2025145705A1 (fr) Saut d'occasion d'intervalle de mesure

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23893263

Country of ref document: EP

Kind code of ref document: A1