[go: up one dir, main page]

WO2024234703A1 - Transfert intercellulaire conditionnel pour économie d'énergie de réseau - Google Patents

Transfert intercellulaire conditionnel pour économie d'énergie de réseau Download PDF

Info

Publication number
WO2024234703A1
WO2024234703A1 PCT/CN2024/072092 CN2024072092W WO2024234703A1 WO 2024234703 A1 WO2024234703 A1 WO 2024234703A1 CN 2024072092 W CN2024072092 W CN 2024072092W WO 2024234703 A1 WO2024234703 A1 WO 2024234703A1
Authority
WO
WIPO (PCT)
Prior art keywords
cho
nes
candidate cell
specific
triggering event
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/072092
Other languages
English (en)
Inventor
Min Xu
Ran YUE
Lianhai WU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2024/072092 priority Critical patent/WO2024234703A1/fr
Publication of WO2024234703A1 publication Critical patent/WO2024234703A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H04B7/18539—Arrangements for managing radio, resources, i.e. for establishing or releasing a connection
    • H04B7/18541—Arrangements for managing radio, resources, i.e. for establishing or releasing a connection for handover of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to wireless communications, and more specifically to conditional handover (CHO) for network energy saving (NES) .
  • CHO conditional handover
  • NES network energy saving
  • 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
  • NTN non-terrestrial network
  • An NTN refers to a network or segments of a network using radio frequency (RF) resources on board a satellite.
  • the satellite in NTN may be a geostationary earth orbiting (GEO) satellite with a fixed location to the earth, or a low earth orbiting (LEO) satellite orbiting around the earth.
  • GEO geostationary earth orbiting
  • LEO low earth orbiting
  • the present disclosure relates to methods, apparatuses, and systems that support CHO for NES. With the apparatuses and methods, it is possible to improve the NES-specific CHO procedure efficiently.
  • a UE comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a base station (BS) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO; and perform a CHO procedure from a serving cell to the at least one candidate cell based on the NES-specific CHO configuration.
  • BS base station
  • NES network energy saving
  • CHO conditional handover
  • a method performed by the UE comprises: receiving, from a base station (BS) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO; and performing a CHO procedure from a serving cell to the at least one candidate cell based on the NES-specific CHO configuration.
  • BS base station
  • NES network energy saving
  • CHO conditional handover
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the at least one processor to: receive, from a base station (BS) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO; and perform a CHO procedure from a serving cell to the at least one candidate cell based on the NES-specific CHO configuration.
  • BS base station
  • NES network energy saving
  • CHO conditional handover
  • the location-based triggering event comprises conditional event (condEvent) D1 or condEvent D2, and the time-based triggering event comprises condEvent T1.
  • Some implementations of the method and the UE described herein may further include receiving an indication indicating that the location-based triggering event is enabled for a candidate cell of the at least one candidate cell; determining the location-based triggering event is fulfilled for handover from the serving cell to the candidate cell in response to an entry condition applicable for the location-based triggering event is fulfilled for the candidate cell during a time period; or determining the location-based triggering event is not fulfilled for handover from the serving cell to the candidate cell, in response to that a leaving condition applicable for the location-based triggering event is not fulfilled for the candidate cell during the time period.
  • Some implementations of the method and the UE described herein may further include receiving an indication indicating that the time-based triggering event is enabled for a candidate cell of the at least one candidate cell; determining the time-based triggering event is fulfilled for handover from the serving cell to the candidate cell, in response to an entry condition applicable for the time-based triggering event is fulfilled for the candidate cell; or determining the time-based triggering event is not fulfilled for the candidate cell, in response to a leaving condition applicable for the time-based triggering event is not fulfilled for the candidate cell.
  • Some implementations of the method and the UE described herein may further include receiving an indication indicating that the location-based triggering event or the time-based triggering event is disabled for a candidate cell of the at least one candidate cell; and determining the location-based triggering event or the time-based triggering event is not fulfilled for the candidate cell.
  • a candidate cell of the at least one candidate cell is configured with one or more triggering events associated with NES-specific CHO and one or more triggering events not associated with NES-specific CHO
  • performing the CHO procedure comprises one of the following: in response to the candidate cell is configured with one triggering event associated with NES-specific CHO, and a combination of two triggering events not associated with NES-specific CHO, determining the candidate cell as a triggered cell for CHO, when the triggering event associated with NES-specific CHO is fulfilled or the combination of two triggering events not associated with NES-specific CHO is fulfilled; in response to the candidate cell is configured with a combination of two triggering events associated with NES-specific CHO, and one triggering event not associated with NES-specific CHO, determining the candidate cell as a triggered cell for CHO, when the combination of two triggering events associated with NES-specific CHO is fulfilled or the triggering event not associated with NES-specific CHO is fulfilled; or
  • performing the CHO procedure comprises: receiving an indication indicating that one or more triggering events associated with NES-specific CHO are enabled for the at least one candidate cell; and perfoming one of the following: avoiding informing lower layers that uplink synchronization is lost upon an expiry of a timer for uplink synchronization; suspending the timer; or starting another timer for the CHO procedure.
  • performing the CHO procedure comprises: receiving an indication indicating that one or more triggering events associated with NES-specific CHO are disabled for the at least one candidate cell; and acquiring a system information block (SIB) for uplink synchronization before an expiry of a timer for uplink synchronization.
  • SIB system information block
  • performing the CHO procedure comprises: determining, from the at least one candidate cell, a first candidate cell as a triggered cell for CHO; and keeping an NES-specific CHO configuration for one or more other candidate cells, the one or more other candidate cells being determined by excluding the first candidate cell from the at least one candidate cell.
  • keeping the NES-specific CHO configuration for the one or more other candidate cells comprises: keeping the NES-specific CHO configuration for the one or more other candidate cells after CHO to the first candidate cell is not completed.
  • performing the CHO procedure comprises: determining, from the one or more other candidate cells, a second candidate cell as another triggered cell for CHO; and performing CHO to the second candidate cell based on the kept NES-specific CHO configuration of the second candidate cell.
  • determining the second candidate cell as the another triggered cell for CHO comprises: evaluating one or more triggering events associated with NES-specific CHO for the second candidate cell if one of the following: the second candidate cell has a capability of supporting NES; or the serving cell indicates that the one or more triggering events associated with NES-specific CHO are enabled for the second candidate cell.
  • keeping the NES-specific CHO configuration for the one or more other candidate cells comprises: keeping the NES-specific CHO configuration for the one or more other candidate cells after CHO to the first candidate cell is completed. In some implementations of the method and the UE described herein, keeping the NES-specific CHO configuration for the one or more other candidate cells comprises: keeping the NES-specific CHO configuration for the one or more other candidate cells based on one of the following: receiving an indication to keep the NES-specific CHO configuration for the one or more other candidate cells, or determining that the first candidate cell supports NES.
  • performing the CHO procedure comprises: based on the first candidate cell indicating that one or more triggering events associated with NES-specific CHO are enabled, performing CHO to a second candidate cell of the one or more other candidate cells based on the kept NES-specific CHO configuration of the second candidate cell.
  • performing the CHO procedure comprises: determining that one or more triggering events associated with NES-specific CHO are enabled or disabled for one or more of the one or more other candidate cells by default or based on receiving an indication of enabling or disabling the one or more triggering events.
  • the one or more triggering events comprises one or more of: one of the location-based triggering event, or the time-based triggering event; or a signal quality-based triggering event.
  • the NES-specific CHO configuration for the at least one candidate cell comprises a reference CHO configuration and one or more delta CHO configurations for one or more of the at least one candidate cell, a respective delta CHO configuration of a respective candidate cell of the one or more of the at least one candidate cell comprising a configuration difference between the reference CHO configuration and a respective CHO configuration of the respective candidate cell.
  • the at least one candidate cell comprises a non-terrestrial network (NTN) cell.
  • NTN non-terrestrial network
  • a base station comprising at least one memory; and at least one processor coupled with the at least one memory and configured to cause the BS to: transmit, to a user equipment (UE) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO.
  • UE user equipment
  • NES network energy saving
  • CHO conditional handover
  • a method performed by the BS comprises: transmitting, to a user equipment (UE) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO.
  • UE user equipment
  • NES network energy saving
  • CHO conditional handover
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the at least one processor to: transmit, to a user equipment (UE) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO.
  • UE user equipment
  • NES network energy saving
  • CHO conditional handover
  • the location-based triggering event comprises conditional event (condEvent) D1, or condEvent D2, and the time-based triggering event comprises condEvent T1.
  • the at least one candidate cell comprises a non-terrestrial network (NTN) cell.
  • NTN non-terrestrial network
  • FIG. 1 illustrates an example of a wireless communications system that supports CHO for NES in accordance with aspects of the present disclosure
  • FIG. 2 illustrates an example process flow in accordance with some example embodiments of the present disclosure
  • FIG. 3 illustrates an example of a device that supports CHO for NES in accordance with aspects of the present disclosure
  • FIG. 4 illustrates an example of a processor that supports CHO for NES in accordance with aspects of the present disclosure
  • FIGS. 5 through 6 illustrate flowcharts of methods that support CHO for NES 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.
  • 3GPP Rel-17 is the first release supporting NTN essential functions.
  • 3GPP release 18 (Rel-18) and release 19 (Rel-19) study further enhancements to improve NTN performance.
  • NTN-specific CHO events were introduced in Rel-17 in addition to signal-based events (for example, condEvent A3, condEvent A4, or condEvent A5) for quasi-earth-fixed cells: distance-based (also referred to as location-based) conditional event (condEvent) D1 and time-based condEvent T1.
  • distance-based also referred to as location-based
  • conditional event condEvent
  • T1 time-based condEvent T1
  • the network may configure a second triggering event condEvent A3, condEvent A4, or condEvent A5 for the same candidate cell.
  • the network may not configure both condEvent D1 and condEvent T1 for the same candidate cell.
  • condEvent D2 has been introduced for earth-moving cells in NTN.
  • the network may configure condEvent D1/D2 or condEvent T1 independently for a candidate cell without condEvent A3, condEvent A4, or condEvent A5.
  • the network may configure at most one from condEvent D1, condEvent D2, or condEvent T1 for the same candidate cell.
  • a satellite with limited transmission power and limited processing bandwidth may only serve part of the potential satellite coverage area at the same time.
  • downlink coverage enhancement techniques to maximize the number of satellite beams that can be activated simultaneously and to ensure that all UEs can be served across the satellite coverage through dynamic and efficient power control.
  • TN terrestrial network
  • the NES-specific CHO event is introduced in Rel-18 to allow the network to configure UE to perform CHO in case the serving cell is about to activate cell DTX/DRX or turn off.
  • IE information element
  • nesEvent With a configuration of the information element (IE) nesEvent, it means that the associated event is an NES-specific CHO event, and the event is only considered to be satisfied if indication from lower layers (i.e., a DCI) is received indicating the applicability of NES-specific CHO event and the related entry condition (s) is fulfilled.
  • a restriction is specified that nesEvent can only be configured for condEvent A3, condEvent A4, or condEvent A5 as shown in the following:
  • the NTN scenarios are not in the scope of NES in Rel-18.
  • the logic of fulfillment for an NES-specific event only considers at most two CHO events if configured (i.e., one normal A3/A4/A5 event and one NES-specific A3/A4/A5 event) , and a candidate cell may be determined as a triggered cell if either any of the CHO events is fulfilled. Fulfillment determination for the CHO events may be performed as follows:
  • Embodiments of the present disclosure provide a solution for NES-specific CHO, especially, applying NES-specific CHO in NTN.
  • a UE receives, from a BS, an NES-specific CHO configuration for at least one candidate cell.
  • the NES-specific CHO configuration comprises a location-based triggering event or a time-based triggering event associated with NES-specific CHO.
  • the UE performs a CHO procedure from a serving cell to the at least one candidate cell based on the NES-specific CHO configuration
  • This solution allows to support NES-specific CHO considering NTN-specific events, that is, the location-based triggering event or a time-based triggering event. In this way, it is possible to improve the NES-specific CHO procedure efficiently, especially, to improve the CHO procedure with network energy savings in NTN.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports CHO for NES in accordance with aspects of the present disclosure.
  • 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 (NE) 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 be implemented as a satellite.
  • a network entity 102 in form of a satellite can directly communicate to UE 104 using NR/LTE Uu interface.
  • the satellite may be a transparent satellite or a regenerative satellite.
  • a base station on earth may communicate with a UE via the satellite.
  • a communication link 110 between the satellite and the UE 104, a communication link 110 between the satellite and a base station on earth, and a communication link 116 between the base station on earth and core network 106 may be used for the NTN transparent mode.
  • the base station may be on board and directly communicate with the UE.
  • a communication link 110 between the satellite and the UE 104, and a communication link 116 between the satellite (with full or part of an eNB/gNB on board) and core network 106 may be used for the NTN regenerative mode.
  • 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, messaging, 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, N2, 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) .
  • FIG. 2 illustrates an example process flow 200 in accordance with some example embodiments of the present disclosure.
  • the process 200 will be described with reference to FIG. 1, and the process 200 may involve a UE 104 and a network entity 102 as shown in FIG. 1.
  • the network entity 102 may be implemented as a base station. It is to be understood that the steps and the order of the steps in FIG. 2 are merely for illustration, and not for limitation. It is to be understood that process 200 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the BS 102 transmits (205) , to the UE 104, an NES-specific CHO configuration for at least one candidate cell (also referred to as applicable cell) .
  • the at least one candidate cell may comprise an NTN cell.
  • the at least one candidate cell may comprise a TN cell.
  • the at least one candidate cell may be a cell under the control of the BS 102 or a further BS.
  • the NES-specific CHO configuration may comprise a CHO configuration including an NES indication “nesEvent” .
  • the NES-specific CHO configuration may comprise a location-based triggering event or a time-based triggering event associated with NES-specific CHO.
  • the location-based triggering event may comprise conditional event (condEvent) D1 or condEvent D2.
  • the time-based triggering event may comprise condEvent T1.
  • the BS 102 may configure the UE 104 with the location-based or time-based CHO event associated with the nesEvent, i.e., the condEvent D1/D2/T1 associated with the nesEvent for at least one candidate cell.
  • the UE 104 may receive the configuration from the BS 102 and consider the condEvent D1/D2/T1 associated with the nesEvent as an NES-specific CHO event for the at least one candidate cell.
  • each individual CHO event of condEvent D1, D2, and T1 may be added to the allowed list of the nesEvent.
  • the corresponding field description of the nesEvent may comprise:
  • nesEvent Indicates the event is a NES-specific CHO event and the event is only considered to be satisfied if indication from lower layers is received indicating the applicability of NES-specific CHO event and the related entry condition (s) is fulfilled.
  • This field can only be configured for condEvent A3, condEvent A4, condEvent A5 or condEvent D1/D2/T1
  • the description of restricting association between the nesEvent and any CHO event may be removed.
  • the corresponding field description of the nesEvent may comprise:
  • nesEvent Indicates the event is a NES-specific CHO event and the event is only considered to be satisfied if indication from lower layers is received indicating the applicability of NES-specific CHO event and the related entry condition (s) is fulfilled. (No restriction for a specific CHO event it can be associated with)
  • the UE 104 after receiving the NES-specific CHO configuration, performs (210) a CHO procedure from a serving cell to the at least one candidate cell based on the NES-specific CHO configuration.
  • the UE 104 may need to evaluate whether the above location-based triggering event or the time-based triggering event associated with NES-specific CHO is fulfilled. For example, the UE 104 may perform the evaluation after receiving an indication (for example, referred to as an NES mode indication) indicating whether the location-based triggering event or the time-based triggering event associated with NES-specific CHO is enabled for the at least one candidate cell.
  • an indication for example, referred to as an NES mode indication
  • the UE 104 may determine the location-based triggering event is fulfilled for handover from the serving cell to the candidate cell if an entry condition applicable for the location-based triggering event is fulfilled for the candidate cell during a time period (for example, during a corresponding trigger time (also referred to as timeToTrigger) defined for this location-based triggering event) .
  • a time period for example, during a corresponding trigger time (also referred to as timeToTrigger) defined for this location-based triggering event
  • the UE 104 may determine the location-based triggering event is not fulfilled for handover from the serving cell to the candidate cell if a leaving condition applicable for the location-based triggering event is not fulfilled for the candidate cell during the time period.
  • the UE 104 may consider the condEvent D1/D2 as fulfilled if the entry conditions applicable for this event is fulfilled for the candidate cell during the corresponding timeToTrigger defined for this event, or the UE 104 may consider the condEvent D1/D2 as not fulfilled if the leaving conditions applicable for this event is fulfilled for the candidate cell during the corresponding timeToTrigger defined for this event.
  • the UEu 104 may determine the time-based triggering event is fulfilled for handover from the serving cell to the candidate cell, if an entry condition applicable for the time-based triggering event is fulfilled for the candidate cell. Alternatively or additionally, the UE 104 may determine the time-based triggering event is not fulfilled for the candidate cell if a leaving condition applicable for the time-based triggering event is not fulfilled for the candidate cell.
  • the UE 104 may consider the condEventT1 as fulfilled if the entry condition applicable for this event is fulfilled for the candidate cell, or the UE 104 may consider the condEventT1 as not fulfilled if the leaving condition applicable for this event is fulfilled for the candidate cell.
  • the UE 104 may determine the location-based triggering event or the time-based triggering event is not fulfilled for the candidate cell.
  • the UE 104 may consider the condEvent D1/D2/T1 as not fulfilled for the candidate cell.
  • the NES-specific CHO configuration may comprise one or more triggering events associated with NES-specific CHO and/or one or more triggering events not associated with NES-specific CHO for a candidate cell.
  • a triggering event not associated with NES-specific CHO may also be referred to as a normal event.
  • the one or more triggering events associated with NES-specific CHO or not associated with NES-specific CHO may comprise one of the location-based triggering event or the time-based triggering event (i.e., the condEvent D1/D2/T1) ; or a signal quality-based triggering event (i.e., the condEvent A3/A4/A5) .
  • a candidate cell may be configured with a combination of two CHO events associated with the nesEvent, and/or a combination of two CHO events not associated with the nesEvent.
  • the UE 104 may consider the candidate cell as a triggered cell when the combined events of one of the above at least one combination are fulfilled, or when the other event without combination is fulfilled.
  • the UE 104 may determine the candidate cell as a triggered cell for CHO, when the triggering event associated with NES-specific CHO is fulfilled or the combination of two triggering events not associated with NES-specific CHO is fulfilled.
  • the candidate cell when the UE 104 is configured with 1 NES-specific event associated with the nesEvent (for example, the condEvent D1/D2/T1, or the condEvent A3/A4/A5 associated with the nesEvent) and a combination of 2 normal events (for example, the normal condEvent D1/D2/T1 + the normal condEvent A3/A4/A5, which are not associated with the nesEvent) for the candidate cell, the candidate cell may be considered as a triggered cell when either of the 1 NES-specific event associated with the nesEvent or the combination of 2 normal events is fulfilled.
  • 1 NES-specific event associated with the nesEvent for example, the condEvent D1/D2/T1, or the condEvent A3/A4/A5 associated with the nesEvent
  • 2 normal events for example, the normal condEvent D1/D2/T1 + the normal condEvent A3/A4/A5, which are not associated with the nesEvent
  • the UE 104 may determine the candidate cell as a triggered cell for CHO, when the combination of two triggering events associated with NES-specific CHO is fulfilled or the triggering event not associated with NES-specific CHO is fulfilled.
  • the candidate cell may be considered as a triggered cell when either of the combination of 2 NES-specific events associated with the nesEvent or the 1 normal event is fulfilled.
  • 2 NES-specific events associated with the nesEvent for example, the condEvent D1/D2/T1 + the condEvent A3/A4/A5 associated with the nesEvent
  • 1 normal event for example, the normal condEvent D1/D2/T1, or normal the condEvent A3/A4/A5, which is not associated with the nesEvent
  • the candidate cell may be considered as a triggered cell when either of the combination of 2 NES-specific events associated with the nesEvent or the 1 normal event is fulfilled.
  • the UE 104 may determine the candidate cell as a triggered cell for CHO, when the combination of two triggering events associated with NES-specific CHO is fulfilled or the combination of two triggering events not associated with NES-specific CHO is fulfilled.
  • the candidate cell may be considered as a triggered cell when either of the combination of 2 NES-specific events associated with the nesEvent or the combination of 2 normal events is fulfilled.
  • the UE 104 may further consider the handling of uplink synchronization.
  • timer 430 T430 may be used to ensure that the UE 104 has a valid SIB19 for uplink synchronization to its serving NTN cell. It starts upon reception of the SIB19 with a value set to ntn-UlSyncValidityDuration from a subframe indicated by epochTime.
  • the UE 104 may attempt to re-acquire SIB19 before the T430 expiry and when the T430 expires, the UE 104 may consider the uplink synchronization to its serving NTN cell is lost.
  • timer 317 T317) may be used to ensure that the UE 104 has a valid SIB31 for uplink synchronization to its serving NTN cell. It starts upon reception of the SIB31 with a value set to ntn-UlSyncValidityDuration from a subframe indicated by epochTime.
  • T317 expires, another timer 318 (T318) starts and the UE 104 may attempt to re-acquire SIB31 before T318 expiry.
  • the UE When the T318 expires, the UE considers the uplink synchronization to its serving NTN cell is lost.
  • a triggering event associated with NES-specific CHO is enabled, or in other words, when NES-specific CHO execution condition is enabled, which means the serving cell is about to turn off, it is meaningless to re-acquire its SIB19/SIB31 for uplink synchronization to the serving cell before timer expiry. Otherwise, the evaluation for CHO events may be interrupted due to SIB19/SIB31 reception. On this basis, to avoid unnecessary interruption of CHO evaluation and execution, some considerations will be discussed as follows.
  • the UE 104 may avoid informing lower layers that uplink synchronization is lost upon the expiry of a timer for uplink synchronization. For example, for NR NTN access, if the NES mode indication is received from lower layers, indicating that the CHO event (s) associated with the nesEvent is enabled for at least one candidate cell, the UE 104 may not be required to re-acquire SIB19 before T430 expiry, and the UE 104 may not inform lower layers that uplink synchronization is lost upon T430 expiry.
  • the UE 104 may not be required to re-acquire SIB31 or SIB31-NB, before T318 expiry, and the UE 104 may not inform lower layers that uplink synchronization is lost upon T318 expiry.
  • the UE 104 may suspend the timer. For example, for NR NTN access, if the NES mode indication is received from lower layers, indicating that the CHO event (s) associated with the nesEvent is enabled for at least one candidate cell, the UE 104 may suspend T430. As another example, for LTE NTN access, if the NES mode indication is received from lower layers, indicating that the CHO event (s) associated with the nesEvent is enabled for at least one candidate cell, the UE 104 may suspend the T317 or T318.
  • the UE 104 may start another timer for the CHO procedure. For example, for NR NTN access, if the NES mode indication is received from lower layers, indicating that the CHO event (s) associated with the nesEvent is enabled for at least one candidate cell, the UE 104 may start another timer to allow the UE 104 to complete CHO execution.
  • the UE 104 may use the T318 for the CHO procedure.
  • the UE 104 may acquire the SIB for uplink synchronization to its serving cell before an expiry of a timer for uplink synchronization. For example, for NR NTN access, if the NES mode indication is received from lower layers, indicating that the CHO event (s) associated with the nesEvent is disabled for at least one candidate cell, the UE 104 may be required to re-acquire SIB19 before T430 expiry. The UE 104 may resume the T430 if suspended.
  • the UE 104 may be required to re-acquire SIB31 before T318 expiry. The UE 104 may resume the T317 or the T318 if suspended.
  • the UE 104 may determine, from the at least one candidate cell, a first candidate cell as a triggered cell for CHO.
  • the UE 104 may keep (or in other words, does not discard) an NES-specific CHO configuration (s) for one or more other candidate cells.
  • the one or more other candidate cell may be determined by excluding the first candidate cell from the at least one candidate cell.
  • the UE 104 may keep the CHO configuration (s) of other candidate cell (s) after the UE 104 executes a CHO to the triggered cell to reduce signalling overhead, with a consideration that the other candidate cell (s) may still be candidate (s) for the triggered cell.
  • the UE 104 may keep the NES-specific CHO configuration for the one or more other candidate cells after CHO to the first candidate cell is not completed. In this case, the UE 104 may determine, from the one or more other candidate cells, a second candidate cell as another triggered cell for CHO, and then perform CHO to the second candidate cell based on the kept NES-specific CHO configuration of the second candidate cell. In other words, when the CHO to the first candidate cell fails, the UE 104 may select another candidate cell (i.e., the second candidate cell) included in the kept CHO configuration, and then may use the kept CHO configuration of the second candidate cell to access the second candidate cell. In this way, it is allowed to reduce signaling overhead and accelerate CHO failure recovery in NTN.
  • the UE 104 may evaluate triggering event (s) associated with NES-specific CHO for the second candidate cell. For example, the UE 104 may evaluate one or more triggering events (for example, the condEvent D1/D2/T1, and/or the condEvent A3/A4/A5) associated with NES-specific CHO for the second candidate cell if the second candidate cell has a capability of supporting NES, which may be determined based on cellBarredNES in SIB1 of the second candidate cell. In this case, the UE 104 may evaluate the CHO event (s) associated with the nesEvent for the second candidate cell if the second cell supports the NES feature. As another example, the UE 104 may evaluate one or more triggering events associated with NES-specific CHO for the second candidate cell if the serving cell indicates that the one or more triggering events associated with NES-specific CHO are enabled for the second candidate cell.
  • triggering events for example, the condEvent D1/D2/T1, and/or the condEvent A3/A4
  • the UE 104 may keep the NES-specific CHO configuration for the one or more other candidate cells after CHO to the first candidate cell is completed. For example, the UE 104 may keep the NES-specific CHO configuration for the one or more other candidate cells according to a network indication. The UE 104 may keep the NES-specific CHO configuration for the one or more other candidate cells if it receives an indication to keep the NES-specific CHO configuration for the one or more other candidate cells. Alternatively or additionally, the UE 104 may keep the NES-specific CHO configuration for the one or more other candidate cells according to whether the first candidate cell supports the NES feature. The UE 104 may keep the NES-specific CHO configuration for the one or more other candidate cells if the first candidate cell supports NES.
  • the UE 104 may determine the second candidate cell from the one or more other candidate cells likewise, and perform CHO to the second candidate cell based on the kept NES-specific CHO configuration of the second candidate cell.
  • whether one or more triggering events associated with NES-specific CHO are enabled or disabled for one or more of the one or more other candidate cells may be considered by default or based on an indication of enabling or disabling the one or more triggering events, such as an explicit indication from the network, for example, from the serving cell, or from the first candidate cell.
  • NTN cells generated by the same satellite may have similar NES pattern (for example, footprints with the same size and cells with similar power on/off duration)
  • the NES-specific CHO configurations in the serving cell and a candidate cell may be similar or the same, for example, have the same distance thresholds or signal strength thresholds.
  • delta CHO configuration may be considered for NES-specific CHO events in NTN.
  • the delta CHO configuration may be understood as a configuration difference between a reference CHO configuration and a respective CHO configuration. In this way, it is possible to reduce signaling overhead for subsequent CHO.
  • the NES-specific CHO configuration for the at least one candidate cell may comprise a reference CHO configuration and one or more delta CHO configurations for one or more of the at least one candidate cell.
  • the NES-specific CHO configuration may comprise a reference CHO configuration and N delta CHO configurations, each of which may correspond to each of the N candidate cells.
  • the reference CHO configuration may comprise a CHO configuration of the serving cell or a specified CHO configuration.
  • the reference CHO configuration may be a CHO configuration of one of the N candidate cells, and in this case, the NES-specific CHO configuration may comprise the reference CHO configuration and N-1 delta CHO configurations, each of which may correspond to each of the other N-1 candidate cells other than the candidate cell associated with the reference CHO configuration.
  • the UE 104 may derive the CHO configuration with NES-specific CHO event (s) for the candidate cell based on the reference CHO configuration and the delta CHO configuration.
  • FIG. 3 illustrates an example of a device 300 that supports CHO for NES in accordance with aspects of the present disclosure.
  • the device 300 may be an example of a UE 104 or a network entity 102 as described herein.
  • the device 300 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 300 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 302, a memory 304, a transceiver 306, and, optionally, an I/O controller 308. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • interfaces e.g., buses
  • the processor 302, the memory 304, the transceiver 306, 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 302, the memory 304, the transceiver 306, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 302, the memory 304, the transceiver 306, 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 302 and the memory 304 coupled with the processor 302 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 302, instructions stored in the memory 304) .
  • the processor 302 may support wireless communication at the device 300 in accordance with examples as disclosed herein.
  • the processor 302 may be configured to operable to support a means for receiving, from a base station (BS) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO; and means for performing a CHO procedure from a serving cell to the at least one candidate cell based on the NES-specific CHO configuration.
  • BS base station
  • NES network energy saving
  • CHO conditional handover
  • the processor 302 may be configured to operable to support a means for transmitting, to a user equipment (UE) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO.
  • UE user equipment
  • NES network energy saving
  • CHO conditional handover
  • the processor 302 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 302 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 302.
  • the processor 302 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 304) to cause the device 300 to perform various functions of the present disclosure.
  • the memory 304 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 302 cause the device 300 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 302 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 304 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 308 may manage input and output signals for the device 300.
  • the I/O controller 308 may also manage peripherals not integrated into the device M02.
  • the I/O controller 308 may represent a physical connection or port to an external peripheral.
  • the I/O controller 308 may utilize an operating system such as or another known operating system.
  • the I/O controller 308 may be implemented as part of a processor, such as the processor 306.
  • a user may interact with the device 300 via the I/O controller 308 or via hardware components controlled by the I/O controller 308.
  • the device 300 may include a single antenna 310. However, in some other implementations, the device 300 may have more than one antenna 310 (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 306 may communicate bi-directionally, via the one or more antennas 310, wired, or wireless links as described herein.
  • the transceiver 306 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 306 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 310 for transmission, and to demodulate packets received from the one or more antennas 310.
  • the transceiver 306 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 310 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 310 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. 4 illustrates an example of a processor 400 that supports CHO for NES in accordance with aspects of the present disclosure.
  • the processor 400 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 400 may include a controller 402 configured to perform various operations in accordance with examples as described herein.
  • the processor 400 may optionally include at least one memory 404, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 400 may optionally include one or more arithmetic-logic units (ALUs) 400.
  • ALUs arithmetic-logic units
  • the processor 400 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 400) 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 402 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 400 to cause the processor 400 to support various operations in accordance with examples as described herein.
  • the controller 402 may operate as a control unit of the processor 400, generating control signals that manage the operation of various components of the processor 400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 402 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 404 and determine subsequent instruction (s) to be executed to cause the processor 400 to support various operations in accordance with examples as described herein.
  • the controller 402 may be configured to track memory address of instructions associated with the memory 404.
  • the controller 402 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 402 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 400 to cause the processor 400 to support various operations in accordance with examples as described herein.
  • the controller 402 may be configured to manage flow of data within the processor 400.
  • the controller 402 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 400.
  • ALUs arithmetic logic units
  • the memory 404 may include one or more caches (e.g., memory local to or included in the processor 400 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 404 may reside within or on a processor chipset (e.g., local to the processor 400) . In some other implementations, the memory 404 may reside external to the processor chipset (e.g., remote to the processor 400) .
  • caches e.g., memory local to or included in the processor 400 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 404 may reside within or on a processor chipset (e.g., local to the processor 400) . In some other implementations, the memory 404 may reside external to the processor chipset (e.g., remote to the processor 400) .
  • the memory 404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 400, cause the processor 400 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 402 and/or the processor 400 may be configured to execute computer-readable instructions stored in the memory 404 to cause the processor 400 to perform various functions.
  • the processor 400 and/or the controller 402 may be coupled with or to the memory 404, and the processor 400, the controller 402, and the memory 404 may be configured to perform various functions described herein.
  • the processor 400 may include multiple processors and the memory 404 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 400 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 400 may reside within or on a processor chipset (e.g., the processor 400) .
  • the one or more ALUs 400 may reside external to the processor chipset (e.g., the processor 400) .
  • One or more ALUs 400 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 400 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 400 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 400 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 400 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 400 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 400 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 400 may be configured to or operable to support a means for receiving, from a base station (BS) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO; and means for performing a CHO procedure from a serving cell to the at least one candidate cell based on the NES-specific CHO configuration.
  • BS base station
  • NES network energy saving
  • CHO conditional handover
  • the processor 400 may be configured to or operable to support a means for transmitting, to a user equipment (UE) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO.
  • UE user equipment
  • NES network energy saving
  • CHO conditional handover
  • FIG. 5 illustrates a flowchart of a method 500 that supports CHO for NES in accordance with aspects of the present disclosure.
  • the operations of the method 500 may be implemented by a device or its components as described herein.
  • the operations of the method 500 may be performed by a UE 104 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, from a base station (BS) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO.
  • BS base station
  • NES network energy saving
  • CHO conditional handover
  • the method may include performing a CHO procedure from a serving cell to the at least one candidate cell based on the NES-specific CHO configuration.
  • the operations of 520 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 520 may be performed by a UE 104 as described with reference to FIG. 1.
  • FIG. 6 illustrates a flowchart of a method 600 that supports CHO for NES in accordance with aspects of the present disclosure.
  • the operations of the method 600 may be implemented by a device or its components as described herein.
  • the operations of the method 600 may be performed by a BS 102 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting, to a user equipment (UE) , a network energy saving (NES) -specific conditional handover (CHO) configuration for at least one candidate cell, the NES-specific CHO configuration comprising a location-based triggering event or a time-based triggering event associated with NES-specific CHO.
  • UE user equipment
  • NES network energy saving
  • CHO conditional handover
  • the operations of 610 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 610 may be performed by a BS 102 as described with reference to FIG. 1.
  • 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)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent un transfert intercellulaire conditionnel (CHO) pour une économie d'énergie de réseau (NES). Dans certains modes de réalisation, un UE reçoit, en provenance d'une BS, une configuration de CHO spécifique à NES pour au moins une cellule candidate. La configuration de CHO spécifique à NES comprend un événement de déclenchement basé sur l'emplacement ou un événement de déclenchement basé sur le temps associé à un CHO spécifique à NES. De plus, l'UE effectue une procédure de CHO d'une cellule de desserte vers la au moins une cellule candidate sur la base de la configuration de CHO spécifique à NES. De cette manière, il est possible d'améliorer efficacement la procédure de CHO spécifique à NES.
