Configuration of idle / inactive UE logging (RRM compliant) and reporting

The framework enhances UE measurement logging in idle/inactive states with RRM-compliant configurations and structured reporting to address data quality issues, ensuring high-quality data collection for AI/ML models without impacting connected state operations.

WO2026235597A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/SE2026/050305
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-05
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Current 3GPP specifications lack standardized accuracy requirements for UE measurements in idle/inactive states, leading to inconsistent data quality that can degrade AI/ML mobility model accuracy, and existing MDT frameworks are not optimized for RRM-compliant, high-fidelity data collection during these states.

Method used

A framework is introduced to configure UEs in idle/inactive states with RRM-compliant measurement logging and reporting, using enhanced MDT-like configurations with strict accuracy requirements, DRX-aligned micro-wake logging, and structured reporting triggers to ensure data quality for AI/ML model training.

Benefits of technology

Enables high-quality data collection for AI/ML mobility models without impairing connected state processes, ensuring RRM compliance, power efficiency, and timely reporting, thereby enhancing model trust and reducing network costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure SE2026050305_12112026_PF_FP_ABST
    Figure SE2026050305_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Systems and methods are disclosed for logging of data at a User Equipment (UE) when in idle or inactive state and reporting of the logged data. In one embodiment, a method performed by a UE for data collection logging when in an idle or inactive state and associated reporting comprises receiving, from a network node, configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitly indicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state. The method further comprises storing the configuration information at the UE and, while in the idle or inactive state, performing radio resource management data collection logging and associated reporting, in accordance with the received configuration information.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CONFIGURATION OF IDLE / INACTIVE UE LOGGING (RRM COMPLIANT) AND REPORTING RELATED APPLICATIONS

[0002] This application claims the benefit of U. S. Provisional Patent Application No. 63 / 802,396, filed May 8, 2025, the disclosure of which is hereby incorporated herein by reference in its entirety.

[0003] TECHNICAL FIELD

[0004] The present disclosure relates to a wireless communication network and, more specifically, to logging of data at a User Equipment (UE) when in idle or inactive mode and reporting of the logged data.

[0005] BACKGROUND

[0006] 1 Al for Mobility

[0007] The Artificial Intelligence (AI) / Machine Learning (ML) for the physical layer (PHY) work in 3rdGeneration Partnership Project (3GPP) Release (Rel-) 18 has been limited to lower layer features, such as Beam Management, which is sometimes referred to as intra-cell mobility. Other features, such as Layer 3 (L3) handovers, Radio Resource Control (RRC) measurements configuration and reporting of predictions have not been part of the Rel-18.

[0008] Hence, a Rel- 19 Study Item to study the usage of Al / ML for L3 Mobility and / or Radio Resource Management (RRM) measurements is considered. As described in 3GPP Technical Report (TR) 38.843 V18.0.0, the objective of the study item includes the following:

[0009] • Study and evaluate potential benefits and gains of AI / ML aided mobility for network triggered L3 -based handover, considering the following aspects:

[0010] o AI / ML based RRM measurement and event prediction

[0011] ■ Cell-level measurement prediction including intra and inter-frequency (User Equipment (UE) sided and network (NW) sided model)

[0012] • Inter-cell Beam-level measurement prediction for L3 Mobility (UE sided and NW sided model)

[0013] o Handover (HO) failure / Radio Link Failure (RLF) prediction (UE sided model) o Measurement events prediction (UE sided model)

[0014] • Study the need / benefits of any other UE assistance information for the network side model.The evaluation of the AI / ML aided mobility benefits should consider HO performance Key Performance Indicators (KPIs) and complexity tradeoffs

[0015] 2 Legacy MDT Framework

[0016] The Minimization of Drive Tests (MDT) framework, standardized in 3GPP since Long Term Evolution (LTE) Release 10 and extended into 5thGeneration (5G) New Radio (NR), was introduced to reduce the need for costly, manual field testing for coverage validation, troubleshooting, and network performance assessment. MDT allows the network to leverage real UE in the field as passive data collectors. The core specifications related to the legacy MDT framework include the following:

[0017] • 3GPP TS 38.331 — NR Radio Resource Control (RRC) protocol specification

[0018] • 3GPP TS 37.320 — Overall MDT framework description

[0019] • 3GPP TS 38.133 — RRM measurement requirements (accuracy and procedures) • 3GPP TS 38.304 — Measurement procedures for mobility

[0020] A) Immediate MDT (RRC CONNECTED mode)

[0021] In Immediate MDT, the network (i.e., the gNodeB (gNB)) configures the UE to perform and report measurements in real-time while connected.

[0022] • Configuration

[0023] o Delivered via RRCReconfiguration — > measConfig

[0024] o Key Information Elements (IES) and object types:

[0025] ■ measObjectToAddModList (frequencies / cells to measure) ■ reportConfigToAddModList (event-based or periodic reporting)

[0026] ■ measIdToAddModList (associates measObject + reportConfig)

[0027] ■ quantityConfig (which metrics: Synchronization Signal (SS) Reference Signal Received Power (SS-RSRP), SS Reference Signal Received Quality (SS-RSRQ), SS Signal to Interference plus Noise Ratio (SS-SINR)) • Measurement Events (see 3GPP TS 38.331 V18.5.1, §5.5.3.1)

[0028] o Event Al: Serving becomes better than threshold

[0029] o Event A2: Serving becomes worse than threshold

[0030] o Event A3: Neighbor becomes offset-better than serving

[0031] o Event A5: Combined serving degradation and neighbor improvement • Reporting

[0032] o Reports sent via MeasurementReport RRC message.• Use Cases

[0033] o Real-time handover evaluation

[0034] o Call / session quality monitoring

[0035] o Network optimization (fast-response diagnostics)

[0036] B) Logged MDT (RRC IDLE or RRC INACTIVE mode)

[0037] In Logged MDT, the UE logs measurements locally without sending them immediately, typically while not connected. This is useful for offline diagnostics and post-mobility evaluation.

[0038] • Configuration

[0039] o Provided while UE is in RRC CONNECTED:

[0040] ■ Delivered via RRCReconfiguration —> measConfig.mdt-Configuration o Key IES (see 3GPP TS 38.331 §5.6.3):

[0041] ■ mdt- Activation = loggedMDT

[0042] ■ areaScope: Defines where logging is allowed (via cell list, Tracking Area (TA) list, or Public Land Mobile Network (PLMN))

[0043] ■ loggingDuration: Total time to log (e.g., s600)

[0044] ■ reportInterval: Frequency of log entries (e.g., ms512, ms1024)

[0045] ■ measurementQuantities: e.g., SS-RSRP, SS-SINR

[0046] ■ positioningMethod: Global Navigation Satellite System (GNSS), Enhanced Cell Identity (ECID), or none

[0047] • Logging Behavior

[0048] o UE logs measurements per configuration only inside areaScope

[0049] o No reporting occurs in IDLE / INACTIVE; logs stored in memory

[0050] o Power-efficient: No uplink, Discontinuous Reception (DRX)-observant, no realtime processing

[0051] • Reporting (see 3GPP TS 38.331 §5.6.4)

[0052] o Upon reconnecting (RRC connection establishment or resume):

[0053] ■ UE sets loggedMeasurementAvailable-r16 = TRUE in RRCSetupComplete or RRCResumeComplete

[0054] ■ gNB triggers reporting via UEInformationRequest

[0055] ■ UE responds with UEInformationResponse (contains logged MDT data) • Limitations

[0056] o No real-time feedback

[0057] o No awareness of DRX or paging conflictso No ML labeling, no structured outcomes, no per-log quality flag o Cannot autonomously initiate reporting (e.g., on buffer full)

[0058] 3 Legacy RRM Framework

[0059] Radio Resource Management (RRM) in 3GPP encompasses the procedures that ensure efficient and reliable use of radio resources while maintaining service continuity, mobility, and quality of experience. It defines how UEs perform signal measurements and how networks interpret them for decisions like handover, cell reselection, and resource allocation.

[0060] Key RRM measurement components include:

[0061] • SS-RSRP (Reference Signal Received Power): Measures received signal strength from Synchronization Signal Blocks (SSBs),

[0062] • SS-RSRQ (Reference Signal Received Quality): Quantifies the quality of the received signal relative to overall interference, and

[0063] • SS-SINR (Signal -to-Interference-plus-Noise Ratio): Reflects signal clarity, particularly important in high-density deployments.

[0064] RRM measurement behavior is governed by:

[0065] • 3GPP TS 38.133 (conformance and accuracy requirements),

[0066] • 3GPP TS 38.331 (RRC configuration and measurement control),

[0067] • Measurement gaps for inter-frequency or inter-Radio Access Technology (RAT) measurement during RRC CONNECTED, and

[0068] • System Information Block (SIB)-based cell reselection rules in RRC IDLE Legacy RRM frameworks assume that measurements are either:

[0069] • Used immediately in the connected state for real-time control, or

[0070] • Used indirectly via periodic IDLE measurements for reselection — not for training intelligent models.

[0071] They do not address:

[0072] • High-frequency, structured logging for offline learning,

[0073] • DRX-aware data alignment, and

[0074] • Autonomous UE behavior for Al-friendly log capture.

[0075] SUMMARY

[0076] Systems and methods are disclosed for logging of data at a User Equipment (UE) when in idle or inactive mode and reporting of the logged data. In one embodiment, a methodperformed by a UE for data collection logging when in an idle or inactive state and associated reporting comprises receiving, from a network node, configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitly indicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state. The method further comprises storing the configuration information at the UE and transitioning to the idle or inactive state. The method further comprises, while in the idle or inactive state, performing radio resource management data collection logging and associated reporting, in accordance with the received configuration information. In this manner, the UE is enabled to collect data (e.g., for the sake of model training for mobility use cases) while the UE is in idle or inactive state in such a manner that the data collection process does not impair other high priority process(es) in connected state.

[0077] In one embodiment, the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to when such configuration information does not comprise information that explicitly or implicitly indicates one or more increased accuracy requirements.

[0078] In one embodiment, the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to default accuracy requirements for radio resource management data collection logging when in the idle or inactive state.

[0079] In one embodiment, the one or more accuracy requirements comprise one or more increased accuracy requirements that are the same as accuracy requirements for radio resource management data collection logging when in a connected state.

[0080] In one embodiment, the configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state comprises an indication of a logging purpose.

[0081] In one embodiment, the configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state comprises an explicit indication of strict logging accuracy.

[0082] In one embodiment, the configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state comprises any one or more of the following: an indication to monitor one or more triggering conditions for logging of the radio resource management data, one or more time-based conditions related to logging of the radio resource management data, an indication of one or more mobility events related to logging of the radio resource management data, one or more measurement thresholds related tologging of the radio resource management data, an indication for the UE to wake up for data collection during discontinuous reception (DRX) operation, one or more UE offsets for waking up within a DRX cycle or paging occasion to perform and log the radio resource management data, an indication of a duration of time over which the radio resource management data collection logging is to be performed, one or more absolute radio frequency channel numbers to which the UE is to tune to perform measurements for the radio resource management data collection logging, information that indicates one or more logging metrics, information that indicates one or more logging metrics to which strict requirements are applicable, information that indicates a sampling frequency of measurements during the logging, and information that controls when the UE is to report the logged data.

