Method and apparatus for artificial intelligence / machine learning assisted mobility for wireless communications

Abstract

Methods and apparatus are provided for artificial intelligence / machine learning assisted mobility for wireless communications, in which a method of a user equipment includes triggering a measurement report, and including in the measurement report a plurality of measurement results at a plurality of points in time for a cell, wherein the plurality of points in time comprises one or more of: (i) points in time configured by the network; and (ii) points in time within a time window configured by the network.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority and benefit to U.S. Provisional Patent Application No. 63 / 703,826, filed October 4, 2024, and U.S. Provisional Patent Application No. 63 / 864,934, filed August 15, 2025, each of which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more specifically to a method and apparatus for artificial intelligence / machine learning (AI / ML) assisted mobility in wireless communication systems. Background Technology

[0004] With the rapid growth in demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks are evolving into networks that communicate using Internet Protocol (IP) packets. This IP packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and on-demand communication services.

[0005] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN systems can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing next-generation (e.g., 5G) New Radio technologies. Therefore, changes to the current core of the 3GPP standards are currently being submitted and considered to facilitate their evolution and completion. Summary of the Invention

[0006] Methods, systems, and devices for artificial intelligence and machine learning (AI / ML)-assisted mobility in wireless communication systems are provided, enabling networks (NWs) to receive useful measurements to assist in handover decisions.

[0007] In various embodiments, a method for a user equipment (UE) in a wireless communication system includes triggering a measurement report and including in the measurement report multiple measurement results for a cell at multiple time points, wherein the multiple time points include one or more of the following: (i) time points configured by the NW; and (ii) time points within a time window configured by the NW. Attached Figure Description

[0008] Figure 1The accompanying drawings illustrate a wireless communication system according to an embodiment of the present invention.

[0009] Figure 2 This is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention.

[0010] Figure 3 This is a functional block diagram of a communication system according to an embodiment of the present invention.

[0011] Figure 4 This is an embodiment of the present invention. Figure 3 Functional block diagram of the program code.

[0012] Figure 5 It comes from 3GPP TS 38.331 V18.1.0 (2024-03) 3GPP. Figure 5 5.5.1-1: Reproduction of measurement reports.

[0013] Figure 6 This is an example diagram illustrating how an AI model for RRM prediction works according to an embodiment of the present invention.

[0014] Figure 7 This is an example diagram illustrating a UE (configured) according to an embodiment of the present invention to include multiple measurement results at multiple time points (e.g., for cells) in a measurement report, wherein the UE may be constrained (or restricted) to include measurement results within a time window.

[0015] Figure 8 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes transmitting to a network a message containing measurement results, a message not containing some measurement results and some cells, and distinguishing the message from a message triggered based on actual measurements.

[0016] Figure 9 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes transmitting a message containing measurement results to a network, predicting some measurement results of some cells, and distinguishing the message from a message triggered based on actual measurements.

[0017] Figure 10 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes transmitting a message containing measurement results to a network, including some actual measurement values, and distinguishing the message from a message triggered based on the actual measurements.

[0018] Figure 11This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes transmitting a message containing measurement results, some measurement values ​​containing multiple time points to a network, and distinguishing the message from a message triggered based on actual measurements.

[0019] Figure 12 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, the method including receiving a first configuration for reporting measurement values, and including measurement results for a plurality of time points for a cell in the measurement report, wherein the plurality of time points are within a time window including a reference time.

[0020] Figure 13 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes triggering a measurement report and including multiple measurement results for a cell at multiple time points in the measurement report, wherein the multiple time points include one or more of the following: (i) time points configured by the NW; and (ii) time points within a time window configured by the NW. Detailed Implementation

[0021] The invention described herein can be applied to, or implemented in, the exemplary wireless communication systems and apparatus described below. Furthermore, the invention is described primarily in the context of the 3GPP architecture reference model. However, it should be understood that, with the aid of the disclosed information, those skilled in the art can readily adapt various aspects of the invention to use and implement in 3GPP2 network architectures and other network architectures.

[0022] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice and data. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMAX®, 3GPP New Radio (NR), or some other modulation techniques.

[0023] Specifically, the exemplary wireless communication systems and apparatus described below may be designed to support one or more standards, such as those provided by the alliance known herein as the 3rd Generation Partnership Project (3GPP), including: [1] RP-240082, “Modified SID for AIML of Mobility in NR”; [2] 3GPP TR 38.843 V18.0.0 (2023-12) 3GPP; TSG RAN; Research on Artificial Intelligence (AI) / Machine Learning (ML) for the NR Air Interface (Revision 18); and [3] 3GPP TS 38.331 V18.1.0 (2024-03) 3GPP; TSG RAN; NR; Radio Resource Control (RRC) Protocol Specification (Revision 18). The full text of the standards and documents listed above is hereby expressly and entirely incorporated by reference.

[0024] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is illustrated. Access network 100 (AN) includes multiple antenna groups, one antenna group including 104 and 106, another antenna group including 108 and 110, and additional antenna groups including 112 and 114. Figure 1 In this diagram, only two antennas are shown for each antenna group; however, more or fewer antennas can be used for each antenna group. Access Terminal (AT) 116 communicates with antennas 112 and 114, which transmit information to AT 116 on forward link 120 and receive information from AT 116 on reverse link 118. AT 122 communicates with antennas 106 and 108, which transmit information to AT 122 on forward link 126 and receive information from AT 122 on reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 can communicate using different frequencies. For example, forward link 120 can use a different frequency than the frequency used by reverse link 118.

[0025] Each antenna group and / or the area in which they are designed to communicate is generally referred to as a sector of the access network. In an embodiment, each antenna group is designed to communicate with an access terminal in a sector of an area covered by access network 100.

[0026] In communications on forward links 120 and 126, the transmit antennas of access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links used for different access terminals 116 and 122. Furthermore, compared to access networks that transmit to all their access terminals via a single antenna, access networks that use beamforming to transmit to access terminals randomly distributed throughout their coverage area generally cause less interference to access terminals in adjacent cells.

[0027] An AN can be a fixed station or base station used for communication with a terminal, and may also be referred to as an access point, Node B, base station, enhanced base station, eNodeB, or other terminology. An AT can also be referred to as a user equipment (UE), wireless communication device, terminal, access terminal, or other terminology.

[0028] Figure 2 This is a simplified block diagram of an embodiment of the transmitter system 210 (also referred to as the access network) and receiver system 250 (also referred to as the access terminal (AT) or user equipment (UE)) in the MIMO system 200. At the transmitter system 210, service data of several data streams is provided from the data source 212 to the transmit (TX) data processor 214.

[0029] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, encodes, and interleaves the service data of the data streams based on a specific encoding scheme selected for each data stream to provide encoded data.

[0030] OFDM technology can be used to multiplex the coded data and pilot data of each data stream. The pilot data is typically a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data of each data stream are then modulated (e.g., symbol mapping) based on a specific modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for the data stream to provide modulation symbols. The data rate, encoding, and modulation for each data stream can be determined by instructions executed by processor 230. Memory 232 is coupled to processor 230.

[0031] The modulation symbols of all data streams are then provided to the TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then... T A modulation symbol stream is provided to N T Transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data stream and the antennas transmitting the symbols from it.

[0032] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission via a MIMO channel. Then, from N...T Antennas 224a to 224t transmit N from transmitters 222a to 222t. T A modulated signal.

[0033] At receiver system 250, via N R Each antenna 252a to 252r receives the transmitted modulated signal and provides the signal received from each antenna 252 to a corresponding receiver (RCVR) 254a to 254r. Each receiver 254 modulates (e.g., filters, amplifies, and down-converts) the corresponding received signal, digitizes the modulated signal to provide a sample, and further processes the sample to provide a corresponding "received" symbol stream.

[0034] The RX data processor 260 then uses specific receiver processing technology from N R Each receiver receives and processes N data. R Each received symbol stream provides N T Each detected symbol stream is then demodulated, deinterleaved, and decoded by the RX data processor 260 to recover the service data of the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and TX data processor 214 at the transmitter system 210.

[0035] Processor 270 periodically determines which precoding matrix to use (discussed below). Processor 270 formulates a reverse link message that includes a matrix index portion and a rank portion.

[0036] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives service data from several data streams from the data source 236), modulated by the modulator 280, regulated by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

[0037] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Processor 230 then determines which precoding matrix to use to determine beamforming weights and then processes the extracted message.

[0038] Memory 232 can be used to temporarily store some buffered / computational data from 240 or 242 via processor 230, some buffered data from 212, or some specific program code. Furthermore, memory 272 can be used to temporarily store some buffered / computational data from 260 via processor 270, some buffered data from 236, or some specific program code.

[0039] Turning Figure 3 This figure illustrates an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. Figure 3 As shown, this can be achieved using the communication device 300 in a wireless communication system. Figure 1 The UE (or AT) 116 and 122 are used, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sound via the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, deliver the received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306.

[0040] Figure 4 This is an embodiment of the present invention. Figure 3 A simplified block diagram of program code 312 is shown below. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 typically performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connections.

[0041] For LTE, LTE-A, or NR systems, layer 2, part 404 may include the Radio Link Control (RLC) layer and the Medium Access Control (MAC) layer. Layer 3, part 402 may include the Radio Resource Control (RRC) layer.

[0042] Any two or more of the following paragraphs, (sub)bullets, points, actions or claims described in each paragraph or section of the invention may be logically, reasonably and appropriately combined to form a particular method.

[0043] Any sentence, paragraph, (sub)bullet, point, action, or claim described in each of the following paragraphs or sections of the invention may be practiced independently and separately to form a particular method or apparatus. Dependencies such as “based on,” “more specifically,” and “example” in the following disclosure are merely possible embodiments that do not limit the particular method or apparatus.

[0044] In SID RP-240082 ([1] RP-240082, “Modified SID for AIML of Mobility in NR”), the objectives of AI / ML mobility are specified:

[0045] Beginning of quotation [1]

[0046] 3 Explanations

[0047] Existing L3 handover mechanisms trigger and execute handover based on reported historical measurements and / or measurement events; essentially, they are reactive schemes. This works well between macrocells when UE mobility is low for existing services. However, it can be problematic when UE mobility is high, between high-density microcells, or for both existing and future services (e.g., XR), where such reactive schemes can lead to more unintended events such as handover failures, radio link failures, ping-pong, throughput loss, or handovers too early / too late. Conditional handover was introduced in Rel-16 to improve handover robustness, and LTMHO was introduced in Rel-18 to reduce the downtime of frequent handovers between microcells. However, these two mechanisms are insufficient as they remain reactive schemes by design. On the other hand, AI / ML-based mechanisms have the potential to achieve proactive schemes.

[0048] In Rel-18, the SID known as FS_NR_AIML_air was extensively studied in physical layer center use cases, including spatial and temporal beam prediction. Temporal prediction within the serving cell primarily predicts the best or top K beams or beam pairs in the time domain to improve UE throughput. Predicting the best or top K beams or beam pairs within a set of beams by measuring a smaller set can help reduce RS signaling overhead, measurement workload, and UE power consumption. Much of the RAN1 work can be reused through extended L1 beam measurements from the serving cell to neighboring cells. Since L3 measurements are based on filtering of L1 measurements, studies of AI / MI for air can be utilized for mobility purposes; for example, temporal prediction can also be used to predict beam / cell degradation, enabling the avoidance of unintended events such as radio link failures or short-duration handovers.

[0049] Mobility enhancements were also studied in RAN3 of Rel-17, known as FS_NR_ENDC_data_collect, and are now specified in the Rel-18 WID NR_AIML_NGRAN-core. In these RAN3 projects, the research and specification work on mobility enhancements was based on information available on the network side, such as inter-cell handover and dwell time history, to predict the UE's trajectory in a single hop and thus predict potential candidates. In Rel-19, RAN3 will further study the UE's trajectory for multiple hops. The predicted UE trajectory contributes to the study of AI / ML mobility on the air interface.

[0050] Based on the progress made to date in RAN1 and RAN3 and the assumptions about UE trajectories, it is feasible to predict RRM measurements and / or events, and thus predict candidate target cells on the UE side. On the network side, new auxiliary information and statistical information based on measurement reports from the UE and / or neighboring nodes can also be used for intelligent prediction, if needed. If the network has access to some predictive information, proactive measures can be taken to improve handover and / or RRM performance, enabling better decision-making or avoiding unintended events.

[0051] 4 objectives

[0052] 4.1 SI or core WI or test WI target

[0053] This research will focus on mobility enhancements in the RRC_CONNECTED pattern on the air interface, following existing mobility frameworks, where handover decisions are always made on the network side. Mobility use cases focus on independent NR PCell changes. AI / ML models on the UE side and network side can be considered separately.

[0054] Research and evaluate the potential benefits and gains of AI / ML-assisted mobility in network-triggered L3-based handover, considering the following aspects:

[0055] • AI / ML-based RRM measurement and event prediction

[0056] • Cell-level measurement prediction, including intra-frequency and inter-frequency (UE-side and NW-side models) [RAN2]

[0057] • Inter-cell beam hierarchy measurement prediction for L3 mobility (UE-side and NW-side models) [RAN2]

[0058] • HO Fault / RLF Prediction (UE-side Model) [RAN2]

[0059] • Measurement event prediction (UE-side model) [RAN2]

[0060] • The need / benefits of researching any other UE-assisted information in the network-side model [RAN2]

[0061] • The evaluation of the benefits of AI / ML-assisted mobility should consider HO performance KPIs (e.g., ping-pong HO, HOF / RLF, dwell time, handover interruption, prediction accuracy, and measurement reduction) and complexity trade-offs [RAN2]

[0062] •Note: Simulation assumptions and methods can utilize TR 38.901, 38.843, and 36.839. A detailed discussion is left for RAN2.

[0063] • Potential AI mobility-specific enhancements should be based on the Rel19 AI / ML-Air Interface WID general framework (e.g., LCM, performance monitoring, etc.) [RAN2]

[0064] •Note: This will only be addressed after sufficient progress has been made in the Rel-19 AI / ML air interface WID.

[0065] • Potential canonical implications of AI / ML-assisted mobility [RAN2]

[0066] • Assess testability, interoperability, and the impact on RRM requirements and performance [RAN4]

[0067] End of quotation [1]

[0068] In TR 38.843 ([2] 3GPP TR 38.843 V18.0.0(2023-12) 3GPP; TSG RAN), the general framework and operation of LCM were studied:

[0069] Beginning of quotation [2]

[0070] 4. General AI / ML Frameworks

[0071] The purpose of this clause is to identify common notations and terminology for AI / ML related functions, procedures, and interfaces.

[0072] 4.1 Description of the AI / ML stage

[0073] This clause characterizes the definition phase and associated complexity of AI / ML-related algorithms, namely:

[0074] - Model generation, such as model training (including input / output, preprocessing / postprocessing, online / offline, if applicable), model validation, and model testing (if applicable).

[0075] - Inference operations, such as input / output, preprocessing / postprocessing (if applicable).

[0076] In addition, the processing of the datasets used for training, validation, testing, and inference is documented.

[0077] 4.2 Lifecycle Management

[0078] This clause characterizes the lifecycle management (LCM) of AI / ML models (e.g., model training, model deployment, model inference, model monitoring, and model updates) and the functionality of AI / ML.

[0079] The following aspects were examined in LCM, including the definition (if necessary) and necessity of components:

[0080] -Data collection

[0081] -Note: This also includes related auxiliary information, if applicable.

[0082] Model Training

[0083] - Functional / Model Identification

[0084] -Model delivery / transfer

[0085] -Model inference operation

[0086] - Functionality / model selection, activation, deactivation, switching, and rollback operations.

[0087] -Including: network decisions (initiated by the network or initiated by the UE and requested from the network), UE decisions (triggered by events configured by the network, with the UE reporting its decisions to the network, or autonomous decisions by the UE, with the UE reporting its decisions to the network or not).

[0088] - Functional / Model Monitoring

[0089] -Model Update

[0090] -UE capabilities

[0091] 4.2.1 LCM Characteristics

[0092] The LCM procedure is studied for cases where the AI / ML model has a model ID with associated information and / or for cases where a given functionality is provided by some AI / ML operations. Note: The applicability of functionality-based LCM and model ID-based LCM is a separate discussion.

[0093] From RAN1's ​​perspective, the AI / ML model identified by the model ID can be logical, and how it maps to a physical AI / ML model may depend on the implementation. When a distinction is necessary for discussion purposes, companies may use the term "logical AI / ML model" to refer to the model that is identified and assigned a model ID, and "physical AI / ML model" to refer to the actual implementation of such a model.

[0094] For the UE-side model and the UE portion of the dual-side model:

[0095] - Used for AI / ML functional identifiers

[0096] -The traditional 3GPP feature framework is considered the starting point.

[0097] -UE indicates one or more supported functionalities for a given subuse case.

[0098] -UE capability reports are considered a starting point.

[0099] - Used for AI / ML model identification

[0100] - The model is identified by the model ID at the network. The UE indicates the supported AI / ML models.

[0101] In function-based LCM, the network instructs the activation / deactivation / fallback / switching of AI / ML functionality via 3GPP signaling (e.g., RRC, MAC-CE, DCI). Model identification is not required at the network level, and the UE can perform model-level LCM. Further research is needed on whether the NW should have awareness / interaction with model-level LCM and how much awareness / interaction it should have. For functionality identification, one or more functions can exist within AI / ML-enabled features, where an AI / ML-enabled feature is one in which AI / ML can be used. Note: A UE can have one AI / ML model for functionality, or a UE can have multiple AI / ML models for functionality.

