Method and apparatus for synchronization signal block adaptation for mobility operations

By enabling dynamic SSB configuration switching based on explicit signaling, the UE adapts SSB measurements for improved downlink synchronization and measurement during mobility events, addressing inefficiencies in 5G NR systems and reducing mobility event failures.

WO2026235035A1PCT designated stage Publication Date: 2026-11-12SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/016595
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-07
Filing Date
2026-04-24
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems, particularly 5G NR, face challenges in optimizing synchronization signal block configurations for efficient mobility operations, leading to inefficiencies in downlink synchronization and measurement during mobility events.

Method used

The UE receives explicit signaling to switch between different SSB configurations, allowing for dynamic adaptation of SSB-based measurements during mobility procedures, including L1/L2 and L3 operations, by transitioning from an Always-On SSB configuration to an On-Demand SSB configuration based on network conditions.

Benefits of technology

This approach enhances the efficiency of downlink synchronization and measurement during mobility operations, reducing the failure rate of Layer-3 mobility events and improving overall network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026016595_12112026_PF_FP_ABST
    Figure JP2026016595_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method performed by a User Equipment (UE) for performing a Synchronization Signal Block (SSB) adaptation operation is provided. The method receives, from a Base Station (BS) via a serving cell, a Radio Resource Control (RRC) reconfiguration message including a first SSB configuration and a second SSB configuration for a candidate cell. The method receives, from the BS via the serving cell, an explicit signaling. In response to receiving the explicit signaling, the method changes a parameter for SSB-based measurement for a mobility procedure associated with the candidate cell from a first value to a second value. The method performs the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR SYNCHRONIZATION SIGNAL BLOCK ADAPTATION FOR MOBILITY OPERATIONS

[0001] The present disclosure relates to wireless communication, and in particular, to methods and apparatus for synchronization signal block adaptation for mobility operations.

[0002] Various efforts have been made to improve different aspects of wireless communication for the cellular wireless communication systems, such as the 5thGeneration (5G) New Radio (NR) system, by improving data rate, latency, reliability, and mobility. The 5G NR system is designed to provide flexibility and configurability to optimize network services and types, accommodating various use cases, such as enhanced Mobile Broadband (eMBB), massive Machine-Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC). As the demand for radio access continues to increase, however, there exists a need for further improvements in the art.

[0003] The present disclosure relates to wireless communication, and in particular, to methods and apparatus for synchronization signal block adaptation for mobility operations. The present disclosure provides mechanisms by which a UE may detect different Synchronization Signal Block (SSB) burst sets from a candidate cell based on different SSB configurations at different phases of a mobility operation, where switching between the SSB configurations may be triggered in response to reception of an explicit signaling, thereby facilitating efficient downlink synchronization and measurement throughout the mobility operation.

[0004] In a first aspect of the present disclosure, a UE for performing an SSB adaptation operation is provided. The UE includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The one or more computer-executable instructions, when executed by the at least one processor, cause the UE to: receive, from a Base Station (BS) via a serving cell, a Radio Resource Control (RRC) reconfiguration message including a first SSB configuration and a second SSB configuration for a candidate cell; receive, from the BS via the serving cell, an explicit signaling; in response to receiving the explicit signaling, change a parameter for SSB-based measurement for a mobility procedure associated with the candidate cell from a first value to a second value; and perform the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value.

[0005] In some implementations of the first aspect, the explicit signaling corresponds to the RRC reconfiguration message, a Medium Access Control (MAC) Control Element (CE), or an RRC signaling.

[0006] In some implementations of the first aspect, the MAC CE or the RRC signaling includes at least one of an SSB configuration index, an SSB-index bitmap indicating an activated or de-activated status of specific SSB blocks, or a parameter index associated with one or more pre-configured SSB parameters.

[0007] In some implementations of the first aspect, the parameter for SSB-based measurement includes at least one of an SSB position in a burst, an SSB periodicity, a system frame number (SFN) SSB offset, an SSB transmit power, an SSB sub-carrier spacing, or an SSB frequency.

[0008] In some implementations of the first aspect, the mobility procedure corresponds to a Layer-1 / Layer-2 (L1 / L2) mobility operation that includes at least one of a Layer-1 / Layer-2 Triggered Mobility (LTM), a conditional LTM, a subsequent LTM, an inter-Central Unit (CU) LTM, or an intra-CU LTM.

[0009] In some implementations of the first aspect, the mobility procedure corresponds to a Layer-3 (L3) mobility operation that includes at least one of a handover, a conditional handover, or a Dual-Active-Protocol-Stack (DAPS) handover.

[0010] In some implementations of the first aspect, changing the parameter for SSB-based measurement from the first value to the second value includes at least one of an activation of the second SSB configuration or a deactivation of the first SSB configuration.

[0011] In some implementations of the first aspect, the first SSB configuration is an Always-On SSB (AW-SSB) configuration, and the second SSB configuration is an On-Demand SSB (OD-SSB) configuration. In addition, performing the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value includes detecting an SSB burst set from the candidate cell based on a combination of the AW-SSB configuration and the OD-SSB configuration in at least one of a valid time period, a range in a frequency domain, or a power domain.

[0012] In some implementations of the first aspect, one of the first SSB configuration and the second SSB configuration is applied by the UE during a cell Discontinuous Transmission (DTX) non-active duration of the candidate cell and includes at least one of a long periodicity or a sparse SSB set pattern. In addition, the other one of the first SSB configuration and the second SSB configuration is applied by the UE during a cell DTX active duration of the candidate cell and includes at least one of a short periodicity or a dense SSB set pattern.

[0013] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: determine, based on the explicit signaling, that a cell Discontinuous Transmission (DTX) state of the candidate cell transitions from a non-active duration to an active duration or from the active duration to the non-active duration.

[0014] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: transmit an RRC reconfiguration complete message to the BS via the serving cell in response to receiving the RRC reconfiguration message, where the UE changes the parameter for SSB-based measurement from the first value to the second value upon transmitting the RRC reconfiguration complete message.

[0015] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: transmit a mobility completion message to the candidate cell in response to completing the mobility procedure, where the UE changes the parameter for SSB-based measurement from the first value to the second value upon transmitting the mobility completion message.

[0016] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: start a timer in response to receiving the explicit signaling, where the UE changes the parameter for SSB-based measurement from the first value to the second value upon expiration of the timer.

[0017] In a second aspect of the present disclosure, a BS for supporting an SSB adaptation operation is provided. The BS includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The one or more computer-executable instructions, when executed by the at least one processor, cause the BS to: transmit, to a UE via a serving cell, an RRC reconfiguration message including a first SSB configuration and a second SSB configuration for a candidate cell; and transmit, to the UE via the serving cell, an explicit signaling. In response to receiving the explicit signaling, the UE changes a parameter for SSB-based measurement for a mobility procedure associated with the candidate cell from a first value to a second value. The UE performs the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value.

[0018] In a third aspect of the present disclosure, a method performed by a UE for performing an SSB adaptation operation is provided. The method includes: receiving, from a BS via a serving cell, an RRC reconfiguration message including a first SSB configuration and a second SSB configuration for a candidate cell; receiving, from the BS via the serving cell, an explicit signaling; in response to receiving the explicit signaling, changing a parameter for SSB-based measurement for a mobility procedure associated with the candidate cell from a first value to a second value; and performing the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value.

[0019] Aspects of the present disclosure are best understood from the following detailed disclosure when read with the accompanying drawings. Various features are not drawn to scale. Dimensions of various features may be arbitrarily increased or reduced for clarity of discussion.

[0020] FIG. 1 is a schematic diagram illustrating SSB adaptation during an LTM operation according to a first mode (Mode 1) of operation, according to an example implementation of the present disclosure.

[0021] FIG. 2A is a schematic diagram illustrating SSB adaptation during an LTM operation according to a second mode (Mode 2) of operation, according to an example implementation of the present disclosure.

[0022] FIG. 2B is a schematic diagram illustrating SSB adaptation during an LTM operation according to a sub-mode (Mode 2a) of the second mode of operation, according to an example implementation of the present disclosure.

[0023] FIG. 3 is a schematic diagram illustrating SSB adaptation during a conditional LTM operation according to a third mode (Mode 3) of operation, according to an example implementation of the present disclosure.

[0024] FIG. 4 is a flowchart illustrating an implicit and explicit SSB adaptation mechanism at a UE side, according to an example implementation of the present disclosure.

[0025] FIG. 5 is a schematic diagram illustrating cross-layer SSB parameter adaptation at a UE side, according to an example implementation of the present disclosure.

[0026] FIG. 6A is a schematic diagram illustrating SSB configurations applied during a cell Discontinuous Transmission (DTX) active duration and a cell DTX non-active duration, according to an example implementation of the present disclosure.

[0027] FIG. 6B is a schematic diagram illustrating cell DTX adaptation in which a cell DTX active duration is inspired by an LTM configuration, according to an example implementation of the present disclosure.

[0028] FIG. 6C is a schematic diagram illustrating cell DTX adaptation in which a cell DTX active duration is interrupted by an LTM cell switch command, according to an example implementation of the present disclosure.

[0029] FIG. 7 is a schematic diagram illustrating SSB adaptation between an Always-On SSB (AW-SSB) configuration and an On-Demand SSB (OD-SSB) configuration during an LTM operation, according to an example implementation of the present disclosure.

[0030] FIG. 8A is a schematic diagram illustrating an example MAC CE structure with separate fields for SSB operation during an LTM procedure and SSB operation after LTM completion, according to an example implementation of the present disclosure.

[0031] FIG. 8B is a schematic diagram illustrating another example MAC CE structure with a field for an activated / de-activated SSB configuration during a mobility operation, according to an example implementation of the present disclosure.

[0032] FIG. 9 is a signaling flow diagram illustrating an LTM Serving Cell Switch (LTM SCS) procedure, according to an example implementation of the present disclosure.

[0033] FIG. 10 is a flowchart illustrating a method / process performed by a UE for SSB adaptation in connection with a mobility operation, according to an example implementation of the present disclosure.

[0034] FIG. 11 is a flowchart illustrating a method / process performed by a UE for SSB adaptation in connection with a Layer-3 handover or a conditional handover operation, according to an example implementation of the present disclosure.

[0035] FIG. 12 is a flowchart illustrating a method / process performed by a UE for SSB adaptation in connection with a Dual-Active-Protocol-Stack (DAPS) handover operation, according to an example implementation of the present disclosure.

[0036] FIG. 13 is a block diagram illustrating a node for wireless communication, according to an example implementation of the present disclosure.

[0037] Some of the abbreviations in the present application are defined as follows and, unless otherwise specified, the abbreviations have the following meanings: Abbreviation    Full name 3GPP      3rd Generation Partnership Project 6G        Sixth Generation AC        Additional Condition AI / ML      Artificial Intelligence / Machine Learning AM        Acknowledgement Mode / Acknowledged Mode ARFCN      Absolute Radio Frequency Channel Number AW-SSB      Always-On SSB BA        Bandwidth Adaptation BFD        Beam Failure Detection BFR        Beam Failure Recovery BM        Beam Management BS        Base Station BWP      Bandwidth Part CA        Carrier Aggregation CCCH      Common Control Channel CD-SSB      Cell-Defining SSB CE        Control Element   CHO      Conditional Handover CORESET    Control Resource Set CPAC      Conditional PSCell Addition or Change CPC        Conditional PSCell Change CQI        Channel Quality Indicator C-RNTI      Cell-Radio Network Temporary Identifier CSC        Cell Switch Command CSI        Channel State Information CSI-RS      Channel State Information-Reference Signal DAPS      Dual Active Protocol Stack DC        Dual Connectivity DCI        Downlink Control Information DL        Downlink DL-DCCH    Downlink-Dedicated Control Channel DRX      Discontinuous Reception DTX      Discontinuous Transmission FR        Frequency Range ID        Identifier / Identity IE        Information Elements L1        Layer-1 L2        Layer-2 L3        Layer-3 LBT        Listen Before Talk LCM      Life Cycle Management LTM      L1 / L2 Triggered Mobility MAC      Medium Access Control MAC CE      Medium Access Control Control Element MCG      Master Cell Group MCS      Modulation Coding Scheme MDT      Minimum Drive Test MIB        Master Information Block MIMO      Multiple Input Multiple Output NR        New Radio NW        Network NW-AC      Network-side Additional Condition NZP        Non-Zero-Power OD-SSB      On-Demand SSB PBCH      Physical Broadcast CHannel PCell      Primacy Cell PDCCH      Physical Downlink Control CHannel PDSCH      Physical Downlink Shared CHannel PHY      Physical Layer PRACH      Physical Random Access CHannel PUCCH      Physical Uplink Control CHannel PUSCH      Physical Uplink Shared CHannel RA        Random Access RAN      Radio Access Network RAR      Random Access Response RB        Resource Block RE        Resource Element Rel        Release RNTI      Radio Network Temporary Identifier RLC        Radio Link Control RLC-SAP    Radio Link Control - Service Access Point RLM      Radio Link Monitoring RRC      Radio Resource Control RRM      Radio Resource Management RSRP      Reference Signal Received Power RSRQ      Reference Signal Received Quality SCell      Secondary Cell SCG        Secondary Cell Group SCS        Serving Cell Switch S-CPAC      Subsequent Conditional PSCell Addition or Change SINR      Signal to Inference and Noise Ratio SNR        Signal to Noise Ratio SR        Scheduling Request SRB        Signaling Radio Bearer SS        Search Space SSB        Synchronization Signal Block TM        Transparent Mode UCI        Uplink Control Information UE        User Equipment UL        Uplink UL-DCCH    Uplink Dedicated Control Channel

[0038] The following contains specific information related to implementations of the present disclosure. The drawings and their accompanying detailed disclosure are merely directed to implementations. However, the present disclosure is not limited to these implementations. Other variations and implementations of the present disclosure will be obvious to those skilled in the art.

[0039] Unless noted otherwise, like or corresponding elements among the drawings may be indicated by like or corresponding reference numerals. Moreover, the drawings and illustrations in the present disclosure are generally not to scale and are not intended to correspond to actual relative dimensions.

[0040] For consistency and ease of understanding, like features may be identified (although, in some examples, not illustrated) by the same numerals in the drawings. However, the features in different implementations may be different in other respects and shall not be narrowly confined to what is illustrated in the drawings.

[0041] References to “one implementation,” “an implementation,” “example implementation,” “various implementations,” “some implementations,” “implementations of the present application,” etc., may indicate that the implementation(s) of the present application so described may include a particular feature, structure, or characteristic, but not every possible implementation of the present application necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “in one implementation,” or “in an example implementation,” “an implementation,” do not necessarily refer to the same implementation, although they may. Moreover, any use of phrases like “implementations” in connection with “the present application” are never meant to characterize that all implementations of the present application must include the particular feature, structure, or characteristic, and should instead be understood to mean “at least some implementations of the present application” includes the stated particular feature, structure, or characteristic.

[0042] The term “coupled” is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to physical connections. The term “comprising,” when utilized, means “including, but not necessarily limited to”; it specifically indicates open-ended inclusion or membership in the so-described combination, group, series, and the equivalent.

[0043] The expression “at least one of A, B and C” or “at least one of the following: A, B and C” means “only A, or only B, or only C, or any combination of A, B and C.” The terms “system” and “network” may be used interchangeably. The term “and / or” is only an association relationship for describing associated objects and represents that three relationships may exist such that A and / or B may indicate that A exists alone, A and B exist at the same time, or B exists alone. The character “ / ” generally represents that the associated objects are in an “or” relationship.

[0044] For the purposes of explanation and non-limitation, specific details, such as functional entities, techniques, protocols, and standards, are set forth for providing an understanding of the disclosed technology. In other examples, detailed disclosure of well-known methods, technologies, systems, and architectures are omitted so as not to obscure the present disclosure with unnecessary details.

[0045] Persons skilled in the art will immediately recognize that any network function(s) or algorithm(s) disclosed may be implemented by hardware, software, or a combination of software and hardware. Disclosed functions may correspond to modules which may be software, hardware, firmware, or any combination thereof.

[0046] A software implementation may include computer executable instructions stored on a computer-readable medium, such as memory or other type of storage devices. One or more microprocessors or general-purpose computers with communication processing capability may be programmed with corresponding executable instructions and perform the disclosed network function(s) or algorithm(s).

[0047] The microprocessors or general-purpose computers may include Application-Specific Integrated Circuits (ASICs), programmable logic arrays, and / or one or more Digital Signal Processor (DSPs). Although some of the disclosed implementations are oriented to software installed and executing on computer hardware, alternative implementations implemented as firmware, as hardware, or as a combination of hardware and software are well within the scope of the present disclosure. The computer-readable medium includes but is not limited to Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory, Compact Disc Read-Only Memory (CD-ROM), magnetic cassettes, magnetic tape, magnetic disk storage, or any other equivalent medium capable of storing computer-readable instructions.

[0048] A radio communication network architecture such as a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a 5G NR Radio Access Network (RAN) typically includes at least one base station (BS), at least one UE, and one or more optional network elements that provide connection within a network. The UE communicates with the network such as a Core Network (CN), an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial RAN (E-UTRAN), a 5G Core (5GC), or an internet via a RAN established by one or more BSs.

[0049] A UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. The UE may be a portable radio equipment that includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, or a Personal Digital Assistant (PDA) with wireless communication capability. The UE is configured to receive and transmit signals over an air interface to one or more cells in a RAN. A UE may be referred to as a PHY / MAC / RLC / PDCP / SDAP entity. The PHY / MAC / RLC / PDCP / SDAP entity may be referred to as the UE.

[0050] The BS may be configured to provide communication services according to at least a Radio Access Technology (RAT) such as Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM) that is often referred to as 2G, GSM Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunication System (UMTS) that is often referred to as 3G based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), LTE, LTE-A, evolved LTE (eLTE) that is LTE connected to 5GC, NR (often referred to as 5G), and / or LTE-A Pro. However, the scope of the present disclosure is not limited to these protocols.

[0051] The BS may include, but is not limited to, a node B (NB) in the UMTS, an evolved node B (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in the GSM / GERAN, an ng-eNB in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS in connection with 5GC, a next generation Node B (gNB) in the 5G-RAN, or any other apparatus capable of controlling radio communication and managing radio resources within a cell. The BS may serve one or more UEs via a radio interface.

[0052] The BS may be operable to provide radio coverage to a specific geographical area using multiple cells forming the RAN. The BS may support the operations of the cells. Each cell may be operable to provide services to at least one UE within its radio coverage.

[0053] A software implementation of the technical solutions provided in the present disclosure may include computer-executable instructions and / or Artificial Intelligence (AI) / Machine Learning (ML) module(s) stored on a computer-readable medium, such as a memory or other type of storage devices. One or more microprocessors or general-purpose computers with communication processing capability may be programmed with the corresponding computer-executable instructions and may perform the disclosed network function(s), AI / ML module(s), or algorithm(s). The AI / ML module(s) may be implemented with a supervised learning approach, a semi-supervised learning approach, an unsupervised learning approach (e.g., a Transductive approach and an Inductive approach), a federated learning approach, or a Reinforcement Learning (RL) approach, but the present disclosure is not limited thereto. The computer-executable instructions associated with the AI module(s) and / or the ML module(s) may include but are not limited to, data management instructions (e.g., collection instructions, validation instructions, etc.), model monitoring and management instructions (e.g., network (NW) Key Performance Indicators (KPIs) monitoring, model input / output monitoring, model selection / switching / update / upload / download, model (de)activation, model identification, functionality selection, etc.), and / or pre-process input instructions.

[0054] In some implementations, the UE may be an AI / ML-enabled device and / or an AI / ML capable device that may be equipped with AI module(s) and / or ML module(s).

[0055] In some implementations, the BS may be an AI / ML-enabled device and / or an AI / ML capable device that may be equipped with AI module(s) and / or ML module(s).

[0056] Each cell (often referred to as a serving cell) may provide services to serve one or more UEs within its radio coverage, such that each cell schedules the DL (and optionally UL resources) to at least one UE within its radio coverage for DL (and optionally UL packet transmissions from the UE). The BS may communicate with one or more UEs in the radio communication system via the multiple cells.

[0057] A cell may allocate sidelink (SL) resources for supporting the Proximity Service (ProSe) or Vehicle to Everything (V2X) service. Each cell may have overlapped coverage areas with other cells.

[0058] In Multi-RAT Dual Connectivity (MR-DC) cases, the primary cell of a Master Cell Group (MCG) or a Secondary Cell Group (SCG) may be referred to as a Special Cell (SpCell). A Primary Cell (PCell) may include the SpCell of an MCG. A Primary SCG Cell (PSCell) may include the SpCell of an SCG. MCG may include a group of serving cells associated with the Master Node (MN), including the SpCell and optionally one or more Secondary Cells (SCells). An SCG may include a group of serving cells associated with the Secondary Node (SN), including the SpCell and optionally one or more SCells.

[0059] As described above, the frame structure for NR supports flexible configurations for accommodating various next generation (e.g., 5G) communication requirements, such as Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), while fulfilling high reliability, high data rate, and low latency requirements. The Orthogonal Frequency-Division Multiplexing (OFDM) technology in the 3GPP may serve as a baseline for an NR waveform. The scalable OFDM numerology, such as adaptive sub-carrier spacing, channel bandwidth, and Cyclic Prefix (CP), may also be used.

[0060] Two coding schemes may be considered for NR, specifically Low-Density Parity-Check (LDPC) code and Polar Code. The coding scheme adaption may be configured based on channel conditions and / or service applications.

[0061] At least the DL transmission data, a guard period, and UL transmission data should be included in a transmission time interval (TTI) of a single NR frame. The respective portions of the DL transmission data, the guard period, and the UL transmission data should also be configurable based on, for example, the network dynamics of NR. SL resources may also be provided in an NR frame to support ProSe services or V2X services.

[0062] Any two or more of the following paragraphs, (sub)-bullets, points, actions, behaviors, terms, or claims described in the present disclosure may be combined logically, reasonably, and properly to form a specific method.

[0063] Any sentence, paragraph, (sub)-bullet, point, action, behaviors, terms, or claims described in the present disclosure may be implemented independently and separately to form a specific method.

[0064] Dependency, e.g., “based on”, “more specifically”, “preferably”, “in one embodiment”, “in some implementations”, etc., in the present disclosure is just one possible example which would not restrict the specific method.

[0065] “A and / or B” in the present disclosure may refer to either A or B, both A and B, or at least one of A and B.

[0066] In this disclosure, “X / Y” may encompass the meanings of “X or Y,” “X and Y,” and “X and / or Y,” as indicated by two or more of the sentences, paragraphs, sub-bullets, points, actions, behaviors, terms, alternatives, aspects, examples, embodiments, or claims described in the following invention(s).

[0067] One aspect of the present disclosure may be applied in various contexts, including communications, communication equipment (such as mobile telephone apparatus, base station apparatus, wireless LAN apparatus, and / or sensor devices), integrated circuits (such as communication chips), and software programs, among others.

[0068] The terms “an antenna port” and “antenna ports,” as discussed in the present disclosure, may refer to “an antenna port used for transmission of PUSCH(s) / PUCCH(s)” and “antenna ports used for transmission of PUSCH(s) / PUCCH(s),” respectively.

[0069] Some of the terms, definitions, and / or abbreviations included in the present disclosure may either be sourced from existing documents (such as those from ETSI, ITU, or other sources) or may be newly created by experts from the 3GPP whenever there was a need for a precise vocabulary.

[0070] In the present disclosure, although the term “gNB” may have been used throughout the document, it should be understood that the term “gNB” may be replaced by any other type of BS (e.g., an eNB). Multiple PLMNs may operate on the unlicensed spectrum. Multiple PLMNs may share the same unlicensed carrier. The PLMNs may be public or private. Public PLMNs may include the operators or virtual operators, which may provide radio services to the public subscribers. Public PLMNs may own the licensed spectrum and may support the radio access technology on the licensed spectrum as well. Private PLMNs may include the micro-operators, factories, or enterprises, which may provide radio services to the private users (e.g., employees or machines). In some implementations, public PLMNs may support more deployment scenarios, such as carrier aggregation between licensed band NR (PCell) and NR-U (SCell), dual connectivity between licensed band LTE (PCell) and NR-U (PSCell), stand-alone NR-U, an NR cell with DL in unlicensed band and UL in licensed band, and dual connectivity between licensed band NR (PCell) and NR-U (PSCell). In some implementations, private PLMNs may mainly support the stand-alone unlicensed radio access technology (e.g., stand-alone NR-U).

[0071] Additionally, in the present disclosure, the term “reference signal” may broadly encompass various types of signals. When referring to “the sequence of signals” or “the sequence of reference signals,” these terms may be used interchangeably. The reference signal may be used for measurement, synchronization, and / or cell identification purposes. The reference signal may include, but may not be limited to, synchronization signals, discovery signals, tracking signals, measurement signals, pilot signals, beacon signals, or any other signals that may be transmitted by the cell for the UE to detect, measure, and / or decode. In some implementations, the reference signal may refer to any signal that may enable the UE to identify whether a cell may support AI / ML features, 6G and beyond RAT, or specific AI / ML use cases. The reference signal may also include composite signals that may combine multiple signal types or signal components for enhanced detection and measurement capabilities. Furthermore, the reference signal may include both periodic signals and aperiodic signals, where the periodic signals may be transmitted at regular intervals and the aperiodic signals may be transmitted based on specific triggers or conditions. The flexibility in signal types may allow the network to optimize the signaling overhead while providing sufficient information for AI / ML-capable UEs to perform efficient cell selection and reselection procedures.

[0072] Examples of some selected terms in the present disclosure are provided as follows.

[0073] The network, cell, camped cell, serving cell, base station, gNB, eNB and ng-eNB may be used interchangeably. In some implementations, some of these items may refer to the same network entity.

[0074] The RAT may include NR, LTE, E-UTRA connected to 5GC, LTE connected to 5GC, E-UTRA connected to EPC, LTE connected to EPC, and 6G RAT. The proposed mechanism may be applied for UEs in public networks, or in private networks, e.g., NPN, SNPN, or PNI-NPN.

