WO2024259991A1 - Défaillance dans une communication par relais - Google Patents

Défaillance dans une communication par relais Download PDF

Info

Publication number
WO2024259991A1
WO2024259991A1 PCT/CN2024/075386 CN2024075386W WO2024259991A1 WO 2024259991 A1 WO2024259991 A1 WO 2024259991A1 CN 2024075386 W CN2024075386 W CN 2024075386W WO 2024259991 A1 WO2024259991 A1 WO 2024259991A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay
remote
message
failure
base station
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/CN2024/075386
Other languages
English (en)
Inventor
Lianhai WU
Yibin ZHUO
Ran YUE
Jing HAN
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/CN2024/075386 priority Critical patent/WO2024259991A1/fr
Publication of WO2024259991A1 publication Critical patent/WO2024259991A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • 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
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • 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

Definitions

  • the present disclosure relates to wireless communications, and more specifically to user equipment (UE) , methods, apparatuses, processors, and computer readable medium for failure in a relay communication.
  • UE user equipment
  • 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
  • U2N UE-to-network
  • 3GPP third generation partner project
  • An indirect path is a type of U2N transmission path, where data is forwarded via at least one U2N relay UE between a U2N remote UE and the network.
  • a failure may occur and a communication between the remote UE and the network may be affected.
  • details on the U2N relay with at least two relay UEs are needed to be further studied.
  • the present disclosure relates to a first relay UE, a second relay UE, a remote UE, methods, apparatuses, processors, and computer readable medium for failure in a U2N relay communication.
  • a failure in case a failure occurs, other UEs in the communication may be aware of the failure in time, and thus one or more further operations may be performed to maintain the communication.
  • a first relay UE comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first relay UE to: determine whether a trigger event is happened, wherein the trigger event comprises one of: receiving a first message from a second relay UE which communicates with a base station, executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and the second relay UE, wherein the first relay UE is connected to the base station via the second relay UE, and wherein a remote UE is connected to the base station via the first relay UE and the second relay UE; and in accordance with a determination that the trigger event is happened, transmit, to the remote UE, a second message.
  • a first relay UE comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first relay UE to: determine whether a trigger event is happened, wherein the trigger event comprises one of: executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and a remote UE, wherein the first relay UE is connected to a base station via a second relay UE, and wherein the remote UE is connected to the base station via the first relay UE and the second relay UE; and in accordance with a determination that the trigger event is happened, transmit, to the second relay UE, a third message.
  • the trigger event comprises one of: executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and a remote UE, wherein the first relay UE is connected to a base station via a second relay UE, and wherein the remote UE is connected to the base station via the first relay
  • a remote UE comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the remote UE to: receive, from a first relay UE, a second message indicating a failure, wherein the first relay UE is connected to a base station via a second relay UE, and wherein the remote UE is connected to the base station via the first relay UE and the second relay UE; and initiate a re-establishment procedure based on the second message.
  • a second relay UE comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second relay UE to: receive, from a first relay UE, a third message indicating a failure, wherein the first relay UE is connected to a base station via the second relay UE, and wherein a remote UE is connected to the base station via the first relay UE and the second relay UE; and stop forwarding data towards the remote UE via the first relay UE.
  • a method performed by the first relay UE comprises: determining whether a trigger event is happened, wherein the trigger event comprises one of: receiving a first message from a second relay UE which communicates with a base station, executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and the second relay UE, wherein the first relay UE is connected to the base station via the second relay UE, and wherein a remote UE is connected to the base station via the first relay UE and the second relay UE; and in accordance with a determination that the trigger event is happened, transmitting, to the remote UE, a second message.
  • a method performed by the first relay UE comprises: determining whether a trigger event is happened, wherein the trigger event comprises one of: executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and a remote UE, wherein the first relay UE is connected to a base station via a second relay UE, and wherein the remote UE is connected to the base station via the first relay UE and the second relay UE; and in accordance with a determination that the trigger event is happened, transmitting, to the second relay UE, a third message.
  • a method performed by the remote UE comprises: receiving, from a first relay UE, a second message indicating a failure, wherein the first relay UE is connected to a base station via a second relay UE, and wherein the remote UE is connected to the base station via the first relay UE and the second relay UE; and initiating a re-establishment procedure based on the second message.
  • a method performed by the second relay UE comprises: receiving, from a first relay UE, a third message indicating a failure, wherein the first relay UE is connected to a base station via the second relay UE, and wherein a remote UE is connected to the base station via the first relay UE and the second relay UE; and stopping forwarding data towards the remote UE via the first relay UE.
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the processor to: determine whether a trigger event is happened, wherein the trigger event comprises one of: receiving a first message from a second relay UE which communicates with a base station, executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and the second relay UE, wherein the first relay UE is connected to the base station via the second relay UE, and wherein a remote UE is connected to the base station via the first relay UE and the second relay UE; and in accordance with a determination that the trigger event is happened, transmit, to the remote UE, a second message.
  • the trigger event comprises one of: receiving a first message from a second relay UE which communicates with a base station, executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and the second relay UE, wherein the first relay UE is connected
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the processor to: determine whether a trigger event is happened, wherein the trigger event comprises one of: executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and a remote UE, wherein the first relay UE is connected to a base station via a second relay UE, and wherein the remote UE is connected to the base station via the first relay UE and the second relay UE; and in accordance with a determination that the trigger event is happened, transmit, to the second relay UE, a third message.
  • the trigger event comprises one of: executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and a remote UE, wherein the first relay UE is connected to a base station via a second relay UE, and wherein the remote UE is connected to the base station via the first relay UE and the second relay UE; and
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a first relay UE, a second message indicating a failure, wherein the first relay UE is connected to a base station via a second relay UE, and wherein the remote UE is connected to the base station via the first relay UE and the second relay UE; and initiate a re-establishment procedure based on the second message.
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a first relay UE, a third message indicating a failure, wherein the first relay UE is connected to a base station via the second relay UE, and wherein a remote UE is connected to the base station via the first relay UE and the second relay UE; and stop forwarding data towards the remote UE via the first relay UE.
  • the methods and the first relay UE described herein further comprising: receiving, from the second relay UE, the first message being a notification message or a release message.
  • the second message indicates a failure between the first relay UE and the second relay UE or between the second relay UE and the base station, further comprising: receiving, from the first relay UE, a further notification message indicating that a re-establishment procedure of the first relay UE is successful.
  • the remote UE described herein further comprising: in accordance with a determination that the remote UE is in an idle or inactive state and the link with the first relay UE is to be released, providing indication to an upper layer of the remote UE to release the link with the first relay UE.
  • the first message is a notification message or a release message
  • the notification message comprises a first failure type indicating one of the following: an RLF between the second relay UE and the base station, a handover of the second relay UE, a cell reselection of the second relay UE, a radio resource control (RRC) connection establishment failure of the second relay UE, or an RRC connection resume failure of the second relay UE.
  • RRC radio resource control
  • the second message comprises a second failure type indicating one of the following: the RLF between the second relay UE and the base station, the handover of the second relay UE, the cell reselection of the second relay UE, the RRC connection establishment failure of the second relay UE, the RRC connection resume failure of the second relay UE, or a reception of the release message from the second relay UE.
  • the second message comprises a second failure type indicating that the re-establishment procedure of the first relay UE is failed.
  • the second message comprises: information indicating that the re-establishment procedure is successful, and a re-established cell identifier or relay identifier selected by the first relay UE for a re-establishment procedure of the first relay UE.
  • the second message comprises a second failure type indicating the handover of the first relay UE.
  • the second message comprises a second failure type indicating an RLF between the first relay UE and the second relay UE.
  • the third message comprises a third failure type indicating the handover of the first relay UE.
  • the third message indicates an RLF between the first relay UE and the remote UE, and the third message comprises an identifier of the remote UE.
  • FIG. 1 illustrates an example of a wireless communications system in which some embodiments of the present disclosure can be implemented
  • FIG. 2A illustrates a schematic diagram of an example communication network in which some embodiments of the present disclosure can be implemented
  • FIG. 2B illustrates a schematic diagram of an example communication network in which some embodiments of the present disclosure can be implemented
  • FIG. 3 illustrates a signalling chart illustrating communication process in accordance with some example embodiments of the present disclosure
  • FIG. 4 illustrates a signalling chart illustrating communication process in accordance with some example embodiments of the present disclosure
  • FIG. 5 illustrates a signalling chart illustrating communication process in accordance with some example embodiments of the present disclosure
  • FIG. 6 illustrates a signalling chart illustrating communication process in accordance with some example embodiments of the present disclosure
  • FIG. 7 illustrates an example of a device that is suitable for implementing embodiments of the present disclosure
  • FIG. 8 illustrates an example of a processor that is suitable for implementing some embodiments of the present disclosure
  • FIG. 9 illustrates a flowchart of an example method implemented at a first relay UE in accordance with aspects of the present disclosure
  • FIG. 10 illustrates a flowchart of an example method implemented at a first relay UE in accordance with aspects of the present disclosure
  • FIG. 11 illustrates a flowchart of an example method implemented at a remote UE in accordance with aspects of the present disclosure.
  • FIG. 12 illustrates a flowchart of an example method implemented at a second relay UE in accordance with aspects of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms. In some examples, values, procedures, or apparatuses are referred to as “best, ” “lowest, ” “highest, ” “minimum, ” “maximum, ” or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • the term “includes” and its variants are to be read as open terms that mean “includes, but is not limited to. ”
  • the term “based on” is to be read as “based at least in part on. ”
  • the term “one embodiment” and “an embodiment” are to be read as “at least one embodiment. ”
  • the term “another embodiment” is to be read as “at least one other embodiment. ”
  • the use of an expression such as “Aand/or B” can mean either “only A” or “only B” or “both A and B. ”
  • Other definitions, explicit and implicit, may be included below.
  • FIG. 1 illustrates an example of a wireless communications system 100 in which some embodiments of the present disclosure can be implemented.
  • the wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network (CN) 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 a long term evolution (LTE) network or an LTE-Advanced (LTE-A) network.
  • LTE long term evolution
  • LTE-A LTE-Advanced
  • the wireless communications system 100 may be a 5G network, such as a new radio (NR) network.
  • NR new radio
  • 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 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 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the network entities 102 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 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • a network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, message, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112.
  • a network entity 102 and a UE 104 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 102 may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • 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 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 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 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 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 104 may be stationary in the wireless communications system 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1.
  • a UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the CN 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 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink (SL) .
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • a network entity 102 may support communications with the CN 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the CN 106 through one or more backhaul links 116 (e.g., via an S1, N2, N3, or another network interface) .
  • the network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the CN 106) .
  • one or more network entities 102 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 104 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 102 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 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)) .
  • 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) .
  • One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 102 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 network entities 102 that are in communication via such communication links.
  • the CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the CN 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 104 served by the one or more network entities 102 associated with the CN 106.
  • NAS non-access stratum
  • the CN 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N3, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • one or more UEs 104 may communicate with the application server 118.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via a network entity 102.
  • the CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 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 104 and the CN 106 (e.g., one or more network functions of the CN 106) .
  • the network entities 102 and the UEs 104 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 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the network entities 102 and the UEs 104 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 102 and the UEs 104, 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) .
  • proximity communication 5 (PC5) link may be used interchangeably with PC5 interface, sidelink (SL) , PC5 unicast link, SL unicast link, device-to-device (D2D) link, user-to-user link, UE-to-UE (U2U) link, or the like.
  • the term “relay UE” may be used interchangeably with U2N relay UE, U2U relay UE, layer 2 (L2) relay UE, L2 U2N relay UE, L2 U2U relay UE, or the like.
  • the term “relay UE ID” may be used interchangeably with link ID, path ID, L2 relay UE ID, or the like.
  • a failure type may also be used interchangeably with a failure cause, a cause value, a cause type, etc., the present disclosure does not limit this aspect.
  • a wireless communications system may include one or more devices, such as one or more base stations and/or one or more UEs.
  • two different UEs may communicate with each other via a PC5 link (PC5 interface)
  • two different base stations may communicate with each other via an Xn link (Xn interface)
  • Xn interface Xn link
  • Uu link Uu interface
  • FIG. 2A illustrates a schematic diagram of an example communication network 210 in which some embodiments of the present disclosure can be implemented.
  • a UE 211 may communicate with a base station via a relay UE.
  • the base station may be a gNB 212 or an NG-eNB 213, and the relay UE may be a relay UE 214 or a relay UE 215.
  • the NG-eNB 213 may be an evolved long term evolution (eLTE) base station that supports an NG interface.
  • eLTE evolved long term evolution
  • the sidelink transmission and reception over the PC5 link are supported when the UE 211 is inside Next Generation Radio Access Network (NG-RAN) coverage, irrespective of which RRC state the UE is in, and also supported when the UE 211 is outside NG-RAN coverage.
  • NG-RAN Next Generation Radio Access Network
  • U2N Relay UE 5G ProSe UE-to-Network (U2N) Relay function to provide connectivity to the network for U2N Remote UE.
  • a U2N Relay UE shall be in RRC_CONNECTED to perform relaying of unicast data.
  • RRC state combinations are supported:
  • Both L2 U2N Relay UE and L2 U2N Remote UE shall be in RRC_CONNECTED to perform transmission/reception of relayed unicast data;
  • the L2 U2N Relay UE can be in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED as long as all the L2 U2N Remote UE (s) that are connected to the L2 U2N Relay UE are either in RRC_INACTIVE or in RRC_IDLE.
  • a single unicast link is established between one L2 U2N Relay UE and one L2 U2N Remote UE.
  • the traffic of L2 U2N Remote UE via a given L2 U2N Relay UE and the traffic of the L2 U2N Relay UE shall be separated in different Uu Relay RLC channels.
  • more than one relay UE is needed for a communication of the U2N remote UE.
  • FIG. 2B illustrates a schematic diagram of an example communication network 220 in which some embodiments of the present disclosure can be implemented.
  • the communication network 220 includes a remote UE 221-1 which is connected to the base station 224 via a relay UE 222-1 and a relay UE 223.
  • the communication network 220 also include a remote UE 221-2 which is connected to the base station 224 via a relay UE 222-2 and a relay UE 223.
  • the relay UE 222-2 and the relay UE 223 are located in coverage of the base station 224, while the remote UE 221-1, the remote UE 221-2, and the relay UE 222-1 are outside the coverage of the base station 224.
  • the remote UE 221-1 and the remote UE 221-2 can be collectively or separately referred to as a remote UE 221, and the relay UE 222-1 and the relay UE 222-2 can be collectively or separately referred to as a first relay UE 222.
  • a remote UE 221 accesses the base station 224 via two relay UEs including a first relay UE and a second relay UE, and the first relay UE accesses (e.g. connects) the base station 224 via the second relay UE.
  • the second relay UE may also be called as a parent relay UE, a first hop relay UE, a top relay UE, etc.
  • the first relay UE may also be called as a child relay UE, a second hop relay UE, etc.
  • the relay UE 222 may be the child relay UE or the first relay UE; and the relay UE 223 may be the parent relay UE or the second relay UE.
  • FIG. 2B the number of devices in FIG. 2B is given for the purpose of illustration without suggesting any limitations to the present disclosure. For example, there may be more relay UEs between the remote UE 221 and the base station 224.
  • FIG. 3 illustrates a signalling chart illustrating communication process 300 in accordance with some example embodiments of the present disclosure.
  • the process 300 may involve the remote UE 221, the first relay UE 222, the second relay UE 223, and the base station 224 as shown in FIG. 2B. It is to be understood that the process 300 may also be applied to another scenario different from that shown in FIG. 2B, the present disclosure does not limit this aspect.
  • the remote UE 221 is connected to the BS 224 via the first relay UE 222 and the second relay UE 223, where the second relay UE 223 connects to the BS 224 via a Uu interface, and the first relay UE 222 connects to the BS 224 via the second relay UE.
  • the first relay UE 222 will access the BS 224 (i.e. serving gNB) via an L2 U2N relay UE (such as the second relay UE 223) before the remote UE 221 accesses the BS 224 via the two relay UEs 222 and 223.
  • the remote UE 221 if the remote UE 221 is in an RRC connected (RRC_CONNECTED) state, an end-to-end RRC connection between the remote UE 221 and the BS 224 is established.
  • RRC_CONNECTED RRC connected
  • the second relay UE 223 transmits a first message to the first relay UE 222 at 310.
  • the first message may be a notification message or a release message.
  • the notification message is a PC5 RRC message.
  • the release message could be a PC5-Smessage.
  • the PC5-Slayer is a layer above an access stratum (AS) layer.
  • the first message may be another type of message and the present disclosure does not limit this aspect.
  • the second relay UE 223 may transmit the first message: Uu RLF of the second relay UE 223, a handover of the second relay UE 223, a cell reselection of the second relay UE 223, an RRC connection establishment failure of the second relay UE 223, or an RRC connection resume failure of the second relay UE 223.
  • the first message may be a notification message which includes a first failure type, for example, the first failure type may indicate one of the following: Uu RLF of the second relay UE 223, a handover of the second relay UE 223, a cell reselection of the second relay UE 223, an RRC connection establishment failure of the second relay UE 223, or an RRC connection resume failure of the second relay UE 223.
  • the first message may be a release message. For example, there is no failure type included in the release message.
  • the first relay UE 222 initiates a re-establishment procedure at 320 after receiving the first message.
  • the first relay UE 222 transmits a second message to the remote UE 221 at 330 after receiving the first message.
  • the second message may be transmitted over a PC5 RRC link or a PC5-Slink between the first relay UE 222 and the remote UE 221.
  • the operations 320 and 330 may be performed independently.
  • the second message may be a notification message or a release message which is transmitted over a PC5 RRC link between the first relay UE 222 and the remote UE 221.
  • the second message is a notification message which include a second failure type.
  • the second failure type may be determined based on the received first message, for example, the second failure type may indicate one of: Uu RLF of the second relay UE 223, a handover of the second relay UE 223, a cell reselection of the second relay UE 223, an RRC connection establishment failure of the second relay UE 223, an RRC connection resume failure of the second relay UE 223, or a reception of a release message from the second relay UE 223 (e.g. the first message is a release message) .
  • the second message may be a notification message which further includes information about whether the first relay UE 222 decides to keep the current PC5 link or not.
  • whether the second message is a notification message or a release message may be determined based on a predefined principle.
  • the predefined principle may be one of principle 1, principle 2, principle 3, or principle 4 below.
  • a notification message may be used as the second message transmitted to the remote UE 221.
  • the second message which is a notification message may include a second failure type indicating a reception of the release message from the second relay UE 223.
  • the second message at 330 may depend on a result of the re-establishment procedure of the first relay UE 222.
  • the second message is transmitted after the re-establishment procedure of the first relay UE 222 is finished, for example, the re-establishment procedure of the first relay UE 222 may be successful or may be failed.
  • the re-establishment procedure of the first relay UE 222 at 320 is successful, for example, the first relay UE 222 successfully completes its re-establishment procedure, then the second message may indicate that the re-establishment procedure of the first relay UE 222 is successful.
  • the second message may include a re-established cell ID or relay ID.
  • the second message may be omitted, that is, the first relay UE 222 may not transmit the second message to the remote UE 221.
  • the re-establishment procedure of the first relay UE 222 at 320 is failed, for example, the first relay UE 222 fails to complete its re-establishment procedure, then the second message may be a notification message which indicates that the re-establishment procedure of the first relay UE 222 is failed or may be a release message.
  • the remote UE 221 initiates a re-establishment procedure at 340 after receiving the second message.
  • the second message may indicate that a re-establishment procedure of the first relay UE 222 is successful, and the second message may include a re-established cell ID or relay ID, in this case, the remote UE 221 may determine whether the re-established cell ID or relay ID is the same as that of the second relay UE 223. In some examples, if the re-established cell ID or relay ID is the same as that of the second relay UE 223, the remote UE 221 may do nothing, for example, no re-establishment procedure is needed.
  • the remote UE 221 may initiate the re-establishment procedure via the same relay UE (i.e. the first relay UE 222) .
  • the remote UE 221 may perform a relay selection or a cell selection, and the same relay UE (i.e. the first relay UE 222) will be selected.
  • the second message may be a notification message which include a second failure type as described above, or the second message may be a release message, or the second message may indicate that a re-establishment procedure of the first relay UE 222 is failed, in this case, the remote UE 221 may initiate the re-establishment procedure.
  • the remote UE 221 may perform a relay reselection or a cell reselection, for example, the same relay UE (i.e. the first relay UE 222) will not be selected, that is, the remote UE 221 will avoid selecting the same relay UE.
  • the first relay UE 222 may transmit a second message to the remote UE 221 in case a first message is received from the second relay UE 223, therefore a re-establishment procedure may be initiated.
  • the operations shown in FIG. 3 are only for illustration without any limitation.
  • the second message at 330 may be omitted in case a re-establishment procedure is successful and the second relay UE 223 is still used.
  • the re-establishment procedure at 340 may be omitted in case the second message indicates a successful re-establishment procedure of the first relay UE 222 and the second relay UE 223 is still used.
  • a further notification may be transmitted from the first relay UE 222 to the remote UE 221.
  • the first relay UE 222 may transmit the second message which may be a notification message indicating a failure.
  • the remote UE 221 may not initiate a re-establishment procedure after receiving the second message.
  • the PC5 link towards the second relay UE 223 may be suspended or continue being kept.
  • the first relay UE 222 may transmit the further notification message to the remote UE 221 after a completion of the re-establishment procedure (e.g. successful or failed) .
  • FIG. 4 illustrates a signalling chart illustrating communication process 400 in accordance with some example embodiments of the present disclosure.
  • the process 400 may involve the remote UE 221, the first relay UE 222, the second relay UE 223, and the base station 224 as shown in FIG. 2B. It is to be understood that the process 400 may also be applied to another scenario different from that shown in FIG. 2B, the present disclosure does not limit this aspect.
  • the remote UE 221 is connected to the BS 224 via the first relay UE 222 and the second relay UE 223, where the second relay UE 223 connects to the BS 224 via a Uu interface, and the first relay UE 222 connects to the BS 224 via the second relay UE.
  • the first relay UE 222 will access the BS 224 (i.e. serving gNB) via an L2 U2N relay UE (such as the second relay UE 223) before the remote UE 221 accesses the BS 224 via the two relay UEs 222 and 223.
  • the remote UE 221 if the remote UE 221 is in an RRC connected (RRC_CONNECTED) state, an end-to-end RRC connection between the remote UE 221 and the BS 224 is established.
  • RRC_CONNECTED RRC connected
  • the first relay UE 222 executes a handover towards a candidate cell or a candidate relay UE at 410.
  • the candidate cell is provided by another base station different from the BS 224.
  • the candidate relay UE is different from the second relay UE 223.
  • the first relay UE 222 may be configured with a CHO configuration, in some examples, the first relay UE 222 may determine that an execution condition of the CHO candidate cell is met. In some other implementations, the first relay UE 222 may receive a handover command from its serving gNB (such as the BS 224) .
  • the first relay UE 222 transmits a second message to the remote UE 221 at 420 and transmits a third message to the second relay UE 223 at 430.
  • the second and third messages may be triggered after the first relay UE 222 executes the handover towards the candidate cell or the candidate relay UE.
  • the second message transmitted to the remote UE 221 may be a notification message or a release message.
  • the notification message may include a second failure type indicating a handover of the first relay UE 222.
  • the second failure type may be a newly defined value or an existing value associated with a handover.
  • the third message transmitted to the second relay UE 223 may be a notification message or a release message or a newly defined PC5 message.
  • the third message may include a failure type indicating a handover of the first relay UE 222.
  • the remote UE 221 may initiate a re-establishment procedure at 440.
  • the second relay UE 223 may stop forwarding data towards the remote UE 221 at 450.
  • the remote UE 221 and the second relay UE 223 may be aware of the handover, and thus one or more necessary operations may be performed. For example, a re-establishment procedure may be initiated by the remote UE 221, to make sure that a communication between the remote UE 221 and the BS 224 is performed. For example, the forwarding of data towards the remote UE 221 may be stopped by the second relay UE 223, therefore, the transmission resource may be used for other communications.
  • FIG. 5 illustrates a signalling chart illustrating communication process 500 in accordance with some example embodiments of the present disclosure.
  • the process 500 may involve the remote UE 221, the first relay UE 222, the second relay UE 223, and the base station 224 as shown in FIG. 2B. It is to be understood that the process 500 may also be applied to another scenario different from that shown in FIG. 2B, the present disclosure does not limit this aspect.
  • the remote UE 221 is connected to the BS 224 via the first relay UE 222 and the second relay UE 223, where the second relay UE 223 connects to the BS 224 via a Uu interface, and the first relay UE 222 connects to the BS 224 via the second relay UE.
  • the first relay UE 222 will access the BS 224 (i.e. serving gNB) via an L2 U2N relay UE (such as the second relay UE 223) before the remote UE 221 accesses the BS 224 via the two relay UEs 222 and 223.
  • the remote UE 221 if the remote UE 221 is in an RRC connected (RRC_CONNECTED) state, an end-to-end RRC connection between the remote UE 221 and the BS 224 is established.
  • RRC_CONNECTED RRC connected
  • the first relay UE 222 detects an RLF between the first relay UE 222 and the second relay UE 223 at 510. In some implementations, the first relay UE 222 may detect whether the sidelink between the first relay UE 222 and the second relay UE 223 is failed.
  • the first relay UE 222 initiates a re-establishment procedure at 520 after detecting the RLF between the first relay UE 222 and the second relay UE 223.
  • the first relay UE 222 transmits a second message to the remote UE 221 at 530 after detecting the RLF between the first relay UE 222 and the second relay UE 223.
  • the second message may be transmitted over a PC5 RRC link or a PC5-Slink between the first relay UE 222 and the remote UE 221.
  • the second message at 530 may be a notification message which includes a second failure type.
  • the second failure type may indicate the RLF between the first relay UE 222 and the second relay UE 223.
  • the remote UE 221 initiates a re-establishment procedure at 540 after receiving the second message.
  • an upper layer of the remote UE 221 may be instructed to trigger the PC5 unicast link release.
  • an RRC layer of the remote UE 221 may provide an indication to the PC5-Slayer of the remote UE 221.
  • the remote UE 221 may consider that a cell re-selection occurs.
  • the second message may be transmitted to the remote UE 221, in this case, the remote UE 221 may be aware of the RLF between the first relay UE 222 and the second relay UE 223, and thus one or more necessary operations may be performed.
  • the PC5 RRC connection may be released or be maintained by the remote UE 221.
  • FIG. 6 illustrates a signalling chart illustrating communication process 600 in accordance with some example embodiments of the present disclosure.
  • the process 600 may involve the remote UE 221, the first relay UE 222, the second relay UE 223, and the base station 224 as shown in FIG. 2B. It is to be understood that the process 600 may also be applied to another scenario different from that shown in FIG. 2B, the present disclosure does not limit this aspect.
  • the remote UE 221 is connected to the BS 224 via the first relay UE 222 and the second relay UE 223, where the second relay UE 223 connects to the BS 224 via a Uu interface, and the first relay UE 222 connects to the BS 224 via the second relay UE.
  • the first relay UE 222 will access the BS 224 (i.e. serving gNB) via an L2 U2N relay UE (such as the second relay UE 223) before the remote UE 221 accesses the BS 224 via the two relay UEs 222 and 223.
  • the remote UE 221 if the remote UE 221 is in an RRC connected (RRC_CONNECTED) state, an end-to-end RRC connection between the remote UE 221 and the BS 224 is established.
  • RRC_CONNECTED RRC connected
  • the first relay UE 222 detects an RLF between the first relay UE 222 and the remote UE 221. In some implementations, the first relay UE 222 may detect whether the sidelink between the first relay UE 222 and the remote UE 221 is failed.
  • the first relay UE 222 transmits a third message to the second relay UE 223 at 620 after detecting the RLF between the first relay UE 222 and the remote UE 221.
  • the third message may be transmitted over a PC5 RRC link or a PC5-S link between the first relay UE 222 and the second relay UE 223.
  • the third message at 620 may include an ID of the remote UE 221, such as a local UE ID for the remote UE 221.
  • the second relay UE 223 stops forwarding data towards the remote UE 221.
  • the third message may be transmitted to the second relay UE 223, in this case, the second relay UE 223 may be aware of the RLF between the first relay UE 222 and the remote UE 221, and thus one or more necessary operations may be performed. For example, the forwarding of data towards the remote UE 221 may be stopped by the second relay UE 223, therefore, the transmission resource may be used for other communications.
  • FIG. 7 illustrates an example of a device 700 that is suitable for implementing embodiments of the present disclosure.
  • the device 700 may be an example of a RAN node as described herein.
  • the device 700 may support wireless communication with the remote UE 221, the first relay UE 222, the second relay UE 223, or any combination thereof.
  • the device 700 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 702, a memory 704, a transceiver 706, and, optionally, an I/O controller 708. 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 702, the memory 704, the transceiver 706, 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 702, the memory 704, the transceiver 706, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 702, the memory 704, the transceiver 706, 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 702 and the memory 704 coupled with the processor 702 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704) .
  • the processor 702 may support wireless communication at the device 700 in accordance with examples as disclosed herein.
  • the processor 702 may be configured to operable to support a means for actions discussed above.
  • the processor 702 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 702 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 702.
  • the processor 702 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 704) to cause the device 700 to perform various functions of the present disclosure.
  • the memory 704 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 702 cause the device 700 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 702 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 704 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 708 may manage input and output signals for the device 700.
  • the I/O controller 708 may also manage peripherals not integrated into the device M02.
  • the I/O controller 708 may represent a physical connection or port to an external peripheral.
  • the I/O controller 708 may utilize an operating system such as or another known operating system.
  • the I/O controller 708 may be implemented as part of a processor, such as the processor 706.
  • a user may interact with the device 700 via the I/O controller 708 or via hardware components controlled by the I/O controller 708.
  • the device 700 may include a single antenna 710. However, in some other implementations, the device 700 may have more than one antenna 710 (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 706 may communicate bi-directionally, via the one or more antennas 710, wired, or wireless links as described herein.
  • the transceiver 706 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 706 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 710 for transmission, and to demodulate packets received from the one or more antennas 710.
  • the transceiver 706 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 710 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 710 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. 8 illustrates an example of a processor 800 that is suitable for implementing some embodiments of the present disclosure.
  • the processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein.
  • the processor 800 may optionally include at least one memory 804, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806.
  • 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 800 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 800) 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 802 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 800 to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction (s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may be configured to track memory address of instructions associated with the memory 804.
  • the controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 802 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may be configured to manage flow of data within the processor 800.
  • the controller 802 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 800.
  • ALUs arithmetic logic units
  • the memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800) . In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800) .
  • caches e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800) . In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800) .
  • the memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 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 802 and/or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions.
  • the processor 800 and/or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein.
  • the processor 800 may include multiple processors and the memory 804 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 806 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800) .
  • the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800) .
  • One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 806 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 806 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 806 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 806 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 800 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 800 may be configured to or operable to support a means for operations described in some embodiments of the present disclosure.
  • FIG. 9 illustrates a flowchart of a method 900 performed by a first relay UE 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 the first relay UE 222 in FIG. 2B.
  • 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 may include receiving a first message from a second relay UE which communicates with a base station, executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and the second relay UE, wherein the first relay UE is connected to the base station via the second relay UE, and wherein a remote UE is connected to the base station via the first relay UE and the second relay UE.
  • the operations of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 910 may be performed by the first relay UE 222 as described with reference to FIG. 2B.
  • the method may include in accordance with a determination that the trigger event is happened, transmitting, to the remote UE, a second message.
  • the operations of 920 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 920 may be performed by the first relay UE 222 as described with reference to FIG. 2B.
  • FIG. 10 illustrates a flowchart of a method 1000 performed by a first relay UE 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 the first relay UE 222 in FIG. 2B.
  • 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 may include determining whether a trigger event is happened, wherein the trigger event comprises one of: executing a handover towards a candidate cell or a candidate relay UE, or detecting a failure between the first relay UE and a remote UE, wherein the first relay UE is connected to a base station via a second relay UE, and wherein the remote UE is connected to the base station via the first relay UE and the second relay UE.
  • the operations of 1010 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1010 may be performed by the first relay UE 222 as described with reference to FIG. 2B.
  • the method may include in accordance with a determination that the trigger event is happened, transmitting, to the second relay UE, a third message.
  • the operations of 1020 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1020 may be performed by the first relay UE 222 as described with reference to FIG. 2B.
  • FIG. 11 illustrates a flowchart of a method 1100 performed by a remote UE in accordance with aspects of the present disclosure.
  • the operations of the method 1100 may be implemented by a device or its components as described herein.
  • the operations of the method 1100 may be performed by the remote UE 221 in FIG. 2B.
  • 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 may include receiving, from a first relay UE, a second message indicating a failure, wherein the first relay UE is connected to a base station via a second relay UE, and wherein the remote UE is connected to the base station via the first relay UE and the second relay UE.
  • the operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by the remote UE 221 as described with reference to FIG. 2B.
  • the method may include initiating a re-establishment procedure based on the second message.
  • the operations of 1120 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1120 may be performed by the remote UE 221 as described with reference to FIG. 2B.
  • FIG. 12 illustrates a flowchart of a method 1200 performed by a second rely UE in accordance with aspects of the present disclosure.
  • the operations of the method 1200 may be implemented by a device or its components as described herein.
  • the operations of the method 1200 may be performed by the second relay UE 223 in FIG. 2B.
  • 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 may include receiving, from a first relay UE, a third message indicating a failure, wherein the first relay UE is connected to a base station via the second relay UE, and wherein a remote UE is connected to the base station via the first relay UE and the second relay UE.
  • the operations of 1210 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1210 may be performed by the second relay UE 223 as described with reference to FIG. 2B.
  • the method may include stopping forwarding data towards the remote UE via the first relay UE.
  • the operations of 1220 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1220 may be performed by the second relay UE 223 as described with reference to FIG. 2B.
  • 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.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.