[0102] For the AI / ML functionality identifier and functionality-based LCM of the UE portion of the UE-side model and / or dual-side model, functionality refers to an AI / ML-enabled feature / FG enabled by configuration, where the configuration is supported based on conditions indicated by UE capabilities. Accordingly, the functionality-based LCM operates based on at least one configuration of the AI / ML-enabled feature / FG or a specific configuration of the AI / ML-enabled feature / FG.

[0103] Following the functional identification, the study examines the necessity and mechanism for UEs to report updates regarding applicable functionalities, where applicable functionalities can be a subset of all functionalities. UEs can report applicable functionalities.

[0104] In model ID-based LCM, the model is identified at the network, and the network / UE can activate / deactivate / select / switch various AI / ML models via the model ID.

[0105] For the AI / ML model identification and model ID-based LCM of the UE portion of the UE-side model and / or dual-side model, the model ID-based LCM operates based on the identified model, wherein the model may be associated with a specific configuration / condition, which is associated with the UE capability of the AI / ML enabled feature / FG and additional conditions (e.g., scene, site, and dataset) determined / identified between the UE side and NW side.

[0106] Following model identification, the necessity and mechanism for UE reporting updates regarding applicable UE-part / UE-side models were investigated, where applicable models can be a subset of all identified models. UEs can report the applicable models.

[0107] The study aims to investigate how to address the impact of the UE's internal conditions (such as memory, battery, and other hardware limitations) on functionality / model operation and the enabling of AI / ML features. Note: This does not exclude any existing solutions.

[0108] For LCMs based on functional / model IDs, once the functional / model is identified, the same or similar procedures can be used for its activation, deactivation, switching, rollback, and monitoring.

[0109] If needed, the model ID can be used in the functionality of LCM operations (defined in functionality-based LCM).

[0110] End of quotation [2]

[0111] In TS 38.331 ([3]3GPP TS 38.331 V18.1.0(2024-03)3GPP), the procedures for measurement are specified:

[0112] Beginning of quotation [3]

[0113] 5.5 Measurement

[0114] 5.5.1 Introduction

[0115] The network can configure RRC_CONNECTED UEs to perform measurements. The network can configure the UE to report measurements based on the measurement configuration, or perform conditional reconfiguration assessments based on conditional reconfiguration. The measurement configuration is provided via dedicated signaling, specifically using RRCReconfiguration or RRCResume.

[0116] The network can configure the UE to perform the following types of measurements:

[0117] -NR measurement;

[0118] -E-UTRA frequency RAT inter-measurement;

[0119] -RAT measurements of UTRA-FDD frequency;

[0120] - NR side link measurement of L2 U2N relay UE.

[0121] The network can be configured for the UE to report the following measurement information based on the SS / PBCH block:

[0122] - Measurement results for each SS / PBCH block;

[0123] - Measurement results per cell based on SS / PBCH blocks;

[0124] -SS / PBCH block index.

[0125] The network can be configured to allow the UE to report the following measurement information based on CSI-RS resources:

[0126] - Measurement results per CSI-RS resource;

[0127] - Measurement results per cell based on CSI-RS resources;

[0128] -CSI-RS Resource Measurement Identifier.

[0129] The measurement configuration includes the following parameters:

[0130] 1. Measurement Object: A list of objects that the UE should perform measurements on.

[0131] - For intra-frequency and inter-frequency measurements, the measurement object indicates the frequency / time location and subcarrier spacing of the reference signal to be measured. Associated with this measurement object, the network can configure lists of cell-specific offsets, lists of 'blacklisted' cells, and lists of 'whitelisted' cells. Blacklisted cells are not applicable in event assessments or measurement reports. Whitelisted cells are the only cells applicable in event assessments or measurement reports.

[0132] - The measObjectId corresponding to the MO of each serving cell is indicated by the servingCellMO in the serving cell configuration.

[0133] - For inter-RAT E-UTRA measurements, the measurement object is a single E-UTRA carrier frequency. Associated with this E-UTRA carrier frequency, the network can configure a list of cell-specific offsets and a list of 'blacklisted' cells. Blacklisted cells are not applicable in event assessments or measurement reports.

[0134] - For RAT-to-RAT UTRA-FDD measurements, the measurement object is a group of cells on a single UTRA-FDD carrier frequency.

[0135] 2. Report Configuration: A list of report configurations, where one or more report configurations can exist for each measurement object. Each measurement report configuration consists of the following items:

[0136] - Reporting Criteria: Criteria that trigger the UE to send measurement reports. This can be periodic or a description of a single event.

[0137] -RS type: RS (SS / PBCH block or CSI-RS) used by the UE for beam and cell measurement results.

[0138] - Report format: The UE includes in the measurement report the amount of each cell and each beam (e.g., RSRP) and other related information, such as the maximum number of cells and the maximum number of beams per cell to be reported.

[0139] Under conditions where reconfiguration is possible, each configuration consists of the following:

[0140] - Execution criteria: Criteria used by the UE for conditional reconfiguration execution.

[0141] -RS type: The RS (based on SS / PBCH block or CSI-RS) used by the UE to obtain beam and cell measurement results, used to evaluate the conditions for conditional reconfiguration.

[0142] 3. Measurement Identity: For measurement reports, a list of measurement identities, where each measurement identity links a measurement object to a report configuration. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same report configuration, and more than one report configuration to the same measurement object. Measurement identities also serve as references to the network in the measurement report that triggers the report. For conditional reconfiguration triggers, a measurement identity is linked to exactly one conditional reconfiguration trigger configuration. And at most two measurement identities can be linked to a conditional reconfiguration execution condition.

[0143] 4. Measurement Configuration: Measurement configuration defines the measurement filtering configuration used for all event assessments and related reporting, and for periodic reporting of the measurements. For NR measurements, the network can configure up to two measurement configurations by referencing the configuration to be used in the NR measurement object. In each configuration, different filtering coefficients can be configured for different measurement quantities, different RS types, and measurements per cell and per beam.

[0144] 5. Measurement gap: The period that the UE can use to perform measurements.

[0145] 6. Effective Measurement Window: The period that the UE can use to perform RAT inter-measurement.

[0146] The UE in RRC_CONNECTED state maintains a list of measurement objects, a list of report configurations, and a list of measurement identities according to the signaling and procedures described in this specification. The list of measurement objects may include NR measurement objects, CLI measurement objects, inter-RAT objects, and L2 U2N trunk objects. Similarly, the list of report configurations includes NR, inter-RAT, and L2 U2N trunk report configurations. Any measurement object can be linked to any report configuration of the same RAT type. Some report configurations may not be linked to measurement objects. Likewise, some measurement objects may not be linked to report configurations.

[0147] The measurement procedure distinguishes the following types of cells:

[0148] 1. NR Serving Cells - These are SpCells and one or more SCells.

[0149] 2. Listed Cells - These are the cells listed within the measurement object.

[0150] 3. Detected Cells - These are cells not listed in the measurement object but detected by the UE at the SSB frequency and subcarrier spacing indicated by the measurement object.

[0151] For NR measurement targets, the UE measures and reports on the serving cell / serving relay UE (for L2 U2N remote UEs), the listed cells, and / or the detected cells. For E-UTRA inter-RAT measurement targets, the UE measures and reports on the listed cells and the detected cells, and for RSSI and channel occupancy measurements, the UE measures and reports on the configured resources on the indicated frequencies. For UTRA-FDD inter-RAT measurement targets, the UE measures and reports on the listed cells. For CLI measurement targets, the UE measures and reports on the configured measurement resources (i.e., SRS resources and / or CLI-RSSI resources). For L2 U2N relay targets, the UE measures and reports on the serving NR cell and the discovered L2 U2N relay UEs.

[0152] Whenever a procedural specification other than that contained in sub-clause 5.5.2 indicates a field, it refers to a field included in VarMeasConfig (unless otherwise explicitly stated), that is, only the measurement configuration procedure covers direct UE actions related to the received measConfig.

[0153] In NR-DC, the UE can receive two independent measConfig:

[0154] - The measConfig associated with MCG, which is included in the RRCReconfiguration message received via SRB1; and

[0155] - The measConfig associated with SCG, which is included in the RRCReconfiguration message received via SRB3, or alternatively included in the RRCReconfiguration message embedded in the RRCReconfiguration message received via SRB1.

[0156] In this case, the UE maintains two independent VarMeasConfig and VarMeasReportList, one associated with each measConfig, and unless otherwise expressly stated, performs all procedures in Clause 5.5 independently for each measConfig and its associated VarMeasConfig and VarMeasReportList.

[0157] …

[0158] 5.5.3 Perform the measurement

[0159] 5.5.3.1 Overview

[0160] For RRC_CONNECTED UEs, cell measurement results should be derived by measuring one or more beams associated with each cell as configured by the network, as described in 5.5.3.3. For all cell measurement results (except RSSI) and CLI measurement results in RRC_CONNECTED, the UE applies Layer 3 filtering as specified in 5.5.3.2, and then uses the measurement results to evaluate reporting criteria, measurement reports, or trigger criteria for conditional reconfiguration execution. For cell measurements, the network can configure RSRP, RSRQ, SINR, RSCP, or EcN0 as trigger values. For CLI measurements, the network can configure SRS-RSRP or CLI-RSSI as trigger values. For cell and beam measurements, the reported quantity can be any combination of quantities unrelated to the trigger quantity (i.e., RSRP only; RSRQ only; SINR only; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR; RSCP only; EcN0 only; RSCP and EcN0), and for CLI measurements, the reported quantity can be SRS-RSRP or CLI-RSSI. For conditional reconfiguration execution, the network can configure up to two quantities, both using the same RS type. The UE does not apply Layer 3 filtering to derive CBR measurements as specified in 5.5.3.2. The UE does not apply Layer 3 filtering to derive Rx-Tx time difference measurements as specified in 5.5.3.2. The UE does not apply Layer 3 filtering to derive altitude measurements as specified in 5.5.3.2.

[0161] The network can also be configured for the UE to report measurement information per beam (which may be per-beam measurement results with corresponding beam identifiers or only beam identifiers), derived as described in 5.5.3.3a. If the beam measurement information is configured to be included in the measurement report, the UE applies Layer 3 beam filtering as specified in 5.5.3.2. On the other hand, the exact L1 filtering used to derive the beam measurement values ​​for the cell measurement results depends on the implementation scheme.

[0162] UE should:

[0163] 1> Whenever a UE has a measConfig, RSRP and RSRQ measurements are performed for each serving cell configured with servingCellMO as follows:

[0164] 2> If the reportConfig associated with at least one measId in the measIdList included in VarMeasConfig contains an rsType set to ssb and ssb-ConfigMobility is configured in the measObject indicated by servingCellMO:

[0165] 3> If the reportConfig associated with at least one measId in the measIdList included in VarMeasConfig contains reportQuantityRS-Indexes and maxNrofRS-IndexesToReport and contains rsType set to ssb:

[0166] 4> Based on the SS / PBCH block, derive the layer 3 filtering RSRP and RSRQ for each beam of the serving cell, as described in 5.5.3.3a;

[0167] 3> Derive serving cell measurement results based on SS / PBCH blocks, as described in 5.5.3.3;

[0168] 2> If the reportConfig associated with at least one measId in the measIdList included in VarMeasConfig contains an rsType set to csi-rs and CSI-RS-ResourceConfigMobility is configured in the measObject indicated by servingCellMO:

[0169] 3> If the reportConfig associated with at least one measId in the measIdList included in VarMeasConfig contains reportQuantityRS-Indexes and maxNrofRS-IndexesToReport and contains rsType set to csi-rs:

[0170] 4> Based on CSI-RS, derive the layer 3 filtering RSRP and RSRQ for each beam of the serving cell, as described in 5.5.3.3a;

[0171] 3> Derive serving cell measurement results based on CSI-RS, as described in 5.5.3.3;

[0172] 1> For each serving cell configured with servingCellMO, if the reportConfig associated with at least one measId in the measIdList included in VarMeasConfig contains SINR as a trigger quantity and / or reporting quantity:

[0173] 2> If reportConfig contains rsType set to ssb and ssb-ConfigMobility is configured in servingCellMO:

[0174] 3> If reportConfig contains reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0175] 4> Derive the layer 3 filtered SINR for each beam of the serving cell based on the SS / PBCH block, as described in 5.5.3.3a;

[0176] 3> Derive the serving cell SINR based on the SS / PBCH block, as described in 5.5.3.3;

[0177] 2> If reportConfig contains rsType set to csi-rs and CSI-RS-ResourceConfigMobility is configured in servingCellMO:

[0178] 3> If reportConfig contains reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0179] 4> Derivation of layer 3 filtered SINR for each beam of the serving cell based on CSI-RS, as described in 5.5.3.3a;

[0180] 3> Derive the serving cell SINR based on CSI-RS, as described in 5.5.3.3;

[0181] 1> For each measId included in the measIdList within VarMeasConfig:

[0182] …

[0183] 2> If the reportType used for the associated reportConfig is periodic or eventTriggered; or

[0184] 2> If the associated reportConfig's reportType is condTriggerConfig, then the measId is within MCGVarMeasConfig and is indicated in the condExecutionCond or condExecutionCondPSCell associated with the condReconfigId in MCG VarConditionalReconfig (for CHO, CPA, MN-initiated inter-SN CPC or subsequent CPAC in NR-DC); or

[0185] 2> If the associated reportConfig's reportType is condTriggerConfig, then the measId is within SCGVarMeasConfig and is indicated in the condExecutionCond associated with the condReconfigId in SCG VarConditionalReconfig (for CPC within SN or subsequent CPAC); or

[0186] 2> If the associated reportConfig's reportType is condTriggerConfig, then the measId is within SCGVarMeasConfig and is indicated in condExecutionCondSCG associated with condReconfigId in MCG VarConditionalReconfig (for SN-initiated inter-SN CPC or subsequent CPAC in NR-DC); or

[0187] 2> If the reportType of the associated reportConfig is condTriggerConfig, then the measId is in SCGVarMeasConfig and is indicated in the triggerConditionSN associated with the condReconfigurationId in VarConditionalReconfiguration, as specified in TS 36.331

[10] (for SN-initiated inter-SN CPC in EN-DC):

[0188] 3> If the measurement gap configuration is set, or

[0189] 3> If the UE does not require a measurement gap to perform the measurements involved;

[0190] 4> If s-MeasureConfig is not configured, or

[0191] 4> If s-MeasureConfig is set to ssb-RSRP and the NRSpCell RSRP based on the SS / PBCH block after layer 3 filtering is lower than ssb-RSRP, or

[0192] 4> If s-MeasureConfig is set to csi-RSRP and the NRSpCell RSRP based on CSI-RS is lower than csi-RSRP after layer 3 filtering:

[0193] 5> If measObject is associated with NR and rsType is set to csi-rs:

[0194] 6> If reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured for the associated reportConfig:

[0195] 7> The beam measurements of the layer 3 filter are derived from the CSI-RS only for each measurement indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a;

[0196] 6> Use the parameters from the associated measObject to derive cell measurement results based on the CSI-RS used for the trigger quantity and each measurement quantity indicated in reportQuantityCell, as described in 5.5.3.3;

[0197] 5> If measObject is associated with NR and rsType is set to ssb:

[0198] 6> If reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured for the associated reportConfig:

[0199] 7> The beam measurements of the layer 3 filter are derived only from the SS / PBCH block of each measurement indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a;

[0200] 6> Use the parameters from the associated measObject to derive cell measurement results based on the trigger amount and the SS / PBCH block indicated in reportQuantityCell for each measurement, as described in 5.5.3.3; ...

[0202] 4> If measRSSI-ReportConfig is configured in the associated reportConfig:

[0203] 5> Perform RSSI and channel occupancy measurements on the frequency configured for rmtc-Frequency in the associated measObject;

[0204] …

[0205] 5.5.3.2 Layer 3 Filtering

[0206] UE should:

[0207] 1> For each cell measurement, each beam measurement, and each sidelink measurement required in Clause 5.8.10, for each CLI measurement performed by the UE according to 5.5.3.1, for each candidate L2 U2N relay UE measurement according to 5.5.3.4, for evaluating detected NR sidelink U2N relay UEs according to 5.8.15.3, for evaluating SyncRef UEs according to 5.8.5 and 5.8.6, for evaluating NR sidelink U2U relay / remote UE threshold conditions according to 5.8.16.2 and 5.8.17.2, for evaluating NR sidelink U2U relay UE selection and reselection conditions according to 5.8.17.3, and for evaluating detected NR sidelink U2U relay UEs according to 5.8.17.4:

[0208] 2> Before using the measurement results for evaluation reporting criteria, measurement reporting, U2N / U2U trunk (reselection) evaluation, or SyncRef UE evaluation, filter them using the following formula:

[0209] F n = (1 - a) F n-1 + a M n

[0210] in

[0211] M n It is the latest measurement result received from the physical layer;

[0212] F n It is an updated, filtered measurement result used for evaluation reporting criteria, measurement reporting, U2N / U2U relay (re)selection evaluation, or SyncRef UE evaluation;

[0213] F n-1 These are the old, filtered measurement results, where F0 is set to M1 when the first measurement result from the physical layer is received; and for MeasObjectNR, a = 1 / 2 (ki / 4) , where k i It is the filterCoefficient of the measurement quantity corresponding to the i-th QuantityConfigNR in the quantityConfigNR-List, and i is indicated by the quantityConfigIndex in MeasObjectNR; for other measurements, a = 1 / 2 (k / 4) Where k is the filterCoefficient of the corresponding measurement received by quantityConfig; for UTRA-FDD, a=1 / 2(k / 4) , where k is the filterCoefficient of the corresponding measurement received by quantityConfigUTRA-FDD in QuantityConfig;

