Method and apparatus for layer 1 measurement reporting

Abstract

A method performed by a UE for L1 measurement reporting is provided. The method receives, from a BS, an L1 measurement configuration that configures at least one LTM event. The method measures multiple candidate beams to obtain multiple L1 measurement results. The method determines, based on the at least one LTM event, a priority of each of the multiple candidate beams. The method generates an L1 measurement report (L1-MR) MAC CE by assembling the multiple L1 measurement results associated with the multiple candidate beams in the L1-MR MAC CE based on the priority of each of the multiple candidate beams. The method transmits, to the BS, the L1-MR MAC CE, where each of the multiple candidate beams is associated with a reference signal index of an LTM candidate cell, and the L1-MR MAC CE is generated by a MAC entity of the UE.

Description

METHOD AND APPARATUS FOR LAYER 1 MEASUREMENT REPORTING

[0001] The present disclosure is related to wireless communication and, more specifically, to a User Equipment (UE), Base Station (BS), and method for layer 1 (L1) measurement reporting in the wireless communication networks.

[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), 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 grow, however, there exists a need for further improvements in the next-generation wireless communication systems, such as improvements in a beam management procedure.

[0003] The present disclosure is related to a UE, a BS, and a method for layer 1 (L1) measurement reporting in the wireless communication networks.

[0004] In a first aspect of the present disclosure, a UE for layer 1 (L1) measurement reporting 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 computer-executable instructions, when executed by the at least one processor, cause the UE to: receive, from a base station (BS), an L1 measurement configuration that configures at least one layer 1 (L1) / layer 2 (L2) triggered mobility (LTM) event; measure multiple candidate beams to obtain multiple L1 measurement results; determine, based on the at least one LTM event, a priority of each of the multiple candidate beams; generate an L1 measurement report (L1-MR) medium access control (MAC) control element (CE) by assembling the multiple L1 measurement results associated with the multiple candidate beams in the L1-MR MAC CE based on the priority of each of the multiple candidate beams; and transmit, to the BS, the L1-MR MAC CE, where each of the multiple candidate beams is associated with a reference signal index of an LTM candidate cell, and the L1-MR MAC CE is generated by a MAC entity of the UE.

[0005] In some implementations of the first aspect, determining, based on the at least one LTM event, the priority of each of the multiple candidate beams includes: determining that a first candidate beam of the multiple candidate beams has a first priority after determining that a first L1 measurement result of the first candidate beam remains satisfying an entering condition of the at least one LTM event upon expiry of a first time-to-trigger (TTT) timer associated with the entering condition; determining that a second candidate beam of the multiple candidate beams has a second priority after determining that a second L1 measurement result of the second candidate beam remains satisfying a leaving condition of the at least one LTM event upon expiry of a second TTT timer associated with the leaving condition; determining that a third candidate beam of the multiple candidate beams has a third priority after determining that a third L1 measurement result of the third candidate beam has been reported and the third L1 measurement result does not remain satisfying the leaving condition of the at least one LTM event upon expiry of the second TTT timer; and determining that a fourth candidate beam of the multiple candidate beams has a fourth priority after determining that a fourth L1 measurement result of the fourth candidate beam does not remain satisfying the entering condition of the at least one LTM event upon expiry of the first TTT timer and does not remain satisfying the leaving condition of the at least one LTM event upon expiry of the second TTT timer, where the first priority, the second priority, the third priority, and the fourth priority are in a decreasing order of priority.

[0006] In some implementations of the first aspect, generating the L1-MR MAC CE by assembling the multiple L1 measurement results associated with the multiple candidate beams in the L1-MR MAC CE based on the priority of each of the multiple candidate beams includes: assembling the first L1 measurement result in the L1-MR MAC CE before assembling the second L1 measurement result, the third L1 measurement result, and the fourth L1 measurement result in the L1-MR MAC CE; assembling the second L1 measurement result in the L1-MR MAC CE before assembling the third L1 measurement result and the fourth L1 measurement result in the L1-MR MAC CE; assembling the third L1 measurement result in the L1-MR MAC CE before assembling the fourth L1 measurement result in the L1-MR MAC CE; and assembling the fourth L1 measurement result in the L1-MR MAC CE after assembling the first L1 measurement result, second L1 measurement result, and third L1 measurement result in the L1-MR MAC CE after determining that a specific information element (IE) indicating that an L1 measurement result of a candidate beam having the fourth priority is allowed to be reported.

[0007] In some implementations of the first aspect, generating the L1-MR MAC CE by assembling the multiple L1 measurement results associated with the multiple candidate beams in the L1-MR MAC CE based on the priority of each of the multiple candidate beams includes refraining from assembling the first L1 measurement result in the L1-MR MAC CE after determining that the first candidate beam has the first priority and the first L1 measurement result remains satisfying the leaving condition of the at least one LTM event upon expiry of the second TTT timer, and the L1-MR MAC CE includes a truncated L1-MR MAC CE.

[0008] In some implementations of the first aspect, the L1 measurement configuration includes an information element (IE) that indicates that the UE is allowed to generate the L1-MR MAC CE after determining that an L1 measurement result of one of the multiple candidate beams remains satisfying a leaving condition of the at least one LTM event upon expiry of a time-to-trigger (TTT) timer associated with the leaving condition, and the IE is configured by a radio resource control (RRC) configuration.

[0009] 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: receive, from the BS, an information element (IE) that indicates whether an L1 measurement result of a current beam of a serving cell is to be reported via the L1-MR MAC CE; and assemble the L1 measurement result of the current beam of the serving cell in the L1-MR MAC CE after determining that the IE indicates that the L1 measurement result of the current beam of the serving cell is to be reported via the L1-MR MAC CE, where the IE is configured by a radio resource control (RRC) configuration.

[0010] In some implementations of the first aspect, the L1 measurement configuration includes a scheduling request (SR) configuration specific for the transmission of the L1-MR MAC CE, and the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: transmit, to the BS, a scheduling request based on the SR configuration, and after determining that the MAC entity is reset: release the multiple L1 measurement results, the scheduling request, and the L1-MR MAC CE, and stop all running TTT timers associated with the at least one LTM event.

[0011] In some implementations of the first aspect, the L1 measurement configuration further configures a periodical reporting timer and a value of the periodical reporting timer, the periodical reporting timer is used for the UE to report the L1-MR MAC CE periodically, and the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: start or restart the periodical reporting timer; and generate and transmit the L1-MR MAC CE after determining that the periodical reporting timer expires and one or more of the multiple L1 measurement results that satisfy an entering condition or a leaving condition of the at least one LTM event are pending.

[0012] In some implementations of the first aspect, the L1 measurement configuration further configures a maximum number of beams to be reported in the L1-MR MAC CE, and the maximum number is applied to one or more beams of neighbor cells and a current beam of a serving cell when the UE is indicated by the BS to report an L1 measurement result of the current beam of the serving cell.

[0013] In a second aspect of the present disclosure, a method performed by a user equipment (UE) for layer 1 (L1) measurement reporting is provided. The method includes: receiving, from a base station (BS), an L1 measurement configuration that configures at least one layer 1 (L1) / layer 2 (L2) triggered mobility (LTM) event; measuring multiple candidate beams to obtain multiple L1 measurement results; determining, based on the at least one LTM event, a priority of each of the multiple candidate beams; generating an L1 measurement report (L1-MR) medium access control (MAC) control element (CE) by assembling the multiple L1 measurement results associated with the multiple candidate beams in the L1-MR MAC CE based on the priority of each of the multiple candidate beams; and transmitting, to the BS, the L1-MR MAC CE, where each of the multiple candidate beams is associated with a reference signal index of an LTM candidate cell, and the L1-MR MAC CE is generated by a MAC entity of the UE.

[0014] In a third aspect of the present application, a BS for managing layer 1 (L1) measurement reporting 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 computer-executable instructions, when executed by the at least one processor, cause the BS to: transmit, to a user equipment (UE), an L1 measurement configuration that configures at least one layer 1 (L1) / layer 2 (L2) triggered mobility (LTM) event. The L1 measurement configuration causes the UE to: measure multiple candidate beams to obtain a multiple L1 measurement results; determine, based on the at least one LTM event, a priority of each of the multiple candidate beams; generate an L1 measurement report (L1-MR) medium access control (MAC) control element (CE) by assembling the multiple L1 measurement results associated with the multiple candidate beams in the L1-MR MAC CE based on the priority of each of the multiple candidate beams; and transmit, to the BS, the L1-MR MAC CE, where each of the multiple candidate beams is associated with a reference signal index of an LTM candidate cell, and the L1-MR MAC CE is generated by a MAC entity of the UE.

[0015] 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.

[0016] FIG. 1 is a diagram illustrating a time-based evaluation for LTM event conditions, according to an example implementation of the present disclosure.

[0017] FIG. 2 is a diagram illustrating a conditional LTM procedure, according to an example implementation of the present disclosure.

[0018] FIG. 3 is a diagram illustrating a conditional LTM procedure, according to an example implementation of the present disclosure.

[0019] FIG. 4A is a diagram illustrating an assembling sequence when the UE collects multiple LTM / L1 measurement results from the lower layer, according to an example implementation of the present disclosure.

[0020] FIG. 4B is a diagram illustrating an assembling sequence when the UE collects multiple LTM / L1 measurement results from the lower layer, according to an example implementation of the present disclosure.

[0021] FIG. 4C is a diagram illustrating an assembling sequence when the UE collects multiple LTM / L1 measurement results from the lower layer, according to an example implementation of the present disclosure.

[0022] FIG. 5A is a diagram illustrating a timeline for L1-MRs and LTM / L1-MR MAC CE transmission, according to an example implementation of the present disclosure.

[0023] FIG. 5B is a diagram illustrating a timeline for L1-MRs and LTM / L1-MR MAC CE transmission, according to an example implementation of the present disclosure.

[0024] FIG. 6 is a diagram illustrating an LTM cell switch procedure, according to an example implementation of the present disclosure.

[0025] FIG. 7 is a flowchart illustrating a method / process performed by a UE for layer 1 (L1) measurement reporting, according to an example implementation of the present disclosure.

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

[0027] Some of the abbreviations used in the present disclosure include: Abbreviation　　　　Full name 3GPP　　　　3rdGeneration Partnership Project 5G　　　　5thGeneration 5GC 　　　　5G Core AMF 　　　　Access and Mobility Management Function? ARFCN 　　　　Absolute Radio-Frequency Channel Number AS 　　　　Access Stratum BS 　　　　Base Station BWP 　　　　Bandwidth Part CA 　　　　Carrier Aggregation CAG 　　　　Closed Access Group CN 　　　　Core Network CU 　　　　Central Unit DAPS 　　　　Dual Active Protocol Stack DC 　　　　Dual Connectivity DCI 　　　　Downlink Control Information DL 　　　　Downlink DU 　　　　Distributed Unit E-UTRA(N) 　　　　Evolved Universal Terrestrial Radio Access (Network) EN-DC 　　　　E-UTRA NR Dual Connectivity EPC 　　　　Evolved Packet Core FR 　　　　Frequency Range IAB 　　　　Integrated Access and Backhaul ID 　　　　Identifier IE 　　　　Information Element LAN 　　　　Local Area Network LTE 　　　　Long Term Evolution LTM 　　　　L1 / L2 Triggered Mobility LTM SCS 　　　　L1 / L2 Triggered Mobility Serving Cell Switch MAC 　　　　Medium Access Control MAC CE 　　　　MAC Control Element MCG 　　　　Master Cell Group MIB 　　　　Master Information Block MN 　　　　Master Node MSG 　　　　Message MT 　　　　Mobile Termination NAS 　　　　Non-Access Stratum NE-DC 　　　　NR - E-UTRA Dual Connectivity NES 　　　　Network Energy Saving NPN 　　　　Non-Public Network NR 　　　　New Radio NR-U 　　　　NR Unlicensed NW 　　　　Network NSSAI 　　　　Network Slice Selection Assistance Information PCell 　　　　Primary Cell PCI 　　　　Physical Cell Identity PDCCH 　　　　Physical Downlink Control Channel PDSCH 　　　　Physical Downlink Shared Channel PDU 　　　　Protocol Data Unit PHY 　　　　Physical (layer) PLMN 　　　　Public Land Mobile Network PNI-NPN 　　　　Public Network Integrated Non-Public Network PRACH 　　　　Physical Random Access Channel PSCell 　　　　Primary SCG Cell / Primary Secondary Cell PUCCH 　　　　Physical Uplink Control Channel PUSCH 　　　　Physical Uplink Shared Channel RA 　　　　Random Access RAN 　　　　Radio Access Network RAR 　　　　Random Access Response RAT 　　　　Radio Access Technology RF 　　　　Radio Frequency RNTI 　　　　Radio Network Temporary Identifier RRC 　　　　Radio Resource Control RS 　　　　Reference Signal RSRP 　　　　Reference Signal Received Power SCell 　　　　Secondary Cell SCG 　　　　Secondary Cell Group SI 　　　　System Information SIB 　　　　System Information Block SL 　　　　Sidelink SN 　　　　Secondary Node SNPN 　　　　Stand-alond Non-Public Network SSB 　　　　Synchronization Signal Block TS 　　　　Technical Specification UE 　　　　User Equipment UL 　　　　Uplink V2X 　　　　Vehicle-to-Everything WUS 　　　　Wake-Up-Signal / Wake-Up-Signaling

[0028] 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.

[0029] 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.

[0030] For the purposes of 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 may not be narrowly confined to what is illustrated in the drawings.

[0031] 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 some implementations,” 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. 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] A software implementation may include computer-executable instructions and / or Artificial Intelligence (AI) / Machine Learning (ML) module(s) 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 computer-executable instructions and 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., Transductive approach and 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., NW 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.

[0036] The microprocessors or general-purpose computers may include Application-Specific Integrated Circuits (ASICs), programmable logic arrays, Central Processing Units (CPUs), Tensor Processing Units (TPUs), Graphics Processing Units (GPUs), General-purpose computing on GPUs (GPGPU, or less often GPGP), and / or one or more Digital Signal Processors (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 media may include computer-storage media and communication media. Computer-storage media may include both volatile (and / or non-volatile media), and removable (and / or non-removable) media implemented in any method or technology for storage of information such as computer-readable instructions related to AI module(s) and / or the ML module(s), data structures, program modules or data. The computer-readable medium may include, but is not limited to, Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), High Bandwidth Memory (HBM), Magnetoresistive Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Resistive Random Access Memory (RRAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory (or other memory technology), Compact Disc Read-Only Memory (CD-ROM) , Digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), or any other equivalent medium capable of storing computer-readable instructions. Computer-storage media may not include a propagated data signal. Communication media may typically embody computer-readable instructions (e.g., computer-readable instructions related to AI module(s) and / or the ML module(s)), data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transport mechanisms and include any information delivery media.

[0037] The term “modulated data signal” may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Combinations of any of the previously listed components should also be included within the scope of computer-readable media.

[0038] A radio communication network architecture such as a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, a 5G NR Radio Access Network (RAN), 5G-Advanced (5G-A) system, or an open radio access network (O-RAN) may typically include at least one base station (BS), at least one UE, and one or more optional network elements that provide connection within a network. The BS and one or more optional network elements enable the UE to access a radio network. Thus, the UE may communicate with the network, such as a Core Network (CN), an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial RAN (E-UTRAN), a Next-Generation Core (NGC), a 5G Core (5GC), or an internet via a RAN established by one or more BSs and the network elements / functions.

[0039] 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, a virtual reality (VR) device, an augmented (AR) device, an Internet of Things (IoT) device, an unmanned aerial vehicle (UAV), or a Personal Digital Assistant (PDA) with wireless communication capability. The UE may be configured to receive and transmit signals over an air interface to one or more cells in a RAN. In some implementations, the UE may be an AI / ML-enabled device and / or an AI / ML capable device that is equipped with AI module(s) and / or ML module(s).