[0075] The proposed mechanism may be used for licensed frequency and / or unlicensed frequency.

[0076] System information may refer to MIB, SIB1, and other SI. Minimum SI may include MIB and SIB1. Other SI may refer to SIB3, SIB4, SIB5, and other SIBs.

[0077] Dedicated signaling may refer to (but not limited to) RRC message(s). For example, RRC (Connection) Setup Request message, RRC (Connection) Setup message, RRC (Connection) Setup Complete message, RRC (Connection) Reconfiguration message, RRC Connection Reconfiguration message including the mobility control information, RRC Connection Reconfiguration message without the mobility control information inside, RRC Reconfiguration message including the configuration with sync, RRC Reconfiguration message without the configuration with sync inside, RRC (Connection) Reconfiguration Complete message, RRC (Connection) Resume Request message, RRC (Connection) Resume message, RRC (Connection) Resume Complete message, RRC (Connection) Reestablishment Request message, RRC (Connection) Reestablishment message, RRC (Connection) Reestablishment Complete message, RRC (Connection) Reject message, RRC (Connection) Release message, RRC System Information Request message, UE Assistance Information message, UE Capability Enquiry message, and UE Capability Information message. The RRC_CONNECTED UE, RRC_INACTIVE UE, and RRC_IDLE UE may apply the proposed implementations.

[0078] The UE may be served by a cell, e.g., a serving cell. The serving cell may serve an RRC_CONNECTED UE. The serving cell may be a suitable cell.

[0079] The PCell may be the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0080] The PSCell may be, for dual connectivity operation, the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure.

[0081] For a UE in RRC_CONNECTED not configured with CA / DC, there may be only one serving cell including the primary cell. For a UE in RRC_CONNECTED configured with CA / DC, the serving cells may be used to denote the set of cells including the Special Cell and all secondary cells.

[0082] The Secondary Cell may be, for a UE configured with CA, a cell providing additional radio resources on top of the Special Cell.

[0083] The Special Cell may refer to the PCell of the MCG or the PSCell of the SCG for Dual Connectivity operation, otherwise the Special Cell may refer to the PCell.

[0084] The serving cell, TRP associated with the PCI of the serving cell, TRP associated with the serving cell, TRP of a serving cell and TRP of the serving cell may be applied interchangeably.

[0085] The target cell, target serving cell, TRP associated with a PCI different from the PCI of the serving cell, and TRP associated with the target cell may be applied interchangeably. A target serving cell may be identified by a PCI or a PCI index. A UE may be configured with at most 1, 4, 8, or 32 PCI indices. Each PCI index may identify a target serving cell of the UE.

[0086] The candidate cell, neighboring cell and candidate target cell may be applied interchangeably.

[0087] The serving cell in the implementations may be a PCell, SCell or PSCell.

[0088] The target cell in the implementations may be a PCell, SCell or PSCell.

[0089] An inter-cell to the serving cell of the UE may be a neighboring cell, a cell other than the serving cell or a cell with PCI different from the PCI of the serving cell. If the UE can perform the inter-cell beam management, the UE may be in coverage of the inter-cell.

[0090] The reference signal may refer to SSB, CSI-RS, TRS, PT-RS, SRS, and DM-RS.

[0091] A timer may be running once the timer is started, until the timer is stopped or until the timer expires; otherwise the timer may not be running. A timer may be started if the timer is not running or restarted if the timer is running. A timer may always be started or restarted from the initial value of the timer. The duration of a timer may not be updated until the timer is stopped or expires, e.g., due to BWP switching. When the MAC entity applies zero value for a timer, the timer may be started and immediately expire unless explicitly stated otherwise.

[0092] An ML model may be a manageable representation of an ML model algorithm. An ML model algorithm may be a mathematical algorithm through which running a set of input data can generate a set of inference output. An ML model may include metadata. Metadata may include, e.g., information related to the trained model, and applicable runtime context.

[0093] ML model training may be a process performed by an ML training function to take training data, run the training data through an ML model algorithm, derive the associated loss and adjust the parameterization of that ML model iteratively based on the computed loss and generate the trained ML model.

[0094] ML model initial training may be a process of an initial version of an ML model.

[0095] ML model re-training may be a process of training a previous version of an ML model and generating a new version. A new version of a trained ML model may support the same type of inference as the previous version of the ML model, where the data type of inference input and data type of inference output may remain unchanged between the two versions of the ML model, but parameter values may be different for the re-trained model.

[0096] ML model joint training may be a process of training a group of ML models.

[0097] An ML training function may be a logical function with ML model training capabilities.

[0098] ML model testing may be a process of testing an ML model using testing data.

[0099] An ML testing function may be a logical function with ML model testing capabilities.

[0100] AI / ML inference may be a process of running a set of input data through a trained ML model to produce a set of output data, such as predictions. The inference may represent the process to realize the AI capabilities by utilizing a trained ML model and other AI enablers if needed, hence the AI / ML prefix may be used when referring to inference as compared to training and testing.

[0101] An AI / ML inference function may be a logical function that may employ trained ML models to conduct inference.

[0102] AI / ML inference emulation may be running the inference process to evaluate the performance of an ML model in an emulation environment before deploying the ML model into the target environment.

[0103] ML model deployment may be a process of making a trained ML model available for use in the target environment.

[0104] A Network-side AI / ML model may be an AI / ML Model whose inference may be performed entirely at the network.

[0105] A UE-side AI / ML model may be an AI / ML Model whose inference may be performed entirely at the UE.

[0106] A Two-sided AI / ML model may be paired AI / ML Models over which joint inference may be performed, where joint inference may include AI / ML Inference whose inference may be performed jointly across the UE and the network, where the first part of inference may be firstly performed by the UE and then the remaining part may be performed by the gNB, or vice versa.

[0107] A UE supporting AI / ML features may support at least one of AI / ML use cases. A UE supporting a specific AI / ML use case may be supposed to support AI / ML features.

[0108] A cell supporting AI / ML features may support at least one of AI / ML use cases. A cell supporting a specific AI / ML use case may be supposed to support AI / ML features.

[0109] The present disclosure provides Synchronization Signal Block (SSB) adaptation designs that may be used in connection with a Layer-1 / Layer-2 Triggered Mobility (LTM) operation. In some communication systems, to facilitate Network Energy Saving (NES), a base station may broadcast a synchronization signal burst set (SSB set) periodically with a long periodicity or as a sparse SSB set. Under some additional conditions, the SSB set broadcasting may be muted or absent. For example, the SSB set broadcasting may be muted or absent when the loading of a cell is zero. To support a mobile UE in such NES-related deployments, the RAN may activate or de-activate the SSB set broadcasting, or may adjust one or more parameters of the SSB broadcasting, so that the UE may implement downlink (DL) and / or uplink (UL) early synchronization and / or Layer-1 / Layer-3 (L1 / L3) measurement during a mobility operation. By providing such SSB adaptation, the present disclosure may help reduce the failure rate of a Layer-3 (L3) mobility event (e.g., a handover, a conditional handover, or a Dual-Active-Protocol-Stack (DAPS) procedure) and a Layer-1 (L1) mobility event (e.g., LTM).

[0110] For ease of explanation, certain example implementations described herein are explained based on a Layer-1 / Layer-2 Triggered Mobility (LTM) operation. The proposed SSB adaptation, however, may also be applicable during and after another type of mobility operation. For example, the proposed SSB adaptation may be applied to an L3 mobility event such as a handover, a conditional handover, or a DAPS handover. To apply the proposed mechanism to an L3 mobility operation, an "LTM candidate" described in the present disclosure may be replaced by a target cell. For example, the LTM candidate configuration may be replaced by a Radio Resource Control (RRC) reconfiguration message that includes one or more candidates for the (conditional) handover. The LTM cell switch command MAC Control Element (CE) may optionally be replaced by an RRC reconfiguration message that includes a handover command to the UE. During a conditional handover procedure, the UE may initiate the handover procedure based on one or more pre-configured initiation events, such that the handover command may be absent in the RRC reconfiguration message. The LTM cell switch completion message may be replaced by an RRC reconfiguration complete message transmitted by the UE. The proposed SSB adaptation may further be applicable to both LTM operations and conditional LTM operations.

[0111] The present disclosure proposes an SSB adaptation solution to support a unified mobility solution. In some implementations, the UE may receive multiple SSB configurations from the serving RAN. During a mobility operation, the UE may perform early DL / UL synchronization and L1 / L3 measurement with an LTM candidate cell based on a first SSB configuration associated with the LTM candidate cell among the multiple SSB configurations. The UE may receive an explicit signaling indicating de-activation of the first SSB configuration, activation of a second SSB configuration, or both. After receiving the explicit signaling, the UE may determine, based on the received explicit signaling, whether to de-activate the first SSB configuration and whether to activate the second SSB configuration. The UE may perform DL / UL synchronization and L1 / L3 measurement based on the second SSB configuration and an SMTC configuration according to the determination made by the UE. The explicit signaling in the present disclosure may include, but is not limited to, a MAC CE or an RRC signaling.

[0112] In some implementations, the UE may switch from the first SSB configuration to the second SSB configuration upon transmitting an LTM cell switch completion message to a candidate cell of the mobility operation. In such implementations, the LTM cell switch command may include the explicit signaling for de-activating the first SSB configuration and activating the second SSB configuration. In some implementations, the UE may switch from the first SSB configuration to the second SSB configuration upon transmitting an RRCReconfigurationComplete message to the source cell or to a candidate cell of the mobility operation. In some implementations, the first SSB configuration and the second SSB configuration may be jointly activated, and the UE may perform DL / UL synchronization and L1 / L3 measurement by jointly measuring the first SSB configuration and the second SSB configuration in frequency domain and time domain.

[0113] The first SSB configuration and the second SSB configuration may be configured by the serving RAN, and the first SSB configuration and the second SSB configuration may be associated with different parameters. For example, the first SSB configuration and the second SSB configuration may be respectively configured by the source cell and by the LTM candidate, or may be jointly configured by the LTM candidate. The different parameters may include at least one of ssb-PositionsInBurst, ssb-periodicity, sfn-SSB-Offset, ss-PBCH-BlockPower, or ssb-Freq. The mobility operation may be an L1 mobility operation or an L3 mobility operation. For example, the L1 mobility operation may be a Layer-1 or Layer-2 Triggered Mobility (LTM) operation, a conditional LTM operation, a subsequent LTM operation, an inter-CU LTM operation, or an intra-CU LTM operation. For example, the L3 mobility operation may be a handover operation, a conditional handover operation, or a Dual-Active-Protocol-Stack (DAPS) handover operation.

[0114] The implementations described in the present disclosure are provided as illustrative examples, and variations, modifications, and alternative implementations are possible without departing from the scope of the present disclosure.

[0115] Mode 1

[0116] Reference is made to FIG. 1. FIG. 1 is a schematic diagram illustrating an SSB adaptation 100 during an LTM operation according to a first mode (Mode 1) of operation, according to an example implementation of the present disclosure. In Mode 1, the SSB broadcasting pattern of the candidate cell may transition from a first SSB configuration to a second SSB configuration upon or after the LTM cell switch operation is considered completed. The transition may be implemented implicitly, in the sense that the UE and the candidate cell may align on the timing of the transition without requiring an explicit signaling exchange dedicated to the SSB switch. For example, the UE may infer the timing of the SSB configuration switch based on a procedural event (e.g., transmission of an LTM cell switch completion message), without receiving a separate per-event MAC CE or RRC indication that explicitly designates the SSB configuration to be applied. By contrast, an explicit SSB adaptation may rely on a dedicated indication carried in a MAC CE or RRC message that identifies the SSB configuration to be applied.

[0117] In some implementations of the SSB adaptation 100 of FIG. 1, the UE may be pre-configured with one or more SSB configurations during LTM preparation. For example, the one or more SSB configurations may include an SSB#1 configuration and / or an SSB#2 configuration, and the one or more SSB configurations may be configured to the UE as part of an LTM configuration or a conditional LTM configuration. In some implementations, the one or more SSB configurations may be associated with a single LTM candidate. For example, the one or more SSB configurations may be provided under an LTM-candidate configuration corresponding to the single LTM candidate. In some implementations, the one or more SSB configurations may be common to or shared by multiple LTM candidates. For example, the same SSB#1 configuration may be applicable to a group of LTM candidates that operate on the same frequency carrier or share the same beam-direction pattern. The above-described implementations of the association between the one or more SSB configurations and the one or more LTM candidates are provided as illustrative examples, and may be used individually or in any combination depending on the deployment configuration of the candidate cell.

[0118] After the UE receives the (conditional) LTM configuration from the serving cell, the UE may implement early downlink / uplink (DL / UL) synchronization and / or Layer-1 / Layer-3 (L1 / L3) measurements towards all or a subset of the LTM candidates configured by the (conditional) LTM configuration. In some implementations, the UE may report L1 / L3 measurement reports to the serving RAN. For example, the L1 / L3 measurement reports may be reported as part of an LTM measurement report procedure, which is described in further detail in the context of FIG. 9. In addition, the UE may receive at least one LTM cell switch command (CSC) MAC CE, which may also be referred to as an LTM serving cell switch (SCS) MAC CE, from the serving RAN. The LTM CSC MAC CE may instruct the UE to implement an LTM operation associated with one LTM candidate. For example, the LTM CSC MAC CE may instruct the UE to implement an LTM operation associated with an LTM candidate#1 as shown in FIG. 1. Upon receiving the LTM CSC MAC CE, the UE may trigger the LTM operation. For example, the UE may trigger the LTM operation by initiating a random access procedure and / or by performing a data transmission. The UE may then complete the LTM operation accordingly.

[0119] As shown in FIG. 1, the LTM candidate#1 may broadcast a first SSB set, denoted as “SSB#1 Broadcasting” in FIG. 1, periodically based on the first SSB configuration (e.g., the SSB#1 configuration). In addition, the LTM candidate#1 may change or switch the SSB set broadcasting from the SSB#1 configuration to a second SSB configuration (e.g., the SSB#2 configuration) to broadcast a second SSB set, denoted as “SSB#2 Broadcasting” in FIG. 1, after the LTM operation is successfully completed from the perspective of the LTM candidate. For example, the LTM operation may be considered successfully completed from the perspective of the LTM candidate after the LTM candidate#1 receives a first packet transmission from the UE successfully, or after the LTM candidate#1 receives an RRC reconfiguration complete message from the UE successfully. The first packet transmission may, for example, include a UL data packet carrying user data, an RRC reconfiguration complete message, or another type of UL transmission that the LTM candidate may decode successfully.

[0120] The relative periodicity between the SSB#1 configuration and the SSB#2 configuration may take various forms, and several illustrative forms are described below. In some implementations, the periodicity of the SSB#2 configuration (e.g., the periodicity of the SSB burst set associated with the SSB#2 configuration) may be longer than the periodicity of the SSB#1 configuration. For example, the SSB#2 configuration may be used to support a network energy saving deployment in which the LTM candidate, after becoming a serving cell of the UE, may broadcast the SSB set less frequently to reduce energy consumption. In some implementations, the periodicity of the SSB#2 configuration (e.g., a parameter such as ssb-periodicity) may be shorter than the periodicity of the SSB#1 configuration. For example, the SSB#2 configuration may be used in a deployment in which the LTM candidate, after becoming a serving cell of the UE, may broadcast the SSB set more frequently to support enhanced beam tracking, beam refinement, or measurement reporting. The above-described two implementations of the relative periodicity are provided as illustrative examples, and the SSB#1 configuration and the SSB#2 configuration may have any relative periodicity relationship that satisfies the deployment requirement.

[0121] From the perspective of the UE, the UE may consider the SSB#1 configuration to be deactivated and the SSB#2 configuration to be activated by the serving RAN after the UE transmits an LTM cell switch completion message to the candidate cell or to the target cell. The SSB adaptation may be considered to be implemented implicitly, in the sense that the UE may determine the timing of the SSB adaptation in connection with the transmission of the LTM cell switch completion message rather than relying on an explicit per-event SSB activation / de-activation indication. In some implementations, the UE may consider the SSB adaptation to be implemented automatically upon or after the UE transmits the LTM cell switch completion message (e.g., an RRC reconfiguration complete message) to the LTM candidate. For example, transmitting the LTM cell switch completion message to the LTM candidate may serve as a trigger event from the perspective of the UE for switching from the SSB#1 configuration to the SSB#2 configuration. In some implementations, the UE may consider the SSB adaptation to be implemented automatically upon or after the UE transmits the LTM cell switch completion message (e.g., an RRC reconfiguration complete message) to the serving cell. For example, transmitting the RRC reconfiguration complete message to the serving cell upon receipt of the LTM configuration may serve as a trigger event from the perspective of the UE for switching from the SSB#1 configuration to the SSB#2 configuration. The above-described implementations regarding the recipient of the LTM cell switch completion message are independently valid, and the specific implementation may be selected based on the deployment configuration and the procedural step at which the SSB adaptation is intended to take effect.

[0122] In some implementations, the UE may apply an additional Synchronization Signal / Physical Broadcast Channel Block Measurement Timing Configuration (SMTC) associated with the SSB#1 configuration while the UE is monitoring or detecting the SSB#1 configuration for synchronization and / or measurement. For example, the additional SMTC configuration may be configured to the UE by the LTM candidate. The additional SMTC configuration may indicate measurement timing, periodicity, and offset parameters that the UE may use to align the measurement window with the SSB transmission instances of the LTM candidate.

[0123] The actions illustrated in FIG. 1 may be used to characterize the SSB adaptation 100 from the perspective of both the serving RAN and the UE. In action 102, the serving RAN may transmit an LTM (candidate) configuration to the UE, and the UE may transmit a response to the serving RAN. For example, the LTM (candidate) configuration may be transmitted via an RRC reconfiguration message that includes one or more LTM candidates and one or more associated SSB configurations of each LTM candidate, and the response may be transmitted via an RRC reconfiguration complete message acknowledging receipt of the LTM (candidate) configuration. In action 104, the UE may track an activation status of the LTM candidate#1 over time. For example, after the UE receives the LTM candidate configuration that includes the LTM candidate#1, the UE may consider the LTM candidate#1 as activated, such that the UE may begin to perform early DL / UL synchronization and / or L1 / L3 measurement towards the LTM candidate#1. The activation status may be maintained by the UE as an internal state indicator, and the UE may, for example, use the activation status to determine whether to perform measurement and synchronization procedures towards the LTM candidate#1 prior to the LTM cell switch operation. In action 106, the serving RAN may transmit an LTM SCS MAC CE to the UE. For example, the LTM SCS MAC CE may include a target configuration ID that indicates the index of the candidate configuration of the LTM candidate#1, and the LTM SCS MAC CE may instruct the UE to switch to the LTM candidate#1 as a new serving cell. In action 108, the UE may complete the LTM cell switch operation. For example, the UE may transmit an LTM cell switch completion message (e.g., an RRC reconfiguration complete message) to the LTM candidate#1 to indicate the completion of the LTM cell switch operation, or the LTM candidate#1 may consider the LTM cell switch operation as completed upon successful reception of a first packet transmission from the UE. As further shown in FIG. 1, the SSB#1 Broadcasting may be performed by the LTM candidate#1 from a time prior to action 102 and may continue until action 108. After action 108, the LTM candidate#1 may switch to the SSB#2 Broadcasting based on the SSB#2 configuration.

[0124] The mechanism illustrated in FIG. 1 may also be applicable to a (conditional) handover procedure (i.e., a Layer-3 mobility operation). To apply the mechanism of FIG. 1 to a Layer-3 mobility operation based on FIG. 1: in some implementations, the LTM candidate configuration may be replaced by an RRC reconfiguration message that includes one or more candidates for (conditional) handover; in some implementations, the LTM SCS MAC CE may optionally be replaced by an RRC reconfiguration message that includes a handover command to the UE, where during a conditional handover procedure the UE may initiate the handover procedure based on one or more pre-configured initiation events such that the handover command may be absent in the RRC reconfiguration message; and in some implementations, the LTM cell switch completion message may be replaced by an RRC reconfiguration complete message transmitted by the UE.

[0125] The Mode 1 SSB adaptation operation described above may provide certain technical effects. For example, the Mode 1 SSB adaptation operation may enable the LTM candidate cell to switch the SSB broadcasting pattern based on the actual stage of the LTM operation, such that the LTM candidate cell may use the SSB#1 configuration during the LTM preparation and execution stages and may switch to the SSB#2 configuration after the LTM cell switch is completed. By doing so, the LTM candidate cell may, for example, broadcast a denser SSB set during the LTM preparation / execution stage to support efficient early synchronization and L1 / L3 measurement by the UE, and may switch to a sparser SSB set or a different SSB pattern after the LTM cell switch is completed to support network energy saving. In addition, because the SSB adaptation timing may be implicitly determined by the UE based on the transmission of the LTM cell switch completion message, the Mode 1 SSB adaptation operation may avoid the signaling overhead that would be incurred by an explicit SSB activation / de-activation indication for each LTM operation.