PCT/CN2024/072092 2024-01-12 2024-01-12 Transfert intercellulaire conditionnel pour économie d'énergie de réseau Pending WO2024234703A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/072092 WO2024234703A1 (fr) 2024-01-12 2024-01-12 Transfert intercellulaire conditionnel pour économie d'énergie de réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/072092 WO2024234703A1 (fr) 2024-01-12 2024-01-12 Transfert intercellulaire conditionnel pour économie d'énergie de réseau

Publications (1)

Publication Number Publication Date
WO2024234703A1 true WO2024234703A1 (fr) 2024-11-21

Family

ID=93518592

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/072092 Pending WO2024234703A1 (fr) 2024-01-12 2024-01-12 Transfert intercellulaire conditionnel pour économie d'énergie de réseau

Country Status (1)

Country Link
WO (1) WO2024234703A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023170613A1 (fr) * 2022-03-10 2023-09-14 Nokia Technologies Oy Configuration de cho pour un délestage rapide pendant un arrêt de cellule
WO2023196223A1 (fr) * 2022-04-05 2023-10-12 Interdigital Patent Holdings, Inc. Accès à un réseau discontinu
WO2023216214A1 (fr) * 2022-05-13 2023-11-16 Qualcomm Incorporated Mesures de transfert associées à de multiples quantités de seuil
CN117119565A (zh) * 2022-05-16 2023-11-24 维沃移动通信有限公司 信息传输方法、装置、终端及网络侧设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023170613A1 (fr) * 2022-03-10 2023-09-14 Nokia Technologies Oy Configuration de cho pour un délestage rapide pendant un arrêt de cellule
WO2023196223A1 (fr) * 2022-04-05 2023-10-12 Interdigital Patent Holdings, Inc. Accès à un réseau discontinu
WO2023216214A1 (fr) * 2022-05-13 2023-11-16 Qualcomm Incorporated Mesures de transfert associées à de multiples quantités de seuil
CN117119565A (zh) * 2022-05-16 2023-11-24 维沃移动通信有限公司 信息传输方法、装置、终端及网络侧设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "CHO for NES", 3GPP DRAFT; R2-2305860, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 2, no. Incheon, Korea; 20230501, 21 May 2023 (2023-05-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052394691 *
NEC: "CHO procedure enhancement to support NES mode", 3GPP DRAFT; R2-2305864, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 2, no. Incheon, Korean; 20230522 - 20230526, 12 May 2023 (2023-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052390665 *

Similar Documents

Publication Publication Date Title
WO2024234703A1 (fr) Transfert intercellulaire conditionnel pour économie d'énergie de réseau
WO2025011026A1 (fr) Sélection de groupe de ressources
WO2025107718A1 (fr) Prédiction de défaillance de liaison radio
WO2025145658A1 (fr) Contrôle d'accès d'une cellule ntn
WO2025241073A1 (fr) Économie d'énergie de faisceau de satellite dans un ntn
WO2025246425A1 (fr) Gestion de ressource
WO2024093338A1 (fr) Dispositifs et procédés de communication
WO2025107660A1 (fr) Resélection de cellule
WO2025148315A1 (fr) Prédiction de défaillance de liaison radio en double connexion
WO2024093337A1 (fr) Dispositifs et procédés de communication
WO2025236737A1 (fr) Communication de lp-wus
WO2024169254A1 (fr) Détermination d'un état de cellule
WO2025156295A1 (fr) Continuité de service de multidiffusion ou de diffusion
WO2024259991A1 (fr) Défaillance dans une communication par relais
WO2024250686A1 (fr) Prédiction d'échec de transfert
WO2025107722A1 (fr) Détermination d'un état de cellule
WO2025152400A1 (fr) Gestion d'informations système
WO2025097819A1 (fr) Gestion de combinaison de fonctionnalités
WO2024159795A1 (fr) Dispositifs et procédés de communication
WO2025236750A1 (fr) Transmission en liaison montante
WO2024094228A1 (fr) Procédure de défaillance de trajet indirect en multi-trajet
WO2024169257A1 (fr) Rejet a base de psi
WO2025175830A1 (fr) Mobilité déclenchée par couche 1 ou couche 2 conditionnelle
WO2024207740A1 (fr) Mobilité déclenchée de couche 1 ou de couche 2
WO2024230254A1 (fr) Procédé de demande de signal de liaison descendante

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

Country of ref document: EP

Kind code of ref document: A1