[0040] 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.

[0041] 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. Although the gNB is used as an example in some implementations within the present disclosure, it should be noted that the disclosed implementations may also be applied to other types of base stations. In some implementations, the BS may be an AI / ML-enabled device and / or an AI / ML capable device that is equipped with AI module(s) and / or ML module(s).

[0042] 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.

[0043] Each cell (may often referred to as a serving cell) may provide services to one or more UEs within the cell’s 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 cells.

[0044] A cell may allocate Sidelink (SL) resources for supporting Proximity Service (ProSe), LTE SL services, LTE / NR sidelink communication services, LTE / NR sidelink discovery services, and / or LTE / NR Vehicle-to-Everything (V2X) services. In addition, a cell may allocate DL and / or UL resources for supporting Multicast / Broadcast Service (MBS) services, Non-Terrestrial Networks (NTN) services, positioning services, power serving services and / or Network Energy Saving (NES) services.

[0045] 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.

[0046] The terms, definitions, and abbreviations as given in the present disclosure may be either imported from existing documentation (e.g., European Telecommunications Standards Institute (ETSI), International Telecommunication Union (ITU), or elsewhere) or newly created by 3GPP experts whenever the need for precise vocabulary is identified.

[0047] As discussed above, the frame structure for NR may support 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.

[0048] 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.

[0049] 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.

[0050] Any two or more than two 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.

[0051] 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.

[0052] 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.

[0053] In some implementations, all the designs / embodiment / implementations introduced within this disclosure are not limited to be applied for dealing with the problems discussed within this disclosure. For example, the described embodiments may be applied to solve other problems that exist in the RAN of wireless communication systems. In some implementations, all of the numbers listed within the designs / embodiment / implementations introduced within this disclosure are just examples and for illustration, for example, of how the described methods are executed.

[0054] The term “A and / or B” within the present disclosure means “A”, “B”, or “A and B”. The term “A and / or B and / or C” within the present disclosure means “A”, “B”, “C”, “A and B”, “A and C”, “B and C”, or “A and B and C”. The term “A / B” within the present disclosure means “A” or “B”.

[0055] The measurement configuration (e.g., the MeasConfig IE) may specify measurements to be performed by the UE, and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps. Table 1 below illustrates an example of the MeasConfig IE, according to an example implementation of the present disclosure.

[0056] In 3GPP specification, the serving RAN may associate a measurement object configuration with a report configuration by associating the measObjectId IE (e.g., a measurement object ID of the corresponding measurement object configuration) with the reoprtConfigId IE (e.g., a report configuration ID of the corresponding report configuration) while the measID IE is configured to the UE.

[0057] The MeasIdToAddModList IE may concern a list of measurement identities to add or modify, with for each entry the measId IE, the associated measObjectId IE, and the associated reportConfigId IE. Table 2 below illustrates an example of the MeasIdToAddModList IE, according to an example implementation of the present disclosure.

[0058] The MeasResults IE may cover measured results for intra-frequency, inter-frequency, inter-RAT mobility, and measured results for NR sidelink communication / discovery. Table 3A to Table 3D below illustrates an example of the MeasResults IE, according to an example implementation of the present disclosure.

[0059] In the present disclosure, the LTM / L1-MR (beam-level) measurement report configuration is specified. The enhancements to support the Time-To-Trigger (TTT) timer counting procedures and ReportOnLeave / not-satisfied condition report are specified. Furthermore, the solutions for the MAC entity to assemble the LTM / L1-MR (truncated) MAC CE based on different given priority rules (e.g., different priority rules based on LTM types / events / cell / beam / entering or leaving condition) are also specified. The priority rules may be combined jointly in the MAC layer for LTM / L1-MR (truncated) MAC CE generation.

[0060] In some implementations, a method performed by a user equipment (UE) for an LTM / Layer-1 beam-level measurement report procedure, may include: receiving and storing, from serving BS, one or more LTM / Layer-1 beam-level measurement configuration; providing, one or more LTM / L1-MR (truncated) MAC CE, based on the stored LTM / Layer-1 beam-level measurement configuration; and transmitting the one or more LTM / L1-MR (truncated) MAC CE to the serving RAN.

[0061] In some implementations, beam-specific / cell-specific / event-specific parameters for the one or more LTM / Layer-1 beam-level measurement configuration may include at least one of TTT timer, signaling threshold, offset values, and multiplexing window. In some implementations, L1-MR multiplexing rules may be applied while the UE is providing the MAC CE. The L1-MR multiplexing rules may be based on at least one of: beam-based priority rules, cell-based priority rules, event-based priority rules, and entering / leaving condition-based priority rules. In some implementations, the method may further include providing, by UE, ‘not-satisfying event’ L1 measurement report as part of L1-MR to the serving RAN.

[0062] Layer-1 measurement report configuration

[0063] The layer-1 / LTM (beam) measurement reporting / triggering events may be configured to UEs by serving RAN. The layer-1 / LTM (beam) measurement reporting / triggering events may include LTM1, LTM2, LTM3, LTM4, LTM5, and / or LTM6. The LTM1 / LTM2 / LTM3 / LTM4 / LTM5 / LTM6 may be implemented by the PHY layer and may be evaluated by the MAC entity. In some implementations, a UE may be configured with one or more LTM reporting / triggering events in a report configuration. In some implementations, a UE may be configured with one or more Layer-1 beam reporting / triggering events and one or more Layer-3 (beam / cell) triggering events in a report configuration.

[0064] The UE may perform / initiate a measurement report procedure if all of the Layer-1 / Layer-3 reporting / triggering events associated with a report configuration are fulfilled. The (Layer-3) triggering event configured jointly with Layer-1 (beam) measurement may include the following Layer-3 events: A1 / A2 / A3 / A4 / A5 / A6 / B1 / B2 / I1 / C1 / C2 / D1 / D2 / X1 / X2 / Y1 / Y2 / Z1 / H1 / H2. In some implementations, a UE may be configured with one or more Layer-1 beam reporting / triggering events and / or one or more Layer-1 cell triggering events in a report configuration. In some implementations, a report configuration may be associated with any combinations of one or more Layer-1 / Layer-3 cell / beam measurement reporting / triggering events.

[0065] In some implementations, each LTM1 / LTM2 / LTM3 / LTM4 / LTM5 / LTM6 event may be configured with leaving conditions. In some implementations, each LTM1 / LTM2 / LTM3 / LTM4 / LTM5 / LTM6 event may not be configured with leaving conditions. In some implementations, the entering condition of the LTM1 / LTM2 / LTM3 / LTM4 / LTM5 / LTM6 may also be configured as triggering events for a UE to initiate a conditional LTM operation. In some implementations, the entering condition of at least one of LTM1, LTM2, LTM3, LTM4, LTM5, and LTM6 may also be configured as a triggering event for a UE to initiate a conditional LTM operation (e.g., conditional LTM1 (CLTM1) / conditional LTM2 (CLTM2) / conditional LTM3 (CLTM3) / conditional LTM4 (CLTM4) / conditional LTM5 (CLTM5) / conditional LTM6 (CLTM6)). In some implementations, the leaving condition of at least one of LTM1, LTM2, LTM3, LTM4, LTM5, and LTM6 may also be configured as triggering event for a UE to stop a conditional LTM operation (e.g., CLTM1 to CLTM6). In some implementations, the serving cell may be the primary cell, secondary cell, primary secondary cell of the UE.

[0066] LTM1: Serving / current beam of serving cell becomes better than a threshold. The entering condition for the LTM1 event may be defined by Inequality LTM 1-1, and the leaving condition of the LTM1 event may be defined by Inequality LTM 1-2. Inequality LTM 1-1 (Entering condition) may be expressed as: Ms - Hys > Thresh. Inequality LTM 1-2 (Leaving condition) may be expressed as: Ms + Hys< Thresh. The variables in the formula may be defined as follows. Ms may be the measurement result of the current beam of the serving cell, not taking into account any offsets. Ms may be associated with a specific beam direction or a TCI state. Hys may be the hysteresis parameter for this event (e.g., hysteresis as defined within the reportConfigNR IE for this event). Thresh may be the threshold parameter for this event (e.g., a1-Threshold as defined within the reportConfigNR IE for this event). Ms may be expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Hys may be expressed in dB. Thresh may be expressed in the same unit as Ms. The measurement result may be Layer-1 measurement result.

[0067] LTM2: Serving / current beam of serving cell becomes worse than a threshold. The entering condition of the LTM2 event may be defined by Inequality A2-1, and the leaving condition of the LTM2 event may be defined by Inequality A2-2. Inequality A2-1 (Entering condition) may be expressed as: Ms + Hys < Thresh. Inequality A2-2 (Leaving condition) may be expressed as: Ms - Hys > Thresh. Ms may be the measurement result of the current beam of serving cell, not taking into account any offsets. Hys may be the hysteresis parameter for this event (e.g., hysteresis as defined within the reportConfigNR IE for this event). Thresh may be the threshold parameter for this event (e.g., the a2-Threshold as defined within the reportConfigNR IE for this event). Ms may be expressed in dBm in case of RSRP, or may be expressed in dB in case of RSRQ and RS-SINR. Hys may be expressed in dB. Thresh may be expressed in the same unit as Ms. The measurement result may be a Layer-1 measurement result.

[0068] LTM3: A beam of neighbor cell becomes amount of offset better than the current / serving beam of PCell / PSCell. The entering condition of the LTM3 may be defined by Inequality A3-1, and the leaving condition of the LTM3 may be defined by Inequality A3-2. Inequality A3-1 (Entering condition) may be expressed as: Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + Off. Inequality A3-2 (Leaving condition) may be expressed as: Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off.

[0069] Mn may be the measurement result of a beam of a neighboring cell, not taking into account any offsets. Ofn may be the measurement object specific offset of the reference signal of the neighbor cell (e.g., the offsetMO as defined within the measObjectNR IE corresponding to the neighbor cell). Ocn may be the cell / beam specific offset of the neighbor cell (e.g., the cellIndividualOffset as defined within the measObjectNR IE corresponding to the frequency of the neighbor cell, or the cellIndividualOffset as defined within the reportConfigNR IE), and set to zero if not configured for the neighbor cell. In other words, all of the beam of the neighbor cell may share the same cellIndividualOffset value (e.g., cell-specific design). In some implementations, the cellIndividualOffset may be beam-specific. In the beam-specific condition, the cellIndividualOffset (i) may be configured with associated SSB index i or beam index i for the beam-specific offset of the neighbor cell to the UE respectively. Therefore, the UE may need evaluate the triggering event based on the SSB index / beam index of the current beam of the SpCell and the cellIndividualOffset (i) associated with the corresponding SSB index / beam index.

[0070] Mp may be the measurement result of the current / serving beam quality of SpCell, not taking into account any offsets. Ofp may be the measurement object specific offset of the current beam of SpCell (e.g., the offsetMO as defined within the measObjectNR IE corresponding to the SpCell). In some implementations, the offsetMO may be cell-specific to all beam directions of the SpCell. In some implementations, the offsetMO may be beam-specific to each beam directions of the SpCell. In beam-specific condition, an offsetMO(i) value of specific SSB index / beam index may be configured respectively to the UE. Therefore, the UE may need evaluate the triggering event based on the SSB index / beam index of the current beam of the SpCell and and offsetMO(i) associated with the corresponding SSB index / beam index.

[0071] Ocp may be the (e.g., cell specific) offset of the SpCell (e.g., the cellIndividualOffset as defined within the measObjectNR IE corresponding to the current / serving beam of SpCell), and may be set to zero if not configured for the SpCell. In some implementations, the cellIndividualOffset may be cell-specific to all beam directions of the SpCell. In some implementations, the cellIndividualOffset may be beam-specific to each beam directions of the SpCell. In beam-specific condition, a cellIndividualOffset (i) value of specific SSB index / beam index may be configured respectively to the UE. Therefore, the UE may need evaluate the triggering event based on the SSB. index / beam index of the current beam of the SpCell and and cellIndividualOffset (i) associated with the corresponding SSB index / beam index.

[0072] Hys may be the hysteresis parameter for this event (e.g., hysteresis as defined within the reportConfigNR IE for this event), which may also be cell-specific or beam-specific (e.g., hysteresis(i)) associated with a beam index i. Off may be the offset parameter for this event (e.g., the a3-Offset as defined within the reportConfigNR IE for this event), which may also be cell-specific (e.g., a parameter common to all of the SSB index or beams of a cell) or beam-specific (e.g., the a3-Offset (i)) associated with a beam index i.

[0073] Mn and Mp may be expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR, which may also be cell-specific or beam-specific. Ofn, Ocn, Ofp, Ocp, Hys, and Off may be expressed in dB, which may also be cell-specific or beam-specific. In some implementations, the definition of Event LTM3 may also apply to CondEvent LTM3.

[0074] LTM4: A beam of neighbor cell becomes better than an absolute threshold. The entering condition of the LTM4 event may be defined by Inequality LTM4-1, and the leaving condition of the LTM4 event may be defined by Inequality LTM4-2. Inequality LTM4-1 (Entering condition) may be expressed as: Mn + Ofn + Ocn - Hys > Thresh. Inequality LTM4-2 (Leaving condition) may be expressed as: Mn + Ofn + Ocn + Hys < Thresh. Mn may be the measurement result of one of beam of the neighboring cell or the measurement result of current beam of serving PSCell (e.g., in case it is configured as candidate PSCell for CondEvent LTM4 evaluation) for Conditional handover / LTM with candidate SCG(s) case, not taking into account any offsets. Ofn may be the measurement object specific offset of a beam of the neighbor cell (e.g., the offsetMO as defined within the measObjectNR IE corresponding to the neighbor cell). The parameter may be cell-specific or beam-specific. Ocn may be the measurement object specific offset of the beam of neighbor cell (e.g., the cellIndividualOffset as defined within the measObjectNR IE corresponding to the neighbor cell, or the cellIndividualOffset as defined within the reportConfigNR IE), and set to zero if not configured for the neighbour cell. The parameter may be cell-specific or beam-specific. Hys may be the hysteresis parameter for this event (e.g., hysteresis as defined within the reportConfigNR IE for this event). The parameter may be cell-specific or beam-specific. Thresh may be the threshold parameter for this event (e.g., the a4-Threshold as defined within the reportConfigNR IE for this event). The parameter may be cell-specific or beam-specific. Mn may be expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, and Hys may be expressed in dB, which may also be cell-specific or beam-specific. Thresh may be expressed in the same unit as Mn. In some implementations, the definition of Event LTM4 may also apply to CondEvent LTM4.

[0075] LTM5: Serving / Current beam of serving cell (e.g., PCell / PSCell) becomes worse than an absolute threshold1 and a beam of neighbor / SCell becomes better than another absolute threshold2. The entering condition of the LTM5 event may be defined by Inequality LTM5-1 and Inequality LTM5-2, and the leaving condition of the LTM5 event may be defined by Inequality LTM5-3 and Inequality LTM5-4. Inequality LTM5-1 (Entering condition 1) may be expressed as: Mp + Hys < Thresh1. Inequality LTM5-2 (Entering condition 2) may be expressed as: Mn + Ofn + Ocn - Hys > Thresh2. Inequality LTM5-3 (Leaving condition 1) may be expressed as: Mp - Hys > Thresh1. Inequality LTM5-4 (Leaving condition 2) may be expressed as: Mn + Ofn + Ocn + Hys < Thresh2.

[0076] Mp may be the measurement result of the serving beam of NR SpCell, not taking into account any offsets. Mn may be the measurement result of a beam of the neighboring cell, not taking into account any offsets. Ofn may be the measurement object specific offset of the neighbor cell (e.g., the offsetMO as defined within the measObjectNR IE corresponding to the neighbor cell). The parameter may be cell-specific or beam-specific. In some implementations, the offsetMO may be beam-specific to each beam directions of the SpCell. In beam-specific condition, an offsetMO(i) value of specific SSB index / beam index may be configured respectively to the UE. Therefore, the UE may need evaluate the triggering event based on the SSB index / beam index of the current beam of the SpCell and and offsetMO(i) associated with the corresponding SSB index / beam index.