[0214] 2> Adjust the filter so that the time characteristics of the filter remain unchanged under different input rates. Observe filterCoefficient k assuming the sampling rate is equal to X ms; assuming non-DRX operation, the value of X is equal to an L1 measurement period within a frequency defined in TS 38.133

[14] and depends on the frequency range.

[0215] Note 1: If k is set to 0, layer 3 filtering is not applicable.

[0216] Note 2: The filtering is performed in the same domain as that used for evaluation reporting criteria, for measurement reporting, for U2N relay (re)selection evaluation, or for evaluating SyncRef UE, i.e., logarithmic filtering for logarithmic measurements.

[0217] Note 3: The filter input rate depends on the implementation scheme to meet the performance requirements set in TS 38.133

[14] . For further details on physical layer measurements, see TS 38.133

[14] .

[0218] Note 4: For CLI-RSSI measurements, whether filtering is reset after BWP handover depends on the UE implementation scheme.

[0219] Note 5: For SSB measurements when configuring multiple height-range-based ssb-ToMeasure, whether to reset the filtering when entering different height ranges depends on the UE implementation.

[0220] 5.5.3.3 Exporting Cell Measurement Results

[0221] The network can configure the UE in RRC_CONNECTED to export RSRP, RSRQ and SINR measurement results per cell associated with the NR measurement object based on parameters configured in measObject (e.g., the maximum number of beams to be averaged and the beam combining threshold) and parameters configured in reportConfig (rsType, SS / PBCH block or CSI-RS to be measured).

[0222] The network can configure the UE in RRC_IDLE or RRC_INACTIVE to export per-cell RSRP and RSRQ measurements to the NR carrier based on parameters configured in measIdleCarrierListNR within VarMeasIdleConfig for use in measurements performed according to 5.7.8.2a.

[0223] UE should:

[0224] 1> For each cell measurement derived based on SS / PBCH blocks:

[0225] 2> If nrofSS-BlocksToAverage is not configured in the associated measObject in RRC_CONNECTED or in the associated entry in measIdleCarrierListNR within VarMeasIdleConfig in RRC_IDLE / RRC_INACTIVE; or

[0226] 2> If absThreshSS-BlocksConsolidation is not configured in the associated measObject in RRC_CONNECTED or in the associated entry in measIdleCarrierListNR within VarMeasIdleConfig in RRC_IDLE / RRC_INACTIVE; or

[0227] 2> If the value of the highest beam measurement is less than or equal to absThreshSS-BlocksConsolidation:

[0228] 3> The values ​​of each cell measurement are derived as the highest beam measurement based on the SS / PBCH block, where each beam measurement is described in TS 38.215 [9];

[0229] 2> Otherwise:

[0230] 3> The measurements of each cell are derived based on the SS / PBCH block as a linear power scale average of the highest beam measurement value above absThreshSS-BlocksConsolidation, wherein the total number of average beams should not exceed nrofSS-BlocksToAverage, and wherein each beam measurement is described in TS 38.215[9];

[0231] 2> If it is in RRC_CONNECTED, then apply layer 3 cell filtering as described in 5.5.3.2;

[0232] 1> For each cell measurement that will be derived based on CSI-RS:

[0233] 2> When the CSI-RS resource is included in the csi-rs-CellMobility of the cell's physCellId in the associated measObject, the CSI-RS resource is considered suitable for exporting cell measurements;

[0234] 2> If nrofCSI-RS-ResourcesToAverage is not configured in the associated measObject; or

[0235] 2> If absThreshCSI-RS-Consolidation is not configured in the associated measObject; or

[0236] 2> If the value of the highest beam measurement is less than or equal to absThreshCSI-RS-Consolidation:

[0237] 3> Derive the value of each cell measurement as the highest beam measurement based on the applicable CSI-RS resources for the cell, where each beam measurement is described in TS 38.215 [9];

[0238] 2> Otherwise:

[0239] 3> Based on CSI-RS, derive the linear power scale average of each cell measurement as the highest beam measurement value above absThreshCSI-RS-Consolidation, where the total number of average beams should not exceed nrofCSI-RS-ResourcesToAverage;

[0240] 2> Apply layer 3 cell filtering, as described in 5.5.3.2.

[0241] …

[0242] 5.5.4 Measurement Report Trigger

[0243] 5.5.4.1 Overview

[0244] If AS security has been successfully activated, the UE should:

[0245] 1> For each measId included in the measIdList within VarMeasConfig:

[0246] 2> If the corresponding reportConfig includes a reportType set to eventTriggered or periodic:

[0247] 3> If the corresponding measObject involves NR:

[0248] …

[0249] 4> If eventA1 or eventA2 is configured in the corresponding reportConfig:

[0250] 5> Only the service area is considered applicable;

[0251] 4> If eventA3, eventA5, eventA3H1, eventA3H2, eventA5H1, or eventA5H2 are configured in the corresponding reportConfig:

[0252] 5> If a serving cell is associated with a measObjectNR and its neighbor is associated with another measObjectNR, then any serving cell associated with the other measObjectNR will also be considered a neighboring cell;

[0253] …

[0254] 4> If the corresponding reportConfig includes a reportType that is set to periodicity; or

[0255] 4> For measurement events other than eventA1, eventA2, eventD1, eventD2, eventX2, eventH1, or eventH2:

[0256] 5> If useAllowedCellList is set to true:

[0257] 6> When the cell in question is included in allowedCellsToAddModList defined for this measId in VarMeasConfig, any neighboring cells detected based on the parameters in the associated measObjectNR will be considered applicable;

[0258] 5> Otherwise:

[0259] 6> When the cell involved is not included in the excludedCellsToAddModList defined for this measId in VarMeasConfig, any neighboring cells detected based on the parameters in the associated measObjectNR will be considered applicable;

[0260] …

[0261] 2> If reportType is set to eventTriggered, and if the corresponding reportConfig does not include numberOfTriggeringCells, and if, after Layer 3 filtering during timeToTrigger defined for this event in VarMeasConfig, all measurements satisfy the entry conditions applicable to this event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) for one or more applicable cells, and VarMeasReportList does not include a measurement report entry for this measId (i.e., the first cell trigger event):

[0262] 3> Include the measurement report entry for this measId in the VarMeasReportList;

[0263] 3> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0264] 3> The cells involved are included in the cellsTriggeredList defined for this measId within VarMeasReportList;

[0265] 3> If useT312 is set to true in reportConfig for this event:

[0266] 4> If the T310 for the corresponding SpCell is running; and

[0267] 4> If T312 is not running for the corresponding SpCell:

[0268] 5> Start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR;

[0269] 3> Initiate the measurement reporting procedure, as specified in 5.5.5;

[0270] 2> If reportType is set to eventTriggered, and if the corresponding reportConfig does not include numberOfTriggeringCells, and if, after Layer 3 filtering during timeToTrigger defined for this event in VarMeasConfig, all measurements satisfy the entry conditions (subsequent cell triggering events) applicable to this event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) for one or more applicable cells not included in cellsTriggeredList:

[0271] 3> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0272] 3> The cells involved are included in the cellsTriggeredList defined for this measId within VarMeasReportList;

[0273] 3> If useT312 is set to true in reportConfig for this event:

[0274] 4> If the T310 for the corresponding SpCell is running; and

[0275] 4> If T312 is not running for the corresponding SpCell:

[0276] 5> Start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR;

[0277] 3> Initiate the measurement reporting procedure, as specified in 5.5.5;

[0278] 2> If reportType is set to eventTriggered, and if the corresponding reportConfig includes numberOfTriggeringCells, and if after Layer 3 filtering during timeToTrigger defined for this event in VarMeasConfig, all measurements satisfy the entry conditions applicable to this event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) for one or more applicable cells:

[0279] 3> If VarMeasReportList does not include a measurement report entry for this measId (first cell triggered event):

[0280] 4> Include the measurement report entry for this measId in the VarMeasReportList;

[0281] 3> If the number of cells in cellsTriggeredList is greater than or equal to numberOfTriggeringCells:

[0282] 4> The cells involved are included in the cellsTriggeredList defined for this measId within VarMeasReportList;

[0283] 3> Otherwise:

[0284] 4> The cells involved are included in the cellsTriggeredList defined for this measId within VarMeasReportList;

[0285] 4> If the number of cells in cellsTriggeredList is greater than or equal to numberOfTriggeringCells:

[0286] 5> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0287] 5> Initiate the measurement reporting procedure, as specified in 5.5.5;

[0288] 2> If reportType is set to eventTriggered, and if, after Layer 3 filtering during timeToTrigger defined for this event in VarMeasConfig, all measurements satisfy the leave conditions applicable to this event for one or more of the cells included in cellsTriggeredList defined for this measId in VarMeasReportList:

[0289] 3> Remove the involved cells from the cellsTriggeredList defined for this measId within VarMeasReportList;

[0290] 3> If reportOnLeave is set to true for the corresponding report configuration:

[0291] 4> If the corresponding reportConfig does not include numberOfTriggeringCells; or

[0292] 4> If the corresponding reportConfig includes numberOfTriggeringCells and a measurement report for at least one of the involved cells has been previously sent to the network:

[0293] 5> Initiate the measurement reporting procedure, as specified in 5.5.5;

[0294] 3> If the cellsTriggeredList defined for this measId in VarMeasReportList is empty:

[0295] 4> Remove the measurement report entry for this measId from the VarMeasReportList;

[0296] 4> If it is running, stop the periodic reporting timer used for this measId;

[0297] …

[0298] 2> If reportType is set to periodic and (first) measurement results are available:

[0299] 3> Include the measurement report entry for this measId in the VarMeasReportList;

[0300] 3> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0301] …

[0302] 3> Otherwise, if reportAmount exceeds 1:

[0303] 4> Immediately after the quantity to be reported becomes available for use in NR SpCell or for use in serving L2 U2N relay UE (if the UE is an L2 U2N remote UE), initiate a measurement reporting procedure as specified in 5.5.5;

[0304] 3> Otherwise (i.e., reportAmount equals 1):

[0305] 4> Immediately after the quantity to be reported becomes the strongest cell available to the NR SpCell and applicable cells, or the strongest L2 U2N relay UE available to the NR SpCell and applicable L2 U2N relay UE, a measurement reporting procedure is initiated as specified in 5.5.5; or immediately after the quantity to be reported becomes the strongest cell available to the serving L2 U2N relay UE and applicable cells, or the strongest L2 U2N relay UE available to the serving L2 U2N relay UE and applicable L2 U2N relay UE (if the UE is an L2 U2N remote UE), a measurement reporting procedure is initiated as specified in 5.5.5;

[0306] …

[0307] 2> After the periodic reporting timer used for this measId expires:

[0308] 3> Initiate the measurement reporting procedure, as specified in 5.5.5.

[0309] …

[0310] 5.5.4.2 Event A1 (Service becomes better than threshold)

[0311] UE should:

[0312] 1> The entry condition for this event is considered met when condition A1-1 specified below is satisfied;

[0313] 1> The exit condition for this event is considered met when the conditions A1-2 specified below are satisfied;

[0314] 1> For this measurement, consider the NR serving cell corresponding to the associated measObjectNR associated with this event.

[0315] Inequality A1-1 (Entry condition)

[0316] Ms - Hys > Thresh

[0317] Inequality A1-2 (leaving the condition)

[0318] Ms + Hys < Thresh

[0319] The variables in the formula are defined as follows:

[0320] Ms is the measurement result of the serving cell, without considering any offset.

[0321] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0322] Thresh is the threshold parameter for this event (i.e., a1-Threshold as defined in reportConfigNR for this event).

[0323] Ms is expressed in dBm in the case of RSRP, or in dB in the cases of RSRQ and RS-SINR.

[0324] Hys is expressed in dB.

[0325] Thresh is expressed in the same units as Ms.

[0326] 5.5.4.3 Event A2 (Service becomes worse than threshold)

[0327] UE should:

[0328] 1> The entry condition for this event is considered met when condition A2-1 specified below is satisfied;

[0329] 1> The exit condition for this event is considered met when condition A2-2 specified below is satisfied;

[0330] 1> For this measurement, consider the serving cell indicated by the measObjectNR associated with this event.

[0331] Note: If the SCell indicated by the measObjectNR associated with this event is undetectable, the UE should consider the lowest value in the range of measured values ​​for the Ms value as the SCell measurement value.

[0332] Inequality A2-1 (Entry condition)

[0333] Ms + Hys < Thresh

[0334] Inequality A2-2 (leaving the condition)

[0335] Ms - Hys > Thresh

[0336] The variables in the formula are defined as follows:

[0337] Ms is the measurement result of the serving cell, without considering any offset.

[0338] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0339] Thresh is the threshold parameter for this event (i.e., a2-Threshold as defined in reportConfigNR for this event).

[0340] Ms is expressed in dBm in the case of RSRP, or in dB in the cases of RSRQ and RS-SINR.

[0341] Hys is expressed in dB.

[0342] Thresh is expressed in the same units as Ms.

[0343] 5.5.4.4 Event A3 (Neighbor becomes better than SpCell by one offset)

[0344] UE should:

[0345] 1> The entry condition for this event is considered met when condition A3-1 specified below is satisfied;

[0346] 1> The exit condition for this event is considered met when condition A3-2 specified below is satisfied;

[0347] 1> Use SpCell for Mp, Ofp, and Ocp.

[0348] Note 1: The cell that triggers the event has a reference signal that may be indicated in a measObjectNR that is associated with this event, which may be different from the NR SpCellmeasObjectNR.

[0349] Inequality A3-1 (Entry condition)

[0350] Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + Off

[0351] Inequality A3-2 (leaving the condition)

[0352] Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off

[0353] The variables in the formula are defined as follows:

[0354] Mn is the measurement result of neighboring cells, without considering any offset.

[0355] Ofn is the measurement object-specific offset of the reference signal of the neighboring cell (i.e., the offset MO defined within the measObjectNR of the neighboring cell).

[0356] Ocn is the cell-specific offset of the neighboring cell (i.e., cellIndividualOffset defined in measObjectNR corresponding to the frequency of the neighboring cell, or cellIndividualOffset defined in reportConfigNR), and is set to zero if no neighboring cell is configured.

[0357] Mp is the measurement result from SpCell, without considering any offset.

[0358] Ofp is the measurement object-specific offset of SpCell (i.e., the offset MO defined within the measObjectNR of SpCell).

[0359] Ocp is the cell-specific offset of SpCell (i.e., corresponding to cellIndividualOffset defined within the measObjectNR of SpCell), and is set to zero if not configured for SpCell.

[0360] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0361] Off is the offset parameter for this event (i.e., a3-offset as defined in reportConfigNR for this event).

[0362] Mn and Mp are expressed in dBm in the case of RSRP, or in dB in the cases of RSRQ and RS-SINR.

[0363] Ofn, Ocn, Ofp, Ocp, Hys, and Off are expressed in dB.

[0364] Note 2: The definition of event A3 also applies to CondEvent A3.

[0365] 5.5.4.5 Event A4 (Neighbors become better than the threshold)

[0366] UE should:

[0367] 1> The entry condition for this event is considered met when condition A4-1 specified below is satisfied;

[0368] 1> The exit condition for this event is considered met when the condition A4-2 specified below is satisfied.

[0369] Inequality A4-1 (Entry Condition)

[0370] Mn + Ofn + Ocn - Hys > Thresh

[0371] Inequality A4-2 (leaving the condition)

[0372] Mn + Ofn + Ocn + Hys < Thresh

[0373] The variables in the formula are defined as follows:

[0374] Mn is the measurement result of a neighboring cell or serving PSCell for the CHO case with candidate SCG (i.e., when it is configured as a candidate PSCell for CondEvent A4 evaluation), without considering any offset.

[0375] Ofn is the measurement object-specific offset of the neighboring cell (i.e., the offset MO defined within the measObjectNR of the neighboring cell).

[0376] Ocn is the measurement object-specific offset of the neighboring cell (i.e., corresponding to the cellIndividualOffset defined in the measObjectNR of the neighboring cell, or the cellIndividualOffset defined in the reportConfigNR), and is set to zero if no neighboring cell is configured.

[0377] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0378] Thresh is the threshold parameter for this event (i.e., a4-Threshold as defined in reportConfigNR for this event).

[0379] Mn is expressed in dBm in the case of RSRP, or in dB in the cases of RSRQ and RS-SINR.

[0380] Ofn, Ocn, and Hys are expressed in dB.

[0381] Thresh is expressed in the same units as Mn.

[0382] Note: The definition of event A4 also applies to CondEvent A4.

[0383] 5.5.4.6 Event A5 (SpCell becomes worse than threshold1 and its neighbor becomes better than threshold2)

[0384] UE should:

[0385] 1> The entry conditions for this event are considered met when conditions A5-1 and A5-2 specified below are satisfied;

[0386] 1> The departure condition of this event is considered to be met when either condition A5-3 or condition A5-4 specified below is met, that is, at least one of the two conditions.

[0387] 1> Use SpCell for Mp.

[0388] Note 1: The parameters of the reference signal of the cell that triggered the event are indicated in the measObjectNR associated with the event, which may be different from the measObjectNR of the NR SpCell.

[0389] Inequality A5-1 (entering condition 1)

[0390] Mp + Hys < Thresh1