[0083] In one embodiment, the configuration information is received in one or more fields in message.

[0084] In one embodiment, the configuration information configures the UE to report the logged data either periodically or based on one or more event-based triggers.

[0085] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE for data collection logging when in an idle or inactive state and associated reporting comprises a communication interface comprising a transmitter and a receiver. The UE further comprises processing circuitry associated with the communication interface, wherein the processing circuitry is configured to cause the UE to receive, from a network node, configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitly indicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state. The processing circuitry is further configured to cause the UE to store the configuration information at the UE and transition to the idle or inactive state. The processing circuitry is further configured to cause the UE to, while in the idle or inactive state, perform radio resource management data collection logging and associated reporting, in accordance with the received configuration information.

[0086] Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node for configuring a UE for radio resource management data collection logging when in idle or inactive state and associated reporting comprises transmitting, to a UE, configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitlyindicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state.

[0087] In one embodiment, the method further comprises receiving, from the UE, a report comprising radio resource management data collected and logging by the UE when in the idle or inactive state, in accordance with the configuration information.

[0088] In one embodiment, the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to when such configuration information does not comprise information that explicitly or implicitly indicates one or more increased accuracy requirements.

[0089] In one embodiment, the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to default accuracy requirements for radio resource management data collection logging when in the idle or inactive state.

[0090] In one embodiment, the one or more accuracy requirements comprise one or more increased accuracy requirements that are the same as accuracy requirements for radio resource management data collection logging when in a connected state.

[0091] In one embodiment, the configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state comprises an indication of a logging purpose (e.g., AI for mobility or another purpose).

[0092] In one embodiment, the configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state comprises an explicit indication of strict logging accuracy.

[0093] In one embodiment, the configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state comprises any one or more of the following: an indication to monitor one or more triggering conditions for logging of the radio resource management data, one or more time-based conditions related to logging of the radio resource management data, an indication of one or more mobility events related to logging of the radio resource management data, one or more measurement thresholds related to logging of the radio resource management data, an indication for the UE to wake up for data collection during DRX operation, one or more UE offsets for waking up within a DRX cycle or paging occasion to perform and log the radio resource management data, an indication of a duration of time over which the radio resource management data collection logging is to be performed, one or more absolute radio frequency channel numbers to which the UE is to tune to perform measurements for the radio resource management data collection logging, information that indicates one or more logging metrics, information that indicates one or more logging metricsto which strict requirements are applicable, information that indicates a sampling frequency of measurements during the logging, and information that controls when the UE is to report the logged data.

[0094] In one embodiment, the configuration information is received in one or more fields (e.g., one or more fields in an RRC Reconfiguration message).

[0095] In one embodiment, the configuration information configures the UE to report the logged data either periodically or based on one or more event-based triggers.

[0096] Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for configuring a UE for radio resource management data collection logging when in idle or inactive state and associated reporting comprises processing circuitry configured to cause the network node to transmit, to a UE, configuration information that configures the UE to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitly indicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state.

[0097] BRIEF DESCRIPTION OF THE DRAWINGS

[0098] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0099] Figure 1 illustrates the operation of a User Equipment (UE) and a network node in accordance with at least some of the embodiments described above.

[0100] Figure 2 shows an example of a communication system in accordance with some embodiments.

[0101] Figure 3 is another example of a communication system according to some embodiments. Figure 4 shows a wireless device, which may be configured to operate in communication system of Figure 2 or in communication system of Figure 3.

[0102] Figure 5 shows a network node in accordance with some embodiments.

[0103] Figure 6 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0104] DETAILED DESCRIPTION

[0105] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Uponreading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0106] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0107] In current 3rdGeneration Partnership Project (3GPP) specifications, User Equipment (UE) measurement accuracy requirements are explicitly defined only for the RRC CONNECTED state, as outlined in the following text from 3GPP TS 38.133 V18.9.0 Clause 9.1.1:

[0108] This clause contains general requirements on the UE regarding measurement reporting in RRC CONNECTED state. The requirements are split in intra-frequency, inter-frequency, inter-RAT E-UTRAN FDD, inter-RAT E-UTRAN TDD, and Ll-RSRP measurements requirements. These measurements may be used by the NG-RAN. The measurement quantities are defined in TS 38.215 [4], the measurement model is defined in TS 38.300

[0010] , TS 37.340

[0017] and measurement accuracies are specified in clause 10. Control of measurement reporting is specified in TS 38.331 [2],

[0109] As outlined in the 3GPP specifications, for the RRC CONNECTED state, tolerances for Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), and Signal to Interference plus Noise Ratio (SINR) are strictly enforced for conformance. Table 10.1.2.1.1-1 of 3GPP TS 38.133 gives the Synchronization Signal RSRP (SS-RSRP) intra-frequency absolute accuracy in Frequency Range 1 (FR1). This table is reproduced below as Table 1.

[0110] Table 1: Reproduction of Table 10.1.2.1.1-1 from 3GPP TS 38.133 (SS-RSRP Intra-frequency absolute accuracy in FR1)

[0111]

[0112]

[0113]

[0114] In contrast, RRC IDLE and RRC IN ACTIVE states are not subject to any standardized accuracy constraints, leaving measurement behavior largely implementation dependent. This asymmetry introduces a critical issue when leveraging UE-collected measurement data for Artificial Intelligence (AI) / Machine Learning (ML)-based mobility modeling: measurements obtained in idle / inactive states may suffer from relaxed timing, averaging, or calibration, resulting in non-uniform data quality. While Clause 10.1.2B in 3GPP TS 38.133 introduces a specific measurement accuracy requirement for idle / inactive states (e.g., for specific use cases such as Dual Connectivity (DC) and Carrier Aggregation (CA)), it remains functionally and numerically distinct (by couple of decibels (dBs), check Table 10.1.2B.1.1-1) from the rigor of RRC CONNECTED specifications, as shown in the following text from 3GPP TS 38.133 and Table 2.

[0115] 10.1.2B Intra-frequency RSRP accuracy requirements for FR1 for CA / DC Idle Mode Measurements

[0116] 10.1.2B.1 Intra-frequency SS-RSRP accuracy requirements

[0117] The requirements in this clause are applicable for a UE:

[0118] - in state RRC IDLE or RRC INACTIVE

[0119] that is synchronised to the cell that is measured.

[0120] The requirements are for absolute SS-RSRP accuracy.

[0121] 10.1.2B.1.1 Absolute SS-RSRP AccuracyUnless otherwise specified, the requirements for absolute SS-RSRP accuracy in this clause apply to the serving cell in FR1.

[0122] The accuracy requirements in table 10.1.2B.1.1-1 are valid under the following conditions:

[0123] Conditions defined in clause 7.3 of TS 38.101-1

[0018] for reference sensitivity are fulfilled.

[0124] Conditions for intra-frequency measurements are fulfilled according to annex B.1.2 for a corresponding Band for each relevant SSB.

[0125] Table 2: Reproduction of Table 10.1.2B.1.1-1 from 3GPP TS 38.133 (SS-RSRP Intra-frequency absolute accuracy in FR1)

[0126]

[0127] To ensure data consistency and model reliability, especially in training supervised or semisupervised learning systems for mobility prediction, it is therefore essential to tag or filter UE-reported data based on whether it was collected under Radio Resource Management (RRM)-compliant conditions.

[0128] There currently exist certain challenge(s). Current 5thGeneration (5G) Minimization of Drive Tests (MDT) mechanisms are designed primarily for troubleshooting or network coverage optimization and are not optimized for:

[0129] • RRM-compliant, high-fidelity, and accurate data collection during IDLE or INACTIVE states, or

[0130] • Efficient and timely reporting of such data.

[0131] Logged MDT is performed while the UE is in RRC IDLE and RRC INACTIVE. A problem is that the requirements on the UE related to measurements are much more relaxed for UEs in RRC IDLE and RRC INACTIVE compared with RRC CONNECTED, so using measurement results from RRC IDLE and RRC INACTIVE may not be accurate enough as input to the AI / ML model.

[0132] In 3GPP specifications, only RRC CONNECTED measurements have defined accuracy requirements (see 3GPP TS 38.133 Clause 9.1.1), while RRC IDLE / INACTIVE measurements are largely implementation-dependent and less reliable. Although Clause 10.1.2B introduces limited accuracy guidance for idle / inactive states, it remains distinct from RRC_CONNECTED standards. This inconsistency poses a risk for AI / ML mobility model training, where mixed-quality data can degrade model accuracy. To address this, an RRM compliance flag should be added to indicate when measurements meet RRC CONNECTED-grade accuracy — allowing better filtering, weighting, and trust in data-driven mobility optimization.

[0133] There is a need to enable reporting to be opportunistic, efficient, or aligned with paging / Discontinuous Reception (DRX).

[0134] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Systems and methods are disclosed herein that provide a mechanism for a network node (e.g., a Radio Access Network (RAN) node such as, e.g., a gNodeB (gNB)) to configure UEs, while in RRC CONNECTED, with a set of parameters that enable data collection for AI / ML model training while the UE is in RRC IDLE or RRC Inactive states. Embodiments of the present disclosure may include any one or more of the following aspects:

[0135] • RRM-compliant measurement logging in IDLE / INACTIVE states, i.e. the UE performs measurements according to RRC CONNECTED mode requirements while in RRC IDLE and RRC INACTIVE. Note, as mentioned above, in the current 3 GPPspecifications, the requirements for data logging in IDLE / INACTIVE states are not the same as those for data collection in CONNECTED modes.

[0136] • AI / ML-intent-aware configuration using a new loggingPurpose field

[0137] • DRX-aligned Micro-wake logging and reporting via paging occasions (POs)

[0138] • Structured, policy-driven reporting triggers (e.g., onPagingOccasion, onLogSizeThreshold, onTimeExpiry)

[0139] • Optionally, the UE may organize logs into input-output tuples to support AI / ML training.

[0140] In non-limiting examples, the configurations for the data collection for AI / ML model training for RRC_CONNECTED mode mobility use cases as described above can be sent to the UE as part of a logged MDT-like solution (e.g., by enhancing the existing MDT mechanism) or using the RRM measurement configuration framework e.g., using measConfig or ReportConfigNR as part of RRC signaling).

[0141] Embodiments of the present disclosure provide a coordinated framework of enhancements that together enables AI / ML-grade RRM measurement logging and efficient log reporting. More specifically, embodiments of the present disclosure may include any one or more of the following aspects:

[0142] • Proactive Logging Configuration & Ensuring RRM Compliance during IDLE / INACTIVE o Configuration of MDT measurements for data collection for performing training and / or inference of measurement predictions.