[0077] Ocn may be the cell specific offset of the neighbor cell (e.g., the cellIndividualOffset as defined within the measObjectNR IE corresponding to the neighbor cell, or the cellIndividualOffset as defined within the reportConfigNR IE), and set to zero if not configured for the neighbor cell. The parameter may be cell-specific or beam-specific. In beam-specific condition, a cellIndividualOffset (i) value of specific SSB index / beam index may be configured respectively to the UE. Therefore, the UE may need to evaluate the triggering event based on the SSB index / beam index of the current beam of the SpCell and and the cellIndividualOffset (i) associated with the corresponding SSB index / beam index. Hys may be the hysteresis parameter for this event (e.g., hysteresis as defined within the reportConfigNR IE for this event), which may also be cell-specific or beam-specific. In beam-specific condition, a hysteresis (i) value of specific SSB index / beam index may be configured respectively to the UE. Therefore, the UE may need to evaluate the triggering event based on the SSB index / beam index of the current beam of the SpCell and hysteresis (i) associated with the corresponding SSB index / beam index.

[0078] Thresh1 may be the threshold parameter for this event (e.g., the a5-Threshold1 as defined within the reportConfigNR IE for this event), which may also be cell-specific (e.g., a parameter common to all of the SSB index or beams of a cell) or beam-specific (e.g., the a5-Threshold1(i)) associated with a beam index i. Thresh2 may be the threshold parameter for this event (e.g., the a5-Threshold2 as defined within the reportConfigNR IE for this event), which may also be cell-specific (e.g., a parameter common to all of the SSB index or beams of a cell) or beam-specific (e.g., the a5-Threshold2(i)) associated with a beam index i. Mn and Mp may be expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, and Hys may be expressed in dB, which may also be cell-specific (e.g., a parameter common to all of the SSB index or beams of a cell) or beam-specific. Thresh1 may be expressed in the same unit as Mp. Thresh2 may be expressed in the same unit as Mn. In some implementations, the definition of Event LTM5 may also apply to CondEvent LTM5.

[0079] LTM6: A beam of neighbor cell becomes amount of offset better than a current SCell. The entering condition of the LTM6 event may be defined by Inequality LTM6-1, and the leaving condition of the LTM6 event may be defined by Inequality LTM 6-2. Inequality LTM6-1 (Entering condition) may be expressed as: Mn + Ocn - Hys > Ms + Ocs + Off. Inequality LTM 6-2 (Leaving condition) may be expressed as: Mn + Ocn + Hys < Ms + Ocs + Off. Mn may be the measurement result of a beam of a neighboring cell, not taking into account any offsets. Ocn may be the cell specific offset of the neighbor cell (e.g., the cellIndividualOffset as defined within the associated measObjectNR IE, or the cellIndividualOffset as defined within the reportConfigNR IE), and set to zero if not configured for the neighbor cell. In other words, all of the beam of the neighbour cell may share the same cellIndividualOffset value (e.g., cell-specific design). In some implementations, the cellIndividualOffset may be beams-specific. In addition, each neighbor cell may be further configured with different cellIndividualOffset value. In the beam-specific condition, beamIndividualOffset (i) may be configured with associated SSB index i or beam index i for the beam-specific offset of the neighbor cell to the UE respectively. Therefore, the UE may need evaluate the triggering event based on the SSB index / beam index of the current beam of the SpCell and the cellIndividualOffset (i) associated with the corresponding SSB index / beam index.

[0080] Ms may be the measurement result of the current / serving beam of serving cell, not taking into account any offsets. Ocs may be the cell specific offset of current / serving beam of the serving cell (e.g., the cellIndividualOffset as defined within the associated measObjectNR IE), and may be set to zero if not configured for the serving cell, In some implementations, the cellIndividualOffset may be cell-specific (e.g., common to all beams of a serving cell) or beam-specific (e.g., the cellIndividualOffset(i) may be associated with an SSB index i / beam index i of the concerned cell). Hys may be the hysteresis parameter for this event (e.g., hysteresis as defined within the reportConfigNR IE for this event), which may be cell-specific (e.g., common hysteresis value to all beams of a serving cell) or beam-specific (e.g., hysteresis (i) may be associated with an SSB index i / beam index i of the concerned cell). Off may be the offset parameter for this event (e.g., the a6-Offset as defined within the reportConfigNR IE for this event) which may be cell-specific (e.g., common a6-Offset value to all beams of a serving cell) or beam-specific (e.g., the a6-Offset (i) may be configured associated with an SSB index i / beam index i of the concerned cell). Mn and Ms may be expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ocn, Ocs, Hys, and Off may be expressed in dB, which may be cell-specific (e.g., common a6-Offset value to all beams of a serving cell) or beam-specific.

[0081] FIG. 1 is a diagram illustrating a time-based evaluation for LTM event conditions 100, according to an example implementation of the present disclosure. As illustrated in FIG. 1, the diagram may depict the relationship between beam quality measurements and threshold parameters over time, showing how entering conditions and leaving conditions for an LTM event may be evaluated.

[0082] The vertical axis may represent the beam quality measurement in units such as dBm for DL-RSRP, while the horizontal axis may represent time in milliseconds (ms), symbol, or slot. The diagram may include a trigger threshold 110, a layer-1 (beam) threshold 120, and a leave threshold 130. The trigger threshold 110 may be equal to the layer-1 (beam) threshold 120 plus hysteresis, and the leave threshold 130 may be equal to the layer-1 (beam) threshold 120 minus hysteresis.

[0083] A beam quality curve 140 may represent the measurement result of the beam over time. At a first time point 150, the beam quality curve 140 may satisfy the entering condition 152 (e.g., the measurement result may be equal to or greater than the trigger threshold 110). Upon satisfying the entering condition 152, a Time-to-Trigger (TTT) timer may be started. The TTT timer may include a Time-to-Trigger (TTT) Counting period 154. During the TTT counting period 154, the UE may continue to monitor whether the entering condition 152 remains satisfied. As illustrated in FIG. 1, if the entering condition 152 continues to be met throughout the TTT counting period 154, then at a second time point 156, upon expiry of the TTT timer, the UE may determine that the entering condition 152 has been fulfilled and trigger an L1-measurement report (L1-MR) 158.

[0084] In some implementations, after the L1-MR 158 is triggered, the beam quality curve 140 may change. At a third time point 160, the beam quality curve 140 may satisfy the leaving condition 162 (e.g., the measurement result may be equal to or lower than the leave threshold 130). Upon satisfying the leaving condition 162, a Time-to-Trigger (TTT) timer may be started. The TTT timer may include a Time-to-Trigger (TTT) Counting period 164. During the TTT counting period 164, the UE may continue to monitor whether the leaving condition 162 remains satisfied. As illustrated in FIG. 1, if the leaving condition 162 continues to be met throughout the TTT counting period 164, then at a fourth time point 166, upon expiry of the TTT timer, the UE may determine that the leaving condition 162 has been fulfilled and trigger an L1-measurement report (L1-MR) 168.

[0085] The use of hysteresis parameters and TTT timers may prevent rapid oscillation between entering and leaving conditions due to temporary signal variations, thereby improving the stability and efficiency of the LTM process.

[0086] TTT timer design

[0087] In some implementations, the TTT may be evaluated per beam, and measurement report may only be triggered by the beam that has satisfied the condition (e.g., entering / leaving condition) for the whole duration of the TTT. In some implementations, the TTT timer may not be restarted if the current beam changes and the entering condition associated with the new current beam is still met.

[0088] In some implementations, the TTT timer of leaving condition may be considered. In some implementations, a current beam indication or current beam change indication may need to be provided from lower layers (e.g., PHY layer or MAC layer) to upper layers (e.g., MAC layer or RRC layer). The current beam indication may be implemented via the TCI state ID / SSB index / CSI-RS index.

[0089] A beam may be configured / associated with more than one measurement / report configuration. For example, the TCI state ID, SSB index, and / or CSI-RS index in more than one measurement / report configuration may correspond to the same value. In some implementations, one or more TTT timers associated with a beam may be counted simultaneously, and each TTT timer may be counted independently. In some implementations, a beam may not be configured / associated with more than one measurement / report configurations.

[0090] In some implementations, for a beam (e.g., the current beam of the serving cell or a beam of the neighbor cell), only a TTT timer counting activity may be allowed to be activated in time domain. In addition, the UE may start the evaluation of another report configuration and so the counting TTT timer activity only after a previous evaluation associated with the same beam has been finished (e.g., entering condition fulfilled / leaving condition fulfilled / TTT timer expiry) to the UE.

[0091] In some implementations, for all beams of a cell (e.g., the serving cell or neighbor cell), only a TTT timer counting activity may be allowed to be activated in time domain. In addition, the UE may start the evaluation of another report configuration and so the counting TTT timer activity may be triggered / activated only after a previous evaluation associated with the same cell has been finished (e.g., entering condition fulfilled / leaving condition fulfilled / TTT timer expiry) to the UE.

[0092] In some implementations, an ongoing TTT timer may not be restarted if the current beam changes while the leaving condition is still met with the new current beam. In some implementations, an ongoing TTT timer may be restarted if the current beam changes while the leaving condition is still met with the new current beam. In some implementations, different TTT timers (and the associated initial values) may be configured for the entering condition and the leaving condition of the L1 measurement event respectively.

[0093] In some implementations, a specific TTT timer may be configured in a measurement / triggering event and so the TTT timer may be applied to the beam(s) considered / included for evaluation. A beam may be included / considered in more than one events. In other words, two or more TTT timers (e.g., TTT1, TTT2, and TTT3) may be started and counted by a UE with a specific beam. TTT1may be associated an LTM event LTM#a, TTT2may be associated an LTM event LTM#b, and TTT3may be associated an LTM event LTM#c. The UE may trigger TTT1counting activity firstly and then TTT2and then TTT3.

[0094] In some implementations, the timer TTT1(associated with an entering / leaving condition) may expire, and the UE may keep / maintain the running TTT2 / TTT3associated with the same beam. In some implementations, a beam may only be able to be associated with a counting timer and the serving base station may try to avoid the multiple TTT timer counting condition to the same beam based on report configuration.

[0095] In some implementations, a beam may only be able to be associated with a counting timer (e.g., TTT1) and the UE may not trigger TTT2 / TTT3unless TTT1expires. In some implementations, the proposed mechanism may be implemented per beam. In some implementations, the proposed mechanism may be implemented per cell.

[0096] In some implementations, different priority sequences may be defined (e.g., pre-defined in technical specification) or configured (e.g., being configured by the serving RAN via broadcasting system information or UE-specific RRC signaling) for the report configuration (and so the evaluation procedure of the report configuration). In some implementations, a priority index may be configured in the report configuration. In some implementations, the MAC layer may perform the priority rule for different (Layer-1) reports.

[0097] In addition, the running TTT timer of a low priority report configuration may be interrupted by high priority report configuration. In some implementations, the counting activity of a TTT timer (e.g., the UE may start to count a TTT timer from its initial value to zero) of low priority report configuration may be postponed (or be stopped) until the UE finishes the TTT timer county activity of a high priority report configuration.

[0098] In some implementations, the leaving condition of a report configuration (and the TTT timer counting activity associated with the leaving condition) may have a higher priority than the entering condition of the same report configuration (e.g., the entering condition associated with different target beam / cell).

[0099] In some implementations, the entering condition of a report configuration (and the TTT timer counting activity associated with the entering condition) may have a higher priority than the leaving condition of the same report configuration (e.g., the leaving condition of the same or different beam / cell).

[0100] In some implementations, the entering condition of a report configuration (and the TTT timer counting activity associated with the entering condition) may have a higher priority than the leaving condition of other report configurations (e.g., the leaving condition and the associated TTT timer of the same or different beam associated with different report configurations).

[0101] In some implementations, the leaving condition of a report configuration (and the TTT timer counting activity associated with the leaving condition) may have a higher priority than the entering condition of other report configurations (e.g., the entering condition and the associated TTT timer of the same or different beam associated with different report configurations).

[0102] In some implementations, the TCI state activation / de-activation MAC CE may also control the activation / deactivation of LTM / layer-1 measurement associated with the TCI state ID. To a UE, the UE may activate an LTM / L1 measurement if the beam (associated with a TCI state ID) is activated by a TCI state activation MAC CE. To a UE, the UE may de-activate an LTM / L1 measurement if the beam (associated with a TCI state ID) is de-activated by a TCI state activation MAC CE. The UE may release the measurement results and associated timers / counters of an LTM / L1 measurement report configuration if the LTM / L1 measurement report configuration is deactivated by the serving RAN.

[0103] ‘ReportOnLeave’ design & Measurement Report design for Layer-1 measurement

[0104] FIG. 2 is a diagram illustrating a conditional LTM procedure 200, according to an example implementation of the present disclosure. As illustrated in FIG. 2, the diagram may depict the communication signaling exchange between a UE 210 and a RAN 220.

[0105] The RAN 220 may transmit a Layer-1 measurement configuration 230 to the UE 210. The Layer-1 measurement configuration 230 may include parameters for configuring the UE 210 to perform Layer-1 measurements on one or more beams or cells. The Layer-1 measurement configuration 230 may specify measurement objects, reporting configurations, thresholds, hysteresis parameters, and TTT timer values for various LTM events, including both entering conditions and leaving conditions.

[0106] After receiving the Layer-1 measurement configuration 230, the UE 210 may perform Layer-1 measurements on the configured beams or cells. When an entering condition for an LTM event is satisfied and a corresponding TTT timer expires, the UE 210 may transmit a Layer-1 measurement report 240 to the RAN 220 via a MAC CE. The Layer-1 measurement report 240 may include measurement results such as RSRP for one or more beams or cells. When a leaving condition for the LTM event is satisfied and a corresponding TTT timer expires, the UE 210 may transmit another Layer-1 measurement report 250 to the RAN 220 via a MAC CE.

[0107] As illustrated in FIG. 2, upon receiving one or more Layer-1 measurement reports from the UE 210, the RAN 220 may determine whether to initiate a conditional LTM procedure. If the RAN 220 determines that a conditional cell switch is appropriate based on the received measurement reports, the RAN 220 may transmit a conditional LTM cell switch command 260 to the UE 210. The conditional LTM cell switch command 260 may include information identifying a target cell or target beam to which the UE 210 should switch, along with any necessary configuration parameters for accessing the target cell or target beam. The conditional LTM cell switch command 260 may be transmitted via a MAC CE or other Layer-1 / Layer-2 signaling mechanism to enable a fast cell switch with reduced latency compared to traditional Layer-3 based mobility procedures.

[0108] FIG. 3 is a diagram illustrating a conditional LTM procedure 300, according to an example implementation of the present disclosure. As illustrated in FIG. 3, the diagram may depict the communication signaling exchange between a UE 310 and a RAN 320, where different signaling mechanisms may be used for reporting entering conditions and leaving conditions.

[0109] The RAN 320 may transmit a Layer-1 measurement configuration 330 to the UE 310. The Layer-1 measurement configuration 330 may include parameters for configuring the UE 310 to perform Layer-1 measurements on one or more beams or cells. The Layer-1 measurement configuration 330 may specify measurement objects, reporting configurations, thresholds, hysteresis parameters, and TTT timer values for various LTM events, including both entering conditions and leaving conditions.

[0110] After receiving the Layer-1 measurement configuration 330, the UE 310 may perform Layer-1 measurements on the configured beams or cells. When an entering condition for an LTM event is satisfied and a corresponding TTT timer expires, the UE 310 may transmit a Layer-1 measurement report 340 to the RAN 320 via a MAC CE. The Layer-1 measurement report 340 may include measurement results such as RSRP for one or more beams or cells.