[0391] Inequality A5-2 (entering condition 2)

[0392] Mn + Ofn + Ocn - Hys > Thresh2

[0393] Inequality A5-3 (leaving condition 1)

[0394] Mp - Hys > Thresh1

[0395] Inequality A5-4 (leaving condition 2)

[0396] Mn + Ofn + Ocn + Hys < Thresh2

[0397] The variables in the formula are defined as follows:

[0398] Mp is the measurement result of NR SpCell, without considering any offset.

[0399] Mn is the measurement result of neighboring cells, without considering any offset.

[0400] Ofn is the measurement object-specific offset of the neighboring cell (i.e., the offset MO defined within the measObjectNR of the neighboring cell).

[0401] Ocn is the cell-specific offset of the neighboring cell (i.e., corresponding to the cellIndividualOffset defined in the measObjectNR of the neighboring cell, or the cellIndividualOffset defined in the reportConfigNR), and is set to zero if no neighboring cell is configured.

[0402] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0403] Thresh1 is the threshold parameter for this event (i.e., a5-Threshold1 as defined in reportConfigNR for this event).

[0404] Thresh2 is the threshold parameter for this event (i.e., a5-Threshold2 as defined in reportConfigNR for this event).

[0405] Mn and Mp are expressed in dBm in the case of RSRP, or in dB in the cases of RSRQ and RS-SINR.

[0406] Ofn, Ocn, and Hys are expressed in dB.

[0407] Thresh1 is expressed in the same units as Mp.

[0408] Thresh2 is expressed in the same units as Mn.

[0409] Note 2: The definition of event A5 also applies to CondEvent A5.

[0410] 5.5.4.7 Event A6 (Neighbors become offset better than SCell)

[0411] UE should:

[0412] 1> The entry condition for this event is considered met when condition A6-1 specified below is satisfied;

[0413] 1> The exit condition for this event is considered met when condition A6-2 specified below is satisfied;

[0414] 1> For this measurement, the (sub)cell corresponding to the measObjectNR associated with this event is considered the serving cell.

[0415] Note: The reference signals for neighbors and SCells are both indicated in the associated measObjectNR.

[0416] Inequality A6-1 (Entry Condition)

[0417] Mn + Ocn - Hys > Ms + Ocs + Off

[0418] Inequality A6-2 (leaving the condition)

[0419] Mn + Ocn + Hys < Ms + Ocs + Off

[0420] The variables in the formula are defined as follows:

[0421] Mn is the measurement result of neighboring cells, without considering any offset.

[0422] Ocn is the cell-specific offset of the neighboring cell (i.e., cellIndividualOffset as defined in the associated measObjectNR), and is set to zero if no neighboring cell is configured.

[0423] Ms is the measurement result of the serving cell, without considering any offset.

[0424] Ocs is the cell-specific offset of the serving cell (i.e., cellIndividualOffset as defined in the associated measObjectNR, or cellIndividualOffset as defined in reportConfigNR), and is set to zero if not configured for the serving cell.

[0425] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0426] Off is the offset parameter for this event (i.e., the a6-offset as defined in reportConfigNR for this event).

[0427] Mn and Ms are expressed in dBm in the case of RSRP, or in dB in the cases of RSRQ and RS-SINR.

[0428] Ocn, Ocs, Hys, and Off are expressed in dB.

[0429] 5.5.5 Measurement Report

[0430] 5.5.5.1 Overview

[0431] Figure 5 It comes from 3GPP TS 38.331 V18.1.0 (2024-03) 3GPP. Figure 5 5.5.1-1: Reproduction of measurement reports.

[0432] The purpose of this procedure is to transmit measurement results from the UE to the network. The UE will only initiate this procedure after AS security has been successfully activated.

[0433] For the measId that triggers the measurement report procedure, the UE should set the measResults in the MeasurementReport message as follows:

[0434] 1> Set the measId to the measurement identity that triggered the measurement report;

[0435] 1> For each serving cell configured with servingCellMO:

[0436] 2> If the reportConfig associated with the measId that triggered the measurement report includes rsType:

[0437] 3> If the serving cell measurement based on the rsType included in the reportConfig that triggered the measurement report is available:

[0438] 4> Set the measResultServingCell in measResultServingMOList to include the RSRP, RSRQ, and available SINR of the serving cell derived from the rsType included in the reportConfig that triggered the measurement report;

[0439] 2> Otherwise:

[0440] 3> If SSB-based serving cell measurements are available:

[0441] 4> Set the measResultServingCell in measResultServingMOList to include the RSRP, RSRQ and available SINR of the serving cell derived from SSB;

[0442] 3> Otherwise, if serving cell measurements based on CSI-RS are available:

[0443] 4> Set the measResultServingCell in measResultServingMOList to include the RSRP, RSRQ and available SINR of the serving cell derived from CSI-RS;

[0444] 1> Set the servCellId in measResultServingMOList to include each NR serving cell that is configured with servingCellMO (if it exists);

[0445] 1> If the reportConfig associated with the measId that triggered the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0446] 2> For each serving cell configured with servingCellMO, beam measurement information is included according to the associated reportConfig, as described in 5.5.5.2;

[0447] 1> If the reportConfig associated with the measId that triggered the measurement report includes reportAddNeighMeas:

[0448] 2> For each measObjectId referenced in the measIdList of servingCellMO, except for the measObjectId corresponding to the measId that triggered the measurement report:

[0449] 3> If the measObjectNR indicated by servingCellMO includes an RS resource configuration corresponding to the rsType indicated in reportConfig:

[0450] 4> If the RSRP measurement result is available for the cell corresponding to the involved measObjectNR, then the highest measured RSRP is used; otherwise, if the RSRQ measurement result is available for the cell corresponding to the involved measObjectNR, then the highest measured RSRQ is used; otherwise, the highest measured SINR is used. Based on the reportQuantityCell and rsType indicated in the reportConfig of the non-serving cell corresponding to this measObjectNR, the measResultBestNeighCell in measResultServingMOList is set to include physCellId and available measurement quantity.

[0451] 4> If the reportConfig associated with the measId that triggered the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0452] 5> For each best non-serving cell included in the measurement report:

[0453] 6> Include beam measurement information in the associated reportConfig, as described in 5.5.5.2;

[0454] 1> If the reportConfig associated with the measId that triggered the measurement report is set to eventTriggered and the eventID is set to eventA3, eventA4, eventA5, eventB1, eventB2, eventA3H1, eventA3H2, eventA4H1, eventA4H2, eventA5H1, or eventA5H2:

[0455] 2> If the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with MCG:

[0456] 3> Configure measResultServFreqListEUTRA-SCG to include entries for each E-UTRASCG service frequency using the following:

[0457] 4> Includes carrierFreq for E-UTRA service frequencies;

[0458] 4> Set measResultServingCell to include available measurements, and configure the UE to measure the available measurements via a measurement configuration associated with the SCG;

[0459] 4> If the reportConfig associated with the measId that triggered the measurement report includes reportAddNeighMeas:

[0460] 5> On the relevant service frequencies, based on RSRP, set measResultServFreqListEUTRA-SCG to include the best non-serving cell in measResultBestNeighCell;

[0461] 1> If the reportConfig associated with the measId that triggered the measurement report is set to eventTriggered and the eventID is set to eventA3, eventA4, eventA5, eventA3H1, eventA3H2, eventA4H1, eventA4H2, eventA5H1, or eventA5H2:

[0462] 2> If the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with MCG:

[0463] 3> Set measResultServFreqListNR-SCG to include the following items for each NR SCG serving cell that is configured with servingCellMO (if it exists):

[0464] 4> If the reportConfig associated with the measId that triggered the measurement report includes rsType:

[0465] 5> If the serving cell measurement based on the rsType included in the reportConfig that triggered the measurement report is available according to the measurement configuration associated with SCG:

[0466] 6> Set the measResultServingCell in measResultServFreqListNR-SCG to include the RSRP, RSRQ, and available SINR of the serving cell derived from the rsType included in the reportConfig that triggered the measurement report;

[0467] 4> Otherwise:

[0468] 5> If SSB-based serving cell measurements are available according to the measurement configuration associated with SCG:

[0469] 6> Set the measResultServingCell in measResultServFreqListNR-SCG to include the RSRP, RSRQ and available SINR of the serving cell derived from SSB;

[0470] 5> Otherwise, if the CSI-RS-based serving cell measurements are available according to the measurement configuration associated with the SCG:

[0471] 6> Set the measResultServingCell in measResultServFreqListNR-SCG to include the RSRP, RSRQ and available SINR of the serving cell derived from CSI-RS;

[0472] 4> If the results of the serving cell derived based on SSB are included:

[0473] 5> Include ssbFrequency in the value indicated by ssbFrequency included in the MeasObjectNR of the serving cell;

[0474] 4> If results of the serving cell derived from CSI-RS are included:

[0475] 5> Include refFreqCSI-RS into the value indicated by refFreqCSI-RS included in the MeasObjectNR of the serving cell;

[0476] 4> If the reportConfig associated with the measId that triggered the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0477] 5> For each serving cell configured with servingCellMO, beam measurement information is included according to the associated reportConfig, as described in 5.5.5.2, where availability is taken into account based on the measurement configuration associated with SCG;

[0478] 4> If the reportConfig associated with the measId that triggered the measurement report includes reportAddNeighMeas:

[0479] 5> If the measObjectNR indicated by servingCellMO includes an RS resource configuration corresponding to the rsType indicated in reportConfig:

[0480] 6> If the RSRP measurement result is available for the cell corresponding to the involved measObjectNR, the highest measured RSRP is used; otherwise, if the RSRQ measurement result is available for the cell corresponding to the involved measObjectNR, the highest measured RSRQ is used; otherwise, the highest measured SINR is used. Based on the reportQuantityCell and rsType indicated in the reportConfig of the non-serving cell corresponding to this measObjectNR, the measResultNeighCellListNR in measResultServFreqListNR-SCG is set to include an entry with physCellId and available measurement quantity, where availability is considered according to the measurement configuration associated with the SCG.

[0481] 7> If the reportConfig associated with the measId that triggered the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0482] 8> For each best non-serving cell included in the measurement report:

[0483] 9> Include beam measurement information according to the associated reportConfig, as described in 5.5.5.2, where availability is taken into account based on the measurement configuration associated with the SCG;

[0484] …

[0485] 1> If at least one applicable neighboring cell or candidate L2 U2N relay UE exists, report the following:

[0486] 2> If reportType is set to eventTriggered or periodic:

[0487] 3> If the measurement report involves candidate L2 U2N relay UEs:

[0488] …

[0489] 3> Otherwise:

[0490] 4> Set measResultNeighCells to include the best neighboring cells up to maxReportCells based on the following:

[0491] 5> If reportType is set to eventTriggered and eventId is not set to eventD1, eventD2, eventH1, or eventH2:

[0492] 6> Includes cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId;

[0493] 5> Otherwise:

[0494] 6> This includes applicable cells where new measurement results become available since the last periodic report or since the measurement was initiated or reset;

[0495] 5> For each cell included in measResultNeighCells, include physCellId;

[0496] 5> If reportType is set to eventTriggered or periodic:

[0497] 6> For each included cell, the measurement results of the layer 3 filtering are included according to the reportConfig used for this measId, and are sorted as follows:

[0498] 7> If the measObject associated with this measId involves NR:

[0499] 8> If the rsType in the associated reportConfig is set to ssb:

[0500] 9> Set the resultsSSB-Cell in measResult to include the quantity based on SS / PBCH blocks indicated in the reportQuantityCell in the relevant reportConfig, in descending order of sorting quantity, as specified in 5.5.5.3, i.e., first include the best cell;

[0501] 9> If reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, beam measurement information is included, as described in 5.5.5.2;

[0502] 8> Otherwise, if the rsType in the associated reportConfig is set to csi-rs:

[0503] 9> Set the resultsCSI-RS-Cell in measResult to include the CSI-RS-based quantities indicated in reportQuantityCell in the relevant reportConfig, in descending order of sorting quantity, as specified in 5.5.5.3, i.e., first including the best cell;

[0504] 9> If reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, beam measurement information is included, as described in 5.5.5.2;

[0505] …

[0506] 1> Increment the numberOfReportsSent defined in VarMeasReportList for this measId by 1;

[0507] 1> If it is running, stop the periodic report timer;

[0508] 1> If the numberOfReportsSent defined in VarMeasReportList for this measId is less than the reportAmount defined in the corresponding reportConfig for this measId:

[0509] 2> Start the periodic reporting timer with the value of reportInterval defined in the corresponding reportConfig for this measId;

[0510] The next citation [3]

[0511] -MeasurementReport

[0512] The MeasurementReport message is used to indicate measurement results.

[0513] Signaling radio bearers: SRB1, SRB3

[0514] RLC-SAP: AM

[0515] Logical Channel: DCCH

[0516] Direction: UE to network

[0517] MeasurementReport message

[0518] -- ASN1START

[0519] --TAG-MEASUREMENTREPORT-START

[0520] MeasurementReport ::= SEQUENCE {

[0521] criticalExtensions CHOICE {

[0522] measurementReport MeasurementReport-IEs,

[0523] criticalExtensionsFuture SEQUENCE {}

[0524] }

[0525] }

[0526] MeasurementReport-IEs ::= SEQUENCE {

[0527] measResults MeasResults

[0528] lateNonCriticalExtension OCTET STRING

[0529] OPTIONAL

[0530] nonCriticalExtension SEQUENCE{}

[0531] OPTIONAL

[0532] }

[0533] -- TAG-MEASUREMENTREPORT-STOP

[0534] -- ASN1STOP

[0535] …

[0536] -MeasConfig

[0537] IE MeasConfig specifies the measurements to be performed by the UE and covers the configuration of intra-frequency, inter-frequency, and RAT mobility as well as measurement gaps.

[0538] MeasConfig information element

[0539] -- ASN1START

[0540] -- TAG-MEASCONFIG-START

[0541] MeasConfig ::= SEQUENCE {

[0542] measObjectToRemoveList MeasObjectToRemoveList

[0543] OPTIONAL, -- Need N

[0544] measObjectToAddModList MeasObjectToAddModList

[0545] OPTIONAL, -- Need N

[0546] reportConfigToRemoveList ReportConfigToRemoveList

[0547] OPTIONAL, -- Need N

[0548] reportConfigToAddModList ReportConfigToAddModList

[0549] OPTIONAL, -- Need N

[0550] measIdToRemoveList MeasIdToRemoveList

[0551] OPTIONAL, -- Need N

[0552] measIdToAddModList MeasIdToAddModList

[0553] OPTIONAL, -- Need N

[0554] s-MeasureConfig CHOICE {

[0555] ssb-RSRP RSRP-Range,

[0556] csi-RSRP RSRP-Range

[0557] }

[0558] OPTIONAL, -- Need M

[0559] quantityConfig QuantityConfig

[0560] OPTIONAL, -- Need M

[0561] measGapConfig MeasGapConfig

[0562] OPTIONAL, -- Need M

[0563] measGapSharingConfig MeasGapSharingConfig

[0564] OPTIONAL, -- Need M

[0565] ..., [[

[0567] interFrequencyConfig-NoGap-r16 ENUMERATED {true}

[0568] OPTIONAL -- Need R

[0569] ]], [[

[0571] effectiveMeasWindowConfig-r18 SetupRelease {MeasWindowConfig-r18}

[0572] OPTIONAL -- Need M ]]

[0574] }

[0575] MeasObjectToRemoveList ::= SEQUENCE (SIZE (1..maxNrofObjectId))OF MeasObjectId

[0576] MeasIdToRemoveList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OFMeasId

[0577] ReportConfigToRemoveList ::= SEQUENCE (SIZE (1..maxReportConfigId))OF ReportConfigId

[0578] -- TAG-MEASCONFIG-STOP

[0579] -- ASN1STOP

[0580]

[0581] …

[0582] -MeasIdToAddModList

[0583] The IE MeasIdToAddModList contains a list of measurement identities to add or modify, and for each entry, a measId, an associated measObjectId, and an associated reportConfigId.

[0584] MeasIdToAddModList information element

[0585] -- ASN1START

[0586] -- TAG-MEASIDTOADDMODLIST-START

[0587] MeasIdToAddModList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OFMeasIdToAddMod

[0588] MeasIdToAddMod ::= SEQUENCE {

[0589] measId MeasId,

[0590] measObjectId MeasObjectId,

[0591] reportConfigId ReportConfigId

[0592] }

[0593] -- TAG-MEASIDTOADDMODLIST-STOP

[0594] -- ASN1STOP

[0595] …

[0596] -MeasObjectToAddModList

[0597] The IE MeasObjectToAddModList contains a list of measurement objects to be added or modified.

[0598] MeasObjectToAddModList Information Element

[0599] -- ASN1START

[0600] -- TAG-MEASOBJECTTOADDMODLIST-START

[0601] MeasObjectToAddModList ::= SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectToAddMod

[0602] MeasObjectToAddMod ::= SEQUENCE {

[0603] measObjectId MeasObjectId,

[0604] measObject CHOICE {

[0605] measObjectNR MeasObjectNR,

[0606] ...,

[0607] measObjectEUTRA MeasObjectEUTRA,

[0608] measObjectUTRA-FDD-r16 MeasObjectUTRA-FDD-r16,

[0609] measObjectNR-SL-r16 MeasObjectNR-SL-r16,

[0610] measObjectCLI-r16 MeasObjectCLI-r16,

[0611] measObjectRxTxDiff-r17 MeasObjectRxTxDiff-r17,

[0612] measObjectRelay-r17 SL-MeasObject-r16,

[0613] measObjectNR-SL-r18 MeasObjectNR-SL-r18

[0614] }

[0615] }