[0143] o Configuration of measurements with stricter performance requirements compared to existing measurements for RRC IDLE / RRC INACTIVE. In one option, the measurement requirements for RRC CONNECTED are also used for RRC IDLE / RRC INACTIVE.

[0144] o In one example, a network node (e.g., gNB) configures EnhancedMDT- Configuration-r 19:

[0145] ■ loggingPurpose-r19 = aiMobilityModel to ensure data collection for Al for mobility case.

[0146] • Including an RRM compliance flag (strictRRMAccuracy) to indicate that IDLE / INACTIVE measurements must meet RRC CONNECTED-grade accuracy allowing better filtering, weighting, and trust in data-driven mobility optimization.

[0147] • Execution of Logging in RRC IDLE / RRC INACTIVEo Logging of configured measurements, where in one option the measurement requirements are according to the requirements for RRC CONNECTED.

[0148] o Logging is done according to, e.g., loggingDuration, reportinterval, logDuringDRX, and spatial filters (areaScope).

[0149] o Optional virtualGaps concept is introduced to coordinate logging with DRX paging occasions.

[0150] • Advanced Reporting Triggers

[0151] o UE reports logged data based on any one or more of the following:

[0152] ■ onPagingOccasion

[0153] ■ onLogSizeThreshold

[0154] ■ onTimeExpiry

[0155] • RRM Alignment Enforcement

[0156] o Field: strictRRMAccuracy ensures compliance with 3GPP TS 38.133 o UE signals loggedMeasurementQualityCapability to indicate support • Structured AI-Ready Logging Format

[0157] o Optional support for LoggedMeasurementSampleWithOutcome (input-output tuples), aligning each measurement with an outcome (e.g., handover success, paging missed).

[0158] o Enhances ML training utility and enables post-processing trust filtering. Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the solution(s) described herein may enable a UE to collect data for the sake of model training for mobility use cases while the UE is in RRC IDLE or RRC INACTIVE state. The advantage of this solution(s) is that the data collection process does not impair other high priority process in RRC CONNECTED state. For example, the network does not need to allocate measurement gaps for the sake of data collection or the data collection does not impact any ongoing transmissions / receptions. This enhances the quality of service at the UE, in particular if delay sensitive services are running at the UE. In addition, the data collection process in RRC CONNECTED mode may impair the normal RRM measurement that might be urgently needed by the network for the mobility decisions. Therefore, embodiments of the present disclosure may reduce the cost and impairment of data collection in RRC connected state, by performing the same measurements with the same quality (accuracy requirements) in RRC IDLE state. Other advantages that may be provided by various embodiments of the solution(s) disclosed herein are listed below.• AI / ML-Compatible Logging in Idle / Inactive: Enables RRM-compliant measurement logging without requiring RRC connection, which is ideal for large-scale Al mobility training. Ensures logs meet 3GPP TS 38.133 CONNECTED mode RRM measurement standards, increasing trust in Al model inputs.

[0159] • Power-Efficient & Paging Occasion (PO)-Aligned: Supports micro-wake logging aligned with DRX and paging occasion cycles to save battery while maintaining log fidelity.

[0160] • Flexible Logging Triggers: Adds event- or location-based logging activation, allowing network-controlled policies tailored for specific use cases.

[0161] • Structured Input-Output Data for Al: Supports optional logging as input-output tuples, enabling ready-to-train, self-labeling datasets.

[0162] • Purpose-Driven Logging Configuration: Clearly distinguishes Al-focused logging from standard MDT, enabling optimized behavior and interpretation.

[0163] • Backward-Compatible: Extends existing MDT framework with optional fields, ensuring smooth integration across network and UE classes.

[0164] • Network-Directed Logging Control: gNB configures all behavior, ensures only capable UEs participate, and enables real-time log-driven learning.

[0165] From the perspective of the UE, the following description of various UE related embodiments is provided:

[0166] A. UE.1: UE Receives configuration signal for RRM data collection logging in RRC IDLE / INACTIVE (with RRM-Compliant) and associated report.

[0167] UE receives configuration signal (during RRC_CONNECTED) for logging of RRM-compliant measurements when entering RRC IDLE or RRC INACTIVE. Logging activation and deactivation are governed by pre-received configuration, including areaScope, measurement triggers, and duration.

[0168] A. UE.2: Configurations of Storage, Execution, and Reporting of Logging sent in A. UE.l UE internally stores the configuration parameters received from gNB (as described in A. N.2), which may include one or more of the following example fields:

[0169] • Indicator for logging Purpose, this is for explicitly specify to the UE that the MDT logging session is for Al for mobility (or other purpose). A new field could be introduced (e.g., loggingPurpose) as in A. N.7.

[0170] • Strict Logging Accuracy (RRM like), e.g., strictRRMAccuracy. UE ensures MDT logged data / measurement (during inactive / idle modes for model training or inference) quality and accuracy aligned with RRC CONNECTED requirements (as described in clause 9 and 10in TS 38.133 specs). It does not exist in current spec, so a new field is needed, e.g., strictRRMAccuracy, and it could be used as an indicator for indicating that this is data collection for RRM data for AI / ML model training.

[0171] • Indicator to monitor a triggering condition(s) for data logging, e.g., loggingTriggerCondition, UE monitors conditions such as time, mobility events (e.g., cell reselection), or measurement thresholds (e.g., Event A3). This could be mapped to areaScope in MDT-Configuration but also need a new field like loggingTriggerCondition (including eventTriggeredMeasurementList) in ReportConfig. Note that Condition and Event are used exchangeable in this document.

[0172] • Indicator for to wake up for data collection, e.g., logDuringDRX'. If TRUE, UE wakes briefly during DRX sleep period to collect data for AI / ML model training and log it. This does not exist, so a new field is proposed herein which is referred to as new field logDuringDRX.

[0173] • UE offsets logging wake-up within DRX cycle or paging occasion, using a field e.g., logGapOffset. This is a new configuration field that enables precise alignment of measurement logging within the UE's DRX or Paging Occasion (PO) cycles, by defining a relative offset or delay within those cycles. This is needed because in standard 5G MDT (as per loggedMDT-Config in TS 38.331), there is no mechanism to control when within a DRX cycle or PO the UE wakes up to collect / log data.

[0174] • UE maintains an internal timer for the specified duration (e.g., s600), ending logging once expired, e.g., loggingDuration. There exist loggingDuration m MDT-Configuration, so it could be reused, or new fields could be introduced.

[0175] • UE tunes to specified Absolute Radio Frequency Channel Numbers (ARFCNs) to collect RRM measurement for AI / ML model training, e.g., loggingFrequencyList. This already exists in measObjectToAddModList in measConfig, so it could be reused, or new fields could be introduced.

[0176] • UE logs Synchronization Signal (SS) Reference Signal Received Power (SS-RSRP), SS Reference Signal Received Quality (SS-RSRQ), SS Signal to Interference plus Noise Ratio (SS-SINR) values as per strictRRMAccuracy, e.g., loggingMetrics. This already exists in measurementQuantities in MDT-Configuration,' quantityConfig in measConfig, so it can be reused, or new fields could be introduced.

[0177] • Define sampling frequency of measurements during logging, e.g., reportinterval (logginglnterval). This already exists in reportinterval in MDT-Configuration. So, it can be reused or a new filed could be introduced.• Control when to report logs based on condition (PO), e.g., reportTrigger Condition. This configuration / field does not exist in current standard, it is needed to propose new fields that enable this, like: onPagingOccasion, onLogSizeThreshold. Note that Condition and Event are used exchangeable in this document.

[0178] A. UE.2.1: Similar to embodiment in A. N.2.1

[0179] A. UE.2.2: UE executes one of the following logging approaches as indicated by network configuration (in A. N.2.2):

[0180] • Periodical logging

[0181] • Event based logging. Note that Condition and Event are used exchangeable in this document.

[0182] As described above, the proposed information loggingTriggerCondition, could be embedded in:

[0183] - areaScope, which indicate spatial region where the UE is allowed to log. This will be a trigger if the UE is in listed cells (i.e., cellList), or tracking area (i.e., trackingAreaList), or Public Land Mobile Network (PLMN) (i.e., plmn-IdentityList).

[0184] - New field like “eventTriggeredMeasurementList” for inactive / Idle (called loggingTriggerCondition) which specifies the event conditions that cause logging or reporting. Example of event conditions are, A3: Neighbor becomes better than serving, A2: Serving becomes worse than threshold, A5: Serving below + neighbor above threshold. Considering A3, this can be described as follows:

[0185] reportConfigToAddModList = {

[0186] reportConfig = {

[0187] reportType = eventTriggered: {

[0188] eventld = eventA3,

[0189] triggerQuantity = ss-RSRP,

[0190] timeToTrigger = ms160,

[0191] }

[0192] }

[0193] }

[0194] - The condition may rely on UE mobility state, e.g., logging is triggered provided UE fulfills low mobility criterion and / or not-at-cell edge criterion.

[0195] A. UE.2.3 UE is configured with several options for logging duration could be in

[0196] • Seconds

[0197] • Multiple of DRX cycles

[0198] A. UE.2.4. UE is configured with several options for relation between logging and measured data• Log all measured data

[0199] • Log every N measured data

[0200] A. UE.3: UE is configured with the Execution of Logging Triggers

[0201] • UE evaluates loggingTriggerCondition using one or both of:

[0202] o AreaScope Match: Logging starts upon entering a configured Tracking Area (TA) / cell / PLMN.

[0203] o Event-based Trigger: Logging starts when conditions (e.g., A3, A2, A5) are satisfied.

[0204] A. UE.4. To elaborate on A. UE.2., reporting mechanism of UE, UE is configured with several reporting triggering mechanisms, for instance, UE

[0205] - report only if it goes into Connected mode, then no need to change any MDT standard aspect.

[0206] o enabled in legacy MDT with field onReconnection

[0207] - report logs based on pre-decided conditions, such as,

[0208] o Buffer size,

[0209] o Paging alignment,

[0210] o DRX timing,

[0211] o Time window expiry

[0212] A. UE.4.1. To elaborate on the reporting mechanism in A. UE.4., UE is configured with the following parameters in relation to reporting amount and reporting interval,

[0213] - reportAmount (Enum values: rl, r2, r4, r8,..., infinity), which define the maximum number of measurements reports the UE is allowed to send after a report trigger is satisfied. For example, if reportAmount = r4, and event A3 is triggered, UE will send 4 reports and then stop reporting, even if the event condition persists

[0214] - reportinterval — how frequently to log

[0215] A. UE.4.2. To elaborate on conditional based reporting, UE is configured with a new filed reportTriggerCondition. In this field, several reporting conditions could be embedded, including when getting into connected model (this is legacy behavior), when aligned with paging occasion, when buffer size is larger than a threshold, when elapsed timer is expired.

[0216] The above conditions are described in the following proposed MDT field (in MDT-Configuration-r 19), reportTriggerCondition,