[0126] In some other implementations, alternative embodiments of the Mode 1 SSB adaptation operation may be employed. For example, although the Mode 1 SSB adaptation operation as described above is implicitly triggered based on the transmission of the LTM cell switch completion message by the UE, in some other implementations the SSB adaptation timing may be triggered by an explicit indicator transmitted from the serving RAN to the UE (e.g., an indicator carried in the LTM CSC MAC CE or in a separate MAC CE). As another example, although FIG. 1 illustrates the SSB adaptation in connection with a single LTM candidate (e.g., the LTM candidate#1), the SSB adaptation operation may alternatively be applied to multiple LTM candidates in parallel, where each LTM candidate may be associated with one or more SSB configurations and may switch the SSB broadcasting between configurations independently. As yet another example, although FIG. 1 illustrates the SSB#1 configuration and the SSB#2 configuration as being pre-configured during the LTM preparation, in some other implementations the SSB#2 configuration may be configured to the UE later via additional signaling, such as a MAC CE, a downlink control information (DCI), or a combination thereof. As a further example, although the LTM cell switch completion message described above includes an RRC reconfiguration complete message, in some other implementations the LTM cell switch completion message may include another type of message indicative of completion of the LTM operation, such as a dedicated LTM completion indicator carried in a MAC CE or in a UL data packet. The Mode 1 SSB adaptation operation described above is provided as an illustrative example, and other implementations achieving similar technical effects may be employed without departing from the scope of the present disclosure.

[0127] Mode 2 and Mode 2a

[0128] Reference is made to FIG. 2A and FIG. 2B. FIG. 2A is a schematic diagram illustrating an SSB adaptation 200A during an LTM operation according to a second mode (Mode 2) of operation, according to an example implementation of the present disclosure. FIG. 2B is a schematic diagram illustrating an SSB adaptation 200B during an LTM operation according to a sub-mode (Mode 2a) of the second mode of operation, according to an example implementation of the present disclosure. In Mode 2, the candidate cell may switch the SSB broadcasting from the first SSB configuration to the second SSB configuration upon or after the (conditional) LTM configuration is transmitted to the UE, and the parameters of the second SSB configuration may be conveyed to the UE via the LTM CSC MAC CE. In Mode 2a, the candidate cell may further switch from the second SSB configuration to a third SSB configuration after the LTM operation is completed.

[0129] In some implementations of the SSB adaptation 200A of FIG. 2A, the UE may be pre-configured with one or more SSB configurations during LTM preparation. For example, the one or more SSB configurations may include an SSB#1 configuration and / or an SSB#2 configuration, and the one or more SSB configurations may be configured to the UE as part of an LTM configuration or a conditional LTM configuration. After the UE receives the (conditional) LTM configuration from the serving cell, the UE may implement early DL / UL synchronization and / or L1 / L3 measurements towards all or a subset of the LTM candidates configured by the (conditional) LTM configuration based on a first SSB configuration associated with one of the LTM candidates pre-configured in the LTM configuration. For example, the first SSB configuration may include the SSB#1 configuration shown in FIG. 2A, and the UE may detect a first SSB burst set broadcast by the LTM candidate#1 based on the SSB#1 configuration. In some implementations, the UE may report L1 / L3 measurement reports to the serving RAN. For example, the L1 / L3 measurement reports may be reported as part of an LTM measurement report procedure, which is described in further detail in the context of FIG. 9. In addition, the UE may receive at least one LTM CSC MAC CE (or an LTM SCS MAC CE) from the serving RAN to instruct the UE to implement an LTM operation associated with one LTM candidate, such as the LTM candidate#1. The UE may also apply one SMTC configuration associated with the first SSB configuration during the mobility operation for synchronization and measurement.

[0130] The UE may trigger the LTM operation after the UE receives the LTM CSC MAC CE from the source cell, and may then complete the LTM operation accordingly. For example, the UE may trigger the LTM operation by initiating a random access procedure and / or by performing a data transmission. As shown in FIG. 2A, another SSB set, denoted as “SSB#2 broadcasting” in FIG. 2A and associated with one SSB configuration (e.g., the SSB#2 configuration), may be broadcast by the LTM candidate#1 upon or after the (conditional) LTM configuration is transmitted to the UE. In some implementations, one or more control parameters of the SSB#2 configuration, or one or more indicators or indexes associated with the one or more control parameters of the SSB#2 configuration, may be transmitted to the UE via the LTM CSC MAC CE. For example, the one or more control parameters may include an indication of an SSB index, a periodicity, a sub-carrier spacing, or a transmit power for the SSB#2 configuration. After receiving the LTM CSC MAC CE, the UE may implement the subsequent DL / UL synchronization and / or L1 / L3 measurement based on the updated SSB#2 configuration.

[0131] In some implementations, the LTM candidate#1 and the source cell may be controlled, managed, or supported by the same radio node, base station, or central unit (CU). For example, the LTM candidate#1 and the source cell may be cells under the same gNB-CU in an intra-CU LTM deployment, in which case the LTM candidate#1 and the source cell may share LTM-related context information (e.g., a UE context) within the same gNB-CU without involving inter-CU signaling. In some other implementations, the LTM candidate#1 and the source cell may be controlled, managed, or supported by different radio nodes, base stations, or central units (CUs). For example, the LTM candidate#1 and the source cell may be cells under different gNB-CUs in an inter-CU LTM deployment, in which case inter-node signaling (e.g., signaling carried over an Xn interface or another inter-node interface between the gNB-CU of the source cell and the gNB-CU of the LTM candidate#1) may be used for the LTM candidate#1 to start the broadcasting of the updated SSB#2 configuration upon or after the source cell transmits the LTM CSC MAC CE to the UE. The above-described two implementations of the relationship between the LTM candidate#1 and the source cell are provided as illustrative examples, and either implementation may be selected based on the LTM deployment scenario.

[0132] The LTM operation may be considered completed from the perspective of the LTM candidate. For example, the LTM operation may be considered completed from the perspective of the LTM candidate after the LTM candidate#1 receives a first packet transmission from the UE successfully. An LTM candidate that successfully receives the first packet transmission from the UE may also be referred to as a “target LTM candidate” by the UE during the mobility operation. For example, the target LTM candidate may correspond to the LTM candidate that becomes the new serving cell of the UE after the LTM operation is completed, and the UE may, after the LTM cell switch operation, communicate with the network via the target LTM candidate.

[0133] In some implementations, as shown in the SSB adaptation 200B of FIG. 2B (which corresponds to Mode 2a), the (target) LTM candidate#1, which may become a serving cell of the UE after the LTM operation is completed, may change the SSB broadcasting from the SSB#2 configuration to a third SSB configuration (e.g., an SSB#3 configuration) to broadcast a third SSB set, denoted as “SSB#3 broadcasting” in FIG. 2B, after the LTM operation is completed. The transition to the SSB#3 configuration may be enabled by pre-configuring the SSB#3 configuration. For example, the SSB#3 configuration may be configured by the LTM candidate#1 and may be transmitted to the UE as part of the LTM configuration or the LTM candidate configuration. In addition, the LTM candidate#1 may further configure or inform the UE that the SSB#3 configuration would be applied after the LTM operation is completed. For example, the LTM candidate#1 may provide such configuration or information to the UE via the LTM (candidate) configuration or via the LTM CSC MAC CE. Under such an implementation, the UE may directly know that the SSB#3 configuration would be applied after the LTM operation is completed, and the UE may implement DL / UL synchronization and L1 / L3 measurement based on the configured SSB#3 configuration after the LTM operation is completed.

[0134] In a triggering mobility operation, such as a conditional LTM (CLTM) operation, the triggering operation (or execution condition) may also be associated with at least one L1 measurement and / or at least one L3 measurement, which may be measured by the UE based on the adapted SSB patterns during the conditional LTM operation. For example, the UE may switch an operating SMTC configuration from a first SMTC configuration to a second SMTC configuration jointly with the SSB adaptation implementation. In such a case, the first SMTC configuration may be associated with the first SSB configuration (e.g., the SSB#1 configuration) and the second SMTC configuration may be associated with the second SSB configuration (e.g., the SSB#2 configuration).

[0135] The configuring entity for the SSB configurations may take various forms, and several illustrative forms are described below. In some implementations, the SSB#1 configuration and the SSB#2 configuration (and / or the SSB#3 configuration) may be configured or determined by the (target) LTM candidate directly. In some other implementations, the SSB#1 configuration and the SSB#2 configuration (and / or the SSB#3 configuration) may be configured by the source cell directly. In some additional implementations, the SSB#1 configuration may be configured by the source cell and the SSB#2 configuration (and / or the SSB#3 configuration) may be configured by the (target) LTM candidate respectively. The above-described three implementations regarding the configuring entity of the SSB configurations are provided as illustrative examples, and the configuring entity may be assigned in any one or any combination of the above forms based on the inter-node coordination capability and the deployment scenario.

[0136] The configuring entity for the SMTC configurations may also take various forms, and several illustrative forms are described below. In some implementations, the first SMTC configuration and the second SMTC configuration may be configured by the (target) LTM candidate directly. In some other implementations, the first SMTC configuration and the second SMTC configuration may be configured by the source cell directly. In some additional implementations, the first SMTC configuration may be configured by the source cell and the second SMTC configuration may be configured by the (target) LTM candidate respectively. The above-described three implementations regarding the configuring entity of the SMTC configurations are provided as illustrative examples, and the configuring entity may be assigned in any one or any combination of the above forms based on the inter-node coordination capability and the deployment scenario.

[0137] The actions illustrated in FIG. 2A and FIG. 2B may be used to characterize the SSB adaptation 200A and the SSB adaptation 200B, respectively. In action 202, the serving RAN may transmit an LTM (candidate) configuration to the UE, and the UE may transmit a response to the serving RAN. For example, the LTM (candidate) configuration may be transmitted via an RRC reconfiguration message that includes one or more LTM candidates and one or more associated SSB configurations of each LTM candidate (e.g., the SSB#1 configuration, and in some implementations the SSB#3 configuration of FIG. 2B), and the response may be transmitted via an RRC reconfiguration complete message acknowledging receipt of the LTM (candidate) configuration. In action 204, the UE may track an activation status of the LTM candidate#1 over time. For example, after the UE receives the LTM candidate configuration that includes the LTM candidate#1, the UE may consider the LTM candidate#1 as activated, such that the UE may begin to perform early DL / UL synchronization and / or L1 / L3 measurement towards the LTM candidate#1 based on the SSB#1 configuration. In action 206, the serving RAN may transmit an LTM SCS MAC CE to the UE. For example, the LTM SCS MAC CE may include one or more control parameters of the SSB#2 configuration (e.g., a periodicity, a sub-carrier spacing, a transmit power, or one or more parameter indexes referencing pre-configured SSB parameter sets), or one or more indexes referencing the SSB#2 configuration, such that the UE may apply the SSB#2 configuration for subsequent DL / UL synchronization and L1 / L3 measurement. In action 208, the UE may complete the LTM cell switch operation. For example, the UE may transmit an LTM cell switch completion message (e.g., an RRC reconfiguration complete message) to the LTM candidate#1 to indicate the completion of the LTM cell switch operation, or the LTM candidate#1 may consider the LTM cell switch operation as completed upon successful reception of a first packet transmission from the UE. As further shown in FIG. 2A, the SSB#1 broadcasting may be performed by the LTM candidate#1 prior to action 202, and the SSB#2 broadcasting may be performed by the LTM candidate#1 upon or after action 202 (e.g., upon or after the LTM (candidate) configuration is transmitted to the UE in action 202). As further shown in FIG. 2B, in addition to the SSB#1 broadcasting and the SSB#2 broadcasting, the SSB#3 broadcasting may be performed by the LTM candidate#1 after action 208 (e.g., after the LTM operation is considered completed). The timing offset between action 208 and the start of the SSB#3 broadcasting may, for example, be configurable based on the LTM (candidate) configuration or the LTM SCS MAC CE.

[0138] The Mode 2 and Mode 2a SSB adaptation operations described above may provide certain technical effects. For example, by transmitting one or more control parameters of the SSB#2 configuration via the LTM CSC MAC CE, the Mode 2 SSB adaptation operation may enable the serving RAN to dynamically convey or update the SSB broadcasting parameters that the UE applies during the LTM execution stage, such that the SSB#2 configuration may be tailored to the radio condition or the deployment scenario at the time of the LTM cell switch. As another example, by introducing the SSB#3 configuration in Mode 2a, the LTM candidate#1, after becoming a serving cell of the UE, may use the SSB#3 configuration to broadcast the SSB set in a manner that may be optimized for the post-LTM serving-cell operation, such as a less frequent SSB broadcasting for network energy saving or a more frequent SSB broadcasting for enhanced beam refinement.

[0139] In some other implementations, alternative embodiments of the Mode 2 and Mode 2a SSB adaptation operations may be employed. For example, although the parameters of the SSB#2 configuration are described above as being conveyed via the LTM CSC MAC CE, in some other implementations the parameters may alternatively be conveyed via a downlink control information (DCI), via a separate dedicated MAC CE, via an RRC reconfiguration message, or via any combination thereof. As another example, although the SSB#3 configuration is described above as being pre-configured to the UE as part of the LTM configuration or the LTM candidate configuration, in some other implementations the SSB#3 configuration may alternatively be conveyed to the UE after the LTM operation is completed via additional signaling such as a MAC CE or a DCI from the new serving cell. As yet another example, although Mode 2a is described above as introducing one additional SSB configuration (i.e., the SSB#3 configuration) after the LTM operation is completed, in some other implementations the LTM candidate#1 may sequentially apply more than two SSB configurations after the LTM operation is completed (e.g., an SSB#3 configuration during a first post-LTM phase and an SSB#4 configuration during a second post-LTM phase) based on factors such as the time elapsed since the LTM completion, the radio condition, or the network energy saving target. The above-described Mode 2 and Mode 2a SSB adaptation operations are provided as illustrative examples, and other implementations achieving similar technical effects may be employed without departing from the scope of the present disclosure.

[0140] Any of the SSB adaptation modes described in the preceding sections (e.g., the Mode 1 of FIG. 1) may be used in combination with the SSB adaptation modes described in this section (e.g., the Mode 2 of FIG. 2A or the Mode 2a of FIG. 2B). For example, in some implementations, the Mode 1 SSB adaptation may be applied to a first LTM candidate that is associated with two pre-configured SSB configurations, while the Mode 2 SSB adaptation may be applied to a second LTM candidate that is associated with two SSB configurations whose later-stage parameters are conveyed via an LTM CSC MAC CE. The specific combination of the SSB adaptation modes may depend on the deployment scenario, the inter-node coordination capability, and the UE capability.

[0141] Mode 3

[0142] Reference is made to FIG. 3. FIG. 3 is a schematic diagram illustrating an SSB adaptation 300 during a conditional LTM operation according to a third mode (Mode 3) of operation, according to an example implementation of the present disclosure. In Mode 3, the LTM operation may be implemented as a conditional LTM operation, such that the UE may trigger the LTM operation upon determining that one or more pre-configured triggering events associated with the LTM candidate are fulfilled, without receiving an LTM CSC MAC CE from the serving RAN. The candidate cell may switch the SSB broadcasting from the first SSB configuration to the second SSB configuration after the conditional LTM operation is considered completed from the perspective of the LTM candidate. The triggering events that initiate the conditional LTM operation may, for example, include one or more L1 measurement events and / or one or more L3 measurement events that are pre-configured to the UE as part of the LTM (candidate) configuration. For example, the triggering events may correspond to a serving-cell signal quality (e.g., a Reference Signal Received Power (RSRP) or a Reference Signal Received Quality (RSRQ) of the serving cell) falling below a configured threshold concurrently with a candidate-cell signal quality exceeding another configured threshold for a configured time-to-trigger duration.

[0143] In some implementations of the SSB adaptation 300 of FIG. 3, the UE may be pre-configured with one or more SSB configurations during LTM preparation. For example, the one or more SSB configurations may include an SSB#1 configuration and / or an SSB#2 configuration, and the one or more SSB configurations may be configured to the UE as part of an LTM configuration or a conditional LTM configuration. The UE may also be pre-configured with one or more triggering events associated with the LTM candidate. For example, each triggering event may indicate one or more measurement-based conditions on which the UE may autonomously initiate the LTM operation towards the LTM candidate, and the conditions may include one or more of an event-based measurement condition (e.g., an event in which a candidate-cell measurement quantity becomes higher than a serving-cell measurement quantity by an offset), a periodic-trigger-based measurement condition, or a time-to-trigger-based condition.

[0144] After the UE receives the (conditional) LTM configuration from the serving cell, the UE may implement early DL / UL synchronization and / or L1 / L3 measurements towards all or a subset of the LTM candidates configured by the (conditional) LTM configuration. In some implementations, the UE may report L1 / L3 measurement reports to the serving RAN. For example, the L1 / L3 measurement reports may be reported as part of an LTM measurement report procedure, which is described in further detail in the context of FIG. 9. In addition, as shown in FIG. 3, the UE may decide to trigger a conditional LTM operation associated with one LTM candidate (e.g., the LTM candidate#1) when the triggering events associated with the LTM candidate#1 are fulfilled. For example, the triggering events may include one or more L1 / L3 triggering events associated with the LTM candidate#1, which may be pre-configured to the UE as part of the LTM (candidate) configuration. The UE may trigger the conditional LTM operation, for example by initiating a random access procedure and / or by performing a data transmission, and may then complete the triggered LTM operation accordingly.

[0145] As shown in FIG. 3, the LTM candidate#1 may broadcast a first SSB set, denoted as “SSB#1 broadcasting” in FIG. 3, periodically based on the first SSB configuration (e.g., the SSB#1 configuration). In addition, the LTM candidate#1 may change or switch the SSB set broadcasting from the SSB#1 configuration to a second SSB configuration (e.g., the SSB#2 configuration) to broadcast a second SSB set, denoted as “SSB#2 broadcasting” in FIG. 3, after the conditional LTM operation is completed from the perspective of the LTM candidate. For example, the conditional LTM operation may be considered completed from the perspective of the LTM candidate after the LTM candidate#1 receives a first packet transmission from the UE successfully. The first packet transmission may, for example, include a UL data packet carrying user data, an RRC reconfiguration complete message, or another type of UL transmission that the LTM candidate may decode successfully.

[0146] The relative periodicity between the SSB#1 configuration and the SSB#2 configuration in Mode 3 may take various forms, and several illustrative forms are described below. In some implementations, the periodicity of the SSB#2 configuration (e.g., the periodicity of the SSB burst set associated with the SSB#2 configuration) may be longer than the periodicity of the SSB#1 configuration. For example, the SSB#2 configuration may be used to support a network energy saving deployment in which the LTM candidate, after becoming a serving cell of the UE, may broadcast the SSB set less frequently to reduce energy consumption. In some implementations, the periodicity of the SSB#2 configuration may be shorter than the periodicity of the SSB#1 configuration. For example, the SSB#2 configuration may be used in a deployment in which the LTM candidate, after becoming a serving cell of the UE, may broadcast the SSB set more frequently to support enhanced beam tracking, beam refinement, or measurement reporting. The above-described two implementations of the relative periodicity are provided as illustrative examples, and the SSB#1 configuration and the SSB#2 configuration may have any relative periodicity relationship that satisfies the deployment requirement.

[0147] The proposed SSB adaptation mechanism of Mode 3 may also be applicable to a candidate cell that supports On-Demand SIB1 (OD-SIB1) operation during the mobility operation. For example, the OD-SIB1 operation may correspond to an operation in which a System Information Block Type 1 (SIB1) of the candidate cell is broadcast on demand (e.g., upon request from a UE or upon a network trigger) rather than being broadcast continuously. In such a case, the UE may apply the SSB adaptation directly without monitoring the SIB1, since the SIB1 may not be broadcast by the candidate cell during the mobility operation. The candidate cell may not broadcast the SIB1 during the mobility operation (and after the mobility operation), and the UE may still implement the mobility operation (e.g., LTM or (conditional) handover) with the candidate cell. For example, the UE may forgo monitoring the SIB1 of the candidate cell during the mobility operation. In some implementations, the UE may obtain the system information of the candidate cell through one or more alternative mechanisms. For example, in some implementations, the UE may obtain the system information of the candidate cell from the LTM (candidate) configuration provided by the source cell. In some implementations, the UE may obtain the system information of the candidate cell via dedicated signaling from the source cell. In some implementations, the UE may obtain the system information of the candidate cell via inter-node signaling between the source cell and the candidate cell, where the source cell may forward the system information of the candidate cell to the UE on behalf of the candidate cell. The above-described three implementations regarding obtaining the system information of the candidate cell are provided as illustrative examples, and any one or any combination of the above forms may be selected based on the deployment scenario and the inter-node coordination capability.

[0148] The actions illustrated in FIG. 3 may be used to characterize the SSB adaptation 300. In action 302, the serving RAN may transmit an LTM (candidate) configuration to the UE, and the UE may transmit a response to the serving RAN. For example, the LTM (candidate) configuration may be transmitted via an RRC reconfiguration message that includes one or more LTM candidates and one or more associated SSB configurations of each LTM candidate, and the response may be transmitted via an RRC reconfiguration complete message acknowledging receipt of the LTM (candidate) configuration. In addition, the LTM (candidate) configuration may include one or more pre-configured triggering events associated with each LTM candidate (e.g., one or more L1 / L3 triggering events associated with the LTM candidate#1) for the conditional LTM operation. In action 304, the UE may track an activation status of the LTM candidate#1 over time. For example, after the UE receives the LTM candidate configuration that includes the LTM candidate#1, the UE may consider the LTM candidate#1 as activated, such that the UE may begin to perform early DL / UL synchronization and / or L1 / L3 measurement towards the LTM candidate#1, including evaluation of the pre-configured triggering events associated with the LTM candidate#1. In action 306, the UE may determine that the pre-configured triggering events associated with the LTM candidate#1 for the conditional LTM operation are fulfilled, and may trigger the conditional LTM operation. For example, the UE may determine that the pre-configured triggering events are fulfilled when an L1 measurement quantity (e.g., an L1 RSRP) of the LTM candidate#1 satisfies a configured condition relative to that of the serving cell, or when an L3 measurement quantity satisfies a configured event-based condition for a configured time-to-trigger duration. In some implementations, the UE may trigger the conditional LTM operation without receiving an LTM CSC MAC CE from the serving RAN. For example, the UE may forgo waiting for an explicit LTM CSC MAC CE upon determining that the pre-configured triggering events are fulfilled, and the UE may immediately initiate the conditional LTM operation by performing a random access procedure or by transmitting an UL data packet to the LTM candidate#1. In some implementations, the UE may trigger the conditional LTM operation upon receiving an LTM CSC MAC CE that confirms the conditional LTM trigger; for example, the LTM CSC MAC CE may be used to coordinate the conditional LTM execution timing with the serving RAN in a deployment that supports both implicit conditional LTM triggering and serving-RAN-coordinated conditional LTM triggering. The above-described two implementations of the conditional LTM triggering are provided as illustrative examples and are independently valid; the specific implementation may be selected based on the LTM (candidate) configuration and the deployment scenario. In action 308, the UE may complete the (conditional) LTM cell switch operation. For example, the UE may transmit an LTM cell switch completion message (e.g., an RRC reconfiguration complete message) to the LTM candidate#1 to indicate the completion of the conditional LTM operation, or the LTM candidate#1 may consider the LTM cell switch operation as completed upon successful reception of a first packet transmission from the UE. As further shown in FIG. 3, the SSB#1 broadcasting may be performed by the LTM candidate#1 from a time prior to action 302 and may continue until action 308. After action 308, the LTM candidate#1 may switch to the SSB#2 broadcasting based on the SSB#2 configuration.

[0149] The mechanism illustrated in FIG. 3 may also be applicable to a (conditional) handover procedure (i.e., a Layer-3 mobility operation). To apply the mechanism of FIG. 3 to a Layer-3 conditional mobility operation: in some implementations, the LTM candidate configuration may be replaced by an RRC reconfiguration message that includes one or more candidates for conditional handover; in some implementations, the conditional handover may be triggered by the UE based on one or more pre-configured initiation events without receiving an explicit handover command in an RRC reconfiguration message; and in some implementations, the LTM cell switch completion message may be replaced by an RRC reconfiguration complete message transmitted by the UE to the target cell upon completion of the conditional handover.

[0150] The Mode 3 SSB adaptation operation described above may provide certain technical effects. For example, the Mode 3 SSB adaptation operation may enable the LTM candidate cell to switch the SSB broadcasting pattern based on the actual completion of the conditional LTM operation, such that the LTM candidate cell may use the SSB#1 configuration during the conditional LTM preparation and triggering stages and may switch to the SSB#2 configuration after the conditional LTM cell switch is completed. By doing so, the LTM candidate cell may, for example, broadcast a denser SSB set during the conditional LTM preparation / triggering stage to support efficient early synchronization and L1 / L3 measurement by the UE, and may switch to a sparser SSB set or a different SSB pattern after the conditional LTM cell switch is completed to support network energy saving. In addition, because the conditional LTM operation may be autonomously triggered by the UE upon fulfillment of the pre-configured triggering events without requiring an LTM CSC MAC CE from the serving RAN, the Mode 3 SSB adaptation operation may further reduce the signaling overhead at the serving RAN and may shorten the latency between the fulfillment of the triggering events and the initiation of the LTM cell switch.

[0151] In some other implementations, alternative embodiments of the Mode 3 SSB adaptation operation may be employed. For example, although the conditional LTM operation in Mode 3 is described above as being triggered upon fulfillment of one or more L1 / L3 measurement-based triggering events, in some other implementations the conditional LTM operation may be triggered by additional or alternative event types, such as a UE-mobility-state-based event, a UE-location-based event, a Quality of Service (QoS) requirement based event, or a combination thereof. As another example, although Mode 3 is described above as switching the SSB broadcasting from the SSB#1 configuration to the SSB#2 configuration after the conditional LTM operation is completed, in some other implementations the LTM candidate#1 may sequentially apply more than two SSB configurations following the conditional LTM completion (e.g., transitioning through an SSB#2 configuration and then to an SSB#3 configuration based on time-since-completion or post-LTM radio conditions). As yet another example, although the (conditional) LTM operation in Mode 3 is described above as being autonomously triggered by the UE without an LTM CSC MAC CE, in some other implementations the serving RAN may optionally transmit an LTM CSC MAC CE that confirms the conditional LTM trigger or provides additional parameters for the conditional LTM cell switch (e.g., a target configuration ID or a timing advance value), and the UE may take such an LTM CSC MAC CE into account when initiating the conditional LTM operation.

[0152] Any of the SSB adaptation modes described in the preceding sections (e.g., the Mode 1 of FIG. 1, the Mode 2 of FIG. 2A, or the Mode 2a of FIG. 2B) may be used in combination with the Mode 3 SSB adaptation described in this section. For example, in some implementations, an LTM (candidate) configuration may include a first LTM candidate configured for Mode 1, a second LTM candidate configured for Mode 2, and a third LTM candidate configured for Mode 3, where the UE may apply different SSB adaptation modes to different LTM candidates based on the per-candidate configuration. The specific combination of the SSB adaptation modes across LTM candidates may depend on the deployment scenario, the inter-node coordination capability, and the UE capability.

[0153] Implicit / Explicit SSB Adaptation Mechanism

[0154] Reference is made to FIG. 4. FIG. 4 is a flowchart illustrating an implicit and explicit SSB adaptation mechanism at a UE side, according to an example implementation of the present disclosure. The implicit SSB adaptation mechanism may correspond to a mechanism in which the UE determines the timing and the content of an SSB configuration switch based on a procedural event or a pre-configured condition, without relying on a dedicated per-event indication from the serving RAN. The explicit SSB adaptation mechanism may correspond to a mechanism in which the serving RAN transmits a dedicated indication (e.g., carried in a MAC CE or an RRC message) to the UE to designate the SSB configuration to be applied or the SSB parameters to be updated. For example, the explicit SSB adaptation mechanism may be used when the serving RAN desires to override a default implicit SSB configuration, or when the network-side deployment benefits from a per-event signaling exchange that aligns the UE's SSB configuration with a specific radio condition.

[0155] As to the implicit SSB adaptation mechanism, the serving RAN (e.g., the base station, the gNB, or the eNB) may modify the SSB broadcasting activity (or the UE may assume the modification of the SSB broadcasting activity) by adapting the SSB configuration implicitly at different procedural timings. For example, the implicit SSB adaptation may be applied upon or after the source cell transmits the LTM configuration (and the following LTM candidate configuration) to the UE (e.g., via an RRC reconfiguration message). For example, the implicit SSB adaptation may be applied upon or after the UE transmits an RRC reconfiguration complete message to the source cell (e.g., after the UE receives the LTM configuration from the source cell). For example, the implicit SSB adaptation may be applied upon or after the (conditional) LTM operation is considered completed from the perspective of the serving RAN (e.g., upon or after the UE transmits an RRC reconfiguration complete message to the target LTM candidate cell). The above-described three timings for applying the implicit SSB adaptation may be referred to, respectively, as a first implicit timing condition, a second implicit timing condition, and a third implicit timing condition. The first implicit timing condition, the second implicit timing condition, and the third implicit timing condition are provided as illustrative examples, and the implicit SSB adaptation may be applied at any one of these timings or at a combination of these timings based on the configuration received by the UE.

[0156] From the perspective of the UE, the UE may be pre-configured or pre-defined to implement the early DL / UL synchronization and / or L1 / L3 measurement implicitly while one of the first, second, or third implicit timing condition is achieved. For example, the pre-configuration may be provided to the UE as part of the LTM configuration or the LTM candidate configuration associated with the LTM candidate. For example, the pre-definition may be provided to the UE via a radio technology specification or may be stored in a memory module of the UE.

[0157] In some implementations, one additional timing offset may be pre-configured or pre-defined for the UE, such that the UE may start the early synchronization and / or L1 / L3 measurement after the corresponding implicit timing condition is fulfilled. For example, the additional timing offset may correspond to a time interval that the UE may wait after the fulfillment of the implicit timing condition before starting the early synchronization and / or L1 / L3 measurement, in order to align with the timing at which the candidate cell actually begins the updated SSB broadcasting. In some implementations, a respective timing offset may be configured to be associated with each of the first, second, or third implicit timing condition. For example, a first timing offset, a second timing offset, and a third timing offset (which may be generally referred to as Toffset(a), Toffset(b), and Toffset(c), respectively) may be associated with the first, second, and third implicit timing condition, respectively. The UE may start a timer while the corresponding implicit timing condition is met, with an initial value of the timer set to the associated timing offset. For example, the UE may count down the timer to zero, and may start the early synchronization and / or L1 / L3 measurement based on the updated SSB configuration when the timer reaches zero. The timing offsets may be specified as multiples of slots, subframes, or radio frames, or may be specified in units of milliseconds, and other unit choices may also be employed depending on the deployment scenario.

[0158] In some additional implementations, one or more BS-side timing offsets may also be pre-configured or pre-defined for the base station (e.g., the source base station and / or the target LTM candidate) to start the SSB broadcasting activity after a corresponding implicit timing condition is fulfilled. For example, a first BS-side timing offset, a second BS-side timing offset, and a third BS-side timing offset (which may be generally referred to as Toffset(a), BS, Toffset(b), BS, and Toffset(c), BS, respectively) may be associated with the first, second, and third implicit timing condition, respectively. The BS-side timing offset may correspond to a time interval that the base station may wait after the fulfillment of the corresponding implicit timing condition before starting the updated SSB broadcasting activity. In some implementations, the UE-side timing offsets and the BS-side timing offsets may be identical for each implicit timing condition, such that the UE and the base station may align on the starting moment of the updated SSB broadcasting. In some other implementations, the UE-side timing offsets and the BS-side timing offsets may differ, such that the UE and the base station may have respective offsets to account for, for example, a processing latency at each side.

[0159] As to the explicit SSB adaptation mechanism, the UE may be configured with the SSB adaptation via an explicit instruction from the serving cell, the base station, or the serving RAN. For example, the UE may receive one or more LTM CSC MAC CEs from the serving RAN, and the LTM CSC MAC CE may include information or configuration that indicates to the UE how the target LTM candidate (e.g., the LTM candidate#1) may broadcast the SSB burst set periodically. The LTM CSC MAC CE may carry the SSB-related indication in one or more forms, and several illustrative forms are described below.

[0160] In some implementations, the LTM CSC MAC CE may carry an SSB index associated with one pre-configured SSB configuration. For example, the SSB index may identify one of multiple pre-configured SSB configurations that may have been provided to the UE earlier as part of the LTM configuration or the LTM candidate configuration, and the UE may apply the identified SSB configuration after receiving the LTM CSC MAC CE.

[0161] In some implementations, the LTM CSC MAC CE may carry an SSB-index bitmap. Each bit in the bitmap may be used to indicate the SS / PBCH index of the SS / PBCH block corresponding to the SSB configuration. In addition, each bit may be set to‘1’ to represent that the corresponding SS / PBCH block is activated, or set to ‘0’ to represent that the corresponding SS / PBCH block is de-activated. The length of the SSB-index bitmap associated with one SSB configuration may be determined by the maximum number of SS / PBCH blocks per half frame. For example, the SSB-index bitmap may be a short bitmap of 4 bits, a medium bitmap of 8 bits, or a long bitmap of 64 bits.

[0162] In some implementations, the LTM CSC MAC CE may carry a parameter index or bitmap associated with one or more pre-configured SSB parameters of an SSB (e.g., a periodicity of the SSB). For example, the parameter index may identify one entry in a pre-configured SSB parameter list, and the identified entry may specify one or more SSB parameter values. In some implementations, the pre-configured SSB parameters may be associated with a general SSB parameter list in the LTM configuration. For example, the general SSB parameter list may be commonly associated with all of the LTM candidates in the same LTM configuration, such that multiple LTM candidates may share the same set of SSB parameter options. In some other implementations, the pre-configured SSB parameters may be associated with an LTM-specific SSB parameter list, which may be associated with one specific LTM candidate (e.g., the LTM candidate#1 in FIG. 2A and FIG. 2B). For example, the LTM-specific SSB parameter list may enable each LTM candidate to have a tailored set of SSB parameter options that reflects the deployment configuration of the LTM candidate.

[0163] In some implementations, the LTM CSC MAC CE may carry an SSB parameter value, or a differential value between an existing SSB parameter value and an updated SSB parameter value instructed by the serving RAN. For example, the LTM CSC MAC CE may carry a ss-PBCH-BlockPower value for the transmit power level of the SSB set, or may carry a differential value that the UE may add to (or subtract from) an existing ss-PBCH-BlockPower value to derive the updated transmit power level. The differential value form may, for example, reduce the signaling overhead when the updated SSB parameter differs from the existing SSB parameter by a small amount.

[0164] The above-described illustrative forms of the SSB-related indication carried in the LTM CSC MAC CE may be used individually or in any combination, and the specific form may depend on factors such as the pre-configuration granularity, the signaling overhead budget, and the deployment scenario. For example, in some implementations, the LTM CSC MAC CE may carry both an SSB index and one or more differential SSB parameter values, such that the UE may first select a pre-configured SSB configuration based on the SSB index and then adjust one or more parameters of the selected SSB configuration based on the differential values.

[0165] In some implementations, the proposed explicit and implicit SSB adaptation mechanisms may be supported by the serving RAN and the UE. The UE may share or indicate a capability to the serving RAN, where the capability may indicate whether the UE supports the explicit SSB adaptation mechanism, the implicit SSB adaptation mechanism, or both. For example, the capability may correspond to one or more capability bits carried in a UE capability information report. In addition, the serving RAN may configure the UE to apply a selected SSB adaptation mechanism (e.g., the explicit SSB adaptation mechanism or the implicit SSB adaptation mechanism) for a particular LTM candidate or for a group of LTM candidates.

[0166] In some implementations, all of the LTM candidates configured to the UE may be associated with the same SSB adaptation mechanism (e.g., either the explicit SSB adaptation mechanism or the implicit SSB adaptation mechanism) configured by the serving RAN. In some other implementations, each of the LTM candidates (or a subset of the LTM candidates) may be configured with a different SSB adaptation mechanism. For example, a first LTM candidate may be configured with the implicit SSB adaptation mechanism while a second LTM candidate may be configured with the explicit SSB adaptation mechanism.

[0167] In some other implementations, both the implicit SSB adaptation and the explicit SSB adaptation mechanisms may be configured to the serving RAN and the UE simultaneously. One SSB adaptation mechanism (e.g., the implicit SSB adaptation mechanism) may be pre-defined or pre-configured as a default mechanism for the LTM operation. For example, the default mechanism may correspond to an SSB adaptation mechanism that the UE applies when no explicit SSB-related indication is received from the serving RAN. The serving RAN may still transmit an updated SSB configuration or an updated SSB parameter index to the UE via the explicit signaling (e.g., the LTM CSC MAC CE). In addition, the explicit instruction may overwrite the existing SSB configuration or the existing SSB parameter, even if the existing SSB configuration or the existing SSB parameter was derived from the previous implicit SSB adaptation mechanism. For example, when the implicit SSB adaptation mechanism designates an SSB#2 configuration as the post-LTM SSB configuration and the subsequent LTM CSC MAC CE explicitly designates an alternative SSB configuration, the UE may apply the alternative SSB configuration indicated by the LTM CSC MAC CE.

[0168] The actions illustrated in the flowchart of FIG. 4 may be used to characterize the behavior of the UE side with respect to the implicit and explicit SSB adaptation mechanisms. In action 402, the UE may receive the LTM configuration from the serving RAN. For example, the LTM configuration may be received via an RRC reconfiguration message that includes one or more LTM candidates and one or more associated SSB configurations of each LTM candidate. In action 404, the UE may perform early synchronization and / or L1 / L3 measurements based on the SSB parameters configured in the LTM configuration. For example, the UE may perform DL synchronization based on the SSB burst set broadcast by each LTM candidate, and may perform UL synchronization based on a reference signal (e.g., a pre-configured uplink reference signal or a preamble). In action 406, the UE may determine whether an implicit approach or an explicit approach is to be applied for the SSB adaptation. For example, the UE may determine the approach based on the capability indicated by the UE, the configuration received from the serving RAN, or a combination thereof. When the implicit approach is applied, the UE may proceed to action 408. When the explicit approach is applied, the UE may proceed to action 410. In some implementations, the UE may also apply both the implicit approach and the explicit approach in parallel or in combination based on the configuration from the serving RAN.

[0169] In action 408, in the implicit branch, the UE may determine whether the conditional LTM triggering events are fulfilled. For example, the UE may determine the fulfillment of the conditional LTM triggering events based on L1 measurement results and / or L3 measurement results evaluated against pre-configured conditions (e.g., an event-based measurement condition in which a candidate-cell measurement quantity becomes higher than a serving-cell measurement quantity by an offset for a configured time-to-trigger duration). When the conditional LTM triggering events are determined to be fulfilled (i.e., the “Triggered” branch of action 408), the UE may proceed to action 412. When the conditional LTM triggering events are determined not to be fulfilled (i.e., the “Not Triggered” branch of action 408), no SSB parameter update may be performed, and the flow may end without applying an SSB adaptation.

[0170] In action 412, the MAC entity of the UE may notify an upper layer (e.g., an RRC entity of the UE) and / or a lower layer (e.g., a PHY layer of the UE) of the LTM CSC. For example, the notification may indicate to the upper layer and / or the lower layer that an LTM cell switch is to be executed, such that the upper layer and / or the lower layer may prepare for the LTM cell switch. The “LTM CSC” referenced in the notification in action 412 may, in the context of a conditional LTM operation, correspond to an internal representation of the conditional LTM execution trigger that the MAC entity may generate based on the fulfillment of the conditional LTM triggering events, rather than an explicit LTM CSC MAC CE received from the serving RAN. In action 414, the RRC and / or PHY layer of the UE may update the SSB parameters implicitly based on the implicit SSB adaptation configuration. For example, the RRC and / or PHY layer may switch the applied SSB configuration from the pre-configured first SSB configuration (e.g., the SSB#1 configuration) to the pre-configured second SSB configuration (e.g., the SSB#2 configuration) based on the current implicit timing condition. In action 416, the SSB parameters may be updated at the UE, and the flow may end or may loop back for subsequent conditional LTM triggering event evaluation.

[0171] In action 410, in the explicit branch, the UE may determine whether an LTM CSC MAC CE has been received from the serving RAN. When the LTM CSC MAC CE has been received (i.e., the “Yes” branch of action 410), the UE may proceed to action 418. When the LTM CSC MAC CE has not been received (i.e., the “No” branch of action 410), no SSB parameter update may be performed at the current iteration, and the UE may continue to monitor for the LTM CSC MAC CE (e.g., by looping back to action 410 or to an earlier action).

[0172] In action 418, the MAC entity of the UE may receive the LTM CSC MAC CE and may check the content of the LTM CSC MAC CE. For example, the MAC entity may parse the LTM CSC MAC CE to extract one or more of a target configuration ID, an SSB index, a parameter index, an SSB parameter value, a differential SSB parameter value, or a timing advance command. In action 420, the UE may perform the LTM operation based on the received LTM CSC MAC CE. For example, the UE may apply the target configuration indicated by the target configuration ID, and may apply the SSB configuration or the SSB parameters derived from the LTM CSC MAC CE. In action 422, the MAC entity of the UE may notify the upper layer (e.g., the RRC entity) and / or the lower layer (e.g., the PHY layer) of the SSB parameters update, and the UE may perform synchronization and / or L1 / L3 measurements based on the updated SSB parameters. For example, the UE may detect an SSB burst set broadcast by the target LTM candidate based on the updated SSB configuration, and the flow may end or may loop back for subsequent LTM operations.

[0173] The implicit and explicit SSB adaptation mechanisms described above may provide certain technical effects. For example, the implicit SSB adaptation mechanism may reduce the per-event signaling overhead at the serving RAN by relying on procedural events and pre-configured timing offsets instead of dedicated MAC CE transmissions for each SSB configuration switch. As another example, the explicit SSB adaptation mechanism may provide flexibility for the serving RAN to dynamically override a default SSB configuration based on real-time radio conditions, deployment-specific preferences, or network-side optimization targets. As yet another example, the combination of the implicit and explicit SSB adaptation mechanisms may enable a layered design in which a default implicit behavior reduces the typical signaling overhead while an optional explicit indication supports dynamic adaptation when the default implicit behavior is not appropriate.

[0174] In some other implementations, alternative embodiments of the implicit and explicit SSB adaptation mechanisms may be employed. For example, although the implicit SSB adaptation mechanism is described above as being triggered upon one of three implicit timing conditions, in some other implementations additional implicit timing conditions may be defined, such as an implicit timing condition based on the reception of a specific RRC message (e.g., an SMTC configuration update message) or an implicit timing condition based on a pre-configured absolute time reference. As another example, although the explicit SSB adaptation mechanism is described above as being carried in an LTM CSC MAC CE, in some other implementations the explicit SSB adaptation indication may alternatively be carried in a DCI, in a dedicated MAC CE other than the LTM CSC MAC CE, or in an RRC reconfiguration message, or may be carried in a combination of these signaling forms. As yet another example, although the default mechanism is described above as the implicit SSB adaptation mechanism in one illustrative implementation, in some other implementations the default mechanism may be the explicit SSB adaptation mechanism, with the implicit SSB adaptation mechanism being applied only when explicitly enabled by the serving RAN.

[0175] Cross-Layer SSB Parameter Update

[0176] Reference is made to FIG. 5. FIG. 5 is a schematic diagram illustrating a cross-layer SSB parameter adaptation 500 at a UE side, according to an example implementation of the present disclosure. The cross-layer SSB parameter adaptation 500 of FIG. 5 may correspond to an interaction among multiple protocol-stack layers of the UE during a (conditional) LTM operation, in which a MAC entity of the UE may coordinate with an RRC entity of the UE and with a PHY entity of the UE to apply updated SSB parameters to early synchronization and L1 / L3 measurement operations.

[0177] In some implementations, the MAC entity at the UE side may be responsible for modifying or updating the SSB parameters during a (conditional) LTM operation. As shown in FIG. 5, the UE may include a PHY entity 502, a MAC entity 504, and an RRC entity 506. The PHY entity 502 may correspond to a physical-layer entity that may perform, for example, SSB detection, downlink reference signal measurement, and uplink transmission. The MAC entity 504 may correspond to a medium-access-control entity that may perform, for example, MAC CE reception and parsing, logical channel management, and scheduling-related functions. The RRC entity 506 may correspond to a radio-resource-control entity that may perform, for example, RRC message processing, connection management, and activation / deactivation of certain protocol-level operations. In some implementations, the PHY entity 502, the MAC entity 504, and the RRC entity 506 may be associated with a master node (MN) or a master cell group (MCG) of the UE. In some implementations, the PHY entity 502, the MAC entity 504, and the RRC entity 506 may be associated with a secondary node (SN) or a secondary cell group (SCG) of the UE. For example, the MN or MCG may correspond to a node or cell group that provides the primary radio connection for the UE, and the SN or SCG may correspond to a node or cell group that provides an additional radio connection (e.g., in a dual connectivity deployment). The above-described two associations of the PHY / MAC / RRC entities are provided as illustrative examples, and the PHY / MAC / RRC entities associated with each of the MN / MCG and the SN / SCG may operate independently or in coordination based on the deployment scenario.

[0178] As further shown in FIG. 5, the RRC entity 506 may transmit an indication to the MAC entity 504 that a (conditional) LTM operation is activated or enabled by the RRC entity 506. For example, the RRC entity 506 may determine that the (conditional) LTM operation is activated based on a received RRC reconfiguration message (e.g., an LTM configuration or a conditional LTM configuration), and may pass the activation indication to the MAC entity 504 via an internal inter-layer interface. Upon receiving the activation indication from the RRC entity 506, the MAC entity 504 may begin to monitor messages related to the LTM operation. For example, the MAC entity 504 may monitor incoming MAC PDUs for one or more LTM CSC MAC CEs that may carry SSB-related configuration or parameters.

[0179] In some implementations, the MAC entity 504 may receive updated SSB parameters for a candidate cell or a base station of one target mobility operation via a MAC CE reception. For example, the target mobility operation may correspond to an LTM operation targeting an LTM candidate cell, or may correspond to a (conditional) handover targeting a candidate cell for Layer-3 mobility. The MAC entity 504 may then notify or configure a lower layer (e.g., the PHY entity 502 associated with the MAC entity 504) to implement early DL / UL synchronization and L1 / L3 measurement for the candidate cell based on the updated SSB parameters. For example, the MAC entity 504 may pass the updated SSB parameters (e.g., an SSB periodicity, an SSB position in a burst, an SFN-SSB offset, an SSB sub-carrier spacing, or an SSB transmit power) to the PHY entity 502 via an internal inter-layer interface, such that the PHY entity 502 may re-configure the measurement window, the SSB detection position, and related radio-frequency parameters accordingly.

[0180] Subsequently, the PHY entity 502 may report L1 / L3 measurement results to the MAC entity 504 and / or the RRC entity 506. For example, the L1 / L3 measurement results may include measurements of an RSRP, an RSRQ, a Signal-to-Interference-plus-Noise Ratio (SINR), or another signal quality metric for each of the candidate cells. In some additional implementations, the PHY entity 502 may report one or more fulfilled L1 / L3 triggering events to the RRC entity 506 and / or the MAC entity 504. For example, the PHY entity 502 may evaluate one or more pre-configured trigger conditions (e.g., thresholds and offsets that have been pre-configured to the PHY entity 502 via the RRC entity 506 or the MAC entity 504) and may notify the RRC entity 506 and / or the MAC entity 504 when one or more of the trigger conditions are satisfied.

[0181] In some implementations, the MAC entity 504 may further pass the updated SSB parameters to the RRC entity 506, such that the RRC entity 506 may also be aware of the current SSB configuration being applied by the PHY entity 502. For example, the RRC entity 506 may use the updated SSB parameter information to determine how to process subsequent RRC-level configurations or how to respond to reconfiguration messages from the serving RAN. The “Updated SSB parameters” annotation associated with the interaction between the MAC entity 504 and the RRC entity 506 in FIG. 5 may correspond to such an RRC-side awareness of the current SSB parameters applied at the PHY entity 502.

[0182] The cross-layer SSB parameter adaptation 500 described above may provide certain technical effects. For example, by designating the MAC entity 504 as the responsible entity for SSB parameter update during the (conditional) LTM operation, the cross-layer SSB parameter adaptation 500 may enable the UE to apply updated SSB parameters promptly upon receiving an LTM CSC MAC CE (or upon fulfillment of a conditional LTM triggering event), without waiting for a full RRC-level reconfiguration exchange. As another example, by allowing the PHY entity 502 to report L1 / L3 measurement results and fulfilled L1 / L3 triggering events to both the MAC entity 504 and the RRC entity 506, the cross-layer SSB parameter adaptation 500 may enable both the MAC-level and the RRC-level entities of the UE to maintain a consistent view of the UE's current radio-level state, which may facilitate coordinated decisions across the protocol stack.

[0183] In some other implementations, alternative embodiments of the cross-layer SSB parameter adaptation 500 may be employed. For example, although FIG. 5 illustrates the MAC entity 504 as the entity that directly updates the SSB parameters for the PHY entity 502, in some other implementations the RRC entity 506 may directly pass the updated SSB parameters to the PHY entity 502 in response to an explicit RRC reconfiguration message that carries the updated SSB configuration, and the MAC entity 504 may be bypassed for the SSB parameter update for that particular configuration. As another example, although the PHY entity 502 is described above as reporting the L1 / L3 measurement results to both the MAC entity 504 and the RRC entity 506, in some other implementations the PHY entity 502 may report the L1 / L3 measurement results only to the MAC entity 504, and the MAC entity 504 may forward a filtered or aggregated measurement report to the RRC entity 506.

[0184] Cell DTX Adaptation

[0185] Reference is made to FIG. 6A, FIG. 6B, and FIG. 6C. FIG. 6A is a schematic diagram illustrating SSB configurations applied during a cell Discontinuous Transmission (DTX) active duration and a cell DTX non-active duration in a cell DTX adaptation 600A, according to an example implementation of the present disclosure. FIG. 6B is a schematic diagram illustrating a cell DTX adaptation 600B in which a cell DTX active duration of a candidate cell is inspired by an LTM configuration, according to an example implementation of the present disclosure. FIG. 6C is a schematic diagram illustrating a cell DTX adaptation 600C in which a cell DTX active duration of a candidate cell is interrupted by an LTM cell switch command, according to an example implementation of the present disclosure. The cell DTX adaptations 600A, 600B, and 600C may correspond to mechanisms by which the SSB adaptation may be implemented semi-persistently or dynamically in connection with a cell DTX mechanism applied at the candidate cell.

[0186] In some implementations, the SSB adaptation may be implemented semi-persistently with the cell DTX mechanism. The cell DTX mechanism may correspond to a mechanism by which the candidate cell may suspend a portion of downlink transmissions (e.g., one or more downlink reference signals or downlink control channels) during a cell DTX non-active duration to reduce energy consumption, while resuming the suspended downlink transmissions during a cell DTX active duration. The cell DTX active duration and the cell DTX non-active duration may together form a cell DTX cycle that may be repeated periodically at the candidate cell.

[0187] As shown in FIG. 6A, in the cell DTX adaptation 600A, multiple SSB configurations may be pre-configured for the candidate cell with each SSB configuration being associated with a corresponding portion of the cell DTX cycle. For example, a first SSB configuration (e.g., the SSB#1 configuration) may be pre-configured for application during the cell DTX active duration, and a second SSB configuration (e.g., the SSB#2 configuration) may be pre-configured for application during the cell DTX non-active duration. The first SSB configuration applied during the cell DTX active duration may include at least one of a short periodicity or a dense SSB set pattern, and the second SSB configuration applied during the cell DTX non-active duration may include at least one of a long periodicity or a sparse SSB set pattern. The relative density and the relative periodicity may, for example, be selected so that the candidate cell may broadcast more frequent SSB transmissions during the cell DTX active duration to support real-time measurement and synchronization, while reducing the SSB broadcasting frequency during the cell DTX non-active duration to support energy saving at the candidate cell.

[0188] In some implementations, parameters of the cell DTX cycle (e.g., a time span of the cell DTX cycle, a time span of the cell DTX active duration, a time span of the cell DTX non-active duration, or a start timing of the cell DTX cycle) may be pre-configured to the UE as part of the LTM configuration or the LTM candidate configuration. For example, the parameters may be pre-configured so that the UE may determine, for each portion of the cell DTX cycle, whether the candidate cell is in the cell DTX active duration or the cell DTX non-active duration, and so that the UE may apply the corresponding SSB configuration for measurement and synchronization at each portion of the cell DTX cycle.

[0189] In some implementations, the cell DTX operation of the candidate cell may be modified in connection with an LTM operation. As shown in the cell DTX adaptation 600B of FIG. 6B, the cell DTX active duration of the candidate cell may be inspired (or triggered) by transmission of an LTM (candidate) configuration. For example, the serving RAN may transmit the LTM (candidate) configuration to the UE, and the candidate cell (e.g., the LTM candidate#1) may initiate a new cell DTX active duration in response to or in connection with the transmission of the LTM (candidate) configuration. In some implementations, the LTM candidate#1 may be instructed or informed by the source cell (e.g., the serving cell of the UE) to interrupt an ongoing cell DTX non-active duration and to initiate the new cell DTX active duration during an LTM candidate preparation stage. For example, the source cell may transmit such instruction to the LTM candidate#1 via backhaul signaling carried over an Xn interface or an X2 interface between the source cell and the LTM candidate#1.

[0190] After the LTM candidate#1 receives the instruction from the source cell, the LTM candidate#1 may change, update, or modify the SSB set broadcasting from a current SSB configuration (e.g., the SSB#2 configuration applied during the cell DTX non-active duration) to a different SSB configuration (e.g., the SSB#1 configuration applied during the cell DTX active duration). For example, the LTM candidate#1 may switch from a sparse SSB pattern to a dense SSB pattern so that the UE may perform efficient early DL / UL synchronization and L1 / L3 measurement towards the LTM candidate#1 during the LTM preparation stage. In some implementations, after the cell DTX active duration is terminated, the LTM candidate#1 may switch back to the cell DTX non-active duration that may be associated with the second SSB configuration. For example, the LTM candidate#1 may resume the broadcasting of the SSB#2 configuration once the LTM-specific cell DTX active duration ends.

[0191] In some implementations, the LTM candidate#1 may implement one or more LTM-specific cell DTX active durations during the LTM operation, and the time span of each LTM-specific cell DTX active duration may be decided and configured by the LTM candidate#1. For example, the LTM-specific cell DTX active duration may have a time span that differs from the time span of the cell DTX active duration of the candidate cell prior to the LTM operation. The LTM candidate#1 may forward one or more pieces of information to the source cell of the UE via a backhaul connection. For example, the LTM candidate#1 may forward cell DTX information that may include a time span of the cell DTX cycle, a time span of the cell DTX non-active duration, a time span of the cell DTX active duration, and a start timing of the cell DTX cycle. For example, the LTM candidate#1 may further forward a time span of the LTM-specific cell DTX active duration, where the time span of the LTM-specific cell DTX active duration may differ from the time span of the cell DTX active duration of the candidate cell prior to the LTM operation.

[0192] The cell DTX information may be conveyed to the UE through one or more illustrative paths, and several examples are described below. In some implementations, the source cell may adjust and forward parameters of the cell DTX information (associated with one or more LTM candidates) to the UE based on the frame structure, the sub-carrier spacing, or the timing advance of the source cell. For example, the source cell may translate the parameters from a frame structure of the LTM candidate to a frame structure of the source cell prior to forwarding the parameters to the UE, so that the UE may apply the cell DTX information based on a reference timing of the source cell while the UE is still served by the source cell. In some other implementations, the candidate cell (or the target LTM candidate) may decide and configure the parameters of the cell DTX information (associated with one or more LTM candidates) to the UE based on the frame structure, the sub-carrier spacing, or the timing advance of the candidate cell. For example, the candidate cell may forward the cell DTX information directly to the UE through dedicated signaling or via the source cell, with the parameters expressed based on the frame structure of the candidate cell, so that the UE may apply the cell DTX information based on a reference timing of the candidate cell once the LTM cell switch is completed. The above-described two implementations of the cell DTX information forwarding are provided as illustrative examples, and either implementation may be selected based on the deployment scenario.

[0193] As shown in the cell DTX adaptation 600C of FIG. 6C, in some additional implementations the cell DTX active duration of the candidate cell may be interrupted by an LTM cell switch command. For example, the candidate cell may be in an ongoing cell DTX active duration (e.g., an LTM-specific cell DTX active duration that was previously inspired by transmission of the LTM (candidate) configuration), and the serving RAN may transmit an LTM CSC MAC CE to the UE to instruct the UE to switch to the candidate cell as a new serving cell. The transmission of the LTM CSC MAC CE may serve as an event that interrupts the LTM-specific cell DTX active duration at the candidate cell, since the candidate cell, after the LTM cell switch is completed, may become the new serving cell of the UE and may operate based on a different SSB broadcasting pattern. For example, after the LTM cell switch is completed, the candidate cell may either continue the SSB broadcasting pattern applicable to the cell DTX active duration if the candidate cell is to broadcast the SSB densely as the new serving cell, or may switch to a different SSB broadcasting pattern based on the deployment configuration of the candidate cell as the new serving cell.

[0194] In the cell DTX adaptations 600B and 600C, the signaling flow between the serving RAN and the UE to coordinate the cell DTX operation with the LTM operation may include one or more of the following actions. In action 602, the serving RAN may transmit an LTM (candidate) configuration to the UE. For example, the LTM (candidate) configuration may include one or more LTM candidates and the SSB configurations associated with each LTM candidate, and the transmission of the LTM (candidate) configuration may serve as a triggering event for the candidate cell to initiate the LTM-specific cell DTX active duration as described in the context of FIG. 6B. In action 604, the UE may transmit a response to the serving RAN to acknowledge receipt of the LTM (candidate) configuration. For example, the response may include an RRC reconfiguration complete message transmitted by the UE upon storing the LTM (candidate) configuration. In action 606, the serving RAN may transmit an LTM CSC MAC CE to the UE that may indicate a target cell among the one or more LTM candidates. The LTM CSC MAC CE may, for example, trigger the UE to switch from the source cell to the target cell (e.g., the LTM candidate#1) and to apply the SSB configuration associated with the target cell, and may further serve as the event that interrupts the LTM-specific cell DTX active duration as described in the context of FIG. 6C. In action 608, the UE may transmit an LTM cell switch completion message to the target cell to indicate the successful completion of the LTM cell switch procedure. For example, the LTM cell switch completion message may include an RRC reconfiguration complete message transmitted by the UE upon successful completion of the random access procedure towards the target cell.

[0195] As shown in FIG. 6C, the UE may receive an LTM CSC MAC CE in action 606, and the LTM CSC MAC CE may interrupt an on-going cell DTX cycle. In some implementations, the LTM CSC MAC CE may interrupt an on-going cell DTX active duration. In such implementations, the UE may expect that a cell DTX non-active duration is started directly after the LTM CSC MAC CE is transmitted to the UE. It should be noted that, to support the operation in FIG. 6C, the source cell may inform the LTM candidate#1 that the LTM CSC MAC CE is transmitted to the UE, such that the LTM candidate#1 may interrupt the on-going cell DTX active duration and then start a new cell DTX non-active duration. In some implementations, a pre-synchronization between the source cell and the LTM candidate#1 may be performed to pre-determine a timing at which the LTM candidate#1 interrupts the on-going cell DTX cycle. On the UE side, the UE may also be configured with an additional timing offset, and the UE may adjust its DL / UL synchronization and L1 / L3 measurement based on the cell DTX non-active duration triggered by the LTM candidate#1 after the UE receives the LTM CSC MAC CE.

[0196] An explicit indicator or flag may be configured in the LTM CSC MAC CE. The explicit indicator or flag may explicitly indicate that the cell DTX active duration is to be interrupted, and may further indicate the updated SSB configuration (e.g., SSB#2 as shown in FIG. 6C) for the new cell DTX non-active duration. In addition, the timing offset may also be provided by the serving RAN via the LTM CSC MAC CE, where the UE may adjust the DL / UL synchronization and the L1 / L3 measurement based on the cell DTX non-active duration triggered by the LTM candidate#1 according to the timing offset. In some implementations, the serving RAN may enable the UE to adjust the DL / UL synchronization and the L1 / L3 measurement based on the cell DTX non-active duration triggered by reception of the LTM CSC MAC CE. For example, the serving RAN may enable the operation by an explicit configuration in an LTM configuration, which is generally applied to all of the LTM candidates, or by an explicit configuration in an LTM candidate configuration, which is applied to a specific LTM candidate.

[0197] The cell DTX adaptations 600A, 600B, and 600C described above may provide certain technical effects. For example, by mapping the SSB configurations to the cell DTX active duration and the cell DTX non-active duration, the cell DTX adaptation 600A may align the SSB broadcasting density with the cell DTX cycle so that energy consumption at the candidate cell may be reduced during the cell DTX non-active duration, while measurement and synchronization performed by the UE may remain effective during the cell DTX active duration. As another example, by allowing the cell DTX active duration to be inspired by the LTM (candidate) configuration in the cell DTX adaptation 600B, the candidate cell may temporarily broadcast a denser SSB pattern during the LTM preparation stage to support efficient UE measurement, even when the candidate cell would otherwise be in a cell DTX non-active duration. As yet another example, by allowing the cell DTX active duration to be interrupted by the LTM cell switch command in the cell DTX adaptation 600C, the candidate cell may transition out of the LTM-specific cell DTX active duration once the LTM cell switch is completed, so that the candidate cell may operate based on the SSB broadcasting pattern applicable to the candidate cell as the new serving cell.

[0198] In some other implementations, alternative embodiments of the cell DTX adaptation may be employed. For example, although the cell DTX adaptation 600A is described above as mapping a single SSB configuration to each of the cell DTX active duration and the cell DTX non-active duration, in some other implementations multiple SSB configurations may be mapped to the cell DTX active duration (e.g., one SSB configuration per phase within the cell DTX active duration), and multiple SSB configurations may be mapped to the cell DTX non-active duration. As another example, although the cell DTX adaptation 600B is described above as inspiring the cell DTX active duration based on the transmission of the LTM (candidate) configuration, in some other implementations the cell DTX active duration may be inspired based on an alternative event, such as a reception of an L1 / L3 measurement report from the UE that satisfies a pre-configured condition, or a reception of an inter-node signaling message from a neighboring cell. As yet another example, although the cell DTX adaptation 600C is described above as interrupting the cell DTX active duration based on the LTM CSC MAC CE, in some other implementations the interruption of the cell DTX active duration may be triggered by an alternative event, such as a transmission of an LTM cell switch completion message by the UE or a transmission of a dedicated MAC CE by the serving RAN.

[0199] Any of the cell DTX adaptations 600A, 600B, and 600C may be used in combination with any of the SSB adaptation modes described in the preceding sections (e.g., the Mode 1 of FIG. 1, the Mode 2 of FIG. 2A, the Mode 2a of FIG. 2B, or the Mode 3 of FIG. 3) and with the implicit and explicit SSB adaptation mechanisms described in the context of FIG. 4 and FIG. 5. For example, in some implementations, the cell DTX adaptation 600A may be combined with the Mode 1 SSB adaptation, where the SSB#1 configuration applied during the cell DTX active duration may correspond to the first SSB configuration of Mode 1 and the SSB#2 configuration applied during the cell DTX non-active duration may correspond to the second SSB configuration of Mode 1. The specific combination of the cell DTX adaptation and the SSB adaptation mode may depend on the deployment scenario, the network energy saving target, and the inter-node coordination capability.

[0200] Design#1 - OD-SSB and AW-SSB Configurations for LTM

[0201] The present disclosure further provides an example design (referred to herein as Design#1) in which the candidate cell may broadcast the SSB based on an On-Demand SSB (OD-SSB) configuration, an Always-On SSB (AW-SSB) configuration, or a combination of the OD-SSB configuration and the AW-SSB configuration during different stages of an LTM operation. The OD-SSB configuration may correspond to an SSB configuration that may be broadcast on demand (e.g., upon a network trigger or upon an LTM-related event) rather than being broadcast continuously, and the AW-SSB configuration may correspond to an SSB configuration that may be broadcast continuously by the candidate cell. The Design#1 may, for example, support a Layer-1 mobility operation (e.g., an LTM operation, a conditional LTM operation, a subsequent LTM operation, an inter-Central Unit (CU) LTM operation, or an intra-CU LTM operation), and may also support a Layer-3 mobility operation (e.g., a handover, a conditional handover, or a Dual-Active-Protocol-Stack (DAPS) handover).

[0202] In some implementations, the Design#1 may be applied based on a Radio Access Technology (RAT) supported by a UE, a serving cell, a source cell, or an LTM candidate cell. For example, in some implementations, the UE may support LTM candidates that operate based on a 5G or a 5G-Advanced RAT, and the serving cell, the source cell, or the LTM candidate cell may support a set of SSB periodicities that includes one or more of 5 milliseconds, 10 milliseconds, 20 milliseconds, 40 milliseconds, 80 milliseconds, or 160 milliseconds. For example, in some other implementations, the UE may support LTM candidates that operate based on a 6G RAT, and the serving cell, the source cell, or the LTM candidate cell may support a set of SSB periodicities that includes one or more of 1 millisecond, 2 milliseconds, 3 milliseconds, 4 milliseconds, 5 milliseconds, 10 milliseconds, 20 milliseconds, 40 milliseconds, 80 milliseconds, 160 milliseconds, 320 milliseconds, 640 milliseconds, 1280 milliseconds, 2560 milliseconds, 100 milliseconds, 1000 milliseconds, or another SSB periodicity that may be supported by the 6G RAT. The above-described two implementations of the supported SSB periodicities are provided as illustrative examples, and the supported set of SSB periodicities may include any subset or superset of the above-described values based on the deployment configuration of the UE, the serving cell, the source cell, or the LTM candidate cell.

[0203] The Design#1 may be applied to one or more LTM operation scenarios. For example, the Design#1 may be applied to an inter-CU LTM operation in which a Master Node (MN) and a Secondary Node (SN) are switched simultaneously, an inter-CU LTM operation in which only the MN is switched, an inter-CU LTM operation in which only the SN is switched, an intra-CU LTM operation, an inter-CU conditional LTM operation, an intra-CU conditional LTM operation, an inter-MN LTM operation with or without an inter-SN Primary Secondary Cell (PSCell) change, or an MN-initiated inter-SN LTM operation in which the Master Cell Group (MCG) remains unchanged. The above-described LTM operation scenarios are provided as illustrative examples, and the Design#1 may also be applied to other LTM operation scenarios based on the deployment configuration.

[0204] In the Design#1, the serving cell may configure multiple OD-SSB configurations to the UE by transmitting an OD-SSB configuration list to the UE. Each OD-SSB configuration in the OD-SSB configuration list may be further associated with one or more OD-SSB indices (which may also correspond to one or more SS / PBCH block indices). For example, each OD-SSB configuration may be provided to the UE with one associated OD-SSB configuration index, and the OD-SSB configuration index may be further associated with the one or more OD-SSB indices (or SS / PBCH block indices). The OD-SSB indices may indicate that the candidate cell (e.g., the LTM candidate) may broadcast the SSB in beam directions corresponding to each of the OD-SSB indices. In contrast, the absence of an OD-SSB index in the OD-SSB configuration may indicate that the candidate cell may not broadcast the SSB in the corresponding beam direction.

[0205] In some implementations, an additional bitmap may be provided in the OD-SSB configuration, and each bit of the bitmap may be implicitly associated with one OD-SSB index or beam direction based on an SSB pattern that may be pre-defined in a radio technology specification. For example, the bit sequence in the bitmap may be associated with each OD-SSB index in ascending order or in descending order. The OD-SSB configuration may set one bit of the bitmap to a first value (e.g., ‘1’) when the corresponding beam direction or OD-SSB index is to be broadcast, and may set one bit of the bitmap to a second value (e.g., ‘0’) when the corresponding beam direction or OD-SSB index is not to be broadcast.

[0206] The OD-SSB configuration list may be transmitted to the UE through one or more illustrative paths. For example, the OD-SSB configuration list may be transmitted to the UE via a UE-specific configuration (e.g., via a UE-specific RRC reconfiguration message), or via a broadcast system information message. In some implementations, the serving cell or the source cell may configure one LTM configuration that includes one or more LTM candidates, and an LTM candidate may be further associated with one or more OD-SSB indices. The OD-SSB indices that are associated with the LTM candidate may indicate that the LTM candidate may broadcast the SSB based on the OD-SSB configuration in the beam directions associated with the OD-SSB indices, and the absence of an OD-SSB index from the association of the LTM candidate may indicate that the LTM candidate may not broadcast the SSB in the corresponding beam direction. In some additional implementations, the serving RAN may explicitly configure a per-OD-SSB-index broadcast indicator (e.g., “Broadcast” or “Not Broadcast”) for each OD-SSB index that is associated with one LTM candidate, to indicate whether the LTM candidate may broadcast the SSB based on the OD-SSB configuration corresponding to the OD-SSB index.

[0207] An AW-SSB configuration list may be configured to the UE in a manner that may parallel the OD-SSB configuration list. For example, the serving cell may configure multiple AW-SSB configurations to the UE by transmitting the AW-SSB configuration list to the UE. Each AW-SSB configuration in the AW-SSB configuration list may be further associated with one or more AW-SSB indices. The AW-SSB configuration list may be transmitted to the UE via a UE-specific configuration or via a broadcast system information message. In some implementations, the serving cell or the source cell may configure one LTM configuration that includes one or more LTM candidates, and an LTM candidate may be further associated with one or more AW-SSB indices. The AW-SSB indices that are associated with the LTM candidate may indicate that the LTM candidate may broadcast the SSB based on the AW-SSB configuration in the beam directions associated with the AW-SSB indices.

[0208] In the Design#1, the OD-SSB configuration of one LTM candidate may be configured within an LTM candidate configuration of the LTM candidate. In some implementations, the OD-SSB configuration may be configured along with one or more AW-SSB configurations within the LTM configuration (which may be generally applied to multiple LTM candidates) or within the LTM candidate configuration (which may be applied to one specific LTM candidate). For example, the SSB patterns referenced as SSB#1, SSB#2, or SSB#3 in the preceding sections (e.g., in the Mode 1 of FIG. 1, the Mode 2 of FIG. 2A, or the Mode 2a of FIG. 2B) may be pre-configured to be implemented based on a pre-configured OD-SSB configuration with or without joint implementation with an AW-SSB configuration. The serving RAN may further implement an activation or a de-activation of the OD-SSB configuration based on the implicit or explicit SSB adaptation mechanisms described in the context of FIG. 4.

[0209] An association between the OD-SSB configuration and the LTM candidate may take various forms. In some implementations, the OD-SSB configuration may be associated with one specific LTM candidate. In some other implementations, one OD-SSB configuration may be associated with multiple LTM candidates that may share a common OD-SSB pattern. The OD-SSB configuration may be supported in connection with an intra-CU LTM operation, an inter-CU LTM operation, an intra-cell LTM operation, or an inter-cell LTM operation.

[0210] In some implementations, an LTM candidate may be associated with one or more OD-SSB configurations or one or more AW-SSB configurations. For at least one of the SSB configurations associated with the LTM candidate (within the LTM candidate configuration), the SSB configuration may correspond to an AW-SSB configuration. For example, the UE may not expect to receive an LTM candidate configuration that includes only an OD-SSB configuration without an AW-SSB configuration. For example, the UE may expect each LTM candidate configuration to include at least one AW-SSB configuration. In some implementations, the SSB configuration provided in the LTM candidate configuration may include only the AW-SSB configuration without the OD-SSB configuration. In some implementations, an AW-SSB configuration may be configured within the LTM configuration (e.g., shared by all of the LTM candidates in the LTM configuration), so that the AW-SSB configuration may be applied as a common SSB configuration for the LTM candidates in the LTM configuration.

[0211] In some implementations (e.g., in a 5G-Advanced RAT deployment), all of the LTM candidates in one LTM configuration may be associated with the 5G-Advanced RAT only. In some implementations (e.g., in a 6G RAT deployment), some of the LTM candidates in the LTM configuration may support the 5G-Advanced RAT and other LTM candidates in the LTM configuration may support the 6G RAT. In a deployment in which LTM candidates with multiple RATs co-exist in one LTM configuration, the UE may determine the RAT supported by an LTM candidate through one or more illustrative approaches. For example, in some implementations, the UE may determine the RAT based on an explicit indicator that may indicate the cell type of the LTM candidate (e.g., a “5G-Advanced cell” indicator or a “6G cell” indicator). For example, in some implementations, the UE may implicitly determine the cell type of the LTM candidate by referring to the SSB configurations (e.g., a 5G-Advanced SSB configuration or a 6G SSB configuration) associated with the LTM candidate.

[0212] Dynamic activation and de-activation of the AW-SSB configuration and the OD-SSB configuration may be performed by the serving RAN. In some implementations, the SSB adaptation described in the context of FIG. 4 may be applicable to the OD-SSB configuration and to the AW-SSB configuration independently. In some implementations, the SSB adaptation described in the context of FIG. 4 may be applicable to the OD-SSB configuration and to the AW-SSB configuration jointly. In some implementations, both the implicit SSB adaptation mechanism and the explicit SSB adaptation mechanism may be applied jointly or independently to the OD-SSB configuration and to the AW-SSB configuration.

[0213] The UE may implement DL / UL synchronization and L1 / L3 measurement based on different combinations of the OD-SSB configuration and the AW-SSB configuration. For example, in some implementations, the UE may implement DL / UL synchronization and L1 / L3 measurement based on an SSB burst set associated with the OD-SSB configuration only. For example, in some implementations, the UE may implement DL / UL synchronization and L1 / L3 measurement based on an SSB burst set associated with the AW-SSB configuration only. For example, in some other implementations, the UE may implement DL / UL synchronization and L1 / L3 measurement based on a combination of the SSB burst set associated with the OD-SSB configuration and the SSB burst set associated with the AW-SSB configuration in a time domain, a frequency domain, or a power domain. The UE may further apply one corresponding SMTC configuration based on the SSB burst set (e.g., the OD-SSB only, the AW-SSB only, or the combination of the OD-SSB and the AW-SSB) that is being used by the UE.

[0214] In some implementations, a valid time period may be pre-configured for the OD-SSB configuration or for the AW-SSB configuration. For example, the valid time period may correspond to a time interval during which the candidate cell may broadcast the SSB based on the OD-SSB configuration or the AW-SSB configuration. The valid time period may, for example, be specified as a multiple of a system information modification period (e.g., N times the system information modification period, where N is a positive integer) or in another time unit such as a number of slots, subframes, or radio frames. The UE may consider that the broadcasting of the SSB burst set associated with the OD-SSB configuration may be stopped upon or after the valid time period. In some implementations, the UE may determine whether to perform (DL / UL) synchronization and / or (L1 / L3) measurement only during the pre-configured valid time period of the OD-SSB / AW-SSB.

[0215] An initial state of the OD-SSB configuration or the AW-SSB configuration may be configured by the serving RAN. In some implementations, the serving RAN may indicate one of multiple initial states for the OD-SSB configuration or the AW-SSB configuration. For example, in some implementations, the initial state may indicate that the OD-SSB configuration or the AW-SSB configuration may be activated upon configuration via the RRC signaling. For example, in some implementations, the initial state may indicate that the OD-SSB configuration or the AW-SSB configuration may be de-activated as a default setting upon configuration via the RRC signaling. For example, in some implementations, the initial state may indicate that the OD-SSB configuration or the AW-SSB configuration may be de-activated as a default setting upon configuration via the RRC signaling, and may be activated upon receipt of an LTM cell switch command (e.g., the LTM CSC MAC CE).

[0216] In some implementations, an LTM candidate may be associated with multiple OD-SSB configurations or multiple AW-SSB configurations. To facilitate the LTM operation, the source cell may further configure one default OD-SSB configuration or one default AW-SSB configuration that may be associated with the LTM candidate, where the configured default may be in an activated state to indicate to the UE which OD-SSB or AW-SSB configuration is to be applied for the LTM cell switch. The other OD-SSB or AW-SSB configurations associated with the LTM candidate may be considered de-activated as a default setting. In some other implementations, the source cell may configure the default OD-SSB or AW-SSB configuration that may be associated with the LTM candidate as one that may be activated or de-activated later upon receipt of the LTM cell switch command (e.g., the LTM CSC MAC CE) or upon transmission of the LTM cell switch command by the serving RAN. In some implementations, the first OD-SSB or AW-SSB configuration listed within the OD-SSB or AW-SSB configuration list (associated with one LTM candidate) may be considered, by default, as the activated OD-SSB or AW-SSB configuration that the UE may identify via wireless reference signal measurement and detection.

[0217] In some additional implementations, the serving RAN may not configure the default state (e.g., the activated state or the de-activated state) of the OD-SSB or AW-SSB configuration. Under such implementations, the UE may infer that the serving RAN may further activate one specific OD-SSB or AW-SSB configuration later (e.g., after the UE receives the RRC reconfiguration message that includes the OD-SSB configuration or the LTM configuration).

[0218] Impact on the MAC CE (e.g., the LTM CSC MAC CE)

[0219] In some implementations, an additional bit string or octet may be configured in the LTM MAC CE to include an associated OD-SSB configuration index or an associated AW-SSB configuration index in the LTM MAC CE. In addition, an OD-SSB configuration or an OD-SSB pattern associated with the OD-SSB configuration index may also be pre-configured to the UE via DL control signaling, for example, as part of an LTM configuration or an LTM candidate configuration. The DL control signaling may be, for example, UE-specific RRC signaling or cell-specific broadcast system information.

[0220] In some implementations, only one additional bit for OD-SSB index indication may be provided in the MAC CE. In some other implementations, only one additional bit for AW-SSB index indication may be provided in the MAC CE. Therefore, in the MAC CE or in a sub-header of the MAC CE, an indicator for OD-SSB index indication and / or an indicator for AW-SSB indication may be provided in the same LTM CSC MAC CE. In addition, the LTM CSC MAC CE may further provide an additional indication indicating which bits, bitmaps, flags, or indicators are provided in the MAC CE. For example, the additional indication may indicate that the MAC CE provides both an AW-SSB indicator and an OD-SSB indicator, only an AW-SSB indicator, or only an OD-SSB indicator. For example, the additional indication may be in the form of {AW-SSB & OD-SSB}, {AW-SSB only} or {OD-SSB only}.

[0221] In some implementations, the OD-SSB configuration index or the AW-SSB configuration index may be associated with one, some, or a subset of SSB parameters, and the UE may interpret and measure one or more PBCHs of an LTM candidate based on the configured OD-SSB pattern or the configured AW-SSB pattern.

[0222] In some implementations, one, some, or a subset of OD-SSB parameters or AW-SSB parameters may be configured in the LTM MAC CE.

[0223] In some implementations, the proposed LTM cell switch MAC CE design and the proposed OD-SSB activation and de-activation may also be applicable to configuration, activation, and de-activation of always-on SSB (AW-SSB) operation. For example, an AW-SSB index and an AW-SSB configuration may be pre-configured to the UE as part of an LTM configuration or an LTM candidate configuration. In addition, the serving RAN may further configure an AW-SSB index to the UE via an LTM cell switch MAC CE. In some implementations, an LTM MAC CE may include any combination of an AW-SSB configuration index, an OD-SSB configuration index, or both the AW-SSB configuration index and the OD-SSB configuration index. For example, the LTM MAC CE may include any combinations of {AW-SSB (configuration) index}, {OD-SSB (configuration) index}, and {AW-SSB (configuration) index, OD-SSB (configuration) index}.

[0224] Therefore, after receiving the LTM MAC CE from the serving RAN, the UE may perform one of the following actions for Layer-1 or Layer-3 measurement:

[0225] - Action A) The UE may perform measurement based only on the configured OD-SSB configuration, where the configured OD-SSB configuration is associated with the configured OD-SSB index.

[0226] - Action B) The UE may perform measurement based only on the configured AW-SSB configuration, where the configured AW-SSB configuration is associated with the configured AW-SSB index.

[0227] - Action C) The UE may jointly measure the AW-SSB and the OD-SSB for L1 or L3 measurement.

[0228] In some implementations, the serving RAN may further configure the UE to indicate which one of Action A, Action B, and Action C described above the UE is to perform for measurement. In some implementations, the UE measurement may be pre-configured or pre-defined in a 3GPP specification.

[0229] In some implementations, different LCID values may be respectively configured for a first type of LTM MAC CE and a second type of LTM MAC CE. The first type of LTM MAC CE may include one or more OD-SSB configuration indices, one or more OD-SSB parameters, one or more AW-SSB configuration indices, one or more AW-SSB parameters, or any combination thereof. The second type of LTM MAC CE may include none of the OD-SSB configuration indices, the OD-SSB parameters, the AW-SSB configuration indices, or the AW-SSB parameters. For example, the second type of LTM MAC CE may be the LTM MAC CE used in 3GPP Rel-18 specification.

[0230] In some implementations, the serving RAN may change / modify / update a pre-configured OD-SSB configuration associated with an LTM candidate by transmitting one or more LTM CSC MAC CEs.

[0231] The proposed designs regarding the MAC CE may not be limited to the LTM CSC MAC CE or the LTM SCS MAC CE, and may also be applicable to one or more MAC CEs in 3GPP specification. For example, the proposed designs may also be applicable to a MAC CE for SCell activation or de-activation, or to a MAC CE for TCI state indication.

[0232] Joint Activation of LTM Candidate and SSB Operation

[0233] Reference is made to FIG. 7. FIG. 7 is a schematic diagram illustrating an SSB adaptation 700 between an Always-On SSB (AW-SSB) configuration and an On-Demand SSB (OD-SSB) configuration during an LTM operation, according to an example implementation of the present disclosure. In the SSB adaptation 700, the LTM candidate may be configured to the UE with an initial status of “de-activated”, and may be subsequently activated jointly by the LTM cell switch command (e.g., the LTM CSC MAC CE). The SSB broadcasting at the LTM candidate may transition from the AW-SSB configuration alone to a joint broadcasting of the OD-SSB and the AW-SSB configurations (or to one of the OD-SSB or the AW-SSB configurations) when the LTM candidate is activated, and may further transition to a different SSB broadcasting pattern after the LTM cell switch is completed.

[0234] In some implementations of the SSB adaptation 700 of FIG. 7, one configured LTM candidate may be in a de-activated state when the LTM configuration or the LTM candidate configuration is configured to the UE. Additional information of the LTM candidate initial status (e.g., whether the LTM candidate is in an activated state or a de-activated state at the time the UE receives the LTM candidate configuration) may also be configured to the UE as part of the LTM configuration or the LTM candidate configuration. The LTM candidate initial status may, for example, enable the source cell to defer the activation of certain LTM candidates to a later procedural step (e.g., upon transmission of the LTM CSC MAC CE) so that the UE may avoid performing measurement and synchronization towards the LTM candidates that are not yet to be considered.

[0235] Additional information of the SSB operation during the LTM procedure may be configured to the LTM candidate within the LTM configuration or the LTM candidate configuration. The SSB operation during the LTM procedure may indicate which combination of the OD-SSB configuration and the AW-SSB configuration is to be applied by the UE during the LTM execution stage. For example, in some implementations, the SSB operation during the LTM procedure may be configured as a joint combination of {AW-SSB and OD-SSB}, in which case the UE may apply both the AW-SSB configuration and the OD-SSB configuration during the LTM execution stage. For example, in some implementations, the SSB operation during the LTM procedure may be configured as {AW-SSB only}, in which case the UE may apply only the AW-SSB configuration during the LTM execution stage. For example, in some implementations, the SSB operation during the LTM procedure may be configured as {OD-SSB only}, in which case the UE may apply only the OD-SSB configuration during the LTM execution stage. In some additional implementations, the serving RAN may instruct or indicate the SSB operation during the LTM procedure via a MAC CE (e.g., the LTM SCS command MAC CE or another MAC CE). The AW-SSB configuration and the OD-SSB configuration of the indicated LTM candidate may have already been configured to the UE as part of the LTM configuration or the LTM candidate configuration prior to the MAC CE transmission.

[0236] Similarly, additional information of the SSB operation after the LTM procedure complete may be configured to the LTM candidate within the LTM configuration or the LTM candidate configuration. The SSB operation after the LTM procedure complete may indicate which combination of the OD-SSB configuration and the AW-SSB configuration is to be applied by the UE after the LTM operation is completed (e.g., after the LTM candidate becomes the new serving cell of the UE). For example, in some implementations, the SSB operation after the LTM procedure complete may be configured as the joint combination of {AW-SSB and OD-SSB}, the {AW-SSB only}, or the {OD-SSB only} in a manner that may parallel the SSB operation during the LTM procedure. In some additional implementations, the serving RAN may instruct or indicate the SSB operation after the LTM procedure complete via a MAC CE (e.g., the LTM SCS command MAC CE or another MAC CE).

[0237] The actions illustrated in FIG. 7 may be used to characterize the SSB adaptation 700. In action 702, the UE may receive an LTM candidate configuration from the serving RAN, where the LTM candidate configuration may include one or more LTM candidates (e.g., the LTM candidate#1 and one or more additional LTM candidates) and may indicate that the initial status of the LTM candidate#1 is the de-activated state. For example, the LTM candidate configuration may be received via a UE-specific RRC reconfiguration message, and the UE may transmit one RRCReconfigurationComplete message to the serving RAN as a response to the LTM candidate configuration. In action 704, the UE may track the activation status of the LTM candidate#1 over time. For example, after the UE receives the LTM candidate configuration in action 702, the UE may consider the LTM candidate#1 as in the de-activated state, such that the UE may not implement L1 / L3 measurement towards the LTM candidate#1 during the period in which the LTM candidate#1 remains in the de-activated state. For example, the UE may forgo performing L1 / L3 measurement towards the LTM candidate#1 until the LTM candidate#1 is activated by a subsequent procedural event such as receipt of an LTM SCS MAC CE.

[0238] In action 706, the serving RAN may transmit an LTM SCS MAC CE to the UE that may instruct the UE to initiate an LTM operation with the LTM candidate#1. Based on the initial status of the LTM candidate#1 (e.g., the de-activated state) and the receipt of the LTM SCS MAC CE, the UE may infer that the LTM candidate#1 is jointly activated by the LTM SCS MAC CE. The UE may begin to implement L1 / L3 measurement based on the pre-configured AW-SSB configuration, the pre-configured OD-SSB configuration, or both, in accordance with the configured SSB operation during the LTM procedure. The UE may also determine the SMTC configuration to be used for the L1 / L3 measurement based on the SSB operation during the LTM procedure. In action 708, the LTM cell switch operation may be completed (e.g., upon transmission of the LTM cell switch completion message by the UE or upon successful reception of the first packet transmission by the LTM candidate#1). After action 708, the LTM candidate#1 may become the new serving cell of the UE, and the new serving cell may change, switch, or update the SSB broadcasting patterns (e.g., from the OD-SSB patterns to the AW-SSB patterns, or from the joint {AW-SSB and OD-SSB} broadcasting to the AW-SSB patterns) based on the configured SSB operation after the LTM procedure complete. The UE may further determine the SMTC configuration to be used for the L1 / L3 measurement based on the SSB operation after the LTM procedure complete.

[0239] In some implementations, the activation of one LTM candidate may be implemented by the serving RAN through the transmission or reception of a unified Transmission Configuration Indicator (TCI) States Activation / Deactivation MAC CE. For example, the unified TCI States Activation / Deactivation MAC CE may activate or de-activate one or more TCI states associated with the LTM candidate, and the activation of the TCI states may further imply the activation of the LTM candidate from the perspective of the UE.

[0240] Termination or switch of the OD-SSB transmission may be implemented at the LTM candidate or at the new serving cell after the LTM operation is completed. In some implementations, the candidate cell (e.g., the base station, the eNB, or the gNB) may stop or terminate the OD-SSB transmission after the LTM operation is considered finished. The LTM operation may be considered finished by the UE under one or more illustrative conditions. For example, in some implementations, the LTM operation may be considered finished after the UE transmits an RRCReconfigurationComplete message to the LTM candidate. For example, in some implementations, the LTM operation may be considered finished after the UE successfully completes a random access procedure with the LTM candidate (e.g., when the UE has performed the random access procedure as part of the LTM cell switch operation). For example, in some implementations, the LTM operation may correspond to a Random Access Channel (RACH)-less LTM, and the LTM operation may be considered finished when the UE determines that the network has successfully received the first UL data from the UE.

[0241] After the LTM operation is considered finished, the serving cell (which was originally the LTM candidate) may continue or switch the SSB broadcasting through one or more illustrative paths. For example, in some implementations, the serving cell may continue the AW-SSB broadcasting if the AW-SSB was already broadcast by the LTM candidate jointly with the OD-SSB during the LTM operation. For example, in some implementations, the serving cell may switch from the OD-SSB broadcasting to the AW-SSB broadcasting if the AW-SSB was not broadcast by the LTM candidate jointly with the OD-SSB during the LTM operation. In some implementations, the active AW-SSB or OD-SSB configuration of the serving cell may be changed or switched before, during, or after the LTM cell switch configuration via UE-specific RRC signaling. In some implementations, the active AW-SSB or OD-SSB configuration of the serving cell may be changed or switched before, during, or after the LTM cell switch command reception via the LTM cell switch MAC CE reception. In some implementations, the active AW-SSB or OD-SSB configuration of the serving cell may be changed or switched before, during, or after the LTM cell switch is completed. The UE may, for example, assume that the LTM candidate (which becomes the new serving cell of the UE after the LTM cell switch operation) may broadcast the SSB pattern or the SSB configuration periodically based on the AW-SSB configuration that may also be configured as part of the LTM configuration or the LTM candidate configuration.

[0242] An additional SMTC configuration may be configured to support the L1 / L3 measurement based on the OD-SSB configuration. In some implementations, one or more additional SMTC configurations may be configured to the UE to enable the UE to implement early DL / UL synchronization or L1 / L3 measurement of one LTM candidate while the OD-SSB is configured or activated by the serving RAN. The additional SMTC configuration may be explicitly configured to be associated with one or more LTM candidates, with one or more OD-SSB configurations, or with one or more AW-SSB configurations as part of the LTM configuration or the LTM candidate configuration. In some implementations, the LTM candidates in the LTM configuration may be implemented or associated with one or more frequency carriers, and each frequency carrier in the LTM configuration may be associated with one or more additional SMTC configurations.

[0243] The application timing of the additional SMTC configuration may take various forms. For example, in some implementations, the UE may begin to apply the additional SMTC configuration (associated with one LTM candidate, one OD-SSB configuration, or one operating frequency carrier of the LTM candidate) after receiving the LTM configuration or the LTM candidate configuration. For example, in some implementations, the UE may begin to apply the additional SMTC configuration after receiving the LTM CSC MAC CE. For example, in some implementations, the UE may stop applying the additional SMTC configuration after receiving the LTM CSC MAC CE. For example, in some additional implementations, another SMTC configuration (e.g., a second SMTC configuration or SMTC#2) associated with the AW-SSB configuration of the LTM candidate (which may become the new serving cell of the UE after the LTM operation is considered finished) may be configured to the UE as part of the LTM configuration or the LTM candidate configuration. The UE may begin to implement the SMTC#2 associated with the AW-SSB configuration after receiving the LTM CSC MAC CE, or after the LTM operation is considered finished by the UE.

[0244] In some implementations, the UE may stop applying the additional SMTC configuration (associated with one LTM candidate, one OD-SSB configuration, or one operating frequency carrier of the LTM candidate) after the LTM operation is considered finished by the UE. In such implementations, after the LTM operation is considered finished, the UE may begin to implement the SMTC#2 associated with the AW-SSB configuration of the LTM candidate that becomes the new serving cell.

[0245] Inter-node signaling enhancements may be applied to support the Design#1 in connection with an inter-CU LTM operation or an inter-Distributed-Unit (DU) LTM operation. In some implementations, signaling and indicators related to the LTM candidate may be decided by the LTM candidate and may be transmitted to the source cell via backhaul signaling. In addition, the source cell may inform, configure, or notify the LTM candidate of the UE context, the triggering of the LTM operation, or the transmission of the LTM CSC command. The LTM candidate may further transmit a message to the source cell to indicate whether the LTM operation to the UE is successful or has failed. In some implementations, the inter-node signaling described above may be applicable to the inter-node signaling between an eNB, a gNB, or another base station, or to the inter-node signaling between a Central Unit (CU), a Distributed Unit (DU), or a Control Unit.

[0246] The above-described implementations of the termination or the switch of the OD-SSB transmission, the configuration of the AW-SSB or OD-SSB broadcasting timing, and the application timing of the additional SMTC configuration are provided as illustrative examples, and the candidate cell or the UE may apply any one or any combination of the above-described implementations. For example, in some implementations, the candidate cell may switch from the OD-SSB broadcasting to the AW-SSB broadcasting after the LTM operation is finished, and the UE may simultaneously start applying the SMTC#2 associated with the AW-SSB configuration. The specific combination of the implementations may depend on the deployment scenario, the network energy saving target, and the inter-node coordination capability.

[0247] MAC CE Designs for SSB Configuration Indication

[0248] Reference is made to FIG. 8A and FIG. 8B. FIG. 8A is a schematic diagram illustrating an example MAC CE structure 800A with separate fields for SSB operation during an LTM procedure and SSB operation after LTM completion, according to an example implementation of the present disclosure. FIG. 8B is a schematic diagram illustrating another example MAC CE structure 800B with a field for an activated or de-activated SSB configuration during a mobility operation, according to an example implementation of the present disclosure. The MAC CE structure 800A and the MAC CE structure 800B may correspond to two example implementations of the LTM serving cell switch command MAC CE that may be used by the serving RAN to indicate the SSB configuration or the SSB-related parameters to the UE in connection with the LTM operation.

[0249] In the MAC CE structure 800A of FIG. 8A, the MAC CE may include multiple fields, and several illustrative fields are described below. For example, the MAC CE structure 800A may include a target configuration ID field that may indicate the index of the candidate configuration of the target cell. For example, the MAC CE structure 800A may include a random access preamble index field that may indicate a random access preamble that the UE may transmit to the LTM candidate during a random access procedure of the LTM operation. For example, the MAC CE structure 800A may include a separate field for the SSB operation during the LTM procedure and a separate field for the SSB operation after the LTM procedure complete, where each of the separate fields may indicate one of multiple combinations of the OD-SSB and AW-SSB configurations (e.g., a {AW-SSB and OD-SSB} combination, an {AW-SSB only} indication, or an {OD-SSB only} indication) that the UE may apply at the corresponding stage. For example, the MAC CE structure 800A may include one or more OD-SSB configuration index fields or AW-SSB configuration index fields that may indicate the OD-SSB configuration or the AW-SSB configuration to be activated or de-activated. For example, the MAC CE structure 800A may include a Physical Random Access Channel (PRACH) mask index field, a repetition number field, one or more TCI state identifier fields, or a timing advance command field for the target cell.

[0250] In some implementations, the UE may decide the SS / PBCH index or the PRACH mask index by referring to the indicated OD-SSB index or AW-SSB index that may be indicated in the MAC CE structure 800A. For example, the UE may use the indicated OD-SSB index or AW-SSB index to determine the corresponding SS / PBCH block index that the UE may use for synchronization or random access at the LTM candidate.

[0251] In some implementations, the serving RAN may configure the OD-SSB configuration index or the AW-SSB configuration index in the MAC CE structure 800A for the explicit activation or de-activation of an SSB configuration (e.g., the OD-SSB configuration or the AW-SSB configuration). The MAC CE structure 800A may, for example, support the explicit SSB adaptation mechanism described in the context of FIG. 4. The serving RAN may further pre-configure the OD-SSB configuration index or the AW-SSB configuration index that may be applied at different procedural timings (e.g., upon receipt of the LTM CSC MAC CE or upon transmission of the LTM cell switch completion message) for the implicit SSB adaptation mechanism described in the context of FIG. 4.

[0252] In some additional implementations, the serving RAN may pre-configure or activate an AW-SSB configuration or an OD-SSB configuration via the implicit SSB adaptation mechanism (e.g., during the LTM candidate configuration) and may activate one OD-SSB configuration via the explicit SSB adaptation mechanism (e.g., by providing the OD-SSB configuration in the LTM CSC MAC CE). In some additional implementations, the serving RAN may pre-configure or activate an OD-SSB configuration via the implicit SSB adaptation mechanism (e.g., during the LTM candidate configuration), and the UE may de-activate the OD-SSB configuration via the implicit SSB adaptation mechanism (e.g., after transmitting the LTM cell switch completion message to the LTM candidate).

[0253] In the MAC CE structure 800B of FIG. 8B, the MAC CE may include a single field that may indicate the activated or de-activated SSB configuration during the mobility operation, instead of the separate fields used in the MAC CE structure 800A for the SSB operation during the LTM procedure and the SSB operation after the LTM procedure complete. For example, the MAC CE structure 800B may include the same target configuration ID, random access preamble index, OD-SSB or AW-SSB configuration index, PRACH mask index, repetition number, TCI state identifier, and timing advance command fields that are described above in the MAC CE structure 800A. The single SSB configuration field of the MAC CE structure 800B may indicate one combination of the OD-SSB and AW-SSB configurations (e.g., a {AW-SSB and OD-SSB} combination, an {AW-SSB only} indication, or an {OD-SSB only} indication) that the UE may apply throughout the mobility operation, including the LTM execution stage and the post-LTM serving-cell stage.

[0254] The MAC CE structures 800A and 800B described above may provide certain technical effects. For example, by including separate fields for the SSB operation during the LTM procedure and the SSB operation after the LTM procedure complete, the MAC CE structure 800A may enable the serving RAN to flexibly indicate different SSB configurations or different SSB configuration combinations for the LTM execution stage and the post-LTM serving-cell stage, such that the SSB broadcasting at the LTM candidate may be tailored to the deployment requirement at each stage. As another example, by consolidating the SSB configuration indication into a single field in the MAC CE structure 800B, the MAC CE structure 800B may reduce the signaling overhead in deployments where the SSB configuration during the LTM execution stage and the SSB configuration after the LTM procedure complete are intended to be aligned.

[0255] In some other implementations, alternative embodiments of the MAC CE structures 800A and 800B may be employed. For example, although the MAC CE structures 800A and 800B are described above as being based on the LTM serving cell switch command MAC CE, in some other implementations the MAC CE structures may alternatively be based on a dedicated MAC CE other than the LTM serving cell switch command MAC CE, on a downlink control information (DCI), or on an RRC reconfiguration message, or on a combination thereof. As another example, although the MAC CE structure 800A is described above as including separate fields for the SSB operation during the LTM procedure and the SSB operation after the LTM procedure complete, in some other implementations the MAC CE structure 800A may include additional separate fields for SSB operations at additional stages of the LTM operation (e.g., a separate field for the SSB operation during the LTM preparation stage). As yet another example, although the MAC CE structures 800A and 800B are described above as carrying the SSB configuration indication for one LTM candidate, in some other implementations the MAC CE structures may carry the SSB configuration indication for multiple LTM candidates jointly, with one set of fields per LTM candidate.

[0256] Any of the OD-SSB and AW-SSB configurations described in this section may be used in combination with any of the SSB adaptation modes described in the preceding sections (e.g., the Mode 1 of FIG. 1, the Mode 2 of FIG. 2A, the Mode 2a of FIG. 2B, or the Mode 3 of FIG. 3), with the implicit and explicit SSB adaptation mechanisms described in the context of FIG. 4 and FIG. 5, and with the cell DTX adaptations described in the context of FIG. 6A, FIG. 6B, and FIG. 6C. The specific combination may depend on the deployment scenario, the network energy saving target, and the inter-node coordination capability.

[0257] LTM Serving Cell Switch Signaling Procedure

[0258] Reference is made to FIG. 9. FIG. 9 is a signaling flow diagram illustrating an LTM Serving Cell Switch (LTM SCS) procedure 900, according to an example implementation of the present disclosure. The LTM SCS procedure 900 may be performed between a UE, a gNB (or another base station of the serving RAN), and one or more LTM candidate cells. The LTM SCS procedure 900 may, for example, support an LTM operation triggered by an LTM cell switch command MAC CE from the serving RAN, and may also support a conditional LTM operation triggered by the UE upon fulfillment of one or more pre-configured triggering events.

[0259] The LTM SCS procedure 900 may be organized into a sequence of phases from the perspective of the UE. The sequence of phases may include an LTM preparation phase 902, an Early sync phase 904, an LTM cell switch execution phase 906, and an LTM cell switch completion phase 908. Each of the phases 902, 904, 906, and 908 may include one or more actions or events performed by the UE, the gNB, or one or more of the LTM candidate cells as described below.

[0260] At the start of the LTM SCS procedure 900, the UE may be in an RRC_CONNECTED state 910 with the gNB. In the RRC_CONNECTED state 910, the UE may have an established RRC connection with the gNB and may be configured to perform one or more measurement tasks on one or more neighboring cells.

[0261] In the LTM preparation phase 902, the UE and the gNB may exchange signaling to prepare one or more LTM candidate configurations for subsequent use. In action 912, the UE may transmit a measurement report message (e.g., a MeasurementReport message) to the gNB. The measurement report may include one or more L1 measurement results or L3 measurement results that the UE has obtained from the one or more neighboring cells. In action 914, the gNB may, based on the measurement report received in action 912, perform an LTM candidate preparation. The LTM candidate preparation may include the gNB determining to configure the LTM operation for the UE, selecting one or more LTM candidate cells from among a set of neighboring cells indicated by the measurement report, and coordinating with each of the selected LTM candidate cells via inter-node signaling (e.g., via an Xn interface, an X2 interface, or an F1-C interface) to prepare a respective candidate configuration for each of the selected LTM candidate cells. In action 916, the gNB may transmit an RRC reconfiguration message (e.g., an RRCReconfiguration message) to the UE, where the RRC reconfiguration message may include the LTM candidate configurations prepared in action 914. The LTM candidate configurations may, for example, include one or more LTM candidates, the SSB configurations associated with each LTM candidate (e.g., the OD-SSB configuration or the AW-SSB configuration described in the context of FIG. 7), the cell DTX information associated with each LTM candidate (e.g., the cell DTX cycle parameters described in the context of FIG. 6A, FIG. 6B, and FIG. 6C), random access parameters, and one or more conditional LTM triggering events that may be associated with the LTM candidates. Upon receiving the RRC reconfiguration message, the UE may store the LTM candidate configurations (e.g., in a local memory of the UE), so that the LTM candidate configurations may be applied by the UE during one or more subsequent phases of the LTM SCS procedure 900 (e.g., during the Early sync phase 904, during the LTM cell switch execution phase 906, or during the LTM cell switch completion phase 908). In action 918, the UE may transmit an RRC reconfiguration complete message (e.g., an RRCReconfigurationComplete message) to the gNB to acknowledge that the LTM candidate configurations received in action 916 have been successfully stored at the UE. The LTM preparation phase 902 may conclude upon completion of action 918.

[0262] In the Early sync phase 904, the UE may perform early synchronization and measurement with the one or more LTM candidate cells before receiving the LTM cell switch command. In action 920, the UE may perform DL synchronization with one or more of the LTM candidate cells. For example, the UE may activate or de-activate Transmission Configuration Indicator (TCI) states of the LTM candidate cells as triggered by the gNB. The DL synchronization may include the UE detecting the SSB burst set broadcast by each of the LTM candidate cells based on the SSB configuration that has been configured for the corresponding LTM candidate. In action 922, the UE may perform UL synchronization with the one or more LTM candidate cells. For example, the UL synchronization may be performed by using a UE-based Timing Advance (TA) measurement (when the UE-based TA measurement is configured), or by transmitting a preamble towards the LTM candidate cell as triggered by the gNB. When the UE-based TA measurement is configured, the UE may acquire the TA value of the LTM candidate cell by measurement. The UE may further perform an early TA acquisition with the LTM candidate cells as requested by the network before receiving the LTM cell switch command. For example, the early TA acquisition may be performed via a Contention-Free Random Access (CFRA) that may be triggered by a Physical Downlink Control Channel (PDCCH) order from the source cell, following which the UE may transmit a preamble towards the indicated LTM candidate cell. To minimize a data interruption at the source cell due to the CFRA towards the LTM candidate cells, the UE may not receive a random access response from the network for the purpose of the TA value acquisition, and the TA value of the LTM candidate cell may be indicated in the LTM cell switch command. For example, the UE may forgo receiving the random access response and may instead obtain the TA value directly from the LTM cell switch command. The UE may not maintain a TA timer for the LTM candidate cell and may rely on a network implementation to maintain the TA validity. For example, the UE may forgo maintaining the TA timer and may instead apply the TA value provided by the network for the duration of the LTM operation. In action 924, the UE may perform L1 measurements on the configured LTM candidate cells and may transmit one or more L1 measurement reports to the gNB. The L1 measurements may be performed by the UE while the LTM candidate configurations received in action 916 remain applicable to the UE. In action 926, the gNB may make an LTM decision based on one or more of the L1 measurement reports received in action 924, the UL synchronization information obtained in action 922, or other information available at the gNB. For example, the LTM decision may include selecting a target cell from among the one or more LTM candidate cells for a subsequent LTM cell switch. The Early sync phase 904 may conclude upon completion of action 926.

[0263] In the LTM cell switch execution phase 906, the gNB and the UE may cooperate to execute the cell switch to the target cell selected in action 926. In action 928, the gNB may transmit an LTM cell switch command MAC CE that may trigger the cell switch. For example, the LTM cell switch command MAC CE may include a target configuration ID that may indicate the index of the candidate configuration of the target cell, a beam indicator that may indicate one TCI state or beams indicated with DL and UL TCI states, and a timing advance command for the target cell (when available). In action 930, the UE may detach from the source cell and may apply the target configurations indicated by the LTM cell switch command MAC CE received in action 928. For example, the UE may stop monitoring the source cell for downlink transmissions, release one or more radio resources associated with the source cell, apply the candidate configuration indicated by the target configuration ID, and prepare to initiate a random access procedure towards the target cell. The LTM cell switch execution phase 906 may conclude upon completion of action 930.

[0264] In the LTM cell switch completion phase 908, the UE may complete the cell switch by establishing a connection with the target cell. In action 932, the UE may perform a random access (RACH) procedure towards the target cell when the UE does not have a valid TA value of the target cell. For example, the random access procedure may include the UE transmitting a preamble towards the target cell, receiving a random access response from the target cell, and exchanging additional random access messages with the target cell as needed to complete the random access procedure. In action 934, the UE may transmit an LTM cell switch completion message (e.g., an RRCReconfigurationComplete message) to the target cell to indicate successful completion of the LTM cell switch. When the UE has performed the random access procedure in action 932, the UE may consider the LTM cell switch execution as successfully completed when the random access procedure is successfully completed. For a RACH-less LTM operation, the UE may consider the LTM cell switch execution as successfully completed when the UE determines that the network has successfully received the first UL data from the UE. In response to receiving the LTM cell switch completion message transmitted in action 934, the gNB may consider the LTM SCS procedure 900 as successfully completed and may release the source cell resources associated with the UE. For example, the gNB may release the source cell configuration, the source cell radio bearers, and the source cell security context associated with the UE. In the context of SSB adaptation, the gNB may, in response to receiving the LTM cell switch completion message, coordinate with the target cell to begin broadcasting an SSB burst set based on a second SSB configuration (e.g., the OD-SSB configuration) from the target cell, and may deactivate a first SSB configuration (e.g., the AW-SSB configuration) that was used by the UE for measurement prior to the cell switch.

[0265] In some implementations, the serving RAN may configure or enable the UE to implement a conditional LTM operation towards one or more LTM candidates. In some implementations, the LTM candidates configured for the conditional LTM may be jointly configured to the UE within one LTM configuration that also includes other LTM candidates for which the UE may trigger the LTM operation only upon receipt of the LTM cell switch command MAC CE. In some other implementations, the LTM candidates configured for the conditional LTM may be configured separately to the UE within a separate conditional LTM configuration. To support the conditional LTM operation, the UE may be configured with one or more L1 or L3 measurement-based triggering events that may be associated with one LTM candidate. The UE may begin to evaluate the configured L1 or L3 triggering events after receiving the (conditional) LTM configuration. Upon fulfillment of the L1 or L3 triggering events associated with one LTM candidate, the UE may trigger the LTM operation with the LTM candidate without receiving the LTM cell switch command MAC CE from the serving RAN. For a conditional LTM operation, action 928 may be omitted, and the UE may transition from the Early sync phase 904 directly to the LTM cell switch execution phase 906 upon fulfillment of the L1 or L3 triggering events. In the subsequent phases 906 and 908 of the LTM SCS procedure 900, the UE may or may not initiate the random access procedure of action 932 to complete the conditional LTM cell switch operation.

[0266] The actions 920 through 934 may be performed multiple times for subsequent LTM cell switch executions using the LTM candidate configurations provided in action 916. For example, after a first LTM cell switch from the source cell to a first target cell has been completed via the actions 920 through 934, the UE may perform one or more subsequent LTM cell switches from the first target cell to a second target cell (or back to the source cell, or to another LTM candidate cell) via one or more repetitions of the actions 920 through 934, without repeating the LTM preparation phase 902.

[0267] The procedure over the air interface described in FIG. 9 may be applicable to both an intra-gNB-DU LTM operation and an inter-gNB-DU LTM operation. The overall LTM procedure over an F1-C interface (e.g., between a gNB-CU and a gNB-DU) may be supported through a corresponding inter-node signaling procedure between the gNB-CU and the gNB-DU.

[0268] Example Reference Information Elements for SSB Configuration

[0269] The following describes example reference information elements (IEs) that may be used by the serving RAN to configure the SSB-related parameters at the UE in connection with the SSB adaptation designs described above. The IE structures, the field names, the field types, the value ranges, and the optional or mandatory designations of the example IEs are provided as illustrative examples, and other IE structures with different fields, types, value ranges, or designations may be employed without departing from the scope of the present disclosure.

[0270] In some implementations, an example serving cell configuration common information element (referred to herein as the ServingCellConfigCommon IE) may be transmitted by the serving RAN to the UE to configure common parameters of a serving cell. The ServingCellConfigCommon IE may include one or more of the following fields. The ServingCellConfigCommon IE may include a physical cell identifier field (e.g., a physCellId field) that may indicate the physical cell identifier of the serving cell, where the physical cell identifier field may take values from a physical cell identifier type (e.g., a PhysCellId type). In some implementations, the physical cell identifier field may be optional and may be conditioned on a handover procedure or a serving cell addition procedure.

[0271] The ServingCellConfigCommon IE may further include a downlink configuration field (e.g., a downlinkConfigCommon field) that may include downlink common configuration parameters of the serving cell. The downlink configuration field may take values from a downlink configuration type (e.g., a DownlinkConfigCommon type). In some implementations, the downlink configuration field may be optional and may be conditioned on a handover procedure or a serving cell addition procedure.

[0272] The ServingCellConfigCommon IE may further include an uplink configuration field (e.g., an uplinkConfigCommon field) that may include uplink common configuration parameters of the serving cell. The uplink configuration field may take values from an uplink configuration type (e.g., an UplinkConfigCommon type). In some implementations, the uplink configuration field may be optional, and a previously configured value of the uplink configuration field may be retained when the uplink configuration field is not provided in a current configuration.

[0273] The ServingCellConfigCommon IE may further include a supplementary uplink configuration field (e.g., a supplementaryUplinkConfig field) that may include supplementary uplink common configuration parameters of the serving cell. The supplementary uplink configuration field may take values from an uplink configuration type (e.g., the same UplinkConfigCommon type as the uplink configuration field). In some implementations, the supplementary uplink configuration field may be optional, and the supplementary uplink configuration field may be released when not provided in a current configuration.

[0274] The ServingCellConfigCommon IE may further include a timing advance offset field (e.g., an n-TimingAdvanceOffset field) that may indicate one of multiple predefined timing advance offset values. For example, the timing advance offset field may indicate an integer offset value selected from a set of predefined integer offset values, where the set of predefined integer offset values may include one or more of 0, 25600, or 39936. The above-described three predefined integer offset values are provided as illustrative examples, and other integer offset values may be defined depending on the deployment configuration. In some implementations, the timing advance offset field may be optional, and a previously configured value of the timing advance offset field may be retained when the timing advance offset field is not provided in a current configuration.

[0275] The ServingCellConfigCommon IE may further include an SSB positions in burst field (e.g., an ssb-PositionsInBurst field) that may indicate the time domain positions of the transmitted SS / PBCH blocks in a half-frame. The SSB positions in burst field may be implemented as one of multiple choices that may correspond to bitmaps of different lengths. For example, the SSB positions in burst field may be implemented as a short bitmap of 4 bits, a medium bitmap of 8 bits, or a long bitmap of 64 bits. Each bit of the bitmap may correspond to a respective SS / PBCH block index. For example, the leftmost bit of the bitmap may correspond to an SS / PBCH block index 0, the second bit may correspond to an SS / PBCH block index 1, the third bit may correspond to an SS / PBCH block index 2, and the n-th bit may correspond to an SS / PBCH block index of (n minus 1). A bit value of “1” in the bitmap may indicate that the corresponding SS / PBCH block is transmitted, and a bit value of “0” in the bitmap may indicate that the corresponding SS / PBCH block is not transmitted. The serving RAN may configure the same bitmap pattern in the SSB positions in burst field of the ServingCellConfigCommon IE as in a corresponding field of a serving cell configuration common system information block (e.g., a ServingCellConfigCommonSIB).

[0276] For an operation in a shared spectrum channel access deployment, the SSB positions in burst field may indicate one or more candidate SS / PBCH blocks that may be transmitted within a discovery burst transmission window. When the k-th bit of the SSB positions in burst field is set to “1”, the UE may assume that one or more SS / PBCH blocks within the discovery burst transmission window with candidate SS / PBCH block indexes corresponding to an SS / PBCH block index equal to k minus 1 may be transmitted. When the k-th bit of the SSB positions in burst field is set to “0”, the UE may assume that the corresponding SS / PBCH block is not transmitted. The k-th bit may be set to “0” when k is greater than an SSB position quasi-co-location parameter (e.g., an ssb-PositionQCL parameter), and the number of actually transmitted SS / PBCH blocks may not be larger than the number of bits set to “1” in the bitmap. For an operation in a shared spectrum channel access deployment in a Frequency Range 1 (FR1), the medium bitmap may be applied. For an operation in a shared spectrum channel access deployment in a Frequency Range 2 sub-range 2 (FR2-2), the long bitmap may be applied.

[0277] An example representation of the ServingCellConfigCommon IE described above is shown in Table 1 below.

[0278] The fields, the field types, the value ranges, and the optional or conditional designations shown in Table 1 are provided as illustrative examples. In some implementations, the ServingCellConfigCommon IE may include additional fields not shown in Table 1, or one or more of the fields shown in Table 1 may be omitted or modified depending on the deployment configuration of the serving RAN and the UE.

[0279] In some implementations, an example SSB configuration information element (referred to herein as the SSB-Configuration IE) may be transmitted by the serving RAN to the UE to configure parameters of an SSB. The SSB-Configuration IE may include one or more of the following fields. The SSB-Configuration IE may include an SSB frequency field (e.g., an ssb-Freq field) that may indicate a frequency of the SSB, where the SSB frequency field may take values from an absolute radio-frequency channel number type (e.g., an ARFCN-ValueNR type).

[0280] The SSB-Configuration IE may further include a half-frame index field (e.g., a halfFrameIndex field) that may indicate which of two half-frame positions within a frame the SSB is transmitted in. For example, the half-frame index field may indicate one of two enumerated values, where the two enumerated values may include a value indicating a first half-frame (e.g., a value of “zero”) and a value indicating a second half-frame (e.g., a value of “one”).

[0281] The SSB-Configuration IE may further include an SSB sub-carrier spacing field (e.g., an ssbSubcarrierSpacing field) that may indicate the sub-carrier spacing of the SSB. The SSB sub-carrier spacing field may take values from a sub-carrier spacing type (e.g., a SubcarrierSpacing type). The applicable sub-carrier spacing values may depend on the operating frequency of the SSB. For example, in some implementations, the SSB sub-carrier spacing field may indicate a sub-carrier spacing of 15 kHz or 30 kHz for an operation in an FR1 deployment. For example, in some implementations, the SSB sub-carrier spacing field may indicate a sub-carrier spacing of 120 kHz or 240 kHz for an operation in a Frequency Range 2 sub-range 1 (FR2-1) deployment. For example, in some implementations, the SSB sub-carrier spacing field may indicate a sub-carrier spacing of 120 kHz, 480 kHz, or 960 kHz for an operation in an FR2-2 deployment.

[0282] The SSB-Configuration IE may further include an SSB periodicity field (e.g., an ssb-Periodicity field) that may indicate one of multiple periodicity values applicable to the SSB. For example, the SSB periodicity field may indicate a periodicity selected from a set of predefined periodicities, where the set of predefined periodicities may include one or more of 5 milliseconds, 10 milliseconds, 20 milliseconds, 40 milliseconds, 80 milliseconds, or 160 milliseconds. The above-described periodicity values are provided as illustrative examples, and other periodicity values may be defined depending on the deployment configuration (e.g., one or more of 1 millisecond, 2 milliseconds, 3 milliseconds, 4 milliseconds, 320 milliseconds, 640 milliseconds, 1280 milliseconds, 2560 milliseconds, 100 milliseconds, or 1000 milliseconds for a 6G RAT deployment). The SSB periodicity field may further include one or more spare values that may be reserved for future use. In some implementations, the SSB periodicity field may be optional, and a previously configured value of the SSB periodicity field may be retained when the SSB periodicity field is not provided in a current configuration.

[0283] The SSB-Configuration IE may further include a system frame number zero offset field (e.g., an sfn0-Offset field) that may include one or more sub-fields. For example, the system frame number zero offset field may include a frame offset sub-field (e.g., an sfn-Offset sub-field) that may indicate an integer frame offset value, where the integer frame offset value may be selected from a range from 0 to 1023. For example, the system frame number zero offset field may further include an integer subframe offset sub-field (e.g., an integerSubframeOffset sub-field) that may indicate an integer subframe offset value, where the integer subframe offset value may be selected from a range from 0 to 9. In some implementations, the integer subframe offset sub-field may be optional, and the integer subframe offset sub-field may be released when not provided in a current configuration. In some implementations, the system frame number zero offset field as a whole may be optional, and the system frame number zero offset field may be released when not provided in a current configuration.

[0284] The SSB-Configuration IE may further include a system frame number SSB offset field (e.g., an sfn-SSB-Offset field) that may indicate an integer SSB offset value applied with reference to the system frame number. For example, the integer SSB offset value may be selected from a range from 0 to 15.

[0285] The SSB-Configuration IE may further include an SSB transmit power field (e.g., an ss-PBCH-BlockPower field) that may indicate the transmit power level of the SSB (e.g., expressed in decibel-milliwatts (dBm)). For example, the SSB transmit power field may take an integer value selected from a range from - 60 to 50. In some implementations, the SSB transmit power field may be optional and may be conditioned on a path-loss-related operation.

[0286] An example representation of the SSB-Configuration IE described above is shown in Table 2 below.

[0287] The fields, the field types, the value ranges, and the optional or conditional designations shown in Table 2 are provided as illustrative examples. In some implementations, the SSB-Configuration IE may include additional fields not shown in Table 2, or one or more of the fields shown in Table 2 may be omitted or modified depending on the deployment configuration of the serving RAN and the UE.

[0288] In some implementations, an example SSB neighbor cell information element (referred to herein as the SSB-InfoNcell IE) may be transmitted by the serving RAN to the UE to convey SSB-related information of a neighboring cell. The SSB-InfoNcell IE may include one or more of the following fields. The SSB-InfoNcell IE may include a physical cell identifier field (e.g., a physicalCellId field) that may indicate the physical cell identifier of the neighboring cell, where the physical cell identifier field may take values from a physical cell identifier type (e.g., a PhysCellId type).

[0289] The SSB-InfoNcell IE may further include an SSB index field (e.g., an ssb-IndexNcell field) that may indicate an SSB index of the neighboring cell, where the SSB index field may take values from an SSB index type (e.g., an SSB-Index type). In some implementations, the SSB index field may be optional, and a previously configured value of the SSB index field may be retained when the SSB index field is not provided in a current configuration.

[0290] The SSB-InfoNcell IE may further include an SSB configuration field (e.g., an ssb-Configuration field) that may include an SSB configuration information element associated with the neighboring cell (e.g., the SSB-Configuration IE described above). In some implementations, the SSB configuration field may be optional, and a previously configured value of the SSB configuration field may be retained when the SSB configuration field is not provided in a current configuration. The SSB-InfoNcell IE may, for example, be used by the serving RAN to provide neighbor cell SSB information to the UE for L1 measurement or L3 measurement of the neighboring cell.

[0291] An example representation of the SSB-InfoNcell IE described above is shown in Table 3 below.

[0292] The fields, the field types, the value ranges, and the optional or conditional designations shown in Table 3 are provided as illustrative examples. In some implementations, the SSB-InfoNcell IE may include additional fields not shown in Table 3, or one or more of the fields shown in Table 3 may be omitted or modified depending on the deployment configuration of the serving RAN and the UE.

[0293] In some implementations, an example SSB mobility configuration information element (referred to herein as the SSB-ConfigMobility IE) may be transmitted by the serving RAN to the UE to support mobility-related SSB measurement and synchronization. The SSB-ConfigMobility IE may include one or more parameters that may indicate, for example, whether an SSB index of a neighboring cell is to be derived from the serving cell (e.g., one or more deriveSSB-IndexFromCell-related parameters), and which SSB indices the UE may include in the L1 or L3 measurement of the neighboring cell (e.g., one or more SSB-to-measure parameters). The SSB-ConfigMobility IE may, for example, be used in connection with the SSB adaptation designs described in the present disclosure to facilitate the UE in determining which SSB indices to detect and measure based on the configured mobility operation.

[0294] The example ServingCellConfigCommon IE, the example SSB-Configuration IE, the example SSB-InfoNcell IE, and the example SSB-ConfigMobility IE described above are provided as illustrative examples. In some implementations, one or more of the example IEs may include additional fields not described above, or one or more of the fields described above may be omitted. In some implementations, the field names, the field types, the value ranges, or the optional or mandatory designations of the example IEs may be modified based on the deployment configuration of the serving RAN and the UE. The example IEs described above may be used individually or in any combination, and the serving RAN and the UE may use any IE structure that conveys the SSB-related parameters in a manner that supports the SSB adaptation designs described in the present disclosure.

[0295] In some implementations, a method for SSB adaptation performed by a UE may include:   -  receiving multiple SSB configurations from the serving RAN;   -  performing early DL / UL synchronization and L1 / L3 measurement with a (LTM) candidate cell based on a first SSB configuration associated with the LTM candidate cell among the SSB configurations, during a mobility operation;   -  receiving an explicit signaling that indicates the de-activation of the first SSB configuration and / or the activation of a second SSB configuration;   -  performing deactivation of the first SSB configuration and / or activation of the second SSB configuration based on the received explicit signaling; and   -  performing DL / UL synchronization and L1 / L3 measurement based on the second SSB configuration and an SMTC configuration.

[0296] In some implementations, the SMTC configuration may be associated with the second SSB configuration.

[0297] In some implementations, the UE may change from the first SSB configuration to the second SSB configuration upon transmitting an LTM cell switch completion message to a candidate cell of the mobility operation.

[0298] In some implementations, the UE may change from the first SSB configuration to the second SSB configuration upon UE transmitting an RRCReconfigurationComplete message to the source cell or to a candidate cell of the mobility operation.

[0299] In some implementations, the first SSB configuration and the second SSB configuration may be configured by the serving RAN, and the first SSB configuration and the second SSB configuration may be associated with different parameters. For example, the first SSB configuration and the second SSB configuration may be respectively configured by the source cell and by the LTM candidate cell, or may be jointly configured by the LTM candidate cell. The different parameters may include at least one of ssb-PositionsInBurst, ssb-periodicity, sfn-SSB-Offset, ss-PBCH-BlockPower, or ssb-Freq.

[0300] In some implementations, the mobility operation includes an L1 mobility operation (e.g., LTM, conditional LTM, subsequent LTM, inter-CU LTM, intra-CU LTM) or an L3 mobility operation (e.g., handover, conditional handover, DAPS handover).

[0301] FIG. 10 is a flowchart illustrating a method / process 1000 performed by a UE for performing an SSB adaptation operation, according to an example implementation of the present disclosure. In the action 1002, the process 1000 may start by receiving, from a BS via a serving cell, an RRC reconfiguration message including a first SSB configuration and a second SSB configuration for a candidate cell. For example, the serving cell via which the UE receives the RRC reconfiguration message may correspond to a source cell of the mobility procedure, and the BS may determine the first SSB configuration and the second SSB configuration for the candidate cell based on inter-cell signaling exchanged between the source cell and the candidate cell prior to transmitting the RRC reconfiguration message. In some implementations, the first SSB configuration may be associated with a first SSB burst set of the candidate cell, and the second SSB configuration may be associated with a second SSB burst set of the candidate cell that differs from the first SSB burst set in at least one transmission characteristic.

[0302] In the action 1004, the process 1000 may receive, from the BS via the serving cell, an explicit signaling. For example, the explicit signaling may correspond to the RRC reconfiguration message received in the action 1002 itself, or may correspond to a separate signaling transmitted by the BS after the RRC reconfiguration message, such as a MAC CE or another RRC signaling. The BS may transmit the explicit signaling at a timing coordinated with the candidate cell via inter-cell signaling, such that the change of the parameter for SSB-based measurement at the UE is aligned with a change in the SSB transmission pattern of the candidate cell.

[0303] In the action 1006, in response to receiving the explicit signaling, the process 1000 may change a parameter for SSB-based measurement for a mobility procedure associated with the candidate cell from a first value to a second value. For example, the first value may correspond to the first SSB configuration being activated for SSB-based measurement of the candidate cell, and the second value may correspond to the second SSB configuration being activated for SSB-based measurement of the candidate cell. In some implementations, changing the parameter from the first value to the second value may include deactivating the first SSB configuration, activating the second SSB configuration, or both deactivating the first SSB configuration and activating the second SSB configuration. The change of the parameter may cause the UE to transition from monitoring the first SSB burst set of the candidate cell to monitoring the second SSB burst set of the candidate cell.

[0304] In the action 1008, the process 1000 may perform the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value. The process 1000 may then end. For example, performing the SSB-based measurement based on the second value may include detecting the second SSB burst set from the candidate cell based on the second SSB configuration, and performing a L1 measurement or a L3 measurement on the second SSB burst set. The measurement result may be used by the UE to support the mobility procedure with respect to the candidate cell, such as determining whether one or more triggering conditions associated with the candidate cell are fulfilled, or reporting the measurement result to the BS via the serving cell for network-controlled mobility decisions.

[0305] The steps / actions shown in FIG. 10 should not be construed as necessarily order dependent. The order in which the process is described is not intended to be construed as a limitation. Moreover, some of the actions shown in FIG. 10 may be omitted in some implementations and one or more actions shown in FIG. 10 may be combined.

[0306] The technical problem addressed by the method illustrated in FIG. 10 is enabling the UE to efficiently perform downlink synchronization and measurement of a candidate cell across different phases of a mobility procedure, where the characteristics of the SSB transmissions of the candidate cell, such as SSB positions in a burst, SSB periodicity, SFN SSB offset, SSB transmit power, SSB sub-carrier spacing, or SSB frequency, may vary over time. In a mobility procedure such as an LTM operation or a Layer-3 handover, the SSB configuration that is most suitable for the UE to measure the candidate cell at an early phase of the mobility procedure may differ from the SSB configuration that is most suitable at a later phase, for example, because the candidate cell may transition between a cell DTX active duration and a cell DTX non-active duration, or because the candidate cell may employ different types of SSB transmissions (e.g., an Always-On SSB and an On-Demand SSB) at different phases. If the UE were restricted to a single static SSB configuration throughout the mobility procedure, the UE would either miss SSB transmissions from the candidate cell when the transmission pattern changes, or would continue monitoring SSB occasions that are no longer transmitted by the candidate cell, thereby wasting UE power and degrading synchronization and measurement accuracy.

[0307] By receiving, from the BS via the serving cell, an RRC reconfiguration message including a first SSB configuration and a second SSB configuration for the candidate cell, and by subsequently receiving an explicit signaling that triggers the UE to change a parameter for SSB-based measurement from a first value to a second value, the UE is able to pre-obtain all candidate SSB configurations in advance and then dynamically switch the SSB-based measurement between the configurations at a network-controlled timing. This approach allows the network to align the UE's SSB-based measurement with the actual SSB transmission pattern of the candidate cell at each phase of the mobility procedure, without requiring additional RRC reconfiguration signaling each time the SSB transmission pattern changes. The explicit signaling may be implemented, for example, as a MAC CE or an RRC signaling, which provides flexibility in the signaling latency and overhead that is suitable for the mobility procedure. The approach thereby enables the UE to accurately track SSB transmissions of the candidate cell across different mobility phases, reduces UE power consumption by avoiding monitoring of SSB occasions that are not transmitted, reduces RRC signaling overhead by consolidating multiple SSB configurations into a single RRC reconfiguration message, and improves the overall synchronization and measurement performance during the mobility procedure, thereby facilitating more efficient and reliable mobility operations.

[0308] In some implementations, the explicit signaling may correspond to the RRC reconfiguration message, a MAC CE, or an RRC signaling. For example, when the explicit signaling corresponds to the RRC reconfiguration message, the reception of the RRC reconfiguration message in the action 1002 itself may serve as the trigger for changing the parameter for SSB-based measurement in the action 1006. When the explicit signaling corresponds to a MAC CE or an RRC signaling transmitted separately from the RRC reconfiguration message, the UE may defer the change of the parameter until the MAC CE or the RRC signaling is received, which may provide greater flexibility in timing the switch between the first SSB configuration and the second SSB configuration. In some implementations, the explicit signaling may correspond to an LTM CSC MAC CE. In some implementations, the explicit signaling may correspond to a handover command.

[0309] In some implementations, the MAC CE or the RRC signaling may include at least one of an SSB configuration index, an SSB-index bitmap indicating activated or de-activated status of specific SSB blocks, or a parameter index associated with one or more pre-configured SSB parameters. For example, the SSB configuration index may identify one of the first SSB configuration and the second SSB configuration that is pre-configured for the candidate cell via the RRC reconfiguration message. The SSB-index bitmap may indicate, for each SSB block within the first SSB burst set or the second SSB burst set of the candidate cell, whether the corresponding SSB block is activated or deactivated for SSB-based measurement. The parameter index may refer to one of the pre-configured SSB parameters described above with respect to the parameter for SSB-based measurement.

[0310] In some implementations, the parameter for SSB-based measurement may include at least one of an SSB position in a burst, an SSB periodicity, an SFN SSB offset, an SSB transmit power, an SSB sub-carrier spacing, or an SSB frequency. For example, the first SSB configuration and the second SSB configuration may differ in at least one of these parameters, and changing the parameter from the first value to the second value may cause the UE to detect the second SSB burst set at SSB positions, a periodicity, an SFN SSB offset, a transmit power, a sub-carrier spacing, or a frequency that is different from those used for detecting the first SSB burst set. In some implementations, the first SSB configuration may specify a first periodicity and a first SSB frequency for the first SSB burst set, and the second SSB configuration may specify a second periodicity and a second SSB frequency for the second SSB burst set, where the second periodicity differs from the first periodicity or the second SSB frequency differs from the first SSB frequency.

[0311] In some implementations, the mobility procedure may correspond to an L1 / L2 mobility operation that includes at least one of an LTM, a conditional LTM, a subsequent LTM, an inter-CU LTM, or an intra-CU LTM. For example, in an LTM procedure, the UE may be pre-configured with the first SSB configuration and the second SSB configuration for the candidate cell via the RRC reconfiguration message received from the source cell, and the explicit signaling triggering the change of the parameter for SSB-based measurement may correspond to an LTM cell switch command MAC CE transmitted by the source cell. In a conditional LTM procedure, the change of the parameter may be triggered when one or more pre-configured triggering events associated with the candidate cell are fulfilled, rather than upon reception of an explicit cell switch command from the source cell.

[0312] In some implementations, the mobility procedure may correspond to a L3 mobility operation that comprises at least one of a handover, a conditional handover, or a DAPS handover. For example, in an L3 handover procedure, the RRC reconfiguration message received from the source cell may serve as a handover command including the first SSB configuration and the second SSB configuration for the candidate cell, which is the target cell of the handover. The explicit signaling may correspond to the RRC reconfiguration message itself, such that the UE changes the parameter for SSB-based measurement upon receiving the handover command. In a DAPS handover procedure, the UE may maintain connectivity with both the source cell and the candidate cell during the handover, and the change of the parameter for SSB-based measurement of the candidate cell may be performed while the UE continues to communicate with the source cell.

[0313] In some implementations, changing the parameter for SSB-based measurement from the first value to the second value may include at least one of an activation of the second SSB configuration or a deactivation of the first SSB configuration. For example, in a first scenario, the UE may deactivate the first SSB configuration and activate the second SSB configuration, such that the UE transitions from detecting the first SSB burst set to detecting the second SSB burst set of the candidate cell. In a second scenario, the UE may activate the second SSB configuration without de-activating the first SSB configuration, such that the UE detects both the first SSB burst set and the second SSB burst set of the candidate cell jointly. In a third scenario, the UE may deactivate the first SSB configuration without activating the second SSB configuration, such that the UE ceases to detect the first SSB burst set while awaiting a subsequent activation of another SSB configuration.

[0314] In some implementations, the first SSB configuration may be an AW-SSB configuration, and the second SSB configuration may be an OD-SSB configuration. Performing the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value may include detecting an SSB burst set from the candidate cell based on a combination of the AW-SSB configuration and the OD-SSB configuration in at least one of a valid time period, a range in a frequency domain, or a power domain. For example, the AW-SSB configuration may specify the first SSB burst set that is always transmitted by the candidate cell regardless of traffic demand, and the OD-SSB configuration may specify the second SSB burst set that is transmitted by the candidate cell on demand in response to a request from the source cell or a scheduling decision by the candidate cell. By combining the AW-SSB configuration and the OD-SSB configuration, the UE may detect both the first SSB burst set and the second SSB burst set jointly within a valid time period, across overlapping or adjacent frequency ranges, or at different power levels, thereby improving the measurement reliability and coverage for the candidate cell.

[0315] In some implementations, one of the first SSB configuration and the second SSB configuration may be applied by the UE during a cell DTX non-active duration of the candidate cell and may include at least one of a long periodicity or a sparse SSB set pattern, and the other one of the first SSB configuration and the second SSB configuration may be applied by the UE during a cell DTX active duration of the candidate cell and may include at least one of a short periodicity or a dense SSB set pattern. For example, during the cell DTX non-active duration, the candidate cell may reduce SSB transmissions to save network energy, and accordingly the UE may apply the SSB configuration with the long periodicity or the sparse SSB set pattern to align with the reduced first SSB burst set of the candidate cell. During the cell DTX active duration, the candidate cell may resume normal SSB transmissions, and the UE may apply the SSB configuration with the short periodicity or the dense SSB set pattern to detect the more frequent second SSB burst set of the candidate cell. The transition between the DTX non-active duration and the DTX active duration may be coordinated between the source cell and the candidate cell via inter-cell signaling.

[0316] In some implementations, the UE may determine, based on the explicit signaling, that a cell DTX state of the candidate cell transitions from a non-active duration to an active duration or from the active duration to the non-active duration. For example, the explicit signaling may include an indicator or a flag that informs the UE of the DTX state transition of the candidate cell, such that the UE may change the parameter for SSB-based measurement from the first value to the second value in alignment with the DTX state transition. In some implementations, the source cell may determine the timing of the DTX state transition of the candidate cell based on inter-cell signaling exchanged with the candidate cell, and may transmit the explicit signaling to the UE at a timing that enables the UE to apply the updated SSB configuration before or at the onset of the DTX state transition, thereby avoiding a mismatch between the SSB-based measurement of the UE and the actual SSB transmission of the candidate cell.

[0317] In some implementations, the UE may transmit an RRC reconfiguration complete message to the BS via the serving cell in response to receiving the RRC reconfiguration message. The UE may change the parameter for SSB-based measurement from the first value to the second value upon transmitting the RRC reconfiguration complete message. For example, after receiving the explicit signaling (e.g., the RRC reconfiguration message itself) from the source cell, the UE may defer the change of the parameter for SSB-based measurement until the UE transmits the RRC reconfiguration complete message to the source cell to acknowledge receipt of the RRC reconfiguration message. That is, the transmission of the RRC reconfiguration complete message by the UE may serve as the timing at which the UE changes the parameter for SSB-based measurement, such that the UE transitions from detecting the first SSB burst set to detecting the second SSB burst set of the candidate cell upon completion of the RRC reconfiguration procedure with the source cell. By aligning the change of the parameter with the transmission of the RRC reconfiguration complete message, the UE and the source cell may share a common understanding of the timing at which the SSB configuration switch takes place.

[0318] In some implementations, the UE may transmit a mobility completion message to the candidate cell in response to completing the mobility procedure. The UE may change the parameter for SSB-based measurement from the first value to the second value upon transmitting the mobility completion message. For example, the mobility completion message may correspond to an RRC reconfiguration complete message or an LTM cell switch completion message transmitted by the UE to the candidate cell, which has become the serving cell of the UE after the mobility procedure. After receiving the explicit signaling (e.g., the RRC reconfiguration message) from the source cell, the UE may defer the change of the parameter for SSB-based measurement until the UE transmits the mobility completion message to the candidate cell. That is, the transmission of the mobility completion message by the UE may serve as the timing at which the UE changes the parameter for SSB-based measurement, such that the UE transitions from detecting the first SSB burst set to detecting the second SSB burst set of the candidate cell upon completion of the mobility procedure, reflecting a change in the role of the candidate cell from a target cell to the serving cell.

[0319] In some implementations, the UE may start a timer in response to receiving the explicit signaling. The UE may change the parameter for SSB-based measurement from the first value to the second value upon expiration of the timer. For example, after receiving the explicit signaling (e.g., an RRC reconfiguration message, a MAC CE, or another RRC signaling) from the source cell, the UE may start the timer initialized to a timing offset configured by the source cell via the RRC reconfiguration message or via the explicit signaling. The timing offset may be determined by the source cell based on inter-cell signaling with the candidate cell to align the expiration of the timer with an expected change in the SSB transmission pattern of the candidate cell, such as a transition from a cell DTX non-active duration to a cell DTX active duration. That is, the expiration of the timer may serve as the timing at which the UE changes the parameter for SSB-based measurement, such that the UE transitions from detecting the first SSB burst set to detecting the second SSB burst set of the candidate cell upon expiration of the timer, without requiring an additional signaling from the source cell at the time of the parameter change.

[0320] It should be noted that the BS may perform methods or actions corresponding to those performed by the UE. For example, the receiving actions performed by the UE may correspond to the transmitting or configuring actions of the BS; the transmitting actions performed by the UE may correspond to the receiving actions of the BS; and the detecting actions performed by the UE may correspond to the broadcasting actions of the BS. That is, the BS and the UE may have reciprocally aligned roles in transmission and reception.

[0321] For example, the BS (e.g., a serving cell or a source cell) may transmit, to the UE, an RRC reconfiguration message including a first SSB configuration and a second SSB configuration for a candidate cell. The BS may transmit an explicit signaling to the UE. In some implementations, the explicit signaling may correspond to the RRC reconfiguration message. In response to receiving the explicit signaling, the UE may change a parameter for SSB-based measurement for a mobility procedure associated with the candidate cell from a first value to a second value. The UE may perform the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value.

[0322] In some implementations, the BS that transmits the multiple SSB configurations and the BS that broadcasts the first and second SSB burst sets may be implemented as a single base station that supports both the source cell and the candidate cell (e.g., in an intra-CU LTM deployment). In some other implementations, the transmitting of the multiple SSB configurations may be performed by a first base station (e.g., a source base station that supports the source cell) while the broadcasting of the first and second SSB burst sets may be performed by a second base station (e.g., a candidate base station that supports the candidate cell), where the first base station and the second base station may coordinate via inter-node signaling carried over an Xn interface or another inter-node interface to align the SSB broadcasting at the second base station with the RRC message received by the first base station from the UE.

[0323] Reference is made to FIG. 11. FIG. 11 is a flowchart illustrating a method / process 1100 for SSB adaptation in connection with a Layer-3 (L3) handover or a conditional handover operation, according to an example implementation of the present disclosure. The method / process 1100 may be performed by a UE. The method / process 1100 of FIG. 11 may be considered an L3-mobility counterpart of the method / process 1000 of FIG. 10. In the method / process 1100, the UE may transition between a first SSB configuration and a second SSB configuration at different stages of the L3 mobility operation. The ordering of the actions illustrated in FIG. 11 is provided as an illustrative example, and two or more of the actions illustrated in FIG. 11 may be performed in a different order, in an overlapping or interleaved manner, in parallel, or in any other order without departing from the scope of the present disclosure.

[0324] In action 1102, the UE may receive, from a source cell, a Radio Resource Control (RRC) reconfiguration message. The RRC reconfiguration message may include a candidate cell configuration for a target cell and multiple SSB configurations associated with the target cell. For example, the multiple SSB configurations may include a first SSB configuration (e.g., an SSB#1 configuration) and a second SSB configuration (e.g., an SSB#2 configuration). In some implementations, the first SSB configuration may be an Always-On SSB (AW-SSB) configuration, and the second SSB configuration may be an On-Demand SSB (OD-SSB) configuration. In some implementations, the RRC reconfiguration message may further include measurement object parameters that indicate the target cell frequency and SSB-related measurement parameters (e.g., one or more parameters from an SSB-ConfigMobility IE or an SSB-InfoNcell IE as described above). For a conditional handover operation, the RRC reconfiguration message may further include one or more pre-configured triggering events (e.g., one or more L3 measurement-based triggering events) that the UE may use to determine when to initiate the handover procedure.

[0325] In action 1104, the UE may detect a first SSB burst set from the target cell based on the first SSB configuration. For example, the UE may detect the first SSB burst set based on the AW-SSB configuration of the target cell. The UE may apply a first Synchronization Signal / Physical Broadcast Channel Block Measurement Timing Configuration (SMTC) associated with the first SSB configuration to determine the measurement timing window for the first SSB burst set. The UE may use the detected first SSB burst set to perform an L3 measurement (e.g., a Reference Signal Received Power (RSRP) measurement, a Reference Signal Received Quality (RSRQ) measurement, or a Signal-to-Interference-plus-Noise Ratio (SINR) measurement) on the target cell.

[0326] In action 1106, for a handover operation, the UE may transmit a measurement report to the source cell in response to determining that one or more L3 measurement events associated with the target cell are satisfied. For example, the L3 measurement event may be triggered when the measured quality of the target cell exceeds the measured quality of the source cell by a configured offset. In response to receiving the measurement report, the source cell may decide to initiate a handover of the UE to the target cell. For a conditional handover operation, the UE may determine that one or more pre-configured triggering events associated with the target cell are fulfilled, and the UE may initiate the handover procedure based on the fulfillment of the pre-configured triggering events without receiving an explicit handover command from the source cell.

[0327] In action 1108, for a handover operation, the UE may receive, from the source cell, a second RRC reconfiguration message that may include a handover command (e.g., a mobilityControlInfo parameter or a reconfigurationWithSync parameter) that instructs the UE to perform a handover to the target cell. In response to receiving the handover command, the UE may initiate synchronization with the target cell and may perform a random access procedure to the target cell. For a conditional handover operation, action 1108 may be omitted, since the UE may initiate the handover procedure based on the fulfillment of the pre-configured triggering events as described in action 1106. For example, the UE may perform the random access procedure to the target cell in response to determining that the pre-configured triggering events are fulfilled.

[0328] In action 1110, the UE may transmit an RRC reconfiguration complete message to the target cell upon successful completion of the random access procedure. The RRC reconfiguration complete message may indicate that the UE has completed the handover procedure and has successfully transitioned to the target cell. In the context of SSB adaptation, the transmission of the RRC reconfiguration complete message may serve as a triggering event for the SSB adaptation. For example, the UE may consider the first SSB configuration to be deactivated and the second SSB configuration to be activated upon transmitting the RRC reconfiguration complete message.

[0329] In action 1112, the UE may detect a second SSB burst set from the target cell based on the second SSB configuration. For example, the UE may detect the second SSB burst set based on the OD-SSB configuration of the target cell, where the OD-SSB configuration may have a shorter periodicity or a different SSB position in a burst compared to the AW-SSB configuration. In some implementations, the target cell may begin broadcasting the second SSB burst set in response to receiving the RRC reconfiguration complete message from the UE. The UE may apply a second SMTC associated with the second SSB configuration to determine the measurement timing window for the second SSB burst set. The second SSB burst set may be used by the UE for synchronization and / or measurement of the target cell in a serving cell capacity after the handover is completed.

[0330] The method / process 1100 described above may also be applicable to the implicit SSB adaptation mechanism described with reference to FIG. 4 and FIG. 5. For example, the SSB adaptation between the first SSB configuration and the second SSB configuration may be implicitly triggered by the transmission of the RRC reconfiguration complete message in action 1110, without requiring an explicit activation or deactivation command from the serving RAN. In some implementations, the UE may apply the cross-layer signaling mechanism described with reference to FIG. 5 to coordinate the SSB adaptation across the RRC entity, the MAC entity, and the PHY layer of the UE.

[0331] In some implementations, one or more of the actions 1102, 1104, 1106, 1108, 1110, and 1112 may be omitted, combined, or performed in a different order depending on the deployment configuration.

[0332] Reference is made to FIG. 12. FIG. 12 is a flowchart illustrating a method / process 1200 for SSB adaptation in connection with a Dual-Active-Protocol-Stack (DAPS) handover operation, according to an example implementation of the present disclosure. The method / process 1200 may be performed by a UE. In a DAPS handover, the UE may maintain a protocol stack for a source cell and a protocol stack for a target cell simultaneously for a period of time during the handover, which may reduce a data interruption experienced by the UE during the handover. The ordering of the actions illustrated in FIG. 12 is provided as an illustrative example, and two or more of the actions illustrated in FIG. 12 may be performed in a different order, in an overlapping or interleaved manner, in parallel, or in any other order without departing from the scope of the present disclosure.

[0333] In action 1202, the UE may receive, from a source cell, a Radio Resource Control (RRC) reconfiguration message. The RRC reconfiguration message may include a candidate cell configuration for a target cell and multiple SSB configurations associated with the target cell. For example, the multiple SSB configurations may include a first SSB configuration (e.g., an SSB#1 configuration) and a second SSB configuration (e.g., an SSB#2 configuration). In some implementations, the first SSB configuration may be an Always-On SSB (AW-SSB) configuration, and the second SSB configuration may be an On-Demand SSB (OD-SSB) configuration. The RRC reconfiguration message may further include measurement object parameters that indicate the target cell frequency and SSB-related measurement parameters.

[0334] In action 1204, the UE may detect a first SSB burst set from the target cell based on the first SSB configuration. For example, the UE may detect the first SSB burst set based on the AW-SSB configuration of the target cell. The UE may apply a first SMTC associated with the first SSB configuration to determine the measurement timing window for the first SSB burst set. The UE may use the detected first SSB burst set to perform an L3 measurement on the target cell.

[0335] In action 1206, the UE may transmit a measurement report to the source cell in response to determining that one or more L3 measurement events associated with the target cell are satisfied. In response to receiving the measurement report, the source cell may decide to initiate a DAPS handover of the UE to the target cell.

[0336] In action 1208, the UE may receive, from the source cell, a second RRC reconfiguration message that may include a DAPS handover command. The DAPS handover command may instruct the UE to perform a handover to the target cell while maintaining the source cell connection. For example, the second RRC reconfiguration message may include a reconfigurationWithSync parameter with a DAPS handover indication.

[0337] In action 1210, the UE may maintain dual protocol stacks in response to receiving the DAPS handover command. For example, the UE may maintain a first protocol stack associated with the source cell and a second protocol stack associated with the target cell. The UE may continue to communicate with the source cell via the first protocol stack while performing a random access procedure to the target cell via the second protocol stack. The dual protocol stack operation may enable the UE to continue transmitting uplink data to and receiving downlink data from the source cell during the random access procedure to the target cell, thereby reducing the data interruption during the handover.

[0338] In action 1212, the UE may transmit an RRC reconfiguration complete message to the target cell upon successful completion of the random access procedure. The RRC reconfiguration complete message may indicate that the UE has established a connection with the target cell. In the context of SSB adaptation, the transmission of the RRC reconfiguration complete message may serve as a triggering event for the SSB adaptation. For example, the UE may consider the first SSB configuration to be deactivated and the second SSB configuration to be activated upon transmitting the RRC reconfiguration complete message.

[0339] In action 1214, the UE may detect a second SSB burst set from the target cell based on the second SSB configuration. For example, the UE may detect the second SSB burst set based on the OD-SSB configuration of the target cell. In some implementations, the target cell may begin broadcasting the second SSB burst set in response to receiving the RRC reconfiguration complete message from the UE. The UE may apply a second SMTC associated with the second SSB configuration to determine the measurement timing window for the second SSB burst set.

[0340] In action 1216, the source cell may release the UE from the source cell connection. For example, the source cell may transmit a DAPS source release indication to the target cell or to the UE, and the UE may release the first protocol stack associated with the source cell in response to receiving the DAPS source release indication. After the source cell connection is released, the UE may operate on the target cell as the new serving cell, and the UE may use the second SSB burst set detected in action 1214 for synchronization and / or measurement of the target cell in a serving cell capacity.

[0341] The method / process 1200 described above may also be applicable to the implicit SSB adaptation mechanism described with reference to FIG. 4 and FIG. 5. For example, the SSB adaptation between the first SSB configuration and the second SSB configuration may be implicitly triggered by the transmission of the RRC reconfiguration complete message in action 1212, without requiring an explicit activation or deactivation command from the serving RAN. In some implementations, during the dual protocol stack operation of action 1210, the UE may continue to use the first SSB configuration for measurement of the target cell via the second protocol stack, and may switch to the second SSB configuration after the RRC reconfiguration complete message is transmitted.

[0342] In some implementations, one or more of the actions 1202, 1204, 1206, 1208, 1210, 1212, 1214, and 1216 may be omitted, combined, or performed in a different order depending on the deployment configuration.

[0343] Reference is made to FIG. 13. FIG. 13 is a block diagram illustrating a node 1300 for wireless communication, according to an example implementation of the present disclosure. The node 1300 may be used to implement the UE described herein, the BS described herein, or another wireless communication apparatus that may perform one or more of the methods described herein.

[0344] As shown in FIG. 13, the node 1300 may include a transceiver 1320, a processor 1328, a memory 1334, one or more presentation components 1338, and at least one antenna 1336. The node 1300 may also include a Radio Frequency (RF) spectrum band module, a base station communications module, a network communications module, a system communications management module, one or more Input / Output (I / O) ports, one or more I / O components, and a power supply, although these components are not explicitly illustrated in FIG. 13. The components of the node 1300 may be in communication with each other directly or indirectly over one or more buses 1340. In some implementations, the node 1300 may correspond to a UE or a base station that performs one or more of the functions described herein.

[0345] The transceiver 1320 may include a transmitter 1322 (e.g., transmitting circuitry or transmission circuitry) and a receiver 1324 (e.g., receiving circuitry or reception circuitry), and may be configured to transmit or receive time-related or frequency-related resource partitioning information. In some implementations, the transceiver 1320 may be configured to transmit in different types of subframes or slots. For example, the transceiver 1320 may be configured to transmit in usable subframes, non-usable subframes, or flexibly usable subframes, and may be configured to transmit in different slot formats. The transceiver 1320 may further be configured to receive data and control channels.

[0346] The node 1300 may include a variety of computer-readable media. The computer-readable media may include any available media that may be accessed by the node 1300. The computer-readable media may include both volatile and non-volatile media, and removable and non-removable media. The computer-readable media may include computer-storage media and communication media. The computer-storage media may include both volatile and non-volatile media, and removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, AI modules, ML modules, or data. The computer-storage media may include, for example, RAM, DRAM, HBM, MRAM, FRAM, RRAM, ROM, EEPROM, flash memory or another memory technology, CD-ROM, DVD or another optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage, or another magnetic storage device. The computer-storage media may not include a propagated data signal. The communication media may typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or another transport mechanism, and may include any information delivery media. The term "modulated data signal" may indicate a signal that has one or more of various characteristics set or changed in such a manner as to encode information in the signal. The communication media may include wired media such as a wired network or a direct-wired connection, and wireless media such as acoustic, RF, infrared, or other wireless media.

[0347] The memory 1334 may include computer-storage media in the form of volatile memory, non-volatile memory, or a combination thereof. The memory 1334 may be removable, non-removable, or a combination thereof. For example, the memory 1334 may include solid-state memory, a hard drive, or an optical-disc drive. As illustrated in FIG. 13, the memory 1334 may store computer-readable, computer-executable instructions 1332 (e.g., software codes, a set of instructions, AI modules, or ML modules), and may store data 1330. The instructions 1332 may be configured to, when executed by the processor 1328, cause the processor 1328 to perform one or more of the functions described herein. In some implementations, the instructions 1332 may not be directly executable by the processor 1328, but may be configured to cause the node 1300 (e.g., when compiled and executed) to perform one or more of the functions described herein. The AI modules or the ML modules may be implemented with a supervised learning approach, a semi-supervised learning approach, an unsupervised learning approach (e.g., a transductive approach or an inductive approach), a federated learning approach, or a reinforcement learning approach.

[0348] The processor 1328 may include processing circuitry, and may include an intelligent hardware device. For example, the processor 1328 may include a Central Processing Unit (CPU), a Tensor Processing Unit (TPU), a Graphics Processing Unit (GPU), a General-purpose computing on GPUs (GPGPU), a microcontroller, an Application-Specific Integrated Circuit (ASIC), or another type of processor. The processor 1328 may include or be coupled to memory. The processor 1328 may process the data 1330 and the instructions 1332 received from the memory 1334, and may further process information through the transceiver 1320, the base station communications module, or the network communications module. The processor 1328 may also process information to be transmitted to the transceiver 1320 for transmission through the antenna 1336, or to the network communications module for transmission to a core network.

[0349] The one or more presentation components 1338 may present data indications to a person or another device. For example, the one or more presentation components 1338 may include a display device, a speaker, a printing component, or a vibrating component.

[0350] From the description above, various techniques may be used for implementing the concepts described in the present disclosure without departing from the scope of those concepts. Moreover, while the concepts have been described with specific reference to certain implementations, persons of ordinary skill in the art would recognize that changes may be made in form and detail without departing from the scope of those concepts. As such, the described implementations are to be considered in all respects as illustrative and not restrictive. The present disclosure is not limited to the particular implementations described above, and many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

A User Equipment (UE) for performing a Synchronization Signal Block (SSB) adaptation operation, the UE comprising:  at least one processor; and  at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the UE to:    receive, from a Base Station (BS) via a serving cell, a Radio Resource Control (RRC) reconfiguration message comprising a first SSB configuration and a second SSB configuration for a candidate cell;    receive, from the BS via the serving cell, an explicit signaling;    in response to receiving the explicit signaling, change a parameter for SSB-based measurement for a mobility procedure associated with the candidate cell from a first value to a second value; and    perform the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value.The UE of claim 1, wherein the explicit signaling corresponds to the RRC reconfiguration message, a Medium Access Control (MAC) Control Element (CE), or an RRC signaling.The UE of claim 2, wherein the MAC CE or the RRC signaling comprises at least one of an SSB configuration index, an SSB-index bitmap indicating activated or de-activated status of specific SSB blocks, or a parameter index associated with one or more pre-configured SSB parameters.The UE of claim 1, wherein the parameter for SSB-based measurement comprises at least one of an SSB position in a burst, an SSB periodicity, a system frame number (SFN) SSB offset, an SSB transmit power, an SSB sub-carrier spacing, or an SSB frequency.The UE of claim 1, wherein the mobility procedure corresponds to a Layer-1 / Layer-2 (L1 / L2) mobility operation that comprises at least one of a Layer-1 / Layer-2 Triggered Mobility (LTM), a conditional LTM, a subsequent LTM, an inter-Central Unit (CU) LTM, or an intra-CU LTM.The UE of claim 1, wherein the mobility procedure corresponds to a Layer-3 (L3) mobility operation that comprises at least one of a handover, a conditional handover, or a Dual-Active-Protocol-Stack (DAPS) handover.The UE of claim 1, wherein changing the parameter for SSB-based measurement from the first value to the second value comprises at least one of an activation of the second SSB configuration or a deactivation of the first SSB configuration.The UE of claim 1, wherein:  the first SSB configuration is an Always-On SSB (AW-SSB) configuration,  the second SSB configuration is an On-Demand SSB (OD-SSB) configuration, and  performing the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value comprises detecting an SSB burst set from the candidate cell based on a combination of the AW-SSB configuration and the OD-SSB configuration in at least one of a valid time period, a range in a frequency domain, or a power domain.The UE of claim 1, wherein:  one of the first SSB configuration and the second SSB configuration is applied by the UE during a cell Discontinuous Transmission (DTX) non-active duration of the candidate cell and comprises at least one of a long periodicity or a sparse SSB set pattern, and  the other one of the first SSB configuration and the second SSB configuration is applied by the UE during a cell DTX active duration of the candidate cell and comprises at least one of a short periodicity or a dense SSB set pattern.The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to:  determine, based on the explicit signaling, that a cell Discontinuous Transmission (DTX) state of the candidate cell transitions from a non-active duration to an active duration or from the active duration to the non-active duration.The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to:  transmit an RRC reconfiguration complete message to the BS via the serving cell in response to receiving the RRC reconfiguration message,  wherein the UE changes the parameter for SSB-based measurement from the first value to the second value upon transmitting the RRC reconfiguration complete message.The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to:  transmit a mobility completion message to the candidate cell in response to completing the mobility procedure,  wherein the UE changes the parameter for SSB-based measurement from the first value to the second value upon transmitting the mobility completion message.The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to:  start a timer in response to receiving the explicit signaling,  wherein the UE changes the parameter for SSB-based measurement from the first value to the second value upon expiration of the timer.A Base Station (BS) for supporting a Synchronization Signal Block (SSB) adaptation operation, the BS comprising:  at least one processor; and  at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the BS to:    transmit, to a User Equipment (UE) via a serving cell, a Radio Resource Control (RRC) reconfiguration message comprising a first SSB configuration and a second SSB configuration for a candidate cell; and    transmit, to the UE via the serving cell, an explicit signaling, wherein:  in response to receiving the explicit signaling, the UE changes a parameter for SSB-based measurement for a mobility procedure associated with the candidate cell from a first value to a second value, and  the UE performs the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value.A method performed by a User Equipment (UE) for performing a Synchronization Signal Block (SSB) adaptation operation, the method comprising:  receiving, from a Base Station (BS) via a serving cell, a Radio Resource Control reconfiguration message comprising a first SSB configuration and a second SSB configuration for a candidate cell;  receiving, from the BS via the serving cell, an explicit signaling;  in response to receiving the explicit signaling, changing a parameter for SSB-based measurement for a mobility procedure associated with the candidate cell from a first value to a second value; and  performing the SSB-based measurement for the mobility procedure associated with the candidate cell based on the second value.