Landscapes

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

Abstract

Des exemples de modes de réalisation de la présente divulgation concernent un premier UE relais, un second UE relais, un UE distant, des procédés, des appareils, des processeurs et un support lisible par ordinateur pour une défaillance dans une communication relais. Un premier UE relais peut déterminer si un événement déclencheur s'est produit, l'événement déclencheur comprenant par exemple une des actions suivantes : la réception d'un premier message provenant d'un second UE relais, l'exécution d'un transfert vers une cellule candidate ou un UE relais candidat, la détection d'une défaillance entre le premier UE relais et le second UE relais, ou la détection d'une défaillance entre le premier UE relais et l'UE distant. De plus, le premier UE relais peut transmettre un deuxième message à l'UE distant ou un troisième message au deuxième UE relais. La solution proposée permet ainsi, dans le cas où une défaillance se produit, que d'autres UE dans la communication aient connaissance de la défaillance en temps voulu, et qu'une ou plusieurs autres opérations soient effectuées pour maintenir la communication.
PCT/CN2024/075386 2024-02-02 2024-02-02 Défaillance dans une communication par relais Pending WO2024259991A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/075386 WO2024259991A1 (fr) 2024-02-02 2024-02-02 Défaillance dans une communication par relais

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/075386 WO2024259991A1 (fr) 2024-02-02 2024-02-02 Défaillance dans une communication par relais