[0217] MDT-Conf iguration-r 19:: = SEQUENCE {

[0218] reportTriggerCondition-r 19 ENUMERATED {

[0219] onReconnection, -- Default in Rel-16onPagingOccasion, -- New: UE sends UL if log ready

[0220] onLogSizeThreshold, -- New: Triggered by buffer size

[0221] onTimeExpiry -- New: Elapsed timer triggers UL

[0222] } OPTIONAL,

[0223] }

[0224] A. UE.4.2.1 Elaboration on A. UE.4.2’s Log Buffer Size trigger (onLogSizeThreshold). This trigger occurs when the UE's internal log buffer (e.g., 1000 entries or 90% full) reaches a defined threshold. The benefits of this trigger include:

[0225] • Ensures data is offloaded before loss or overwrite.

[0226] • Avoids holding stale data for too long.

[0227] • May reduce the size of uploads if done incrementally.

[0228] Such trigger can be Implemented by following the below steps:

[0229] • UE monitors buffer usage.

[0230] • If the threshold is crossed, UE can:

[0231] o Wake up at next Paging Occasion (PO),

[0232] o Send an UL signal (e.g., LoggedMeasurementAvailable)

[0233] o Wait for grant or lightweight resume.

[0234] A. UE.4.2.2 Elaboration on A. N.4.2’s Paging Occasion Trigger (onPagingOccasion) UE is already awake during a PO (to check for downlink paging), so it checks whether to send a lightweight uplink indication for logs. The benefits of this approach include:

[0235] • No new wake-up required — energy efficient.

[0236] • Enables opportunistic, DRX-aligned log delivery.

[0237] • Allows more frequent, near-real-time upload without full connection setup.

[0238] Such trigger can be Implemented by following the below steps:

[0239] • UE sets an internal flag if logs are ready.

[0240] • During PO, if no downlink message is detected, UE transmits a lightweight UL message (e.g., UEInformationRequest, or new LogReportTrigger).

[0241] • gNB can respond with grant, resume, or defer.

[0242] A. UE.4.2.3 Elaboration on A. UE.4.2’s Time Window Expiry Trigger (onTimeExpiry) After a certain elapsed time (e.g., 10 minutes since first log), the UE sends a log availability notification. The benefits of this approach include:

[0243] • Ensures logs are uploaded within a useful time window for AI / ML inference.

[0244] • Avoids unnecessary retention of outdated logs.

[0245] Such trigger can be implemented by following the below steps:

[0246] • Network provides a reportTimeWindow (e.g., 600 seconds).• UE starts timer when logging begins.

[0247] • At expiry, triggers PO-aligned UL message.

[0248] A. UE.4.2.4 Potential combined report triggering policy

[0249] • Upload if logSize > X or timeWindowExpired.

[0250] • Upload only during the next PO if either is true.

[0251] This can be framed in a new IE like:

[0252] reportTriggerCondition-rl9:: = CHOICE {

[0253] onReconnection NULL, -- Default Rel-16 behavior

[0254] onLogSizeThreshold INTEGER ( 1.. 4096),

[0255] onPagingOccasion NULL,

[0256] onTimeExpiry INTEGER ( 1.. 3600 ) -- seconds

[0257] }

[0258] A. UE.4.3. Network (NW) configures the UE how to act when reporting condition is triggered, one way for UE to report is through the Paging Occasion. Hence, the UE shall follow one of the following procedures to send the data:

[0259] 1. Transit into RRC CONNECTED Mode:

[0260] 1. UE re-establishes RRC connection (e.g., RRCSetup, RRCResume)

[0261] 2. UE includes loggedMeasurementAvailable-rl6 = TRUE

[0262] 3. gNB sends UEInformationRequest

[0263] 4. UE responds with UEInformationRespon.se carrying logged data

[0264] A. UE.5. UE is configured to meet RRM requirement when logging MDT for AI / ML data collection. gNB will enforce this via strictRRMAccuracy. In one embodiment, aligning the Logged MDT framework with RAN4-defined RRM measurement requirements is beneficial; hence the following requirements are enforced:

[0265] • Measurement Accuracy Compliance - May include any one or more of the following:

[0266]

[0267] SS-RSRQ ±3 dB

[0268] SS-SINR -> ±3 dB to ±5 dB depending on SINR level

[0269] o Logged MDT measurements use same radio frequency (RF) front-end and filter settings as RRM-mode measurements.

[0270] o UE does not apply relaxed tolerances during DRX / IDLE logging.

[0271] o If lower-power logging shortcuts are taken (e.g., fewer samples), they must be flagged in metadata.

[0272] o The measurement accuracy is achieved by the required cell detection, measurement and evaluation delays (may be represented by the plurality of SynchronizationSignal Block (SSB) occasions, SSB-based Measurement Timing Configuration (SMTC) occasions, or DRX cycles) with respect to reference signals, e.g., SSB.

[0273] • Measurement Configuration Consistency - May include any one or more of the following:

[0274] o measObjectNR includes clear frequency and SSB set definitions.

[0275] o smtc is consistent.

[0276] o quantityConflg is aligned with active bands and Radio Access Technologies (RATs).

[0277] o Measurements are linked to accurate cell IDs (CGIs) and beam indices, not just ARFCNs.

[0278] o Alternatively, the above parameters or fields / information indicated by the parameters are provided by system information.

[0279] o For the purpose of logging MDT for AI / ML data collection, UE may be required to complete cell detection, measurement and evaluation with different, e.g., shorter or longer, delays than those for cell reselection.

[0280] o For a frequency layer, e.g., intra-frequency or inter-frequency, in one option, UE may perform cell detection, measurement and evaluation for logging MDT for AI / ML data collection and perform cell detection, measurement and evaluation for logging MDT for cell reselection parallelly with same or different radio measurement resources, e.g., for a FR1 UE or a FR2 UE capable of independent beam management. In another option, UE may perform cell detection, measurement and evaluation for logging MDT for AI / ML data collection and perform cell detection, measurement and evaluation for logging MDT for cell reselection sequentially with same or different radio measurement resources, e.g., for a FR2 UE capable of dependent beam management.

[0281] • Logging Fidelity and Timing - May include any one or more of the following:

[0282] o Sampling drift -> Consistent reportinterval

[0283] o Gaps in time / location -> Logging aligned with UE mobility granularity o Battery constraints -> Avoid degrading log fidelity for power reasons unless flagged

[0284] • Measurement Validity Metadata - May include any one or more of the following:

[0285] o Include log quality tags per entry or batch:

[0286] o validityFlag = {accurate, degraded, skipped}

[0287] O logContext = {IDLE, DRX, INACTIVE, CONNECTED}

[0288] • Time and Location Granularity - May include any one or more of the following:o Use positioningMethod in MDT-Configuration (e.g., Global Navigation Satellite System (GNSS) preferred)

[0289] o Add timestampDelta or coarse timeindex to each measurement entry

[0290] o Consider defining a “log epoch format” for ML traceability (e.g., {ARFCN, SSB index, RSRP, time, location})

[0291] • UE Variability and Capability Awareness - May include any one or more of the following:

[0292] o UE should signal its loggedMeasurementQualityCapability during capability exchange

[0293] o gNB configures only Al-grade MDT if UE supports strict mode

[0294] o UE reception configurations, e.g., antenna number / ports for data collection.

[0295] A. UE.6 In another embodiment, UE constructs the logged / reported input & output RSRP data as pairs or tuples, which makes it easier for AI / ML model training in the network (e.g., in the gNB).

[0296] A. UE.7. In a dependent embodiment, UE has an identification that the MDT logging session is for Al for mobility (or other purpose), e.g., aiMobilityModel in loggingPurpose-r19. This is important for the following reasons:

[0297] 1. Clarifies intent to the UE and the network: Current MDT is optimized for troubleshooting, coverage validation, or QoE diagnosis — not data science.

[0298] 2. Allows gNB to enforce stricter configurations, such as:

[0299] a) strictRRMAccuracy can default to RAN4-compliant

[0300] b) logDuringDRX may be enabled with tighter timing tolerance

[0301] c) positioningMethod (e.g., GNSS) may be mandated, not optional

[0302] 3. Guides log interpretation in post-processing

[0303] a) Al pipelines can filter and prioritize logs that were collected for this purpose. b) Avoids mixing diagnostic MDT data with Al datasets.

[0304] loggingPurpose-rl9:: = ENUMERATED {

[0305] standardMDT, -- Default MDT behavior ( Rel-16)

[0306] aiMobilityModel, -- RRM-grade logging for Al-based mobility prediction anomalyDetection, -- Triggered by ML or NW model drift

[0307] vendorcustom -- Reserved

[0308] }