[0111] Upon receiving the Layer-1 measurement report 340, the RAN 320 may determine whether to initiate a conditional LTM procedure. If the RAN 320 determines that a conditional cell switch is appropriate based on the received measurement report, the RAN 320 may transmit a conditional LTM cell switch command 350 to the UE 310. The conditional LTM cell switch command 350 may include information identifying a target cell or target beam to which the UE 310 should switch, along with any necessary configuration parameters for accessing the target cell or target beam.

[0112] After receiving the conditional LTM cell switch command 350, the UE 310 may continue to monitor the configured measurements and evaluate whether the execution conditions for the cell switch are satisfied. In some implementations, when a leaving condition for the LTM event is satisfied and a corresponding TTT timer expires, the UE 310 may transmit another Layer-1 measurement report 360 to the RAN 320. Unlike the Layer-1 measurement report 340 for the entering condition, the Layer-1 measurement report 360 for the leaving condition may be transmitted via RRC signaling rather than via a MAC CE.

[0113] In some implementations, the Layer-1 measurement configuration may be configured to support Layer-1 mobility event (e.g., the Lower-layer Triggered Mobility (LTM) supported by 3GPP R-18 specification and beyond). In addition, the L1 measurement reporting upon / after the leaving condition is fulfilled may also be supported. In the present disclosure, technical solutions to support the Layer-1 measurement report while the Layer-1 leaving condition is fulfilled may be proposed.

[0114] In some implementations, the proposed solutions may be applicable to Layer-1 measurement reporting. In some implementations, the Layer-1 measurement report may be triggered by one or more of the following LTM events (a)-(d) based on beam specific quality of a serving cell and candidate cells as the L1 LTM measurement events.

[0115] (a) Event LTM2: A beam of the serving cell becomes worse than an absolute threshold.

[0116] (b) Event LTM3: A beam of a candidate cell becomes an amount of offset better than a beam of the serving cell.

[0117] (c) Event LTM4: A beam of a candidate cell becomes better than an absolute threshold.

[0118] (d) Event LTM5: A beam of the serving cell becomes worse than an absolute threshold1 and a beam of a candidate cell becomes better than an absolute threshold2.

[0119] In addition, the Reference Signal (RS) type for the Event LTM2, Event LTM3, Event LTM4, and Event LTM5 may include at least one of TRS, CSI-RS, SSB, and on-demand SSB (OD-SSB). In some implementations, both Event LTM3 and Event LTM5 may be supported for the Layer-1 measurement report.

[0120] In some implementations, a new MAC CE (e.g., a MAC CE with a logical channel ID to indicate a Layer-1 measurement report activation) may be configured to support the L1-MR or LTM-MR (e.g., Layer-1 measurement report) to the serving RAN. In some implementations, truncated MAC CE may be configured to support the L1-MR or LTM-MR. In some implementations, the L1 measurement results may include at least one of the L1-RSRP, L1-RSRQ, L1-SINR, CQI, PMI, RI, and LI of one or more candidate cells.

[0121] In some implementations, the L1 measurement results may include the following (a)-(c).

[0122] (a) Beam information: SSBRI / CRI of N beams (or LTM configuration id + SSB index / CSI-RS id / TCI state ID associated with a cell (e.g., PCI, cellidenity, servingcellindex)).

[0123] (b) Beam quantity: L1-RSRP or L1-SINR (e.g., up to RAN1) of N beams.

[0124] (c) Triggered event information (e.g., ReportConfigID).

[0125] In some implementations, each of the configured Event LTM2, Event LTM3, Event LTM4, and Event LTM5 may be associated with a leaving condition. In addition, an LTM event may indicate an ReportOnLeaveL1 IE / indicator (or an ReportOnLeaveLTM IE / indicator). In some implementations, the ReportOnLeave_L1 IE / indicator may be configured as a Boolean value (e.g., ‘true’ or ’false’) to indicate whether the UE should provide an L1 measurement report upon / after the leaving condition of an LTM event (e.g., Event LTM2, Event LTM3, Event LTM4, or Event LTM5) is fulfilled.

[0126] In some implementations, the ReportOnLeaveL1 IE / indicator may include the configuration about whether the Layer-1 measurement report (e.g., triggered due to the leaving condition is fulfilled or not) should be transmitted by RRC signaling (e.g., ReportOnLeaveL1 = ‘RRCSignaling’ / ’RRC’) or by MAC CE (e.g., ReportOnLeaveL1 = ‘MAC CE’ / ’MAC’). In some implementations, the Layer-1 measurement report may be allowed / enabled to be transmitted via either MAC CE or RRC signaling (e.g., ReportOnLeaveL1 = {MAC CE, RRC}).

[0127] The leaving condition evaluation and reporting may also be supported. In the present disclosure, two signaling approaches for the UE to report the measurement results while the leaving condition is fulfilled may be proposed.

[0128] The UE may report the L1 measurement results by transmitting RRC signaling (e.g., the RRCReconfigurationComplete message, the UE Assistance Information) upon / after the UE determines to switch to the target cell (e.g., which may be a candidate cell of the Layer-1 mobility event or Layer-3 mobility event).

[0129] In some implementations, the pending RRC signaling may be transmitted to the source cell before the LTM operation (or before the conditional LTM operation).

[0130] In some implementations, the LTM operation may include at least one of the following steps (a)-(f).

[0131] (a) The UE receives the RRC pre-configuration for the LTM candidate configuration.

[0132] (b) The UE receives the LTM serving cell switch command from the serving RAN.

[0133] (c) The UE performs the early synchronization with an LTM candidate cell.

[0134] (d) The RRC entity of the UE performs the LTM operation by applying the Layer-2 / Layer-1 parameters associated with the LTM candidate cell.

[0135] (e) The UE transmits an LTM complete message to the serving RAN.

[0136] (f) The UE transmits L1 / L3 (beam-level / cell-level) (CSI-RS / SSB) measurement reports to the serving RAN.

[0137] In some implementations, the LTM operation may include at least one of the following steps (a)-(g).

[0138] (a) The UE receives the RRC pre-configuration for the conditional LTM candidate configuration.

[0139] (b) The UE receives the conditional LTM serving cell switch activation message from the serving RAN.

[0140] (c) The UE (e.g., the MAC entity of the UE) determines to initiate an LTM serving cell switch operation to change its serving cell to an LTM candidate.

[0141] (d) The UE performs the early synchronization with an LTM candidate cell.

[0142] (e) The RRC entity of the UE performs the LTM operation by applying the Layer-2 / Layer-1 parameters associated with the LTM candidate cell.

[0143] (f) The UE transmits an LTM complete message to the serving RAN.

[0144] (g) The UE transmits L1 / L3 (beam-level / cell-level) (CSI-RS / SSB) measurement reports to the serving RAN.

[0145] In some implementations, the pending Layer-1 measurement report (e.g., which is waiting to be transmitted via RRC signaling) may be released upon / after the LTM operation (e.g., upon the UE receives the LTM Cell switch MAC CE) or upon / after the condition LTM operation (e.g., upon the UE triggers the switching activity to a target cell based on the serving RAN configuration).

[0146] In some implementations, the pending RRC signaling may be transmitted to the target cell after the LTM operation (or after the conditional LTM operation). In this condition, the UE may keep the pending Layer-1 measurement report (e.g., triggered by the fulfilled leaving condition) upon / after the LTM operation (e.g., upon the UE receives the LTM cell switch MAC CE) or upon / after the conditional LTM operation (e.g., upon the UE triggers the switching activity to a target cell based on the serving RAN configuration).

[0147] The UE may report the L1 measurement results (e.g., triggered by the fulfilled leaving condition) by transmitting one or more MAC CEs.

[0148] In some implementations, the pending MAC CE (e.g., which conveys the Layer-1 measurement triggered by the fulfilled leaving condition) may be transmitted to the source cell before the LTM operation (or before the conditional LTM operation). In some implementations, the pending Layer-1 measurement report (e.g., which is waiting to be transmitted via the MAC CE) may be released upon / after the LTM operation (e.g., upon the UE receives the LTM cell switch MAC CE) or upon / after the condition LTM operation (e.g., upon the UE triggers the switching activity to a target cell based on the serving RAN configuration).

[0149] In some implementations, the pending MAC CE (e.g., which conveys the Layer-1 measurement triggered by the fulfilled leaving condition) may be transmitted to the target cell after the LTM operation (or after the conditional LTM operation). In this condition, the UE may keep the pending Layer-1 measurement report MAC CE (e.g., triggered by the fulfilled leaving condition) upon / after the LTM operation (e.g., upon the UE receives the LTM cell switch MAC CE) or upon / after the conditional LTM operation (e.g., upon the UE triggers the switching activity to a target cell based on the serving RAN configuration).

[0150] In some implementations, the UE may be able to transmit the Layer-1 measurement via both of the RRC signaling and MAC CE upon / after the leaving condition is fulfilled. However, the UE may firstly try to report the Layer-1 measurement report via the MAC CE before the (conditional) LTM operation is triggered. Then, upon / after the (conditional) LTM operation is triggered, the UE may store the pending Layer-1 measurement report (e.g., the MAC entity may forward the Layer-1 measurement result to the RRC layer before the MAC entity is reset due to the triggering of (conditional) LTM operation). Then, after the UE switches to the target cell successfully (e.g., the (conditional) LTM operation is considered successfully), the pending Layer-1 measurement report (e.g., triggered due to the fulfilled leaving condition) may be reported via RRC signaling.

[0151] In some implementations, the UE may store the pending L1 measurement report because the UE has no UL grant associated the candidate cell or the UE has not synchronized with the LTM candidate cell. In some implementations, the UE may be pre-configured by the serving RAN (e.g., as part of LTM candidate configuration) to store and transmit the pending L1 measurement report after the (conditional) LTM operation. The serving RAN may need to collect the L1 measurement report even the (conditional) LTM operation is terminated successfully for the reason of network management / self-organized network (SON) / mobility management / artificial intelligence (AI) model training (or machine learning) or UE data collection. In contrast, the UE may need not to store and report any pending L1 (beam) measurement report if the serving RAN does not configure the UE to do so via DL control signaling (e.g., as part of LTM configuration in the RRCReconfiguration message).

[0152] In some implementations, the UE may report that the pending L1 (beam-level) measurement report is available (e.g., by transmitting an indication in the RRCResumeComplete message, RRCSetupComplete message, RRCRe-establishmentComplete message, or UEAssistanceInformation message). Then, the serving RAN may enquiry / request the UE to transmit the stored L1 (beam) measurement report by transmitting DL control signaling (e.g., L1-beamReport-Enquiry indicator ={true} in the DL RRC signaling). Upon / after receiving the L1-beamReport-Enquiry indicator, the UE may report the pending L1 (beam) measurement report to the serving RAN via a given UL (configured) grant.

[0153] In some implementations, the serving RAN may enquire a UE to report the stored L1 (beam) measurement reports to the serving RAN without the UE reporting whether any L1 (beam) measurement report is pending at the UE or not. For example, the serving RAN may transmit the L1-beamReport-Enquiry indicator in one or more DL control signaling (e.g., the RRCSetup message, RRCResume message, RRCRe-establishment message). Then, the UE may report the stored L1 (beam) measurement reports in the UL message (e.g., the RRCSetupComplete message, RRCResumeComplte message, RRCRe-establishmentComplete message) to the serving RAN.

[0154] In some implementations, the UE may store an L1 (beam) measurement report for a given validity time span (e.g., 5 minutes as default setting). The validity period of L1 (beam) measurement report may be pre-defined by technical specification or be pre-configured by the serving RAN. The UE may start to count the validity of a stored L1 (beam) report upon / after the UE store the L1 (beam) report in the UE side (e.g., in the memory or buffer module of the UE side).

[0155] In addition, the UE may consider a stored L1 (beam) measurement report as out-of-date / invalid once the UE has stored the L1 (beam) measurement report longer than the given validity time span of the stored L1 (beam) report. In this condition, the UE may remove / release the L1 (beam) report accordingly. In some implementations, the UE may remove the stored L1 (beam) measurement report once the UE’s memory module is overloaded / overflow.

[0156] In some implementations, the UE may be configured to report the cell(s) which has met the leaving condition of the Layer-1 measurement / report (e.g., ?refer to cellsMetReportOnLeaveList).

[0157] In some implementations, the serving RAN may configure the cell list (e.g., the white cell ID list) for the UE, where the UE may be configured or enabled to report the cells which have met the leaving condition of Layer-1 measurement / report. So, the UE may report a leaving event “a target cell which has met the leaving condition of Layer-1 measurement / report to the serving RAN only if the cell ID of the target cell is found in / shown in / aligned with any cell ID in the white cell ID list. The UE may report the target cell ID and DL measurement results (e.g., DL-RSRP / DL-RSRQ / DL-RSSI of the target cell by referring to CSI-RS / SSB) to the serving RAN for the leaving event “a target cell which has met the leaving condition of Layer-1 measurement / report” (e.g., via the CellsMetReportOnLeaveList-L1 IE in RRC signaling).

[0158] In some implementations, the UE may not report the event “a target cell which met the leaving condition of Layer-1 measurement / report” to the serving RAN if the cell ID of the target cell is not found in / shown in / aligned with any cell ID in the white cell ID list.

[0159] In some implementations, another black cell ID list may be configured the UE to prevent a UE from reporting the leaving event of a target cell. In this condition, the UE may report a leaving event “a target cell which has met the leaving condition of Layer-1 measurement / report” to the serving RAN only if the cell ID of the target cell is not found in / shown in / aligned with any cell ID in the white cell ID list, and the UE may report the event “a target cell which has met the leaving condition of Layer-1 measurement / report” to the serving RAN if the cell ID of the target cell is not found in / shown in / aligned with any cell ID in the black cell ID list.

[0160] The UE may be configured to report the cells which have met the leaving condition by reusing the ReportOnLeave IE. In this condition, the ReportOnLeave indicator may be configured in the Layer-1 measurement report configuration to indicate the UE to report the cells which have met a leaving condition of a Layer-1 measurement report configuration.

[0161] In some implementations, the CellsMetReportOnLeaveList may be reused for the UE to report the cells which have met the leaving condition of a Layer-1 (beam) report configuration.

[0162] In some implementations, the UE may also report beam ID (e.g., SSB index) along with the cell identity in the CellsMetreportOnLeaveList to report the beam and the corresponding cell which has met the leaving condition. So, to a UE side, it may mean both the fulfilled leaving condition of a Layer-3 measurement report event and Layre-1 measurement report event may be reported in a CellsMetreportOnLeaveList (depends on whether the beam / cell identity is further reported in the CellsMetreportOnLeaveList).

[0163] In some implementations, a UE may be configured with dedicated Scheduling Request (SR) configuration to report the MAC CE which includes the L1-MR. In some implementations, the dedicated SR configuration may be configured for the L1-MR MAC CE which is triggered / created / composed by the L1 (beam) report. In some implementations, the pending SR associated with L1 measurement report MAC CE may be released upon / after the UE performs the LTM serving cell switch (e.g., based on the UE decision or based on the LTM cell switch command received by the UE).

[0164] The MR MAC CE may include the following information (a)-(c).

[0165] (a) Beam information: FFS if SSBRI / CRI of N beams or (LTM configuration id + SSB / CSI-RS id).

[0166] (b) Beam quantity: L1-RSRP or SINR (up to RAN1) of N beams.

[0167] (c) Triggered event information (e.g., ReportConfigID).

[0168] In some implementations, the Layer-1 measurement result created based on different types of L1-MR report configuration (e.g., ‘L1 periodical’, ‘L1 semi-persist’, ‘L1 aperiodic’ or ‘L1 eventtriggered’ L1-MR report configuration) may be able to be combined / merged / multiplexed jointly in a MAC CE.