[0616] -- TAG-MEASOBJECTTOADDMODLIST-STOP

[0617] -- ASN1STOP

[0618] …

[0619] -MeasResults

[0620] IE MeasResults covers measurement results for same-frequency, different-frequency, and RAT-to-RAT mobility and measurement results of NR sidelink communication / discovery.

[0621] MeasResults information element

[0622] -- ASN1START

[0623] -- TAG-MEASRESULTS-START

[0624] MeasResults ::= SEQUENCE {

[0625] measId MeasId,

[0626] measResultServingMOList MeasResultServMOList,

[0627] measResultNeighCells CHOICE {

[0628] measResultListNR MeasResultListNR,

[0629] ...,

[0630] measResultListEUTRA MeasResultListEUTRA,

[0631] measResultListUTRA-FDD-r16 MeasResultListUTRA-FDD-r16,

[0632] sl-MeasResultsCandRelay-r17 OCTET STRING -- ContainsPC5 SL-MeasResultListRelay-r17

[0633] }

[0634] OPTIONAL

[0635] ...,

[0636] }

[0637] MeasResultServMOList ::= SEQUENCE (SIZE (1..maxNrofServingCells))OF MeasResultServMO

[0638] MeasResultServMO ::= SEQUENCE {

[0639] servCellId ServCellIndex,

[0640] measResultServingCell MeasResultNR,

[0641] measResultBestNeighCell MeasResultNR

[0642] OPTIONAL, ...

[0644] }

[0645] MeasResultListNR ::= SEQUENCE (SIZE (1..maxCellReport)) OFMeasResultNR

[0646] MeasResultNR ::= SEQUENCE {

[0647] physCellId PhysCellId

[0648] OPTIONAL,

[0649] measResult SEQUENCE {

[0650] cellResults SEQUENCE{

[0651] resultsSSB-Cell MeasQuantityResults

[0652] OPTIONAL,

[0653] resultsCSI-RS-Cell MeasQuantityResults

[0654] OPTIONAL

[0655] },

[0656] rsIndexResults SEQUENCE{

[0657] resultsSSB-Indexes ResultsPerSSB-IndexList

[0658] OPTIONAL,

[0659] resultsCSI-RS-Indexes ResultsPerCSI-RS-IndexList

[0660] OPTIONAL

[0661] }

[0662] OPTIONAL

[0663] },

[0664] ...,

[0665] }

[0666] …

[0667] MeasQuantityResults ::= SEQUENCE {

[0668] rsrp RSRP-Range

[0669] OPTIONAL,

[0670] rsrq RSRQ-Range

[0671] OPTIONAL,

[0672] sinr SINR-Range

[0673] OPTIONAL

[0674] }

[0675] …

[0676] ResultsPerSSB-IndexList::= SEQUENCE (SIZE (1..maxNrofIndexesToReport2))OF ResultsPerSSB-Index

[0677] ResultsPerSSB-Index ::= SEQUENCE {

[0678] ssb-Index SSB-Index,

[0679] ssb-Results MeasQuantityResults

[0680] OPTIONAL

[0681] }

[0682] ResultsPerCSI-RS-IndexList::= SEQUENCE (SIZE (1..maxNrofIndexesToReport2))OF ResultsPerCSI-RS-Index

[0683] ResultsPerCSI-RS-Index ::= SEQUENCE {

[0684] CSI-RS-Index

[0685] csi-RS-Results MeasQuantityResults

[0686] OPTIONAL

[0687] }

[0688] …

[0689] -- TAG-MEASRESULTS-STOP

[0690] -- ASN1STOP

[0691]

[0692]

[0693] …

[0694] -ReportConfigNR

[0695] IE ReportConfigNR specifies the criteria for triggering NR measurement report events, or CHO, CPA, or CPC events, or L2 U2N relay measurement report events. For events marked AN, where N equals 1, 2, etc., measurement report events and CHO, CPA, or CPC events are based on cell measurement results, which can be derived from SS / PBCH blocks or CSI-RS.

[0696] Event A1: Service becomes better than the absolute threshold;

[0697] Event A2: Service quality deteriorates below the absolute threshold;

[0698] Event A3: The neighbor becomes superior to PCell / PSCell by one offset;

[0699] Event A4: Neighbors become better than the absolute threshold;

[0700] Event A5: PCell / PSCell becomes worse than absolute threshold 1 and the adjacent Scell ​​becomes better than another absolute threshold 2;

[0701] Event A6: The neighbor becomes better than the SCell by one offset;

[0702] …

[0703] ReportConfigNR information element

[0704] -- ASN1START

[0705] -- TAG-REPORTCONFIGNR-START

[0706] ReportConfigNR ::= SEQUENCE {

[0707] reportType CHOICE {

[0708] periodical PeriodicalReportConfig,

[0709] eventTriggered EventTriggerConfig,

[0710] ...,

[0711] ReportCGI ReportCGI,

[0712] reportSFTD ReportSFTD-NR,

[0713] condTriggerConfig-r16 CondTriggerConfig-r16,

[0714] cli-Periodical-r16 CLI-PeriodicalReportConfig-r16,

[0715] cli-EventTriggered-r16 CLI-EventTriggerConfig-r16,

[0716] rxTxPeriodical-r17 RxTxPeriodical-r17,

[0717] reportOnScellActivation-r18 ReportOnScellActivation-r18

[0718] }

[0719] }

[0720] …

[0721] EventTriggerConfig ::= SEQUENCE {

[0722] eventId CHOICE {

[0723] eventA1 SEQUENCE {

[0724] a1-Threshold MeasTriggerQuantity,

[0725] reportOnLeave BOOLEAN,

[0726] hysteresis Hysteresis,

[0727] timeToTrigger TimeToTrigger

[0728] },

[0729] eventA2 SEQUENCE {

[0730] a2-Threshold MeasTriggerQuantity,

[0731] reportOnLeave BOOLEAN,

[0732] hysteresis Hysteresis,

[0733] timeToTrigger TimeToTrigger

[0734] },

[0735] eventA3 SEQUENCE {

[0736] a3-Offset MeasTriggerQuantityOffset,

[0737] reportOnLeave BOOLEAN,

[0738] hysteresis Hysteresis,

[0739] timeToTrigger TimeToTrigger,

[0740] useAllowedCellList BOOLEAN

[0741] },

[0742] eventA4 SEQUENCE {

[0743] a4-Threshold MeasTriggerQuantity,

[0744] reportOnLeave BOOLEAN,

[0745] hysteresis Hysteresis,

[0746] timeToTrigger TimeToTrigger,

[0747] useAllowedCellList BOOLEAN

[0748] },

[0749] eventA5 SEQUENCE {

[0750] a5-Threshold1 MeasTriggerQuantity,

[0751] a5-Threshold2 MeasTriggerQuantity,

[0752] reportOnLeave BOOLEAN,

[0753] hysteresis Hysteresis,

[0754] timeToTrigger TimeToTrigger,

[0755] useAllowedCellList BOOLEAN

[0756] },

[0757] eventA6 SEQUENCE {

[0758] a6-Offset MeasTriggerQuantityOffset,

[0759] reportOnLeaveBOOLEAN

[0760] Hysteresis

[0761] timeToTrigger TimeToTrigger,

[0762] useAllowedCellList BOOLEAN

[0763] },

[0764] ...,

[0765] …

[0766] },

[0767] …

[0768] }

[0769] …

[0770] CellIndividualOffsetList-r18 ::= SEQUENCE {

[0771] physCellId-r18 PhysCellId,

[0772] cellIndividualOffset-r18 Q-OffsetRangeList

[0773] }

[0774] -- TAG-REPORTCONFIGNR-STOP

[0775] -- ASN1STOP

[0776]

[0777] …

[0778] -ReportConfigToAddModList

[0779] The IE ReportConfigToAddModList contains a list of report configurations to add or modify.

[0780] ReportConfigToAddModList Information Element

[0781] -- ASN1START

[0782] -- TAG-REPORTCONFIGTOADDMODLIST-START

[0783] ReportConfigToAddModList ::= SEQUENCE (SIZE (1..maxReportConfigId))OF ReportConfigToAddMod

[0784] ReportConfigToAddMod ::= SEQUENCE {

[0785] reportConfigId ReportConfigId,

[0786] reportConfig CHOICE {

[0787] reportConfigNR ReportConfigNR,

[0788] ...,

[0789] reportConfigInterRAT ReportConfigInterRAT,

[0790] reportConfigNR-SL-r16 ReportConfigNR-SL-r16

[0791] }

[0792] }

[0793] -- TAG-REPORTCONFIGTOADDMODLIST-STOP

[0794] -- ASN1STOP

[0795] End of quotation [3]

[0796] The current Layer 3 (L3) handover mechanism relies on a customized measurement configuration, which uses the measurement object, reporting configuration, and measurement identity to configure the frequencies and cells for user equipment (UE) to measure. The UE first measures the configured frequencies and cells, and then reports the measurement results to the network (NW) when the measurement results meet the reporting trigger conditions. The NW can reconfigure the UE to perform handover based on the triggered event type and measurement results. This mechanism works well but is still limited to a reactive approach. In cases of lower coverage at higher frequencies, handover can occur more frequently, and therefore a more proactive approach can be sought. Currently, for AI / ML mobility enhancement, Radio Resource Management (RRM) measurement prediction, Radio Link Failure (RLF) / Handover Failure (HoF) prediction, and measurement event prediction have been investigated. For RRM measurement prediction, the UE can predict measurement results at future points in time or measurement results of another cell based on historical measurements and include the predicted measurement values ​​in the measurement report. For RLF / HoF prediction, the UE can predict the probability of an RLF / HoF occurring within a time window (or period) prior to its actual occurrence. For measurement event prediction, the UE can predict the probability of a measurement event (e.g., event A3) occurring (or triggering a report, fulfilling entry and / or exit conditions) within a time window (or period) and send a measurement report to the NW. With the help of AI / ML models, the UE can proactively respond to potential radio problems and enhance handover performance. Redundant measurements can also be reduced to save resources (e.g., measurement gaps, UE power).

[0797] In the latest NR Release 18 (e.g., [3] 3GPP TR 38.331 V18.0.0 (2023-12) 3GPP), the NW provides a measurement configuration, and the UE performs measurements and measurement reports based on the configuration. The measurement configuration includes the measurement object, the reporting configuration, and the measurement identity.

[0798] The measurement object configuration indicates the frequency and time of the cell to be measured. The report configuration indicates the conditions under which the UE sends measurement results to the NW. The measurement identity configuration associates the measurement object with the report configuration.

[0799] When at least one reporting configuration associated with the measurement identity exists and conditions such as measurement gaps or threshold limits are met, the UE measures the serving cell and the cell associated with the reporting configuration.

[0800] The UE can initiate a measurement reporting procedure and periodically send measurement reports to the NW, for example, after the periodic reporting timer expires, or when the (first) measurement results are available, or based on a triggered measurement event.

[0801] For measurement reports sent (or triggered) based on measurement events, the UE includes the measurement results of the involved cells in the measurement report when the measurement meets the conditions of the measurement event. The measurement results can be the latest results available (or derived from) during the time period from the initiation of the measurement report procedure to the transmission of the measurement report. The measurement results included in the measurement report meet the triggering conditions of the measurement event that sent (or triggered) the report. The measurement identity is included in the measurement report to notify the NW of the report details (e.g., which event triggered the measurement report).

[0802] In NR Release 19, several AI / ML enhancements to mobility have been studied as research projects. These enhancements include the prediction of measurement events. The UE can predict when a measurement event will occur within a time window (or period) (or trigger a report, meeting entry and / or exit conditions).

[0803] Prediction can be indirect, where the UE can predict the current and / or future measurement results of one or more cells based on the current and / or historical measurement results of one or more cells, and assess the conditions of the metering event (e.g., whether entry and / or exit conditions are met during timeToTrigger).

[0804] Prediction can be direct prediction, where the UE can predict the probability of a measurement event (e.g., event A3) occurring (or triggering a report, meeting entry and / or exit conditions) within a time window (or period) based on current and / or historical measurement results of one or more cells, without predicting the measurement at the expected trigger time of the event.

[0805] When a measurement event is predicted (or triggered), the UE can trigger and / or send a measurement report to the NW.

[0806] For measurement event prediction (e.g., direct prediction), when a measurement event is predicted (or triggered), the UE may not have corresponding measurement results at the expected event trigger time. For example, when the UE predicts that event A3 may occur within the next n time points, the UE may not have measurement results for the involved cells (e.g., serving cell, best non-serving cell, neighboring cells) at the next n time points. Therefore, the currently available measurement results for the involved cells may not yet meet the conditions of the predicted measurement event.

[0807] For measurement event prediction (e.g., direct prediction, indirect prediction), when a measurement event is predicted (or triggered), the UE may not have corresponding measurement results at the expected event trigger time in an unpredicted cell. For example, when the UE predicts that event A3 may occur, the UE may have measurement results for the involved cell and / or applicable neighboring cells (e.g., when the measurement event is indirectly predicted (or triggered)). However, the UE may not have measurement results for the best neighbor / neighboring cell for each frequency (e.g., on the involved serving frequency). Therefore, the UE may not be able to include measurement results for the best neighbor cell for each frequency (e.g., on the involved serving frequency) in measurement reports sent (or triggered) based on measurement event prediction, which is critical in multi-carrier handover scenarios.

[0808] The enhancement also includes predicting future measurement results and unmeasured frequency and / or cell / beam measurements. The UE and / or NW can predict cell / beam measurements based on actual measurements. Actual measurements can be measurements obtained and / or collected by the UE.

[0809] To address at least one or more of the problems described above, at least some of the methods described below may be considered.

[0810] The current procedures for measurement and / or measurement reporting (e.g., [3] 3GPP TR 38.331 V18.0.0(2023-12) 3GPP) can be enhanced or modified. The UE can perform measurement and / or RRM measurement prediction, and / or predict the occurrence of measurement events (or trigger reports, satisfying entry and / or exit conditions) according to the NW configuration. When (or in response to) a predicted (or triggered) measurement event, the UE can send an enhanced (or modified) measurement report to the NW. The enhanced (or modified) measurement report can be compared with the current (or legacy) measurement report (e.g., [3] 3GPP TR 38.331 V18.0.0(2023-12) 3GPP).