[0309] A. UE.8. - Another alternative to mdt-Configuration, UE could receive above configurations in new IE in measConfig, which includes all above fields in A. UE.2. For example, A backward-compatible extension of MDT-Configuration (i.e., EnhancedMDT-Conflguration-rl9), supporting AI / ML-grade logging, DRX-aligned operation, and conditional reporting triggers.EnhancedMDT-Con figuration- r 19: = SEQUENCE {

[0310] loggingPurpose-r 19 ENUMERATED {

[0311] standardMDT, — Default MDT behavior ( Rel-16 )

[0312] aiMobilityModel, — RRM-grade logging for AI / ML mobility training anomalyDetection, — Triggered by ML dri ft or mobility anomalies

[0313] vendor Custom — Reserved for proprietary use

[0314] } OPTIONAL,

[0315] mdt-Acti vation ENUMERATED { immediateMDT, loggedMDT },

[0316] areaScope AreaScope OPTIONAL, -- Spatial restriction

[0317] positioningMethod ENUMERATED { gnss, ecid, none } OPTIONAL, measurementQuanti ties MeasQuantityResults, — SS-RSRP, SS-RSRQ, SS-SINR

[0318] loggingDuration ENUMERATED {

[0319] s 600, S 1200, S 1800, s2400, s 3000, s3600

[0320] },

[0321] report Interval ENUMERATED {

[0322] ms512, msl 024, ms2048, ms5120, ms l0240

[0323] },

[0324] loggingFrequencyList SEQUENCE ( S IZ E ( 1.. maxFreqs ) ) OF ARFCN OPTIONAL, strictRRMAccuracy BOOLEAN OPTIONAL, — Enforce TS 38. 133-grade logging

[0325] logDuringDRX BOOLEAN OPTIONAL, — New: allow DRX-aligned wake logging

[0326] logGapOf f set INTEGER ( 0..maxDRXOf fset) OPTIONAL, — New: offset relative to DRX cycle

[0327] reportTriggerCondition-r19 CHOICE {

[0328] onReconnection NULL, -- Default behavior (Rel-16)

[0329] onPagingOccasion NULL, -- New: PO-aligned reporting

[0330] onLogSizeThreshold INTEGER ( 1.. 4096), onTimeExpiry INTEGER ( 1.. 3600 ) — In seconds

[0331] } OPTIONAL

[0332] A. UE.9 - In RRC IDLE or INACTIVE, inter-frequency or inter-RAT measurement requires time where the UE suspends serving cell / carrier reception (Paging Occasion). Let us call this virtualGaps, to avoid collision with POs (waking up on serving cell / carrier).

[0333] From the perspective of the network or network node, the following network-related embodiments are provided:

[0334] Embodiments of the present disclosure enable a network node (e.g., a gNB for the following description) to proactively configure a UE, during RRC CONNECTED, as follows:

[0335] A. N.1 gNB. Configure UE to collect, log (with RRM-compliant for data-collection process for AI / ML Model training) measurements when it is in RRC IDLE or RRC INACTIVE, then report them.

[0336] A. N.2. As elaboration to A. N. L, gNB Configures the UE with data collection’s Logging (in RRC CONNECTED) Configuration information as below.

[0337] • Indicator for logging Purpose, this is for explicitly specify to the UE that the MDT logging session is for Al for mobility (or other purpose). A new field could be introduced (e.g., loggingPurpose) as in A. N.7.• loggingTriggerCondition -> When and where to log the collected data for AI / ML model: time-based, event-based (e.g., enter a TA or move X dB), etc.

[0338] o This is mapped to areaScope in MDT-Configuration, but also needs a new field like loggingTriggerCondition in ReportConfig (for logged MDT)

[0339] • logDuringDRX -> Boolean: whether to wake up briefly during DRX for logging

[0340] o Does not exist, need to introduce new field

[0341] • logGapOffset -> Offset relative to DRX cycles (or paging occasions) for micro-wakeup o Does not exist, new field is needed

[0342] • reportinterval -> Defines the frequency of log entries during logging

[0343] o exist in reportinterval in MDT-Configuration

[0344] • loggingDuration -> the Duration of collected data for AI / ML model (in seconds or DRX cycles) to continue logging

[0345] o exist in loggingDuration in MDT-Configuration

[0346] • loggingFrequencyList -> List of ARFCNs the UE should measure to collect data for AI / ML model

[0347] o exist in measObjectToAddModList in measConfig

[0348] • loggingMetrics -> Metrics to log: SS-RSRP, RSRQ, SS-SINR, etc.

[0349] o exist in measurementQuantities in MDT-Configuration; quantityConfig in measConfig

[0350] • reportTriggerCondition -> When to report logs based on condition (PO)

[0351] o Does not exist, need to propose new fields that enable this, like: onPagingOccasion, onLogSizeThreshold

[0352] • strictRRMAccuracy -> Flag to enforce RRM-compliant measurement only

[0353] o Does not exist, need to propose new field

[0354] A. N.2.1. In one Option, the configuration information described in A. N.2. can be conveyed in already existing fields, i.e., RRCReconfiguration message, using measConfig. mdt-Configuration.loggedMDT-Config as follows:

[0355] • loggingTriggerCondition can be conveyed in areaScope (which exist in MDT-Configuration inside measConfig) and eventTriggeredMeasurementList like (which exist in ReportConfig inside measConfig).

[0356] • loggingDuration can be conveyed in loggingDuration (enum: s600, s!200,...), which already exist in MDT-Configuration inside measConfig.

[0357] o It Controls how long the UE performs logging of measurements in RRC IDLE or RRC INACTIVE■ Values (enumerated): s600, sl200, sl800, etc.

[0358] ■ Starts once UE enters logging area (areaScope)

[0359] ■ UE collects measurement entries (e.g., every reportlnterval) during this time ■ After this duration, logging stops automatically

[0360] • reportinterval'. Defines the frequency of log entries during logging, and it controls how many entries are created within the logging session, and indirectly affects log size

[0361] o Values: msl024, ms2048, etc.

[0362] o If loggingDuration = s600 and reportinterval = 512 ms, ~1170 entries.

[0363] • loggingFrequencyList can be conveyed in measObjectToAddModList, which exist in MeasConfig (top-level IE in RRCReconfiguration)

[0364] • loggingMetrics can be conveyed in measurementQuantities (e.g., ss-RSRP, ss-RSRQ, ss- SINR), which exist in Quantity Config inside measConfig.

[0365] • logGapOffset, which align logging with DRX / paging cycles

[0366] A. N.2.2 Network configures UE with several methods to trigger logging, i.e., loggingTriggerCondition as in A. N.2., could be:

[0367] • Periodical logging

[0368] • Conditional (event based) logging

[0369] As described above, the proposed information loggingTriggerCondition, could be embedded in:

[0370] - areaScope, which indicates spatial region (spatial filter) where the UE is allowed to log.

[0371] This will be a trigger if the UE is in listed cells (i.e., cellList), or tracking area (i.e., trackingAreaList), or PLMN (i.e., plmn-IdentityList).

[0372] - New field like “eventTriggeredMeasurementList” for inactive / Idle (called loggingTriggerCondition) which specifies the event conditions that cause logging or reporting. Example of event conditions are, A3: Neighbor becomes better than serving, A2: Serving becomes worse than threshold, A5: Serving below + neighbor above threshold. Considering A3, this can be described as follows:

[0373] reportConfigToAddModList = {

[0374] reportConfig = {

[0375] reportType = eventTriggered: {

[0376] eventld = eventA3,

[0377] triggerQuantity = ss-RSRP,

[0378] timeToTrigger = ms160,

[0379] }

[0380] }

[0381] }A. N.2.3 Network configures UE with several options for logging duration could be in • Seconds

[0382] • Multiple of DRX cycles

[0383] A. N.2.4. Network configures UE with several options for relation between logging and measured data

[0384] • Log all measured data

[0385] • Log every N measured data

[0386] A. N.3. Network configures UE to store all, the above configurations (in A. N.2) are stored by the UE and become active once it transitions to IDLE or INACTIVE.

[0387] A. N.4. To elaborate on A. N.2., reporting mechanism of UE, we propose that network configures UE with several reporting triggering mechanisms, NW configures UE to

[0388] - report only if it goes into Connected mode, then no need to change any MDT standard aspect.

[0389] o enabled in legacy MDT with field onReconnection

[0390] - report logs based on pre-decided conditions, such as,

[0391] o Buffer size,

[0392] o Paging alignment,

[0393] o DRX timing,

[0394] o Time window expiry

[0395] A. N.4.1. To elaborate on the reporting mechanism in A. N.4., the network configures the UE with the following parameters in relation to reporting amount and reporting interval,

[0396] - reportAmount (Enum values: rl, r2, r4, r8,..., infinity), which define the maximum number of measurements reports the UE is allowed to send after a report trigger is satisfied. For example, if reportAmount = r4, and event A3 is triggered, UE will send 4 reports and then stop reporting, even if the event condition persists

[0397] - reportinterval — how frequently to log

[0398] A. N.4.2. To elaborate on conditional based reporting, network (NW) configures the UE with a new filed reportTriggerCondition. In this field, NW includes several reporting conditions, including, when getting into connected model (this is legacy behavior), when aligned with paging occasion, when buffer size is larger than a threshold, when elapsed timer is expired.

[0399] The above conditions are described in the following proposed MDT field (in MDT-Configuration-r 19), reportTriggerCondition,

[0400] MDT-Configuration-rl9 SEQUENCE {reportTriggerCondition-r 19 ENUMERATED {

[0401] onReconnection, -- Default in Rel-16

[0402] onPagingOccasion, -- New: UE sends UL if log ready

[0403] onLogSizeThreshold, -- New: Triggered by buffer size

[0404] onTimeExpiry -- New: Elapsed timer triggers UL

[0405] } OPTIONAL,

[0406] }

[0407] A. N.4.2.1 Elaboration on A. N.4.2’s Log Buffer Size trigger (onLogSizeThreshold). This trigger occurs when the UE's internal log buffer (e.g., 1000 entries or 90% full) reaches a defined threshold. The benefits of this trigger include:

[0408] • Ensures data is offloaded before loss or overwrite.

[0409] • Avoids holding stale data for too long.

[0410] • May reduce the size of uploads if done incrementally.

[0411] Such trigger can be Implemented by following the below steps:

[0412] • UE monitors buffer usage.

[0413] • If the threshold is crossed, UE can:

[0414] o Wake up at next Paging Occasion (PO),

[0415] o Send an UL signal (e.g., LoggedMeasurementAvailable)

[0416] o Wait for grant or lightweight resume.

[0417] A. N.4.2. Elaboration on A. N.4.2’s Paging Occasion Trigger (onPagingOccasion) UE is already awake during a PO (to check for downlink paging), so it checks whether to send a lightweight uplink indication for logs. The benefits of this approach include:

[0418] • No new wake-up required — energy efficient.

[0419] • Enables opportunistic, DRX-aligned log delivery.

[0420] • Allows more frequent, near-real-time upload without full connection setup.

[0421] Such trigger can be Implemented by following the below steps:

[0422] • UE sets an internal flag if logs are ready.

[0423] • During PO, if no downlink message is detected, UE transmits a lightweight UL message (e.g., UEInformationRequest, or new LogReportTrigger).

[0424] • gNB can respond with grant, resume, or defer.

[0425] A. N.4.2.3 Elaboration on A. N.4.2’s Time Window Expiry Trigger (onTimeExpiry) After a certain elapsed time (e.g., 10 minutes since first log), the UE sends a log availability notification. The benefits of this approach include:

[0426] • Ensures logs are uploaded within a useful time window for AI / ML inference.

[0427] • Avoids unnecessary retention of outdated logs.

[0428] Such trigger can be Implemented by following the below steps:

[0429] • The network provides a reportTimeWindow (e.g., 600 seconds).• UE starts the timer when logging begins.

[0430] • At expiry, triggers PO-aligned UL message.

[0431] A. N.4.2.4 Potential combined report triggering policy

[0432] • Upload if logSize > X or timeWindowExpired.

[0433] • Upload only during the next PO if either is true.

[0434] This can be framed in a new IE like:

[0435] reportTriggerCondition-rl9:: = CHOICE {

[0436] onReconnection NULL, -- Default Rel-16 behavior

[0437] onLogSizeThreshold INTEGER ( 1.. 4096),

[0438] onPagingOccasion NULL,

[0439] onTimeExpiry INTEGER ( 1.. 3600 ) -- seconds

[0440] }

[0441] A. N.4.3. NW configures the UE how to act when reporting condition is triggered, one way for UE to report is through the Paging Occasion. Hence, the UE shall follow one of the following procedures to send the data:

[0442] • Transit into RRC CONNECTED Mode:

[0443] 1. UE re-establishes RRC connection (e.g., RRCSetup, RRCResume)

[0444] 2. UE includes loggedMeasurementAvailable-rl6 = TRUE

[0445] 3. gNB sends UEInformationRequest

[0446] 4. UE responds with UEInformationRespon.se carrying logged data

[0447] A. N.5. NW configures the UE to meet RRM requirement when logging MDT for AI / ML data collection. gNB will enforce this via strictRRM Accuracy. Aligning the Logged MDT framework with RAN4-defined RRM measurement requirements is crucial, hence one also needs to ensure:

[0448] • Measurement Accuracy Compliance - may include any one or more of the following:

[0449]

[0450] SS-RSRQ ±3 dB

[0451] SS-SINR -> ±3 dB to ±5 dB depending on SINR level

[0452] o Logged MDT measurements use same RF front-end & filter settings as RRM-mode measurements.

[0453] o UE does not apply relaxed tolerances during DRX / IDLE logging.

[0454] o If lower-power logging shortcuts are taken (e.g., fewer samples), they must be flagged in metadata.

[0455] • Measurement Configuration Consistency - may include any one or more of the following:

[0456] o measObjectNR includes clear frequency and SSB set definitions.o smtc (SSB Measurement Timing Configuration) is consistent.

[0457] o quantityConflg is aligned with active bands and RATs.

[0458] o Measurements are linked to accurate cell IDs (CGIs) and beam indices, not just ARFCNs.

[0459] • Logging Fidelity and Timing - may include any one or more of the following:

[0460] o Sampling drift -> Consistent reportinterval

[0461] o Gaps in time / location -> Logging aligned with UE mobility granularity o Battery constraints -> Avoid degrading log fidelity for power reasons unless flagged

[0462] • Measurement Validity Metadata - may include any one or more of the following:

[0463] o Include log quality tags per entry or batch:

[0464] o validityFlag = {accurate, degraded, skipped}

[0465] O logContext = {IDLE, DRX, INACTIVE, CONNECTED}

[0466] • Time and Location Granularity - may include any one or more of the following:

[0467] o Use positioningMethod in MDT-Configuration (e.g., GNSS preferred) o Add timestampDelta or coarse timeindex to each measurement entry

[0468] o Consider defining a “log epoch format” for ML traceability (e.g., {ARFCN, SSB index, RSRP, time, location})

[0469] • UE Variability and Capability Awareness - may include any one or more of the following:

[0470] o UE should signal its loggedMeasurementQualityCapability during capability exchange

[0471] o gNB configures only Al-grade MDT if UE supports strict mode

[0472] A. N.6 In another embodiment, UE needs to construct the logged / reported input & output RSRP data as pairs or tuples, this makes it easier for training in gNB.

[0473] A. N.7. In a dependent embodiment, NW explicitly specifies to the UE that the MDT logging session is for Al for mobility (or other purpose). This is important for the following reasons:

[0474] • Clarifies intent to the UE and the network: Current MDT is optimized for troubleshooting, coverage validation, or QoE diagnosis — not data science.

[0475] • Allows gNB to enforce stricter configurations, such as:

[0476] o strictRRMAccuracy can default to RAN4-compliant

[0477] o logDuringDRX may be enabled with tighter timing tolerance

[0478] o positioningMethod (e.g., GNSS) may be mandated, not optional

[0479] • Guides log interpretation in post-processingo Al pipelines can filter and prioritize logs that were collected for this purpose, o Avoids mixing diagnostic MDT data with Al datasets.

[0480] loggingPurpose-rl9:: = ENUMERATED {

[0481] standardMDT, -- Default MDT behavior ( Rel-16)

[0482] MDT4aiMobilityModel, -- RRM-grade logging for Al-based mobility prediction RRM4aiMobilityModel, -- RRM-grade logging for Al-based mobility prediction vendorcustom -- Reserved

[0483] A. N.8. - Another alternative to mdt-Configuration, is that NW define a new IE in measConfig, which includes all above fields in A. N.2. For example, A backward-compatible extension of MDT-Configuration (i.e., EnhancedMDT-Conflguration-r 19), supporting AI / ML-grade logging, DRX-aligned operation, and conditional reporting triggers.

[0484] EnhancedMDT-Con figuration- r 19 SEQUENCE {

[0485] loggingPurpose-r 19 ENUMERATED {

[0486] standardMDT, — Default MDT behavior ( Rel-16 )

[0487] aiMobilityModel, — RRM-grade logging for AI / ML mobility training anomalyDetection, — Triggered by ML dri ft or mobility anomalies

[0488] vendor Custom — Reserved for proprietary use

[0489] } OPTIONAL,

[0490] mdt-Acti vation ENUMERATED { immediateMDT, loggedMDT },

[0491] areaScope AreaScope OPTIONAL, -- Spatial restriction

[0492] positioningMethod ENUMERATED { gnss, ecid, none } OPTIONAL, measurementQuantities MeasQuantityResults, — SS-RSRP, SS-RSRQ, SS-SINR

[0493] loggingDuration ENUMERATED {

[0494] s 600, S 1200, S 1800, s2400, s 3000, s3600

[0495] },

[0496] report Interval ENUMERATED {

[0497] ms512, msl 024, ms2048, ms5120, ms l0240

[0498] },

[0499] loggingFrequencyList SEQUENCE ( S IZ E ( 1.. maxFreqs ) ) OF ARFCN OPTIONAL, strictRRMAccuracy BOOLEAN OPTIONAL, — Enforce TS 38. 133-grade logging

[0500] logDuringDRX BOOLEAN OPTIONAL, — New: allow DRX-aligned wake logging

[0501] logGapOf f set INTEGER ( 0..maxDRXOf fset) OPTIONAL, — New: offset relative to DRX cycle

[0502] reportTriggerCondition-r19 CHOICE {

[0503] onReconnection NULL, -- Default behavior (Rel-16)

[0504] onPagingOccasion NULL, -- New: PO-aligned reporting

[0505] onLogSizeThreshold INTEGER ( 1.. 4096), onTimeExpiry INTEGER ( 1.. 3600 ) — In seconds

[0506] } OPTIONAL

[0507] }

[0508] A. N.9 - In RRC IDLE or INACTIVE, inter-frequency or inter-RAT measurement requires time where the UE suspends serving cell / carrier reception (Paging Occasion). Let us call this virtualGaps, to avoid collision with POs (waking up on serving cell / carrier).

[0509] Figure 1 illustrates the operation of a UE 100 and a network node 102 in accordance with at least some of the embodiments described above. Optional steps / actions are represented bydashed lines / boxes. The network node 102 may be a RAN node such as, for example, a base station (e.g., a gNB) or Central Unit (CU) or Distributed Unit (DU) of a base station having a split architecture. As illustrated, while the UE 100 is in a connected state (e.g., RRC_CONNECTED), the network node 102 transmits to the UE 100, and the UE 100 receives from the network node 102, configuration information that configures the UE for RRM data collection logging in idle or inactive state (e.g., RRC IDLE or RRC INACTIVE) and associated reporting (step 104). In other words, this configuration information configures the UE to perform RRM data collection logging when the UE enters the idle or inactive state and the associated reporting. In accordance with embodiments of the present disclosure, the configuration information explicitly or implicitly indicates that the UE 100 is to perform the RRM data collection logging in accordance with strict logging accuracy requirements (e.g., the same accuracy requirements as required for RRM measurements performed by the UE 100 when in the connected state). Details regarding this configuration information are provided above and are equally applicable here. Briefly, as described above, the configuration information may include any one or more of the following configuration parameters:

[0510] • Indication of logging purpose (e.g., Al for mobility or other purpose)

[0511] • Indication of strict logging accuracy (e.g., same logging accuracy as required for RRC CONNCECTED)

[0512] • Indication to monitor triggering condition(s) for the data logging, where the triggering condition(s) indicated in the configuration information may include, for example, any one or more of the following:

[0513] o Time-based condition(s)

[0514] o Mobility event(s)

[0515] o Measurement threshold(s)

[0516] • Indication for the UE to wake up for the data collection (e.g., e.g., the UE is to wake up and log the data during DRX)

[0517] • UE offset(s) for waking up within a DRX cycle or PO (e.g., a relative delay within a DRX cycle or PO at which UE will wake up briefly to perform measurement(s))

[0518] • Timer duration (logging ends once the duration has expired)

[0519] o Logging duration could be in seconds or multiple of DRX cycles

[0520] • ARFCN(s) to which the UE 100 is to tune to perform the measurements for the data collection

[0521] • Logging metric(s) to which strict requirements are applicable

[0522] • Sampling frequency of measurements during logging• Information that controls when the UE 100 is to report the measurement results (i. e., the logged data). For example, this information may include information that indicates that the UE 100 is to report the logged data upon occurrence of a PO or when the size of the logged data reaches a certain threshold size. Additional details regarding various embodiments or options related to reporting are described above (e.g., see A. UE.4 and its sub-embodiments).

[0523] • Indication to log every measurement or every Nth measurement

[0524] The configuration parameters can be conveyed in already existing fields, i.e., RRCReconfiguration message, using measConfig.mdt-Configuration.loggedMDT-Config as described in A. N.2.1.

[0525] In one embodiment, the UE 100 can be configured to log all measured data or every Nth measured data.

[0526] In one embodiment, the UE 100 is configured to meet strict RRM requirements when logging MDT for AI / ML data collection. The network node 102 will enforce this, e.g., via strictRRMAccuracy.

[0527] In one embodiment, logging activation / deactivation is governed by configuration (e.g., prior configuration of), e.g., areaScope, measurement trigger(s), and / or duration, as described above.

[0528] Further details regarding the configuration information and now the network node 102 configures the UE 100 to perform the data collection logging and reporting when in the idle or inactive state are included above and are equally applicable here to step 104 of Figure 1.

[0529] The UE 100 stores the configuration information received in step 104 (step 106).

[0530] The UE 100 transitions to idle or inactive state, e.g., a currently specified in 3GPP NR specifications (step 107). When in the idle or inactive state, the UE 100 performs data collection logging and reporting in accordance with the received configuration information from Step 104 (step 108). More specifically, the UE 100 performs the data collection and logging by collecting and logging the data periodically or in response to certain trigger(s) (e.g., area scope match or event-based trigger) (step 108 A). The approach used for the data collection and logging may be configured by the network node 102 (e.g., as part of the configuration information of Step 104). The UE 100 reports the logged data to the network node 102 (or another network node), e.g., in accordance with associated reporting configuration parameter(s) included in the configuration information of Step 104 (step 108B). Further details regarding the data collection logging and reporting are described above and are equally applicable here to step 108.Figure 2 shows an example of a communication system 200 in accordance with some embodiments. The UE 100 may be one of the UEs 212 of Figure 2. The network node 102 may be one of the network nodes 210 of Figure 2.

[0531] In the example, the communication system 200 includes a telecommunications network 202 that includes an access network 204, such as a radio access network (RAN), and a core network 206, which includes one or more core network nodes 208. The access network 204 includes one or more access network nodes or base stations of various types, access network nodes 210A and 210B are depicted (which may be collectively referred to as network nodes 210), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 204 may include more than one access network technology. The network nodes 210 of access network 204 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 212A, 212B, 212C, and 212D (one or more of which may be generally referred to as UEs 212) to the core network 206 over one or more wireless connections.

[0532] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 202 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 202, including one or more access network nodes 210 and / or core network nodes 208.

[0533] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualizationenvironment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0534] The network nodes 210 facilitate direct or indirect connection of one or more UEs 212 to the core network 206 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 200 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 200 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0535] The UEs 212 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 210 and other communication devices. Similarly, the network nodes 208, 210 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 202) with the UEs 212 and / or with other network nodes or equipment in the telecommunications network 202 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 202. More specifically, UEs 212 may send messages, data, and / or other signals to network nodes 208, 210 or other elements of the telecommunications network 202 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 208, 210 may send messages, data, and other signals to UEs 212, other network nodes 208, 210, and other devices in telecommunications network 202 directly or indirectly. As one specific example, a core network node 208 may transmit a particular message to a UE 212 by transmitting the message to an access network node 210 that will then transmit the message to the intended UE 212. Similarly, a core network node 208 may receive a particular message from a UE 212 by receiving the message from an access network node 210 that itself received the message from the UE 212.In the depicted example, the core network 206 connects elements of the access network 204 (e.g., one or more of the network nodes 210) to one or more host computing systems, such as host 216. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 206 includes one or more core network nodes (e.g., core network node 208) of various types, one or more of which may be generally referred to as network nodes 208. Network nodes 208 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 208. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0536] The host 216 may be under the ownership or control of a service provider other than an operator or provider of the access network 204 and / or the telecommunications network 202. The host 216 may be operated by the service provider or on behalf of the service provider. The host 216 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0537] As a whole, the communication system 200 of Figure 2 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 200 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN)standards such as LoRa and Sigfox. Moreover, the communication system 200 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 200 supporting different standards, protocols, or rule sets.