[0169] In some implementations, the Layer-1 measurement result created based on different types of L1-MR report configuration (e.g., ‘L1 periodical’, ‘L1 semi-persist’, ‘L1 aperiodic’ or ‘L1 eventtriggered’ L1-MR report configuration) may not be able to be combined / merged / multiplexed jointly in a MAC CE. In other words, the UE may need to provide separate (truncated) MAC CEs to report the ‘(L1) periodical’, ‘(L1) semi-persist’, ‘(L1) aperiodic’, or ‘(L1) eventtriggered’ L1-MR report respectively to the serving RAN.

[0170] In some implementations, the sequence of transmissions of ‘(L1) periodical’ / ‘(L1) semi-persist’, ‘(L1) aperiodic’, or ‘(L1) eventtriggered’ (truncated) MAC CE(s) may also be prioritized. For example, (L1) eventtriggered L1-MR MAC CE may be configured / defined with the highest priority, (L1) aperiodic L1-MR MAC CE may be configured / defined with the second priority, (L1) semi-persist L1-MR MAC CE may be configured / defined with the third priority, and (L1) periodical L1-MR MAC CE may be configured / defined with the lowest priority. The priority of different types of L1-MR MAC CE may be pre-defined by technical specification or pre-configured to UEs via UE-specific RRC signaling or broadcasting system information. The UE may arrange the MAC CE transmissions (to the lower layers) based on the given priority rules (e.g., the high priority MAC CE firstly and then low priority MAC CE).

[0171] In some implementations, the maximum size of the L1-MR MAC CE may be pre-configured (e.g., by UE-specific RRC signaling) or pre-defined (e.g., as specified in the 3GPP specification). In addition, different priority values may be configured to different types of L1-MR report (e.g., ‘L1 periodical’, ‘L1 semi-persist’, ‘L1 aperiodic’ or ‘L1 eventtriggered’ respectively). Therefore, the MAC entity may decide the sequence of transmitting different types of L1-MR results in a MAC CE. In some implementations, the maximum size of the L1-MR MAC CE may be associated with the number of pending L1-MR results, and each of the pending L1-MR results may be associated with a beam direction to be reported to the serving RAN, as shown in FIG. 4A / 4B / 4C. In some implementations, the pending L1-MR results may include the L1-MR results of the current beam / serving beam of the serving cell, and the current beam / serving beam of the serving cell may have higher priority than the beams of neighbor cells. Therefore, the maximum number of pending L1-MR results for all the neighbor cells may be equivalent to the maximum size of L1-MR MAC CE.

[0172] In some implementations, to a MAC SDU, only an L1-MR MAC CE may be allowed to be assembled into a MAC PDU. In other words, the maximum number of L1-MR MAC CEs in a MAC PDU is one, which may be pre-defined by technical specification or pre-installed in the UE module. In some implementations, the maximum number of L1-MR MAC CEs which could be multiplexed into a MAC PDU (e.g., ML1-MR) may be pre-defined / pre-configured (e.g., by the serving RAN via DL control signaling) to a number larger than one (e.g., by setting ML1-MR =3). In some implementations, there may be no restriction on the maximum number of L1-MR MAC CEs to be assembled in s MAC PDU.

[0173] In some implementations, the multiplexing priority of Layer-1 measurement report MAC CE associated with an LTM report event (e.g., that is triggered while the entering condition is fulfilled and the TTT timer expires) may be higher than the multiplexing priority of Layer-1 measurement report MAC CE associated with the same LTM report event (e.g., that is triggered while the leaving condition is fulfilled and the TTT timer expires).

[0174] In some implementations, the multiplexing priority of Layer-1 measurement report MAC CE associated with an LTM report event (e.g., that is triggered while the leaving condition is fulfilled and the TTT expires) may be higher than the multiplexing priority of the Layer-1 measurement report MAC CE associated with an LTM report event (e.g., that is triggered while the entering condition is fulfilled and the TTT expires). In this condition, it may be the entering / leaving condition of the same LTM / L1-MR event or the entering / leaving condition of different LTM / L1-MR events. In addition, the same LTM / L1-MR events may also be associated with different beams / cells.

[0175] In some implementations, the multiplexing priority of Layer-1 measurement report MAC CE associated with an LTM report event (e.g., that is triggered while the entering condition is fulfilled and the associated TTT timer expires) may be higher than the multiplexing priority of the Layer-1 measurement report MAC CE associated with an LTM report event (e.g., that is triggered while the leaving condition is fulfilled and the TTT timer expires). In this condition, it may be the entering / leaving condition of the same LTM event or the entering / leaving condition of different LTM events.

[0176] FIG. 4A is a diagram illustrating an assembling sequence 400A when the UE collects multiple LTM / L1 measurement results from the lower layer, according to an example implementation of the present disclosure. FIG. 4B is a diagram illustrating an assembling sequence 400B when the UE collects multiple LTM / L1 measurement results from the lower layer, according to an example implementation of the present disclosure. FIG. 4C is a diagram illustrating an assembling sequence 400C when the UE collects multiple LTM / L1 measurement results from the lower layer, according to an example implementation of the present disclosure. Each block in FIG. 4A to FIG. 4C may represent an LTM / L1 measurement result based on an LTM / L1 measurement configuration (e.g., LTM1~6) and each LTM / L1 measurement result may be associated with one or more cells or beams (e.g., based on the definition of LTM events). Each block as illustrated in FIG. 4A to FIG. 4C may include at least one of the following information (a)-(d).

[0177] (a) Beam information: SSBRI / CRI of N beams or (LTM configuration id + SSB index / CSI-RS id / TCI state ID) associated with a cell (e.g., PCI, cellidenity, servingcellindex).

[0178] (b) Beam quantity: L1-RSRP or L1-SINR (up to RAN1) of specific beam(s).

[0179] (c) Triggered event information (e.g., ReportConfigID).

[0180] (d) (fulfilled / satisfied) entering condition / (fulfilled / satisfied) leaving condition / not satisfying event.

[0181] In some implementations, the serving RAN may further configure the priorities of the Layer-1 measurement report (e.g., that is triggered while the entering / leaving condition is fulfilled and the associated TTT timer expires) for multiplexing.

[0182] In some implementations, a specific priority value may be configured for each L1-MR configuration respectively. The specific priority value may be an integer value, where a lower value may represent a higher priority. As shown in FIG. 4A, the UE may be configured with a priority sequence.

[0183] The priority sequence may be defined as the first L1-MR configuration L2 (first priority) > the second L1-MR configuration L3 (second priority) > the third L1-MR configuration L5 (third priority). The UE may report the L1 measurement reports according to the priority sequence, such that the L1 measurement results 410, 420, 430 associated with the first L1-MR configuration L2 may be reported before the L1 measurement results 440, 450 associated with the second L1-MR configuration L3, and the L1 measurement results 440, 450 associated with the second L1-MR configuration L3 may be reported before the L1 measurement results 460, 470 associated with the third L1-MR configuration L5.

