[go: up one dir, main page]

WO2024098839A1 - Ajout de trajet indirect pour communication u2n - Google Patents

Ajout de trajet indirect pour communication u2n Download PDF

Info

Publication number
WO2024098839A1
WO2024098839A1 PCT/CN2023/109366 CN2023109366W WO2024098839A1 WO 2024098839 A1 WO2024098839 A1 WO 2024098839A1 CN 2023109366 W CN2023109366 W CN 2023109366W WO 2024098839 A1 WO2024098839 A1 WO 2024098839A1
Authority
WO
WIPO (PCT)
Prior art keywords
indirect
path
base station
message
relay
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/109366
Other languages
English (en)
Inventor
Lianhai WU
Ran YUE
Le Yan
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/109366 priority Critical patent/WO2024098839A1/fr
Publication of WO2024098839A1 publication Critical patent/WO2024098839A1/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/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • 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
    • 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
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations

Definitions

  • the present disclosure relates to wireless communications, and more specifically to network units, methods, apparatuses, and computer readable medium for indirect path addition for user equipment (UE) -to-network (U2N) communication.
  • UE user equipment
  • U2N user network
  • 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
  • An indirect path is a type of U2N transmission path, where data is forwarded via a U2N relay UE between a U2N Remote UE and the network.
  • An indirect path may be added so that a remote UE may communicate with a base station via a relay UE.
  • some details need to be further studied.
  • the present disclosure relates to network units, methods, apparatuses, and computer readable medium for indirect path addition for U2N communication.
  • a UE comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a base station, a configuration message for adding one or more indirect paths between the UE and the base station; perform, based on the configuration message, an indirect path addition procedure by starting at least one timer; and transmit, to the base station, a response message indicating a result of the indirect path addition procedure.
  • a base station comprising at least one memory; and at least one processor coupled with the at least one memory and configured to cause the base station to: transmit, to a UE, a configuration message for adding one or more indirect paths between the UE and the base station; and receive, from the UE, a response message indicating a result of an indirect path addition procedure performed by the UE based on the configuration message.
  • a method performed by the UE comprises: receiving, from a base station, a configuration message for adding one or more indirect paths between the UE and the base station; performing, based on the configuration message, an indirect path addition procedure by starting at least one timer; and transmitting, to the base station, a response message indicating a result of the indirect path addition procedure.
  • a method performed by the base station comprises: transmitting, to a UE, a configuration message for adding one or more indirect paths between the UE and the base station; and receiving, from the UE, a response message indicating a result of an indirect path addition procedure performed by the UE based on the configuration 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 base station, a configuration message for adding one or more indirect paths between the UE and the base station; perform, based on the configuration message, an indirect path addition procedure by starting at least one timer; and transmit, to the base station, a response message indicating a result of the indirect path addition procedure.
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the processor to: transmit, to a UE, a configuration message for adding one or more indirect paths between the UE and the base station; and receive, from the UE, a response message indicating a result of an indirect path addition procedure performed by the UE based on the configuration message.
  • the configuration message indicates adding a plurality indirect paths
  • the configuration message comprises an indication of a time length for the at least one timer
  • the UE starts a plurality of timers for the plurality of indirect paths respectively.
  • the UE stops a first timer, among the plurality of timers, for a first indirect path of the plurality of indirect paths or determines that the first timer expires, based on a determination that the first indirect path meets one or more following conditions: a reception of a notification message or a release message from a first relay UE associated with the first indirect path, a reception of a radio resource control (RRC) reconfiguration failure sidelink message from the first relay UE, or a detection of a radio link failure (RLF) of a proximity communication 5 (PC5) link between the UE and the first relay UE; and determines that an addition for the first indirect path is failed.
  • RRC radio resource control
  • RLF radio link failure
  • the UE starts a timer for all of the plurality of indirect paths.
  • the UE stops the timer for all of the plurality of indirect paths or determines that the timer expires, based on a determination that each of the plurality of indirect paths meets one or more conditions, wherein the one or more conditions for a first indirect path of the plurality of indirect paths comprises: a reception of a notification message or a release message from a first relay UE associated with the first indirect path, a reception of an RRC reconfiguration failure sidelink message from the first relay UE, or a detection of an RLF of a PC5 link between the UE and the first relay UE; and determines that an addition for all of the plurality of indirect paths is failed.
  • the UE in accordance with a determination that at least one of the one or more indirect paths is successfully added in the indirect path addition procedure, the UE transmits the response message to the base station via one of at least one added indirect path, wherein the response message is an RRC reconfiguration complete message.
  • the RRC reconfiguration complete message comprises at least one of: at least one path identifier (ID) of the at least one added indirect path, or failure information of one or more failed indirect paths.
  • ID path identifier
  • the UE in accordance with a determination that none of the one or more indirect paths is successfully added in the indirect path addition procedure, transmits the response message to the base station via a direct path between the UE and the base station, wherein the response message is a failure report comprising failure information of one or more failed indirect paths.
  • the failure information indicates at least one of: one or more path IDs of the one or more failed indirect paths, or one or more failure types for the one or more failed indirect paths.
  • a first failure type, among the one or more failure types, for a first indirect path of the one or more failed indirect paths indicates one of: an RLF of a PC5 link between the UE and a first relay UE on the first indirect path, a reception of a notification message or a release message from the first relay UE, or an expiry of a timer associated with the first indirect path.
  • the notification message or the release message from the first relay UE indicates one of: an RLF of a Uu link between the first relay UE and the base station, a cell resection of the first relay UE, a failure of an RRC connection establishment at the first relay UE, or a failure of an RRC connection resume at the first relay UE.
  • a path ID comprises a relay UE ID in an associated indirect path.
  • the UE determines that a second indirect path of the one or more indirect paths is successfully added; and in accordance with a determination that the added second indirect path is failed, transmits, to the base station via a direct path or an available indirect path, a failure report indicating that the second indirect path is failed.
  • the failure report comprises at least one of: a path ID of the second indirect path, or a failure type for the second indirect path.
  • the UE transmits, to the base station, capability information indicating at least one of: whether to support one or more indirect paths between the UE and the base station, or a maximum number of the one or more indirect paths supported by the UE.
  • the configuration message indicates adding a plurality indirect paths, and wherein the configuration message comprises an indication of a time length for the at least one timer.
  • the base station receives the response message from the UE via one of at least one added indirect path, wherein the response message is an RRC reconfiguration complete message.
  • the RRC reconfiguration complete message comprises at least one of: at least one path ID of the at least one added indirect path, or failure information of one or more failed indirect paths.
  • the base station receives the response message from the UE via a direct path between the UE and the base station, wherein the response message is a failure report indicating that none of the one or more indirect paths is successfully added in the indirect path addition procedure, and wherein the failure report comprises failure information of one or more failed indirect paths.
  • the failure information indicates at least one of: one or more path IDs of the one or more failed indirect paths, or one or more failure types for the one or more failed indirect paths.
  • a first failure type, among the one or more failure types, for a first indirect path of the one or more failed indirect paths indicates one of: an RLF of a PC5 link between the UE and a first relay UE on the first indirect path, a reception of a notification message or a release message from the first relay UE, or an expiry of a timer associated with the first indirect path.
  • the notification message or the release message from the first relay UE indicates one of: an RLF of a Uu link between the first relay UE and the base station, a cell resection of the first relay UE, a failure of an RRC connection establishment at the first relay UE, or a failure of an RRC connection resume at the first relay UE.
  • a path ID comprises a relay UE ID in an associated indirect path.
  • the base station receives, from the UE via a direct path or an available indirect path, a failure report indicating that a second indirect path which has been successfully added is failed.
  • the failure report comprises at least one of: a path ID of the second indirect path, or a failure type for the second indirect path.
  • the base station receives, from the UE, capability information indicating at least one of: whether to support one or more indirect paths between the UE and the base station, or a maximum number of the one or more indirect paths supported by the 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 an example RRC reconfiguration sidelink procedure
  • FIG. 3A illustrates an example flow signalling for successful second indirect path addition
  • FIG. 3B illustrates an example UE information procedure
  • FIG. 4 illustrates a schematic diagram of an example communication network in which some embodiments of the present disclosure can be implemented
  • FIG. 5 illustrates a signalling chart illustrating communication process in accordance with some example embodiments of the present disclosure
  • FIG. 6 illustrates an example of a device that is suitable for implementing embodiments of the present disclosure
  • FIG. 7 illustrates an example of a processor that is suitable for implementing some embodiments of the present disclosure
  • FIG. 8 illustrates a flowchart of an example method implemented at a UE in accordance with aspects of the present disclosure.
  • FIG. 9 illustrates a flowchart of an example method implemented at a base station in accordance with some embodiments 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 “A and/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 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 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 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 core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 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 core network 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 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 104 served by the one or more network entities 102 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, 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 core network 106 via a network entity 102.
  • the core network 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 core network 106 (e.g., one or more network functions of the core network 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, layer 2 (L2) relay UE, L2 U2N relay UE, or the like.
  • path ID may be used interchangeably with link ID, relay UE ID, L2 relay UE ID, or the like.
  • a wireless communications system may include one or more devices, such as one or more NEs and/or one or more UEs.
  • two different UEs may communicate with each other via a PC5 link
  • 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 and when the UE 211 is outside NG-RAN coverage.
  • NG-RAN Next Generation Radio Access Network
  • FIG. 2B illustrates an example RRC reconfiguration sidelink procedure 220.
  • a UE 221 may transmit an RRCReconfigurationSidelink message to a UE 222, and the UE 222 may transmit an RRCReconfigurationCompleteSidelink message back to the UE 221.
  • the purpose of the procedure 220 is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink data radio bearers (DRBs) , to configure NR sidelink measurement and reporting, to configure sidelink channel state indicator (CSI) reference signal resources.
  • DRBs sidelink data radio bearers
  • CSI sidelink channel state indicator
  • the UE (such as the UE 221) may initiate the sidelink RRC reconfiguration procedure and perform an operation on the corresponding PC5-RRC connection in following cases:
  • FIG. 3A illustrates an example flow signalling 310 for successful second indirect path addition.
  • a remote UE 311 may perform a measurement report to the serving gNB 313 at step 1.
  • a second indirect path via a relay UE may be decided to be added by the serving gNB 313 at step 2.
  • an RRC reconfiguration for path addition may be transmitted from the serving gNB 313 to the remote UE 311.
  • a PC5 connection between the remote UE 311 and the relay UE 312 may be established based on a PC5 connection establishment message at step 4, and an RRC reconfiguration message for remote UE 311 may be transmitted from the serving gNB 313 to the relay UE 312.
  • an indicate path is added after an RRC reconfiguration complete message at step 6, and data transmission or reception at step 7 may be performed.
  • FIG. 3B illustrates an example UE information procedure 320.
  • the UE information procedure 320 may be used by the network to 322 request the UE 321 to report information e.g., rlf-report or successful handover report (SHR) .
  • the network 322 initiates the procedure 320 by sending a UE Information Request message.
  • the network 322 should initiate this procedure 320 only after successful security activation.
  • the UE 321 reports a UE Information Response including rlf-report or SHR to the network 322 after receiving the UE Information Request message.
  • the UE For analysis of connection failures, the UE makes the RLF Report available to the network.
  • the UE stores the latest RLF Report, including both LTE and NR RLF report until the RLF report is fetched by the network or for 48 hours after the connection failure is detected.
  • the UE only indicates RLF report availability and only provides the RLF report to the network if the current registered public land mobile network (RPLMN) is a PLMN that was present in the UE's equivalent PLMN (EPLMN) List or was the RPLMN at the time the connection failure was detected.
  • RPLMN public land mobile network
  • EPLMN equivalent PLMN
  • the UE makes the LTE RLF Report available to NG-RAN nodes and eNB (s)
  • the UE makes the NR RLF Report available to gNB (s) .
  • the NG-RAN node may transfer it to the E-UTRAN node by triggering the Uplink RAN configuration transfer procedure over NG, and the E-UTRAN node can take this into account.
  • an indirect path may be added so that a remote UE may communicate with a base station via a relay UE.
  • 3GPP is discussing a possibility of adding multiple indirect paths. However, in case of multiple indirect paths are needed to be added, some details need to be further studied.
  • Embodiments of the present disclosure provide a solution of communication.
  • a UE may receive a configuration message from a base station, where the configuration message may be used for adding one or more indirect paths between the UE and the base station.
  • the UE may perform an indirect path addition procedure by starting at least one timer; and the UE may transmit a response message to the UE to notify a result of the indirect path addition procedure.
  • a procedure of adding more than one indirect path may be defined and the communication between the UE and the base station may be guaranteed.
  • FIG. 4 illustrates a schematic diagram of an example communication network 400 in which some embodiments of the present disclosure can be implemented.
  • the communication network 400 may include a UE 410 and a base station 430 which may communicate with each other via a direct path.
  • the direct path may be associated with a Uu link there between.
  • the base station 430 may be a serving network device of the UE 410, such as a serving gNB.
  • the communication network 400 may further include a UE 422 and a UE 424.
  • the one or more indirect paths may include an indirect path between the UE 410 and the base station 430 via the UE 422, and/or an indirect path between the UE 410 and the base station 430 via the UE 424.
  • the UE 410 may be a remote UE
  • the UE 422 or 424 may be a relay UE.
  • the base station 430 may communicate with the UE 422/424 via a Uu link, and the UE 410 may communicate with the UE 422/424 via a PC5 link.
  • the UE 410 and the UE 422/424 may communicate with each other via a sidelink channel, such as a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , a physical sidelink feedback channel (PSFCH) , a physical sidelink broadcast channel (PSBCH) or the like.
  • a sidelink channel such as a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , a physical sidelink feedback channel (PSFCH) , a physical sidelink broadcast channel (PSBCH) or the like.
  • a PC5 link or PC5 RRC connection may be established between the UE 410 and the UE 422/424.
  • the UE 422/424 may locate within the coverage of the base station 430. In some embodiments, the UE 410 may move to outside of the coverage of the base station 430. The present disclosure does not limit this aspect.
  • 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 UE 410 and the base station 430 as shown in FIG. 4. It would be appreciated that the process 500 may be applied to other communication scenarios, which will not be described in detail.
  • the UE 410 may be in (i.e., stays at) an RRC connected state, and the UE 410 may access the base station 430 (such as a serving gNB) via a direct path.
  • the base station 430 such as a serving gNB
  • the UE 410 may transmit capability information to the base station 430, e.g., via the direct path.
  • the capability information may indicate whether the UE 410 supports multiple indirect paths.
  • the capability information may indicate a maximum number of the multiple indirect paths the UE 410 supported. For example, the maximum number may be represented as N, which is an integer not smaller than 0.
  • the capability information may indicate that the UE 410 does not support multiple indirect paths, and/or a maximum number of supported indirect paths is 1. In some other examples, the capability information may indicate that the UE 410 supports multiple indirect paths, and/or a maximum number of supported indirect paths is N>1. In some other examples, the capability information may indicate that a maximum number of supported indirect paths is N>1, which can implicitly indicate that the UE 410 supports multiple indirect paths.
  • the UE 410 may report its capability of supporting multiple indirect paths, alternatively, the maximum number of supported indirect paths may be reported to the network.
  • the base station 430 transmits 510 a configuration message 512 to the UE 410.
  • the configuration message 512 may be an RRC reconfiguration message which is used for adding one or more indirect paths between the UE 410 and the base station 430.
  • a number of the one or more indirect paths may be no more than the maximum number indicated in the capability information discussed above.
  • the configuration message 512 may include one or more path IDs of the one or more indirect paths.
  • a path ID may be represented as or may include a relay UE ID associated with the indirect path.
  • one or more candidate relay UE IDs may be included in the configuration message 512.
  • the configuration message 512 may instruct the UE 410 to adding multiple indirect paths between the UE 410 and the base station 430, e.g., the configuration message 512 include multiple candidate relay UE IDs.
  • the configuration message 512 include multiple candidate relay UE IDs.
  • two relay UE IDs of the UE 422 and the UE 424 may be included in the configuration message 512 for adding two indirect paths.
  • the configuration message 512 may include an indication of a time length for at least one timer.
  • the UE 410 receives 514 the configuration message 512.
  • the UE 410 performs 520 an indirect path addition procedure, and the UE 410 transmits 530 a response message 532 to the base station 430.
  • the UE 410 may start a timer, e.g., upon receiving the configuration message 512.
  • the timer may be set with a time length indicated by the configuration message 512.
  • the timer i.e., a single timer
  • the UE 410 may maintain the timer for all of the multiple indirect paths.
  • the UE 410 may stop the timer or consider that the timer expires if none of the multiple indirect paths is successfully added. In some examples, if all of the multiple indicate paths are failed added, the UE 410 may stop the timer or consider the timer expiry. Take a first indirect path as an example, where the first indicate path is associated with a first relay UE, then the first indirect path is not successfully added if one of the following conditions (1) - (3) meets:
  • the notification message or the release message may indicate one of: an RLF of a Uu link between the first relay UE and the base station 430, a handover of the first relay UE, a failure of an RRC connection establishment of the first relay UE (e.g., an RRC connection request is rejected by the base station 430, or a timer T300 associated with an RRC connection procedure expires) , a failure of an RRC connection resume of the first relay UE, or a cell reselection of the first relay UE.
  • the release message may be a PC5-S message or a PC5 unicast link release message, received by a higher layer of the UE 410 and provided to a lower layer.
  • the UE 410 may transmit an RRC reconfiguration complete message to the base station 430, in other words, the response message 532 may be the RRC reconfiguration complete message.
  • the RRC reconfiguration complete message may be transmitted via a successfully added indirect path, such as an available indirect path.
  • the indirect path for transmitting the RRC reconfiguration complete message may be any one of those successfully added indirect paths, or may be an indirect path that is firstly available in the indirect path addition procedure.
  • the UE 410 may stop the timer upon successfully sending the RRC reconfiguration complete message. For example, in case a PC5 RLC acknowledgement (ACK) has been received from a relay UE, the UE 410 may stop the timer.
  • ACK PC5 RLC acknowledgement
  • the RRC reconfiguration complete message may be transmitted from the UE 410 to the base station 430 via one of the multiple indirect paths.
  • the RRC reconfiguration complete message may include multiple path IDs (such as multiple relay UE IDs) of the multiple indirect paths successfully added.
  • the UE 410 may transmit the RRC reconfiguration complete message to the base station 430 via one of the at least one added indirect path.
  • the RRC reconfiguration complete message may include at least one path ID (such as at least one relay UE ID) of the at least one added indirect path.
  • the RRC reconfiguration complete message may include failure information of one or more failed indirect paths.
  • the failure information may indicate one or more path IDs (such as one or more relay UE IDs) of the one or more failed indirect paths.
  • the failure information may indicate one or more failure types for the one or more failed indirect paths.
  • the failure information may include a path ID of a first failed indirect path and corresponding failure type. As such, the base station 430 may be aware of which indirect path is failed and why it is failed.
  • a failure type may indicate a failure cause or a failure reason of a corresponding failed indirect path.
  • a failure type of the first failed indirect path may indicate one of: an RLF of a PC5 link between the UE 410 and the relay UE #1 on the first failed indirect path, or a reception of a notification message or a release message from the relay UE #1 on the first failed indirect path.
  • the notification message or the release message may indicate one of: an RLF of a Uu link between the relay UE #1 and the base station 430, a handover of the relay UE #1, an RRC connection failure of the relay UE #1 (e.g., an RRC connection request is rejected by the base station 430, or a timer T300 associated with an RRC connection procedure expires) , an RRC resume failure of the relay UE #1, or a cell reselection of the relay UE #1.
  • the release message may be a PC5-S message or a PC5 unicast link release message, received by a higher layer of the UE 410 and provided to a lower layer.
  • the UE 410 may transmit a failure report to the base station 430, in other words, the response message 532 may be the failure report.
  • the failure report may be transmitted via the direct path between the UE 410 and the base station 430.
  • the timer (the single timer) is running until expires.
  • the failure report may include failure information of the multiple failed indirect paths.
  • the failure information may indicate multiple path IDs (such as multiple relay UE IDs) of the multiple failed indirect paths.
  • the failure information may indicate multiple failure types for the multiple failed indirect paths.
  • failure information for a specific failed indirect path may include a path ID of the specific failed indirect path and corresponding failure type. It is to be noted that the failure information for a specific failed indirect path may refer to those described above, for ease of description, the details will not be repeated herein.
  • the UE 410 may start multiple timers for the multiple indirect paths respectively, e.g., upon receiving the configuration message 512.
  • each of the multiple timers may be set with a time length indicated by the configuration message 512.
  • one of the multiple timers is used for an associated indirect path.
  • separate timers are started by the UE 410 for each of the multiple indirect paths.
  • each of the multiple timers may be T420.
  • a first timer is used for a first indirect path associated with a first relay UE
  • a second timer is used for a second indirect path associated with a second relay UE, ...etc.
  • the UE 410 may maintain the multiple timers for each of the multiple indirect paths.
  • the UE 410 may stop a timer used for the specific indirect path or consider the timer used for the specific indirect path expires if one of the following conditions (4) - (6) meets:
  • the notification message or the release message may indicate one of: an RLF of a Uu link between the first relay UE and the base station 430, a failure of an RRC connection establishment of the first relay UE (e.g., an RRC connection request is rejected by the base station 430, or a timer T300 associated with an RRC connection procedure expires) , a failure of an RRC connection resume of the first relay UE, or a cell reselection of the first relay UE.
  • the release message may be a PC5-S message or a PC5 unicast link release message, received by a higher layer of the UE 410 and provided to a lower layer e.g., an access stratum (AS) layer.
  • AS access stratum
  • the UE 410 may determine that the specific indirect path is failed in case a failed condition is met, for example, the failed condition may be one of the conditions (4) - (6) above, or the failed condition may be an expiry of the timer used for the specific indirect path.
  • the UE 410 may transmit an RRC reconfiguration complete message to the base station 430, in other words, the response message 532 may be the RRC reconfiguration complete message.
  • the RRC reconfiguration complete message may be transmitted via a successfully added indirect path, such as an available indirect path.
  • the indirect path for transmitting the RRC reconfiguration complete message may be any one of those successfully added indirect paths, or may be an indirect path that is firstly available in the indirect path addition procedure.
  • the RRC reconfiguration complete message may include at least one path ID (at least one relay UE ID) of at least one added indirect path.
  • the RRC reconfiguration complete message may include failure information of one or more failed indirect paths.
  • the failure information may indicate one or more path IDs (such as one or more relay UE IDs) of the one or more failed indirect paths.
  • the failure information may indicate one or more failure types for the one or more failed indirect paths.
  • the failure information may include a path ID of a first failed indirect path and corresponding failure type.
  • a failure type may indicate a failure cause or a failure reason of a corresponding failed indirect path.
  • a failure type of the first failed indirect path may indicate one of:
  • the notification message or the release message may indicate one of: an RLF of a Uu link between the relay UE #1 and the base station 430, an RRC connection failure of the relay UE #1 (e.g., an RRC connection request is rejected by the base station 430, or a timer T300 associated with an RRC connection procedure expires) , an RRC resume failure of the relay UE #1, or a cell reselection of the relay UE #1.
  • the release message may be a PC5-S message or a PC5 unicast link release message, received by a higher layer of the UE 410 and provided to a lower layer e.g., an AS layer.
  • the UE 410 may transmit a failure report to the base station 430, in other words, the response message 532 may be the failure report.
  • the failure report may be transmitted via the direct path between the UE 410 and the base station 430.
  • the failure report may include failure information of the multiple failed indirect paths.
  • the failure information may indicate multiple path IDs (such as multiple relay UE IDs) of the multiple failed indirect paths.
  • the failure information may indicate multiple failure types for the multiple failed indirect paths.
  • failure information for a specific failed indirect path may include a path ID of the specific failed indirect path and corresponding failure type. It is to be noted that the failure information for a specific failed indirect path may refer to those described above, for ease of description, the details will not be repeated herein.
  • the UE 410 may transmit an RRC reconfiguration complete message to the base station 430. In some examples, the UE 410 may further receive or transmit data via the at least one added indirect path.
  • the base station 430 receives 534 the response message 532.
  • the response message 532 may be an RRC reconfiguration complete message indicating at least one added indirect path.
  • each indirect path may be associated with a relay UE.
  • multiple indirect paths are activated and are used for communication between the UE 410 and the base station 430.
  • the UE 410 may transmit a failure report of the second indirect path to the base station 430.
  • the failure report of the second indirect path may indicate that the second indirect path is failed.
  • the UE 410 may determine that the second indirect path fails. For example, if the UE 410 receives a notification message or a release message from the relay UE of the second indirect path, the UE 410 may determine that the second indirect path fails, where the notification message or the release message may indicate one of: an RLF of the Uu link between the relay UE of the second indirect path and the base station 430, a handover of relay UE, an RRC connection failure, or the like.
  • the failure report of the second indirect path may be transmitted via a direct path or via an available indirect path.
  • the failure report of the second indirect path may indicate a path ID of the second indirect path and/or a failure type of the second indirect path.
  • the failure type may indicate a failure cause or a failure reason of the second indirect path, for example, the failure type may indicate one of: an RLF of the PC5 link, a reception of a notification message, or a reception of a release message.
  • the failure report of the one indirect path may be transmitted via the other one indirect path.
  • the path ID of the failed indirect path may be omitted, that is, the failure report may not include the path ID of the failed indirect path may be omitted. As such, an overhead of signalling may be saved.
  • the UE 410 may receive a configuration message for adding multiple indirect paths, and perform an indirect path addition procedure by starting at least one timer. Therefore, a procedure for adding multiple indirect paths is defined.
  • the UE 410 may transmit a response message to the base station 430 indicating a result of the indirect path addition procedure. Therefore, the base station 430 may be aware of which of the multiple indirect paths is added successfully, and thus a further communication may be enabled.
  • FIG. 6 illustrates an example of a device 600 that is suitable for implementing embodiments of the present disclosure.
  • the device 600 may be an example of a UE or a base station as described herein.
  • the device 600 may support wireless communication with the UE 410, the base station 430, or any combination thereof.
  • the device 600 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 602, a memory 604, a transceiver 606, and, optionally, an I/O controller 608. 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) .
  • interfaces e.g., buses
  • the processor 602, the memory 604, the transceiver 606, 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 602, the memory 604, the transceiver 606, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 602, the memory 604, the transceiver 606, 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 602 and the memory 604 coupled with the processor 602 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604) .
  • the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein.
  • the processor 602 may be configured to operable to support a means for receiving, from a base station, a configuration message for adding one or more indirect paths between the UE and the base station; means for performing, based on the configuration message, an indirect path addition procedure by starting at least one timer; and means for transmitting, to the base station, a response message indicating a result of the indirect path addition procedure.
  • the processor 602 may be configured to operable to support a means for transmitting, to a UE, a configuration message for adding one or more indirect paths between the UE and the base station; and means for receiving, from the UE, a response message indicating a result of an indirect path addition procedure performed by the UE based on the configuration message.
  • the processor 602 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 602 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 602.
  • the processor 602 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 604) to cause the device 600 to perform various functions of the present disclosure.
  • the memory 604 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 602 cause the device 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 code may not be directly executable by the processor 602 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 604 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 608 may manage input and output signals for the device 600.
  • the I/O controller 608 may also manage peripherals not integrated into the device M02.
  • the I/O controller 608 may represent a physical connection or port to an external peripheral.
  • the I/O controller 608 may utilize an operating system such as or another known operating system.
  • the I/O controller 608 may be implemented as part of a processor, such as the processor 606.
  • a user may interact with the device 600 via the I/O controller 608 or via hardware components controlled by the I/O controller 608.
  • the device 600 may include a single antenna 610. However, in some other implementations, the device 600 may have more than one antenna 610 (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 606 may communicate bi-directionally, via the one or more antennas 610, wired, or wireless links as described herein.
  • the transceiver 606 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 606 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 610 for transmission, and to demodulate packets received from the one or more antennas 610.
  • the transceiver 606 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 610 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 610 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. 7 illustrates an example of a processor 700 that is suitable for implementing some embodiments of the present disclosure.
  • the processor 700 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 700 may include a controller 702 configured to perform various operations in accordance with examples as described herein.
  • the processor 700 may optionally include at least one memory 704, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 700 may optionally include one or more arithmetic-logic units (ALUs) 700.
  • 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 700 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 700) 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 702 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 700 to cause the processor 700 to support various operations in accordance with examples as described herein.
  • the controller 702 may operate as a control unit of the processor 700, generating control signals that manage the operation of various components of the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instruction (s) to be executed to cause the processor 700 to support various operations in accordance with examples as described herein.
  • the controller 702 may be configured to track memory address of instructions associated with the memory 704.
  • the controller 702 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 702 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein.
  • the controller 702 may be configured to manage flow of data within the processor 700.
  • the controller 702 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 700.
  • ALUs arithmetic logic units
  • the memory 704 may include one or more caches (e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700) . In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700) .
  • caches e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700) . In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700) .
  • the memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 700, cause the processor 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 controller 702 and/or the processor 700 may be configured to execute computer-readable instructions stored in the memory 704 to cause the processor 700 to perform various functions.
  • the processor 700 and/or the controller 702 may be coupled with or to the memory 704, the processor 700, the controller 702, and the memory 704 may be configured to perform various functions described herein.
  • the processor 700 may include multiple processors and the memory 704 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 700 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 700 may reside within or on a processor chipset (e.g., the processor 700) .
  • the one or more ALUs 700 may reside external to the processor chipset (e.g., the processor 700) .
  • One or more ALUs 700 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 700 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 700 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 700 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 700 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 700 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 700 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 700 may be configured to or operable to support a means for operations described in some embodiments of the present disclosure.
  • FIG. 8 illustrates a flowchart of a method 800 performed by a UE 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 UE 410 in FIG. 4.
  • 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 base station, a configuration message for adding one or more indirect paths between the UE and the base station.
  • the operations of 810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 810 may be performed by the UE 410 as described with reference to FIG. 4.
  • the method may include performing, based on the configuration message, an indirect path addition procedure by starting at least one timer.
  • the operations of 820 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 820 may be performed by the UE 410 as described with reference to FIG. 4.
  • the method may include transmitting, to the base station, a response message indicating a result of the indirect path addition procedure.
  • the operations of 830 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 830 may be performed by the UE 410 as described with reference to FIG. 4.
  • the configuration message indicates adding a plurality indirect paths
  • the configuration message comprises an indication of a time length for the at least one timer
  • the UE starts a plurality of timers for the plurality of indirect paths respectively.
  • the UE stops a first timer, among the plurality of timers, for a first indirect path of the plurality of indirect paths or determines that the first timer expires, based on a determination that the first indirect path meets one or more following conditions: a reception of a notification message or a release message from a first relay UE associated with the first indirect path, a reception of an RRC reconfiguration failure sidelink message from the first relay UE, or a detection of an RLF of a PC5 link between the UE and the first relay UE; and determines that an addition for the first indirect path is failed.
  • the UE starts a timer for all of the plurality of indirect paths.
  • the UE stops the timer for all of the plurality of indirect paths or determines that the timer expires, based on a determination that each of the plurality of indirect paths meets one or more conditions, where the one or more conditions for a first indirect path of the plurality of indirect paths comprises: a reception of a notification message or a release message from a first relay UE associated with the first indirect path, a reception of an RRC reconfiguration failure sidelink message from the first relay UE, or a detection of an RLF of a PC5 link between the UE and the first relay UE; and determines that an addition for all of the plurality of indirect paths is failed.
  • the UE transmits the response message to the base station via one of at least one added indirect path, where the response message is an RRC reconfiguration complete message.
  • the RRC reconfiguration complete message comprises at least one of: at least one path ID of the at least one added indirect path, or failure information of one or more failed indirect paths.
  • the UE transmits the response message to the base station via a direct path between the UE and the base station, where the response message is a failure report comprising failure information of one or more failed indirect paths.
  • the failure information indicates at least one of: one or more path IDs of the one or more failed indirect paths, or one or more failure types for the one or more failed indirect paths.
  • a first failure type, among the one or more failure types, for a first indirect path of the one or more failed indirect paths indicates one of: an RLF of a PC5 link between the UE and a first relay UE on the first indirect path, a reception of a notification message or a release message from the first relay UE, or an expiry of a timer associated with the first indirect path.
  • the notification message or the release message from the first relay UE indicates one of: an RLF of a Uu link between the first relay UE and the base station, a cell resection of the first relay UE, a failure of an RRC connection establishment at the first relay UE, or a failure of an RRC connection resume at the first relay UE.
  • a path ID comprises a relay UE ID in an associated indirect path.
  • the UE determines that a second indirect path of the one or more indirect paths is successfully added; and if the added second indirect path is failed, transmits, to the base station via a direct path or an available indirect path, a failure report indicating that the second indirect path is failed.
  • the failure report comprises at least one of: a path ID of the second indirect path, or a failure type for the second indirect path.
  • the UE transmits, to the base station, capability information indicating at least one of: whether to support one or more indirect paths between the UE and the base station, or a maximum number of the one or more indirect paths supported by the UE.
  • FIG. 9 illustrates a flowchart of a method 900 performed by a base station 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 base station 430 in FIG. 4.
  • 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 transmitting, to a UE, a configuration message for adding one or more indirect paths between the UE and the base station.
  • 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 base station 430 as described with reference to FIG. 4.
  • the method may include receiving, from the UE, a response message indicating a result of an indirect path addition procedure performed by the UE based on the configuration 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 base station 430 as described with reference to FIG. 4.
  • the configuration message indicates adding a plurality indirect paths, and where the configuration message comprises an indication of a time length for the at least one timer.
  • the base station receives the response message from the UE via one of at least one added indirect path, where the response message is an RRC reconfiguration complete message.
  • the RRC reconfiguration complete message comprises at least one of: at least one path ID of the at least one added indirect path, or failure information of one or more failed indirect paths.
  • the base station receives the response message from the UE via a direct path between the UE and the base station, where the response message is a failure report indicating that none of the one or more indirect paths is successfully added in the indirect path addition procedure, and where the failure report comprises failure information of one or more failed indirect paths.
  • the failure information indicates at least one of: one or more path IDs of the one or more failed indirect paths, or one or more failure types for the one or more failed indirect paths.
  • a first failure type, among the one or more failure types, for a first indirect path of the one or more failed indirect paths indicates one of: an RLF of a PC5 link between the UE and a first relay UE on the first indirect path, a reception of a notification message or a release message from the first relay UE, or an expiry of a timer associated with the first indirect path.
  • the notification message or the release message from the first relay UE indicates one of: an RLF of a Uu link between the first relay UE and the base station, a cell resection of the first relay UE, a failure of an RRC connection establishment at the first relay UE, or a failure of an RRC connection resume at the first relay UE.
  • the base station receives, from the UE via a direct path or an available indirect path, a failure report indicating that a second indirect path which has been successfully added is failed.
  • the failure report comprises at least one of: a path ID of the second indirect path, or a failure type for the second indirect path.
  • the base station receives, from the UE, capability information indicating at least one of: whether to support one or more indirect paths between the UE and the base station, or a maximum number of the one or more indirect paths supported by the UE.
  • 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 modes de réalisation donnés à titre d'exemple de la présente invention concernent des dispositifs, des procédés et un support de stockage informatique pour un ajout de trajet indirect pour une communication U2N. Dans certains modes de réalisation, un UE reçoit un message de configuration en provenance d'une station de base, le message de configuration pouvant être utilisé pour ajouter un ou plusieurs trajets indirects entre l'UE et la station de base. De plus, l'UE peut effectuer une procédure d'ajout de trajet indirect par démarrage d'au moins un temporisateur; et l'UE peut transmettre un message de réponse à l'UE pour notifier un résultat de la procédure d'ajout de trajet indirect. Ainsi, une procédure d'ajout de plus d'un trajet indirect peut être définie et la communication entre l'UE et la station de base peut être garantie.