[0538] As one example, in certain embodiments, access network 204 may contain some access network nodes 210 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 210 support (or the same access network nodes 210 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 202 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 204 and / or a core network 206 that supports multiple different standard generations or may include multiple access networks 204 and / or multiple core networks 206 with individual networks 204, 206 supporting different standard generations.

[0539] Telecommunications network 202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 202. For example, the telecommunications network 202 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0540] In some examples, one or more of the UEs 212 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 204. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0541] In the example, the hub 214 communicates with the access network 204 to facilitate indirect communication between one or more UEs (e.g., UE 212C and / or 212D) and network nodes (e.g., network node 210B). In some examples, the hub 214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 214 may be a broadband router enabling access to the core network 206 for the UEs. As another example, the hub 214 may be a controller that sends commands or instructions toone or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 210, or by executable code, script, process, or other instructions in the hub 214.

[0542] As another example, the hub 214 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 214 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 214 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0543] The hub 214 may have a constant / persistent or intermittent connection to the network node 210B. The hub 214 may also allow for a different communication scheme and / or schedule between the hub 214 and UEs (e.g., UE 212C and / or 212D), and between the hub 214 and the core network 206. In other examples, the hub 214 is connected to the core network 206 and / or one or more UEs via a wired connection. Moreover, the hub 214 may be configured to connect to an M2M service provider over the access network 204 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 210 while still connected via the hub 214 via a wired or wireless connection. In some embodiments, the hub 214 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 210B. In other embodiments, the hub 214 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 210B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0544] Figure 3 is another example of a communication system 300 according to some embodiments. As used herein, the communication system 300 includes multiple access points (APs) 310 (with four exemplary APs 310A, 310B, 310C, and 310D being depicted) and multiple wireless devices, referred to in the context of communication system 300 as stations (STAs) 312 (referred to individually as STA 312A, STA 312B, STA 312C, STA 312D, and STA 312E). STA 312Ais served by AP 310A in a first basic service set (BSS) 320 A. STA 312B and STA 312C are served by AP 310B in a second BSS, BSS 320B. STA 312D is served by AP 310C in a third BSS, BSS 320C. STA 312E is served by AP 310D in a fourth BSS, BSS 320D. Stations 312 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for AugmentedReality (AR) or Virtual Reality (VR), or the like. Further, stations 312 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0545] Each of STAs 312 may connect through a radio link to one of APs 310. For example, depending on location or channel conditions experienced by a given STA 312, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0546] Each AP 310 may provide data connectivity to STAs 312 connected to a particular AP 310. As illustrated, APs 310 may be connected to a data network 330. In this way, APs 310 may also provide data connectivity between STAs 312 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 312 and its serving AP 310 may be used for providing various kinds of services to STA 312, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 312 and / or on a device linked to STA 312. By way of example, Figure 3 illustrates an application service platform 332 provided in data network 330. The application(s) executed on STA 312 and / or on one or more other devices linked to STA 312 may use the radio link for data communication with one or more other STA 312 and / or the application service platform 332, thereby enabling utilization of the corresponding service(s) at STA 312.