[0184] The first L1-MR configuration L2 may be an event triggered L1 (beam) measurement report configuration associated with one or more LTM events (e.g., LTM1~6). The first L1-MR configuration L2 may have a first priority with a priority value equal to 0. Three set of beams or cells may be associated with the first L1-MR configuration L2, including {L2#1, L2#2, L2#3}. The three set of beams or cells associated with the first L1-MR configuration L2 may be fulfilled at the UE side. In some implementations, a fulfilled condition may be a fulfilled entering condition or a fulfilled leaving condition. The L1 measurement result 410 may be associated with a fulfilled entering condition (e.g., entering#1) for the first L1-MR configuration L2, the L1 measurement result 420 may be associated with a fulfilled entering condition (e.g., entering#2) for the first L1-MR configuration L2, and the L1 measurement result 430 may be associated with a fulfilled leaving condition (e.g., leaving#3) for the first L1-MR configuration L2.

[0185] The second L1-MR configuration L3 may be an event triggered L1 (beam) measurement report configuration associated with one or more LTM events (e.g., LTM1 to LTM6). The second L1-MR configuration L3 may have a second priority with a priority value equal to 1. Two set of beams or cells may be associated with the second L1-MR configuration L3, including {L3#1, L3#2}. The two set of beams or cells associated with the second L1-MR configuration L3 may be fulfilled at the UE side. In some implementations, a fulfilled condition may be a fulfilled entering condition or a fulfilled leaving condition. The L1 measurement result 440 may be associated with a fulfilled entering condition (e.g., entering#1) for the second L1-MR configuration L3, and the L1 measurement result 450 may be associated with a fulfilled leaving condition (e.g., leaving#2) for the second L1-MR configuration L3.

[0186] The third L1-MR configuration L5 may be an event triggered L1 (beam) measurement report configuration associated with one or more LTM event (e.g., LTM1~6). The third L1-MR configuration L5 may have a third priority with a priority value equal to 2. Two set of beams or cells may be associated with the third L1-MR configuration L5, including {L5#1, L5#2}. The two set of beams or cells associated with the third L1-MR configuration L5 may be fulfilled at the UE side. In some implementations, a fulfilled condition may be a fulfilled entering condition or a fulfilled leaving condition). The L1 measurement result 460 may be associated with a fulfilled entering condition (e.g., entering#1) for the third L1-MR configuration L5, and the L1 measurement result 470 may be associated with a fulfilled leaving condition (e.g., leaving#2) for the third L1-MR configuration L5.

[0187] Based on the given rules, the UE may arrange the contents of MAC CE by including all of L1 measurement results associated with the entering conditions and leaving conditions for the first L1-MR configuration L2. In FIG. 4A, the priority of entering condition may be higher than the leaving condition for the same LTM / L1 measurement report configuration / measurement result / triggering event. So, the UE may arrange the contents of the MAC CE based on the sequence the L1 measurement result 410 associated with the fulfilled entering condition (e.g., entering#1) > the L1 measurement result 420 associated with the fulfilled entering condition (e.g., entering#2) > the L1 measurement result 430 associated with the fulfilled leaving condition (e.g., leaving#3).

[0188] In some implementations, the priority of the leaving condition may be higher than the entering condition for the same LTM / L1 measurement report configuration / measurement result / triggering event. In this condition, the UE may arrange the contents of the MAC CE based on the sequence the L1 measurement result 430 associated with the fulfilled leaving condition (e.g., leaving#3) > the L1 measurement result 410 associated with the fulfilled entering condition (e.g., entering#1) > the L1 measurement result 420 associated with the fulfilled entering condition (e.g., entering#2).

[0189] In some implementations, the UE may also arrange the sequence of multiplexing based on the rule that entering conditions are higher than the leaving conditions. As shown in FIG. 4B, the UE may start from the L1 measurement result 410 associated with the fulfilled entering condition (e.g., entering#1) > the L1 measurement result 440 associated with the fulfilled entering condition (e.g., entering#1) > the L1 measurement result 460 associated with the fulfilled entering condition (e.g., entering#1) > the L1 measurement result 420 associated with the fulfilled entering condition (e.g., entering#2) > the L1 measurement result 450 associated with the fulfilled leaving condition (e.g., leaving#2) > the L1 measurement result 470 associated with the fulfilled leaving condition (e.g., leaving#2) > the L1 measurement result 430 associated with the fulfilled leaving condition (e.g., leaving#3). The priority sequence L2 (highest priority) > L3 > L5 (lowest priority) may be pre-configured to the UE by the serving RAN.

[0190] In some implementations, the priority of leaving condition may be higher than the entering condition for the same LTM / L1 measurement report configuration / measurement result / triggering event. As shown in FIG. 4C, the UE may arrange the contents of MAC CE based on the sequence the L1 measurement result 430 associated with the fulfilled leaving condition (e.g., leaving#3) > the L1 measurement result 450 associated with the fulfilled leaving condition (e.g., leaving#2) > the L1 measurement result 470 associated with the fulfilled leaving condition (e.g., leaving#2) > the L1 measurement result 410 associated with the fulfilled entering condition (e.g., entering#1) > the L1 measurement result 440 associated with the fulfilled entering condition (e.g., entering#1) > the L1 measurement result 460 associated with the fulfilled entering condition (e.g., entering#1) > the L1 measurement result 420 associated with the fulfilled entering condition (e.g., entering#2). The priority sequence L2 (highest priority) > L3 > L5 (lowest priority), as shown in FIG. 4C.

[0191] Each block shown in FIG. 4A to FIG. 4C may represent an LTM / L1-MR and the associated contents for reporting.

[0192] In some implementations, an LTM event not configured with an additional priority value may be automatically regarded as the lowest (or highest) priority LTM event during the LTM / L1-MR MAC CE generation / assembly procedure.

[0193] In some implementations, it may be UE implementations to decide the sequence of multiplexing between the events with the same priority values. The proposed multiplexing priority may be used for MAC CE and truncated MAC CE.

[0194] In some implementations, different cells may be configured with different priorities for related LTM / L1-MR transmission. The serving cell may have higher priority than the non-serving cell (or neighbor cell). The special cell may have the higher priority than secondary cells. The cell with higher measured L1-RSRP or L1-SINR value may have higher priority than the cell with lower measured L1-RSRP or L1-SINR value.

[0195] In some implementations, the serving RAN may specify / configure additional priority values (e.g., lower priority value may represents higher priority) to the cells configured by the serving RAN for LTM / L1-MR. (e.g., one or more cells may be configured to be associated with an LTM / L1-MR configuration and each cell may be configured with specific priority value).

[0196] During the LTM / L1-MR MAC CE generation procedure, the MAC entity may compare the priority value of the cells involved in the pending LTM / L1 measurement results. The MAC entity may firstly select the LTM / L1-MR of a cell with the lowest priority values (e.g., cell#1) to fill in the (truncated) MAC CE. All of the LTM / L1 measurement results related to cell#1 (e.g., different LTM events, current beam / specific beam or fulfilled / satisfied / not-satisfied entering condition or fulfilled / satisfied / not-satisfied leaving condition) may be chosen firstly to assemble the (truncated) MAC CE.

[0197] Secondly, the MAC entity may select the LTM / L1-MR of a cell with the second lowest priority values (e.g., cell#2) to fill in the (truncated) MAC CE. All of the LTM / L1 measurement results related to cell#2 (e.g., different LTM events, current beam / specific beam or fulfilled / satisfied / not-satisfied entering condition or fulfilled / satisfied / not-satisfied leaving condition) may be chosen secondly to assemble the (truncated) MAC CE, and so on.

[0198] In some implementations, the cell not configured with an additional priority value may be automatically regarded as lowest (or highest) priority cell during the LTM / L1-MR MAC CE generation / assembly procedure. In some implementations, it may be UE implementation to decide the sequence of LTM / L1-MR assembly while the same priority (value) is configured to different cells.

[0199] In some implementations, different beams (e.g., among the same cell or different cells) may be configured with different priority values for the related LTM / L1-MR transmission. For example, the current / serving beam of the serving cell may have higher priority than the beams of other cells (or neighbor cells).

[0200] In some implementations, the serving RAN may specify / configure additional priority values (e.g., lower priority value may represent higher priority) to a, or a subset of, or all of the beams of a serving cell, special cell, or neighbor cell. For example, one or more beams may be pre-configured to be associated with an LTM / L1-MR configuration, and each beam may be configured with specific priority value.

[0201] In some implementations, a beam not configured with an additional priority value may be automatically regarded as lowest (or highest) priority beam during the LTM / L1-MR MAC CE generation / assembly procedure.

[0202] During the LTM / L1-MR MAC CE generation procedure, the MAC entity may compare the priority value of the beams involved in the pending LTM / L1 measurement results. The MAC entity may firstly select the LTM / L1-MR of a beam with the lowest priority values (e.g., Beam#1 of cell#1) to fill in the (truncated) MAC CE. All of the LTM / L1 measurement results related to Beam#1 of cell#1 (e.g., different LTM events, fulfilled / satisfied / not-satisfied entering condition or fulfilled / satisfied / not-satisfied leaving condition) may be chosen firstly to assemble the (truncated) MAC CE.

[0203] Secondly, the MAC entity may select the LTM / L1-MR of a beam of a cell with the second lowest priority values (e.g., Beam#2 of cell#2) to fill in the (truncated) MAC CE. All of the LTM / L1 measurement results related to Beam#2 of cell#2 (e.g., different LTM events, current beam / specific beam or fulfilled / satisfied / not-satisfied entering condition or fulfilled / satisfied / not-satisfied leaving condition) may be chosen secondly to assemble the (truncated) MAC CE, and so on.

[0204] In some implementations, it may be UE implementation to decide the sequence of LTM / L1-MR assembly while the same priority (value) is configured to different beams.

[0205] In some implementations, a UE may cancel a L1-MR MAC CE transmission (e.g., a L1-MR MAC CE#1 transmission triggered while the entering condition of an LTM measurement event is fulfilled) if the leaving condition of the same LTM event is fulfilled and the L1-MR MAC CE#1 is still pending.

[0206] In some implementations, a UE may cancel / drop an L1-MR MAC CE transmission upon / after the UE trigger conditional LTM cell switch execution / LTM cell switch execution. In some implementations, the UE may still keep / store the (truncated) MAC CE.

[0207] In some implementations, a UE (e.g., the MAC entity of the UE) may trigger a DeadlineToTransmit (DTT) timer associated with the L1-MR MAC CE (or truncated L1-MR MAC CE) while / upon / after the (truncated) MAC CE is created by the MAC entity. The UE may count the DTT timer to zero before the (truncated) MAC CE is transmitted to the lower layer for transmission via the air link. The UE may remove the (truncated) MAC CE if its DTT timer expires and the (truncated) MAC CE is still pending in the UE side.

[0208] In some implementation, the pending SR triggered by the L1-MR MAC CE may also be cancelled if the L1-MR MAC CE is removed / cancelled.

[0209] In some implementations, the Layer-1 report configuration may be configured to be reported periodically. So, an L1-MR report timer may be configured in the MAC entity. The MAC entity may periodically trigger the L1-MR report timer counting activity to zero. The initial value of L1-MR report timer may be pre-configured by the serving RAN (e.g., as part of Layer-1 report configuration). The UE may create one or more L1-MR MAC CEs every time upon the running L1-MR report timer expires and any L1-MR with fulfilled entering / leaving condition is still pending in the UE side.

[0210] In some implementations, the information associated with an L1 measurement / reporting configuration (e.g., Layer 1 beam / cell measurement result) may be released while / upon / after MAC reset. All of the running TTT timers of Layer-1 measurement configuration may be stopped and released while / upon / after MAC reset.

[0211] In some implementations, the pending report (e.g., fulfilled entering condition and / or leaving condition) may be released with MAC reset. In some implementations, the pending L1-MR may be forwarded / transmitted to the RRC entity of the UE. The RRC entity of the UE may transmit L1-MR contents to the serving RAN via RRC signaling (e.g., UEAssistanceInformation).

[0212] In some implementations, an L1-MR report configuration may further indicate whether the L1-MR report (e.g., transmitted by MAC CE / RRC signaling) is enabled (e.g., with information element ‘enabled’) or be disabled (e.g., with information element ‘disabled’) to be transmitted via existing uplink configured grant. In some implementations, an L1-MR report configuration may be further associated with a UL-CG configuration (e.g., with an indicated UL-CG configuration ID).

[0213] In some implementations, the issue “whether a (event-triggered) L1-MR report can be transmitted via UL-CG” may be configured / determined by the serving RAN with the specific information element, which may be applicable to each LTM / L1-MR measurement report configuration respectively and an / each LTM / L1-MR configuration may be further associated with one or more UL-CG configurations (e.g., based on the given UL-CG configuration ID ).

[0214] In some implementations, all (event-triggered) L1-MR reports may be enabled to be transmitted via UL-CG directly / automatically / implicitly without explicit signaling / indication.

[0215] Mechanisms for L1-MR associated with the beams not satisfying the event

[0216] For event-triggered L1 LTM measurement reporting, the NW may control whether the beam(s) not satisfying the event could be reported according to N beams in MR MAC CE. In some implementations, the UE may report the ‘not satisfying condition’ of an LTM event (e.g., LTM event / configuration ID) associated with a beam (e.g., SSBRI / CRI / SSB index) of a cell (e.g., PCI) via uplink RRC signaling (e.g., UEAssistanceInformation).

[0217] In some implementations, a UE may be configured to report the beam(s) not satisfying the event. In some implementations, a UE may be configured not to report the beam(s) not satisfying the event. In some implementations, “To report the beam(s) not satisfying the event” may be an optional (event-based) information element associated with an L1 measurement event (e.g., LTM2 / 3 / 4 / 5). In some implementations, “To report the beam(s) not satisfying the event” may be an optional (LTM candidate-based or cell-based) IE associated with an LTM candidate ID or Cell identity (e.g., Physical cell Identity).

[0218] The events may mean the entering condition of the given LTM events / L1 measurement events. In some implementations, ‘not satisfying the (LTM / L1) event’ may mean that the leaving condition of an event is fulfilled during the corresponding TimeToTrigger defined for this event (but the associated beam may become “not satisfy” (LTM / L1) event before the TTT timer expires) or without the TimeToTrigger. To an event-triggered measurement, the TimeToTrigger may be defined as the given time period during which a specific criterion (e.g., entering / leaving condition) for the event needs to be met in order to trigger a measurement report. The event-triggered measurement may be an LTM measurement or an L1 measurement.

[0219] In some implementations, “not satisfying the (LTM / L1) event” may mean that the entering condition is not fulfilled during the corresponding the TimeToTrigger period defined for this event after the entering condition is triggered / initiated. The leaving condition associated with the same event may be configured. In some implementations, the leaving condition associated with the same event may not be configured.

[0220] In some implementations, “not satisfying the (LTM / L1) event” may mean that the leaving condition is fulfilled while the UE is still staying in the TimeToTrigger period defined for this event. In other words, the leaving condition may or may not be fulfilled during the TimeToTrigger period defined for the leaving condition. The leaving condition associated with the same event may or may not be configured.

[0221] In some implementations, the UE may be triggered to report the situation “the beam(s) not satisfying the event” via specific signaling, which may be associated with a specific LTM / L1 measurement report, a specific LTM candidate cell, the serving cell, a current serving beam, or a specific candidate beam and LTM candidate.

[0222] In some implementations, an explicit indicator “not satisfying event / condition” may be provided / transmitted by the UE to be associated with the beam(s) not satisfying the event (e.g., along with SSBRI / CRI / SSB index / TCI state ID and LTM / Layer-1 event ID) within the L1 (beam) measurement report.

[0223] In some implementations, to a specific event with a specific beam, the UE may face the situation that the leaving condition of a (Layer1 / LTM) event is fulfilled (or is going to be fulfilled while the TimeToTrigger period of the leaving condition is going to be expired) but the L1-MR MAC CE to report the entering condition is still pending on the UE side (e.g., pending in the same MAC entity). In this condition, the UE may stop the transmission of MAC CE which includes the information of fulfilled entering condition and erase / remove the MAC CE or information related to the fulfilled entering condition.

[0224] In some implementations, the UE may suspend / pause / release the L1-MR transmission of a fulfilled entering condition of an event if the leaving condition of the same event associated with the same beam / cell is triggered and the running timer for the TimeToTrigger period calculation of the leaving condition is not fulfilled. In other words, the transmission of L1-MR of a fulfilled entering condition may be paused / stopped / interrupted once the leaving condition of the same event (to the same beam or different beam with the entering condition) is initiated / fulfilled.

[0225] In some implementations, the UE (or MAC entity) may restart / re-prepare the L1-MR transmission of the fulfilled entering condition of an L1-MR / LTM event if the leaving condition is not fulfilled (e.g., after the TimeToTrigger timer associated with the leaving condition expires).

[0226] If there is more than one pending LTM-MR / L1-MR associated with a given LTM event (e.g., LTM2 / LTM3 / LTM5), the UE may decide the sequence for LTM-MR / L1-MR associated with the same event type based on the reported / measured signaling quality (e.g., beam quality).

[0227] In some implementations, the priority rules may be provided for the UE to select the sequence of LTM / Layer1 report event (e.g., LTM2 / LTM3 / LTM5) and the associated information to be included in a MAC CE while there are multiple fulfilled entering conditions for each of (or some of) the LTM-MR / L1-MR events. The proposed rules may also be expressed based on the given FIG. 4A to FIG. 4C.

[0228] Rule#1: A specific priority rules such as LTM2 event (first priority)>LTM3 event (second priority)>LTM5 event (third priority) may be pre-defined (e.g., in technical specification) or pre-configured to the UE (e.g., via UE-specific RRC control signaling or broadcasting system information). The UE may firstly report (all of) the fulfilled entering conditions of LTM2 if there is enough space within the MAC CE. Secondly, the UE may report (all of) the fulfilled entering conditions of LTM3 if there is enough space within the same MAC CE Then, the UE may report (all of) the fulfilled entering conditions of LTM5 if there is enough space within the same MAC CE. The Rule#1 may apply accordingly unless the space of the MAC CE is fully occupied based on the given maximum number of NL1beams in a MAC CE.

[0229] In some implementations, the UE may apply the sequence in Rule#1 for all of the “fulfilled entering condition” report firstly for (truncated) MAC CE generation. Then, if there is remaining space in the MAC CE for the LTM-MR / L1-MR, the UE may apply the sequence again for all of the “fulfilled leaving condition” report until the space of the LTM-MR / L1-MR MAC CE is fully occupied. In some implementations, the UE may apply the sequence in Rule#1 for all of the “fulfilled leaving condition” report firstly for (truncated) MAC CE generation. Then, if there is remaining space in the MAC CE for LTM-MR / L1-MR, the UE may apply the sequence of Rule#1 for all of the “fulfilled entering condition” report until the space of the LTM-MR / L1-MR MAC CE is fully occupied.

[0230] In some implementations, the UE may select both the “fulfilled entering condition” report and “fulfilled leaving condition” report jointly of the same LTM report type (which may be associated with different beams) during the decision. In addition, in some cases, the “fulfilled entering condition” of an LTM report event (e.g., LTM2 / LTM3 / LTM5 associated with a beam) may have the higher priority than “fulfilled leaving condition” of the same LTM report event (e.g., LTM2 / LTM3 / LTM5 associated with the same beam or another different beam) for the UE to select. In some implementations, the “fulfilled leaving condition” of an LTM report event (e.g., LTM2 is presented as L2 in FIG. 4A to FIG. 4C / LTM3 is presented as L3 in FIG. 4A to FIG. 4C / LTM5 is presented as L5 in FIG. 4A to FIG. 4C associated with one beam may have the higher priority than “fulfilled entering condition” of the same LTM report event (e.g., LTM2 / LTM3 / LTM5 associated with the same beam or another different beam) for the UE to select.

[0231] Rule#2: The UE may select a fulfilled entering condition of an LTM-MR / L1-MR event based on the given priority rules (LTM2 (first priority)>LTM3 (second priority)>LTM5 (third priority)) in each round.

[0232] Round#1: Firstly, the UE may check whether there is any fulfilled entering condition associated with LTM2, and the UE may select to report as many KP_LTM2(entering condition fulfilled) beam associated LTM2 firstly if there is any. The UE may not choose an additional (entering condition fulfilled) beam associated with LTM2 in this round#1 if the number of pending LTM2 report is larger than (or equivalent to) KP_LTM2.

[0233] Then, also in round#1, the UE may select to report as many as KP_LTM3(entering condition fulfilled) beam associated with LTM3 secondly if there is any pending LTM3 event. The UE may not choose an additional (entering condition fulfilled) beam associated with LTM3 in this round#1 if the number of pending LTM3 report is larger than (or equivalent to) KP_LTM3.

[0234] Third, in round#1, the UE may select to report KP_LTM5(entering condition fulfilled) beam associated with LTM5 report if there is any. The UE may not choose an additional (entering condition fulfilled) beam associated with LTM5 in this round#1 if the number of pending LTM5 report is larger than (or equivalent to) KP_LTM5.

[0235] The round#1 may be terminated based on the given sequence until the space of a MAC CE is fully occupied.

[0236] In some implementations, the value of {KP_LTM2, KP_LTM3, KP_LTM5} may be pre-defined as KP_LTM2= KP_LTM3= KP_LTM5=1 as a default setting. In some implementations, the values of {KP_LTM2, KP_LTM3, KP_LTM5} may be pre-configured to the UE via UE-specific control signaling or broadcasting system information. In addition, the different values may be configured to KP_LTM2, KP_LTM3, and KP_LTM5respectively.

[0237] Round#2: The UE may initiate round#2 if there is still space in a MAC CE. The UE may select up to KP_LTM2(fulfilled entering condition) LTM event firstly to generate the L1-MR / LTM-MR MAC CE. Then, the UE may select up to KP_LTM3(fulfilled entering condition) LTM3 event secondly to generate the L1-MR / LTM-MR MAC CE. Third, the UE may select up to KP_LTM5(fulfilled entering condition) LTM5 event firstly to generate the MAC CE. The UE may create additional rounds based on the same priority rules if there is space to cover more LTM / L1 measurement reports into the LTM-MR / L1-MR MAC CE.

[0238] In some implementations, the UE may apply round#1 to round#3 in Rule#2 for “fulfilled entering condition” report firstly for (truncated) MAC CE generation. Then, if there is remaining space in the MAC CE for the LTM-MR / L1-MR, the UE may apply the round#1 to 3 for “fulfilled leaving condition” report until the space of the LTM-MR / L1-MR MAC CE is fully occupied. In some implementations, the UE may apply round#1 to round#3 in Rule#2 for “fulfilled leaving condition” report firstly for (truncated) MAC CE generation. Then, if there is remaining space in the MAC CE for LTM-MR / L1-MR, the UE may apply the round#1 to 3 for “fulfilled entering condition” report until the space of the LTM-MR / L1-MR MAC CE is fully occupied.

[0239] In some implementations (for Rule#2), the UE may select both the “fulfilled entering condition” report and “fulfilled leaving condition” report jointly of the same LTM report type (which may be associated with different beams) during the decision. In addition, in some cases, the “fulfilled entering condition” of an LTM report event (e.g., LTM2 / LTM3 / LTM5 associated with a beam) may have the higher priority than “fulfilled leaving condition” of the same LTM report event (e.g., LTM2 / LTM3 / LTM5 associated with the same beam or another different beam) for the UE to select. In some implementations, the “fulfilled leaving condition” of an LTM report event (e.g., LTM2 / LTM3 / LTM5 associated with one beam) may have the higher priority than “fulfilled entering condition” of the same LTM report event (e.g., LTM2 / LTM3 / LTM5 associated with the same beam or another different beam) for the UE to select.

[0240] In some implementations, the UE may select both the “fulfilled entering condition” report and “fulfilled leaving condition” report jointly of the same LTM report type (which may be associated with different beams) during the decision.

[0241] In some implementations, the proposed rules (e.g., Rule#1 and Rule#2) may also be applied to the (fulfilled leaving condition) report. In some implementations, the same parameters (e.g., the same rules and / or the same parameters {KP_LTM2, KP_LTM3, KP_LTM5}) may be applied to the “fulfilled entering condition” report and “fulfilled leaving condition” report jointly. In some implementations, different rules and / or different parameters (e.g., {KP_LTM2, KP_LTM3, KP_LTM5}) may be applied to the “fulfilled entering condition” report and “fulfilled leaving condition” report respectively.

[0242] In some implementations, the UE may generate multiple (truncated) MAC CEs. In addition, the UE may decide the sequences of (truncated) MAC CEs for transmissions (e.g., transmission to the lower layers) based on the contents of the MAC CEs and proposed rules.

[0243] Beam-specific priority rules: The priority rules may be applied to a specific beam (e.g., a current beam, serving beam, or a candidate beam). So, different priority values may be configured (e.g., by the serving RAN, via broadcasting system information, UE-specific RRC signaling, or DL MAC CE) to different beams in a cell.

[0244] Cell-specific priority rules: The priority rules may be applied to a specific cell (e.g., the serving cell or an LTM candidate cell).

[0245] The UE may select / decide which rule is applied (e.g., Rule#1 / Rule#2 / beam-specific / cell-specific) based on the instructions installed in the UE side or based on the instructions from the serving RAN / CN / NW.

[0246] The proposed rules may be applied to the creation of the LTM-MR / L1-MR MAC CE and / or LTM-MR / L1-MR (truncated) MAC CE.

[0247] In some implementations, the UE may decide the sequence of pending (entering condition fulfilled) LTM-MR / L1-MR reports and then create / divide one or more (truncated) MAC CEs to cover those pending LTM-MR / L1-MR reports. Then, the UE may transmit the one or more (truncated) MAC CEs in order.

[0248] In some implementations, whether to generate more than one MAC CE to transmit MR may be indicated before the first transmitted MAC CE.

[0249] In some implementations, the MAC CE / truncated MAC CE generated for Layer1 / LTM measurement may be transmitted via only special cell associated with MCG (PCell) / SCG (PSCell). In some implementations, during the L1-MR MAC CE generation, the UE may firstly report the beams which satisfy the L1 / LTM event (high priority). Then, the UE may report the beams which do not satisfy the L1 / LTM event (low priority). The proposed mechanisms may be applicable to (normal) MAC CE and truncated MAC CE applied for the L1-MR (or LTM-MR) transmission.

[0250] In some implementations, the number of N beams to be reported by a UE in a MAC CE may be defined as NL1. In some implementations, the number of N beams to be reported by a UE in a (MAC) transmission triggered by MAC entity may be defined as NL1. The transmission triggered by MAC entity may be transmitted by one or more MAC CEs and / or truncated MAC CEs. In some implementations, the number of N beams to be reported in a truncated MAC CE may be defined as NL1, truncated. In some implementations, the number of NL1and NL1, truncatedmay be pre-defined via technical specification. The number of NL1and NL1, truncatedmay be pre-configured by the serving RAN via broadcasting system information, SI on-demand procedure, or UE-specific control signaling. In some implementations, NL1may define the maximum number of beams which can be reported by the UE in an L1-MR MAC CE. In some implementations, NL1, truncatedmay define the maximum number of beams which can be reported by the UE in a truncated L1-MR MAC CE.

[0251] FIG. 5A is a diagram illustrating a timeline 500A for L1-MRs and LTM / L1-MR MAC CE transmission, according to an example implementation of the present disclosure. In some implementations, the MAC CE generation of L1-MR MAC CE transmissions may be finished during a configured L1-MR / LTM-MR multiplexing window. As shown in FIG. 5A, an LTM / L1-MR report (e.g., L1-MR#1) is initiated (e.g., aperiodic or event-triggered) in the MAC entity and no pending LTM / L1-MR report before the initiation / generation of L1-MR#1. Then, the MAC entity may kick-off an LTM / L1-MR multiplexing window (e.g., L1-MR multiplexing window#1) after the L1-MR#1 is created. The UE may try to monitor whether there is any remaining LTM / L1-MR report being created during the LTM / L1-MR multiplexing window. As shown in FIG. 5A, the UE may also generate LTM / L1-MR multiplexing windows (e.g., the L1-MR multiplexing window#2 and L1-MR multiplexing window#3) for LTM / L1-MR reports (e.g., L1-MR#2 and L1-MR#3) respectively upon / after L1-MR#2 and L1-MR#3 are generated / obtained.

[0252] After the L1-MR multiplexing window#1 expires in time domain, the UE may assemble all of the created and pending LTM / L1-MR reports (e.g., L1-MR#1, L1-MR#2, and L1-MR#3) in a MAC CE and transmit the MAC CE to the lower layers for transmission to the serving RAN. In addition, the remaining L1-MR multiplexing window#2 and L1-MR multiplexing window#3 may be stopped even though both of the time windows are not expired yet. If the MAC CE created by the UE only be able to include L1-MR#1 and L1-MR#2, then the L1-MR multiplexing window#3 of L1-MR#3 may be still counted by the UE because the L1-MR#3 is remaining in the UE side. Finally, the UE may create an additional MAC CE to transmit the L1-MR#3 upon / after the L1-MR multiplexing window#3 expires. In some implementations, a common L1-MR multiplexing window value may be configured to all of the LTM / L1-MR configurations transmitted to the UE.

[0253] The time span of the LTM / L1-MR multiplexing window may be pre-configured by the serving RAN or pre-defined in technical specification. In some implementations, different time spans of the LTM / L1-MR multiplexing window may be configured to the UE based on the type of L1-MR#1 (e.g., the type of LTM / L1-MR which initiates the LTM / L1-MR multiplexing window) or based on the cell / beam which triggers the L1-MR#1. FIG. 5B is a diagram illustrating a timeline 500B for L1-MRs and LTM / L1-MR MAC CE transmission, according to an example implementation of the present disclosure. As shown in FIG. 5B, the L1-MR multiplexing window#2 triggered by L1-MR#2 may be shorter than L1-MR multiplexing window#1 and L1-MR multiplexing window#3, and the L1-MR multiplexing window#2 may expire earlier than the L1-MR multiplexing window#1 / 3. Therefore, the MAC entity may be triggered to create a MAC CE to transmit {L1-MR#1, L1-MR#2, L1-MR#3} jointly upon / after the L1-MR multiplexing window#2 expires. In addition, the counting L1-MR multiplexing window#1 / 3 may be stopped upon / after the pending L1-MR#1 / L1-MR#3 is transmitted with the MAC CE (e.g., triggered by the L1-MR multiplexing window#2 expiry) jointly.

[0254] In some implementations, the MAC entity may terminate the LTM / L1-MR multiplexing window earlier than the time span of the window if the MAC entity already collects out to N LTM / L1-MR reports to be transmitted. The number of N may also be pre-defined / pre-configured. In this condition, the L1-MR multiplexing window of the pending / remaining L1-MR reports may be still counted by the UE.

[0255] In some implementations, the MAC entity may terminate the LTM / L1-MR multiplexing window earlier than the time span of the window if the UE receives one or more valid UL grants from the serving RAN to transmit pending LTM / L1-MR reports. In contrast, the counting activity of the LTM / L1-MR multiplexing window may be continued if / after the UE receives UL grant which is invalid / not-allowed for the LTM / L1-MR transmission.

[0256] In some implementations, the scheduling request specific for LTM / L1-MR MAC CE transmission may be transmitted upon / after the MAC entity creates / receives the L1-MR#1. In some implementations, the SR specific for LTM / L1-MR MAC CE transmission may be transmitted upon / after the LTM / L1-MR multiplexing window expires. In some implementations, the SR specific for LTM / L1-MR MAC CE transmission may be transmitted upon / after the MAC entity create one or more (truncated) MAC CEs for LTM / L1-MR transmission.

[0257] In some implementations, the MAC entity disclosed in the present disclosure may be the MAC entity associated with master cell group (MCG). In some implementations, the MAC entity disclosed in the present disclosure may be the MAC entity associated with secondary cell group (SCG).

[0258] In some implementations, the UE / MAC entity may be configured / enabled to transmit (truncated) LTM / L1-MR MAC CEs during RA procedures (e.g., 2-step / 4-step procedure). In some implementations, the UE / MAC entity may not be configured / enabled to transmit (truncated) LTM / L1-MR MAC CEs during RA procedures (e.g., 2-step / 4-step procedure). In some implementations, the UE / MAC entity may be configured with the types (e.g., (L1) aperiodic) of LTM / L1-MR (or which cell / beam when the LTM / L1-MR is associated with) that the UE is enabled (or is disabled) to initiate a (2-step / 4-step) RA procedure for the (truncated) LTM / L1-MR MAC CE transmission.

[0259] FIG. 6 is a diagram illustrating an LTM cell switch procedure 600, according to an example implementation of the present disclosure. The LTM cell switch procedure 600 may include the following actions 602 to 616.

[0260] In the action 602, the UE 620 may send a Measurement Report message to the gNB 640. The gNB 640 may decide to configure the LTM and initiates the LTM preparation.

[0261] In the action 604, the gNB 640 may transmit an RRC Reconfiguration message to the UE 620. The RRC Reconfiguration message may include the LTM candidate configurations.

[0262] In the action 606, the UE 620 may store the LTM candidate configurations and transmit an RRC Reconfiguration Complete message to the gNB 640.

[0263] In the action 608a, the UE 620 may perform DL synchronization with the LTM candidate cell(s) before receiving the cell switch command. The UE 620 may activate and deactivate TCI states of LTM candidate cell(s), as triggered by the gNB 640.

[0264] In the action 608b, the UE 620 may perform UL synchronization with LTM candidate cell(s) before receiving the cell switch command, by using UE-based TA measurement, if configured, and / or by transmitting a preamble towards the candidate cell, as triggered by the gNB 640. When the UE-based TA measurement is configured, the UE 620 may acquire the TA value(s) of the candidate cell(s) by measurement. The UE 620 may perform early TA acquisition with the candidate cell(s) as requested by the network before receiving the cell switch command as specified in the 3GPP TS 38.300. This may be done via CFRA triggered by a PDCCH order from the source cell, following which the UE 620 may send preamble towards the indicated candidate cell. In order to minimize the data interruption of the source cell due to CFRA towards the candidate cell(s), the UE 620 may not receive random access response from the network (e.g., gNB 640) for the purpose of TA value acquisition and the TA value of the candidate cell may be indicated in the cell switch command. The UE 620 may not maintain the TA timer for the candidate cell and rely on network implementation to guarantee the TA validity.

[0265] In the action 610, the UE 620 may perform L1 measurements on the configured LTM candidate cell(s) and transmit L1 measurement reports to the gNB 640. The L1 measurement may be performed as long as RRC reconfiguration (action 604) is applicable.

[0266] In the action 612, the gNB 640 may decide to execute cell switch to a target cell and transmit an LTM cell switch command MAC CE triggering cell switch by including a target configuration ID which indicates the index of the candidate configuration of the target cell, a beam indicated with a TCI state or beams indicated with DL and UL TCI states, and a timing advance command for the target cell, if available. The UE 620 may switch to the target cell and apply the candidate configuration indicated by the target configuration ID.

[0267] In the action 614, the UE 620 may perform the random access procedure towards the target cell, if UE 620 does not have valid TA of the target cell as specified in the 3GPP TS 38.321.

[0268] In the action 616, the UE 620 may complete the LTM cell switch procedure by sending RRC Reconfiguration Complete message to target cell. If the UE 620 has performed a RA procedure in the action 614, the UE 620 may consider that LTM cell switch execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE 620 may consider that LTM cell switch execution is successfully completed when the UE 620 determines that the network has successfully received its first UL data.

[0269] The actions 608-616 may be performed multiple times for subsequent LTM cell switch executions using the LTM candidate configuration(s) provided in the action 604. The procedure over the air interface as illustrated in FIG. 7 may be applicable to both intra-gNB-DU LTM and inter-gNB-DU LTM. The overall LTM procedures over F1-C interface may be captured in the 3GPP TS 38.401.

[0270] FIG. 7 is a flowchart illustrating a method / process 700 performed by a UE for layer 1 (L1) measurement reporting, according to an example implementation of the present disclosure.

[0271] In the action 702, the process 700 may start by receiving, from a base station (BS), an L1 measurement configuration that configures at least one layer 1 (L1) / layer 2 (L2) triggered mobility (LTM) event.

[0272] In the action 704, the process 700 may measure multiple candidate beams to obtain multiple L1 measurement results.

[0273] In the action 706, the process 700 may determine, based on the at least one LTM event, a priority of each of the multiple candidate beams.

[0274] In the action 708, the process 300 may generate an L1 measurement report (L1-MR) medium access control (MAC) control element (CE) by assembling the multiple L1 measurement results associated with the multiple candidate beams in the L1-MR MAC CE based on the priority of each of the multiple candidate beams.

[0275] In the action 710, the process 700 may transmit, to the BS, the L1-MR MAC CE. Each of the multiple candidate beams may be associated with a reference signal index of an LTM candidate cell, and the L1-MR MAC CE may be generated by a MAC entity of the UE. The process 700 may then end.

[0276] In some implementations, determining, based on the at least one LTM event, the priority of each of the multiple candidate beams may include: determining that a first candidate beam of the multiple candidate beams has a first priority after determining that a first L1 measurement result of the first candidate beam remains satisfying an entering condition of the at least one LTM event upon expiry of a first time-to-trigger (TTT) timer associated with the entering condition; determining that a second candidate beam of the multiple candidate beams has a second priority after determining that a second L1 measurement result of the second candidate beam remains satisfying a leaving condition of the at least one LTM event upon expiry of a second TTT timer associated with the leaving condition; determining that a third candidate beam of the multiple candidate beams has a third priority after determining that a third L1 measurement result of the third candidate beam has been reported and the third L1 measurement result does not remain satisfying the leaving condition of the at least one LTM event upon expiry of the second TTT timer; and determining that a fourth candidate beam of the multiple candidate beams has a fourth priority after determining that a fourth L1 measurement result of the fourth candidate beam does not remain satisfying the entering condition of the at least one LTM event upon expiry of the first TTT timer and does not remain satisfying the leaving condition of the at least one LTM event upon expiry of the second TTT timer, where the first priority, the second priority, the third priority, and the fourth priority may be in a decreasing order of priority.

[0277] In some implementations, generating the L1-MR MAC CE by assembling the multiple L1 measurement results associated with the multiple candidate beams in the L1-MR MAC CE based on the priority of each of the multiple candidate beams may include: assembling the first L1 measurement result in the L1-MR MAC CE before assembling the second L1 measurement result, the third L1 measurement result, and the fourth L1 measurement result in the L1-MR MAC CE; assembling the second L1 measurement result in the L1-MR MAC CE before assembling the third L1 measurement result and the fourth L1 measurement result in the L1-MR MAC CE; assembling the third L1 measurement result in the L1-MR MAC CE before assembling the fourth L1 measurement result in the L1-MR MAC CE; and assembling the fourth L1 measurement result in the L1-MR MAC CE after assembling the first L1 measurement result, second L1 measurement result, and third L1 measurement result in the L1-MR MAC CE after determining that a specific information element (IE) indicating that an L1 measurement result of a candidate beam having the fourth priority is allowed to be reported.

[0278] In some implementations, generating the L1-MR MAC CE by assembling the multiple L1 measurement results associated with the multiple candidate beams in the L1-MR MAC CE based on the priority of each of the multiple candidate beams may include refraining from assembling the first L1 measurement result in the L1-MR MAC CE after determining that the first candidate beam has the first priority and the first L1 measurement result remains satisfying the leaving condition of the at least one LTM event upon expiry of the second TTT timer, where the L1-MR MAC CE may include a truncated L1-MR MAC CE.

[0279] In some implementations, the L1 measurement configuration may include an information element (IE) that indicates that the UE is allowed to generate the L1-MR MAC CE after determining that an L1 measurement result of one of the multiple candidate beams remains satisfying a leaving condition of the at least one LTM event upon expiry of a time-to-trigger (TTT) timer associated with the leaving condition, where the IE may be configured by a radio resource control (RRC) configuration.

[0280] In some implementations, the process 700 may receive, from the BS, an information element (IE) that indicates whether an L1 measurement result of a current beam of a serving cell is to be reported via the L1-MR MAC CE; and assemble the L1 measurement result of the current beam of the serving cell in the L1-MR MAC CE after determining that the IE indicates that the L1 measurement result of the current beam of the serving cell is to be reported via the L1-MR MAC CE, where the IE may be configured by a radio resource control (RRC) configuration.

[0281] In some implementations, the L1 measurement configuration may include a scheduling request (SR) configuration specific for the transmission of the L1-MR MAC CE, and the process 700 may transmit, to the BS, a scheduling request based on the SR configuration, and after determining that the MAC entity is reset: release the plurality of L1 measurement results, the scheduling request, and the L1-MR MAC CE, and stop all running TTT timers associated with the at least one LTM event.

[0282] In some implementations of the first aspect, the L1 measurement configuration may further configure a periodical reporting timer and a value of the periodical reporting timer, the periodical reporting timer may be used for the UE to report the L1-MR MAC CE periodically, and the process 700 may start or restart the periodical reporting timer; and generate and transmit the L1-MR MAC CE after determining that the periodical reporting timer expires and one or more of the multiple L1 measurement results that satisfy an entering condition or a leaving condition of the at least one LTM event are pending.

[0283] In some implementations of the first aspect, the L1 measurement configuration may further configure a maximum number of beams to be reported in the L1-MR MAC CE, and the maximum number may be applied to one or more beams of neighbor cells and a current beam of a serving cell when the UE is indicated by the BS to report an L1 measurement result of the current beam of the serving cell.

[0284] The steps / actions shown in FIG. 7 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. 7 may be omitted in some implementations and one or more actions shown in FIG. 7 may be combined.

[0285] The technical problem addressed by the method illustrated in FIG. 7 is how to implement an efficient Layer 1 measurement reporting mechanism at the MAC layer that can handle multiple candidate beams associated with LTM events, organize their measurement results according to event-based priorities, and generate compact MAC CEs for transmission to the network. The advantageous technical effect achieved by the method illustrated in FIG. 7 is that by generating the L1-MR MAC CE at the MAC entity with priority-based assembly of measurement results, the UE can provide a streamlined reporting mechanism that reduces MAC layer processing overhead, minimizes air interface signaling, and enables the network to efficiently process beam measurements for LTM procedures, thereby supporting faster mobility decisions and improved radio resource management.

[0286] FIG. 8 is a block diagram illustrating a node 800 for wireless communication in accordance with various aspects of the present disclosure. As illustrated in FIG. 8, a node 800 may include a transceiver 820, a processor 828, a memory 834, one or more presentation components 838, and at least one antenna 836. The node 800 may also include a radio frequency (RF) spectrum band module, a BS communications module, a network communications module, and a system communications management module, Input / Output (I / O) ports, I / O components, and a power supply (not illustrated in FIG. 8).

[0287] Each of the components may directly or indirectly communicate with each other over one or more buses 840. The node 800 may be a UE or a BS that performs various functions disclosed with reference to FIGS. 1 through 7.

[0288] The transceiver 820 has a transmitter 822 (e.g., transmitting / transmission circuitry) and a receiver 824 (e.g., receiving / reception circuitry) and may be configured to transmit and / or receive time and / or frequency resource partitioning information. The transceiver 820 may be configured to transmit in different types of subframes and slots including, but not limited to, usable, non-usable, and flexibly usable subframes and slot formats. The transceiver 820 may be configured to receive data and control channels.

[0289] The node 800 may include a variety of computer-readable media. Computer-readable media may be any available media that may be accessed by the node 800 and include volatile (and / or non-volatile) media and removable (and / or non-removable) media.

[0290] The computer-readable media may include computer-storage media and communication media. Computer-storage media may include both volatile (and / or non-volatile media), and removable (and / or non-removable) media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, Artificial Intelligence (AI) / Machine Learning (ML) module(s), or data.

[0291] Computer-storage media may include RAM, DRAM, HBM, MRAM, FRAM, PRAM, ROM, EPROM, EEPROM, flash memory (or other memory technology), CD-ROM, Digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), etc. Computer-storage media may not include a propagated data signal. 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 other transport mechanisms and include any information delivery media.

[0292] The term “modulated data signal” may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above listed components should also be included within the scope of computer-readable media.

[0293] The memory 834 may include computer-storage media in the form of volatile and / or non-volatile memory. The memory 834 may be removable, non-removable, or a combination thereof. Example memory may include solid-state memory, hard drives, optical-disc drives, etc. As illustrated in FIG. 8, the memory 834 may store a computer-readable and / or computer-executable instructions 832 (e.g., software codes) that are configured to, when executed, cause the processor 828 to perform various functions disclosed herein, for example, with reference to FIGS. 1 through 7. Alternatively, the instructions 832 may not be directly executable by the processor 828 but may be configured to cause the node 800 (e.g., when compiled and executed) to perform various functions disclosed herein. The AI / ML module(s) may be implemented with a supervised learning approach or an unsupervised learning approach (e.g., Transductive approach and Inductive approach).

[0294] The processor 828 (e.g., having processing circuitry) may include an intelligent hardware device, e.g., a Central Processing Unit (CPU), a microcontroller, an ASIC, etc. The processor 828 may include memory. The processor 828 may process the data 830 and the instructions 832 received from the memory 834, and information transmitted and received via the transceiver 820, the baseband communications module, and / or the network communications module. The processor 828 may also process information to send to the transceiver 820 for transmission via the antenna 836 to the network communications module for transmission to a CN.

[0295] One or more presentation components 838 may present data indications to a person or another device. Examples of presentation components 838 may include a display device, a speaker, a printing component, a vibrating component, etc.

[0296] In view of the present disclosure, it is obvious that various techniques may be used for implementing the disclosed concepts without departing from the scope of those concepts. Moreover, while the concepts have been disclosed with specific reference to certain implementations, a person of ordinary skill in the art may recognize that changes may be made in form and detail without departing from the scope of those concepts. As such, the disclosed implementations are to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the particular implementations disclosed and many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

1. A user equipment (UE) for layer 1 (L1) measurement reporting, the UE comprising: 　　　　at least one processor; and 　　　　at least one non-transitory computer-readable medium coupled to 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), an L1 measurement configuration that configures at least one layer 1 (L1) / layer 2 (L2) triggered mobility (LTM) event; 　　　　　　　　measure a plurality of candidate beams to obtain a plurality of L1 measurement results; 　　　　　　　　determine, based on the at least one LTM event, a priority of each of the plurality of candidate beams; 　　　　　　　　generate an L1 measurement report (L1-MR) medium access control (MAC) control element (CE) by assembling the plurality of L1 measurement results associated with the plurality of candidate beams in the L1-MR MAC CE based on the priority of each of the plurality of candidate beams; and 　　　　　　　　transmit, to the BS, the L1-MR MAC CE, wherein: 　　　　　　　　　　　　each of the plurality of candidate beams is associated with a reference signal index of an LTM candidate cell, and 　　　　　　　　　　　　the L1-MR MAC CE is generated by a MAC entity of the UE.

2. The UE of claim 1, wherein determining, based on the at least one LTM event, the priority of each of the plurality of candidate beams comprises: 　　　　determining that a first candidate beam of the plurality of candidate beams has a first priority after determining that a first L1 measurement result of the first candidate beam remains satisfying an entering condition of the at least one LTM event upon expiry of a first time-to-trigger (TTT) timer associated with the entering condition; 　　　　determining that a second candidate beam of the plurality of candidate beams has a second priority after determining that a second L1 measurement result of the second candidate beam remains satisfying a leaving condition of the at least one LTM event upon expiry of a second TTT timer associated with the leaving condition; 　　　　determining that a third candidate beam of the plurality of candidate beams has a third priority after determining that a third L1 measurement result of the third candidate beam has been reported and the third L1 measurement result does not remain satisfying the leaving condition of the at least one LTM event upon expiry of the second TTT timer; and 　　　　determining that a fourth candidate beam of the plurality of candidate beams has a fourth priority after determining that a fourth L1 measurement result of the fourth candidate beam does not remain satisfying the entering condition of the at least one LTM event upon expiry of the first TTT timer and does not remain satisfying the leaving condition of the at least one LTM event upon expiry of the second TTT timer, wherein 　　　　　　　　the first priority, the second priority, the third priority, and the fourth priority are in a decreasing order of priority.

3. The UE of claim 2, wherein generating the L1-MR MAC CE by assembling the plurality of L1 measurement results associated with the plurality of candidate beams in the L1-MR MAC CE based on the priority of each of the plurality of candidate beams comprises: 　　　　assembling the first L1 measurement result in the L1-MR MAC CE before assembling the second L1 measurement result, the third L1 measurement result, and the fourth L1 measurement result in the L1-MR MAC CE; 　　　　assembling the second L1 measurement result in the L1-MR MAC CE before assembling the third L1 measurement result and the fourth L1 measurement result in the L1-MR MAC CE; 　　　　assembling the third L1 measurement result in the L1-MR MAC CE before assembling the fourth L1 measurement result in the L1-MR MAC CE; and 　　　　assembling the fourth L1 measurement result in the L1-MR MAC CE after assembling the first L1 measurement result, second L1 measurement result, and third L1 measurement result in the L1-MR MAC CE after determining that a specific information element (IE) indicating that an L1 measurement result of a candidate beam having the fourth priority is allowed to be reported.

4. The UE of claim 2, wherein: 　　　　generating the L1-MR MAC CE by assembling the plurality of L1 measurement results associated with the plurality of candidate beams in the L1-MR MAC CE based on the priority of each of the plurality of candidate beams comprises refraining from assembling the first L1 measurement result in the L1-MR MAC CE after determining that the first candidate beam has the first priority and the first L1 measurement result remains satisfying the leaving condition of the at least one LTM event upon expiry of the second TTT timer, and 　　　　the L1-MR MAC CE includes a truncated L1-MR MAC CE.

5. The UE of claim 1, wherein: 　　　　the L1 measurement configuration comprises an information element (IE) that indicates that the UE is allowed to generate the L1-MR MAC CE after determining that an L1 measurement result of one of the plurality of candidate beams remains satisfying a leaving condition of the at least one LTM event upon expiry of a time-to-trigger (TTT) timer associated with the leaving condition, and 　　　　the IE is configured by a radio resource control (RRC) configuration.

6. The UE of claim 1, wherein the one or more computer-executable instructions that, when executed by the at least one processor, further cause the UE to: 　　　　receive, from the BS, an information element (IE) that indicates whether an L1 measurement result of a current beam of a serving cell is to be reported via the L1-MR MAC CE; and 　　　　assemble the L1 measurement result of the current beam of the serving cell in the L1-MR MAC CE after determining that the IE indicates that the L1 measurement result of the current beam of the serving cell is to be reported via the L1-MR MAC CE, wherein 　　　　　　　　the IE is configured by a radio resource control (RRC) configuration.

7. The UE of claim 1, wherein: 　　　　the L1 measurement configuration comprises a scheduling request (SR) configuration specific for the transmission of the L1-MR MAC CE, and 　　　　the one or more computer-executable instructions that, when executed by the at least one processor, further cause the UE to: 　　　　transmit, to the BS, a scheduling request based on the SR configuration, and 　　　　after determining that the MAC entity is reset: 　　　　　　　　release the plurality of L1 measurement results, the scheduling request, and the L1-MR MAC CE, and 　　　　　　　　stop all running TTT timers associated with the at least one LTM event.

8. The UE of claim 1, wherein: 　　　　the L1 measurement configuration further configures a periodical reporting timer and a value of the periodical reporting timer, 　　　　the periodical reporting timer is used for the UE to report the L1-MR MAC CE periodically, and 　　　　the one or more computer-executable instructions that, when executed by the at least one processor, further cause the UE to: 　　　　　　　　start or restart the periodical reporting timer; and 　　　　　　　　generate and transmit the L1-MR MAC CE after determining that the periodical reporting timer expires and one or more of the plurality of L1 measurement results that satisfy an entering condition or a leaving condition of the at least one LTM event are pending.

9. The UE of claim 1, wherein: 　　　　the L1 measurement configuration further configures a maximum number of beams to be reported in the L1-MR MAC CE, and 　　　　the maximum number is applied to one or more beams of neighbor cells and a current beam of a serving cell when the UE is indicated by the BS to report an L1 measurement result of the current beam of the serving cell.

10. A method performed by a user equipment (UE) for layer 1 (L1) measurement reporting, the method comprising: 　　　　receiving, from a base station (BS), an L1 measurement configuration that configures at least one layer 1 (L1) / layer 2 (L2) triggered mobility (LTM) event; 　　　　measure a plurality of candidate beams to obtain a plurality of L1 measurement results; 　　　　determine, based on the at least one LTM event, a priority of each of the plurality of candidate beams; 　　　　generate an L1 measurement report (L1-MR) medium access control (MAC) control element (CE) by assembling the plurality of L1 measurement results associated with the plurality of candidate beams in the L1-MR MAC CE based on the priority of each of the plurality of candidate beams; and 　　　　transmit, to the BS, the L1-MR MAC CE, wherein: 　　　　　　　　each of the plurality of candidate beams is associated with a reference signal index of an LTM candidate cell, and 　　　　　　　　the L1-MR MAC CE is generated by a MAC entity of the UE.

11. A base station (BS) for managing layer 1 (L1) measurement reporting, 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), an L1 measurement configuration that configures at least one layer 1 (L1) / layer 2 (L2) triggered mobility (LTM) event, wherein the L1 measurement configuration causes the UE to: 　　　　　　　　　　　　measure a plurality of candidate beams to obtain a plurality of L1 measurement results; 　　　　　　　　　　　　determine, based on the at least one LTM event, a priority of each of the plurality of candidate beams; 　　　　　　　　　　　　generate an L1 measurement report (L1-MR) medium access control (MAC) control element (CE) by assembling the plurality of L1 measurement results associated with the plurality of candidate beams in the L1-MR MAC CE based on the priority of each of the plurality of candidate beams; and 　　　　　　　　　　　　transmit, to the BS, the L1-MR MAC CE, wherein: 　　　　　　　　　　　　　　　　each of the plurality of candidate beams is associated with a reference signal index of an LTM candidate cell, and 　　　　　　　　　　　　　　　　the L1-MR MAC CE is generated by a MAC entity of the UE.

12. The BS of claim 11, wherein: 　　　　the L1 measurement configuration comprises an information element (IE) that indicates that the UE is allowed to generate the L1-MR MAC CE after determining that an L1 measurement result of one of the plurality of candidate beams remains satisfying a leaving condition of the at least one LTM event upon expiry of a time-to-trigger (TTT) timer associated with the leaving condition, and 　　　　the IE is configured by a radio resource control (RRC) configuration.

13. The BS of claim 11, wherein the one or more computer-executable instructions that, when executed by the at least one processor, further cause the BS to: 　　　　transmit, to the UE, an information element (IE) that indicates whether an L1 measurement result of a current beam of a serving cell is to be reported via the L1-MR MAC CE, wherein the IE causes the UE to: 　　　　　　　　assemble the L1 measurement result of the current beam of the serving cell in the L1-MR MAC CE after determining that the IE indicates that the L1 measurement result of the current beam of the serving cell is to be reported via the L1-MR MAC CE, wherein 　　　　　　　　　　　　the IE is configured by a radio resource control (RRC) configuration.

14. The BS of claim 11, wherein: 　　　　the L1 measurement configuration comprises a scheduling request (SR) configuration specific for the transmission of the L1-MR MAC CE, and 　　　　the L1 measurement configuration causes the UE to: 　　　　　　　　transmit, to the BS, a scheduling request based on the SR configuration, and 　　　　　　　　after determining that the MAC entity is reset: 　　　　　　　　　　　　release the plurality of L1 measurement results, the scheduling request, and the L1-MR MAC CE, and 　　　　　　　　　　　　stop all running TTT timers associated with the at least one LTM event.

15. The BS of claim 11, wherein: 　　　　the L1 measurement configuration further configures a maximum number of beams to be reported in the L1-MR MAC CE, and 　　　　the maximum number is applied to one or more beams of neighbor cells and a current beam of a serving cell when the UE is indicated by the BS to report an L1 measurement result of the current beam of the serving cell.

Images