[go: up one dir, main page]

WO2024093439A1 - Ajout ou libération de trajet dans un trajet multiple inter-gnb - Google Patents

Ajout ou libération de trajet dans un trajet multiple inter-gnb Download PDF

Info

Publication number
WO2024093439A1
WO2024093439A1 PCT/CN2023/113293 CN2023113293W WO2024093439A1 WO 2024093439 A1 WO2024093439 A1 WO 2024093439A1 CN 2023113293 W CN2023113293 W CN 2023113293W WO 2024093439 A1 WO2024093439 A1 WO 2024093439A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran node
request
relay
path
message
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/113293
Other languages
English (en)
Inventor
Lianhai WU
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/CN2023/113293 priority Critical patent/WO2024093439A1/fr
Publication of WO2024093439A1 publication Critical patent/WO2024093439A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/03—Reselecting a link using a direct mode connection
    • H04W36/033—Reselecting a link using a direct mode connection in pre-organised networks
    • 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/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/302—Reselection being triggered by specific parameters by measured or perceived connection quality data due to low signal strength
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure

Definitions

  • the present disclosure relates to wireless communications, and more specifically to radio access network (RAN) nodes, methods, apparatuses, and computer readable medium for path addition or path release in inter-gNB multi-path communication.
  • RAN radio access 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
  • U2N UE-to-network
  • 3GPP third generation partner project
  • inter-gNB based multi-path is being discussed, for example, two different gNBs may communicate with the UE via a direct path and an indirect path respectively. However, some details need to be further studied for the inter-gNB multi-path.
  • the present disclosure relates to RAN nodes, methods, apparatuses, and computer readable medium for path addition or release in inter-gNB multi-path scenario.
  • the inter-gNB multi-path is supported.
  • a second RAN node comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second RAN node to: transmit, to a first RAN node, a request for adding a direct path between the first RAN node and a UE, wherein there has been an indirect path between the second RAN node and the UE via a relay UE; and receive, from the first RAN node, a response at least comprising a first configuration of the direct path.
  • a first RAN node comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first RAN node to: receive, from a second RAN node, a request for adding a direct path between the first RAN node and a UE, wherein there has been an indirect path between the second RAN node and the UE via a relay UE; and transmit, to the second RAN node, a response at least comprising a first configuration of the direct path.
  • a method performed by the second RAN node comprises: transmitting, to a first RAN node, a request for adding a direct path between the first RAN node and a UE, wherein there has been an indirect path between the second RAN node and the UE via a relay UE; and receiving, from the first RAN node, a response at least comprising a first configuration of the direct path.
  • a method performed by the first RAN node comprises: receiving, from a second RAN node, a request for adding a direct path between the first RAN node and a UE, wherein there has been an indirect path between the second RAN node and the UE via a relay UE; and transmitting, to the second RAN node, a response at least comprising a first configuration of the direct path.
  • 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 first RAN node, a request for adding a direct path between the first RAN node and a UE, wherein there has been an indirect path between the second RAN node and the UE via a relay UE; and receive, from the first RAN node, a response at least comprising a first configuration of the direct path.
  • 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 second RAN node, a request for adding a direct path between the first RAN node and a UE, wherein there has been an indirect path between the second RAN node and the UE via a relay UE; and transmit, to the second RAN node, a response at least comprising a first configuration of the direct path.
  • RRC radio resource control
  • the request comprises one of: an ID of the relay UE associated with the indirect path between the second RAN node and the UE, a cell ID of a cell which serves the relay UE, a configuration of the indirect path, a cell ID of a candidate cell, a cause value indicating a purpose of the request for direct path addition or multi-path establishment, UE context information of the UE, or at least one suggested radio bearer (RB) to be served by the first RAN node.
  • RB radio bearer
  • the UE context information comprises one of: information of one or more packet data unit (PDU) sessions, information of one or more RBs, or a quality of service (QoS) requirement for each of one or more RBs.
  • PDU packet data unit
  • QoS quality of service
  • the request is comprised in one of: a handover request message, a path switching request message, or a direct path addition message.
  • the response is comprised in one of: a handover request acknowledge message, or a path switching request acknowledge message.
  • a first RAN node comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first RAN node to: transmit, to a second RAN node, a request for primary cell (PCell) change or for releasing an indirect path, wherein there are a direct path between the first RAN node and a UE and the indirect path between the second RAN node and the UE via a relay UE; and receive, from the second RAN node, a response for accepting the request or rejecting the request.
  • PCell primary cell
  • a second RAN node comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second RAN node to: receive, from a first RAN node, a request for PCell change or for releasing an indirect path, wherein there are a direct path between the first RAN node and a UE and the indirect path between the second RAN node and the UE via a relay UE; and transmit, to the first RAN node, a response for accepting the request or rejecting the request.
  • a method performed by the first RAN node comprises: transmitting, to a second RAN node, a request for PCell change or for releasing an indirect path, wherein there are a direct path between the first RAN node and a UE and the indirect path between the second RAN node and the UE via a relay UE; and receiving, from the second RAN node, a response for accepting the request or rejecting the request.
  • a method performed by the second RAN node comprises: receiving, from a first RAN node, a request for PCell change or for releasing an indirect path, wherein there are a direct path between the first RAN node and a UE and the indirect path between the second RAN node and the UE via a relay UE; and transmitting, to the first RAN node, a response for accepting the request or rejecting the request.
  • 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 second RAN node, a request for PCell change or for releasing an indirect path, wherein there are a direct path between the first RAN node and a UE and the indirect path between the second RAN node and the UE via a relay UE; and receive, from the second RAN node, a response for accepting the request or rejecting the request.
  • 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 RAN node, a request for PCell change or for releasing an indirect path, wherein there are a direct path between the first RAN node and a UE and the indirect path between the second RAN node and the UE via a relay UE; and transmit, to the first RAN node, a response for accepting the request or rejecting the request.
  • the request is used for releasing the indirect path between the second RAN node and the UE via the relay UE, and the request comprises a cause value for releasing the indirect path.
  • the cause value indicates one of: a radio link failure (RLF) of a sidelink between the UE and the relay UE, an RLF of a Uu link between the relay UE and the second RAN node, a reception of a notification message at the UE from the relay UE, a reception of a release message at the UE from the relay UE, or a reduced bit rate of the UE.
  • RLF radio link failure
  • the request is comprised in one of: a secondary node (SN) release request message, or an indirect path release request message.
  • SN secondary node
  • the response is comprised in one of: an SN release request acknowledge message, or an indirect path release request acknowledge message.
  • the request is used for PCell change, and the request comprises one of: an ID of a candidate relay UE, a cause value indicating a purpose of the request, or information of buffer report (BR) in the direct path.
  • the request comprises one of: an ID of a candidate relay UE, a cause value indicating a purpose of the request, or information of buffer report (BR) in the direct path.
  • the candidate relay UE is the same as the relay UE associated with the indirect path between the second RAN node and the UE.
  • the response comprises a configuration of the indirect path associated with the candidate relay UE.
  • the request is comprised in a handover request message
  • the response is comprised in a handover request acknowledge message.
  • a second RAN node comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second RAN node to: transmit, to a first RAN node, a request for releasing an indirect path between the second RAN node and a UE via a relay UE, wherein there is a direct path between the first RAN node and the UE; and receive, from the first RAN node, a response indicating a confirmation of the request.
  • a first RAN node comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first RAN node to: receive, from a second RAN node, a request for releasing an indirect path between the second RAN node and a UE via a relay UE, wherein there is a direct path between the first RAN node and the UE; and transmit, to the second RAN node, a response indicating a confirmation of the request.
  • a method performed by the second RAN node comprises: transmitting, to a first RAN node, a request for releasing an indirect path between the second RAN node and a UE via a relay UE, wherein there is a direct path between the first RAN node and the UE; and receiving, from the first RAN node, a response indicating a confirmation of the request.
  • a method performed by the first RAN node comprises: receiving, from a second RAN node, a request for releasing an indirect path between the second RAN node and a UE via a relay UE, wherein there is a direct path between the first RAN node and the UE; and transmitting, to the second RAN node, a response indicating a confirmation of the request.
  • 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 first RAN node, a request for releasing an indirect path between the second RAN node and a UE via a relay UE, wherein there is a direct path between the first RAN node and the UE; and receive, from the first RAN node, a response indicating a confirmation of the request.
  • 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 second RAN node, a request for releasing an indirect path between the second RAN node and a UE via a relay UE, wherein there is a direct path between the first RAN node and the UE; and transmit, to the second RAN node, a response indicating a confirmation of the request.
  • the request comprises a cause value indicating a purpose of the request, and wherein the cause value indicates one of: an overload of the relay UE, an RLF of a sidelink between the UE and the relay UE, an RLF of a Uu link between the relay UE and the second RAN node, or a handover of the relay UE.
  • the request is comprised in an SN release required message
  • the response is comprised in an SN release confirm message
  • 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. 3 illustrates an example flow signalling for successful second indirect path addition
  • 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 for indirect path addition in accordance with some example embodiments of the present disclosure
  • FIG. 6 illustrates a signalling chart illustrating communication process for direct path addition in accordance with some example embodiments of the present disclosure
  • FIG. 7A illustrates a signalling chart illustrating communication process for releasing an indirect path in accordance with some example embodiments of the present disclosure
  • FIG. 7B illustrates a signalling chart illustrating communication process for releasing an indirect path in accordance with some example embodiments of the present disclosure
  • FIG. 8 illustrates a signalling chart illustrating communication process for PCell change in accordance with some example embodiments of the present disclosure
  • FIG. 9 illustrates an example of a device that is suitable for implementing embodiments of the present disclosure.
  • FIG. 10 illustrates an example of a processor that is suitable for implementing some embodiments of the present disclosure
  • FIG. 11 illustrates a flowchart of an example method implemented at a second RAN node in accordance with aspects of the present disclosure
  • FIG. 12 illustrates a flowchart of an example method implemented at a first RAN node in accordance with aspects of the present disclosure
  • FIG. 13 illustrates a flowchart of an example method implemented at a first RAN node in accordance with some embodiments of the present disclosure.
  • FIG. 14 illustrates a flowchart of an example method implemented at a second RAN node 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 “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.
  • relay UE ID may be used interchangeably with link ID, path ID, L2 relay UE ID, or the like.
  • 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
  • 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. 3 illustrates an example flow signalling 300 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 indirect path is added after an RRC reconfiguration complete message at step 6, and data transmission or reception at step 7 may be performed.
  • 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 inter-gNB based multi-path, for example, whether a dual connectivity (DC) framework is reused.
  • DC dual connectivity
  • One way forward (WF) is that DC framework can be reused, and PCell may be configured in direct path.
  • WF dual connectivity
  • the second way forward is that non-DC framework is used, and there is no secondary cell group (SCG) in multi-path case.
  • SCG secondary cell group
  • inter-gNB multi-path case one of the direct path and the indirect path may be added or released, and some details need to be further studied.
  • Embodiments of the present disclosure provide a solution of communication.
  • a second RAN node may communicate with a UE via an indirect path via a relay UE, and the second RAN node may transmit a request for adding a direct path between the first RAN node and a UE to the first RAN node.
  • the first RAN node may transmit a response including a first configuration of the direct path to the second RAN node.
  • a procedure of adding a direct path may be defined and the communication between the UE and the network side may be guaranteed. Therefore, an inter-gNB multi-path is supported. Principles and implementations of the present disclosure will be described in detail below with reference to the figures.
  • 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 first RAN node 410, a second RAN node 420, and a UE 430.
  • the first RAN node 410 and the UE 430 may communicate with each other via a direct path.
  • the direct path may be associated with a Uu link there between.
  • the first RAN node 410 may be a serving network device of the UE 430, such as a serving gNB.
  • the communication network 400 may further include a UE 425.
  • the second RAN node 420 may communicate with the UE 425 via a Uu link
  • the UE 430 may communicate with the UE 425 via a PC5 link.
  • the UE 430 may be a remote UE
  • the UE 425 may be a relay UE.
  • the multi-path scenario may be based on a DC framework or a non-DC framework, the present disclosure does not limit this aspect.
  • the first RAN node 410 and the second RAN node 420 may communicate with each other, e.g., via an Xn interface.
  • 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 a first RAN node 410, a second RAN node 420, a relay UE 425, and a UE 430, as show 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.
  • An initial scenario for process 500 may be that, there has been a direct path between the first RAN node 410 and the UE 430, while the indirect path between the second RAN node 420 and the UE 430 has not been established.
  • the UE 430 may be in (i.e., stays at) an RRC connected state, and the UE 430 may access the first RAN node 410 (such as serving gNB) via a direct path.
  • the UE 430 may transmit capability information of the UE 430 indicating whether the UE 430 supports inter-gNB multi-path, and it is assumed that the UE 430 has a capability of supporting the inter-gNB multi-path in the following description.
  • the UE 430 may transmit measurement results to the first RAN node 410, e.g., based on a measurement configuration.
  • the measurement results may include a UE ID of a relay UE (such as the relay UE 425 in FIG. 4) and corresponding sidelink reference signal received power (SL-RSRP) of the PC5 link between the UE 430 and the UE 425.
  • the measurement results may include an ID of a cell which serves the relay UE, e.g., a cell ID is included.
  • the cell ID may be a physical cell identifier (PCI) or E-UTRAN cell global identifier (ECGI) .
  • PCI physical cell identifier
  • ECGI E-UTRAN cell global identifier
  • the first RAN node 410 transmits, at 510, a request for adding an indirect path to the second RAN node 420.
  • the request may be included in an existing Xn message, such as S-NG-RAN node Addition Preparation message, e.g., if DC framework is used (or reused) .
  • the request may be included in a new Xn message, e.g., an indirect path addition preparation message.
  • the request may include at least one ID of the at least one candidate relay UE.
  • at least one candidate relay UE ID may be included in the request, where the at least one candidate relay UE is served by the second RAN node 420.
  • the at least one candidate relay UE may include the relay UE 425 as shown in FIG. 4.
  • the request may include at least one cell ID which indicates at least one cell serving the at least one candidate relay UE.
  • the request may include one or more candidate relay UE IDs and corresponding cell ID (s) .
  • the request may include an indication which indicates whether the at least one candidate relay UE belongs to a same cell or different cells.
  • an indication for indirect path addition for multi-path case may be included in the request.
  • the indication for indirect path addition for multi-path case may be included in SN Addition Trigger Indication.
  • the first RAN node 410 and the second RAN node 420 may consider that the purpose of the SN Addition Trigger Indication is to add the indirect path.
  • the request may include an ID of the UE 430, that is, a remote UE ID is included.
  • the second RAN node 420 transmits, at 520, a response to the request for adding indirect path to the first RAN node 410.
  • the second RAN node 420 may reject the request.
  • the response may include a rejection to the request.
  • the response may be included in an existing Xn message, such as S-NODE Addition Request Reject message, e.g., if DC framework is used (or reused) .
  • the response may be included in a new Xn message, e.g., an indirect path addition reject message.
  • the response may include a cause of the rejection.
  • the cause may indicate an overload of the at least one candidate relay UE.
  • the second RAN node 420 cannot find the at least one candidate relay UE (e.g., the possible reason is that the at least one candidate relay UE moves to other cells) , and the cause may indicate “no found relay” .
  • the cause may indicate relay UE leaving, e.g., the at least one candidate relay UE is moving outside coverage of the second RAN node 420.
  • the response may include one or more suggested candidate relay UEs and/or one or more suggested candidate cells, for example, the first RAN node 410 may generate another request based on the suggestion from the second RAN node 420.
  • the second RAN node 420 may accept the request.
  • the response may include an acceptance to the request.
  • the response may be included in an existing Xn message, such as S-NODE Addition Request Acknowledge message, e.g., if DC framework is used (or reused) .
  • the response may be included in a new Xn message, e.g., an indirect path addition request acknowledge message, which may include a relay UE ID and a cell ID associated with the indirect path to be added.
  • the second RAN node 420 may determine whether the candidate relay UE (such as UE 425 in FIG. 4) can be used as a target relay UE. For example, if accepted, the second RAN node 420 may transmit the response which includes a configuration related to the target relay UE, such as the relay UE 425 in FIG. 4. For example, the response may include a configuration of the indirect path between the second RAN node 420 and the UE 430 via the target relay UE 425.
  • the second RAN node 420 may determine (select) one of the multiple candidate relay UEs as the target relay UE, e.g., the relay UE 425 is selected.
  • the response may include an ID of the target relay UE 425 and a configuration of the indirect path between the second RAN node 420 and the UE 430 via the target relay UE 425.
  • the first RAN node 410 may transmit a reconfiguration message (RRC reconfiguration message) to the UE 430 at 530, where the reconfiguration message may be associated with the indirect path addition.
  • the reconfiguration message may include an ID of the target relay UE 425.
  • the reconfiguration message may include a cell ID of a target cell which serves the target relay UE 425.
  • the reconfiguration message may include a configuration of the indirect path between the second RAN node 420 and the UE 430 via the target relay UE 425.
  • the indirect path may be established between the second RAN node 420 and the UE 430 via the relay UE 425, at 540.
  • the UE 430 may perform an indirect path addition based on the reconfiguration message from the first RAN node 410.
  • the UE 430 may further transmit, at 550, an RRC reconfiguration complete message to the second RAN node 420 via the indirect path after the UE 430 successfully accesses the second RAN node 420.
  • the second RAN node 420 may further transmit, at 560, an indication of successful indirect path addition to the first RAN node 410, after receiving the RRC reconfiguration complete message from the UE 430.
  • the indirect path between the second RAN node 420 and the UE 430 may be added, and thus an inter-gNB multi-path may be supported. Accordingly, after the UE 430 has a connection with the first RAN node 410 via a direct path, an Xn enhancement for one indirect path addition is proposed.
  • 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 a first RAN node 410, a second RAN node 420, a relay UE 425, and a UE 430, as show in FIG. 4. It would be appreciated that the process 600 may be applied to other communication scenarios, which will not be described in detail.
  • An initial scenario for process 600 may be that, there has been an indirect path between the second RAN node 420 and the UE 430 via the relay UE 425, while the direct path between the first RAN node 410 and the UE 430 has not been established.
  • the UE 430 may be in (i.e., stays at) an RRC connected state, and the UE 430 may access the second RAN node 420 (such as serving gNB) via an indirect path. In some example embodiments, the UE 430 may transmit measurement results to the second RAN node 420, e.g., based on a measurement configuration.
  • the second RAN node 420 transmits, at 610, a request for adding a direct path to the first RAN node 410.
  • the request may be included in an existing Xn message, such as a handover request message, e.g., if DC framework is used (or reused) .
  • the request may be included in a new Xn message, e.g., a path switching request message or a direct path addition message.
  • the request may include an ID of the relay UE associated with the indirect path between the second RAN node 420 and the UE 430, in other words, a UE ID of the relay UE 425 is included.
  • the request may include a cell ID of a cell which serves the relay UE 425, in other words, a cell ID may be included.
  • the request may include a configuration of the indirect path.
  • the current indirect path configuration is included in the request.
  • the request may include a cell ID of a candidate cell, for example, a candidate cell ID may be associated with the first RAN node 410 or the direct path to be added.
  • the request may include a cause value indicating a purpose of the request for direct path addition or multi-path establishment.
  • the request may include UE context information of the UE 430.
  • the UE context information may include one or more of: information of one or more PDU sessions, information of one or more RBs, or a QoS requirement for each of one or more RBs.
  • all PDU session information, all RB information, and QoS for each RB may be included in the request.
  • the request may include at least one suggested RB to be served by the first RAN node 410.
  • the second RAN node 420 may provide at least one suggested RB to be served by the first RAN node 410.
  • the first RAN node 410 transmits, at 620, a response to the request for adding direct path to the second RAN node 420.
  • the response may indicate an acceptance of the request.
  • the response may be included in an existing Xn message, such as a handover request acknowledge message, e.g., if DC framework is used (or reused) .
  • the response may be included in a new Xn message, e.g., a path switching request acknowledge message or a direct path addition acknowledge message.
  • the response may include a first configuration of the direct path.
  • the first RAN node 410 may decide to configure only the direct path, e.g., the first RAN node 410 can handle all ongoing traffic, and the first RAN node 410 may transmit the response including the first configuration of the direct path.
  • the response may include a first configuration of the direct path and a second configuration of the indirect path.
  • the first RAN node 410 may decide to configure multi-path, e.g., both the direct path and the indirect path are configured, and the first RAN node 410 may transmit the response including both the first configuration of the direct path and the second configuration of the indirect path.
  • the request may include a current indirect path configuration
  • the response may include a delta configuration on top of the current indirect path configuration, in other words, the second configuration of the indirect path may be determined based on the current indirect path configuration and the delta configuration.
  • the second RAN node 420 transmits, at 630, an RRC reconfiguration message to the UE 430.
  • the RRC reconfiguration message is used for the direct path addition.
  • the RRC reconfiguration message may include the first configuration of the direct path.
  • the RRC reconfiguration message may further include the second configuration of the indirect path.
  • the UE 430 performs, at 640, a random access procedure to the first RAN node 410.
  • the UE 430 may perform a random access procedure to a target cell associated with the first RAN node 410 based on the RRC reconfiguration message from the second RAN node 420.
  • the UE 430 may start a timer (T304) for the random access procedure.
  • the direct path between the first RAN node 410 and the UE 430 may be added, and thus an inter-gNB multi-path may be supported.
  • PCell should be located in the direct path, and then the case of direct path addition may be handled as path switching with indirect path unchanged. Accordingly, after the UE 430 has a connection with the second RAN node 420 via an indirect path, an Xn enhancement for one direct path addition is proposed.
  • FIG. 7A illustrates a signalling chart illustrating communication process 700 in accordance with some example embodiments of the present disclosure.
  • the process 700 may involve a first RAN node 410, a second RAN node 420, a relay UE 425, and a UE 430, as show in FIG. 4. It would be appreciated that the process 700 may be applied to other communication scenarios, which will not be described in detail.
  • the process 700 may be applied to the communication network 400 in FIG. 4, with reference to FIG. 4, there is a direct path between the first RAN node 410 and the UE 430, and there is an indirect path between the second RAN node 420 and the UE 430 via the relay UE 425.
  • the UE 430 may be in (i.e., stays at) an RRC connected state, and the UE 430 may access the first RAN node 410 (such as serving gNB) via a direct path and access the second RAN node 420 via an indirect path. In some example embodiments, the UE 430 may transmit measurement results to the first RAN node 410 and the second RAN node 420 respectively.
  • the first RAN node 410 such as serving gNB
  • the UE 430 may transmit measurement results to the first RAN node 410 and the second RAN node 420 respectively.
  • the first RAN node 410 transmits, at 710, a request for releasing the indirect path to the second RAN node 420.
  • the first RAN node 410 may decide to release the indirect path between the second RAN node 420 and the UE 430 via the relay UE 425.
  • the request for releasing the indirect path may be included in an existing Xn message, such as S-NODE release request message, e.g., if DC framework is used (or reused) .
  • the request for releasing the indirect path may be included in a new Xn message, e.g., an indirect path release request message.
  • the request for releasing the indirect path may include a cause value for releasing the indirect path.
  • the cause value may indicate an RLF of the sidelink between the UE 430 and the relay UE 425.
  • the cause value may indicate an RLF of a Uu link between the relay UE 425 and the second RAN node 420.
  • the cause value may indicate a reception of a notification message at the UE 430 from the relay UE 425.
  • the cause value may indicate a reception of a release message at the UE 430 from the relay UE 425.
  • the cause value may indicate a reduced bit rate of the UE 430.
  • the second RAN node 420 transmits, at 720, a response to the first RAN node 410.
  • the second RAN node 420 may reject the request.
  • the response may include a rejection to the request.
  • the response may be included in an existing Xn message, such as S-NODE release request reject message, e.g., if DC framework is used (or reused) .
  • the response may be included in a new Xn message, e.g., an indirect path release reject message.
  • the second RAN node 420 may accept the request.
  • the response may include an acceptance to the request.
  • the response may be included in an existing Xn message, such as S-NODE release request acknowledge message, e.g., if DC framework is used (or reused) .
  • the response may be included in a new Xn message, e.g., an indirect path release request acknowledge message.
  • the first RAN node 410 may transmit, at 732, a reconfiguration message to the UE 430, or the second RAN node 420 may transmit, at 734, a reconfiguration message to the UE 430.
  • the reconfiguration message may be used for releasing the indirect path.
  • a configuration of the indirect path may be released.
  • at least one data radio bearer (DRB) in the indirect path may be reconfigured to the direct path.
  • DRB data radio bearer
  • the UE 430 performs a transmission with the first RAN node 410 via the direct path, at 740.
  • the UE 430 may receive/transmit data from/to the first RAN node 410 via the direct path.
  • FIG. 7B illustrates a signalling chart illustrating communication process 750 in accordance with some example embodiments of the present disclosure.
  • the process 750 may involve a first RAN node 410, a second RAN node 420, a relay UE 425, and a UE 430, as show in FIG. 4. It would be appreciated that the process 750 may be applied to other communication scenarios, which will not be described in detail.
  • the process 750 may be applied to the communication network 400 in FIG. 4, with reference to FIG. 4, there is a direct path between the first RAN node 410 and the UE 430, and there is an indirect path between the second RAN node 420 and the UE 430 via the relay UE 425.
  • the UE 430 may be in (i.e., stays at) an RRC connected state, and the UE 430 may access the first RAN node 410 (such as serving gNB) via a direct path and access the second RAN node 420 via an indirect path. In some example embodiments, the UE 430 may transmit measurement results to the first RAN node 410 and the second RAN node 420 respectively.
  • the first RAN node 410 such as serving gNB
  • the UE 430 may transmit measurement results to the first RAN node 410 and the second RAN node 420 respectively.
  • the second RAN node 420 transmits, at 760, a request for releasing the indirect path to the first RAN node 410.
  • the second RAN node 420 may decide to release the indirect path between the second RAN node 420 and the UE 430 via the relay UE 425.
  • the request from the second RAN node 420 may be a required message.
  • the required message for releasing the indirect path may be included in an existing Xn message, such as S-NODE release required message, e.g., if DC framework is used (or reused) .
  • the required message for releasing the indirect path may be included in a new Xn message, e.g., an indirect path release required message.
  • the required message for releasing the indirect path may include a cause value for releasing the indirect path.
  • the cause value may indicate an overload of the relay UE 425.
  • the cause value may indicate an RLF of the sidelink between the UE 430 and the relay UE 425.
  • the cause value may indicate an RLF of a Uu link between the relay UE 425 and the second RAN node 420.
  • the cause value may indicate a handover of the relay UE 425.
  • the first RAN node 410 transmits, at 770, a response to the second RAN node 420.
  • the first RAN node 410 may reject the required message.
  • the response may include a rejection to the required message.
  • the response may be included in an existing Xn message, such as S-NODE release required reject message, e.g., if DC framework is used (or reused) .
  • the response may be included in a new Xn message, e.g., an indirect path release required reject message.
  • the first RAN node 410 may accept the required message.
  • the response may include a confirmation to the required message.
  • the response may be implemented as a confirm message.
  • the confirm message may be included in an existing Xn message, such as S-NODE release confirm message, e.g., if DC framework is used (or reused) .
  • the response may be included in a new Xn message, e.g., an indirect path release confirm message.
  • the first RAN node 410 may transmit, at 782, a reconfiguration message to the UE 430, or the second RAN node 420 may transmit, at 784, a reconfiguration message to the UE 430.
  • the reconfiguration message may be used for releasing the indirect path.
  • a configuration of the indirect path may be released.
  • at least one data radio bearer (DRB) in the indirect path may be reconfigured to the direct path.
  • DRB data radio bearer
  • the UE 430 performs a transmission with the first RAN node 410 via the direct path, at 790.
  • the UE 430 may receive/transmit data from/to the first RAN node 410 via the direct path.
  • the UE 430 may be configured with inter-gNB multi-path, and the indirect path between the second RAN node 420 and the UE 430 may be released, where the releasing may be initiated by the first RAN node 410 or the second RAN node 420. That is, after Inter-gNB based multi-path has been established already, the indirect path may be released while the releasing is triggered by the first RAN node or the second RAN node.
  • FIG. 8 illustrates a signalling chart illustrating communication process 800 in accordance with some example embodiments of the present disclosure.
  • the process 800 may involve a first RAN node 410, a second RAN node 420, a relay UE 425, and a UE 430, as show in FIG. 4. It would be appreciated that the process 800 may be applied to other communication scenarios, which will not be described in detail.
  • the process 800 may be applied to the communication network 400 in FIG. 4, with reference to FIG. 4, there is a direct path between the first RAN node 410 and the UE 430, and there is an indirect path between the second RAN node 420 and the UE 430 via the relay UE 425.
  • the UE 430 may be in (i.e., stays at) an RRC connected state, and the UE 430 may access the first RAN node 410 (such as serving gNB) via a direct path and access the second RAN node 420 via an indirect path. In some example embodiments, the UE 430 may transmit measurement results to the first RAN node 410 and the second RAN node 420 respectively.
  • the first RAN node 410 such as serving gNB
  • the UE 430 may transmit measurement results to the first RAN node 410 and the second RAN node 420 respectively.
  • the first RAN node 410 transmits, at 810, a request for PCell change to the second RAN node 420.
  • the first RAN node 410 may decide to release the direct path between the first RAN node 410 and the UE 430.
  • the request for PCell change may be included in an existing Xn message, such as a handover request message, e.g., if DC framework is used (or reused) .
  • the request for PCell change may be included in a new Xn message.
  • the request for PCell change may include an ID of a candidate relay UE.
  • the candidate relay UE may be the same as the relay UE associated with the indirect path, i.e., the relay UE 425.
  • the request for PCell change may include a cause value indicating a purpose of the request.
  • the cause value may indicate that the purpose is PCell changing.
  • the request for PCell change may include information of BR in the direct path.
  • BR information in the direct path may be included in the request, which may be used for PCell change.
  • the second RAN node 420 transmits, at 820, a response to the first RAN node 410.
  • the second RAN node 420 may reject the request.
  • the response may include a rejection to the request.
  • the response may be included in an existing Xn message, such as a handover request reject message, e.g., if DC framework is used (or reused) .
  • the response may be included in a new Xn message.
  • the second RAN node 420 may accept the request.
  • the response may include an acceptance to the request.
  • the response may be included in an existing Xn message, such as a handover request acknowledge message, e.g., if DC framework is used (or reused) .
  • the response may be included in a new Xn message.
  • the response may include a configuration of the indirect path associated with the relay UE.
  • the configuration is associated with the candidate relay UE in the request, e.g., the candidate relay UE is the relay UE 425.
  • the second RAN node 420 may transmit, at 830, a reconfiguration message to the UE 430, where the reconfiguration message is used for PCell change.
  • the reconfiguration message may include an ID of the candidate relay UE.
  • the reconfiguration message may indicate to the UE 340 to switch to a PCell associated with the candidate relay UE.
  • the second RAN node 420 may provide a suitable configuration to cover all RBs.
  • the UE 430 may keep the PC5 link with the relay UE 425. Alternatively, the UE 430 may start a timer (such as T420) upon receiving a path switching command.
  • a timer such as T420
  • the UE 430 performs a transmission with the second RAN node 420 via the indirect path, at 840.
  • the UE 430 may receive/transmit data from/to the second RAN node 420 via the indirect path.
  • the UE 430 may be configured with inter-gNB multi-path, and the direct path between the first RAN node 410 and the UE 430 may be released, specifically, the UE 430 may fall back to a scenario with an indirect path, and accordingly the PCell may change to the indirect path. That is, after Inter-gNB based multi-path has been established already, the direct path may be released while the releasing is triggered by the first RAN node.
  • FIG. 9 illustrates an example of a device 900 that is suitable for implementing embodiments of the present disclosure.
  • the device 900 may be an example of a RAN node as described herein.
  • the device 900 may support wireless communication with the first RAN node 410, the second RAN node 420, or any combination thereof.
  • the device 900 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 902, a memory 904, a transceiver 906, and, optionally, an I/O controller 908. 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 902, the memory 904, the transceiver 906, 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 902, the memory 904, the transceiver 906, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 902, the memory 904, the transceiver 906, 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 902 and the memory 904 coupled with the processor 902 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904) .
  • the processor 902 may support wireless communication at the device 900 in accordance with examples as disclosed herein.
  • the processor 902 may be configured to operable to support a means for transmitting, to a first RAN node, a request for adding a direct path between the first RAN node and a UE, wherein there has been an indirect path between the second RAN node and the UE via a relay UE; and means for receiving, from the first RAN node, a response at least comprising a first configuration of the direct path.
  • the processor 902 may be configured to operable to support a means for receiving, from a second RAN node, a request for adding a direct path between the first RAN node and a UE, wherein there has been an indirect path between the second RAN node and the UE via a relay UE; and means for transmitting, to the second RAN node, a response at least comprising a first configuration of the direct path.
  • the processor 902 may be configured to operable to support a means for transmitting, to a second RAN node, a request for PCell change or for releasing an indirect path, wherein there are a direct path between the first RAN node and a UE and the indirect path between the second RAN node and the UE via a relay UE; and means for receiving, from the second RAN node, a response for accepting the request or rejecting the request.
  • the processor 902 may be configured to operable to support a means for receiving, from a first RAN node, a request for PCell change or for releasing an indirect path, wherein there are a direct path between the first RAN node and a UE and the indirect path between the second RAN node and the UE via a relay UE; and means for transmitting, to the first RAN node, a response for accepting the request or rejecting the request.
  • the processor 902 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 902 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 902.
  • the processor 902 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 904) to cause the device 900 to perform various functions of the present disclosure.
  • the memory 904 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 902 cause the device 900 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 902 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 904 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 908 may manage input and output signals for the device 900.
  • the I/O controller 908 may also manage peripherals not integrated into the device M02.
  • the I/O controller 908 may represent a physical connection or port to an external peripheral.
  • the I/O controller 908 may utilize an operating system such as or another known operating system.
  • the I/O controller 908 may be implemented as part of a processor, such as the processor 902.
  • a user may interact with the device 900 via the I/O controller 908 or via hardware components controlled by the I/O controller 908.
  • the device 900 may include a single antenna 910. However, in some other implementations, the device 900 may have more than one antenna 910 (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 906 may communicate bi-directionally, via the one or more antennas 910, wired, or wireless links as described herein.
  • the transceiver 906 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 906 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 910 for transmission, and to demodulate packets received from the one or more antennas 910.
  • the transceiver 906 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 910 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 910 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. 10 illustrates an example of a processor 1000 that is suitable for implementing some embodiments of the present disclosure.
  • the processor 1000 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 1000 may include a controller 1002 configured to perform various operations in accordance with examples as described herein.
  • the processor 1000 may optionally include at least one memory 1004, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 1000 may optionally include one or more arithmetic-logic units (ALUs) 1006.
  • 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 1000 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 1000) 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 1002 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 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein.
  • the controller 1002 may operate as a control unit of the processor 1000, generating control signals that manage the operation of various components of the processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 1002 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1004 and determine subsequent instruction (s) to be executed to cause the processor 1000 to support various operations in accordance with examples as described herein.
  • the controller 1002 may be configured to track memory address of instructions associated with the memory 1004.
  • the controller 1002 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 1002 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein.
  • the controller 1002 may be configured to manage flow of data within the processor 1000.
  • the controller 1002 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1000.
  • ALUs arithmetic logic units
  • the memory 1004 may include one or more caches (e.g., memory local to or included in the processor 1000 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1004 may reside within or on a processor chipset (e.g., local to the processor 1000) . In some other implementations, the memory 1004 may reside external to the processor chipset (e.g., remote to the processor 1000) .
  • caches e.g., memory local to or included in the processor 1000 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 1004 may reside within or on a processor chipset (e.g., local to the processor 1000) . In some other implementations, the memory 1004 may reside external to the processor chipset (e.g., remote to the processor 1000) .
  • the memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1000, cause the processor 1000 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 1002 and/or the processor 1000 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the processor 1000 to perform various functions.
  • the processor 1000 and/or the controller 1002 may be coupled with or to the memory 1004, the processor 1000, the controller 1002, and the memory 1004 may be configured to perform various functions described herein.
  • the processor 1000 may include multiple processors and the memory 1004 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 1006 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 1006 may reside within or on a processor chipset (e.g., the processor 1000) .
  • the one or more ALUs 1006 may reside external to the processor chipset (e.g., the processor 1000) .
  • One or more ALUs 1006 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 1006 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 1006 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 1006 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1006 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 1006 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 1000 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 1000 may be configured to or operable to support a means for operations described in some embodiments of the present disclosure.
  • FIG. 11 illustrates a flowchart of a method 1100 performed by a second RAN node 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 second RAN node 420 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 first RAN node, a request for adding a direct path between the first RAN node and a UE, wherein there has been an indirect path between the second RAN node and the UE via a 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 second RAN node 420 as described with reference to FIG. 4.
  • the method may include receiving, from the first RAN node, a response at least comprising a first configuration of the direct path.
  • 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 second RAN node 420 as described with reference to FIG. 4.
  • FIG. 12 illustrates a flowchart of a method 1200 performed by a first RAN node 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 first RAN node 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 second RAN node, a request for adding a direct path between the first RAN node and a UE, where there has been an indirect path between the second RAN node and the UE via a 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 first RAN node 410 as described with reference to FIG. 4.
  • the method may include transmitting, to the second RAN node, a response at least comprising a first configuration of the direct path.
  • 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 first RAN node 410 as described with reference to FIG. 4.
  • FIG. 13 illustrates a flowchart of a method 1300 performed by a first RAN node in accordance with aspects of the present disclosure.
  • the operations of the method 1300 may be implemented by a device or its components as described herein.
  • the operations of the method 1300 may be performed by the first RAN node 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 transmitting, to a second RAN node, a request for PCell change or for releasing an indirect path, wherein there are a direct path between the first RAN node and a UE and the indirect path between the second RAN node and the UE via a relay UE.
  • the operations of 1310 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1310 may be performed by the first RAN node 410 as described with reference to FIG. 4.
  • the method may include receiving, from the second RAN node, a response for accepting the request or rejecting the request.
  • the operations of 1320 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1320 may be performed by the first RAN node 410 as described with reference to FIG. 4.
  • FIG. 14 illustrates a flowchart of a method 1400 performed by a second RAN node in accordance with aspects of the present disclosure.
  • the operations of the method 1400 may be implemented by a device or its components as described herein.
  • the operations of the method 1400 may be performed by the second RAN node 420 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 first RAN node, a request for PCell change or for releasing an indirect path, wherein there are a direct path between the first RAN node and a UE and the indirect path between the second RAN node and the UE via a relay UE.
  • the operations of 1410 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1410 may be performed by the second RAN node 420 as described with reference to FIG. 4.
  • the method may include transmitting, to the first RAN node, a response for accepting the request or rejecting the request.
  • the operations of 1420 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1420 may be performed by the second RAN node 420 as described with reference to FIG. 4.
  • 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 à titre d'exemples de la présente invention concernent des nœuds RAN, des procédés, un appareil, des processeurs, et un support de stockage informatique pour l'ajout ou la libération de trajet dans un scénario à trajet multiple inter-gNB. Dans la solution, un second nœud RAN qui a un trajet indirect avec l'UE peut transmettre au premier nœud RAN une requête pour ajouter un trajet direct entre le premier nœud RAN et l'UE. De plus, le premier nœud RAN peut transmettre une réponse comprenant une première configuration du trajet direct au second nœud RAN. En tant que telle, une procédure d'ajout d'un trajet direct peut être définie et la communication entre l'UE et le côté réseau peut être garantie. Par conséquent, un trajet multiple inter-gNB est pris en charge. En outre, après qu'un trajet multiple inter-gNB a été déjà établi, l'un du trajet indirect et du trajet direct peut être libéré et déclenché par le premier nœud RAN ou le second nœud RAN.
PCT/CN2023/113293 2023-08-16 2023-08-16 Ajout ou libération de trajet dans un trajet multiple inter-gnb Pending WO2024093439A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/113293 WO2024093439A1 (fr) 2023-08-16 2023-08-16 Ajout ou libération de trajet dans un trajet multiple inter-gnb

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/113293 WO2024093439A1 (fr) 2023-08-16 2023-08-16 Ajout ou libération de trajet dans un trajet multiple inter-gnb

Publications (1)

Publication Number Publication Date
WO2024093439A1 true WO2024093439A1 (fr) 2024-05-10

Family

ID=90929636

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/113293 Pending WO2024093439A1 (fr) 2023-08-16 2023-08-16 Ajout ou libération de trajet dans un trajet multiple inter-gnb

Country Status (1)

Country Link
WO (1) WO2024093439A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109246793A (zh) * 2017-05-17 2019-01-18 华为技术有限公司 多链接的数据传输方法及装置
CN110741726A (zh) * 2017-06-16 2020-01-31 瑞典爱立信有限公司 主基站发起的辅基站释放与辅基站发起的辅基站改变过程之间的竞争条件避免
CN115024020A (zh) * 2020-01-22 2022-09-06 联发科技（新加坡）私人有限公司 侧链路中继信道建立方法和设备
CN116171640A (zh) * 2020-07-29 2023-05-26 欧芬诺有限责任公司 配置释放
CN116472747A (zh) * 2020-11-24 2023-07-21 三菱电机株式会社 通信系统及通信终端

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109246793A (zh) * 2017-05-17 2019-01-18 华为技术有限公司 多链接的数据传输方法及装置
CN110741726A (zh) * 2017-06-16 2020-01-31 瑞典爱立信有限公司 主基站发起的辅基站释放与辅基站发起的辅基站改变过程之间的竞争条件避免
CN115024020A (zh) * 2020-01-22 2022-09-06 联发科技（新加坡）私人有限公司 侧链路中继信道建立方法和设备
CN116171640A (zh) * 2020-07-29 2023-05-26 欧芬诺有限责任公司 配置释放
CN116472747A (zh) * 2020-11-24 2023-07-21 三菱电机株式会社 通信系统及通信终端

Similar Documents

Publication Publication Date Title
WO2024183313A1 (fr) Ltm scg inter-sn
WO2024093428A1 (fr) Mécanisme pour cho avec des scg candidats
WO2024087755A1 (fr) Transmissions de psfch multiples sur un spectre sans licence
WO2024146185A1 (fr) Ltm basé sur une condition
WO2024093447A1 (fr) Procédure de préparation pour ltm
WO2024093397A1 (fr) Duplication de pdcp pour slrb
WO2024093439A1 (fr) Ajout ou libération de trajet dans un trajet multiple inter-gnb
WO2024109166A1 (fr) Changement de trajet indirect dans un trajet multiple
WO2024094228A1 (fr) Procédure de défaillance de trajet indirect en multi-trajet
WO2024199052A1 (fr) Procédure de défaillance de trajet indirect due à ltm de l'ue relais dans un trajet multiple
WO2025035808A1 (fr) Gestion de connexion pc5 de bout en bout dans un relais u2u
WO2024259991A1 (fr) Défaillance dans une communication par relais
WO2025107677A1 (fr) Dispositifs et procédés de communication
WO2024098839A1 (fr) Ajout de trajet indirect pour communication u2n
WO2024207740A1 (fr) Mobilité déclenchée de couche 1 ou de couche 2
WO2025241602A1 (fr) Mobilité intra-rat et inter-rat
WO2025148315A1 (fr) Prédiction de défaillance de liaison radio en double connexion
WO2025246425A1 (fr) Gestion de ressource
WO2025097801A1 (fr) Dispositifs et procédés de communication
WO2025156295A1 (fr) Continuité de service de multidiffusion ou de diffusion
WO2024093344A1 (fr) Mécanisme de détermination d'id court
WO2024250686A1 (fr) Prédiction d'échec de transfert
WO2024093345A1 (fr) Fourniture de prédiction de trajectoire d'ue
WO2025251726A1 (fr) Mobilité déclenchée par couche 1 ou couche 2 conditionnelle
WO2024093655A1 (fr) Division de données de liaison montante déclenchée par état de retard

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

Country of ref document: EP

Kind code of ref document: A1