[0547] Figure 4 shows a wireless device 400, which may be configured to operate in communication system 200 of Figure 2 or in communication system 300 of Figure 3. The wireless device 400 may be alternatively referred to as a UE 400, like a UE 212 within the context of communication system 200, or as a station (STA) 400 or as a non-access-point station (non-AP STA) 400, like a STA 312 within the context of the communication system 300, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smartdevice, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0548] A wireless device 400 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 400 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 400 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 400 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0549] In particular embodiments, wireless device 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a power source 408, a memory 410, a communication interface 412, and / or any other component, or any combination thereof. Certain embodiments of wireless device 400 may include all or a subset of the components shown in Figure 4. The level of integration between the components may vary from one embodiment of wireless device 400 to another. In general, in a particular embodiment of wireless device 400, processing circuitry 402, input / output interface 406, power source 408, memory 410, and communication interface 412 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 400. Further, certain embodiments of wireless devices 400 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0550] The processing circuitry 402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 410. The processing circuitry 402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), togetherwith appropriate software; or any combination of the above. For example, the processing circuitry 402 may include multiple central processing units (CPUs).

[0551] In the example, the input / output interface 406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 400. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0552] In some embodiments, the power source 408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 408 may further include power circuitry for delivering power from the power source 408 itself, and / or an external power source, to the various parts of wireless device 400 via input circuitry or an interface such as an electrical power cable. Power source 408 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 400 to which power is supplied.

[0553] The memory 410 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 410 includes one or more programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416. The memory 410 may store, for use by wireless device 400, any of a variety of various operating systems or combinations of operating systems.

[0554] The memory 410 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical discdrive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 410 may allow wireless device 400 to access instructions, programs, and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 410, which may be or comprise a device-readable storage medium.

[0555] The processing circuitry 402 may be configured to communicate with an access network or other network via or using the communication interface 412. The communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422. The communication interface 412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 418 and / or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., antenna 422) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0556] In the illustrated embodiment, communication functions of the communication interface 412 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.In particular embodiments, wireless device 400 may provide an output of data captured via a sensor, through its communication interface 412, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 400 can be communicated through a wireless connection to a network node via another wireless device 400. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0557] As another example, wireless device 400 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 400 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0558] Wireless device 400, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 400 represents an IoT device that comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the example embodiment of wireless device 400 shown in Figure 4.

[0559] As yet another specific example, in an IoT scenario, wireless device 400 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 400 may in this case be an M2M device, which may in a 3GPP context be referredto as an MTC device. As one particular example, wireless device 400 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 400 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0560] In practice, any number of wireless devices 400 may be used together with respect to a single use case. For example, a first wireless device 400 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 400 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 400 may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 400 can also include more than one of the functionalities described above. For example, wireless device 400 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0561] Figure 5 shows a network node 500 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 500 may be configured to operate in communication system 200 of Figure 2, like network nodes 208 or 210, or in communication system 300 of Figure 3, like an AP 310 or a station 312. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0562] Network nodes 500 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 500 may be a relay node or a relay donor node controlling a relay. Network nodes 500 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0563] Other examples of network nodes 500 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers suchas radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O& M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0564] In particular embodiments, network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508. In general, in a particular embodiment of network node 500, processing circuitry 502, memory 504, communication interface 506, and power source 508 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 500.

[0565] The network node 500 may be composed of multiple distinct network entities (e.g., a NodeB entity and an RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 500 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 504 or portions of memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs). The network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same chip or different chips or set of chips and other components within network node 500.

[0566] The processing circuitry 502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 504, to provide network node 500 functionality.

[0567] In some embodiments, the processing circuitry 502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 502 includes one or more of radio frequency (RF)transceiver circuitry 512 and baseband processing circuitry 514. In some embodiments, the RF transceiver circuitry 512 and the baseband processing circuitry 514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 512 and baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.

[0568] The memory 504 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 502. The memory 504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and / or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and memory 504 are integrated.

[0569] The communication interface 506 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 506 comprises port(s) / terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 400 may be capable of wireless communication and communication interface 506 may also include radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, an antenna 510. Particular embodiments of radio front-end circuitry 518 include filter(s) 520 and amplifier(s) 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio front-end circuitry may be configured to condition signals communicated between antenna 510 and processing circuitry 502. The radio front-end circuitry 518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 518 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 520 and / or amplifiers 522. The radio signal(s) may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502.In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0570] In certain alternative embodiments, network node 500 may be capable of wireless communication but does not include separate radio front-end circuitry 518, instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512, as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).

[0571] The antenna 510 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 510 is separate from the network node 500 and connectable to the network node 500 through one or more interfaces or ports.

[0572] The antenna 510, communication interface 506, and / or the processing circuitry 502 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 500. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 510, the communication interface 506, and / or the processing circuitry 502 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 500. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0573] The power source 508 provides power to the various components of network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein. For example, the network node 500 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 508. As a further example, the power source 508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.Embodiments of the network node 500 may include additional components beyond those shown in Figure 5 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.

[0574] Figure 6 is a block diagram illustrating a virtualization environment 600 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0575] Applications 602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 600 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0576] Hardware 604 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 608A and VM 608B (which may be collectively referred to as VMs 608), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 606 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 608.The VMs 608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 606. Different embodiments of the instance of a virtual appliance 602 may be implemented on one or more of VMs 608, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0577] In the context of NFV, each of the VMs 608 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 608, and that part of hardware 604 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 608 on top of the hardware 604 and corresponds to an application 602.

[0578] Hardware 604 may be implemented in a standalone network node with generic or specific components. Hardware 604 may implement some functions via virtualization. Alternatively, hardware 604 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 610, which, among others, oversees lifecycle management of applications 602. In some embodiments, hardware 604 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 612 which may alternatively be used for communication between hardware nodes and radio units.

[0579] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information storedin the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0580] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0581] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0582] Group A Embodiments

[0583] Embodiment 1: A method performed by a User Equipment, UE, (100) for data collection logging when in an idle or inactive state and associated reporting, the method comprising: receiving (104), from a network node (102), configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitly indicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state; storing (106) theconfiguration information at the UE (100); transitioning (107) to the idle or inactive state; and, while in the idle or inactive state, performing (108) radio resource management data collection logging and associated reporting, in accordance with the received configuration information.

[0584] Embodiment 2: The method of embodiment 1, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to when such configuration information does not comprise information that explicitly or implicitly indicates one or more increased accuracy requirements.

