Methods and devices for l1 measurement reporting
By maintaining predefined beam lists and triggering event-based measurement reports with priority rules, the solution addresses inefficiencies in Layer-1 measurement reporting, enhancing the efficiency and speed of Layer-1/Layer-2 triggered mobility in wireless networks.
Patent Information
- Application Number
- PCT/CN2025/093859
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face challenges in efficiently managing Layer-1 measurement reporting for fast serving cell changes, including determining the content, provisioning, and configuring beams for L1 measurement reports, which affect the efficiency of Layer-1/Layer-2 triggered mobility.
The solution involves maintaining predefined beam lists with different types (Type 1-4) based on entering and leaving conditions, updating these lists, and triggering event-based measurement reports to efficiently select and report beams, with priority rules and constraints on the number of beams included in the report.
This approach enhances the efficiency of Layer-1/Layer-2 triggered mobility by optimizing beam selection and reporting, reducing signaling overhead, and improving the speed and reliability of cell switching in wireless networks.
Smart Images

Figure CN2025093859_12112026_PF_FP_ABST
Abstract
Description
METHODS AND DEVICES FOR L1 MEASUREMENT REPORTINGTECHNICAL FIELD
[0001] The present disclosure is directed generally to wireless communications. Particularly, the present disclosure relates to methods and devices for Layer-1 (L1) measurement reporting in a mobile communication system.BACKGROUND
[0002] Wireless communication technologies are moving the world toward an increasingly connected and networked society. High-speed and low-latency wireless communications rely on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations) . A new generation network is expected to provide high speed, low latency and ultra-reliable communication capabilities and fulfill the requirements from different industries and users.
[0003] In a wireless communication system, Layer 1 / Layer 2 triggered mobility (LTM) constitutes an important technology to perform fast serving cell change compared to a legacy handover, as the LTM may dramatically reduce handover delays. To enable fast cell switch, the network can pre-configure multiple LTM candidate configurations based on a Layer 1 (L1) measurement report. To reduce signaling overhead, the LTM configurations can also be provided based on a reference configuration. However, there are some challengers / problems associated with L1 measurement reporting. For example, the content of the L1 measurement report needs to be determined, beams to be reported need to be provisioned, maintained and selected, and / or the format of the L1 measurement report needs to be configured as well.
[0004] The present disclosure describes various embodiments for L1 measurement reporting in a mobile communication system, addressing at least one of the challenges / problems discussed in the present disclosure, thereby increasing efficiency of LTM, enabling future wireless communication system to provide improved performance to meet various demands of new generation wireless services.SUMMARY
[0005] The present disclosure is directed generally to wireless communications. Particularly, the present disclosure relates to methods and devices for event-based Layer-1 (L1) measurement reporting in a mobile communication system. The beams being measured and reported are maintained in a set of predefined beam lists. Each beam may further be associated with a beam type that indicates its status in meeting an entering condition and / or leaving condition of the event and reporting status thereof. A beam may change type during an L1 measurement procedure and / or an L1 measurement reporting procedure and may be moved into or out of a particular beam list. The multiple beam lists facilitate selection of beams to report when the event-based report is triggered.
[0006] In some example implementations, a method performed by a User Equipment (UE) in communication with a base station in a wireless communication network is disclosed. The method may include performing Layer-1 (L1) measurement of a beam according to a measurement configuration provided by the base station; determining a beam type of the beam among a plurality of predefined beam types according to an evaluation of the L1 measurement of the beam against an entering condition or a leaving condition of an event; and triggering a measurement report to report the L1 measurement of the beam to the base station, when the L1 measurement of the beam meets the entering condition or the leaving condition of the event.
[0007] In the example implementations above, the method may further include updating a plurality of beam lists separately maintained by the UE according to the evaluation, each beam list of the plurality of beam lists identifying beams belonging to one or more beam types of the plurality of predefined beam types.
[0008] In any one of the example implementations above, the method may further include, when the measurement report is triggered, performing at least one of the following: selecting one or more beams from a plurality of beam lists; including measurements for the one or more beams in the measurement report; transmitting the measurement report to the base station; and updating the plurality of beam lists with respect to the one or more beams as a result of them being included in the measurement report.
[0009] In any one of the example implementations above, the plurality of predefined beam types comprises: a first type (Type 1) for any beam just fulfilling the entering condition of the event; a second type (Type 2) for any beam having previously-reported fulfilment of the entering condition of the event and having just fulfilled the leaving condition of the event; a third type (Type 3) for any beam having previously-reported fulfilment of the entering condition of the event but having not fulfilled the leaving condition of the event; and a fourth type (Type-4) for any beam having not fulfilled the entering condition of the event.
[0010] In any one of the example implementations above, wherein determining the beam type of the beam among the plurality of predefined beam types comprises: modifying the beam from Type 1 to Type 4 when the beam was of Type 1 but has subsequently fulfilled the leaving condition of the event according to the L1 measurement without its previous fulfilment of the entering condition of the event being reported yet.
[0011] In any one of the example implementations above, wherein determining the beam type of the beam among the plurality of predefined beam types comprises: modifying the beam from Type-2 to Type-1 or Type 3 when the beam was of Type 2 but has subsequently fulfilled the entering condition of the event according to the L1 measurement without its previous fulfilment of the leaving condition of the event being reported yet.
[0012] In any one of the example implementations above, the method further include maintaining a plurality of beam lists, wherein the plurality of beam lists comprise: a first beam list for Type-1 beams, a second beam list for Type 2 beams, and a third beam list for Type 3 beams; or a first beam list for Type 1 beams and type 2 beams, and a second beam list for Type 3 beams; or a first beam list for Type 1 beams and Type 3 beams, and a second beam list for Type 2 beams; or a first beam list for Type 1 beams, and a second beam list for Type-2 beams and Type 3 beams; or a single beam list for Type 1 beams, Type 2 beams, and Type-3 beams; or a single beam list for Type 1 beams, Type 2 beams, Type-3 beams, and Type 4 beams.
[0013] In any one of the example implementations above, beam types of beams within a beam list encompassing multiple beam types are identified by explicit or implicit beam type flags.
[0014] In any one of the example implementations above, the plurality of beam lists comprise a first beam list for Type-1 beams, a second beam list for Type 2 beams, and a third beam list for Type 3 beams, and wherein the method further comprises updating the plurality of beam lists after the measurement report is triggered by performing at least one of the following: moving, from the first beam list to the third beam list, beams that have been reported; removing, from the first beam list, beams that are not reported; moving, from the third beam list to the second beam list, beams that subsequently fulfill the leaving condition of the event, followed by removing one or more of these beams from the second beam list after they are further reported; and removing, from the second beam list, beams that have been reported.
[0015] In any one of the example implementations above, the method may further include updating the plurality of beam lists by removing beams from the plurality of beam lists or moving beams from one beam list to another beam list according to status change of the beams with respect to their report status and their fulfilment of the entering conditions or the leaving conditions of the event.
[0016] In any one of the example implementations above, the method further include, when the measurement report is triggered, selecting one or more beams from the plurality of beam lists for reporting by performing at least one of the following: determining an upper bound number of beams that can be included in the measurement report; and selecting the one or more beams from the plurality of beam lists according to a predefined priority rule, limited by the upper bound number of beams.
[0017] In any one of the example implementations above, wherein determining the upper bound number of beams that can be included in the measurement report comprises at least one of the following: receiving a UL grant from the base station for the measurement report; and determining the upper bound number of beams that can be included in an MR MAC CE (measurement report MAC CE) or truncated MR MAC CE according to a maximum number of beams that can be accommodated in the MR MAC CE or the truncated MR MAC CE as limited by a size of the UL grant.
[0018] In any one of the example implementations above, the predefined priority rule comprises selecting, from the plurality of beam lists until an upper bound number of beams are reached, in a descending priority order of: Type 1, Type 2, Type 3, Type 4; Type 1 / Type 2, Type 3, Type 4; Type 1 / Type 2, Type 3, Type 4, serving; Type 1 / Type 2, Type 3, serving, Type 4; or Type 1 / Type 2, serving, Type 3, Type 4.
[0019] In any one of the example implementations above, wherein a triggered measurement report is considered complete or cancelled when: all beam lists including Type 1 beams are empty; all beam lists including Type 1 beams and Type 2 beams are empty; all beam lists including Type 1 beams and Type 2 beams and Type 3 beams are empty; an MR MAC CE or a truncated MR MAC CE for the triggered measurement report has been successfully transmitted; all beams of Type 1 and Type 2 having been included in an MR MAC CE or a truncated MR MAC CE for the measurement report previously transmitted; a beam having met the entering condition firstly then meets the leaving condition before receiving a UL grant for the triggered measurement report; or a beam having met the leaving condition firstly then meets the entering condition before receiving a UL grant for the triggered measurement report.
[0020] In any one of the example implementations above, the method may further include removing entries in the triggered measurement report from a measurement result list.
[0021] In any one of the example implementations above, when not all beams of Type 1 and Type 2 in the plurality of beam lists can be included in an MR MAC CE or a truncated MR MAC CE for the measurement report: initiating another measurement reporting procedure for the event; or not initiating another measurement reporting procedure for the event until a new beam meets the entering condition or the leaving condition of the event; or including, in the MR MAC CE or the truncated MR MAC CE, an indication of remaining triggered beams that have not been included in the MR MAC CE or the truncated MR MAC CE.
[0022] In any one of the example implementations above, the method further include the measurement report is triggered as a periodic reporting procedure with a reporting periodicity and number of reports for the periodic reporting procedure; and the method further comprises: maintaining a counter of reports for each report configuration associated with the event; and resetting the counter to zero when there is a new beam meeting the entering condition of the event.
[0023] In any one of the example implementations above, the event is associated with qualities of current serving beams of the UE and the method further comprises: determining whether candidate beams for LTM (Layer-1 / Layer-2 Triggered Mobility) candidate cells are permitted in the measurement report; and when the candidate beams for LTM candidate cells are permitted in the measurement report, including the candidate beams in the measurement report under a condition that inclusion of the current serving beams in the measurement report takes priority over the candidate beams for LTM candidate cells.
[0024] In any one of the example implementations above, whether the candidate beams for LTM candidate cells are to be included in the measurement report is indicated by the base station.
[0025] 20. The method of claim 19, wherein when the candidate beams for LTM candidate cells are not permitted in the measurement report, the method further comprises only including the current serving beams in the measurement report.
[0026] In some other embodiments, the UE above may include a memory storing instructions and at least one processing circuitry in communication with the memory. When the at least one processing circuitry executes the instructions, the at least one processing circuitry is configured to carry out any of the methods above and / or in the present disclosure.
[0027] In some other embodiments, a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the methods above and / or in the present disclosure. The computer-readable medium may be a non-transitory computer-readable medium.
[0028] In some other embodiments, a computer program product comprising a computer-readable program medium code stored thereupon, the computer-readable program medium code, when executed by at least one processor, causing the at least one processor to implement any of the methods above and / or in the present disclosure. The computer program product may be a non-transitory computer program product. The computer-readable program medium code may be a non-transitory computer-readable program code.
[0029] The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.BRIEF DESCRIPTION OF THE DRAWINGS
[0030] FIG. 1 illustrates an example wireless communication network including a wireless access network, a core network, and data networks.
[0031] FIG. 2 illustrates an example wireless access network including a plurality of mobile stations / terminals or User Equipments (UEs) and a wireless access network node in communication with one another via an over-the-air radio communication interface.
[0032] FIG. 3 shows an example radio access network (RAN) architecture.
[0033] FIG. 4 shows an example communication protocol stack in a wireless access network node or wireless terminal device including various network layers.
[0034] FIG. 5 shows an example flow for determining beam types in an L1 measurement reporting procedure.
[0035] FIG. 6 shows another example flow for determining beam types in an L1 measurement reporting procedure.DETAILED DESCRIPTION
[0036] The present disclosure will now be described in detail hereinafter with reference to the accompanied drawings, which form a part of the present disclosure, and which show, by way of illustration, specific examples of embodiments. Please note that the present disclosure may, however, be embodied in a variety of different forms and, therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the embodiments to be set forth below.
[0037] Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment” or “in some embodiments” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment” or “in other embodiments” as used herein does not necessarily refer to a different embodiment. The phrase “in one implementation” or “in some implementations” as used herein does not necessarily refer to the same implementation and the phrase “in another implementation” or “in other implementations” as used herein does not necessarily refer to a different implementation. It is intended, for example, that claimed subject matter includes combinations of exemplary embodiments or implementations in whole or in part.
[0038] In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and” , “or” , or “and / or, ” as used herein may include a variety of meanings that may depend at least in part upon the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” or “at least one” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a” , “an” , or “the” , again, may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” or “determined by” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.
[0039] Wireless Network Overview
[0040] An example wireless communication network, shown as 100 in FIG. 1, may include wireless terminal devices or user equipment (UE) 110, 111, and 112, a carrier network 102, various service applications 140, and other data networks 150. The wireless terminal devices or UEs, may be alternatively referred to as wireless terminals. The carrier network 102, for example, may include access network nodes 120 and 121, and a core network 130. The carrier network 110 may be configured to transmit voice, data, and other information (collectively referred to as data traffic) among UEs 110, 111, and 112, between the UEs and the service applications 140, or between the UEs and the other data networks 150. The access network nodes 120 and 121 may be configured as various wireless access network nodes (WANNs, alternatively referred to as wireless base stations) to interact with the UEs on one side of a communication session and the core network 130 on the other. The term “access network” may be used more broadly to refer a combination of the wireless terminal devices 110, 111, and 112 and the access network nodes 120 and 121. A wireless access network may be alternatively referred to as Radio Access Network (RAN) . The core network 130 may include various network nodes configured to control communication sessions and perform network access management and traffic routing. The service applications 140 may be hosted by various application servers deployed outside of but connected to the core network 130. Likewise, the other data networks 150 may also be connected to the core network 130.
[0041] In the example wireless communication network of 100 of FIG. 1, the UEs may communicate with one another via the wireless access network. For example, UE 110 and 112 may be connected to and communicate via the same access network node 120. The UEs may communicate with one another via both the access networks and the core network. For example, UE 110 may be connected to the access network node 120 whereas UE 111 may be connected to the access network node 121, and as such, the UE 110 and UE 111 may communicate to one another via the access network nodes 120 and 121, and the core network 130. The UEs may further communicate with the service applications 140 and the data networks 150 via the core network 130. Further, the UEs may communicate to one another directly via side link communications, as shown by 113.
[0042] FIG. 2 further shows an example system diagram of the wireless access network 120 including a WANN 202 serving UEs 110 and 112 via the over-the-air interface 204. The wireless transmission resources for the over-the-air interface 204 include a combination of frequency, time, and / or spatial resource. Each of the UEs 110 and 112 may be a mobile or fixed terminal device installed with mobile access units such as SIM / USIM modules for accessing the wireless communication network 100. The UEs 110 and 112 may each be implemented as a terminal device including but not limited to a mobile phone, a smartphone, a tablet, a laptop computer, a vehicle on-board communication equipment, a roadside communication equipment, a sensor device, a smart appliance (such as a television, a refrigerator, and an oven) , or other devices that are capable of communicating wirelessly over a network. As shown in FIG. 2, each of the UEs such as UE 112 may include transceiver circuitry 206 coupled to one or more antennas 208 to effectuate wireless communication with the WANN 120 or with another UE such as UE 110. The transceiver circuitry 206 may also be coupled to a processor 210, which may also be coupled to a memory 212 or other storage devices. The memory 212 may be transitory or non-transitory and may store therein computer instructions or code which, when read and executed by the processor 210, cause the processor 210 to implement various ones of the methods described herein.
[0043] Similarly, the WANN 120 may include a wireless base station or other wireless network access point capable of communicating wirelessly via the over-the-air interface 204 with one or more UEs and communicating with the core network 130. For example, the WANN 120 may be implemented, without being limited, in the form of a 2G base station, a 3G nodeB, an LTE eNB, a 4G LTE base station, a 5G NR base station of a 5G gNB, a 5G central-unit base station, or a 5G distributed-unit base station. Each type of these WANNs may be configured to perform a corresponding set of wireless network functions. The WANN 202 may include transceiver circuitry 214 coupled to one or more antennas 216, which may include an antenna tower 218 in various forms, to effectuate wireless communications with the UEs 110 and 112. The transceiver circuitry 214 may be coupled to one or more processors 220, which may further be coupled to a memory 222 or other storage devices. The memory 222 may be transitory or non-transitory and may store therein instructions or code that, when read and executed by the one or more processors 220, cause the one or more processors 220 to implement various functions of the WANN 120 described herein.
[0044] Data packets in a wireless access network such as the example described in FIG. 2 may be transmitted as protocol data units (PDUs) . The data included therein may be packaged as PDUs at various network layers wrapped with nested and / or hierarchical protocol headers. The PDUs may be communicated between a transmitting device or transmitting end (these two terms are used interchangeably) and a receiving device or receiving end (these two terms are also used interchangeably) once a connection (e.g., a radio link control (RRC) connection) is established between the transmitting and receiving ends. Any of the transmitting device or receiving device may be either a wireless terminal device such as device 110 and 120 of FIG. 2 or a wireless access network node such as node 202 of FIG. 2. Each device may both be a transmitting device and receiving device for bi-directional communications.
[0045] The core network 130 of FIG. 1 may include various network nodes geographically distributed and interconnected to provide network coverage of a service region of the carrier network 102. These network nodes may be implemented as dedicated hardware network nodes. Alternatively, these network nodes may be virtualized and implemented as virtual machines or as software entities. These network nodes may each be configured with one or more types of network functions which collectively provide the provisioning and routing functionalities of the core network 130.
[0046] Returning to wireless radio access network (RAN) , FIG. 3 illustrates an example RAN 340 in communication with a core network 310 and wireless terminals UE1 to UE7. The RAN 340 may include one or more various types of wireless base station or WANNs 320 and 321 which may include but are not limited to gNB, eNodeB, NodeB, or other type of base stations. The RAN 340 may be backhauled to the core network 310. The WANNs 320, for example, may further include multiple separate access network nodes in the form of a Central Unit (CU) 322 and one or more Distributed Unit (DU) 324 and 326. The CU 322 is connected with DU1 324 and DU2 326 via various interfaces, for example, an F1 interface. The F1 interface, for example, may further include an F1-C interface and an F1-U interface, which may be used to carry control plane information and user plane data, respectively. In some embodiments, the CU may be a gNB Central Unit (gNB-CU) , and the DU may be a gNB Distributed Unit (gNB-DU) . While the various implementations described below are provided in the context of a 5G cellular wireless network, the underlying principles described herein are applicable to other types of radio access networks including but not limited to other generations of cellular network, as well as Wi-Fi, Bluetooth, ZigBee, and WiMax networks.
[0047] The UEs may be connected to the network via the WANNs 320 over an air interface. The UEs may be served by at least one cell. Each cell is associated with a coverage area. These cells may be alternatively referred to as serving cells. The coverage areas between cells may partially overlap. Each UE may be actively communicating with at least one cell while may be potentially connected or connectable to more than one cell. In the example of FIG. 1, UE1, UE2, and UE3 may be served by cell1 330 of the DU1, whereas UE4 and UE5 may be served by cell2 332 of the DU1, and UE6 and UE7 may be served by cell3 associated with DU2. In some implementations, a UE may be served simultaneously by two or more cells. Each of the UE may be mobile and the signal strength and quality from the various cells at the UE may depend on the UE location and mobility.
[0048] FIG. 4 further illustrates a simplified view of the various network layers involved in transmitting user-plane PDUs from a transmitting device 402 to a receiving device 404 in the example wireless access network of FIGs. 1-3. FIG. 4 is not intended to be inclusive of all essential device components or network layers for handling the transmission of the PDUs. FIG. 4 illustrates that the data packaged by upper network layers 420 at the transmitting device 402 may be transmitted to corresponding upper layer 430 (such as radio resource control or RRC layer) at the receiving device 304 via Packet Data Convergence Protocol layer (PDCP layer, not shown in FIG. 4) and radio link control (RLC) layer 422 and of the transmitting device, the physical (PHY) layers of the transmitting and receiving devices and the radio interface, as shown as 406, and the media access control (MAC) layer 434 and RLC layer 432 of the receiving device. Various network entities in each of these layers may be configured to handle the transmission and retransmission of the PDUs.
[0049] In FIG. 4, the upper layers 420 may be referred as layer-3 or L3, whereas the intermediate layers such as the RLC layer and / or the MAC layer and / or the PDCP layer (not shown in FIG. 4) may be collectively referred to as layer-2, or L2, and the term layer-1 is used to refer to layers such as the physical layer and the radio interface-associated layers. In some instances, the term “low layer” may be used to refer to a collection of L1 and L2, whereas the term “high layer” may be used to refer to layer-3. In some situations, the term “lower layer” may be used to refer to a layer among L1, L2, and L3 that are lower than a current reference layer. Control signaling may be initiated and triggered at each of L1 through L3 and within the various network layers therein. These signaling messages may be encapsulated and cascaded into lower layer packages and transmitted via allocated control or data over-the-air radio resources and interfaces. The term “layer” generally includes various corresponding entities thereof. For example, a MAC layer encompasses corresponding MAC entities that may be created. The layer-1 (L1) , for example, encompasses PHY entities. The layer-2 (L2) , for another example encompasses MAC layers / entities, RLC layers / entities, service data adaptation protocol (SDAP) layers and / or PDCP layers / entities.
[0050] L1 / L2 Triggered Mobility (LTM)
[0051] General handover procedure for UE mobility may be applied at various network layers. For example, a handover procedure may be applied to Layer-1 / Layer-2 Triggered Mobility (LTM) . LTM refers to a procedure in which a base station (e.g., a gNB, which is used interchangeably with the term “base station” ) receives L1 measurement report (s) from a UE, and on that basis changes UE’s serving cell by a cell switch command signaled via, for example, a MAC CE. The cell switch command indicates as a target cell an LTM candidate cell with a cell configuration that the gNB previously prepared and provided to the UE through RRC signaling. Then the UE switches to the target cell according to the cell switch command. The cell switch command may be conveyed in a MAC CE, which contains the necessary information to perform the LTM cell switch. An LTM cell switching may be inter-gNB or intra-gNB, depending on whether the source cell and the target cell are from a same gNB or from different gNBs. Because LTM occurs at L1 / L2, unlike the traditional Layer-3 (L3) handover, the cell switching efficiency and speed may be greatly improved, thereby reducing mobility delays.
[0052] In an example LTM procedure, a set of LTM candidates may be pre-configured before any cell switching. Specifically, to enable fast cell switch, the network can pre-configure multiple candidates with various LTM configurations. To reduce signaling overhead, the LTM configuration can also be provided based on a reference configuration.
[0053] For LTM, L1 measurements of the serving cells and the neighboring as performed by the UE are essential. These L1 measurements provide the network with information to determine whether to trigger handover, e.g., LTM cell switching. For the network to make such determination, the L1 measurements need to be reported to the network by the UE.
[0054] The L1 measurements may be made by the UE on both serving and neighbor cells. The L1 measurements may then be reported to the network (e.g., a source base station for the UE) periodically, semi-persistently, aperiodically, or when a specific event is considered to be met. For event-based L1 measurement reporting, the L1 measurement report may be sent to the network via, for example, a MAC CE.
[0055] Further, to reduce latency, before an LTM execution, the network can configure and activate TCI (Transmission Configuration Indication) states for candidate cells, allowing the UE to maintain downlink (DL) synchronization with these cells. Additionally, the network can also include the TCI-state in an LTM cell switch MAC CE when executing the LTM cell switching to indicate activated beam (s) of an LTM target cell.
[0056] Likewise, to reduce latency, RACH-less (Random Access Channel-less) based LTM may be supported, which allows the UE to complete uplink (UL) synchronization in advance without going through the standard RACH procedure. To achieve this, LTM procedure may introduce a PDCCH (Physical Downlink Control Channel) ordered RACH mechanism, where the network triggers the UE to acquire the TA of the target cell (or candidate cell) through PDCCH. Additionally, the network can also configure the UE to enable “UE-based TA” , where a UE with such capabilities can acquire the TA of a target cell or candidate cell based on UE’s calculation before LTM execution.
[0057] From a network perspective, the network can trigger early DL / UL synchronization above based on received L1 measurement report. As such, the L1 measurements not only can be used by the network to determine when to trigger LTM cell switching but also can be used to assist early DL / UL synchronization to further reduce latency.
[0058] The various example implementations disclosed below provide (1) example manner in which L1 measurement reporting is triggered, particularly for event trigger based measurement reporting, (2) example manners in which the status of various beams (including current serving cell beams and neighboring beams, either intra-base station, or inter-base station) with respect to triggering the event and reporting thereof is categorized and updated, (3) example manners in which such status is used to prioritize selection of beams to report when a number beams that can be included in a measurement report (MR) is limited, (4) example manner in which MRs are triggered, among several other improvements for event-based L1 measurement reporting.
[0059] Event-Based L1 Measurement Reporting
[0060] In some implementations, for an event-based L1 measurement reporting, a network may configure the L1 measurement configuration to a UE. The L1 measurement configuration may include reference signal (RS) resources (e.g., synchronization signal block (SSB) or channel state information reference signal (CSI-RS) ) and associated L1 reporting configuration. In the reporting configuration, the network may indicate the report type, including periodical reporting, aperiodical reporting, semi-persistent reporting, or event-based reporting.
[0061] In some example implementations, for event-based reporting, the network may further indicate the event type among a predefined set of event types (e.g., LTM2, LTM3, LTM4, LTM5, LTM6 event types, and the like) and corresponding event related parameters (e.g., thresholds, TimeToTrigger, etc. ) .
[0062] In some example implementations, after receiving the L1 measurement configuration, the UE may start to perform L1 measurements according to the measurement configuration, and to perform event evaluation based on the L1 measurement results.
[0063] In some example implementations, for event evaluation, the event may be defined with an “entering condition” and an “leaving condition” . For example, for the LTM3 event, its entering condition and leaving condition may be defined as below:
[0064] Inequality LTM3-1 (Entering condition) : Mn + Obn -Hys > Ms + Obs + Off;
[0065] Inequality LTM3-2 (Leaving condition) : Mn + Obn + Hys < Ms + Obs + Off,
[0066] where Mn represents the beam measurement quantity of an LTM candidate cell (or target cell or neighbor cell) and Ms represents the beam measurement quantity of the serving cell. Hys represents a hysteresis for providing measurement headroom between the entering level and the leaving level.
[0067] In some example implementations, when the entering condition is fulfilled for TimeToTrigger duration, the UE may trigger L1 measurement reporting. Similarly, once a beam already fulfills entering condition and measurement report is sent to the network, and when the leaving condition is fulfilled later on for TimeToTrigger (TTT) duration for this beam, the UE may trigger L1 measurement reporting if ReportOnLeave is configured. The combination of meeting / fulfilling the entering condition or leaving condition for the TTT duration may be referred to as meeting / fulfilling a triggering entering / leaving condition, or for simplicity, as meeting / fulfilling the entering / leaving condition.
[0068] In some example implementations, for event-based L1 measurement reporting, the UE needs to evaluate whether a specific event is fulfilled in order to trigger the measurement report (MR) .
[0069] In some example implementations, multiple events may be supported. For example, LTM-2 event may be supported and it means that the beam quality of a serving cell is worse than a threshold; LTM-3 may be supported and it means that the beam quality of a neighbor cell is offset better than the beam quality of beam in the serving cell; LTM-4 event may be supported and it means that the beam quality of a neighbor cell is better than a threshold; and LTM-5 may be supported and it means that the beam quality of a neighbor cell is better than a threshold and the beam quality of beam in the serving cell is worse than another threshold.
[0070] In some example implementations, regarding the content of an MR, at least beam indicator (s) (or beam index (s) ) and beam level measurement results (e.g., L1 reference signal received power (L1-RSRP) , L1 reference signal received quality (L1-RSRQ) , L1 signal to interference and noise ratio (L1-SINR) ) may be reported. Since the MR is sent via MAC CE (as described in further detail below) , in order to obtain valuable information from the UE and to ensure the size of the MR is not unlimited, the network may configure a maximum number of beams that can be reported in one MR. If the configured maximum number is larger than the number of beams that have fulfilled the entering condition or leaving condition of the event, the UE can report all these beams in one MR and may also include other beam (s) and corresponding beam results that have not met the event threshold. Whether the non-satisfied beams in that circumstance can be reported or not may be configurable.
[0071] In some example implementations, to reduce the message size of L1 measurement report MAC CE (MR MAC CE) , RSRP differential values or other types of differential values (i.e., an offset value relative to a reference value, rather than an actual or absolute value) may be reported, which means that in an L1 measurement report MAC CE, one beam (e.g., with highest RSRP value) may be reported with absolute RSRP value serving as a reference value, and other beams are reported with their offset values to reference value of the first reported beam.
[0072] In this disclosure, the terms “target cell or target beam” and “serving cell or serving beam” are used. The term “target cell” can be used to refer to a PCell (or a PSCell) of a configured candidate configuration. Alternatively, it can be an SCell of a configured candidate configuration. Alternatively, it can be a configured neighbor cell or detected neighbor cell. The term “target beam” is used to refer to a beam of a target cell.
[0073] The term “serving cell” may be used to refer to a serving PCell or PSCell. Alternative, it may be used to refer to a serving SCell. The term “serving beam” may be used to refer to the best beam of a serving cell, or it can be used to refer to a beam indicated by activated TCI-state. Alternative, it may be used to refer to a beam that quasi-collocated with a beam indicated by the activated TCI-state.
[0074] Further in this disclosure, the UE can be a standalone UE in 5G system, 6G system, etc. The UE can also be configured with Carrier Aggregation (CA) and / or dual connect (DC) . In case the UE is configured with DC, the term “network” or “network node” can be used to refer to an MN (Master Node) or an SN (Secondary Node) . In a CU-DU split scenario, the term “network” or “network node” can be used to refer to a CU or a DU.
[0075] In this disclosure, the methods described are applicable to (but are not limit to) L1 event-based measurement reporting and L1 event-based periodical measurement reporting, or a mix thereof.
[0076] In this disclosure, the term “entering condition is fulfilled” may be used to mean that both threshold condition is met and the TimeToTrigger is fulfilled (the threshold condition for entering is met for a TimeToTrigger (TTT) duration) . Similarly, the term “leaving condition is fulfilled” may be used to mean that both a threshold condition is met and the TimeToTrigger is fulfilled (the threshold condition for leaving is met for a TimeToTrigger (TTT) duration) . For disjunctive reference to “MR MAC CE” or “truncated MR MAC CE, it means both the normal MR MAC CE and / or the truncated MR MAC CE can be considered. The notion of “ (truncated) MR MAC CE” also means either or both of the normal MR MAC CE and / or the truncated MR MAC CE.
[0077] The various example implementations and solutions described below in this disclosure are applicable to L1 measurement reporting, but are not so limited. The underlying principles disclosed herein are also applicable to, for example, L3 based measurements reporting. In addition, these example implementations and solutions are applied to MAC CE based measurement reporting, but are not so limited. For example, the disclosed underlying principles disclosed herein may also be applicable to Signal Radio Bearer (SRB) based measurement reporting. The SRB can be SRB1 / 2 / 3 / 4 or a new type of SRB. The SRB may be terminated at CU or DU. The SRB used to transmit the measurement report may be pre-defined or may be configured by the network.
[0078] L1 Measurement Procedure-Beam Types
[0079] For an event-based L1 measurement reporting, the UE performs measurements and measurement event evaluations according to the event configuration. For example, if a neighbor beam fulfills an event condition (e.g., entering condition) , the beam will be stored in an L1 triggered beam list at the UE, and the UE may then initiate an L1 measurement reporting procedure. If more than one neighbor beams have fulfilled the event condition, then the L1 triggered beam list can store each of all those beams that have fulfilled the event condition until it later fulfills the leaving condition. Once a beam in the L1 triggered beam list has fulfilled the leaving condition, that beam will be removed from the L1 triggered beam list stored by the UE.
[0080] In some example implementations, in addition to the L1 triggered beam list, an L1 leaving beam list may also be maintained for the UE. for example, when a neighbor beam fulfills the leaving condition, it may be stored in the L1 leaving beam list at the UE, and the UE may initiate the L1 measurement reporting procedure if, for example, “reportOnLeave” is configured. For each beam that fulfills the leaving condition, it may only be reported once. If a beam that fulfilled the leaving condition is successfully reported to the network, the beam will be removed from the L1 leaving beam list stored by the UE so that it will not be reported again when a next reporting is triggered.
[0081] As such, in some example implementations, from UE’s perspective, there may be 4 types of beams:
[0082] ● Type 1 beam: A beam that just fulfills the entering condition and is initiating L1 measurement reporting.
[0083] ● Type 2 beam: A beam that just fulfills the leaving condition and has been previously reported in an L1 measurement reporting, e.g., via (truncated) MR MAC CE, when it previously met the entering condition, and would initiate L1 measurement reporting because the satisfaction of the leaving condition if reportOnLeave is configured.
[0084] ● Type 3 beam: A beam that already fulfilled the entering condition and has been previously reported in the L1 measurement reporting and has not met the leaving condition. These beams can be reported in the same MR when the L1 measurement reporting procedure is initiated again due to triggering by other Type 1 or Type 2 beams above.
[0085] ● Type 4 beam: A beam that has not fulfilled the entering condition, i.e. a beam of neither Type 1 nor Type 2 nor Type 3 above.
[0086] Due to triggered reporting of the beams, the type of a particular beam may change. An example beam type change flow is shown in FIG. 5.
[0087] As shown in the example of FIG. 5, one or more beams that newly meet the triggering entering condition of the event (e.g., the entering condition is met for a TTT duration) are Type 1 beams. Beams that have not met any triggering entering condition are type 4 beams. Once a Type 1 beam is reported, it becomes a type 3 beam if it has not met the leaving condition. One or more type 1 beams, if meeting the leaving condition of the event (associated with a report configuraiton ID) before being reported yet (e.g., it has not been reported because there was not enough room in a triggered (truncated) MR MAC CE) or before obtaining a UL grant for transmission of the MR (triggered by the fulfillment of the entering condition of the event) , the UE may treat these beams with the following options:
[0088] Option 1: The UE may still consider these concerned beams as Type 1 beams, and / or trigger the measurement reporting procedure for these concerned beams. In other words, the UE may discount the fact that the leaving condition was met because the previously entering condition satisfaction has not been reported yet) .
[0089] Option 2: The UE may consider these concerned beams as Type 4 beams, and / or not trigger the measurement reporting procedure for the concerned beams. In other words, the UE may consider the satisfaction of the leaving condition as offsetting the unreported satisfaction of entering condition and treat the concerned beams as having not satisfied any condition. In another example, the UE may cancel the previously triggered measurement reporting procedure for the concerned beams. The previous measurement reporting procedure, for example, may be triggered by the fulfillment of the entering condition of the event.
[0090] As further shown in FIG. 5, a Type 3 beam, once later meets the triggering leaving condition, it would be turned into a Type 2 beam, otherwise it remains a Type 3 beam.
[0091] In some example implementations, if the leaving condition for the event (associated with a report configuration ID) is fulfilled for one or more beams (e.g., Type 2 beam) , and then the entering condition for the event is fulfilled for the concerned beams, e.g., before the concerned beams have been reported in (truncated) MR MAC CE or before obtaining a UL grant for transmission of the MR (triggered by the fulfillment of the leaving condition of the event) , the UE may have the following options:
[0092] Option 1: The UE may still consider the concerned beams as Type 2 beams, and / or trigger the measurement reporting procedure for the concerned beams. In other words, the UE may discount the latest entering condition fulfilment.
[0093] Option 2: The UE may consider the concerned beams as becoming Type 1 beams, and / or trigger the measurement reporting procedure for the concerned beams. In other words, the UE may only count the recent entering condition fulfilment and discount the previous fulfilment of the entering condition followed by the previous fulfilment of the leaving condition. In another example, the UE may cancel the previously triggered measurement reporting procedure for the concerned beams. The previous measurement reporting procedure is triggered by the fulfillment of the leaving condition of the event. And the UE may trigger another measurement reporting procedure for the concerned beams. The another measurement reporting procedure is triggered by the fulfillment of the entering condition of the event.
[0094] Option 3: The UE may consider the concerned beams as becoming Type 3 beams, and / or not trigger the measurement reporting procedure for the concerned beams. In other words, the UE uses the last fulfilment of the entering condition to cancel the preceding fulfilment of leaving condition and treats the beams as if they only had the original reported fulfilment of the entering condition. In another example, the UE may cancel the previously triggered measurement reporting procedure for the concerned beams. The previous measurement reporting procedure is triggered by the fulfillment of the leaving condition of the event.
[0095] Measurement Report Triggering
[0096] The UE may be configured to manage reporting of the L1 measurement of the beams as one or more beam lists. Several example constructions of the one or more beam lists according to beam types may be considered.
[0097] In Option 1: The UE maintains the following 3 beam lists to record / track different types of beams:
[0098] ● Type 1 beam list (e.g., beam_triggered_list) : including Type 1 beam, e.g., indicated by the RS / beam index (e.g., SSBRI (SSB Resource Indicator) , CRI (CSI-RS Resource Indicator) ) . Beams in this list have not been reported in the (truncated) MR MAC CE.
[0099] ● Type 2 beam list (e.g., beam_leaving_list) : including Type 2 beam, e.g., indicated by the RS / beam index.
[0100] ● Type 3 beam list (e.g., beam_reported_list) : including Type 3 beam, e.g., indicated by the RS / beam index.
[0101] In Option 2: The UE maintains the following 2 beam lists to record different types of beams:
[0102] ● Type 1&2 beam list (e.g., beam_triggered_list) : including Type 1 beams and Type 2 beams, e.g., indicated by the RS / beam index. The Type 1 beams and Type 2 beams in this list may be marked with the following options:
[0103] ○ Option a: for a Type 2 beam in the list, it is marked with a flag / indicator, e.g., beamsTriggeredLeaving. Or for a Type 1 beam, it is marked with a flag / indicator, e.g., beamsTriggeredEntry.
[0104] ○ Option b: an indication can be included to mark a beam in the list to indicate the beam type, e.g., beamType {Type 1, Type 2} .
[0105] ● Type 3 beam list (e.g., beam_reported_list) : including Type 3 beams, e.g., indicated by the RS / beam index.
[0106] In Option 3: The UE maintains the following 2 beam lists to record different types of beams:
[0107] ● Type 1&3 beam list (e.g., beam_triggered_list) : including Type 1 beams and Type 3 beams, e.g., indicated by the RS / beam index. The Type 1 beams and Type 3 beams in this list may be marked with the following options:
[0108] ○ Option a: For a Type 3 beam, it is marked with a flag / indicator, e.g., beamsReported. Or for a Type 1 beam, it is marked with a flag / indicator, e.g. beamsTriggeredEntry.
[0109] ○ Option b: an indication can be included to mark a beam in the list to indicate the beam type, e.g., beamType {Type 1, Type 3} .
[0110] ● Type 2 beam list (e.g., beam_leaving_list) : including Type 2 beams, e.g., indicated by the RS / beam index.
[0111] In Option 4: The UE maintains the following 2 beam lists to record different types of beams:
[0112] ● Type 1 beam list (e.g., beam_triggering_list) : including Type 1 beams, e.g., indicated by the RS / beam index.
[0113] ● Type 2&3 beam list (e.g., beam_reported_list) : including Type 2 beams and Type 3 beams, e.g., indicated by the RS / beam index. The Type 2 beams and Type 3 beams in this list may be marked with the following options:
[0114] ○ Option a: For a Type 3 beam, it is marked with a flag / indicator, e.g., beamsReported. Or for a Type 2 beam, it is marked with a flag / indicator, e.g., beamsTriggeredLeaving.
[0115] ○ Option b: an indication can be included to mark a beam in the list to indicate the beam type, e.g., beamType {Type 2, Type 3} .
[0116] In Option 5: The UE maintains the following beam lists to record different types of beams:
[0117] ● A single Type 1&2&3 beam list (e.g., beam_triggered_list) : including Type 1 beams, Type 2 beams, and Type 3 beams, e.g., indicated by the RS / beam index. The Type 1 beams, Type 2 beams, and Type 3 beams in this list may be marked with the following options:
[0118] ○ Option a: For a Type 1 beam, it is marked with a flag / indicator, e.g., beamsTriggeredEntry. Or for a Type 2 beam, it is marked with a flag / indicator, e.g., beamsTriggeredLeaving. Or for a Type 3 beam, it is marked with another flag / indicator, e.g., beamsReported.
[0119] ○ Option b: an indication can be included to mark a beam in the list to indicate the beam type, e.g., beamType {Type 1, Type 2, Type 3} .
[0120] In Option 6: The UE maintains the following beam lists to record different types of beams:
[0121] ● A single beam list (e.g., beam_list) : including Type 1 beams, Type 2 beams, Type 3 beams, and Type 4 beams, e.g., indicated by the RS / beam index. The beams in this list may be marked with the following options:
[0122] ○ Option a: For a Type 1 beam, it is marked with a flag / indicator, e.g., beamsTriggeredEntry. Or for a Type 2 beam, it is marked with a flag / indicator, e.g., beamsTriggeredLeaving. Or for a Type 3 beam, it is marked with another flag / indicator, e.g., beamsReported. Or for a Type 4 beam, it is marked with another flag / indicator, e.g., beamsNonFullfilled.
[0123] ○ Option b: an indication can be included to mark a beam in the list to indicate the beam type, e.g., beamType {Type 1, Type 2, Type 3, Type 4} .
[0124] In some example implementations, the beam lists above can be maintained per triggering event, per report configuration, or per candidate cell. The beam lists may be associated with a corresponding ID, e.g., triggering event ID, report configuration ID, or candidate cell / configuration ID.
[0125] Further, in some example implementations, the UE can maintain a measurement result list (e.g., MR_list) . The measurement result list can be maintained per triggering event, per report configuration, or per candidate cell. The measurement result lists may be associated with a corresponding ID, e.g., triggering event ID, report configuration ID, or candidate cell / configuration ID.
[0126] In some example implementations, the measurement result list may include at least one of the following information items:
[0127] ● the report configuration ID;
[0128] ● the RS resource configuration ID;
[0129] ● the candidate cell ID, e.g., LTM candidate configuration index;
[0130] ● the RS / beam index of the candidate cell, e.g., SSBRI, CRI;
[0131] ● the L1 measurement results of the RS / beam, e.g., RSRP, RSRQ, SINR; or
[0132] ● the beam type of the RS / beam, e.g., Type 1 beam, Type 2 beam, Type 3 beam, Type 4 beam.
[0133] In some example implementations, for a specific beam, if the beam type changes, the UE may remove the beam from the old beam type list and add this beam into the new beam type list if appropriate.
[0134] Measurement Report Triggering -Embodiment 1
[0135] Based on option 1 above, an example of beam type change during measurements and measurement reporting of beams is shown in FIG. 6 and the L1 measurement report triggering procedure can be performed as below. The UE uses example Option 1 above to main three beam lists for Type 1, Type 2, and Type 3 beams, respectively.
[0136] For example, if the entering condition for the event (associated with a report configuration ID) is fulfilled for one or more applicable beams, the UE may perform at least one of the following:
[0137] ● Include a measurement report entry in the measurement result list, if the measurement result list (associated with the report configuration ID) does not include a measurement reporting entry.
[0138] ● Include index of each of the concerned beam (s) in the Type 1 beam list (602 of FIG. 6);
[0139] ● Initiate the L1 measurement report;
[0140] ● If the concerned beam (s) has been reported in the L1 measurement report, remove the concerned beam (s) from Type 1 beam list, and include the concerned beam (s) into the Type 3 beam list (604 of FIG. 6) .
[0141] ● Else if the concerned beam (s) has not been reported in the L1 measurement report:
[0142] ○ If the leaving condition is fulfilled for the beam (s) , remove the concerned beam (s) from Type 1 beam list (606 of FIG. 6) . Otherwise maintain it in the type 1 beam list (608 of FIG. 6) .
[0143] For example, if the leaving condition for the event (associated with a report configuration ID) is fulfilled for one or more applicable beams included in the Type 3 beam list, the UE may perform at least one of the following:
[0144] ● Remove the concerned beam (s) from the Type 3 beam list and Include the index of concerned beam (s) in the Type 2 beam list (610 of FIG. 6) ;
[0145] ● Initiate the L1 measurement report, e.g., if ReportOnLeave is configured;
[0146] ● If the concerned beam (s) has been reported in the L1 measurement report: remove the concerned beam (s) from Type 2 beam list (612 of FIG. 6) , otherwise maintain Type 2 (614 of FIG. 6) .
[0147] For example, if the Type 1 beam list or Type 2 beam list is not empty at are reporting time, the UE may perform at least one of the following:
[0148] ● Initiate the L1 measurement report;
[0149] ● If the beam (s) in Type 1 beam list has been reported in the L1 measurement report: remove the reported beam (s) from Type 1 beam list, and / or include the beam (s) into Type 3 beam list (604 of FIG. 6) ;
[0150] ● If the beam (s) in Type 2 beam list has been reported in the L1 measurement report: remove the reported beam (s) from Type 2 beam list (612 of FIG. 6) .
[0151] Measurement Report Triggering -Embodiment 2
[0152] Based on option 2 above, an example of beam type change during measurements and measurement reporting of beams and the L1 measurement report triggering procedure can be performed as below. The UE uses example Option 2 above to main two beam lists for Type 1&2 beams and Type 3 beams.
[0153] For example, the L1 measurement report triggering procedure can be performed as below.
[0154] If the entering condition for the event (associated with a report configuration ID) is fulfilled for one or more applicable beams, the UE may perform at least one of the following:
[0155] ● Include a measurement report entry in the measurement result list, if the measurement result list (associated with the report configuration ID) does not include a measurement reporting entry.
[0156] ● Include the index of concerned beam (s) in the Type 1&2 beam list;
[0157] ● Initiate the L1 measurement report;
[0158] ● If the concerned beam (s) has been reported in the L1 measurement report, remove the concerned beam (s) from Type 1&2 beam list, and include the concerned beam (s) into the Type 3 beam list. Else if the concerned beam (s) has not been reported in the L1 measurement report, and if the leaving condition is fulfilled for the beam (s) , remove the concerned beam (s) from Type 1&2 beam list.
[0159] For example, if the leaving condition for the event (associated with a report configuration ID) is fulfilled for one or more applicable beams included in the Type 3 beam list, the UE may perform at least one of the following:
[0160] ● Remove the concerned beam (s) from the Type 3 beam list;
[0161] ● Include the index of concerned beam (s) in the Type 1&2 beam list, and / or mark the concerned beam (s) as Type 2 beam;
[0162] ● Initiate the L1 measurement report, e.g., if ReportOnLeave is configured;
[0163] ● If the beam (s) marked as Type 2 beam has been reported in the L1 measurement report, remove the concerned beam (s) from Type 1&2 beam list.
[0164] In some example implementations, if the Type 1&2 beam list is not empty at a report time, the UE may perform at least one of the following:
[0165] ● Initiate the L1 measurement report;
[0166] ● If the beam (s) marked as Type 1 beam has been reported in the L1 measurement report, remove the reported beam (s) from Type 1&2 beam list, and / or include the beam (s) into Type 3 beam list;
[0167] ● If the beam (s) marked as Type 2 beam has been reported in the L1 measurement report, remove the reported beam (s) from Type 1&2 beam list.
[0168] Measurement Report Triggering -Other Embodiments
[0169] For option 2 / 3 / 4 / 5 / 6, the UE behavior is similarly derived. For a specific beam, upon the beam type change, the UE can remove the beam from the old beam type list and add this beam into the new beam type list. If the old beam type and the new beam type are recorded via separate beam lists. In addition, the UE may mark the beam type in the corresponding beam list, if the beam list includes beams with multiple / different beam types.
[0170] In some example embodiments, if the entering condition for the event (associated with a report configuration ID) is fulfilled for one or more applicable beams included in the Type 2 beam list, e.g., before the concerned beams have been reported in (truncated) MR MAC CE or before obtaining an UL grant for transmission of the MR (triggered by the fulfillment of the leaving condition of the event previously, e.g., for Type 2 beam) , the UE may perform at least one of the following:
[0171] ● Remove the concerned beam (s) from the Type 2 beam list;
[0172] ● In addition:
[0173] ○ Option a: Include the index of concerned beam (s) in the Type 1 beam list, initiate the L1 measurement report, and / or perform the similar operation as above (e.g., determine whether the concerned beam (s) has been reported in the L1 measurement report and perform the corresponding handling) ;
[0174] ○ Option b: Include the index of concerned beam (s) in the Type 3 beam list, not initiate the L1 measurement report, and / or cancel the previous triggered L1 measurement report (triggered by the fulfillment of the leaving condition of the event previously, e.g., for Type 2 beam) .
[0175] In some example embodiments, if the leaving condition for the event (associated with a report configuration ID) is fulfilled for one or more applicable beams included in the Type 1 beam list, e.g., before the concerned beams have been reported in (truncated) MR MAC CE or before obtaining a UL grant for transmission of the MR (triggered by the fulfillment of the entering condition of the event previously, e.g., for Type 1 beam) , the UE may perform at least one of the following:
[0176] ● Remove the concerned beam (s) from the Type 1 beam list; Not initiate the L1 measurement report; or
[0177] ● Cancel the previously triggered L1 measurement report (triggered by the fulfillment of the entering condition of the event previously, e.g., for Type 1 beam) .
[0178] Determination and Selection of Beams from Beam Lists to Include in L1 Measurement Report and / or to Generate L1 (Truncated) MR MAC CE
[0179] For L1 measurement reporting, the network can configure a maximum number of reported beams to the UE, to indicate how many beams other than the serving beam can be reported in an L1 measurement report MAC CE. This maximum number of reported beams can be configured in the L1 measurement reporting configuration and transmitted from the network to the UE via RRC message.
[0180] In addition, the UE may start to generate the MR MAC CE only when receiving the UL grant, and the UL grant may not fit the full size of the MR MAC CE. Then a truncated MR MAC CE may be used in this case to include only limited number of beams.
[0181] For an L1 reporting configuration, it is possible that the total number of Type 1, Type 2 and / or Type 3 beams are larger than the maximum number of reported beams configured by the network or to be included in the truncated MAC CE. In this case, the UE needs to decide which beam (s) to be reported in (truncated) MR MAC CE.
[0182] When receiving the UL grant, the UE determines the number of beams to be included in the (truncated) MR MAC CE, e.g., according to the maximum number of reported beams configured by the NW or the size of the UL grant. And then the UE can generate the MAC CE by selecting the determined number of beams from the corresponding beam type lists, e.g., as defined above. Among all selected beams, the UE uses the best quality beam as the reference beam as the first one included in the (truncated) MR MAC CE.
[0183] In some example implementation, the beams to report may be selected based on one of the example descending priorities defined below:
[0184] ● Option 1: newly triggered beam (s) (including beam (s) that satisfied the entering condition and beam (s) that satisfied the leaving condition, i.e., Type 1 and Type 2 beam) > already reported triggering beams (i.e., Type 3 beam) > non-satisfied beam (i.e., Type 4 beam)
[0185] ● Option 2: Type 1 beam > Type 2 beam > Type 3 beam > Type 4 beam
[0186] In some example implementations, in case that the current serving beam is not the triggering beam (e.g., for event LTM3 / 4 / 5) , if the current serving beam is to be included in the (truncated) MR MAC CE (e.g., the NW indicates to include the serving beam) , and the MAC CE cannot include all current serving beam and candidate beam (s) , the priority of beam selection / reporting can be considered as follows:
[0187] ● Option1: Type1 / 2 beam > Type 3 beam > Type 4 beam > serving beam
[0188] ● Option 2: Type1 / 2 beam > Type 3 beam > serving beam > Type 4 beam
[0189] ● Option 3: Type1 / 2 beam > serving beam > Type 3 beam > Type 4 beam
[0190] For the options above, in one example, Type 1 beam is prioritized than Type 2 beam. In another example, Type 1 beam and Type 2 beam have the same priority.
[0191] In some example implementations, in case that the current serving beam is the triggering beam (e.g., for event LTM2) , if the candidate beam is to be included in the (truncated) MR MAC CE (e.g., the NW indicates to include the candidate beam) , and the MAC CE cannot include all current serving beam and candidate beam (s) , the priority of beam selection / reporting can be considered as follows: serving beam > candidate beam.
[0192] Determination of Completion or Cancellation of Triggered L1 Measurement Report Procedure
[0193] In some example implementations, for a triggered L1 MR procedure of a specific event or report configuration (e.g., associated with a report configuration ID) , based on one or more of the following conditions:
[0194] ● if the beam list including the Type 1 beam (e.g., Type 1 beam list as defined above) is empty, or
[0195] ● if the beam list including the Type 1 beam and Type 2 beam (e.g., the Type 1 and Type 2 beam can be included in the same beam list or separate beam lists, as defined above) are empty, or
[0196] ● if the beam list including the Type 1 beam, Type 2 beam and Type 3 beam (e.g., the Type 1, Type 2 beam and Type 3 beam can be included in the same beam list or separate beam lists, as defined above) are empty, or
[0197] ● if L1 (truncated) MR MAC CE has been successfully transmitted to the NW, or
[0198] ● if all triggered beam (s) have been reported in the previous (truncated) MR MAC CE, even if there are some other beam information (e.g., for Type 3 and Type 4 beam) not included in the previous MAC CE, or
[0199] ● if a beam having met the entry condition firstly later meets the leaving condition before being reported yet or before obtaining the UL grant for transmission of the MR (triggered by the fulfillment of the entry condition of the event previously) , or
[0200] ● if a beam having met the leaving condition firstly later meets the entry condition before being reported yet or before getting the UL grant for transmission of the MR (triggered by the fulfillment of the leaving condition of the event previously) , the UE may perform at least one of the following:
[0201] ● consider the triggered L1 measurement report procedure is completed,
[0202] ● cancel the triggered L1 measurement report,
[0203] ● remove the corresponding measurement report entry (e.g., the entry with the report configuration ID) in the measurement result list. In some example, the corresponding measurement report entry includes the beam that has been reported.
[0204] In the above, the beam list being empty means that all beams for beam types associated with the beam list have been reported in the MR MAC CE (s) for a specific event or report configuration.
[0205] In some implementations, if not all triggered beams (e.g., Type 1 / 2 beam) can be included in one (truncated) MR MAC CE (e.g., the corresponding beam list is not empty) , upon the MAC CE being generated / transmitted, the UE may perform at least one of the following operations:
[0206] ● Option 1: consider the L1 MR procedure as completed, and / or cancel the triggered L1 MR procedure.
[0207] ● Option 2: consider the L1 MR procedure as pending, and / or cancel the triggered L1 MR procedure only when all triggered beams have been reported to the network (NW) . In some examples, the UE may send an SR (Scheduling Request) to the NW to request a new UL grant to accommodate the MAC CE to report the remaining triggered beams.
[0208] ● Option 3: initiate a measurement reporting procedure for the specific event associated with the report configuration ID. For example, the UE can initiate the measurement reporting procedure if the triggered beam list is not empty, even if no new beam (e.g., new Type 1 beam or Type 3 beam) meets the entering condition or leaving condition for the specific event associated with the report configuration ID.
[0209] ● Option 4: not initiate a measurement reporting procedure for the specific event associated with the report configuration ID, until a new beam meeting the triggering / entering condition or leaving condition. In other words, a measurement reporting procedure can be pending until a new beam meeting the triggering / entering condition or leaving condition. For example, the UE may not initiate the measurement report procedure for the specific event associated with the report configuration ID to report the remaining triggered beams until there is a new beam (which have not been reported and have not been recorded in the triggering beam list, e.g., new Type 1 beam) meeting the triggering / entering condition or there is a new reported beam (which have been reported, e.g., new Type 2 beam) meeting the leaving condition.
[0210] ● Option 5: include an indication into the MAC CE to indicate that there are remaining triggered beams that have not been included in this MAC CE. The UE may also indicate the number of the remaining triggered beams, and / or the beam types of the remaining triggered beams (e.g., Type 1 or type 2) .
[0211] The UE may perform any combination of options above, e.g., option 1+4, option 1+3, option 2+3, and the like.
[0212] Handling on MR Sent Counter
[0213] For event-based L1 measurement reporting, the network can configure a non-zero Report Interval (referred to as ReportInterval) and non-zero number of Reports (referred to as Report amount) to the UE. Once these parameters are configured, and an L1 measurement reporting procedure is triggered, the UE will periodically send the report according to the configured report interval (as periodicity) for the number of MRs (Report amount) . As described above, there may be multiple MR MAC CE or truncated MR MAC CE in a reporting period in order to report, for example, Type 1 and Type 2 beams in the beam lists for the event, particularly when one MR MAC CE cannot include all these beams to report. In each following reporting period, the UE can report the beams that still fulfilled the entering condition (e.g. Type 3 beam) , and may also report other types of beams (e.g., Type 1, Type 2, Type 4 beam) such as beams that just meet the entering condition or the leaving condition of the event. New beam meeting the entering condition or leaving condition (e.g., Type 1 or Type 2 beam) , may initiating a new measurement reporting procedure at the same or similar occasion when the periodical reporting occurs for the pervious MR (e.g., triggered by a beam previously meeting the entering condition) , the UE can include the new triggering beams (e.g., Type 1 or Type 2 beam) , and previously triggered beam (e.g., Type 3 beam) into the same MR MAC CE or truncated MR MAC CE for the existing periodic reporting for event based reporting.
[0214] For event triggered periodic reporting, the UE can maintain a counter (e.g., referred to as MR_sent_counter) to record the number of event triggered L1 measurement reports performed by UE if the triggering / entering condition is met for the corresponding event associated with a report configuration ID.
[0215] In some example implementations, the counter above can be maintained per event, per report configuration, per cell or per beam / RS. The counter may be associated with a corresponding ID, e.g., triggering event ID, report configuration ID, candidate cell / configuration ID, or beam / RS index.
[0216] If the counter is maintained per beam / RS, when two (or more) candidate beams fulfill the entering condition at different time occasions, two (or more) individual L1 measurement reporting procedures may be initiated. If ReportInterval and ReportAmount above are not set to 0, then the two (or more) parallel periodical reporting procedures may occur, which would increase the signaling overhead since the two (or more) parallel MR may include same or overlapping or redundant content.
[0217] An alternative example option is to maintain the counter per report configuration. When periodical reporting is configured, there is only one periodical reporting process. In order to let the network (NW) receive sufficient number of measurement reports for each triggering beams (which may fulfill the entering / leaving condition at different time occasions) , the UE may reset the counter every time when a new beam for the corresponding event associated with the report configuration ID meets the triggering / entering condition or leaving condition or there is remaining triggered beams in the corresponding beam list, which initiates the MR procedure. In other alternative implementations, the UE may not reset the counter in such cases.
[0218] In case that the counter is maintained per report configuration (e.g., for the specific event associated with a report configuration ID) , if the measurement reporting procedure is initiated since a new beam for the corresponding event associated with the report configuration ID meets the triggering / entering condition, since a new beam for the corresponding event associated with the report configuration ID meets the leaving condition, or since there is remaining triggered beams in the corresponding beam list (e.g., the corresponding beam list is not empty) , the UE may reset the counter, e.g., set the counter number to 0.
[0219] Whether To Include L1 Measurements for LTM Candidates in The MR Triggered by Event LTM2
[0220] Event LTM2 for event-based measurement report triggering refers to the beam of serving cell becoming worse than threshold. As such, for event LTM2, the UE only needs to evaluate the L1 measurement results of the serving beam. The serving beam is indicated / identified by the activated TCI state, or is quasi-collocated with beam of activated TCI state, depending on the configured RS type.
[0221] However, the LTM CSI resource configuration associated with the report configuration for event LTM2 may also include the RS (s) from LTM candidate cell (s) . The UE can also measure such RS (s) from LTM candidate cell (s) . So, it is possible to include the L1 measurements for LTM candidates in the triggered MR, in addition to the current serving beam information.
[0222] In some example implementation, the NW can indicate to the UE whether to only include the current beam information in the MR MAC CE or the MR can include measurements for LTM candidates, e.g., via an example indication allowReportAnyBeam, or introducing a new indication (e.g., allowReportCandidateBeam) configured in RRC. If the indication disables including the measurements for LTM candidates, the UE only include the current beam information in the MR MAC CE. If the indication enables inclusion of the measurements for LTM candidates, the UE can include measurements for the RS / beam (s) of LTM candidate cells which are indicated by the corresponding CSI resource configuration ID.
[0223] In some example implementations, if the UE is allowed to include measurements for LTM candidates in the MR MAC CE triggered by LTM2, the UE may ensure that the current serving beam information be included in the MR (if the MR cannot include all current serving beam and LTM candidate beams) . I. e., the current serving beam has higher priority than LTM candidate beams.
[0224] Conditional LTM
[0225] In some example implementations, conditional LTM (C-LTM) cell switch may be executed by the UE when one or more L1-based or L3-based LTM cell switch execution conditions are met.
[0226] For C-LTM, the NW (e.g., the source cell) can trigger early synchronization (e.g., PDCCH order based early RACH) to the UE to acquire TA of candidate cell. The source cell can provide the TA value of the candidate cell that the UE has performed UL synchronization with, e.g., via MAC CE (e.g., LTM Candidate Timing Advance Command MAC CE) . Upon receiving the TA value for the indicated candidate cell, the UE may store the TA value for the indicated candidate cell and start / restart the TA timer (TAT) associated with the indicated candidate cell. Upon TAT expiry, the UE removes the stored TA value of the corresponding candidate cell. The UE may receive and / or maintain TA values for multiple candidate cells before the C-LTM is executed.
[0227] In some example implementations, upon C-LTM cell switch execution, the UE may not stop the TAT for the target cell if the associated TAT is running, and starts the PTAG using the remaining time from the associated TAT. In addition, the UE may maintain the TA value and keep the corresponding TAT running for other candidate cells than the target candidate cell. However, the maximum number of TA values for candidate cells that the UE can maintain / store may be limited by the corresponding UE capability, e.g., cltm-EarlyTA-Indication.
[0228] After the UE switches to a new source cell, even if the number of maintained TA for candidate cells has reached the maximum number indicated by the UE, the new source cell may still want to trigger PDCCH order early RACH towards other candidate cells for TA acquisition, e.g., based on the newly received L1 measurement report. In this situation, the maintained TA for candidate cells needs to be managed to ensure the number of TA for candidate cells maintained by the UE does not exceed the UE capability. There are several example options / implementations to be considered:
[0229] For example, in Option 1, the NW indicates to the UE to cancel / remove a TA which has been previously acquired for a candidate cell, or to indicate which candidate cell’s TA may be cancelled / removed by the UE.
[0230] Particularly in Option 1a, an indication can be included in the PDCCH order to indicate to cancel a TA which has been previously acquired for a candidate cell, or to indicate which candidate cell’s TA to be cancelled (e.g., by indicating the LTM candidate ID) .
[0231] Particularly in Option 1b, an indication can be included in the TA MAC CE (e.g., LTM Candidate Timing Advance Command MAC CE) to indicate to cancel a TA which has been previously acquired for a candidate cell, or to indicate which candidate cell’s TA to be cancelled (e.g., by indicating the LTM candidate ID) .
[0232] In one example, the indication can be a default value of the TA (e.g., FFF) . For example, if the TA MAC CE includes a candidate cell ID (e.g., candidate config ID) and a default TA value (e.g., set to “FFF” ) , it means the TA of the indicated candidate cell is to be cancelled. When the UE receives the TA MAC CE, the UE may remove the stored TA of the indicated candidate cell and / or stop the TAT associated with the indicated candidate cell.
[0233] In another example, the indication can be a flag. For example, if the flag is set to 1, it means that the PDCCH order or the TA MAC CE is used to cancel a TA of a candidate cell; if the flag is set to 0, it means that the PDCCH order or the TA MAC CE is used to acquire or transfer a TA of a candidate cell; and vice versa.
[0234] For the indicated candidate cell, the UE may remove the maintained TA value and / or stop the corresponding TAT, e.g., when receiving the indication or when receiving the TA MAC CE.
[0235] For another example, in Option 2, the UE autonomously cancels / removes a maintained TA of a candidate cell when receiving a TA value for other candidate cell (e.g., whose TA has not been received previously) via the TA MAC CE, and / or stops the corresponding TAT of the candidate cell.
[0236] For yet another example, in Option 3 (acombination of option 1+2) , the NW indicates to the UE to cancel a TA which has been previously acquired for a candidate cell, e.g., via PDCCH order or MAC CE. Upon receiving the indication or the TA MAC CE, the UE determines which candidate cell’s TA to be cancelled / removed. The UE cancels / removes a maintained TA of the determined candidate cell and stops the corresponding TAT of the candidate cell.
[0237] For the example Option 2 or 3 above, the following implementations may be used to determine which candidate cell’s TA to be cancelled / removed:
[0238] ● Option a: the candidate cell whose remaining time for the TAT is the shortest;
[0239] ● Option b: the candidate cell whose TA received time is the earliest;
[0240] ● Option c: it can be up to UE implementation which candidate cell’s TA may be cancelled / removed.
[0241] For the NW side operation, the NW (e.g., the source cell) may perform similar operations as the UE to remove the TA value of the candidate cell and stop the corresponding TAT, e.g., when sending the new TA MAC CE. For example, the NW may cancel / remove the candidate cell’s TA, whose remaining time for the TAT is the shortest or whose TA received time is the earliest.
[0242] Fast Failure Recovery
[0243] For Inter-CU LTM, security key update may need to be performed upon inter-CU LTM cell switch, e.g. when the security change related ID is different between the target cell and the source cell. In such a case, the source cell may send NCC to the UE, e.g., via LTM cell switch command MAC CE. Upon receiving the NCC, the UE may store the received NCC value into a UE state variable. If a new NCC value is received, e.g., via LTM cell switch command MAC CE, the UE may replace the stored NCC value with the newly received one.
[0244] In some embodiments, upon receiving the NCC, the UE’s MAC layer may indicate the received NCC value to the upper layers (e.g., RRC layer) . Upon receiving the indicated NCC value from the lower layers (e.g., MAC layer) , the UE’s RRC layer may store the NCC value e.g. in a UE state variable if there is no entry in the corresponding UE state variable. Otherwise (i.e., if there is an entry in the corresponding UE state variable) , the UE’s RRC layer may replace the stored NCC value with the newly received one.
[0245] In some example implementations, upon inter-CU LTM failure (e.g., T304 expiry) , the UE may revert back to the UE configuration used in the source cell (e.g., source PCell) , and / or initiate the connection re-establishment procedure. For example, the UE may revert back to the security configuration (e.g., the security key, the NH value) used in the source cell.
[0246] In a connection re-establishment procedure, if the selected cell is an LTM candidate cell which belongs to different security set with the source cell (e.g., the security change related ID of the source cell and the selected target cell is different) , the UE may perform LTM cell switch procedure for the selected LTM candidate cell. The UE may derive or update the security key (e.g., KgNB) based on the current security key or the NH, using the stored NCC parameter.
[0247] LTM in NR-DC
[0248] For intra-CU / inter-CU MCG (Master Cell Group) LTM with SCG (Secondary Cell Group) configuration and intra-CU / inter-CU SCG LTM with MCG configuration, the candidate configuration may include both MCG-part and SCG-part configuration, i.e., an MN RRCReconfiguration message may include an embedded SN RRCReconfiguration message. In such a case, it is possible that the same MCG RRC transaction ID (included in the MN RRCReconfiguration message) is used for multiple LTM candidates’ MCG-part configurations belonging to the same MN. Similarly, the same SCG RRC transaction ID (included in the SN RRCReconfiguration message) may be used for multiple LTM candidates’ SCG-part configurations belonging to the same SN. Thus, it would be safer to use the LTM candidate configuration ID + MCG RRC transaction ID to help the target MN identify the correct MCG configuration to be applied. And the LTM candidate configuration ID + SCG RRC transaction ID can be used to assist the target SN to identify the correct SCG configuration to be applied.
[0249] Upon triggering the inter-CU MCG LTM cell switch execution, the source MN may send a cell switch notification message to the target candidate MN, which can include the indicated LTM candidate configuration ID. Thus, for a successful inter-CU MCG LTM cell switch execution, the target MN can identify the correct MCG configuration applied by the UE. However, if LTM based fast failure recovery is supported for inter-CU LTM failure, the UE can select inter-CU LTM candidate. If only RRC transaction ID is included in the RRCReconfigurationComplete message, the NW may use the wrong LTM candidate configuration other than the UE selected one. As such, the applied LTM candidate configuration ID should be included in the MCG RRCReconfigurationComplete message to help the target MN to identify the selected candidate MCG configuration. For example, for inter-CU MCG LTM without SCG configuration, the UE can include the applied LTM candidate configuration ID in an MCG RRCReconfigurationComplete message upon LTM cell switch execution. For another example, for intra-CU / inter-CU MCG LTM with SCG configuration, the UE can include the applied LTM candidate configuration ID in both MCG and SCG RRCReconfigurationComplete messages upon LTM cell switch execution.
[0250] For inter-CU SCG LTM with MCG configuration, the source SN may inform the indicated LTM candidate configuration ID to the MN and the target SN via the Cell Switch Notification message upon SCG LTM cell switch execution, so the MN and the target SN can correctly identify which MCG / SCG configuration is applied by the UE. For intra-CU SCG LTM with MCG configuration, the source SN can inform the MN about the indicated LTM candidate configuration ID upon SCG LTM cell switch execution, e.g., via the Cell Switch Notification message.
[0251] For intra-CU / inter-CU MCG LTM with SCG configuration, it is the MN who generates the LTM configuration (e.g., LTM-Config) and allocates the LTM candidate configuration ID for each LTM candidate. In order to let the involved NW node know the association between the LTM candidate configuration ID and an LTM candidate, for inter-CU MCG LTM with SCG configuration, the source MN can inform the association between the LTM candidate configuration ID with the candidate PCell / MCG to the candidate MN, and / or the candidate MN can notify the association between the LTM candidate configuration ID with the associated candidate PSCell / SCG to the (candidate) SN. For intra-CU MCG LTM with SCG configuration, the source MN can inform the association between the LTM candidate configuration ID with the associated candidate PSCell / SCG to the (candidate) SN.
[0252] For intra-CU / inter-CU SCG LTM with MCG configuration, it can be the MN or the source SN who allocates the LTM candidate configuration ID for each LTM candidate. In order to let the involved NW node know the association between the LTM candidate configuration ID and LTM candidate, the node (e.g., the source SN, or the MN) allocating the LTM candidate configuration ID needs to inform the association between the LTM candidate configuration ID and the candidate MCG / SCG configuration to other involved nodes (e.g., the candidate SN, the MN, or the source SN) .
[0253] Reference signaling (RS) Association between L1 RS and L3 RS
[0254] In order to support L3 measurement based LTM in a CU-DU split situation, the CU may transfer some assistance information to the DU to trigger an LTM cell switch and / or early synchronization for the UE. Regarding the assistance information, it may include the suggested RS of the candidate cell, and / or the L3 measurement results of the suggested candidate RS / cell, e.g., via indicating the SSB index or CSI-RS index. Currently, the L3 measurement configuration is generated by the CU, while the L1 measurement configuration and / or early synchronization (e.g., early RACH, TCI-state configuration) are generated by the DU. For the CSI-RS related configuration, the CU is responsible to assign the CSI-RS index for the L3 measurement configuration (e.g., csi-RS-Index IE included in CSI-RS-ResourceConfigMobility IE within MeasObjectNR IE) . The DU is responsible for assigning the CSI-RS index for the L1 measurement configuration and / or the LTM TCI-state configuration (e.g., csi-RS-Index IE included in CandidateTCI-State IE within LTM-TCI-Info IE) . However, the CU and the DU may assign different index for the same CSI-RS resource. If the CU just sends CSI-RS index to the DU to indicate the suggested RS for triggering LTM cell switch and / or early synchronization, the DU may find the wrong CSI-RS resource referred to this index, which is not the same CSI-RS resource as assigned by the CU. In order to ensure the CSI-RS index assigned by the CU points to the right CSI-RS resource, the CU and the DU may need to coordinate the detailed CSI-RS resource configuration.
[0255] Considering that there must be a L3 measurement for the candidate cell where L1 measurement is performed, the L1 measurement configuration (if provided) can be associated with an L3 measurement configuration. The NW can explicitly associate the L1 RS resource configuration with the L3 RS resource configuration, e.g., associating the L1 CSI-RS or SSB resource configuration with the L3 CSI-RS or SSB resource configuration.
[0256] For example, in Option 1, the CU can transfer the L3 CSI-RS resource configuration information (e.g., the CSI-RS index, the CSI-RS periodicity, subcarrier spacing, frequency domain, and / or time domain information) or L3 SSB resource configuration information (e.g., the SSB index, the SSB periodicity, subcarrier spacing, frequency domain information, and / or time domain information) to the DU. The L3 CSI-RS resource configuration information may be indicated via an CSI-RS-Resource-Mobility IE. The L3 SSB resource configuration information may be indicated via an ssb-ConfigMobility IE. In another example, the CU can transfer the L3 measurement object information (e.g., MeasObjectId) , cell ID (e.g., PCI) , and / or the associated L3 CSI-RS / SSB resource configuration information to the DU. The CU can transfer such information when initiating LTM preparation, e.g., via a UE context setup / modification request message.
[0257] If L1 measurement configuration is provided / configured by the DU, the DU can include the associated L3 CSI-RS or SSB resource index information into the L1 CSI-RS resource configuration. For example, the L1 CSI-RS resource configuration (e.g., NZP-CSI-RS-resource IE) can include an indication (e.g., associatedL3CSI-RS, associatedL3SSB) to indicate the associated L3 CSI-RS or SSB resource configuration. The indication may include the measurement object ID (e.g., MeasObjectId) , cell ID (e.g., PCI) , and / or L3 CSI-RS / SSB resource index (e.g., CSI-RS-Index, or SSB-Index) .
[0258] For L3 measurement based LTM, the CU can send the L3 CSI-RS / SSB resource configuration information, the corresponding CSI-RS / SSB index, and / or the L3 measurement for the corresponding CSI-RS / SSB index, to the DU via a F1 message, e.g., CU-DU mobility initiation request message, to trigger a cell switch command and / or early synchronization. Then the DU can find the corresponding L1 CSI-RS resource for the TCI-state, and then indicate the right TCI-state info to the UE via cell switch command MAC CE. The DU may also indicate the CSI-RS index for Contention-Free Random Access (CFRA) via cell switch command MAC CE.
[0259] In some embodiments, for inter-CU LTM, the source CU / node can transfer the L3 CSI-RS or SSB resource configuration information to the candidate CU / node. In another example, the source CU / node can transfer the L3 measurement object information (e.g., MeasObjectId) , cell ID (e.g., PCI) , and / or the associated L3 CSI-RS / SSB resource configuration information to the candidate CU / node. The source CU / node can transfer such information to the candidate CU / node when initiating LTM preparation, e.g., via handover request message. And the candidate CU / node can transfer such information to the candidate DU, e.g., via UE context setup / modification request message. The DU may include the associated L3 CSI-RS or SSB resource index information into the L1 CSI-RS resource configuration, as described above.
[0260] For another example, in Option 2, the DU can transfer the L1 CSI-RS resource configuration information (e.g., the CSI-RS index, the CSI-RS periodicity, subcarrier spacing, frequency domain, and / or time domain information) to the CU. The DU can transfer such information during LTM preparation procedure, e.g., via UE context setup / modification response message.
[0261] If L1 measurement configuration is provided / configured by the DU, the DU can transfer L1 CSI-RS resource configuration to the CU, e.g., including ltm-NZP-CSI-RS-ResourceToAddModList, ltm-NZP-CSI-RS-ResourceToReleaseList, ltm-NZP-CSI-RS-ResourceSetToAddModList, and / or ltm-NZP-CSI-RS-ResourceSetToReleaseList. According to the L1 CSI-RS resource configuration, the CU can include the associated L1 CSI-RS resource information into the L3 CSI-RS / SSB resource configuration. For example, the L3 CSI-RS resource configuration (e.g., CSI-RS-Resource-Mobility IE) or L3 SSB resource configuration (e.g., ssb-ConfigMobility IE) can include an indication (e.g. associatedL1CSI-RS) to indicate the associated L1 CSI-RS resource configuration. The indication may include the candidate cell / configuration ID (e.g. LTM-CandidateId) , and / or L1 CSI-RS resource index (e.g., NZP-CSI-RS-ResourceId) .
[0262] In some embodiments, for inter-CU LTM, the candidate CU / node can transfer the L1 CSI-RS resource configuration information to the source CU / node. The candidate CU / node can transfer such information during LTM preparation procedure, e.g., via handover request acknowledge message. Before transferring the L1 CSI-RS resource configuration information to the source CU / node, the candidate CU / node receives such information from the candidate DU, e.g., via UE context setup / modification response message. According to the received L1 CSI-RS resource configuration, the source CU / node may include the associated L1 CSI-RS resource information into the L3 CSI-RS / SSB resource configuration, as described above.
[0263] For the information transferred between the CU and the DU, or between the source CU / node and the candidate CU / node:
[0264] For one example, the information may be directly included in an Xn / X2 message or F1 message, e.g., it may be included as one information element in the Xn / X2 message or F1 message.
[0265] For another example, the information may be included in a RRC message, e.g., HandoverPreparationInformation, HandoverCommand, CG-ConfigInfo, CG-Config or other message. The RRC message may be included as one information element in an Xn / X2 message or F1 message.
[0266] In some other embodiments, a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods. The computer-readable medium may be referred to as non-transitory computer-readable media (CRM) that stores data for extended periods such as a flash drive or compact disk (CD) , or for short periods in the presence of power such as a memory device or random access memory (RAM) . In some embodiments, computer-readable instructions may be included in a software, which is embodied in one or more tangible, non-transitory, computer-readable media. Such non-transitory computer-readable media can be media associated with user-accessible mass storage as well as certain short-duration storage that are of non-transitory nature, such as internal mass storage or ROM. The software implementing various embodiments of the present disclosure can be stored in such devices and executed by a processor (or processing circuitry) . A computer-readable medium can include one or more memory devices or chips, according to particular needs. The software can cause the processor (including CPU, GPU, FPGA, and the like) to execute particular processes or particular parts of particular processes described herein, including defining data structures stored in RAM and modifying such data structures according to the processes defined by the software. In various embodiments in the present disclosure, the term “processor” may mean one processor that performs the defined functions, steps, or operations or a plurality of processors that collectively perform defined functions, steps, or operations, such that the execution of the individual defined functions may be divided amongst such plurality of processors.
[0267] Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present solution should be or are included in any single implementation thereof. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of the features and advantages, and similar language, throughout the specification may, but do not necessarily, refer to the same embodiment.
[0268] Furthermore, the described features, advantages and characteristics of the present solution may be combined in any suitable manner in one or more embodiments, for non-limiting examples, a portion from one or more embodiments may be combined with another portion of other embodiments. One of ordinary skill in the relevant art will recognize, in light of the description herein, that the present solution can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.
Claims
1.A method performed by a User Equipment (UE) in communication with a base station in a wireless communication network, the method comprising:performing Layer-1 (L1) measurement of a beam according to a measurement configuration provided by the base station;determining a beam type of the beam among a plurality of predefined beam types according to an evaluation of the L1 measurement of the beam against an entering condition or a leaving condition of an event; andtriggering a measurement report to report the L1 measurement of the beam to the base station, when the L1 measurement of the beam meets the entering condition or the leaving condition of the event.2.The method of claim 1, further comprising:updating a plurality of beam lists separately maintained by the UE according to the evaluation, each beam list of the plurality of beam lists identifying beams belonging to one or more beam types of the plurality of predefined beam types.3.The method of claim 1, further comprising, when the measurement report is triggered, performing at least one of the following:selecting one or more beams from a plurality of beam lists;including measurements for the one or more beams in the measurement report;transmitting the measurement report to the base station; andupdating the plurality of beam lists with respect to the one or more beams as a result of them being included in the measurement report.4.The method of claim 1, wherein the plurality of predefined beam types comprises:a first type (Type 1) for any beam just fulfilling the entering condition of the event;a second type (Type 2) for any beam having previously-reported fulfilment of the entering condition of the event and having just fulfilled the leaving condition of the event;a third type (Type 3) for any beam having previously-reported fulfilment of the entering condition of the event but having not fulfilled the leaving condition of the event; anda fourth type (Type-4) for any beam having not fulfilled the entering condition of the event.5.The method of claim 4, wherein determining the beam type of the beam among the plurality of predefined beam types comprises: modifying the beam from Type 1 to Type 4 when the beam was of Type 1 but has subsequently fulfilled the leaving condition of the event according to the L1 measurement without its previous fulfilment of the entering condition of the event being reported yet.6.The method of claim 4, wherein determining the beam type of the beam among the plurality of predefined beam types comprises: modifying the beam from Type-2 to Type-1 or Type 3 when the beam was of Type 2 but has subsequently fulfilled the entering condition of the event according to the L1 measurement without its previous fulfilment of the leaving condition of the event being reported yet.7.The method of claim 4, further comprising maintaining a plurality of beam lists, wherein the plurality of beam lists comprise:a first beam list for Type-1 beams, a second beam list for Type 2 beams, and a third beam list for Type 3 beams; ora first beam list for Type 1 beams and type 2 beams, and a second beam list for Type 3 beams; ora first beam list for Type 1 beams and Type 3 beams, and a second beam list for Type 2 beams; ora first beam list for Type 1 beams, and a second beam list for Type-2 beams and Type 3 beams; ora single beam list for Type 1 beams, Type 2 beams, and Type-3 beams; ora single beam list for Type 1 beams, Type 2 beams, Type-3 beams, and Type 4 beams.8.The method of claim 7, wherein beam types of beams within a beam list encompassing multiple beam types are identified by explicit or implicit beam type flags.9.The method of claim 7, wherein the plurality of beam lists comprise a first beam list for Type-1 beams, a second beam list for Type 2 beams, and a third beam list for Type 3 beams, and wherein the method further comprises updating the plurality of beam lists after the measurement report is triggered by performing at least one of the following:moving, from the first beam list to the third beam list, beams that have been reported;removing, from the first beam list, beams that are not reported;moving, from the third beam list to the second beam list, beams that subsequently fulfill the leaving condition of the event, followed by removing one or more of these beams from the second beam list after they are further reported; andremoving, from the second beam list, beams that have been reported.10.The method of claim 7, further comprising updating the plurality of beam lists by removing beams from the plurality of beam lists or moving beams from one beam list to another beam list according to status change of the beams with respect to their report status and their fulfilment of the entering conditions or the leaving conditions of the event.11.The method of claim 7, further comprising, when the measurement report is triggered, selecting one or more beams from the plurality of beam lists for reporting by performing at least one of the following:determining an upper bound number of beams that can be included in the measurement report; andselecting the one or more beams from the plurality of beam lists according to a predefined priority rule, limited by the upper bound number of beams.12.The method of claim 11, wherein determining the upper bound number of beams that can be included in the measurement report comprises at least one of the following:receiving a UL grant from the base station for the measurement report; anddetermining the upper bound number of beams that can be included in an MR MAC CE (measurement report MAC CE) or truncated MR MAC CE according to a maximum number of beams that can be accommodated in the MR MAC CE or the truncated MR MAC CE as limited by a size of the UL grant.13.The method of claim 11, wherein the predefined priority rule comprises selecting, from the plurality of beam lists until an upper bound number of beams are reached, in a descending priority order of:Type 1, Type 2, Type 3, Type 4;Type 1 / Type 2, Type 3, Type 4;Type 1 / Type 2, Type 3, Type 4, serving;Type 1 / Type 2, Type 3, serving, Type 4; orType 1 / Type 2, serving, Type 3, Type 4.14.The method of claim 7, wherein a triggered measurement report is considered complete or cancelled when:all beam lists including Type 1 beams are empty;all beam lists including Type 1 beams and Type 2 beams are empty;all beam lists including Type 1 beams and Type 2 beams and Type 3 beams are empty;an MR MAC CE or a truncated MR MAC CE for the triggered measurement report has been successfully transmitted;all beams of Type 1 and Type 2 having been included in an MR MAC CE or a truncated MR MAC CE for the measurement report previously transmitted;a beam having met the entering condition firstly then meets the leaving condition before receiving a UL grant for the triggered measurement report; ora beam having met the leaving condition firstly then meets the entering condition before receiving a UL grant for the triggered measurement report.15.The method of claim 14, further comprising:removing entries in the triggered measurement report from a measurement result list.16.The method of claim 7, wherein, when not all beams of Type 1 and Type 2 in the plurality of beam lists can be included in an MR MAC CE or a truncated MR MAC CE for the measurement report:initiating another measurement reporting procedure for the event; ornot initiating another measurement reporting procedure for the event until a new beam meets the entering condition or the leaving condition of the event; orincluding, in the MR MAC CE or the truncated MR MAC CE, an indication of remaining triggered beams that have not been included in the MR MAC CE or the truncated MR MAC CE.17.The method of claim 1, wherein:the measurement report is triggered as a periodic reporting procedure with a reporting periodicity and number of reports for the periodic reporting procedure; andthe method further comprises:maintaining a counter of reports for each report configuration associated with the event; andresetting the counter to zero when there is a new beam meeting the entering condition of the event.18.The method of claim 1, wherein the event is associated with qualities of current serving beams of the UE and the method further comprises:determining whether candidate beams for LTM (Layer-1 / Layer-2 Triggered Mobility) candidate cells are permitted in the measurement report; andwhen the candidate beams for LTM candidate cells are permitted in the measurement report, including the candidate beams in the measurement report under a condition that inclusion of the current serving beams in the measurement report takes priority over the candidate beams for LTM candidate cells.19.The method of claim 18, wherein whether the candidate beams for LTM candidate cells are to be included in the measurement report is indicated by the base station.20.The method of claim 19, wherein when the candidate beams for LTM candidate cells are not permitted in the measurement report, the method further comprises only including the current serving beams in the measurement report.21.A User Equipment (UE) in communication with a base station in a wireless communication network, the UE comprising a memory for storing instructions and at least one processor configured to execute the instructions to cause the UE to:perform Layer-1 (L1) measurement of a beam according to a measurement configuration provided by the base station;determine a beam type of the beam among a plurality of predefined beam types according to an evaluation of the L1 measurement of the beam against an entering condition or a leaving condition of an event; andtrigger a measurement report to report the L1 measurement of the beam to the base station, when the L1 measurement of the beam meets the entering condition or the leaving condition of the event.22.The UE of any one of claims 2 to 20, comprising at least one processor and a memory, wherein the at least one processor is configured to read instructions from the memory and implement the method recited in any one of claims 2 to 20.23.A non-transitory computer-readable storage medium for storing instructions, the instructions, when executed by at least one processor of a User Equipment (UE) in communication with a base station in a wireless communication network, are configured to execute the instructions to cause the UE to:perform Layer-1 (L1) measurement of a beam according to a measurement configuration provided by the base station;determine a beam type of the beam among a plurality of predefined beam types according to an evaluation of the L1 measurement of the beam against an entering condition or a leaving condition of an event; andtrigger a measurement report to report the L1 measurement of the beam to the base station, when the L1 measurement of the beam meets the entering condition or the leaving condition of the event.24.A non-transitory computer-readable medium for storing instructions, which, when executed by at least one processor of the UE of any one of claims 2 to 20, are configured to execute the instructions to cause the UE to carry out the method recited in any one of claims 2 to 20.