[0811] For example, a UE may trigger a first (type) measurement report (e.g., a current or legacy measurement report (e.g., [3] 3GPP TR 38.331 V18.0.0(2023-12) 3GPP) based on a first measurement event. A UE may trigger a first (type) measurement report (e.g., via actual UE measurement, without prediction, without performing or activating AI / ML functionality). A UE may trigger a second (type) measurement report (e.g., an enhanced or modified measurement report) based on a second measurement event. A UE may trigger a second (type) measurement report based on measurement event prediction and / or predicted measurement (e.g., by performing or activating AI / ML functionality). The first and second measurement events may be the same. The first and second measurement events may be different. The first and second measurement events may be distinguished based on whether AI / ML functionality and / or prediction are involved. For example, the first measurement event may be event A3. The second measurement event may be an event similar to A3, but with prediction.

[0812] Enhancements or modifications may include one or more of the concepts (or examples) described below, and / or may combine one or more of the concepts (or examples):

[0813] Concept A: At least some cell and / or measurement results are not included (or may not exist) in the measurement report. Reports (e.g., second (type) measurement reports) may be sent (or triggered) based on measurement event predictions. (The aforementioned at least some cell and / or measurement results are included (or mandated) in measurement reports sent (or triggered) based on actual measurements (e.g., first (type) measurement reports).

[0814] Concept B: The UE can predict at least some measurement results based on RRM measurement prediction and / or include said at least some measurement results in the measurement report. Reports (e.g., second (type) measurement reports) can be sent (or triggered) based on measurement event prediction.

[0815] For example, the ability / availability / applicability / configuration / activation of measurement event prediction and RRM prediction can be separate.

[0816] For example, the UE may provide (or indicate) a first capability for measurement event prediction (or related to measurement event prediction). The UE may provide (or indicate) a second capability for RRM prediction (or related to RRM prediction). The first and second capabilities may be different (e.g., considered as different capabilities). The first and second capabilities may be contained in the same message or signaling.

[0817] For example, the UE can provide (or indicate) a first availability for measurement event prediction (or related to measurement event prediction). The UE can provide (or indicate) a second availability for RRM prediction (or related to RRM prediction). The first availability and the second availability can be different (e.g., considered as different availability). The first availability and the second availability can be included in the same message or signaling.

[0818] For example, the UE may provide (or indicate) a first applicability for measurement event prediction (or related to measurement event prediction). The UE may provide (or indicate) a second applicability for RRM prediction (or related to RRM prediction). The first and second applicability may be different (e.g., considered as different applicability). The first and second applicability may be contained in the same message or signaling.

[0819] For example, the UE may receive a first configuration for measurement event prediction (or related to measurement event prediction). The UE may receive a second configuration for RRM prediction (or related to RRM prediction). The first and second configurations may be different (e.g., considered to be different configurations). The first and second configurations may be included in the same message or signaling (e.g., RRC reconfiguration).

[0820] For example, the UE may receive a first activation for measurement event prediction (or related to measurement event prediction). The UE may receive a second activation for RRM prediction (or related to RRM prediction). The first and second activations may be different (e.g., considered as different activations). The first and second activations may be contained in the same message or signaling (e.g., RRC reconfiguration).

[0821] The UE may include at least some of the measurement results based on its RRM measurement prediction capability / availability / applicability / configuration / activation status (e.g., performing RRM measurement prediction when (or in response to) its capability / availability / applicability / configuration / activation).

[0822] For example, the UE can determine whether to include at least some measurement results in a measurement report triggered by a measurement event prediction based on whether the UE has available (related or involved) measurement results, whether the UE has (or can) predict (related or involved) measurement results, and / or the state of the UE's RRM prediction.

[0823] For example, if (at least) the UE is capable of RRM prediction, the UE is configured with RRM prediction, the functionality of the UE's RRM prediction is available, and / or the functionality of the UE's RRM prediction is activated, then the UE can (determine) include at least some measurement results (e.g., based on RRM prediction).

[0824] For example, if (at least) the UE is unable to perform RRM prediction, the UE is not configured with RRM prediction, the functionality of the UE's RRM prediction is unavailable, and / or the functionality of the UE's RRM prediction is not activated, then the UE may (determine) not include the at least some of the measurement results (e.g., based on RRM prediction).

[0825] For example, a UE may include at least some of the measurement results regardless of its RRM prediction configuration / activation status (e.g., performing RRM measurement prediction even when (or in response to) it being inactive or not configured).

[0826] For example, the UE may include at least some of the measurement results (e.g., based on RRM prediction), regardless of whether the UE is capable of RRM prediction, whether the UE is configured with RRM prediction, whether the UE's RRM prediction functionality is available, and / or whether the UE's RRM prediction functionality is activated.

[0827] For example, even when the UE is not configured with RRM prediction and / or the UE's RRM prediction functionality is not activated, the UE may still include at least some of the measurement results (e.g., based on RRM prediction).

[0828] For example, NW can ensure that when (or in response to) the (related or involved) measurement event prediction is configured and / or activated, the (related or involved) RRM measurement prediction is configured and / or activated.

[0829] For example, measurement event prediction can be performed when (or in response to) (related or involved) RRM measurements are capable / available / applicable / configured / activated.

[0830] For example, the ability / availability / applicability / configuration / activation of measurement event prediction and RRM prediction can be correlated.

[0831] For example, the UE can provide (or indicate) the capability to predict measurement events and the capability to predict Relational Resource Registry (RRM). The indication can specify the UE's ability to perform both measurement event prediction and RRM prediction functionalities.

[0832] For example, the UE can provide (or indicate) the availability of measurement event prediction and RRM prediction (or an indication related to the availability of measurement event prediction and RRM prediction). The indication can suggest that the functionality of measurement event prediction and the functionality of RRM prediction (both) are available.

[0833] For example, the UE can provide (or indicate) the applicability of measurement event prediction and RRM prediction (or related to the applicability of measurement event prediction and RRM prediction). The indication can suggest that the functionality of measurement event prediction and RRM prediction (both) is applicable.

[0834] For example, the UE may receive configurations for measurement event prediction and RRM prediction (or related to measurement event prediction and RRM prediction). These configurations may be associated with measurement event prediction and RRM prediction.

[0835] For example, the UE may receive activation for measurement event prediction and RRM prediction (or related to measurement event prediction and RRM prediction). The activation may enable the functionality of measurement event prediction and RRM prediction.

[0836] Concept C: At least some of the most recent available measurements are included in the measurement report. Reports can be sent (or triggered) based on predicted measurement events, regardless of whether the measurements meet the conditions of the predicted event. For example, the most recent available measurements may not reflect the radio conditions at the predicted time of the predicted measurement event.

[0837] Concept D: At least some of the available measurement results from multiple time points are included in the measurement report. Reports can be sent (or triggered) based on measurement event predictions. The multiple time points may include past and / or future time points (e.g., starting from the last measurement report). The report can assist in decision-making on the NW side.

[0838] For the NW side model, RRM prediction is performed by the network to predict future measurements and make decisions based on current measurements collected from the UE. Figure 6 The figure illustrates an example of how an AI model used for RRM prediction works. As shown, the observation window (OW) can be a time window in which measurements are used as input to the AI ​​model, and the prediction window (PW) can be a time window in which the AI ​​model can predict the measurement results.

[0839] For AI models on the NW side, inputs for the AI ​​model must be collected from the UE. Based on the current mechanism, only the most recent measurement results can be included in the measurement report. Furthermore, the NW may need to configure intensive measurement reporting to collect measurement results from multiple time points.

[0840] To enhance measurement reporting for NW-side model prediction, the UE can be configured to report measurement results at multiple time points within a single measurement. However, if the UE decides to freely include measurement results, the measurement report may include results that are not helpful for NW-side prediction (e.g., measurements prior to OW may be outdated for prediction).

[0841] To at least address the aforementioned problem, when a UE is configured to include multiple measurement results at multiple time points (e.g., for a cell) in a measurement report, the UE can be constrained (or restricted) to include measurement results within a time window. Figure 7 An example is shown. For instance, the UE may include measurements taken at points within a time window before and at the time of a report and / or event triggering. The UE may not (is not allowed to) include measurements taken at points outside the time window.

[0842] At least one or more of the above concepts can be applied to (1) the serving cell, (2) the best neighboring cell for each frequency (e.g., on the serving frequency in question), and / or (3) neighboring cells. The concepts can be applied to multiple cells. Different concepts (or examples) can be applied to different cells.

[0843] To avoid confusion on the NW side, it may be necessary to distinguish between measurement reports sent (or triggered) based on predicted measurement events and actual measurements. For example, the UE may indicate to the NW (whether) to send (or trigger) a measurement report based on predicted measurement events. In another example, the UE may indicate to the NW (whether) to send (or trigger) a measurement report based on actual measurements. For instance, the UE may indicate to the NW (whether) to send (or trigger) a measurement report based on either predicted measurement events or actual measurements.

[0844] One or more of the methods (or examples) described below can be used to enhance or modify measurement reports. The information elements or fields described below can be included, in whole or in part, in measurement reports or measurement configurations. Cells, measurement configurations, and measurement reports can be associated with (only) primary cell groups (MCGs) or (only) secondary cell groups (SCGs).

[0845] One or more methods (or examples) described below can be used at least for concept A:

[0846] - For example, the UE can set the identifier / identity (ID) (e.g., servCellId) of the serving cell within an information element or field in a measurement report (e.g., measResultServingMOList) to include (only) some serving cells. The cell may be involved in a predicted (or triggered) measurement event.

[0847] - For example, the UE can set the measurement results (e.g., measResultServingCell) of the serving cell in the information elements or fields of the measurement report (e.g., measResultServingMOList) to include the reference signal received power (RSRP), reference signal received quality (RSRQ), and / or signal-to-interference-plus-noise ratio (SINR) of (only) some serving cells. The cell may involve predicted (or triggered) measurement events.

[0848] - For example, the cells included in (or involving) predicted (or triggered) measurement events in the measurement report can be cells predicted by the UE (or cells whose functionality is predicted based on measurement events).

[0849] - For example, a cell included in (or involving) a predicted (or triggered) measurement event in a measurement report could be a serving cell whose measurement results are better (or expected / predicted to be better) than its best neighbor cell (or neighboring cell) at the same frequency.

[0850] - For example, the UE may not set the serving cell ID (e.g., servCellId) in the information element or field of the measurement report (e.g., measResultServingMOList) so that some serving cells are not included. The cell may not be involved in the predicted (or triggered) measurement event.

[0851] - For example, the UE may not set the measurement results of the serving cell (e.g., measResultServingCell) in the information elements or fields of the measurement report (e.g., measResultServingMOList) so as not to include the RSRP, RSRQ and / or SINR of some serving cells.

[0852] - For example, a cell not included in the measurement report could be a serving cell whose measurement results are worse (or expected / predicted to be worse) than its best neighbor cell (or neighboring cell) at the same frequency.

[0853] - For example, the UE can set the ID of the best neighbor cell for a frequency (e.g., physCellId) within the information element or field of the measurement report (e.g., measResultServingMOList) to include (only) some of the best neighbor cells for that frequency.

[0854] - For example, the UE can set the measurement results of the best neighbor cell for a frequency (e.g., measResultBestNeighCell) in the information elements or fields of the measurement report (e.g., measResultServingMOList) to include the RSRP, RSRQ and / or SINR of (only) some of the best neighbor cells for the frequency.

[0855] - For example, the cell included in the measurement report could be the best neighbor cell at a frequency whose measurement results are better (or expected / predicted to be better) than those of a serving cell at the same frequency.

[0856] - For example, the UE may not set the ID of the best neighbor cell for a frequency (e.g., physCellId) in the information element or field of the measurement report (e.g., measResultServingMOList) so that some best neighbor cells for a frequency are not included.

[0857] - For example, the UE may not set the measurement results of the best neighbor cell for a frequency in the information elements or fields of the measurement report (e.g., measResultServingMOList) so that the RSRP, RSRQ and / or SINR of some best neighbor cells for a frequency are not included.

[0858] - For example, a cell not included in the measurement report could be the best neighbor cell at a frequency whose measurement results are worse than (or expected / predicted to be worse) than those of a serving cell at the same frequency.

[0859] - For example, the UE can set information elements or fields (e.g., measResultNeighCells) to include (only) some of the best neighboring cells up to a configured number (e.g., maxReportCells). Cells can involve predicted (or triggered) measurement events.

[0860] - For example, the UE can include the cell ID (e.g., physCellId) for some (neighboring) cells contained in information elements or fields (e.g., measResultNeighCells).

[0861] - For example, a UE can include measurement results for some included (neighboring) cells based on a report configuration (e.g., reportConfig) for this measurement identity (e.g., measId).

[0862] - For example, the UE can set the measurement results (e.g., resultsSSB-Cell, resultsCSI-RS-Cell) of (neighboring) cells in the information element or field (e.g., measResult) to include the amount (in descending order of sorting quantity) of the synchronization signal (SS) / physical broadcast channel (PBCH) block (i.e., SSB) (or channel state information reference signal (CSI-RS)) indicated in the information element or field (e.g., reportQuantityCell) in the relevant report configuration (e.g., reportConfig).

[0863] - For example, the cells included in (or involving) predicted (or triggered) measurement events in the measurement report can be cells predicted by the UE (or cells whose functionality is predicted based on measurement events).

[0864] - For example, the UE may not set information elements or fields (e.g., measResultNeighCells) so as not to include some best neighboring cells up to a configured number (e.g., maxReportCells). Cells may not involve predicted (or triggered) measurement events.

[0865] - For example, the UE may exclude the cell ID (e.g., physCellId) for some cells included in information elements or fields (e.g., measResultNeighCells).

[0866] - For example, a UE may exclude measurement results from the report configuration (e.g., reportConfig) based on the measurement identity (e.g., measId) for some included cells.

[0867] - For example, the UE may not set the measurement results of neighboring cells in the information element or field (e.g., measResult) (e.g., resultsSSB-Cell, resultsCSI-RS-Cell) so as not to include the quantity based on SS / PBCH block (or CSI-RS) indicated in the information element or field (e.g., reportQuantityCell) in the relevant report configuration (e.g., reportConfig) (in descending order of sorting quantity).

[0868] - For example, the measurement report could be a first (type) measurement report.

[0869] - For example, the measurement report can be a second (type) measurement report.

[0870] - For example, the measurement report may not be the first (type) measurement report.

[0871] - For example, the measurement report may not be a second (type) measurement report.

[0872] One or more methods (or examples) described below can be used at least for Concept B:

[0873] - For example, the UE can obtain predicted measurement results based on another AI / ML functionality (e.g., RRM measurement prediction, measurement event prediction, RLF / HoF prediction).

[0874] - For example, when (or in response to) an AI / ML function being capable / available / applicable / configured / activated, or when (or in response to) an AI / ML function being incapable / unavailable / inapplicable / unconfigured / unactivated, the UE may execute (or trigger) another AI / ML function (e.g., RRM measurement prediction, measurement event prediction, RLF / HoF prediction) to obtain a predicted measurement result.

[0875] - For example, when (or in response to) an event entry condition (or exit condition) is (predicted to be) met, when (or in response to) the UE setting or including a measurement result, when (or in response to) no measurement result (for a certain point in time) is available, or when (or in response to) the UE predicting that a measurement event will occur (or triggering a report), the UE may perform (or trigger) AI / ML functionality (e.g., RRM measurement prediction, measurement event prediction, RLF / HoF prediction).

[0876] - For example, when (or in response to) the UE performing or triggering AI / ML functionality (e.g., RRM measurement prediction, measurement event prediction, RLF / HoF prediction), the UE can obtain (future) measurement results for cells included in the measurement report (or involving predicted (or triggered) measurement events, such as serving cells, neighboring cells), cells configured by NW (e.g., in RRCReconfiguration messages), and / or cells that can assist L3 mobility decisions (e.g., applicable neighboring cells, best neighboring cells for each frequency).

[0877] - For example, the UE can set the measurement results of the serving cell (e.g., measResultServingCell) in the information elements or fields of the measurement report (e.g., measResultServingMOList) to include the RSRP, RSRQ and / or SINR of some serving cells.

[0878] - For example, the UE can set the measurement results of the best neighbor cell for a frequency (e.g., measResultBestNeighCell) in the information element or field of the measurement report (e.g., measResultServingMOList) to include the RSRP, RSRQ and / or SINR of some best neighbor cells for a frequency.

[0879] - For example, a UE can include measurement results for some included (neighboring) cells based on a report configuration (e.g., reportConfig) for this measurement identity (e.g., measId).

[0880] - For example, the UE can set the measurement results (e.g., resultsSSB-Cell, resultsCSI-RS-Cell) of (neighboring) cells in the information element or field (e.g., measResult) to include the quantity (in descending order of sorting quantity) based on the SS / PBCH block (or CSI-RS) indicated in the information element or field (e.g., reportQuantityCell) in the relevant report configuration (e.g., reportConfig).

[0881] - For example, measurement results can refer to measurement results predicted based on AI / ML functionality (e.g., RRM measurement prediction, measurement event prediction, RLF / HoF prediction).

[0882] - For example, AI / ML functionality can be the first AI / ML functionality.

[0883] - For example, another AI / ML functionality can be a second AI / ML functionality.

[0884] - For example, the first AI / ML functionality and the second AI / ML functionality can be different.

[0885] - For example, the first AI / ML functionality and the second AI / ML functionality can be the same.

[0886] - For example, the first and / or second AI / ML functionality may be (or include) RRM (measurement) prediction, measurement event prediction, RLF prediction and / or HoF prediction.

[0887] One or more methods (or examples) described below can be used at least for concept C:

[0888] - For example, the UE can set the measurement results of the serving cell (e.g., measResultServingCell) in the information elements or fields of the measurement report (e.g., measResultServingMOList) to include the RSRP, RSRQ and / or SINR of some serving cells.

[0889] - For example, the UE can set the measurement results of the best neighbor cell for a frequency (e.g., measResultBestNeighCell) in the information element or field of the measurement report (e.g., measResultServingMOList) to include the RSRP, RSRQ and / or SINR of some best neighbor cells for a frequency.

[0890] - For example, a UE can include measurement results for some included (neighboring) cells based on a report configuration (e.g., reportConfig) for this measurement identity (e.g., measId).

[0891] - For example, the UE can set the measurement results (e.g., resultsSSB-Cell, resultsCSI-RS-Cell) of (neighboring) cells in the information element or field (e.g., measResult) to include the quantity (in descending order of sorting quantity) based on the SS / PBCH block (or CSI-RS) indicated in the information element or field (e.g., reportQuantityCell) in the relevant report configuration (e.g., reportConfig).

[0892] - For example, measurement results may be (or include) the latest available measurement results when (or in response to) a predicted (or triggered) measurement event, when event entry (or exit) conditions are met, or when a measurement report is transmitted.

[0893] - For example, the measurement result may not meet the event's entry conditions (e.g., for cases where a measurement report is triggered based on event entry conditions).

[0894] - For example, the measurement results may not meet the event's exit conditions (e.g., for cases where a measurement report is triggered based on the event's exit conditions).

[0895] - For example, the measurement report could be a first (type) measurement report.

[0896] - For example, the measurement report can be a second (type) measurement report.

[0897] - For example, the measurement report may not be the first (type) measurement report.

[0898] - For example, the measurement report may not be a second (type) measurement report.

[0899] One or more methods (or examples) described below can be used at least for concept D:

[0900] - For example, the UE can set the measurement results of the serving cell (e.g., measResultServingCell) in the information elements or fields of the measurement report (e.g., measResultServingMOList) to include the RSRP, RSRQ and / or SINR of some serving cells.

[0901] - For example, the UE can set the measurement results of the best neighbor cell for a frequency (e.g., measResultBestNeighCell) in the information element or field of the measurement report (e.g., measResultServingMOList) to include the RSRP, RSRQ and / or SINR of some best neighbor cells for a frequency.

[0902] - For example, a UE can include measurement results for some included (neighboring) cells based on a report configuration (e.g., reportConfig) for this measurement identity (e.g., measId).

[0903] - For example, the UE can set the measurement results (e.g., resultsSSB-Cell, resultsCSI-RS-Cell) of (neighboring) cells in the information element or field (e.g., measResult) to include the quantity (in descending order of sorting quantity) based on the SS / PBCH block (or CSI-RS) indicated in the information element or field (e.g., reportQuantityCell) in the relevant report configuration (e.g., reportConfig).

[0904] - For example, measurement results can refer to measurements taken at multiple points in time (within a time window).

[0905] Measurement results may include actual measurements and / or predicted measurements. Measurement results may include new measurements that have been available since the last periodic or event-triggered report or since the measurement was initiated or reset.

[0906] - The multiple time points (within the time window) can be configured by NW (e.g., reconfigured via RRC). The multiple time points (within the time window) can include the time before, during, and / or after the time when the measurement event is predicted (or triggered), the time when the event entry (or exit) conditions are met, the time when the measurement report is transmitted, and the time when the last measurement report (periodic or event-triggered) is transmitted.

[0907] For example, the UE can receive (and / or be configured) to include measurement results at multiple time points (e.g., for cells, for beams) in the measurement report. The NW can provide a configuration (or indication) instructing the UE to include measurement results at multiple time points (e.g., for cells, for beams) in the measurement report. The measurement results and / or measurement reports can be used (by the NW) for AI / ML functionality (e.g., RRM measurement prediction, NW-side prediction, cell prediction, and / or beam prediction).

[0908] - The configuration (or indication) can indicate which (or what) cell's measurement results should be provided (or included). A cell can be (or include) a serving cell, a neighboring cell, a PCell, an SCell, a neighboring cell on the serving MO (the measurement object), a configured cell, an indicated cell, an associated cell, an applicable cell, and / or a detected cell. When the UE is configured to include measurement results at multiple time points in the measurement report, the UE can include measurement results for multiple time points for a cell in the measurement report (if available). For cells(one or more) other than the stated cell, the UE can include the most recent measurement result for that cell (e.g., at a single time point) in the measurement report (or not include measurement results for that cell).

[0909] - Measurement results can be (or include) cellResults, resultsSSB-Cell, resultsCSI-RS-Cell, MeasQuantityResults, RSRP, RSRQ and / or SINR.

[0910] For example, measurement results at multiple time points for a cell can be included in a measurement report. The measurement report can be triggered by a timer (e.g., periodically) and / or measurement events. The multiple time points are within a time window. The time window can be based on a reference time. The UE can perform measurements, predictions, sampling, and / or include measurement results in the report based on the time window (and / or multiple time points).

[0911] - Time windows (and / or multiple time points) can be implicitly indicated or explicitly configured. The UE can determine whether to include (or exclude) measurement results at a particular time point (e.g., whether the time point is within (or outside) the time window) based on the time window. The UE can (be configured to) exclude measurement results far from the reference time (e.g., measurement results at times before the reference time, measurement results not within the time window, measurement results at time points outside the time window). The UE can (be configured to) include measurement results close to the reference time (e.g., the latest measurement result before the reference time, measurement results within the time window, measurement results at time points within the time window). The UE can determine the actual timestamp of the measurement result. The UE can report (or include) the timestamp of the corresponding measurement result. The UE can report (up to) a (configured) number of measurement results.

[0912] For example, a time window (and / or multiple time points) can be (or include, encompass) at least one or more of the following: a duration (or time period) ending (or beginning) at a reference time (containing several measurement results), one or more time gaps (or durations, time periods), the latest (or most recent) K time gaps (or durations, time periods) before (or after) the reference time (e.g., measurement results obtained within (or based on) said time gaps (or durations, time periods)), every N time points (e.g., ms) before (or after) the reference time (at most K) (e.g., N can be determined by the UE and K can be configured by the NW), several measurement results at different time points before (or after) the reference time, and / or the (at most) latest (available) K measurement results at different time points. Letter symbols (e.g., N, K) can be numbers.

[0913] - For example, the reference time may be (or include, encompass) at least one or more of the following: the time when the UE (for cell, frequency, and / or beam) performs (latest) measurements; the time when the UE (for cell, frequency, and / or beam) performs (latest) predictions; the time when the UE (for cell, frequency, and / or beam) obtains (latest) (available) measurements (e.g., predicted and / or actually measured); the time when the UE (for cell, frequency, and / or beam) derives (latest) (available) measurements (e.g., predicted and / or actually measured); the time when the UE (for cell, frequency, and / or beam) returns to (latest) (available) measurements (e.g., predicted and / or actually measured). The actual measurement time, the time of sampling, the time of the latest (available) measurement result (e.g., predicted and / or actually measured) for the cell, frequency and / or beam, the time of the latest (available) measurement result (e.g., predicted and / or actually measured) for the cell, frequency and / or beam prior to the reference time, the time of UE triggering a report (e.g., based on timers, events and / or predictions) for the cell, frequency and / or beam, the time of UE setting a measurement result (e.g., predicted and / or actually measured) for the cell, frequency and / or beam, and / or the time of UE transmitting a measurement report for the cell, frequency and / or beam.

[0914] - For example, one or more parameters (e.g., parameters of time window, number of time points, number of measurement results) may be (or include, encompass) pre-configured by the NW (e.g., via the Master Information Block (MIB) or System Information Block (SIB) specified in the broadcast specification), configured by the NW (e.g., via RRC messages (e.g., RRCReconfiguration, Media Access Control (MAC) Control Element (CE), Downlink Control Information (DCI)), and / or determined by the UE (e.g., by the UE via UE Assistance Information (UAI), RRCReconfigurationComplete, RRCResumeComplete, RRCSetupComplete, RRCReestablishmentComplete requests and / or indications).

[0915] - For example, measurements at multiple time points (included in the report) can be equally spaced.

[0916] - For example, measurements at multiple time points (included in the report) may be predicted and / or actually measured.

[0917] - For example, a time window (and / or multiple time points) may be (or include, encompass) configured timings (or time points) based on (or following) occasions for measurement, prediction, sampling, and / or resource (e.g., SSB, CSI-RS) transmission (e.g., based on periodicity, offset, duration, frequency, and / or repetition). The UE may perform measurements, predictions, sampling, and / or include measurement results in reports based on (or following) configured timings (or time points) for sampling and / or resource (e.g., SSB, CSI-RS) transmission (e.g., based on periodicity, offset, duration, frequency, and / or repetition).

[0918] - The configuration (or indication) may indicate which (or what) beam's measurement results should be provided (or included). A beam may be (or include) a serving cell, neighboring cells, primary cell (PCell), secondary cell (SCell), neighboring cells on a serving measurement object (MO), configured cells, indicated cells, associated cells, applicable cells, and / or detected cells. When the UE is configured to include measurement results at multiple time points in a measurement report, the UE may include measurement results for a beam at multiple time points in the measurement report (if available). For beams(one or more) other than the stated beam, the UE may include the most recent measurement result for that beam in the measurement report (e.g., at a single time point).

[0919] - Measurement results can be (or include) rsIndexResults, resultsSSB-Indexes, resultsCSI-RS-Indexes, ResultsPerSSB-IndexList, ResultsPerSSB-Index, ResultsPerCSI-RS-IndexLists, ResultsPerCSI-RS-Index, MeasQuantityResults, RSRP, RSRQ, and / or SINR.

[0920] For example, measurement results at multiple time points for a beam can be included in a measurement report. The measurement report can be triggered by a timer (e.g., periodically) and / or measurement events. These multiple time points are within a time window. The time window can be based on a reference time. The UE can perform measurements, predictions, sampling, and / or include measurement results in the report based on the time window (and / or multiple time points).

[0921] - For example, the measurement report could be a first (type) measurement report.

[0922] - For example, the measurement report can be a second (type) measurement report.

[0923] - For example, the measurement report may not be the first (type) measurement report.

[0924] - For example, the measurement report may not be a second (type) measurement report.

[0925] One or more methods (or examples) described below can be used to distinguish between measurement reports sent (or triggered) based on measurement event prediction or actual measurement, and / or one or more methods (or examples) described below can be used to distinguish between first (type) measurement reports and second (type) measurement reports:

[0926] - The distinction can be based on the message (or message type or information element) used for the measurement report (e.g., different message types (or information elements) for the first (type) measurement report and the second (type) measurement report).

[0927] - For example, the first message (or message type or information element) may be used by the UE for a measurement report (or a second (type) measurement report) based on a measurement event prediction. The first message (or message type or information element) may not be used by the UE for a measurement report (or a first (type) measurement report) based on an actual measurement.

[0928] - For example, a second message (or message type or information element) may be used by the UE for a measurement report based on actual measurements (or a first (type) measurement report). A first message (or message type or information element) may not be used by the UE for a measurement report based on measurement event prediction (or a second (type) measurement report).

[0929] - The first message (or message type or information element) differs from the second message. The first message (or information element) and / or the second message (or message type or information element) can be an RRC message (or information element). The second message (or message type or information element) can be a measurement report (or measurement result information element).

[0930] - Distinctions can be made based on fields (or indications) in the measurement report.

[0931] - For example, a field (or indicator) can be included in the measurement report to instruct the sending (or triggering) of a report based on a measurement event prediction (or a second (type) measurement report).

[0932] - For example, a field (or indication) can be included in the measurement report to instruct the report to be sent (or triggered) based on the actual measurement (or the first (type) measurement report).

[0933] - The field or indicator can be a true / false value.

[0934] - The field or indicator can be an index or a bit string (series).

[0935] The NW can be configured to use which concept(s) or method(s) or combination of concept(s) or method(s) to use. The UE can receive messages (e.g., RRCReconfiguration) and / or configurations (e.g., measurement configuration, reporting configuration) indicating which concept(s) or method(s) or combination of concept(s) to use.

[0936] UE can decide which concept(s)(or methods) or combination of concepts(or methods) to use.

[0937] - For example, when (or in response to) AI / ML functionality (e.g., RRM measurement prediction, measurement event prediction, RLF / HoF prediction) is capable / available / applicable / configured / activated / inferred and / or the output of AI / ML functionality is used, the UE may use Concept A, Concept B, Concept C, Concept D and / or one or more specified examples, or a combination of Concept A, Concept B, Concept C, Concept D and / or one or more specified examples.

[0938] - For example, when (or in response to) AI / ML functionality (e.g., RRM measurement prediction, measurement event prediction, RLF / HoF prediction) is not capable / unavailable / inapplicable / unconfigured / unactivated / uninferred and / or the output of AI / ML functionality is not used, the UE may use Concept A, Concept B, Concept C, Concept D and / or one or more specified examples, or a combination of Concept A, Concept B, Concept C, Concept D and / or one or more specified examples.

[0939] For example, when (or in response to) a cell's measurement result being higher or lower than a threshold (e.g., configured by the NW and included in a message (e.g., RRCReconfiguration) or configuration (e.g., measurement configuration, reporting configuration)), the UE may use Concept A, Concept B, Concept C, Concept D, and / or one or more specified examples, or a combination of Concept A, Concept B, Concept C, Concept D, and / or one or more specified examples. A cell may be the serving cell, the best neighbor cell of a frequency, neighboring cells, and / or the average of multiple cells (or a function of multiple cells or measurement results as input).

[0940] The NW can configure which cells(s) use a concept(or method) or a combination of concepts(or methods). The UE can receive messages (e.g., RRCReconfiguration) and / or configurations (e.g., measurement configuration, reporting configuration) indicating which cells(s) use the concept(or method) or combination of concepts(or methods).

[0941] The UE can decide which cells(s) use the stated concept(s) or combination of the stated concept(s).

[0942] - For example, when (or in response to) AI / ML functionality (e.g., RRM measurement prediction, measurement event prediction, RLF / HoF prediction) is capable / available / applicable / configured / activated / inferred and / or the output of AI / ML functionality is used for the first cell, the UE may use Concept A, Concept B, Concept C, Concept D and / or one or more specified examples for the second cell, or a combination of Concept A, Concept B, Concept C, Concept D and / or one or more specified examples.

[0943] - For example, when (or in response to) AI / ML functionality (e.g., RRM measurement prediction, measurement event prediction, RLF / HoF prediction) is not capable / unavailable / inapplicable / unconfigured / unactivated / uninferred for the first cell and / or the output of AI / ML functionality is not used for the first cell, the UE may use Concept A, Concept B, Concept C, Concept D and / or one or more specified examples for the second cell, or a combination of Concept A, Concept B, Concept C, Concept D and / or one or more specified examples.

[0944] For example, when (or in response to) a measurement result of the first cell being higher or lower than a threshold (e.g., configured by the NW and included in a message (e.g., RRCReconfiguration) or configuration (e.g., measurement configuration, reporting configuration)), the UE may use Concept A, Concept B, Concept C, Concept D and / or one or more specified examples for the second cell, or a combination of Concept A, Concept B, Concept C, Concept D and / or one or more specified examples. The first cell may be the serving cell, the best neighbor cell of the frequency, neighboring cells, and / or the average of multiple cells (or a function of multiple cells or measurement results as input).

[0945] - The first community can be the same as the second community. The first community can be different from the second community.

[0946] Various examples and embodiments of the invention are described below. The following aspects and embodiments are possible in relation to the methods, alternatives, concepts, examples, and embodiments detailed above and herein.

[0947] refer to Figure 8Utilizing such and other concepts, systems, and methods of the present invention, a method 1000 for a UE in a wireless communication system includes: transmitting to a network a message containing measurement results, wherein the message is triggered by a measurement event prediction (step 1002); not containing some measurement results and some cells (step 1004); and distinguishing the message from a message triggered based on actual measurements (step 1006).

[0948] In various embodiments, the UE provides an indication of whether the transmission of the indication message was triggered by an actual measurement.

[0949] In various embodiments, the indication is associated with the measurement result.

[0950] In various embodiments, the indication is associated with the triggering of measurement reports and events.

[0951] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) transmit a message containing measurement results to the network, wherein the message is triggered by a measurement event prediction; (ii) not contain some measurement results and some cells; and (iii) distinguish the message from a message triggered based on actual measurements. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0952] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a network node in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive a message containing measurement results from a device (e.g., UE), wherein the message is triggered by a measurement event prediction; (ii) at the device, the message does not contain some measurement results and some cells; and (iii) at the device, the message is distinguished from a message triggered based on an actual measurement. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0953] refer to Figure 9Utilizing such and other concepts, systems, and methods of the present invention, a method 1010 for a UE in a wireless communication system includes: transmitting a message containing measurement results to a network, wherein the message is triggered by a measurement event prediction (step 1012); predicting some measurement results for some cells (step 1014); and distinguishing the message from messages triggered based on actual measurements (step 1016).