[0585] Embodiment 3: The method of embodiment 1, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to default accuracy requirements for radio resource management data collection logging when in the idle or inactive state.

[0586] Embodiment 4: The method of embodiment 1, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements that are the same as accuracy requirements for radio resource management data collection logging when in a connected state.

[0587] Embodiment 5: The method of any of embodiments 1 to 4, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises an indication of a logging purpose (e.g., AI for mobility or another purpose).

[0588] Embodiment 6: The method of any of embodiments 1 to 5, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises an explicit indication of strict logging accuracy.

[0589] Embodiment 7: The method of any of embodiments 1 to 6, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises any one or more of the following: an indication to monitor triggering condition(s) for logging of the radio resource management data; one or more time-based conditions related to (e.g., triggering) logging of the radio resource management data; an indication of one or more mobility events related to (e.g., triggering) logging of the radio resource management data; one or more measurement thresholds (e.g., related to logging of the radio resource management data); an indication for the UE (100) to wake up for data collection (e.g., log during DRX); one or more UE offsets (e.g., time offset(s)) for waking up within a DRX cycle or paging occasion to perform and log the radio resource management data (e.g., a relative delay within a DRX cycle or paging occasion at which the UE (100) is to wake up to perform measurement(s)); an indication of a duration of time over which the radio resource managementdata collection logging is to be performed (e.g., end logging once the duration of time has expired); one or more ARFCN(s) to which the UE (100) is to tune to perform measurements for the radio resource management data collection logging; information that indicates one or more logging metrics; information that indicates one or more logging metrics to which strict requirements are applicable; information that indicates a sampling frequency of measurements during the logging; information that controls when the UE (100) is to report the logged data (e.g., one or more conditions that define when the UE (100) is to report the logged data).

[0590] Embodiment 8: The method of any of embodiments 1 to 7, wherein the configuration information is received in one or more fields (e.g., one or more fields in an RRC Reconfiguration message).

[0591] Embodiment 9: The method of any of embodiments 1 to 8, wherein the configuration information configures the UE to report the logged data either periodically or based on one or more event-based triggers.

[0592] Embodiment 10: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

[0593] Group B Embodiments

[0594] Embodiment 11: A method performed by a network node (102) for configuring a User Equipment, UE, (100) for radio resource management data collection logging when in idle or inactive state and associated reporting, the method comprising: transmitting (104), to a UE (100), configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitly indicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state.

[0595] Embodiment 12: The method of embodiment 11, further comprising receiving (108B), from the UE (100), a report comprising radio resource management data collected and logging by the UE (100) when in the idle or inactive state, in accordance with the configuration information.

[0596] Embodiment 13: The method of embodiment 11 or 12, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to when such configuration information does not comprise information that explicitly or implicitly indicates one or more increased accuracy requirements.Embodiment 14: The method of embodiment 11 or 12, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to default accuracy requirements for radio resource management data collection logging when in the idle or inactive state.

[0597] Embodiment 15: The method of embodiment 11 or 12, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements that are the same as accuracy requirements for radio resource management data collection logging when in a connected state.

[0598] Embodiment 16: The method of any of embodiments 11 to 15, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises an indication of a logging purpose (e.g., AI for mobility or another purpose).

[0599] Embodiment 17: The method of any of embodiments 11 to 16, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises an explicit indication of strict logging accuracy.

[0600] Embodiment 18: The method of any of embodiments 11 to 17, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises any one or more of the following: an indication to monitor triggering condition(s) for logging of the radio resource management data; one or more time-based conditions related to (e.g., triggering) logging of the radio resource management data; an indication of one or more mobility events related to (e.g., triggering) logging of the radio resource management data; one or more measurement thresholds (e.g., related to logging of the radio resource management data); an indication for the UE (100) to wake up for data collection (e.g., log during DRX); one or more UE offsets (e.g., time offset(s)) for waking up within a DRX cycle or paging occasion to perform and log the radio resource management data (e.g., a relative delay within a DRX cycle or paging occasion at which the UE (100) is to wake up to perform measurement(s)); an indication of a duration of time over which the radio resource management data collection logging is to be performed (e.g., end logging once the duration of time has expired); one or more ARFCN(s) to which the UE (100) is to tune to perform measurements for the radio resource management data collection logging; information that indicates one or more logging metrics; information that indicates one or more logging metrics to which strict requirements are applicable; information that indicates a sampling frequency of measurements during the logging; information that controls when the UE (100) is to report the logged data (e.g., one or more conditions that define when the UE (100) is to report the logged data).Embodiment 19: The method of any of embodiments 11 to 18, wherein the configuration information is received in one or more fields (e.g., one or more fields in an RRC Reconfiguration message).

[0601] Embodiment 20: The method of any of embodiments 11 to 19, wherein the configuration information configures the UE to report the logged data either periodically or based on one or more event-based triggers.

[0602] Embodiment 21: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0603] Group C Embodiments

[0604] Embodiment 22: A User Equipment, UE, comprising: processing circuitry configured to perform any of the operations of any of the Group A embodiments; and a power source configured to supply power to the processing circuitry.

[0605] Embodiment 23: A network node comprising: processing circuitry configured to perform any of the operations of any of the Group B embodiments; and a power source circuitry configured to supply power to the processing circuitry.

[0606] Embodiment 24: A User Equipment, UE, comprising: one or more antennas; communication interface connected to the one or more antennas and to processing circuitry; the processing circuitry being configured to perform any of the operations of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the UE.

Claims

CLAIMS1. A method performed by a User Equipment, UE, (100) for data collection logging when in an idle or inactive state and associated reporting, the method comprising:receiving (104), from a network node (102), configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitly indicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state;storing (106) the configuration information at the UE (100);transitioning (107) to the idle or inactive state;while in the idle or inactive state, performing (108) radio resource management data collection logging and associated reporting, in accordance with the received configuration information.

2. The method of claim 1, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to when such configuration information does not comprise information that explicitly or implicitly indicates one or more increased accuracy requirements.

3. The method of claim 1, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to default accuracy requirements for radio resource management data collection logging when in the idle or inactive state.

4. The method of claim 1, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements that are the same as accuracy requirements for radio resource management data collection logging when in a connected state.

5. The method of any of claims 1 to 4, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises an indication of a logging purpose.

6. The method of any of claims 1 to 5, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises an explicit indication of strict logging accuracy.

7. The method of any of claims 1 to 6, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises any one or more of the following:an indication to monitor one or more triggering conditions for logging of the radio resource management data;one or more time-based conditions related to logging of the radio resource management data;an indication of one or more mobility events related to logging of the radio resource management data;one or more measurement thresholds related to logging of the radio resource management data;an indication for the UE (100) to wake up for data collection during discontinuous reception, DRX, operation;one or more UE offsets for waking up within a DRX cycle or paging occasion to perform and log the radio resource management data;an indication of a duration of time over which the radio resource management data collection logging is to be performed;one or more absolute radio frequency channel numbers to which the UE (100) is to tune to perform measurements for the radio resource management data collection logging;information that indicates one or more logging metrics;information that indicates one or more logging metrics to which strict requirements are applicable;information that indicates a sampling frequency of measurements during the logging; information that controls when the UE (100) is to report the logged data.

8. The method of any of claims 1 to 7, wherein the configuration information is received in one or more fields in message.

9. The method of any of claims 1 to 8, wherein the configuration information configures the UE to report the logged data either periodically or based on one or more event-based triggers.

10. A User Equipment, UE, (100; 400) for data collection logging when in an idle or inactive state and associated reporting, the UE (100; 400) comprising:a communication interface (412) comprising a transmitter (418) and a receiver (420); and processing circuitry (402) associated with the communication interface (412), the processing circuitry (402) configured to cause the UE (100; 400) to:receive (104), from a network node (102), configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitly indicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state;store (106) the configuration information at the UE (100);transition (107) to the idle or inactive state;while in the idle or inactive state, perform (108) radio resource management data collection logging and associated reporting, in accordance with the received configuration information.

11. A method performed by a network node (102) for configuring a User Equipment, UE, (100) for radio resource management data collection logging when in idle or inactive state and associated reporting, the method comprising:transmitting (104), to a UE (100), configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitly indicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state.

12. The method of claim 11, further comprising receiving (108B), from the UE (100), a report comprising radio resource management data collected and logging by the UE (100) when in the idle or inactive state, in accordance with the configuration information.

13. The method of claim 11 or 12, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements as compared to when such configuration information does not comprise information that explicitly or implicitly indicates one or more increased accuracy requirements.

14. The method of claim 11 or 12, wherein the one or more accuracy requirements compriseone or more increased accuracy requirements as compared to default accuracy requirements for radio resource management data collection logging when in the idle or inactive state.

15. The method of claim 11 or 12, wherein the one or more accuracy requirements comprise one or more increased accuracy requirements that are the same as accuracy requirements for radio resource management data collection logging when in a connected state.

16. The method of any of claims 11 to 15, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises an indication of a logging purpose.

17. The method of any of claims 11 to 16, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises an explicit indication of strict logging accuracy.

18. The method of any of claims 11 to 17, wherein the configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state comprises any one or more of the following:an indication to monitor triggering condition(s) for logging of the radio resource management data;one or more time-based conditions related to (e.g., triggering) logging of the radio resource management data;an indication of one or more mobility events related to (e.g., triggering) logging of the radio resource management data;one or more measurement thresholds (e.g., related to logging of the radio resource management data);an indication for the UE (100) to wake up for data collection (e.g., log during DRX); one or more UE offsets (e.g., time offset(s)) for waking up within a DRX cycle or paging occasion to perform and log the radio resource management data (e.g., a relative delay within a DRX cycle or paging occasion at which the UE (100) is to wake up to perform measurement(s));an indication of a duration of time over which the radio resource management data collection logging is to be performed (e.g., end logging once the duration of time has expired);one or more ARFCN(s) to which the UE (100) is to tune to perform measurements for the radio resource management data collection logging;information that indicates one or more logging metrics;information that indicates one or more logging metrics to which strict requirements are applicable;information that indicates a sampling frequency of measurements during the logging; information that controls when the UE (100) is to report the logged data (e.g., one or more conditions that define when the UE (100) is to report the logged data).

19. The method of any of claims 11 to 18, wherein the configuration information is received in one or more fields.

20. The method of any of claims 11 to 19, wherein the configuration information configures the UE to report the logged data either periodically or based on one or more event-based triggers.

21. A network node (102; 500) for configuring a User Equipment, UE, (100) for radio resource management data collection logging when in idle or inactive state and associated reporting, the network node (102; 500) comprising processing circuitry (502) configured to cause the network node (102; 500) to:transmit (104), to a UE (100), configuration information that configures the UE (100) to perform radio resource management data collection logging when in the idle or inactive state and associated reporting, the configuration information comprising information that explicitly or implicitly indicates one or more accuracy requirements for the radio resource management data collection logging when in the idle or inactive state.