PCT/CN2023/109366 2023-07-26 2023-07-26 Ajout de trajet indirect pour communication u2n Pending WO2024098839A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/109366 WO2024098839A1 (fr) 2023-07-26 2023-07-26 Ajout de trajet indirect pour communication u2n

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/109366 WO2024098839A1 (fr) 2023-07-26 2023-07-26 Ajout de trajet indirect pour communication u2n

Publications (1)

Publication Number Publication Date
WO2024098839A1 true WO2024098839A1 (fr) 2024-05-16

Family

ID=91031871

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/109366 Pending WO2024098839A1 (fr) 2023-07-26 2023-07-26 Ajout de trajet indirect pour communication u2n

Country Status (1)

Country Link
WO (1) WO2024098839A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022236674A1 (fr) * 2021-05-11 2022-11-17 Qualcomm Incorporated Opérations de commutation de liaison hertzienne dans une communication sans fil
CN115843444A (zh) * 2022-09-30 2023-03-24 北京小米移动软件有限公司 路径添加方法和装置
WO2023044758A1 (fr) * 2021-09-24 2023-03-30 Apple Inc. Fonctionnement à trajets multiples dans un relais de liaison latérale d'équipement utilisateur à reseau (ue-to-nw)
WO2023123242A1 (fr) * 2021-12-30 2023-07-06 Lenovo (Beijing) Limited Procédés et appareils de traitement d'établissement et de défaillance en cas de multiples trajets

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022236674A1 (fr) * 2021-05-11 2022-11-17 Qualcomm Incorporated Opérations de commutation de liaison hertzienne dans une communication sans fil
WO2023044758A1 (fr) * 2021-09-24 2023-03-30 Apple Inc. Fonctionnement à trajets multiples dans un relais de liaison latérale d'équipement utilisateur à reseau (ue-to-nw)
WO2023123242A1 (fr) * 2021-12-30 2023-07-06 Lenovo (Beijing) Limited Procédés et appareils de traitement d'établissement et de défaillance en cas de multiples trajets
CN115843444A (zh) * 2022-09-30 2023-03-24 北京小米移动软件有限公司 路径添加方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Discussion on service continuity for L2 UE to NW Relay", 3GPP DRAFT; R2-2108622, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20210809 - 20210827, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052034961 *