[0954] In various embodiments, the UE provides an indication of whether the transmission of the indication message was triggered by an actual measurement.

[0955] In various embodiments, the indication is associated with the triggering of measurement reports and events.

[0956] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) transmit a message containing measurement results to the network, wherein the message is triggered by a measurement event prediction; (ii) predict some measurement results for some cells; and (iii) distinguish the message from messages triggered based on actual measurements. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0957] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a network node in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive a message containing measurement results from a device (e.g., UE), wherein the message is triggered by a measurement event prediction; (ii) predict some measurement results for some cells at the device; and (iii) distinguish the message at the device from messages triggered based on actual measurements. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0958] refer to Figure 10 Utilizing such and other concepts, systems, and methods of the present invention, a method 1020 for a UE in a wireless communication system includes: transmitting to a network a message containing measurement results, wherein the message is triggered by a measurement event prediction (step 1022); including some actual measurement values ​​(step 1024); and distinguishing the message from messages triggered based on actual measurements (step 1026).

[0959] In various embodiments, the UE provides an indication of whether the transmission of the indication message was triggered by an actual measurement.

[0960] In various embodiments, the indication is associated with the triggering of measurement reports and events.

[0961] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) transmit a message containing measurement results to the network, wherein the message is triggered by a measurement event prediction; (ii) contain some actual measurement values; and (iii) distinguish the message from messages triggered based on actual measurements. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0962] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a network node in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive a message containing measurement results from a device (e.g., UE), wherein the message is triggered by a measurement event prediction; (ii) contain some actual measurement values; and (iii) distinguish the message at the device from messages triggered based on actual measurements. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0963] refer to Figure 11 Utilizing such and other concepts, systems, and methods of the present invention, a method 1030 for a UE in a wireless communication system includes: transmitting to a network a message containing measurement results, wherein the message is triggered by a measurement event prediction (step 1032); including some measurement values ​​at multiple time points (step 1034); and distinguishing the message from a message triggered based on actual measurements (step 1036).

[0964] In various embodiments, the UE provides an indication of whether the transmission of the indication message was triggered by an actual measurement.

[0965] In various embodiments, the indication is associated with the triggering of measurement reports and events.

[0966] Return to reference Figure 3 and 4In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) transmit a message containing measurement results to the network, wherein the message is triggered by a measurement event prediction; (ii) contain some measurement values ​​at multiple time points; and (iii) distinguish the message from messages triggered based on actual measurements. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0967] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a network node in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive a message containing measurement results from a device (e.g., UE), wherein the message is triggered by a measurement event prediction; (ii) contain some measurement values ​​at multiple time points; and (iii) distinguish the message from messages triggered based on actual measurements. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0968] refer to Figure 12 Utilizing such and other concepts, systems, and methods of the present invention, a method 1040 for a UE in a wireless communication system includes: receiving a first configuration for reporting measurement values ​​(step 1042); and including measurement results for a plurality of time points for a cell in the measurement report, wherein the plurality of time points are within a time window including a reference time (step 1044).

[0969] In various embodiments, the plurality of time points within the time window further include time points before and / or after the reference time.

[0970] In various embodiments, the reference time includes the time of triggering the report, the time of executing the report, the time of setting the measurement result, the time of measuring (or sampling, deriving, predicting, collecting and / or obtaining) the latest (available) measurement result, the time of predicting (or triggering) the measurement event, the time of transmitting the measurement report, the time of meeting the event entry (or exit) conditions, and / or the time of the last transmission (periodic or event-triggered) measurement report.

