WO2024063760A1 - Preconfigured cho - Google Patents

Preconfigured cho Download PDF

Info

Publication number
WO2024063760A1
WO2024063760A1 PCT/US2022/044149 US2022044149W WO2024063760A1 WO 2024063760 A1 WO2024063760 A1 WO 2024063760A1 US 2022044149 W US2022044149 W US 2022044149W WO 2024063760 A1 WO2024063760 A1 WO 2024063760A1
Authority
WO
WIPO (PCT)
Prior art keywords
conditional handover
conditional
indication
preconfigured
control
Prior art date
Application number
PCT/US2022/044149
Other languages
French (fr)
Inventor
Dimitri GOLD
Lars Dalsgaard
Original Assignee
Nokia Technologies Oy
Nokia Of America Corporation
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 Nokia Technologies Oy, Nokia Of America Corporation filed Critical Nokia Technologies Oy
Priority to PCT/US2022/044149 priority Critical patent/WO2024063760A1/en
Publication of WO2024063760A1 publication Critical patent/WO2024063760A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/34Reselection control
    • H04W36/36Reselection control by user or terminal equipment
    • H04W36/362Conditional handover

Definitions

  • Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as 3 rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), 5 th generation (5G) radio access technology (RAT), new radio (NR) access technology, 6 th generation (6G), and/or other communications systems.
  • 3GPP 3 rd Generation Partnership Project
  • LTE Long Term Evolution
  • 5G 5 th generation
  • RAT radio access technology
  • NR new radio
  • 6G 6 th generation
  • certain example embodiments may relate to systems and/or methods for mobility setting preconfiguration, activation, and execution for conditional handover.
  • Examples of mobile or wireless telecommunication systems may include radio frequency (RF) 5G RAT, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, NR access technology, and/or MulteFire Alliance.
  • 5G wireless systems refer to the next generation (NG) of radio systems and network architecture.
  • NG next generation
  • a 5G system is typically built on a 5G NR, but a 5G (or NG) network may also be built on E- UTRA radio.
  • NR can support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency- communication (URLLC), and massive machine-type communication (mMTC).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency- communication
  • mMTC massive machine-type communication
  • NG-RAN represents the radio access network (RAN) for 5G, which may provide radio access for NR, LTE, and LTE-A.
  • next-generation Node B when built on NR radio
  • NG-eNB next-generation eNB
  • a method may include transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover.
  • the method may further include detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers.
  • the method may further include transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
  • an apparatus may include means for transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover.
  • the apparatus may further include means for detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers.
  • the apparatus may further include means for transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
  • a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method.
  • the method may include transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover.
  • the method may further include detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers.
  • the method may further include transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
  • a computer program product may perform a method.
  • the method may include transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover.
  • the method may further include detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers.
  • the method may further include transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
  • an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to transmit, to a user equipment, a control message comprising at least one preconfigured conditional handover.
  • the at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to detect at least one setting associated with activation of at least one of the preconfigured conditional handovers.
  • the at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
  • an apparatus may include transmitting circuitry configured to transmit, to a user equipment, a control message comprising at least one preconfigured conditional handover.
  • the apparatus may further include detecting circuitry configured to detect at least one setting associated with activation of at least one of the preconfigured conditional handovers.
  • the apparatus may further include transmitting circuitry configured to transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
  • a method may include receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration.
  • the method may further include receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition.
  • the method may further include executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
  • an apparatus may include means for receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration.
  • the apparatus may further include means for receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition.
  • the apparatus may further include means for executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
  • a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method.
  • the method may include receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration.
  • the method may further include receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition.
  • the method may further include executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
  • a computer program product may perform a method.
  • the method may include receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration.
  • the method may further include receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition.
  • the method may further include executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
  • an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive, from a source network entity, a control message comprising at least one conditional handover preconfiguration.
  • the at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition.
  • the at least one memory and instructions, when executed by the at least one processor may further cause the apparatus at least to execute, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
  • an apparatus may include receiving circuitry configured to receive, from a source network entity, a control message comprising at least one conditional handover preconfiguration.
  • the apparatus may further include receiving circuitry configured to receive, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition.
  • the apparatus may further include executing circuitry configured to execute, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
  • FIG. 1 illustrates an example of a conditional handover procedure.
  • FIG. 2 illustrates an example downlink beam changes in a high speed train scenario.
  • FIG. 3 illustrates an example of reference signal received power traces of serving and target remote radio heads.
  • FIG. 4 illustrates mobility failure statistics from a system-level simulator.
  • FIG. 5 illustrates handover system-level simulations statistics comparing conservative and aggressive mobility settings for different values of discontinuous reception.
  • FIG. 6 illustrates an example of a flow diagram of a method according to various example embodiments.
  • FIG. 7 illustrates an example of a signaling diagram according to certain example embodiments.
  • FIG. 8A illustrates an example of reference signal received power traces of a serving and best target cell for one generic mobility setting.
  • FIG. 8A illustrates an example of reference signal received power traces of a serving and best target cell for two mobility settings.
  • FIG. 9 illustrates an example of various network devices according to some example embodiments.
  • FIG. 10 illustrates an example of a 5G network and system architecture according to certain example embodiments.
  • CHO may be defined as a handover (HO) that is executed by a user equipment (UE) when one or more HO execution conditions are met.
  • HO handover
  • UE user equipment
  • FIG. 1 CHO can enable a network to preconfigure the UE with one or more HO candidates and conditions when the UE autonomously initiates HO towards one of the preconfigured CHO candidates.
  • the UE may perform normal mobility measurements on the configured candidates, and possibly non-CHO candidate cells. If one of the CHO candidate cells fulfill the conditions configured for the CHO, the UE may switch to the target CHO candidate cells and initiate a random access procedure, without needing to send a measurement report and then waiting for a HO command.
  • HST high speed train
  • FIG. 2 Using these techniques, HO can be used between cells in high speed train (HST) deployments, as shown in FIG. 2 and other scenarios.
  • HST deployments are used as an example in this disclosure, any type of scenario where a UE moves, including moving rapidly, between serving areas may be used (e.g., cars, motorcycles, aircraft, drones).
  • the method may be applied in general and is not limited to specific velocities or scenarios.
  • 3GPP Release (Rel)-17 includes requirements for the HST deployments in millimeter wave (mmWave) bands (e.g., frequency range 2 (FR2)). For example, two requirements correspond to 2 receive (Rx) beams at the UE when remote radio heads (RRH) are located next to a road or railway track (e.g., 10 meters away), and with 6 Rx beams when the RRHs at positioned at a further distance.
  • 3GPP Rel-18 is continuing to develop HST FR2 techniques, including deployments in tunnels where the RRHs are positioned relatively close to the track, creating challenging mobility conditions.
  • Some such mobility scenarios require very timely and low latency cell changes and beam switches.
  • UEs may cross the edge of a cell and beam and/or beams at very high speeds; in a high-frequency (e.g., mmWave) deployment, the serving beam may deteriorate very rapidly when the UE approaches, for example, the cell edge.
  • a high-frequency (e.g., mmWave) deployment the serving beam may deteriorate very rapidly when the UE approaches, for example, the cell edge.
  • FIG. 3 shows RSRP traces of serving and target RRHs, with vertical lines indicating event A3 trigger coordinates (i.e., triggered when a neighboring cell becomes better than the serving cell by an offset), HO complete, and source RRH locations.
  • This drop in RSRP may occur due to sharp beamforming used in FR2 to cover the longer inter-cell distance (700 m in HST FR2 priority scenarios). Additionally, the backplane may cancel the signal radiation behind the RRH. Therefore, if high-speed mobility relies on legacy mechanisms (e.g., layer 1 (Ll)/L3 measurements averaging, feedback from the UE, mobility command signaling to/from the base station), the UE may experience very low signal to interference & noise ratio (SINR) conditions. Closed mobility loops based on measurements may also be too slow to avoid signal degradation and mobility problems from the serving beam. This is depicted in the results of mobility failure statistics from a system-level simulator shown in FIG.
  • Ll layer 1
  • DRX discontinuous reception
  • the network would need the UE to provide the network with assistance and feedback (z.e., RSRP reports, RSRQ reports, SINR reports). If the beam change involves strict timing requirements, continuous and low latency reports may be needed from the UE, which could increase UE measurement burdens, power consumption, and reporting and network UL resources consumed by the UE.
  • assistance and feedback z.e., RSRP reports, RSRQ reports, SINR reports.
  • the HO may be reconfigured with aggressive cell mobility parameters. However, this may also affect other deployment areas that are distant from the cell edge, since such aggressive mobility parameters can cause unnecessary mobility events, and lead to unnecessary HOs and ping-pongs between cells, as shown in FIG. 5.
  • FIG. 5 depicts system-level simulations comparing conservative and aggressive mobility settings, where settings that are more aggressive generally correspond with large increases in HO frequency. This may result in frequent interruptions and breaks in data transmissions, and a more general degradation in overall system performance.
  • CHO may lead to reduced HO procedure latencies, wherein the UE does not need an explicit HO command (e.g., based on a measurement report) from the base station to switch to the new cell.
  • Timely configuration of CHO (z.e., steps 2-3 in FIG. 1) may also increase RRC signaling delays from the base station and UE processing delays, creating additional latency in dynamic mobility conditions.
  • special UE conditions e.g., close to the edge of the beam/RRH coverage
  • HO/CHO(s) with more aggressive parameters are configured too early, unnecessary mobility events may interrupt data transmissions, degrading network performance.
  • timely configuration of CHO may also be difficult due to RRC signaling delays from the base station and UE processing delays.
  • Certain example embodiments described herein may have various benefits and/or advantages to overcome the disadvantages described above.
  • certain example embodiments may provide highly flexible mobility configurations tailored to the deployment due to the ability to configure multiple mobility settings in a cell. Slower mobility CHO setting preparation and preconfiguration operations may also be separated from the faster activation and execution steps.
  • mobility settings may be activated with low latencies; thus, different mobility settings can be used in areas where they are specifically needed. For example, CHO with aggressive parameters may only be used in a small area near the edge of a RRH or cell.
  • CHO mobility settings may be restricted to certain regions and/or UE conditions (e.g., when the last beam of the cell is used and/or when the UE can switch to the first beam of the new cell).
  • UE conditions e.g., when the last beam of the cell is used and/or when the UE can switch to the first beam of the new cell.
  • Various example embodiments discussed herein may enable low latency switching and execution of different mobility settings in the cell, allowing the most appropriate mobility parameters to be used in the corresponding coverage areas/UE conditions.
  • Several sets of CHO parameters z.e., several different mobility settings
  • the UE may not be allowed to use CHOs before the mobility setting change is triggered.
  • the UE may use its original mobility settings (e.g., regular HO or default CHO setting) in the wide area.
  • the most demanding and timeconsuming preparation and signaling e.g., steps 2 and 3 in FIG. 1 may be performed early enough, including before the UE enters the area where different (e.g., more aggressive) mobility settings shall be used.
  • the new mobility setting i.e., another CHO setting
  • the new mobility setting is triggered either with, for example, faster medium access control (MAC) control element (CE) or downlink control information (DO) signaling, or alternatively, by certain conditions directly at the UE indicated to it at 603, as discussed below.
  • MAC medium access control
  • CE control element
  • DO downlink control information
  • FIG. 6 illustrates an example of a flow diagram of a method of mobility setting preconfiguration, activation, and execution for the case of the nonlimiting example using CHO that may be performed by aNE, such as NE 910 illustrated in FIG. 9, according to various example embodiments. More specifically, FIG. 5 depicts CHO (pre) configuration and activation as a realization of multiple mobility settings
  • the method may include determining whether the UE is deployed and/or whether conditions exist for multiple mobility settings.
  • the method may include preparing a CHO with at least one candidate NE, including parameters including HO request, admission control, and HO acknowledgement required.
  • the method may include either re-using existing RRC signaling or extending the existing RRC signaling with additional CHO activation and/or execution criteria where new mobility settings are (pre)configured (e.g., CHO configuration is signaled to the UE).
  • the new mobility settings may indicate that the CHO shall be activated only if a particular serving transmit (Tx) beam/transmission configuration indicator (TCI) state is used/activated.
  • Tx serving transmit
  • TCI beam/transmission configuration indicator
  • UE-based activation and switching to preconfigured CHO according to mobility settings may be triggered by CHO activation/switching conditions preconfigured at the UE by the NW, such as RRC signaling; this may be performed additionally to, or alternatively from, CHO pre-configured before 601.
  • the RRC signaling may indicate that the CHO is shall not be active before a mobility setting change is triggered (i.e., 604).
  • the method may further include configuring the CHO with additional conditions that the CHO may be executed only for predefined target cells and/or beams. It is noted that 601-603 may be performed individually, in certain groups, or together (e.g., when the UE connects to a cell).
  • the method may include determining whether the conditions for the mobility change have been triggered. For example, if different mobility settings are to be applied only for a given serving beam/TCI state, and were already signaled to the UE at 603, the UE may activate a new mobility parameter setting (CHO setting) on its own.
  • the new mobility parameter setting may be changed while executing CHO (e.g., serving cell is changed), or without executing CHO (e.g., serving cell is not changed).
  • the change of mobility parameter setting may be executed while executing the CHO (e.g., change of the cell).
  • the change of mobility parameter setting may be executed without executing the CHO (e.g., the serving cell is not changed).
  • the decision to change mobility setting can be made at the NW side, and then signaled to the UE either explicitly or together with other signaling (e.g., with TCI state switching command).
  • aNE may determine to change mobility setting, and then signal to the UE either explicitly or with other signaling (e.g., with TCI state switching command).
  • the method may include forwarding, by a source NE, data to candidate cells (i.e., early status transfer).
  • the method may include changing the mobility settings (i.e., CHO activation) at the UE, enabling the UE to execute CHO.
  • mobility settings i.e., CHO activation
  • the method may include checking either regular or additional new conditions at 603 conditions for CHO execution.
  • new additional conditions may include that the target cell and/or beam are from the preconfigured list.
  • the preconfigured conditions from 603 may also be checked.
  • the method may include resetting, updating, and/or returning to a default mobility setting at the UE.
  • FIG. 7 illustrates an example of a signaling diagram depicting for mobility setting preconfiguration, activation, and execution for CHO.
  • Source NE 730 and target NE(s) 740, and UE 720 may be similar to NE 910 and UE 920, respectively, as illustrated in FIG. 9, according to certain example embodiments.
  • UE 720 may establish a connection with source NE 730.
  • Some default mobility settings may be used to establish the connection; for example, the default mobility settings may be regular HO-based mobility settings.
  • source NE 730 may provide those additional mobility settings to UE 720 at the initial RRC cell configuration.
  • source NE 730 may use measurements to infer that UE 720 is moving and the direction of motion.
  • NE 730 may transmit controls and/or measurement configurations and UE 720 may report measurements to source NE 730.
  • source NE 730 may determine whether multiple mobility settings are needed.
  • target NE(s) 740 may prepare CHO with candidate cells.
  • source NE 730 may transmit a RRC message to UE 720, which may include at least one CHO preconfiguration.
  • the RRC message may include new additional instructions for UE 720 regarding the CHO (z.e., preconfiguration and/or conditions to activate/change in between CHO configurations, i.e., mobility settings).
  • the RRC message may indicate to UE 720 that configured CHO may not be used before it is activated from source NE 730, or until an additional condition is triggered (e.g, UE 720 is switched to a particular TCI state/beam).
  • UE 720 may transmit to source NE 730 a RRC complete message.
  • UE 720 and source NE 730 may exchange user data.
  • UE 720, source NE 730, and target NE(s) 740 may perform NE measurements and reports.
  • source NE 730 may evaluate and detect at least one triggering condition, such as mobility setting triggering conditions for CHO preconfiguration activation.
  • UE 720 may continue regular operation while source NE 730 continuously checks for CHO activation conditions (z.e., for conditions to trigger the change mobility settings).
  • the mobility setting triggering conditions may be based upon network signaling or a preconfigured condition.
  • source NE 730 may transmit to UE 720, in response to the detection, an indication to activate the preconfigured CHO via DCI and/or MAC CE.
  • UE 720, source NE 730, and target NE(s) 740 may perform NE measurements and reports in normal operation. However, a new mobility setting (CHO configuration) may be active at UE 720.
  • UE 720 may continuously monitor for CHO conditions.
  • conditions may include regular CHO or additionally preconfigured conditions at 706 (e.g., target beam/TCI state).
  • UE 720, source NE 730, and target NE(s) 740 may execute, based upon the RRC message received at 706 and/or the indicated received at 711, the CHO, and data exchanges may continue with a new NE.
  • UE 720, source NE 730, and target NEs 740 may exchange user data.
  • FIGs. 8A-B depict two RSRP time traces in an example where the train is traveling in the opposite direction to the serving beam, similar to that shown in FIG. 2.
  • FIG. 8A depicts the RSRP trace when only one generic mobility setting is configured
  • FIG. 8B illustrates a trace when two settings are use, with aggressive parameters next to the RRH. Both figures show that significant drops in the signal strength next to the RRH can be avoided.
  • FIG. 9 illustrates an example of a system according to certain example embodiments.
  • a system may include multiple devices, such as, for example, NE 910 and/or UE 920.
  • NE 910 may be one or more of a base station, such as an eNB or gNB, a serving gateway, a server, and/or any other access node or combination thereof.
  • NE 910 may further comprise at least one gNB-centralized unit (CU), which may be associated with at least one gNB-distributed unit (DU).
  • CU gNB-centralized unit
  • DU gNB-distributed unit
  • a gNB- CU and a gNB-DU may be in communication via at least one Fl interface, at least one X n -C interface, and/or at least one NG interface via a 5 th generation core (5GC).
  • 5GC 5 th generation core
  • UE 920 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof.
  • a mobile device such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof.
  • GPS global positioning system
  • NE 910 and/or UE 920 may be one or more of a citizens broadband radio service device (CBSD).
  • CBSD citizens broadband radio service device
  • NE 910 and/or UE 920 may include at least one processor, respectively indicated as 911 and 921.
  • processors 911 and 921 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device.
  • the processors may be implemented as a single controller, or a plurality of controllers or processors.
  • At least one memory may be provided in one or more of the devices, as indicated at 912 and 922.
  • the memory may be fixed or removable.
  • the memory may include computer program instructions or computer code contained therein.
  • Memories 912 and 922 may independently be any suitable storage device, such as a non-transitory computer-readable medium.
  • the term “non-transitory,” as used herein, may correspond to a limitation of the medium itself (z.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., random access memory (RAM) vs. read-only memory (ROM)).
  • RAM random access memory
  • ROM read-only memory
  • a hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used.
  • the memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors.
  • the computer program instructions stored in the memory, and which may be processed by the processors may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
  • Processors 911 and 921, memories 912 and 922, and any subset thereof, may be configured to provide means corresponding to the various blocks of FIGs. 6-7.
  • the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device.
  • MEMS micro electrical mechanical system
  • Other sensors are also permitted, and may be configured to determine location, elevation, velocity, orientation, and so forth, such as barometers, compasses, and the like.
  • transceivers 913 and 923 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 914 and 924.
  • the device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple RATs. Other configurations of these devices, for example, may be provided.
  • Transceivers 913 and 923 may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.
  • the memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE, to perform any of the processes described above (z.e., FIGs. 6-7). Therefore, in certain example embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain example embodiments may be performed entirely in hardware.
  • an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIGs. 6- 7.
  • circuitry may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry), (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions), and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
  • software e.g., firmware
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • FIG. 10 illustrates an example of a 5G network and system architecture according to certain example embodiments. Shown are multiple network functions that may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware.
  • the NE and UE illustrated in FIG. 10 may be similar to NE 1010 and UE 1020, respectively.
  • the user plane function (UPF) may provide services such as intra- RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of downlink packets, and/or triggering of downlink data notifications.
  • the application function (AF) may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.
  • processors 911 and 921, and memories 912 and 922 may be included in or may form a part of processing circuitry or control circuitry.
  • transceivers 913 and 923 may be included in or may form a part of transceiving circuitry.
  • an apparatus e.g., NE 910 and/or UE 920
  • the means may include one or more processors, memory, controllers, transmitters, receivers, and/or computer program code for causing the performance of the operations.
  • NE 910 may be controlled by memory 912 and processor 911 to transmit, to a user equipment, a control message comprising at least one preconfigured conditional handover; detect at least one setting associated with activation of at least one of the preconfigured conditional handovers; and transmit, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
  • Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover; means for detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers; and means for transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
  • UE 920 may be controlled by memory 912 and processor 921 to receive, from a source network entity, a control message comprising at least one conditional handover preconfiguration; receive, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition; and execute, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
  • Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration; means for receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition; and means for executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
  • eMBB Enhanced Mobile Broadband
  • eNB Evolved Node B