Similar Documents

Publication Publication Date Title
WO2024093428A1 (fr) Mécanisme pour cho avec des scg candidats
WO2024183312A1 (fr) Procédés et appareils pour des procédures ltm intra-bs et inter-bs
WO2024098839A1 (fr) Ajout de trajet indirect pour communication u2n
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
WO2024094228A1 (fr) Procédure de défaillance de trajet indirect en multi-trajet
WO2024259991A1 (fr) Défaillance dans une communication par relais
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
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
WO2025251726A1 (fr) Mobilité déclenchée par couche 1 ou couche 2 conditionnelle
WO2025107718A1 (fr) Prédiction de défaillance de liaison radio
WO2024250686A1 (fr) Prédiction d'échec de transfert
WO2025148422A1 (fr) Procédés et appareils pour prendre en charge une mobilité déclenchée par l1/l2 (ltm) conditionnelle
WO2025222941A1 (fr) Collecte de données pendant des événements de mobilité
WO2024109164A1 (fr) Dispositifs et procédés de communication
WO2025145658A1 (fr) Contrôle d'accès d'une cellule ntn
WO2025156295A1 (fr) Continuité de service de multidiffusion ou de diffusion
WO2025256157A1 (fr) Récupération rapide basée sur un ltm
WO2025175830A1 (fr) Mobilité déclenchée par couche 1 ou couche 2 conditionnelle
WO2025097794A1 (fr) Acquisition de sib dans une communication relais
WO2025035789A1 (fr) Détection et mise à jour de dispositif aiot
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)

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

Country of ref document: EP

Kind code of ref document: A1