Publications (1)

Publication Number Publication Date
WO2024259991A1 true WO2024259991A1 (fr) 2024-12-26

Family

ID=93934815

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/075386 Pending WO2024259991A1 (fr) 2024-02-02 2024-02-02 Défaillance dans une communication par relais

Country Status (1)

Country Link
WO (1) WO2024259991A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102021113144A1 (de) * 2020-05-20 2021-11-25 Intel Corporation Relais-(neu-)auswahl über sidelink in zellularen netzwerken
WO2022027548A1 (fr) * 2020-08-07 2022-02-10 Qualcomm Incorporated Défaillance de liaison radio dans un relais de liaison latérale
US20230269809A1 (en) * 2020-08-17 2023-08-24 Qualcomm Incorporated Rrc re-establishment and radio link failure reporting in sidelink relay systems
US20240023189A1 (en) * 2021-03-30 2024-01-18 Vivo Mobile Communication Co., Ltd. Communication Path Switching Method and Terminal

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102021113144A1 (de) * 2020-05-20 2021-11-25 Intel Corporation Relais-(neu-)auswahl über sidelink in zellularen netzwerken
WO2022027548A1 (fr) * 2020-08-07 2022-02-10 Qualcomm Incorporated Défaillance de liaison radio dans un relais de liaison latérale
US20230269809A1 (en) * 2020-08-17 2023-08-24 Qualcomm Incorporated Rrc re-establishment and radio link failure reporting in sidelink relay systems
US20240023189A1 (en) * 2021-03-30 2024-01-18 Vivo Mobile Communication Co., Ltd. Communication Path Switching Method and Terminal