Landscapes

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

Abstract

Systems, methods, apparatuses, and computer program products for mobility setting preconfiguration, activation, and execution for conditional handover. One method may include transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover; detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers; and transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.

Description

TITLE:
PRECONFIGURED CHO
TECHNICAL FIELD:
[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), 5th generation (5G) radio access technology (RAT), new radio (NR) access technology, 6th generation (6G), and/or other communications systems. For example, certain example embodiments may relate to systems and/or methods for mobility setting preconfiguration, activation, and execution for conditional handover.
BACKGROUND:
[0002] Examples of mobile or wireless telecommunication systems may include radio frequency (RF) 5G RAT, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, NR access technology, and/or MulteFire Alliance. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. A 5G system is typically built on a 5G NR, but a 5G (or NG) network may also be built on E- UTRA radio. It is expected that NR can support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency- communication (URLLC), and massive machine-type communication (mMTC). NR is expected to deliver extreme broadband, ultra-robust, low- latency connectivity, and massive networking to support the Internet of Things (loT). The next generation radio access network (NG-RAN) represents the radio access network (RAN) for 5G, which may provide radio access for NR, LTE, and LTE-A. It is noted that the nodes in 5G providing radio access functionality to a user equipment (e.g., similar to the Node B in UTRAN or the Evolved Node B (eNB) in LTE) may be referred to as next-generation Node B (gNB) when built on NR radio, and may be referred to as next-generation eNB (NG-eNB) when built on E-UTRA radio.
SUMMARY:
[0003] In accordance with some example embodiments, a method may include transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover. The method may further include detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers. The method may further include transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
[0004] In accordance with certain example embodiments, an apparatus may include means for transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover. The apparatus may further include means for detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers. The apparatus may further include means for transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
[0005] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover. The method may further include detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers. The method may further include transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers. [0006] In accordance with some example embodiments, a computer program product may perform a method. The method may include transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover. The method may further include detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers. The method may further include transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers. [0007] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to transmit, to a user equipment, a control message comprising at least one preconfigured conditional handover. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to detect at least one setting associated with activation of at least one of the preconfigured conditional handovers. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
[0008] In accordance with various example embodiments, an apparatus may include transmitting circuitry configured to transmit, to a user equipment, a control message comprising at least one preconfigured conditional handover. The apparatus may further include detecting circuitry configured to detect at least one setting associated with activation of at least one of the preconfigured conditional handovers. The apparatus may further include transmitting circuitry configured to transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers. [0009] In accordance with some example embodiments, a method may include receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration. The method may further include receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition. The method may further include executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
[0010] In accordance with certain example embodiments, an apparatus may include means for receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration. The apparatus may further include means for receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition. The apparatus may further include means for executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
[0011] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration. The method may further include receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition. The method may further include executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration. [0012] In accordance with some example embodiments, a computer program product may perform a method. The method may include receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration. The method may further include receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition. The method may further include executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
[0013] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive, from a source network entity, a control message comprising at least one conditional handover preconfiguration. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to execute, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
[0014] In accordance with various example embodiments, an apparatus may include receiving circuitry configured to receive, from a source network entity, a control message comprising at least one conditional handover preconfiguration. The apparatus may further include receiving circuitry configured to receive, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition. The apparatus may further include executing circuitry configured to execute, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
BRIEF DESCRIPTION OF THE DRAWINGS:
[0015] For a proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:
[0016] FIG. 1 illustrates an example of a conditional handover procedure.
[0017] FIG. 2 illustrates an example downlink beam changes in a high speed train scenario.
[0018] FIG. 3 illustrates an example of reference signal received power traces of serving and target remote radio heads.
[0019] FIG. 4 illustrates mobility failure statistics from a system-level simulator.
[0020] FIG. 5 illustrates handover system-level simulations statistics comparing conservative and aggressive mobility settings for different values of discontinuous reception.
[0021] FIG. 6 illustrates an example of a flow diagram of a method according to various example embodiments.
[0022] FIG. 7 illustrates an example of a signaling diagram according to certain example embodiments.
[0023] FIG. 8A illustrates an example of reference signal received power traces of a serving and best target cell for one generic mobility setting.
[0024] FIG. 8A illustrates an example of reference signal received power traces of a serving and best target cell for two mobility settings.
[0025] FIG. 9 illustrates an example of various network devices according to some example embodiments.
[0026] FIG. 10 illustrates an example of a 5G network and system architecture according to certain example embodiments.
DETAILED DESCRIPTION: [0027] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for mobility setting preconfiguration, activation, and execution for conditional handover (CHO) is not intended to limit the scope of certain example embodiments, but is instead representative of selected example embodiments.
[0028] CHO may be defined as a handover (HO) that is executed by a user equipment (UE) when one or more HO execution conditions are met. As illustrated in FIG. 1, CHO can enable a network to preconfigure the UE with one or more HO candidates and conditions when the UE autonomously initiates HO towards one of the preconfigured CHO candidates. Once the UE has been configured with one or more CHO candidates, the UE may perform normal mobility measurements on the configured candidates, and possibly non-CHO candidate cells. If one of the CHO candidate cells fulfill the conditions configured for the CHO, the UE may switch to the target CHO candidate cells and initiate a random access procedure, without needing to send a measurement report and then waiting for a HO command. Using these techniques, HO can be used between cells in high speed train (HST) deployments, as shown in FIG. 2 and other scenarios. While HST deployments are used as an example in this disclosure, any type of scenario where a UE moves, including moving rapidly, between serving areas may be used (e.g., cars, motorcycles, aircraft, drones). The method may be applied in general and is not limited to specific velocities or scenarios.
[0029] 3GPP Release (Rel)-17 includes requirements for the HST deployments in millimeter wave (mmWave) bands (e.g., frequency range 2 (FR2)). For example, two requirements correspond to 2 receive (Rx) beams at the UE when remote radio heads (RRH) are located next to a road or railway track (e.g., 10 meters away), and with 6 Rx beams when the RRHs at positioned at a further distance. 3GPP Rel-18 is continuing to develop HST FR2 techniques, including deployments in tunnels where the RRHs are positioned relatively close to the track, creating challenging mobility conditions.
[0030] Some such mobility scenarios require very timely and low latency cell changes and beam switches. For example, UEs may cross the edge of a cell and beam and/or beams at very high speeds; in a high-frequency (e.g., mmWave) deployment, the serving beam may deteriorate very rapidly when the UE approaches, for example, the cell edge.
[0031] This may occur when a HST UE travels towards a transmission point (e.g., transmission reception point (TRP), RRH, access point (AP)), as depicted in FIG. 2. In this situation, the reference signal received power (RSRP) of the serving beam may drop from -80 decibel-milliwatts (dBm) to -110 dBm in less than 20 meters, as shown in FIG. 3. In particular, FIG. 3 shows RSRP traces of serving and target RRHs, with vertical lines indicating event A3 trigger coordinates (i.e., triggered when a neighboring cell becomes better than the serving cell by an offset), HO complete, and source RRH locations. This drop in RSRP may occur due to sharp beamforming used in FR2 to cover the longer inter-cell distance (700 m in HST FR2 priority scenarios). Additionally, the backplane may cancel the signal radiation behind the RRH. Therefore, if high-speed mobility relies on legacy mechanisms (e.g., layer 1 (Ll)/L3 measurements averaging, feedback from the UE, mobility command signaling to/from the base station), the UE may experience very low signal to interference & noise ratio (SINR) conditions. Closed mobility loops based on measurements may also be too slow to avoid signal degradation and mobility problems from the serving beam. This is depicted in the results of mobility failure statistics from a system-level simulator shown in FIG. 4, which shows that, even with enhanced requirements (e.g., Scaling 2), mobility failures may occur without discontinuous reception (DRX) (i.e., DRX 0 in FIG. 4), e.g., in the scenario shown in FIG. 2. As shown in FIG. 2, the train may move in the direction opposite to the orientation of the RRH panels and beams.
[0032] In order to provide timely and robust beam changes, the network would need the UE to provide the network with assistance and feedback (z.e., RSRP reports, RSRQ reports, SINR reports). If the beam change involves strict timing requirements, continuous and low latency reports may be needed from the UE, which could increase UE measurement burdens, power consumption, and reporting and network UL resources consumed by the UE.
[0033] The HO may be reconfigured with aggressive cell mobility parameters. However, this may also affect other deployment areas that are distant from the cell edge, since such aggressive mobility parameters can cause unnecessary mobility events, and lead to unnecessary HOs and ping-pongs between cells, as shown in FIG. 5. In particular, FIG. 5 depicts system-level simulations comparing conservative and aggressive mobility settings, where settings that are more aggressive generally correspond with large increases in HO frequency. This may result in frequent interruptions and breaks in data transmissions, and a more general degradation in overall system performance. [0034] CHO may lead to reduced HO procedure latencies, wherein the UE does not need an explicit HO command (e.g., based on a measurement report) from the base station to switch to the new cell. However, as explained above, configuring only one set of HO or CHO parameters may not always be optimal. In addition, CHO may trigger the UE to perform HO at unnecessary times (e.g., where the target cell is available long before the HO should occur). [0035] Timely configuration of CHO (z.e., steps 2-3 in FIG. 1) may also increase RRC signaling delays from the base station and UE processing delays, creating additional latency in dynamic mobility conditions. Thus, it may be desirable for re-configuration of mobility parameters next to the area with special UE conditions (e.g., close to the edge of the beam/RRH coverage) to include UE reporting assistance without delaying the cell switch. [0036] There may be scenarios where the lowest possible latency cell/beam switching delay is essential. In order to enable timely and robust HO, more aggressive HO parameters and/or reporting may be required in some areas, such as at the cell edge. However, closed mobility loops based on measurements may be too slow to avoid signal degradation from the serving beam. Generic mobility setting/configuration/parametrizations may also be unsuitable for all areas/UE conditions of the deployment/cell. If HO/CHO(s) with more aggressive parameters are configured too early, unnecessary mobility events may interrupt data transmissions, degrading network performance. Alternatively, timely configuration of CHO may also be difficult due to RRC signaling delays from the base station and UE processing delays.
[0037] Certain example embodiments described herein may have various benefits and/or advantages to overcome the disadvantages described above. For example, certain example embodiments may provide highly flexible mobility configurations tailored to the deployment due to the ability to configure multiple mobility settings in a cell. Slower mobility CHO setting preparation and preconfiguration operations may also be separated from the faster activation and execution steps. In addition, mobility settings may be activated with low latencies; thus, different mobility settings can be used in areas where they are specifically needed. For example, CHO with aggressive parameters may only be used in a small area near the edge of a RRH or cell. Furthermore, particular CHO mobility settings may be restricted to certain regions and/or UE conditions (e.g., when the last beam of the cell is used and/or when the UE can switch to the first beam of the new cell). As a result, mobility robustness may be improved with minimal performance losses. Thus, certain example embodiments discussed below are directed to improvements in computer-related technology.
[0038] Various example embodiments discussed herein may enable low latency switching and execution of different mobility settings in the cell, allowing the most appropriate mobility parameters to be used in the corresponding coverage areas/UE conditions. Several sets of CHO parameters (z.e., several different mobility settings) may be provided to the UE that is entering the cell (e.g., together with RRC configuration) or at a later stage (e.g., with RRC Reconfiguration). Compared to conventional CHO procedures, after the candidate target cells are prepared, and when the UE is configured with the CHOs (i.e., with new mobility settings), the UE may not be allowed to use CHOs before the mobility setting change is triggered. Thus, the UE may use its original mobility settings (e.g., regular HO or default CHO setting) in the wide area. At the same time, the most demanding and timeconsuming preparation and signaling (e.g., steps 2 and 3 in FIG. 1) may be performed early enough, including before the UE enters the area where different (e.g., more aggressive) mobility settings shall be used. Then, the new mobility setting (i.e., another CHO setting) is triggered either with, for example, faster medium access control (MAC) control element (CE) or downlink control information (DO) signaling, or alternatively, by certain conditions directly at the UE indicated to it at 603, as discussed below. Alternatively, other signaling may be used.
[0039] FIG. 6 illustrates an example of a flow diagram of a method of mobility setting preconfiguration, activation, and execution for the case of the nonlimiting example using CHO that may be performed by aNE, such as NE 910 illustrated in FIG. 9, according to various example embodiments. More specifically, FIG. 5 depicts CHO (pre) configuration and activation as a realization of multiple mobility settings
[0040] At 601, the method may include determining whether the UE is deployed and/or whether conditions exist for multiple mobility settings.
[0041] At 602, the method may include preparing a CHO with at least one candidate NE, including parameters including HO request, admission control, and HO acknowledgement required. [0042] At 603, the method may include either re-using existing RRC signaling or extending the existing RRC signaling with additional CHO activation and/or execution criteria where new mobility settings are (pre)configured (e.g., CHO configuration is signaled to the UE). For example, the new mobility settings may indicate that the CHO shall be activated only if a particular serving transmit (Tx) beam/transmission configuration indicator (TCI) state is used/activated. In some example embodiments, UE-based activation and switching to preconfigured CHO according to mobility settings may be triggered by CHO activation/switching conditions preconfigured at the UE by the NW, such as RRC signaling; this may be performed additionally to, or alternatively from, CHO pre-configured before 601.
[0043] Alternatively, the RRC signaling may indicate that the CHO is shall not be active before a mobility setting change is triggered (i.e., 604). In various example embodiments, the method may further include configuring the CHO with additional conditions that the CHO may be executed only for predefined target cells and/or beams. It is noted that 601-603 may be performed individually, in certain groups, or together (e.g., when the UE connects to a cell).
[0044] At 604, the method may include determining whether the conditions for the mobility change have been triggered. For example, if different mobility settings are to be applied only for a given serving beam/TCI state, and were already signaled to the UE at 603, the UE may activate a new mobility parameter setting (CHO setting) on its own. In various example embodiments, the new mobility parameter setting may be changed while executing CHO (e.g., serving cell is changed), or without executing CHO (e.g., serving cell is not changed). In some example embodiments, the change of mobility parameter setting may be executed while executing the CHO (e.g., change of the cell). In certain example embodiments, the change of mobility parameter setting may be executed without executing the CHO (e.g., the serving cell is not changed). [0045] Alternatively, the decision to change mobility setting can be made at the NW side, and then signaled to the UE either explicitly or together with other signaling (e.g., with TCI state switching command). Alternatively, aNE may determine to change mobility setting, and then signal to the UE either explicitly or with other signaling (e.g., with TCI state switching command).
[0046] At 605, the method may include forwarding, by a source NE, data to candidate cells (i.e., early status transfer).
[0047] At 606, the method may include changing the mobility settings (i.e., CHO activation) at the UE, enabling the UE to execute CHO.
[0048] At 607, the method may include checking either regular or additional new conditions at 603 conditions for CHO execution. For example, new additional conditions may include that the target cell and/or beam are from the preconfigured list. The preconfigured conditions from 603 may also be checked.
[0049] At 608, the method may include resetting, updating, and/or returning to a default mobility setting at the UE.
[0050] FIG. 7 illustrates an example of a signaling diagram depicting for mobility setting preconfiguration, activation, and execution for CHO. Source NE 730 and target NE(s) 740, and UE 720, may be similar to NE 910 and UE 920, respectively, as illustrated in FIG. 9, according to certain example embodiments.
[0051] At 701, UE 720 may establish a connection with source NE 730. Some default mobility settings may be used to establish the connection; for example, the default mobility settings may be regular HO-based mobility settings.
[0052] At 702, if source NE 730 already knows by some means at the connection establishment (e.g., from the sequence of the previous HOs, UE location) that multiple mobility settings (e.g. , CHO configurations) need to be configured at UE 720, source NE 730 may provide those additional mobility settings to UE 720 at the initial RRC cell configuration. In various example embodiments, source NE 730 may use measurements to infer that UE 720 is moving and the direction of motion. At 703, NE 730 may transmit controls and/or measurement configurations and UE 720 may report measurements to source NE 730.
[0053] At 704, based on the measurement reports received from UE 720, source NE 730 may determine whether multiple mobility settings are needed.
[0054] At 705, target NE(s) 740 may prepare CHO with candidate cells.
[0055] At 706, if UE 720 has not received new mobility settings, source NE 730 may transmit a RRC message to UE 720, which may include at least one CHO preconfiguration. In various example embodiments, the RRC message may include new additional instructions for UE 720 regarding the CHO (z.e., preconfiguration and/or conditions to activate/change in between CHO configurations, i.e., mobility settings). For example, the RRC message may indicate to UE 720 that configured CHO may not be used before it is activated from source NE 730, or until an additional condition is triggered (e.g, UE 720 is switched to a particular TCI state/beam). In response, at 707, UE 720 may transmit to source NE 730 a RRC complete message.
[0056] At 708, UE 720 and source NE 730 may exchange user data.
[0057] At 709, UE 720, source NE 730, and target NE(s) 740 may perform NE measurements and reports.
[0058] At 710, source NE 730 may evaluate and detect at least one triggering condition, such as mobility setting triggering conditions for CHO preconfiguration activation. In particular, UE 720 may continue regular operation while source NE 730 continuously checks for CHO activation conditions (z.e., for conditions to trigger the change mobility settings). The mobility setting triggering conditions may be based upon network signaling or a preconfigured condition.
[0059] At 711, source NE 730 may transmit to UE 720, in response to the detection, an indication to activate the preconfigured CHO via DCI and/or MAC CE. [0060] At 712, UE 720, source NE 730, and target NE(s) 740 may perform NE measurements and reports in normal operation. However, a new mobility setting (CHO configuration) may be active at UE 720.
[0061] At 713, UE 720 may continuously monitor for CHO conditions. For example, conditions may include regular CHO or additionally preconfigured conditions at 706 (e.g., target beam/TCI state).
[0062] At 714, UE 720, source NE 730, and target NE(s) 740 may execute, based upon the RRC message received at 706 and/or the indicated received at 711, the CHO, and data exchanges may continue with a new NE.
[0063] At 715, UE 720, source NE 730, and target NEs 740 may exchange user data.
[0064] FIGs. 8A-B depict two RSRP time traces in an example where the train is traveling in the opposite direction to the serving beam, similar to that shown in FIG. 2. FIG. 8A depicts the RSRP trace when only one generic mobility setting is configured, while FIG. 8B illustrates a trace when two settings are use, with aggressive parameters next to the RRH. Both figures show that significant drops in the signal strength next to the RRH can be avoided.
[0065] FIG. 9 illustrates an example of a system according to certain example embodiments. In one example embodiment, a system may include multiple devices, such as, for example, NE 910 and/or UE 920.
[0066] NE 910 may be one or more of a base station, such as an eNB or gNB, a serving gateway, a server, and/or any other access node or combination thereof. [0067] NE 910 may further comprise at least one gNB-centralized unit (CU), which may be associated with at least one gNB-distributed unit (DU). A gNB- CU and a gNB-DU may be in communication via at least one Fl interface, at least one Xn-C interface, and/or at least one NG interface via a 5th generation core (5GC).
[0068] UE 920 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof. Furthermore, NE 910 and/or UE 920 may be one or more of a citizens broadband radio service device (CBSD).
[0069] NE 910 and/or UE 920 may include at least one processor, respectively indicated as 911 and 921. Processors 911 and 921 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.
[0070] At least one memory may be provided in one or more of the devices, as indicated at 912 and 922. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. Memories 912 and 922 may independently be any suitable storage device, such as a non-transitory computer-readable medium. The term “non-transitory,” as used herein, may correspond to a limitation of the medium itself (z.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., random access memory (RAM) vs. read-only memory (ROM)). A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory, and which may be processed by the processors, may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
[0071] Processors 911 and 921, memories 912 and 922, and any subset thereof, may be configured to provide means corresponding to the various blocks of FIGs. 6-7. Although not shown, the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors are also permitted, and may be configured to determine location, elevation, velocity, orientation, and so forth, such as barometers, compasses, and the like.
[0072] As shown in FIG. 9, transceivers 913 and 923 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 914 and 924. The device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple RATs. Other configurations of these devices, for example, may be provided. Transceivers 913 and 923 may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.
[0073] The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE, to perform any of the processes described above (z.e., FIGs. 6-7). Therefore, in certain example embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain example embodiments may be performed entirely in hardware.
[0074] In certain example embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIGs. 6- 7. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry), (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions), and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0075] FIG. 10 illustrates an example of a 5G network and system architecture according to certain example embodiments. Shown are multiple network functions that may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware. The NE and UE illustrated in FIG. 10 may be similar to NE 1010 and UE 1020, respectively. The user plane function (UPF) may provide services such as intra- RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of downlink packets, and/or triggering of downlink data notifications. The application function (AF) may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.
[0076] According to certain example embodiments, processors 911 and 921, and memories 912 and 922, may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 913 and 923 may be included in or may form a part of transceiving circuitry. [0077] In some example embodiments, an apparatus (e.g., NE 910 and/or UE 920) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and/or computer program code for causing the performance of the operations.
[0078] In various example embodiments, NE 910 may be controlled by memory 912 and processor 911 to transmit, to a user equipment, a control message comprising at least one preconfigured conditional handover; detect at least one setting associated with activation of at least one of the preconfigured conditional handovers; and transmit, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
[0079] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover; means for detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers; and means for transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
[0080] In various example embodiments, UE 920 may be controlled by memory 912 and processor 921 to receive, from a source network entity, a control message comprising at least one conditional handover preconfiguration; receive, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition; and execute, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
[0081] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration; means for receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition; and means for executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
[0082] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “various embodiments,” “certain embodiments,” “some embodiments,” or other similar language throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an example embodiment may be included in at least one example embodiment. Thus, appearances of the phrases “in various embodiments,” “in certain embodiments,” “in some embodiments,” or other similar language throughout this specification does not necessarily all refer to the same group of example embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.
[0083] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0084] Additionally, if desired, the different functions or procedures discussed above may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the description above should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.
[0085] One having ordinary skill in the art will readily understand that the example embodiments discussed above may be practiced with procedures in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although some embodiments have been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the example embodiments.
[0086] Partial Glossary
[0087] 3GPP 3rd Generation Partnership Project
[0088] 5G 5th Generation
[0089] 5GC 5th Generation Core
[0090] 6G 6th Generation
[0091] AF Application Function
[0092] AP Access Point
[0093] ASIC Application Specific Integrated Circuit
[0094] BS Base Station
[0095] CBSD Citizens Broadband Radio Service Device
[0096] CE Control Elements
[0097] CHO Conditional Handover
[0098] CN Core Network
[0099] CPU Central Processing Unit
[0100] CU Centralized Unit
[0101] dBm Decibel-milliwatts
[0102] DCI Downlink Control Information
[0103] DRX Discontinuous Reception
[0104] DU Distributed Unit
[0105] eMBB Enhanced Mobile Broadband [0106] eNB Evolved Node B
[0107] FR Frequency Range
[0108] gNB Next Generation Node B
[0109] GPS Global Positioning System
[0110] HDD Hard Disk Drive
[0111] HO Handover
[0112] HST High-Speed Train
[0113] loT Internet of Things
[0114] LI Layer 1
[0115] L3 Layer 3
[0116] LTE Long-Term Evolution
[0117JLTE-A Long-Term Evolution Advanced
[0118] MAC Medium Access Control
[0119] MAC CE Medium Access Control Control Element
[0120] MEMS Micro Electrical Mechanical System
[0121] MIMO Multiple Input Multiple Output
[0122] mMTC Massive Machine Type Communication
[0123] mmWave Millimeter Wave
[0124] NE Network Entity
[0125] NG Next Generation
[0126]NG-eNB Next Generation Evolved Node B
[0127JNG-RAN Next Generation Radio Access Network
[0128] NR New Radio
[0129] PDA Personal Digital Assistance
[0130] QoS Quality of Service
[0131] RAM Random Access Memory
[0132] RAN Radio Access Network
[0133] RAT Radio Access Technology
[0134] RE Resource Element
[0135] RF Radio Frequency [0136] ROM Read-Only Memory
[0137] RRC Radio Resource Control
[0138] RRH Remote Radio Head
[0139] RSRP Reference Signal Received Power
[0140] Rx Receive
[0141] SINR Signal to Interference & Noise Ratio
[0142] TCI Transmission Configuration Indicator
[0143] TRP Transmission Reception Point
[0144] Tx Transmit
[0145] UE User Equipment
[0146] UMTS Universal Mobile Telecommunications System
[0147] UPF User Plane Function
[0148JURLLC Ultra-Reliable and Low-Latency Communication
[0149JUTRAN Universal Mobile Telecommunications System
Terrestrial Radio Access Network

Claims

WE CLAIM:
1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: transmit, to a user equipment, a control message comprising at least one preconfigured conditional handover; detect at least one setting associated with activation of at least one of the preconfigured conditional handovers; and transmit, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
2. The apparatus of claim 1, wherein the control message comprises an indication that at least one of the preconfigured conditional handovers is usable after it is activated by the apparatus.
3. The apparatus of any of claims 1 or 2, wherein the control message comprises an indication that at least one of the preconfigured conditional handovers is usable after an additional condition is triggered.
4. The apparatus of claim 3, wherein the additional condition comprises the user equipment switching to at least one of the following: a particular transmission configuration indicator state or a particular transmission configuration indicator beam.
5. The apparatus of any of claims 1-4, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: continuously monitor for conditional handover.
6. The apparatus of any of claims 1 -5, wherein the indication to activate the conditional handover according to at least one of the preconfigured conditional handovers is transmitted via at least one of the following: downlink control information or at least one medium access control control element.
7. The apparatus of any of claims 1-6, wherein the control message comprises at least one of the following: a radio resource control setup message, radio resource control configuration message, or a radio resource control reconfiguration message.
8. The apparatus of any of claims 1-7, wherein the at least one mobility setting triggering condition is based upon network signaling or a preconfigured condition.
9. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a source network entity, a control message comprising at least one conditional handover preconfiguration; receive, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition; and execute, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
10. The apparatus of claim 9, wherein the at least one change triggering condition comprises a network-indicated change.
11. The apparatus of claim 9, wherein the at least one change triggering condition comprises a UE-initiated trigger.
12. The apparatus of any of claims 9-11, wherein the control message comprises an indication that the at least one conditional handover preconfiguration is usable after it is activated by the source network entity.
13. The apparatus of any of claims 9-12, wherein the control message comprises an indication that the at least one conditional handover preconfiguration is usable after an additional condition is triggered.
14. The apparatus of claim 13, wherein the additional condition comprises the apparatus switching to at least one of the following: a particular transmission configuration indicator state or a particular transmission configuration indicator beam.
15. The apparatus of claim 14, wherein the additional condition comprises a signal condition.
16. The apparatus of claim 15, wherein the signal condition comprises at least one of reference signal received power or reference signal received quality.
17. The apparatus of any of claims 9-16, wherein the indication to activate conditional handover is transmitted via at least one of the following: downlink control information or at least one medium access control control element.
18. The apparatus of any of claims 9-17, wherein the control message comprises at least one of the following: a radio resource control setup message, radio resource control configuration message, or a radio resource control reconfiguration message.
19. An apparatus comprising: means for transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover; means for detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers; and means for transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
20. The apparatus of claim 19, wherein the control message comprises an indication that at least one of the preconfigured conditional handovers is usable after it is activated by the apparatus.
21. The apparatus of any of claims 19 or 20, wherein the control message comprises an indication that at least one of the preconfigured conditional handovers is usable after an additional condition is triggered.
22. The apparatus of claim 21, wherein the additional condition comprises the user equipment switching to at least one of the following: a particular transmission configuration indicator state or a particular transmission configuration indicator beam.
23. The apparatus of any of claims 19-22, further comprising: means for continuously monitoring for conditional handover.
24. The apparatus of any of claims 19-23, wherein the indication to activate the conditional handover according to at least one of the preconfigured conditional handovers is transmitted via at least one of the following: downlink control information or at least one medium access control control element.
25. The apparatus of any of claims 19-24, wherein the control message comprises at least one of the following: a radio resource control setup message, radio resource control configuration message, or a radio resource control reconfiguration message.
26. The apparatus of any of claims 19-25, wherein the at least one mobility setting triggering condition is based upon network signaling or a preconfigured condition.
27. An apparatus comprising: means for receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration; means for receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition; and means for executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
28. The apparatus of claim 27, wherein the at least one change triggering condition comprises a network-indicated change.
29. The apparatus of claim 27, wherein the at least one change triggering condition comprises a UE-initiated trigger.
30. The apparatus of any of claims 27-29, wherein the control message comprises an indication that the at least one conditional handover preconfiguration is usable after it is activated by the source network entity.
31. The apparatus of any of claims 27-30, wherein the control message comprises an indication that the at least one conditional handover preconfiguration is usable after an additional condition is triggered.
32. The apparatus of claim 31, wherein the additional condition comprises the apparatus switching to at least one of the following: a particular transmission configuration indicator state or a particular transmission configuration indicator beam.
33. The apparatus of claim 32, wherein the additional condition comprises a signal condition.
34. The apparatus of claim 33, wherein the signal condition comprises at least one of reference signal received power or reference signal received quality.
35. The apparatus of any of claims 27-34, wherein the indication to activate conditional handover is transmitted via at least one of the following: downlink control information or at least one medium access control control element.
36. The apparatus of any of claims 27-35, wherein the control message comprises at least one of the following: a radio resource control setup message, radio resource control configuration message, or a radio resource control reconfiguration message.
37. A method comprising: transmitting, to a user equipment, a control message comprising at least one preconfigured conditional handover; detecting at least one setting associated with activation of at least one of the preconfigured conditional handovers; and transmitting, to the user equipment, in response to the detection, an indication configured to activate conditional handover according to at least one of the preconfigured conditional handovers.
38. The method of claim 37, wherein the control message comprises an indication that at least one of the preconfigured conditional handovers is usable after it is activated by the apparatus.
39. The method of any of claims 37 or 38, wherein the control message comprises an indication that at least one of the preconfigured conditional handovers is usable after an additional condition is triggered.
40. The method of claim 39, wherein the additional condition comprises the user equipment switching to at least one of the following: a particular transmission configuration indicator state or a particular transmission configuration indicator beam.
41. The method of any of claims 37-40, further comprising: continuously monitoring for conditional handover.
42. The method of any of claims 37-41, wherein the indication to activate the conditional handover according to at least one of the preconfigured conditional handovers is transmitted via at least one of the following: downlink control information or at least one medium access control control element.
43. The method of any of claims 37-42, wherein the control message comprises at least one of the following: a radio resource control setup message, radio resource control configuration message, or a radio resource control reconfiguration message.
44. The method of any of claims 34-43, wherein the at least one mobility setting triggering condition is based upon network signaling or a preconfigured condition.
45. A method comprising: receiving, from a source network entity, a control message comprising at least one conditional handover preconfiguration; receiving, from the source network entity, an indication configured to activate conditional handover according to the at least one conditional handover preconfiguration and at least one change triggering condition; and executing, based upon the received control message and received indication, conditional handover according to the at least one conditional handover preconfiguration.
46. The method of claim 45, wherein the at least one change triggering condition comprises a network-indicated change.
47. The method of claim 45, wherein the at least one change triggering condition comprises a UE-initiated trigger.
48. The method of any of claims 45-47, wherein the control message comprises an indication that the at least one conditional handover preconfiguration is usable after it is activated by the source network entity.
49. The method of any of claims 45-48, wherein the control message comprises an indication that the at least one conditional handover preconfiguration is usable after an additional condition is triggered.
50. The method of claim 49, wherein the additional condition comprises the apparatus switching to at least one of the following: a particular transmission configuration indicator state or a particular transmission configuration indicator beam.
51. The method of claim 50, wherein the additional condition comprises a signal condition.
52. The method of claim 51, wherein the signal condition comprises at least one of reference signal received power or reference signal received quality.
53. The method of any of claims 45-52, wherein the indication to activate conditional handover is transmitted via at least one of the following: downlink control information or at least one medium access control control element.
54. The method of any of claims 45-53, wherein the control message comprises at least one of the following: a radio resource control setup message, radio resource control configuration message, or a radio resource control reconfiguration message.
55. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method according to any of claims 37-54.
56. An apparatus comprising circuitry configured to perform a method according to any of claims 37-54.
57. A computer program comprising instructions, which, when executed by an apparatus, cause the apparatus to perform the method of any of claims 37-54.
PCT/US2022/044149 2022-09-20 2022-09-20 Preconfigured cho WO2024063760A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2022/044149 WO2024063760A1 (en) 2022-09-20 2022-09-20 Preconfigured cho

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2022/044149 WO2024063760A1 (en) 2022-09-20 2022-09-20 Preconfigured cho

Publications (1)

Publication Number Publication Date
WO2024063760A1 true WO2024063760A1 (en) 2024-03-28

Family

ID=83899806

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/044149 WO2024063760A1 (en) 2022-09-20 2022-09-20 Preconfigured cho

Country Status (1)

Country Link
WO (1) WO2024063760A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190223073A1 (en) * 2018-01-12 2019-07-18 FG Innovation Company Limited Conditional handover procedures
US20210377830A1 (en) * 2018-10-11 2021-12-02 Samsung Electronics Co., Ltd. Ue and base station in mobile communication system and operating method therefor
WO2022153255A1 (en) * 2021-01-14 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Procedural options for cho in non-terrestrial networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190223073A1 (en) * 2018-01-12 2019-07-18 FG Innovation Company Limited Conditional handover procedures
US20210377830A1 (en) * 2018-10-11 2021-12-02 Samsung Electronics Co., Ltd. Ue and base station in mobile communication system and operating method therefor
WO2022153255A1 (en) * 2021-01-14 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Procedural options for cho in non-terrestrial networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Conditional handover failures in LTE", vol. RAN WG2, no. Xi'an, China; 20190408 - 20190412, 28 March 2019 (2019-03-28), XP051693124, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F105bis/Docs/R2%2D1903888%2Ezip> [retrieved on 20190328] *

Similar Documents

Publication Publication Date Title
US11653276B2 (en) Apparatus and method in wireless communication system and computer readable storage medium
US11265749B2 (en) Device, method, and computer readable storage medium in wireless communication system
US10966271B2 (en) Connection setup recovery for wireless networks
TW202025811A (en) Method of measurement for layer-1 reference signal received power and user equipment thereof
US20210345211A1 (en) Timing advance for rach-less backhaul handover
TWI796458B (en) Wireless communication device, communication device and communication control method
US20210076226A1 (en) Wireless communication device, control device, and control method
US20200187035A1 (en) Measurement Reporting Prohibit Timer for Measurement of Signals Originating from Two Different Cells or Beams
JP2024512750A (en) Electronic equipment, communication methods, and storage media
US20240064598A1 (en) Radio Network Node, User Equipment, and Methods Performed Therein
US20230412257A1 (en) Neighbor low earth orbit/high altitude platform stations inter-satellite link change and synchronization signal block measurements
EP3157182B1 (en) Techniques for measurement filtering for wireless systems
US20230059284A1 (en) Facilitating explicit latency mode determination in beam switching
US20200245156A1 (en) Communication apparatus and communication method
WO2023122950A1 (en) Methods and apparatuses for mobility enhancements for uav
WO2021204250A1 (en) Method and network device for coverage enhancement
WO2024063760A1 (en) Preconfigured cho
WO2024065497A1 (en) Methods and apparatuses for receiving and sending configuration information, and readable storage medium
EP4346280A1 (en) Timing advance triggering measurement report for fr2 handover
US20240080727A1 (en) Measurement Adjustment in Low Mobility
US20230037650A1 (en) Enhanced multi-panel user equipment measurement for improved mobility robustness
US20240121732A1 (en) Timing advance loops
US20240214879A1 (en) Physical cell identity collision resolution for wireless networks
WO2024080964A1 (en) Link-based adaptation of synchronization signal physical broadcast channel block measurement timing configuration sharing
WO2023117054A1 (en) Reduced impact on positioning accuracy in telecommunications systems

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

Country of ref document: EP

Kind code of ref document: A1