[0971] In various embodiments, the time window is configured by NW.

[0972] In various embodiments, the time window is included in the RRC reconfiguration message.

[0973] In various embodiments, the plurality of measurement results include new measurement values ​​that have been available since the last periodic or event-triggered report or since the measurement was initiated or reset.

[0974] In various embodiments, the plurality of measurement results include actual measured values ​​and / or predicted measured values.

[0975] In various embodiments, measurement reports are event-triggered and / or periodically triggered.

[0976] In various embodiments, the measurement results at multiple time points are included for all serving cells or a subset of serving cells.

[0977] In various embodiments, the measurement results at multiple time points are included for all neighboring cells or a subset of neighboring cells.

[0978] In various embodiments, the time window ends at (or begins at) a reference time.

[0979] In various embodiments, a time window includes one or more durations, one or more time periods, several time points (or a list of time points) (e.g., including specific frames and / or time slots) and / or several measurements.

[0980] In various embodiments, the measurement results include cell and / or beam measurements.

[0981] In various embodiments, the plurality of measurements (and / or time points) are the closest before (or after) the reference time.

[0982] In various embodiments, the UE is instructed to report specific resource indices and / or measurement results for a specific beam.

[0983] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive a first configuration for reporting measurement values; and (ii) include in the measurement report measurement results for a plurality of time points for the cell, said plurality of time points being within a time window including a reference time. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0984] Return to reference Figure 3 and 4In one or more embodiments viewed from the perspective of a network node in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) transmit a first configuration for reporting measurement values; and (ii) include in the measurement report measurement results for a plurality of time points for the cell, said plurality of time points being within a time window including a reference time. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0985] refer to Figure 13 Utilizing such and other concepts, systems and methods of the present invention, a method 1050 for a UE in a wireless communication system includes: triggering a measurement report (step 1052); and including in the measurement report multiple measurement results for a cell at multiple time points, wherein the multiple time points include one or more of the following: (i) time points configured by the NW, and (ii) time points within a time window configured by the NW (step 1054).

[0986] In various embodiments, the plurality of time points include one or more time points before, during, or after one or more of the following: (i) the time when a measurement event is predicted; (ii) the time when a measurement event is triggered; (iii) the time when a measurement report is transmitted; (iv) the time when an event entry condition is met; (v) the time when an event exit condition is met; (vi) the time when a measurement report is last transmitted; (vii) the time when a periodic measurement report is last transmitted; (viii) the time when an event-triggered measurement report is last transmitted; (ix) the time when the UE performs a measurement; (x) the time when the UE performs the latest measurement; (xi) the time when the UE performs a measurement prediction; (xii) the time when the UE performs the latest measurement prediction; (xiii) the time when the UE obtains a measurement value; (xiv) the time when the UE obtains the latest measurement value; (xv) the time when the UE triggers a measurement report; and (xvi) the time when the UE sets the measurement result in the measurement report.

[0987] In various embodiments, the time points configured by the NW further include one or more of the following: (i) the NW configures the UE to report K measurement results, where K is a number configured by the NW; (ii) the NW configures the UE to report up to K measurement results, where K is a number configured by the NW; (iii) the NW configures the UE to report the latest K measurement results obtained by the UE, where K is a number configured by the NW; and (iv) the NW configures the interval of the measurement results.

[0988] In various embodiments, the time points within the time window configured by the NW further include the duration at which the NW configuration ends or begins at one or more of the following: (i) the time of predicting a measurement event; (ii) the time of triggering a measurement event; (iii) the time of transmitting a measurement report; (iv) the time of satisfying an event entry condition; (v) the time of satisfying an event exit condition; (vi) the time of the last transmission of a measurement report; (vii) the time of the last transmission of a periodic measurement report; (viii) the time of the last transmission of an event-triggered measurement report; (ix) the time when the UE performs a measurement; (x) the time when the UE performs the latest measurement; (xi) the time when the UE performs a measurement prediction; (xii) the time when the UE performs the latest measurement prediction; (xiii) the time when the UE obtains a measurement value; (xiv) the time when the UE obtains the latest measurement value; (xv) the time when the UE triggers a measurement report; and (xvi) the time when the UE sets the measurement result within the measurement report.

[0989] In various embodiments, when the measurement report is sent or triggered based on a measurement event prediction, the UE includes in the measurement report the latest available measurement result actually measured in one or more of the following locations: (i) the time when the measurement event is predicted; (ii) the time when the measurement event is triggered; (iii) the time when the event entry condition is met; (iv) the time when the event exit condition is met; and (v) the time when the measurement report is transmitted.

[0990] In various embodiments, the UE includes new measurement values ​​in the measurement report that have been available since the last periodic report or event-triggered report, or since the measurement was initiated or reset.

[0991] In various embodiments, the plurality of measurement results include actual measured values, predicted measured values, or both actual measured values ​​and predicted measured values.

[0992] In various embodiments, the measurement report is triggered by a predicted measurement event, a predicted measurement value satisfying a measurement event, an actual measurement value satisfying a measurement event, a timer expiration, or whether the measurement result is available.

[0993] In various embodiments, the plurality of measurement results are included for one or more of the following: (i) all serving cells; (ii) a subset of serving cells; (iii) all neighboring cells; and (iv) a subset of neighboring cells.

[0994] In various embodiments, the following conditions exist: (i) an event entry condition or an event exit condition is met; (ii) an event entry condition or an event exit condition is predicted to be met; (iii) the UE sets or includes a measurement result; (iv) no measurement result is available at a certain point in time; (v) the UE triggers a report; and (vi) the UE predicts that a measurement event will occur. When one or more of these conditions occur, the UE performs RRM measurement prediction and / or obtains one or more measurement results for one or more of the following: (i) a cell included in a measurement report; (ii) a cell involved in a predicted or triggered measurement event; and (iii) a cell indicated by the NW.

[0995] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) trigger a measurement report; and (ii) include in the measurement report multiple measurement results for multiple time points for the cell, wherein the multiple time points include one or more of the following: (i) time points configured by the NW; and (ii) time points within a time window configured by the NW. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0996] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a network node in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) trigger a measurement report at the UE; and (ii) include in the measurement report multiple measurement results for multiple time points for the cell, wherein the multiple time points include one or more of the following: (i) time points configured by the NW; and (ii) time points within a time window configured by the NW. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or elsewhere herein.

[0997] Any combination of the concepts or teachings above or herein may be combined, in whole or in part, together or to form new embodiments. The disclosed details and embodiments may be used to solve at least (but not limited to) the problems mentioned above and herein.

[0998] It should be noted that any of the methods, alternatives, steps, examples, and embodiments presented herein may be used independently, separately, and / or in combination with multiple methods, alternatives, steps, examples, and embodiments.

[0999] Various aspects of this disclosure have been described above. It should be understood that the teachings herein can be embodied in a wide variety of forms, and any particular structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and that two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice. Furthermore, this apparatus or practice can be implemented using structures, functions, or structures and functions other than or different from the one or more aspects set forth herein. As examples of some of the concepts above, in some aspects, a parallel channel can be established based on the pulse repetition frequency. In some aspects, a parallel channel can be established based on the pulse position or offset. In some aspects, a parallel channel can be established based on a time jump sequence. In some aspects, a parallel channel can be established based on the pulse repetition frequency, the pulse position or offset, and the time jump sequence.

[1000] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the foregoing description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[1001] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or a combination of both, designed using source coding or some other technique) and have instructions in various forms of program or design code (which, for convenience, may be referred to herein as "software" or "software module"), or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as causing a departure from the scope of this disclosure.

[1002] Furthermore, the various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or executed by an integrated circuit (“IC”), access terminal, or access point. An IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general-purpose processor may be a microprocessor; however, alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors incorporating a DSP core, or any other such configuration.

[1003] It should be understood that any particular order or hierarchy of steps in any disclosed process is an example of an exemplary method. Based on design preferences, it should be understood that a particular order or hierarchy of steps in the process may be rearranged while remaining within the scope of this disclosure. The appended method claims present the elements of each step in an exemplary order and are not intended to be limited to the particular order or hierarchy presented.

[1004] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module (e.g., comprising executable instructions and associated data) and other data can reside in a data memory, such as RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage medium known in this art. The sample storage medium can be coupled to a machine such as a computer / processor (which may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. The sample storage medium can be integrated with the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage medium can reside as discrete components in a user equipment. Furthermore, in some aspects, any suitable computer program product can include a computer-readable medium comprising code associated with one or more aspects of this disclosure. In some respects, computer program products may include packaging materials.

[1005] While the invention has been described in conjunction with various aspects and examples, it should be understood that further modifications are possible. This application is intended to cover any variations, uses, or adaptations of the invention that generally follow the principles of the invention, and includes deviations from this disclosure that occur within the scope of known and customary practice in the field to which this invention pertains.

Claims

1. A method for a user equipment, characterized in that, include: Trigger measurement report; as well as The measurement report contains multiple measurement results for a cell at multiple time points, wherein the multiple time points include one or more of the following: (i) time points configured by the network, and (ii) time points within a time window configured by the network.

2. The method according to claim 1, characterized in that, The multiple time points include one or more time points before, during, or after one or more of the following: (i) the time when the measurement event is predicted; (ii) the time when the measurement event is triggered; (iii) the time when the measurement report is transmitted; (iv) the time when the event entry condition is met; (v) the time when the event exit condition is met; (vi) the time when the last measurement report is transmitted; (vii) the time when the last periodic measurement report is transmitted; (viii) the time when the last event-triggered measurement report is transmitted; (ix) the time when the user equipment performs a measurement; (x) the time when the user equipment performs the latest measurement; (xi) the time when the user equipment performs a measurement prediction; (xii) the time when the user equipment performs the latest measurement prediction; (xiii) the time when the user equipment obtains a measurement value; (xiv) the time when the user equipment obtains the latest measurement value; (xv) the time when the user equipment triggers a measurement report. And (xvi) the user equipment sets the time for the measurement results in the measurement report.

3. The method according to claim 1, characterized in that, The time points configured by the network further include one or more of the following: (i) the network configures the user equipment to report K measurement results, where K is a number configured by the network; (ii) the network configures the user equipment to report up to K measurement results, where K is a number configured by the network; (iii) the network configures the user equipment to report the latest K measurement results obtained by the user equipment, where K is a number configured by the network; and (iv) the network configures the intervals for the measurement results.

4. The method according to claim 1, characterized in that, The time points within the time window of the network configuration further include the duration at which the network configuration ends or begins at one or more of the following: (i) the time of predicting a measurement event; (ii) the time of triggering a measurement event; (iii) the time of transmitting a measurement report; (iv) the time when an event entry condition is met; (v) the time when an event exit condition is met; (vi) the time of the last transmission of a measurement report; (vii) the time of the last transmission of a periodic measurement report; (viii) the time of the last transmission of an event-triggered measurement report; (ix) the time when the user equipment performs a measurement; (x) the time when the user equipment performs the latest measurement; (xi) the time when the user equipment performs a measurement prediction; (xii) the time when the user equipment performs the latest measurement prediction; (xiii) the time when the user equipment obtains a measurement value; (xiv) the time when the user equipment obtains the latest measurement value; (xv) the time when the user equipment triggers a measurement report. And (xvi) the user equipment sets the time for the measurement results in the measurement report.

5. The method according to claim 1, characterized in that, When the measurement report is sent or triggered based on a measurement event prediction, the user equipment includes in the measurement report the latest available measurement result actually measured in one or more of the following locations: (i) the time when the measurement event is predicted; (ii) the time when the measurement event is triggered; (iii) the time when the event entry condition is met; (iv) the time when the event exit condition is met; And (v) the time for transmitting measurement reports.

6. The method according to claim 1, characterized in that, The user equipment includes one or more new measurement values ​​in the measurement report that have been available since the last periodic report or event-triggered report, or since the measurement was initiated or reset.

7. The method according to claim 1, characterized in that, The multiple measurement results include one or more actual measured values, one or more predicted measured values, or both one or more actual measured values ​​and one or more predicted measured values.

8. The method according to claim 1, characterized in that, The measurement report is triggered by the following: a predicted measurement event, one or more predicted measurement values ​​satisfying a measurement event, one or more actual measurement values ​​satisfying a measurement event, a timer expiring, or whether the measurement result is available.

9. The method according to claim 1, characterized in that, For one or more of the following, the plurality of measurement results are included: (i) all serving cells; (ii) a subset of serving cells; (iii) all neighboring cells; and (iv) a subset of neighboring cells.

10. The method according to claim 1, characterized in that, The following conditions exist: (i) an event entry or exit condition is met; (ii) an event entry or exit condition is predicted to be met; (iii) the user equipment sets or includes measurement results; (iv) no measurement results are available at a certain point in time; (v) the user equipment triggers a report; and (vi) the user equipment predicts that a measurement event will occur. When one or more of these conditions occur, the user equipment performs radio resource management measurement prediction and / or obtains one or more measurement results for one or more of the following: (i) a cell included in the measurement report; (ii) a cell involved in the predicted or triggered measurement event; and (iii) a cell indicated by the network.

11. A user equipment, characterized in that, include: Memory; as well as A processor, operably coupled to the memory, wherein the processor is configured to execute program code to: Trigger measurement report; as well as The measurement report contains multiple measurement results for a cell at multiple time points, wherein the multiple time points include one or more of the following: (i) time points configured by the network, and (ii) time points within a time window configured by the network.

12. The user equipment according to claim 11, characterized in that, The multiple time points include one or more time points before, during, or after one or more of the following: (i) the time when the measurement event is predicted; (ii) the time when the measurement event is triggered; (iii) the time when the measurement report is transmitted; (iv) the time when the event entry condition is met; (v) the time when the event exit condition is met; (vi) the time when the last measurement report is transmitted; (vii) the time when the last periodic measurement report is transmitted; (viii) the time when the last event-triggered measurement report is transmitted; (ix) the time when the user equipment performs a measurement; (x) the time when the user equipment performs the latest measurement; (xi) the time when the user equipment performs a measurement prediction; (xii) the time when the user equipment performs the latest measurement prediction; (xiii) the time when the user equipment obtains a measurement value; (xiv) the time when the user equipment obtains the latest measurement value; (xv) the time when the user equipment triggers a measurement report. And (xvi) the user equipment sets the time for the measurement results in the measurement report.

13. The user equipment according to claim 11, characterized in that, The time points configured by the network further include one or more of the following: (i) the network configures the user equipment to report K measurement results, where K is a number configured by the network; (ii) the network configures the user equipment to report up to K measurement results, where K is a number configured by the network; (iii) the network configures the user equipment to report the latest K measurement results obtained by the user equipment, where K is a number configured by the network; and (iv) the network configures the interval of the measurement results.

14. The user equipment according to claim 11, characterized in that, The time points within the time window of the network configuration further include the duration at which the network configuration ends or begins at one or more of the following: (i) the time of predicting a measurement event; (ii) the time of triggering a measurement event; (iii) the time of transmitting a measurement report; (iv) the time when an event entry condition is met; (v) the time when an event exit condition is met; (vi) the time of the last transmission of a measurement report; (vii) the time of the last transmission of a periodic measurement report; (viii) the time of the last transmission of an event-triggered measurement report; (ix) the time when the user equipment performs a measurement; (x) the time when the user equipment performs the latest measurement; (xi) the time when the user equipment performs a measurement prediction; (xii) the time when the user equipment performs the latest measurement prediction; (xiii) the time when the user equipment obtains a measurement value; (xiv) the time when the user equipment obtains the latest measurement value; (xv) the time when the user equipment triggers a measurement report. And (xvi) the user equipment sets the time for the measurement results in the measurement report.

15. The user equipment according to claim 11, characterized in that, When the measurement report is sent or triggered based on a measurement event prediction, the user equipment includes in the measurement report the latest available measurement result actually measured in one or more of the following locations: (i) the time when the measurement event is predicted; (ii) the time when the measurement event is triggered; (iii) the time when the event entry condition is met; (iv) the time when the event exit condition is met; And (v) the time for transmitting measurement reports.

16. The user equipment according to claim 11, characterized in that, The user equipment includes one or more new measurement values ​​in the measurement report that have been available since the last periodic report or event-triggered report, or since the measurement was initiated or reset.

17. The user equipment according to claim 11, characterized in that, The multiple measurement results include one or more actual measured values, one or more predicted measured values, or both one or more actual measured values ​​and one or more predicted measured values.

18. The user equipment according to claim 11, characterized in that, The measurement report is triggered by the following: a predicted measurement event, one or more predicted measurement values ​​satisfying a measurement event, one or more actual measurement values ​​satisfying a measurement event, a timer expiring, or whether the measurement result is available.

19. The user equipment according to claim 11, characterized in that, For one or more of the following, the plurality of measurement results are included: (i) all serving cells; (ii) a subset of serving cells; (iii) all neighboring cells; and (iv) a subset of neighboring cells.

20. The user equipment according to claim 11, characterized in that, The following conditions exist: (i) an event entry or exit condition is met; (ii) an event entry or exit condition is predicted to be met; (iii) the user equipment sets or includes measurement results; (iv) no measurement results are available at a certain point in time; (v) the user equipment triggers a report; and (vi) the user equipment predicts that a measurement event will occur. When one or more of these conditions occur, the user equipment performs radio resource management measurement prediction and / or obtains one or more measurement results for one or more of the following: (i) the cell included in the measurement report; (ii) the cell involved in the predicted or triggered measurement event. and (iii) the cell indicated by the network.

Images