Similar Documents

Publication Publication Date Title
WO2024093428A9 (fr) Mécanisme pour cho avec des scg candidats
WO2024234727A1 (fr) Configuration simultanée pour changement de pcell et ajout/changement de pscell
WO2024094228A1 (fr) Procédure de défaillance de trajet indirect en multi-trajet
WO2024250686A1 (fr) Prédiction d'échec de transfert
WO2024093655A1 (fr) Division de données de liaison montante déclenchée par état de retard
WO2024159795A1 (fr) Dispositifs et procédés de communication
WO2024259991A1 (fr) Défaillance dans une communication par relais
WO2024199052A1 (fr) Procédure de défaillance de trajet indirect due à ltm de l'ue relais dans un trajet multiple
WO2024109166A1 (fr) Changement de trajet indirect dans un trajet multiple
WO2024098839A1 (fr) Ajout de trajet indirect pour communication u2n
WO2025251726A1 (fr) Mobilité déclenchée par couche 1 ou couche 2 conditionnelle
WO2024207740A1 (fr) Mobilité déclenchée de couche 1 ou de couche 2
WO2025035808A1 (fr) Gestion de connexion pc5 de bout en bout dans un relais u2u
WO2024093439A1 (fr) Ajout ou libération de trajet dans un trajet multiple inter-gnb
WO2025107677A1 (fr) Dispositifs et procédés de communication
WO2024244539A1 (fr) Transfert d'informations de radiomessagerie dans une communication relais
WO2025097801A1 (fr) Dispositifs et procédés de communication
WO2025175830A1 (fr) Mobilité déclenchée par couche 1 ou couche 2 conditionnelle
WO2026025974A1 (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
WO2025145658A1 (fr) Contrôle d'accès d'une cellule ntn
WO2025107718A1 (fr) Prédiction de défaillance de liaison radio
WO2025246425A1 (fr) Gestion de ressource
WO2026091642A1 (fr) Planification d'un ensemble de pdu dl sur la base d'un retard dl
WO2025011026A1 (fr) Sélection de groupe de ressources

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: 24824894

Country of ref document: EP

Kind code of ref document: A1