User equipment communicating data to network across different radio resource control (RRC) states to support artificial intelligence model

Abstract

The application relates to coordination between a UE and a network for collection of data by the UE and use of the data by a model hosted by the network. In one example, a network configures a UE to perform and record MDT measurements for a model. The UE may be configured to do so across all RRC states, including the RRCCONNECTED state. The UE may also be configured to report such logged MDT measurements in more than one state, such as in an RRCINACTIVE state in addition to an RRCCONNECTED state.

Description

Technical Field

[0001] This application relates generally to network communications, and more specifically to user equipment transmitting data to a network across different Radio Resource Control (RRC) states to support artificial intelligence models. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) Technical Specifications (TS) define standards for wireless networks. These standards may include, for example, Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and other standards. Attached Figure Description

[0003] Figure 1 Examples of network environments based on some implementation schemes are provided.

[0004] Figure 2 An example is illustrated where a user equipment (UE) transmits data to a network for use by a network-hosted model, according to some implementation schemes.

[0005] Figure 3 Examples of Radio Resource Control (RRC) states according to some implementation schemes are illustrated.

[0006] Figure 4 Examples of components for configuring a UE to transmit data to a network, according to some implementation schemes, are illustrated.

[0007] Figure 5 Examples of UEs transmitting data to the network in the RRC_IDLE and RRC_INACTIVE states according to some implementation schemes are illustrated.

[0008] Figure 6 An example is shown of a UE transmitting data to the network in all RRC states according to some implementation schemes.

[0009] Figure 7 An example sequence diagram is shown, according to some implementation schemes, for configuring a UE to transmit data to the network in all RRC states for artificial intelligence / machine learning purposes.

[0010] Figure 8 Examples of operational flow / algorithm structures implemented by the UE for transmitting data to the network in all RRC states are illustrated according to some implementation schemes.

[0011] Figure 9 Examples of operational flow / algorithm structures implemented by the network according to some implementation schemes for configuring a UE to transmit data to the network in all RRC states are illustrated.

[0012] Figure 10Examples of receiving components according to some implementation schemes are shown.

[0013] Figure 11 Examples of UEs according to some implementation schemes are shown.

[0014] Figure 12 Examples of base stations based on some implementation schemes are shown. Detailed Implementation

[0015] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as particular structures, architectures, interfaces, and techniques, are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases “A / B” and “A or B” refer to (A), (B), or (A and B); and the phrase “based on A” means “at least partially based on A,” for example, it can be “based solely on A” or it can be “partially based on A.”

[0016] This disclosure relates to the coordination between a User Equipment (UE) and a network for the use of data collected by the UE and by a model hosted by the network. This model may be an artificial intelligence (AI) model that provides network functions such as channel state information (CSI) feedback, beam management, positioning, etc. (In one example, the AI ​​model may be a machine learning (ML) model). In one example, the data includes Minimum Driven Test (MDT) data. Coordination may include the network configuring the UE to perform measurements and record relevant measurement data across different Radio Resource Control (RRC) states, including the RRC_CONNECTED state. This configuration may indicate the timing for initiating measurements for recording and / or the measurement events used for recording. The configuration may also indicate specific measurements to be performed (e.g., per-beam measurements) and / or enable the UE to report unspecified measurements or data in a transparent container. Furthermore, the UE may record measurements in memory buffers (e.g., access layer (AS) buffers and / or application buffers). If the size of the memory buffer exceeds a threshold, the UE can transmit the recorded measurements even when it is in the RRC_INACTIVE state (e.g., by using Measurement Object Short Data Transmission (MO-SDT)). These and other features are described further below.

[0017] The embodiments disclosed herein offer various technical advantages. For example, logging data when the UE is in the RRC_CONNECTED state supports use cases of AI and / or ML models that require continuous measurements across all RRC states (e.g., for AI / ML-based positioning) or improve training on such models (e.g., by using continuous data samples). Furthermore, logging data across all RRC states enables continuous log measurements, rather than discontinuous measurements (e.g., when the UE is in a specific RRC state, such as the RRC_CONNECTED state). Continuous log measurements support potentially timing-sensitive AI / ML use cases (e.g., beam prediction use cases). Additionally, the UE can be configured with explicit or implicit measurement ranges that may extend beyond measurements with only a configured list of cell identifiers (IDs), tracking area codes (TACs), or frequency lists. This provides support for AI / ML use cases that may target beam lists (e.g., for beam prediction or CSI prediction). The embodiments also enable the collection of different types and quantities of data (even data that can be dynamically specified by the operator). Doing so supports a wider range of AI / ML use cases and / or improves AI / ML training. It also provides the flexibility to handle any available memory buffer of a limited size, allowing the UE to still record relevant data.

[0018] For clarity, various implementations of this disclosure are described in conjunction with MDT data and specific AI / ML use cases (e.g., beam prediction, CSI feedback, localization). However, the implementations are not limited thereto, but are equivalently and similarly applicable to any type of data and any AI / ML use case that relies on that data.

[0019] The following is a glossary of terms that may be used in this disclosure.

[0020] As used herein, the term "circuit" refers to, is part of, or includes a hardware component configured to provide the described functionality. Hardware components may include electronic circuitry, logic circuitry, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), or digital signal processors (DSPs). In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or combinations of circuits used in electrical or electronic systems) and program code for executing the functionality. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0021] As used herein, the term "processor circuit" means a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data; a part of a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data; or includes circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0022] As used herein, the term "interface circuit" refers to circuitry that enables the exchange of information between two or more components or devices, a portion thereof, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, and network interface cards.

[0023] As used herein, the term "user equipment" or "UE" refers to equipment having radio communication capabilities that allow a user to access network resources within a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Furthermore, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0024] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0025] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database and application, or workload unit. "Hardware resource" can refer to computing, storage, or network resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or network resources provided by virtualization infrastructure to an application, device, or system. The terms "network resource" or "communication resource" can refer to resources accessible by a computer device / system via a communication network. The term "system resource" can refer to any kind of shared entity providing a service and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0026] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to transmit data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a means or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of transmitting and receiving information.

[0027] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0028] The term "connection" can refer to an established signaling relationship between two or more elements at a common communication protocol layer through a communication channel, link, interface, or reference point.

[0029] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, network hardware, network equipment, network node, or virtualized network function.

[0030] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0031] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include UE 104 and gNB 108. gNB 108 may be a base station providing a radio access cell, for example, UE 104 may communicate with gNB 108 through a 3GPP New Radio (NR) cell. UE 104 and gNB 108 may communicate through an air interface compatible with 3GPP technical specifications, such as those defining the fifth-generation (5G) NR system standard.

[0032] The gNB 108 transmits information (e.g., data and control signaling) in the downlink direction by mapping logical channels to transport channels and transport channels to physical channels. Logical channels transmit data between the Radio Link Control (RLC) and MAC layers; transport channels transmit data between the MAC and PHY layers; and physical channels transmit information across the air interface. Physical channels may include the Physical Broadcast Channel (PBCH), the Physical Downlink Control Channel (PDCCH), and the Physical Downlink Shared Channel (PDSCH).

[0033] The PBCH can be used to broadcast system information that UE 104 can use for initial access to the serving cell. The PBCH can be transmitted together with the Physical Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS) in the Synchronization Signal (SS) / PBCH block. During the cell search process (including cell selection and reselection) and for beam selection, UE 104 can use the SS / PBCH block (SSB).

[0034] PDSCH can be used to transmit end-user application data, signaling radio bearer (SRB) messages, system information messages (except for MIBs), and paging messages.

[0035] The PDCCH can transmit DCIs used by the gNB 108 scheduler to allocate both uplink and downlink resources. DCIs can also be used to provide uplink power control commands, configure time slot formats, or indicate that preemption has occurred.

[0036] gNB 108 can also transmit various reference signals to UE 104. Reference signals may include DMRS for PBCH, PDCCH, and PDSCH. UE 104 can compare the received version of the DMRS with a known sequence of transmitted DMRS to estimate the impact of the propagation channel. UE 104 can then apply the inverse channel of the propagation channel during the demodulation process transmitted on the corresponding physical channel. UE 104 can similarly transmit various reference signals, including, for example, DMRS, to gNB 108 for processing in association with uplink channels (e.g., Physical Uplink Control Channel (PUCCH) and Physical Uplink Shared Channel (PUSCH)).

[0037] The reference signal may also include a Channel State Information Reference Signal (CSI-RS). The CSI-RS can be a multipurpose downlink transmitter that can be used for CSI reporting, beam management, connection mode mobility, radio link failure detection, beam failure detection and recovery, and fine-tuning of time and frequency synchronization.

[0038] Reference signals and information from the physical channel can be mapped to resources in the resource grid. For a given antenna port, subcarrier spacing configuration, and transmission direction (e.g., downlink or uplink), there exists a resource grid. The basic unit of the NR downlink resource grid can be a resource element, which can be defined by a subcarrier in the frequency domain and an orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain can constitute a physical resource block (PRB). A resource element group (REG) can include a PRB in the frequency domain and an OFDM symbol in the time domain, for example, twelve resource elements. A control channel element (CCE) can represent a resource group used to transmit the PDCCH. One CCE can be mapped to multiple REGs, for example, six REGs.

[0039] UE 104 can use physical uplink channels to send data and control information to gNB 108. Different types of physical uplink channels are possible, including, for example, PUCCH and PUSCH. PUCCH carries control information from UE 104 to gNB 108, such as uplink control information (UCI), while PUSCH carries data traffic (e.g., end-user application data) and may carry UCI.

[0040] UE 104 and gNB 108 can perform beam management operations to identify and maintain the desired beams for transmission in both the uplink and downlink directions. Beam management can be applied to both PDSCH and PDCCH in the downlink direction and both PUSCH and PUCCH in the uplink direction.

[0041] In one example, communication with the gNB 108 and / or the base station can utilize channels in the Frequency Range 1 (FR1) band, the Frequency Range 2 (FR2) band, and / or the High Frequency Range (FRH) band. The FR1 band includes both licensed and unlicensed frequency bands. The NR unlicensed band (NR-U) includes spectrum shared with other types of Radio Access Technologies (RATs) (e.g., LTE-LAA, WiFi, etc.). A Listen-Before-Speak (LBT) process can be used to avoid or minimize conflicts between different RATs in the NR-U, whereby the device should apply a Clear Channel Assessment (CCA) check before using the channel.

[0042] although Figure 1Not illustrated, network environment 100 may include other network components. For example, network environment 100 may use various radio access networks (RANs) to enable communication between the UE (e.g., UE 104) and the RAN's base station (e.g., NB 108) (which may sometimes be collectively referred to as RAN nodes, network nodes, or simply nodes). For 5G-NR, the 3GPP RAN may be referred to as the Next Generation Radio Access Network (NG-RAN).

[0043] Each RAN can use one or more Radio Access Technologies (RATs) to perform communication between the base station and the UE. For example, the NG-RAN implements the NR RAT (sometimes referred to in this document as the 5G RAT, 5G NR RAT, or simply NR). In some deployments, the NG-RAN may also implement the Long Term Evolution (LTE) RAT.

[0044] The base station used by the RAN (e.g., gNB 108) can correspond to the RAN. The RAN provides communication services with external entities through its connection to the core network (CN). For example, the NG-RAN can utilize the 5G core network (5GC). As used herein, "network" can refer to any or a combination of a base station, RAN, or CN.

[0045] For clarity, various embodiments of this disclosure are described in the context of 5G NR. However, the embodiments are not limited thereto and are similarly and equivalently applicable to other wireless communication systems, such as 4G LTE / LTE-A, or various wireless communication systems to be developed in the future. Equivalents of the architectures, entities, functions, and processes described herein can be found in these communication systems. Various embodiments are also described in relation to the UE. However, references to the UE are provided for illustrative purposes only. Example embodiments may be used with any electronic components that can establish a connection to a network and utilize hardware, software, and / or firmware configurations for exchanging information and data with the network. Therefore, the UE as described herein is used to refer to any suitable electronic component. Examples of UEs may include mobile devices, personal digital assistants (PDAs), tablet computers, laptop computers, personal computers, Internet of Things (IoT) devices, or machine-type communication (MTC) devices, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.

[0046] Figure 2 Example 200 illustrates a UE 210 transmitting data to a network 250 for use by a model 232 hosted by the network 250, according to some implementation schemes. In the example, UE 210 ( Figure 1 Example of UE 104) and base station 220 ( Figure 1(Example of gNB 108) is communicatively coupled, and the base station may be a component of the RAN of network 250. The network also includes a destination node 230 (e.g., a server, which may be part of the core network), which hosts model 232 as executable program code. Model 232 may support specific network functions (such as CSI feedback, beam management, positioning, etc.) and may be implemented as an AI model (or, in a specific example, as an ML model). Model 232 is referred to herein as an AI / ML model.

[0047] In one example, the data is MDT data and may take the form of a recorded measurement report 212 that can be transmitted by UE 210. For this purpose, network 250 may transmit MDT configuration 222 to UE 210 via base station 220. MDT configuration 222 may define various parameters for performing, recording, and / or reporting MDT measurements. These parameters may instruct UE 210 to perform and record MDT measurements in different RRC states (including, for example, RRC_CONNECTED state), the timing for starting recording, the measurement-based events for starting and / or ending recording, the different types of measurements to be performed, the different types of data to be included in the recorded measurement report 212, and / or the mechanisms for transmitting the recorded measurement report 212. These and other parameters are further described below.

[0048] Generally, AI / ML models can be implemented as machines or systems capable of simulating human intelligence and behavior. Different types of AI / ML models are possible, including, for example, neural networks (NNs), such as convolutional neural networks (CNNs), recurrent / recurrent neural networks (RNNs), generative adversarial networks (GANs), etc. Air interface designs can be extended to support improvements to AI / ML models to enhance performance and / or reduce complexity / overhead. Performance enhancements depend on the use case considered and can be, for example, improved throughput, robustness, accuracy, or reliability. Use cases may include CSI feedback enhancements (e.g., for overhead reduction, improved accuracy, prediction, etc.), beam management (e.g., for beam prediction in the temporal and / or spatial domains to reduce overhead and latency, improved beam selection accuracy, etc.), and localization accuracy enhancements for different scenarios, including (e.g., for those with severe non-line-of-sight (NLOS) conditions), to name just a few.

[0049] In this illustration, consider the CSI feedback enhancement use case. Massive multiple-input multiple-output (MIMO) systems rely on CSI feedback to perform pre-decoding and achieve performance gains. However, the large number of antennas in MIMO systems can pose challenges to conventional CSI feedback reduction methods and result in excessive feedback overhead. Autoencoder / decoder-based CSI feedback enhancement is an example of a method to address this challenge. In an example implementation of autoencoder / decoder-based CSI feedback enhancement, on the UE side, the preprocessed CSI input is encoded by an encoder (which can be an AI / ML model) and quantized by a quantizer before being sent to network 250. On the network side, the CSI feedback is dequantized by a dequantizer and decoded by a decoder to compute a pre-decoder, which can also be an AI / ML model (e.g., model 232).

[0050] The encoder AI / ML model can be an encoder NN, and the decoder AI / ML model can be a decoder NN. The encoder / decoder-based approach preferably trains both the encoder and decoder NNs using deep learning to minimize the total loss function of the decoder output versus the encoder input. Encoder / decoder training can be centralized (e.g., local to network 250), while the inference function is split between the UE 250 and NG-RAN nodes (e.g., base station 220, in which case the destination node 230 is the same as base station 230). That is, encoder inference occurs at the UE 210, and decoder inference occurs at the base station 220.

[0051] In one example, the recorded measurement report 212 includes data that can be used to train model 232. For example, the recorded measurement report includes ground-based location data (e.g., generated by the satellite receiver of UE 210) and recorded measurements (e.g., time-of-flight measurements). The recorded measurements can be used to generate predictions for UE positioning by model 232, while the ground-based location data can be used to compute a loss function of model 232 relative to the UE positioning prediction, allowing the parameters of model 232 to be refined during training. In another example, the recorded measurement report 212 includes data that can be used by model 232 to perform inference. For example, and returning to the reference UE positioning use case, the recorded measurement report 212 may include recorded measurements but not ground-based location data. In this case, the trained model 232 predicts the positioning of UE 210 given the recorded measurements.

[0052] Figure 3 Example 300 illustrates an RRC state according to some implementation schemes. In one example, the UE (e.g., Figure 2 UE 210) and base station (e.g., Figure 2The base station 220 is connected and can operate in a first state from possible states, including RRC_CONNECTED, RRC_IDLE, and RRC_INACTIVE states. When operating in the RRC_CONNECTED state, the base station can configure the UE (e.g., by transmitting...). Figure 2 The MDT configuration (222) is used to perform and record MDT measurements. Due to different triggers, the UE can switch to a second state among the possible states. For example, the UE can switch from the RRC_CONNECTED state to the RRC_INACTIVE state based on the base station's RRC release message, switch from the RRC_CONNECTED state to the RRC_IDLE state based on the base station's RRC release message, switch from the RRC_INACTIVE state to the RRC_IDLE state based on the base station's RRC release message, switch from the RRC_INACTIVE state to the RRC_CONNECTED state based on the base station's RRC recovery message, or switch from the RRC_IDLE state to the RRC_CONNECTED state based on the base station's RRC establishment message.

[0053] Depending on the MDT configuration, the UE can record MDT measurements in one or more RRC states, potentially across all three RRC states. Furthermore, depending on the MDT configuration, the UE can report recorded MDT measurements at least in the RRC_CONNECTED state, and may also report them in other RRC states, such as the RRC_INACTIVE state.

[0054] Figure 4 Examples of components 400 for configuring a UE to transmit data to a network, according to some implementation schemes, are illustrated. As illustrated, these components include an Operation, Management, and Maintenance (OAM) module 410 (e.g., a module implemented at a network node of the network), an Access and Mobility Management Function (AMF) 420 (e.g., a module implemented at a network node of the network), and a gNB 430 of the network.

[0055] In one example, the OAM module 410 can provide configuration information to the AMF 420 to configure the UE to perform and report measurements related to the AI / ML model. Figure 4 In the example, the first UE is configured for recorded MDT measurements, while the second UE is configured for instantaneous MDT measurements. Therefore, two sets of configuration information can be provided: one set for recorded MDT measurements and one set for instantaneous MDT measurements.

[0056] Subsequently, AMF 420 can forward the configuration information to gNB 430, which in turn transmits the relevant set of configuration information to each of the two UEs. For example, when the first UE is in RRC_CONNECTED state 440, gNB 430 can transmit the configuration for the recorded MDT measurements to the first UE in a LoggedMeasurementConfiguration RRC message. When the second UE is in RRC_CONNECTED state 470, gNB 430 can also transmit the configuration for immediate MDT measurements to the second UE in a MeasurementConfigurationRRC message. Afterward, when the first UE is in RRC_IDLE or INACTIVE state 450, the first UE can begin recording MDT measurements. In contrast, the second UE can begin recording MDT measurements immediately.

[0057] Figure 5 Example 500 illustrates a UE transmitting data to the network in RRC_IDLE and RRC_INACTIVE states according to some implementation schemes. Here, the UE receives a configuration for recorded MDT measurements. However, this configuration enables the UE to record MDT measurements only when in the RRC_IDLE or RRC_INACTIVE state, and not when in the RRC_CONNECTED state. When the UE switches to the RRC_CONNECTED state, the UE can report the recorded measurements.

[0058] As illustrated, when in the RRC_CONNECTED state, the UE accesses the network (e.g., Figure 4 The UE (gNB 430) receives configuration information for the recorded MDT measurements (e.g., in the LoggedMeasurementConfiguration RRC message). The configuration information may include the recording interval and recording duration. Upon receiving the configuration information, the UE starts a timer (e.g., referred to as T330 in a 5G wireless network). The timer length is set to the recording duration. The UE is also configured to perform periodic MDT recording, where periodicity equals the recording interval. Periodic recording is performed when the UE is in the RRC_IDLE or RRC_INACTIVE state. MDT recording is not performed when the UE is in the RRC_CONNECTED state. For each record, both the absolute time included in the recording configuration and the relative time of the record are recorded.

[0059] exist Figure 5In the example, when the UE receives configuration information and starts timer T330, the UE is initially in the RRC_CONNECTED state. Next, the UE switches to the RRC_IDLE state. At this point, the UE begins recording MDT measurements and continues recording MDT measurements until the UE switches back to the RRC_CONNECTED state. Since the UE is now in the RRC_CONNECTED state, it stops recording MDT measurements. Afterward, the UE switches to the RRC_INACTIVE state, and then switches back to the RRC_IDLE state. The UE records MDT measurements while in either of these states. Figure 5 In the example, when the UE is in the RRC_IDLE state, timer T330 expires. At this point, the UE stops recording MDT measurements. At some point, the UE switches to the RRC_CONNECTED state.

[0060] The recorded MDT measurements can be transmitted to a network (e.g., Figure 4 (gNB 430). For example, the network can request the UE to report its recorded MDT measurements by sending a UEInformationRequest message to the UE. In response, the UE can send a UEInformationResponse message containing the recorded MDT measurements.

[0061] Therefore, the UE performs measurements in the RRC_IDLE and RRC_INACTIVE states. The LoggedMeasurementConfiguration RRC message is used to configure the measurement. The results are retrieved using the UEInformationRequest / UEInformationResponse RRC messages. For this purpose, when the UE is in RRC_CONNECTED, the UE starts running timer T330 upon receiving the LoggedMeasurementConfiguration message.

[0062] Configurable periodic recording and event-triggered recording. However, if the UE is in the RRC_CONNECTED state, the UE stops recording. The UE continues recording during state transitions between RRC_IDLE and RRC_INACTIVE.

[0063] Figure 6 Example 600 illustrates a UE transmitting data to the network in all RRC states according to some implementation schemes. Here, the UE also receives configurations for recorded MDT measurements. Figure 5Unlike Example 500, this configuration enables the UE to record MDT measurements not only when in RRC_IDLE or RRC_INACTIVE state, but also when in RRC_CONNECTED state. The UE can report the recorded measurements when in RRC_CONNECTED state and possibly when in RRC_INACTIVE state.

[0064] exist Figure 6 In the example, when the UE is from the network (e.g., from...) Figure 4 When the gNB 430 receives the MDT configuration, the UE is in the RRC_CONNECTED state. The MDT configuration indicates various parameters used to perform and record MDT measurements. These parameters are further described below. Figure 5 In the example, the UE can record MDT measurements during a recording period (which may be the same as, but not necessarily the same as, timer T330). The UE can begin recording MDT measurements upon triggering. The trigger can be time-based (e.g., a predefined or configured amount of time since receiving the MDT configuration) or measurement event-based (e.g., certain measurements meet a condition). This start may correspond to a point in time when the UE is in the RRC_CONNECTED state. Afterward, the UE switches to the RRC_IDLE state and continues recording MDT measurements. Then, the UE switches back to the RRC_CONNECTED state and continues recording MDT measurements. MDT measurements are recorded in a memory buffer (such as an AS buffer with a maximum size (e.g., 64KB)). The UE can report the recorded MDT measurements when the amount of data representing the MDT measurements reaches a threshold (e.g., the threshold may be set to be equal to or less than the maximum size). Figure 6 In the example, the UE is in the RRC_INACTIVE state when the threshold condition is met. Based on the MDT configuration, the UE can transmit recorded MDT measurements to the network (e.g., gNB 430) while in the RRC_INACTIVE state using, for example, MO-SDT. While still in the RRC_INACTIVE state, the UE can continue recording MDT measurements until an end event occurs. The end event can be a time-based event (e.g., a timer expires) or a measurement-based event (e.g., a measurement no longer meets the condition). Figure 6In the example, the termination event occurs when the UE is in the RRC_INACTIVE state. When the UE switches to the RRC_CONNECTED state, the UE can transmit any attached recorded MDT measurements since the last report to the network (e.g., to gNB 430). In the RRC_CONNECTED state, the UEInformationRequest and UEInformationResponse messages can be used for this purpose.

[0065] Of course, the RRC state sequence and the associated MDT recording and reporting are provided for illustrative purposes. Other RRC state sequences are also possible. Similarly, other parameters for MDT recording and reporting are also possible and will be described below.

[0066] Specifically, regarding MDT configuration, this MDT configuration can be referred to as a hybrid MDT configuration or an enhanced MDT configuration because it allows MDT recording when the UE is in the RRC_CONNECTED state. When the UE is in the RRC_CONNECTED state, the network can configure the hybrid MDT via the LoggedMeasurementConfiguration RRC message. In this case, this message includes an indication of the hybrid MDT. This indication can be explicit or implicit (e.g., the message can thus include different parameters for the hybrid MDT). Alternatively, when the UE is in the RRC_CONNECTED state, the network can use an explicit RRC message (e.g., HybridMeasurementConfiguration) to configure the MDT. In both cases, the parameters of the hybrid MDT can be included in the RRC message, indicating various configurations specific to the hybrid MDT.

[0067] One example parameter relates to triggering the start of MDT recording. This parameter indicates when to begin measurement for recording. The specified time information element (IE) may include any or a combination of the following: absolute time (e.g., UTC time), source time timing (e.g., a combination of supersystem frame number (H-SFN), system frame number (SFN), and slot offset, or a combination of H-SFN, SFN, and subframe offset), immediate timing indicating that the UE will start measurement immediately upon receiving the MDT configuration (e.g., the parameter may not be missing from the MDT configuration, or if included, may have a zero value), thresholds for measurement comparison (e.g., measurements and recording may be triggered based on thresholds for serving cell reference signal received power (RSRP), cell reference signal received quality (RSRQ), and cell signal-to-interference-plus-noise ratio (SINR), such as when the serving cell RSRP, RSRQ, and / or SINR exceed the thresholds), measurement events (e.g., measurements and recording may be triggered based on one or more of events A1-A6), or network-provided model suitability conditions (e.g., measurements and recording may be triggered based on conditions such as the network indicating triggering when the UE is indoors, outdoors, stationary, moving, in a specific location, at a specific site, etc.).

[0068] Another example parameter relates to the recording duration. A specific duration IE may include any or a combination of absolute duration (e.g., 19 minutes, 50 seconds, etc.), number of time slots, number of subframes, or the number of times the UE has reported such recorded measurements to the network.

[0069] As a supplement to or alternative to start time and / or recording duration, event-based parameters can be configured. Here, the UE can begin MDT recording when an event is determined to be met, and can continue recording until the event is no longer met. The use of time-based triggering and / or measurement event-based triggering can be indicated by the recording type parameter.

[0070] Regarding events, existing Layer 1 and Layer 2 events can be used. Additional events can be introduced. For example, an X1 event can be defined to extend existing Layer 2 events to all RRC states (e.g., triggering an MDT record when the serving / camping cell's RSRP / RSRQ is less than a threshold), not just to the RRC_IDLE and RRC_CONNECTED states. Similarly, an X2 event can be defined whereby an MDT record is triggered when a cell's RSRP / RSRQ exceeds a threshold, and an X3 event can be defined whereby an MDT record is also triggered when a neighboring cell's RSRP and / or RSRQ exceeds a threshold. These two events can apply to all RRC states. An X4 event can also be defined where an MDT record is triggered when the RSRP and / or RSRQ of the best beam in the serving / camping cell is less than a threshold. The threshold, trigger time (e.g., determining the time between the event being satisfied and the start of the MDT record), and whether RSRP and / or RSRQ should be measured can be configured as part of the X4 event. As part of the X4 event, the network can also configure whether the beam to be measured is SSB, CSI-RS, PRS, or TRS. An X5 event can also be defined, which triggers MDT recording when the RSRP and / or RSRQ of the best beam in a neighboring cell exceeds a threshold. An X6 event can be defined, which triggers MDT recording when the model applicability conditions provided by the network are met (e.g., the UE is indoor / outdoor, stationary / mobile, at a specific location / site). An X7 event can also be defined and can be associated with measurement events A1-A6.

[0071] Example parameter is the measurement range. Specifically, the network can configure the UE to perform measurements and / or report measurements on specific components. The measurement range can be explicit, whereby the network can indicate any or a combination of the following: a list of cell IDs (e.g., a list of cell IDs), a list of frequencies (e.g., a list of frequencies), a list of TACs (e.g., a list of TACs), or a list of reference signal (RS) indices (e.g., including SSB indices, CSI-RS indices, positioning reference signal (PRS) indices, shift reference signal (TRS) indices, or any combination thereof). For example, the combination could be a list of cell IDs and associated SSB indices. Alternatively, the measurement range can be implicit. Here, the network can configure the UE to record or report the top “M” cell-level measurements and / or the top “N” beam-level measurements (e.g., the “M” strongest cell-level measurements, corresponding to the cell with the best RSRP, RSRQ, and / or SINR measurements, and the “N” strongest beam-level measurements, corresponding to the cell with the best RSRP, RSRQ, and / or SINR measurements). The values ​​of “M” and “N” can be indicated in the MDT configuration.

[0072] The MDT configuration may also include parameters indicating the quantities of measurement the UE needs to perform (e.g., the type of measurement to be performed on the indicated component). For example, the parameter may indicate whether to measure cell RSRP, RSRQ, and / or SINR. Additionally or alternatively, the parameter may indicate whether to measure beam RSRP, RSRQ, and / or SINR. In both examples, the parameter may indicate the frequency of the cell and / or beam measurements. Different frequencies may be configured for different measurements (e.g., the frequency may differ between cell-level and beam-level measurements). The parameter may additionally or alternatively indicate whether to perform or record layer 1 and / or layer 3 measurements. In cases where the measurements are used for AI / ML training, ground-based data associated with the measurements may be available at the UE. In this case, the parameter may also indicate whether to report ground-based data. For example, for positioning purposes, the MDT configuration may instruct the UE to report ground-based positioning (e.g., available via the UE's Global Navigation Satellite System (GNSS) receiver) or other ground-based data (e.g., line-of-sight (LoS) path).

[0073] The parameter used to trigger a report of a recorded MDT measurement can be the amount of memory buffer used to store the recorded MDT measurements. For example, an AS buffer can be used. A threshold can be configured to trigger a MO-SDT-based report in the RRC_INACTIVE state. Specifically, if the usage exceeds the threshold, MO-SDT is used to report the recorded MDT measurements.

[0074] Furthermore, the UE can support multiple recorded MDTs for AI / ML purposes. For example, the UE can record multiple different logs of MDT measurements in parallel, where each log may correspond to a different AI / ML model. In this case, the UE can indicate its capabilities to the network. Subsequently, the network can configure multiple parallel recorded MDTs for the UE for AI / ML purposes. Specifically, the MDT configuration can indicate the number of MDT records to be executed in parallel as a parameter and / or may include multiple configurations, each corresponding to one MDT log. The number of configurations cannot exceed the maximum number supported by the UE.

[0075] MDT configuration (which may also be referred to as hybrid MDT configuration or enhanced MDT configuration) can induce specific UE behaviors relative to MDT measurement recording and reporting. Upon receiving the MDT configuration, the UE stores the MDT configuration (e.g., as VarHybridMeasConfig to retain all parameters). The UE can then begin performing measurements when the configured conditions are met. Conditions can be time-based (e.g., absolute time, source time timing, instantaneous, etc.) or event-based (e.g., any of events X1-X7, any of events A1-A6, network-provided model suitability conditions, AS buffer exceeding a threshold, etc.). For time-based conditions, when the timing condition is met, the UE starts a timer based on the configured recording duration. When the timer expires, the UE stops the measurement. For event-based conditions, the UE starts the measurement when the event is met and can stop the measurement when the event is no longer met or after a predefined amount of time.

[0076] When conditions (time or event) are met, the UE records the latest measurement. The recorded information may include different types of information. In the case of an explicit measurement range, the recorded information may include any or a combination of the following: cell ID, cell-level measurements (e.g., configured cell measurements such as cell layer 1 RSRP, RSRQ, and / or SINR), beam-level measurements, a list of beam types (e.g., SSB, CSI-RSR, and / or PRS, etc.), or a list of beam indices and configured measurements (e.g., layer 1 beam RSRP and / or RSRQ). For both cell measurement records and beam measurement records, the order of the recorded measurements may be based on the order of the indices or the order of the configured measurements (e.g., the strongest cell / beam is placed first in the report). For implicit measurement range records (e.g., a record using the first "M" cell measurements and / or the first "N" beam measurements), for the first "M" cells, the record information may include the cell ID and a list of configured cell layer 1 measurements, and / or for the first "N" beams, the record information may include the cell ID, reference signal type (e.g., SSB), beam index, and a list of configured layer 1 beam measurements. For both cell measurement records and beam measurement records, the order is based on the configured measurements (e.g., the strongest cell / beam is placed first in the report).

[0077] In addition to the information mentioned above, the recorded information may also include additional information (e.g., the recorded MDT report to be transmitted to the network). For explicit or implicit recording, the additional information may be any or a combination of the following: UE ID, Cell Radio Network Temporary Identifier (C-RNTI), Globally Unique Temporary Identifier (GUTI), timestamp of the recorded measurement (which may be specified by absolute UTC time or H-SFN, SFT, and slot / subframe index), indication of when the UE received the MDT configuration to begin measurement for recording, cell identifier (e.g., the UE's cell ID in RRC_IDLE or RRC_INACTIVE state, or the serving cell ID of the UE in RRC_CONNECTED state), indication of the UE's RRC state when the UE recorded the measurement, or UE location information.

[0078] Furthermore, the network can configure the UE (e.g., via MDT) to record unspecified data (e.g., data not described in the technical specifications, which may be dynamically specified by the operator). For example, unspecified data may include ground real-time information (e.g., the UE's actual location). Unspecified data may be included in a log file, a separate transparent container in the UEInformationResponse message, or in the MO-MDT.

[0079] The UE may include the destination of the report in the report (e.g., to indicate the location where the report ends). This destination may correspond to a Tracking Collection Entity (TCE) or a dedicated server for AI / ML purposes and / or MDT purposes (e.g., a server configured for artificial intelligence, machine learning, or for Minimum Driven Testing (MDT), for example, by including storage space for training or being trained AI / ML models and / or for MDT data collection).

[0080] Recorded information can be stored as a recorded measurement report in a file. This file can be stored in an AS buffer and / or an application buffer. Typically, the AS buffer has a small buffer size limit, such as 64KB for a recorded MDT. In contrast, the application buffer is much larger than the AS buffer. The choice of which memory buffer to use can be part of the MDT configuration.

[0081] When the UE is in the RRC_CONNECTED state, the UE can report the log file via UEInformationRequest / UEInformationResponse messages when one or more conditions are met. At least some of these conditions can also be configured via MDT configuration. An example configuration is when the usage of the memory buffer (e.g., AS buffer) exceeds a threshold (e.g., this threshold may be indicated in the MDT configuration). Another condition may correspond to a network request for reporting. This request can be separated from the UEInformationRequest / UEInformationResponse message as a separate downlink RRC message. This downlink message can trigger the UEInformationRequest / UEInformationResponse message exchange. Another condition may involve periodicity. Specifically, the UE can configure to periodically transmit recorded measurement reports. In yet another example, the condition may be specific to a particular UE implementation.

[0082] When a UE enters the RRC_IDLE or RRC_INACTIVE state, the UE continues measurements for recording. If an AS buffer is used and its size is limited, different methods (either replacing or combining with each other) can be used to mitigate the small size limit. For example, if the UE is in the RRC_INACTIVE state and reporting conditions are met (e.g., AS buffer usage exceeds a threshold), the UE initiates an MO-SDT procedure to report the log file to the network. In another example, if the UE is in the RRC_INACTIVE state and reporting conditions are met (e.g., AS buffer usage exceeds a threshold), the UE reports the availability of the recorded MDT data and the log buffer size to the network via MO-SDT. The network then determines whether to continue the SDT session or place the RRC_INACTIVE UE into the RRC_CONNECTED state for MDT reporting. In yet another example, if the UE is in the RRC_IDLE or RRC_INACTIVE state and reporting conditions are met (e.g., AS buffer usage exceeds a threshold), the UE requests to enter the RRC_CONNECTED state to report the log file to the UE via a UEInformationRequest / UEInformationResponse message. In another example, if the network urgently needs to train a new model, it can page the UE with a new paging reason to request the UE to report the recorded measurements. The paging reason can indicate the recorded MDT measurements to be reported.

[0083] When the memory buffer is full and the UE is unable to report the log file (e.g., the UE is not in the RRC_CONNECTED state), the UE may discard some recorded MDT measurements. Different methods are possible for discarding. In one example, a specific UE implementation may instruct the logic to be executed to discard measurements. In another example, the UE may discard these measurements based on their priority or timing (e.g., low-priority and / or older measurements may be discarded). For example, the UE may first discard measurements collected in a specific area or at a specific time and / or in an RRC state. Priorities can be configured via MDT configuration.

[0084] As explained above, the UE can send recorded measurement reports in the MO-SDT or by using UEInformationRequest / UEInformationResponse messages. Various transmission mechanisms can be used. For example, recorded measurement reports can be sent along with a signaling radio bearer (SRB) (e.g., a new SRB specific to MDT reports). The priority of the recorded measurement reports can be configurable (e.g., in the MDT configuration) and can be used to include the recorded measurement reports in the SRB. In all these cases, the recorded measurement reports can be sent in multiple segments. Each segment can have a predefined data size, depending on the amount of data to be reported and the transmission mechanism. These segments can include at least one common set of information to identify that the segments were transmitted from the same UE and belong to the same report (e.g., each segment may include a UE ID and possibly a report ID; if no report ID is included, a timestamp may be included, and the timestamp may indicate the time series of the segment; alternatively, a sequence ID may be included in each segment to indicate the time series).

[0085] Figure 7An example of sequence diagram 700, according to some embodiments, for configuring UE 710 to transmit data to network 720 for AI / ML purposes in all RRC states is illustrated. As illustrated, when UE 710 is in the RRC_CONNECTED state, UE capability information is exchanged between UE 710 and network 720. For example, the UE uses the UE capability information to respond to capability requests transmitted from a base station of the network. This information may indicate the maximum number of hybrid MDT recordings and / or parallel MDT recordings that the UE supports. When the UE is in the RRC_CONNECTED state, network 720 may transmit an MDT configuration to UE 710 (e.g., via a base station). The MDT configuration may be a hybrid MDT configuration that configures UE 710 to perform and record MDT measurements in all RRC states. Where applicable (e.g., based on time-triggered or event-triggered recording), UE 710 may record MDT measurements while still in the RRC_CONNECTED state. Furthermore, where applicable (e.g., based on time-triggered or event-triggered reporting), the recorded MDT measurements can be reported to network 720 after a UEInformationRequest RRC message from network 720, thereby transmitting the recorded MDT measurements in a UEInformationResponse RRC message.

[0086] At a certain point, the UE enters the RRC_INACTIVE state. Here, based on the MDT configuration and where applicable (e.g., time-triggered or event-triggered), the UE 710 can continue recording (or re-record if no recording was previously performed) MDT measurements while in the RRC_INACTIVE state. Furthermore, where applicable (e.g., time-triggered or event-triggered for reporting, including when the AS buffer approaches a maximum size threshold), the UE 710 can report the recorded MDT measurements to the network 720 (e.g., to the base station). Since the UE is in the RRC_INACTIVE state, reporting can be performed using MO-SDT. This report may also include the UE ID, measurement, timestamp, ID of the cell where the UE is camped, and the RRC state at the time of recording. If configured for unspecified data (e.g., UE location derived from a GNSS receiver), the report may also include a container for the unspecified data.

[0087] In sequence diagram 700, UE 710 then enters the RRC_CONNECTED state. Where applicable, the UE may continue recording MDT measurements. Upon receiving a UEInformationRequest RRC message from network 720, UE 710 may transmit the recorded measurement report to network 720 (e.g., to a base station) in a UEInformationResponse RRC message. This report may also include the UE ID, measurement, timestamp, ID of the cell where the measurement was recorded, and the RRC state at the time of recording. If configured for unspecified data (e.g., UE location derived from a GNSS receiver), the report may also include a container for the unspecified data.

[0088] Of course, sequence diagram 700 is an example of UE 710 recording MDT measurements and transmitting the resulting recorded measurement report to network 720. For example... Figure 6 As described herein, other sequences and / or triggers (e.g., RRC states) are possible.

[0089] Figure 8 Examples of operational flow / algorithm structures 800 for transmitting data to the network in all RRC states, implemented by a UE according to some implementation schemes, are illustrated. The UE can be any of the UEs described above herein. Components of the UE, such as one or more of its processors, may implement the operational flow / algorithm structure 800. Figure 11 This type of component is further described in the text.

[0090] Figure 8 Examples of operational flow / algorithm structures 800 implemented by a UE for coordinating the use of an AI model with the network, according to some implementation schemes, are illustrated. In one example, the operational flow / algorithm structure 800 includes, at step 812, receiving an MDT configuration from the network including a model, the MDT configuration indicating that measurements should be performed and recorded by the UE across different RRC states, wherein the model includes an artificial intelligence model or a machine learning model, and wherein the model is configured to use input based on the measurements. For example, the MDT configuration is an instruction... Figure 6 The MDT configuration refers to one or more parameters described in the parameters section. The MDT configuration can be received when the UE is in the RRC_CONNECTED state. Furthermore, the MDT configuration can be received after the UE has transmitted UE capability information to the network indicating its support for hybrid MDT recording. Based on the trigger indicated by the MDT configuration, the UE can begin recording MDT measurements when it is in the RRC_CONNECTED state.

[0091] In one example, the operation flow / algorithm structure 800 includes, at step 814, performing a first measurement based on the MDT configuration when the UE is in an RRC_INACTIVE or RRC_IDLE state. For example, the UE enters the RRC_INACTIVE or RRC_IDLE state from the RRC_CONNECTED state. If the UE has already started recording MDT measurements, the UE continues to do so in the entered RRC state. Otherwise, MDT recording is triggered according to the triggering parameters indicated in the MDT configuration. The first measurement may be one of the MDT measurements performed and recorded by the UE according to the MDT configuration (e.g., a cell-level measurement or beam-level measurement corresponding to a specific measurement quantity). If the UE is in the RRC_INACTIVE state and the memory buffer for recording MDT measurements is close to a size threshold, the UE may trigger an MDT reporting procedure (e.g., transmitting a report via MO-SDT or requesting a switch to the RRC_CONNECTED state for MDT measurement reporting).

[0092] In one example, the operation flow / algorithm structure 800 includes, at step 816, performing a second measurement based on the MDT configuration while the UE is in the RRC_CONNECTED state. Here, the UE continues to do so while in the RRC_CONNECTED state. The second measurement can be another MDT measurement (e.g., a cell-level measurement or beam-level measurement corresponding to a specific measurement quantity) among the MDT measurements performed and recorded by the UE according to the MDT configuration.

[0093] In one example, the operation flow / algorithm structure 800 includes, at step 818, storing the first and second measurements in a memory buffer. The memory buffer can be an AS buffer or an application buffer.

[0094] In one example, the operation flow / algorithm structure 800 includes, at step 820, transmitting the first and second measurements to the network in the recorded measurement report. For example, when the UE is in the RRC_CONNECTED state, the recorded measurement report can be transmitted in the UEInformationResponse RRC message. Alternatively, if the UE has switched back to the RRC_INACTIVE state, the recorded measurement report can be transmitted via MO-SDT.

[0095] Figure 9 An example of an operational flow / algorithm structure 900, implemented by a network according to some implementation schemes, for configuring a UE to transmit data to the network in all RRC states, is illustrated. The operational flow / algorithm structure 900 may be implemented by one or more nodes of a network including a base station, RAN, and / or core network.

[0096] In one example, the operation flow / algorithm structure 900 includes, at step 912, transmitting an MDT configuration to the user equipment (UE). This MDT configuration indicates that measurements should be performed and recorded by the UE across different RRC states, wherein the model is stored at the network, configured to use measurement-based inputs, and includes an artificial intelligence model or a machine learning model. For example, the MDT configuration indicates... Figure 6 The MDT configuration is a hybrid MDT configuration of one or more parameters described in the specification. The MDT configuration can be transmitted when the UE is in the RRC_CONNECTED state. Alternatively, the MDT configuration can be transmitted after receiving capability information from the UE indicating UE support for hybrid MDT records.

[0097] In one example, the operation flow / algorithm structure 900 includes, at step 914, receiving a recorded measurement report from the UE based on the MDT configuration. The recorded measurement report includes measurements performed and recorded by the UE when the UE is in the RRC_CONNECTED state. The measurements can be MDT measurements performed and recorded based on the MDT configuration. The recorded measurement report may also include additional MDT measurements performed and recorded by the UE when it is in other RRC states. The recorded measurement report can be received when the UE is in the RRC_CONNECTED state and / or when the UE is in the RRC_INACTIVE state.

[0098] Figure 10 A receiving component 1000 according to some embodiments is illustrated. A UE (such as any of the UEs described above) may include the receiving component 1000. The receiving component 1000 may include an antenna panel 1004 that includes a plurality of antenna elements. Panel 1004 is shown as having four antenna elements, but other embodiments may include other numbers of antenna elements.

[0099] Antenna panel 1004 may be coupled to an analog beamforming (BF) assembly comprising a plurality of phase shifters 1008(1) to 1008(4). Phase shifters 1008(1) to 1008(4) may be coupled to radio frequency (RF) chain 1012. RF chain 1012 may amplify received analog RF signals, downconvert RF signals to baseband, and convert analog baseband signals into digital baseband signals that can be provided to a baseband processor for further processing.

[0100] In various implementations, control circuitry residing in the baseband processor may provide phase shifters 1008(1) to 1208(4) with BF weights (e.g., W1 to W4) that represent phase shift values ​​to provide a receive beam at antenna panel 1004. These BF weights may be determined based on channel-based beamforming.

[0101] Figure 11A UE 1100 according to some embodiments is illustrated. UE 1100 may be similar to and substantially interchangeable with any of the UEs described above herein. Devices (such as those described in any of the figures above) may include similar components, including, for example, a processor, memory, and RF interface circuitry.

[0102] Similar to the description above relative to UE 104, UE 1100 can be any mobile or non-mobile computing device, such as a mobile phone, computer, tablet, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, voltmeters / ammeters, actuators, etc.), video surveillance / monitoring devices (e.g., cameras, camcorders, etc.), wearable devices, or loosely coupled IoT devices. In some implementations, the UE can be a reduced-capacity UE or an NR lightweight UE.

[0103] UE 1100 may include a processor 1104, RF interface circuitry 1108, memory / storage device 1112, user interface 1116, sensor 1120, drive circuitry 1122, power management integrated circuit (PMIC) 1124, and battery 1128. The components of UE 1100 may be implemented as integrated circuits (ICs), portions of such integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 11 The block diagram is intended to show a high-level view of some of the components of the UE 1100. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0104] The components of UE 1100 can be coupled to various other components via one or more interconnects 1132, which can represent any type of interface, input / output, bus (local, system, or extended), transmit line, trace, optical connection, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0105] Processor 1104 may include processor circuitry such as baseband processor circuitry (BB) 1104A, central processing unit circuitry (CPU) 1104B, and graphics processing unit circuitry (GPU) 1104C. Processor 1104 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures from memory / storage device 1112) to cause UE 1100 to perform the operations described herein.

[0106] In some implementations, the baseband processor circuit 1104A can access the communication protocol stack 1136 in the memory / storage device 1112 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1104A can access the communication protocol stack to perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and Non-Access Stratum (NAS) layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 1108.

[0107] The baseband processor circuit 1104A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0108] The baseband processor circuit 1104A can also access group information from the memory / storage device 1112 to determine multiple repeated search space groups in which PDCCH can be sent.

[0109] The memory / storage device 1112 may include any type of volatile or non-volatile memory that can be distributed throughout the UE 1100. In some embodiments, some of the memory / storage devices 1112 may be located on the processor 1104 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 1112 are external to the processor 1104 but can be accessed via a memory interface. The memory / storage device 1112 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0110] RF interface circuitry 1108 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 1100 to communicate with other devices via a radio access network. RF interface circuitry 1108 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0111] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 1150 and continue to filter and amplify the signal (using a low-noise amplifier). The signal can be provided to the receiver of the transceiver, which down-converts the RF signal into a baseband signal that is provided to the baseband processor of processor 1104.

[0112] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 1150.

[0113] In various implementations, the RF interface circuit 1108 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0114] Antenna 1150 may include multiple antenna elements, each of which converts an electrical signal into radio waves for propagation through the air and converts received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 1150 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input multiple-output communication. Antenna 1150 may include microstrip antennas, patch antennas, phased array antennas, printed antennas fabricated on the surface of one or more printed circuit boards, etc. Antenna 1150 may have one or more panels designed for a specific frequency band included in FR1 or FR2.

[0115] User interface circuitry 1116 includes various input / output (I / O) devices designed to enable a user to interact with UE 1100. User interface 1116 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a head-mounted device, etc. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes (LEDs) and multi-character visual outputs) or more complex outputs (such as display devices or touchscreens such as liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 1100.

[0116] Sensor 1120 may include a device, module, or subsystem designed to detect events or changes in its environment and transmit information about the detected events (sensor data) to another device, module, subsystem, etc. Examples of such sensors include, in particular, inertial measurement units, which include: accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including: triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; and so on.

[0117] The driving circuitry 1122 may include software and hardware elements that operate to control a specific device embedded in, attached to, or otherwise communicatively coupled to the UE 1100. The driving circuitry 1122 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 1100. For example, the driving circuitry 1122 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for obtaining sensor readings from the sensor circuitry 1120 and controlling and allowing access to the sensor circuitry 1120; a driver for obtaining actuator positioning of an electromechanical component or controlling and allowing access to an electromechanical component; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0118] The PMIC 1124 manages the power supplied to various components of the UE 1100. Specifically, relative to the processor 1104, the PMIC 1124 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0119] In some implementations, the PMIC 1124 may control or otherwise be part of various power-saving mechanisms of the UE 1100. For example, if the platform UE is in the RRC_Connected state (described herein as the RRC_CONNECTED state), in which the platform UE remains connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform UE may enter a state known as Discontinuous Receive Mode (DRX). During this state, the UE 1100 may power down for short intervals, thus saving power. If there is no data traffic activity during an extended period, the UE 1100 may transition to the RRC_Idle state (described herein as the RRC_IDLE state), in which the UE disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The UE 1100 enters a very low-power state, and the UE performs paging, in which the UE periodically wakes up again to listen to the network, and then power down again. The UE 1100 may not receive data in this state; to receive data, the UE must transition back to the RRC_Connected state. An additional power-saving mode renders the device unusable for a period exceeding the paging interval (from seconds to hours). During this time, the device is completely unconnected to the network and may be completely powered off. Any data transmitted during this period will incur significant latency, which is assumed to be acceptable.

[0120] Battery 1128 can power UE 1100, but in some examples, UE 1100 may be installed and deployed in a fixed location and may have a power source coupled to the power grid. Battery 1128 may be a lithium-ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 1128 may be a typical lead-acid automotive battery.

[0121] Figure 12 An example of a gNB 1200 according to some implementation schemes is shown. The gNB 1200 can be used with... Figure 1 The gNB 108 is similar to and largely interchangeable with it, and is an example of any of the base stations described above in this article.

[0122] The gNB 1200 may include a processor 1204, RAN interface circuitry 1208, core network (CN) interface circuitry 1212, and memory / storage device circuitry 1216. Components of the gNB 1200 may be coupled to various other components via one or more interconnects 1228.

[0123] The processor 1204, RAN interface circuit 1208, memory / storage device circuit 1216 (including communication protocol stack 1210), antenna 1250, and interconnect 1228 are compatible with... Figure 11 The similarly named components shown and described are similar.

[0124] The CN interface circuit 1212 can provide connectivity to a core network (e.g., a 5GC using a fifth-generation core network (5GC) compatible network interface protocol (such as Carrier Ethernet protocol) or some other suitable protocol). Network connectivity can be provided to / from the gNB 1200 via fiber optic or wireless backhaul. The CN interface circuit 1212 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1212 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0125] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0126] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more embodiments described below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more embodiments described in the Embodiments section below.

[0127] Example Further exemplary implementations are provided in the following sections.

[0128] Example 1 includes a method implemented by a user equipment (UE), the method comprising: receiving a Minimum Driven Test (MDT) configuration from a network including a model, the MDT configuration indicating measurements to be performed and recorded by the UE across different Radio Resource Control (RRC) states, wherein the model includes an artificial intelligence model or a machine learning model, and wherein the model is configured to use inputs based on the measurements; performing a first measurement based on the MDT configuration when the UE is in an RRC_INACTIVE state or an RRC_IDLE state; performing a second measurement based on the MDT configuration when the UE is in an RRC_CONNECTED state; storing the first measurement and the second measurement in a memory buffer; and transmitting the first measurement and the second measurement to the network in a recorded measurement report.

[0129] Example 2 includes a method implemented by a node of a network, the method comprising: transmitting a Minimum Driven Test (MDT) configuration to a User Equipment (UE), the MDT configuration indicating that measurements should be performed and recorded by the UE across different Radio Resource Control (RRC) states, wherein a model is stored at the network, configured to use inputs based on the measurements, and includes an artificial intelligence model or a machine learning model; and receiving a recorded measurement report from the UE based on the MDT configuration, the recorded measurement report including measurements performed and recorded by the UE when the UE is in an RRC_CONNECTED state.

[0130] Example 3 includes the method according to any of Examples 1 to 2, the method further comprising: switching from the RRC_INACTIVE state or the RRC_IDLE state to the RRC_CONNECTED state; and during the switching, continuing to perform and record the measurement based on the MDT configuration.

[0131] Example 4 includes the method according to any of Examples 1 to 3, wherein the MDT configuration is received in a LoggedMeasurementConfiguration RRC message which includes an indication for performing and recording the measurement across the RRC state, or in a HybridLoggedMeasurementConfiguration RRC message which indicates that the MDT configuration is a hybrid MDT configuration.

[0132] Example 5 includes the method according to any of Examples 1 to 4, wherein the MDT configuration includes an indication of the start of the measurement, wherein the indication includes at least one of: absolute time, source time timing, measurement start upon receipt of the MDT configuration, triggering based on a measurement event, or conditional triggering provided by the network.

[0133] Example 6 includes the method according to any of Examples 1 to 5, wherein the MDT configuration includes an indication of the recording duration defined about at least one of the number of time slots, the number of subframes, or the number of measurements that the UE has reported recording.

[0134] Example 7 includes the method according to any of Examples 1 to 6, wherein the MDT configuration indicates a measurement range, wherein the measurement range includes at least one of the following: a cell identifier list, a frequency list, a tracking area code (TAC) list, or a reference signal index list.

[0135] Example 8 includes the method according to any of Examples 1 to 7, wherein the MDT configuration indicates a measurement range, wherein the measurement range includes at least one of the following: a first number of the strongest cell-level measurements to be reported or a second number of the strongest beam-level measurements to be reported.

[0136] Example 9 includes the method according to any of Examples 1 to 8, wherein the MDT configuration indicates a set of measurements, wherein the set includes at least one of the following: cell reference signal received power (RSRP), cell reference signal received quality (RSRQ), cell signal-to-interference-plus-noise ratio (SINR), beam RSRP, or beam RSRQ.

[0137] Example 10 includes the method according to any of Examples 1 to 9, wherein the MDT configuration further indicates at least one of the following: a list of frequencies of cells or beams to be measured, or whether to perform a Layer 1 measurement or a Layer 3 measurement.

[0138] Example 11 includes the method according to any of Examples 1 to 10, wherein the MDT configuration instructs the UE to report UE location data, the UE location data including at least one of ground real-time location data or line-of-sight (LoS) path data.

[0139] Example 12 includes the method according to any of Examples 1 to 11, wherein the MDT configuration indicates a measurement-based event for triggering the execution or recording of the measurement.

[0140] Example 13 includes the method according to Example 12, wherein the measurement-based event includes at least one of the following: when the UE is in any RRC state, the cell reference signal received power (RSRP) or cell reference signal received quality (RSRQ) exceeds a first threshold; the first beam RSRP or first beam RSRQ of the serving cell or camped cell is less than a second threshold; the second beam RSRP or second beam RSRQ of a neighboring cell exceeds the second threshold; or conditions provided by the network.

[0141] Example 14 includes the method according to any of Examples 1 to 13, wherein the MDT configuration indicates a memory buffer threshold for triggering a Measurement Object Short Data Transmission (MO-SDT) report in the RRC_INACTIVE state.

[0142] Example 15 includes the method according to any of Examples 1 to 14, wherein the MDT configuration indicates a plurality of MDT configurations recorded in parallel, wherein the recorded measurement report corresponds to one of the plurality of MDT configurations recorded in parallel.

[0143] Example 16 includes the method according to Example 14, the method further comprising: transmitting to the network UE capability information indicating a maximum number of concurrently recorded MDT configurations supported by the UE, wherein the MDT configurations are based on the UE capability information.

[0144] Example 17 includes the method according to any of Examples 1 to 15, wherein the first measurement includes at least one of a cell-level measurement or a beam-level measurement and is stored in association with a cell identifier.

[0145] Example 18 includes the method according to any of Examples 1 to 17, wherein the recorded measurement report includes an ordered list of at least cell-level or beam-level measurements, and wherein the ordered list is based on the order of an index or the order of configured measurements.

[0146] Example 19 includes the method according to any of Examples 1 to 18, wherein the recorded measurement report includes cell-level measurements, cell identifiers, and an ordered list of cell layer 1 measurements.

[0147] Example 20 includes the method according to any of Examples 1 to 19, wherein the recorded measurement report includes beam-level measurements, cell identifiers, reference signal types, beam indices, and an ordered list of layer 1 beam measurements.

[0148] Example 21 includes the method according to any of Examples 1 to 20, wherein the memory buffer is an application buffer.

[0149] Example 22 includes the method according to any of Examples 1 to 21, wherein the recorded measurement report is transmitted when a condition is met and when the UE is in the RRC_CONNECTED state, wherein the condition includes at least one of the following: the size of the memory buffer exceeds a threshold, a downlink RRC message indicating a request for the recorded measurement report is received from the network, or the periodicity of the report.

[0150] Example 23 includes the method according to any of Examples 1 to 22, wherein the recorded measurement report is transmitted when the conditions are met and when the UE is in the RRC_INACTIVE state, wherein the recorded measurement report is transmitted at least by using a Measurement Object Short Data Transmission (MO-SDT) report in the RRC_INACTIVE state.

[0151] Example 24 includes the method according to any of Examples 1 to 23, wherein a recorded measurement report is transmitted when a condition is met while the UE is in the RRC_INACTIVE state, and wherein the method further includes: transmitting to the network an indication that the recorded MDT data is available and the size of the memory buffer; receiving from the network a message for transmitting the recorded MDT data based on at least one of the indication or the size; and switching to the RRC_CONNECTED state based on the message, wherein the recorded measurement report is transmitted when the UE is in the RRC_CONNECTED state.

[0152] Example 25 includes the method according to any of Examples 1 to 23, wherein a recorded measurement report is transmitted when a condition is met while the UE is in the RRC_INACTIVE state or the RRC_IDLE state, and wherein the method further includes: transmitting a request to the network to enter the RRC_CONNECTED state based on the condition being met; receiving a message from the network to enter the RRC_CONNECTED state based on the request; and switching to the RRC_CONNECTED state based on the message, wherein the recorded measurement report is transmitted when the UE is in the RRC_CONNECTED state.

[0153] Example 26 includes the method according to any of Examples 1 to 25, the method further comprising: receiving from the network a paging message indicating a request for a recorded measurement report, wherein the recorded measurement report is transmitted based on the request.

[0154] Example 27 includes the method according to any of Examples 1 to 27, the method further comprising: performing a third measurement based on the MDT configuration when the UE is in any of the RRC states; storing the third measurement in the memory buffer; determining that the size of the memory buffer exceeds a threshold; and discarding the third measurement from the memory buffer such that the third measurement is excluded from the recorded measurement report, wherein the third measurement is discarded based on at least one of: the priority of the third measurement, the timing of the third measurement, or the MDT configuration.

[0155] Example 28 includes the method according to any of Examples 1 to 27, wherein the recorded measurement report further includes at least one of the following: the UE's identifier, a Cell Radio Network Temporary Identifier (C-RNTI), a Globally Unique Temporary Identifier (GUTI), a timestamp for recording the measurement, an indication of when the UE received the MDT configuration, a cell identifier, an indication of the RRC state in which the UE was when the UE recorded the measurement, or UE location information.

[0156] Example 29 includes the method according to any of Examples 1 to 28, wherein the MDT configuration indicates the type of data to be recorded, wherein the data is included in the recorded measurement report or transmitted separately from the recorded measurement report.

[0157] Example 30 includes the method according to any of Examples 1 to 29, wherein the recorded measurement report indicates the destination address to which the recorded measurement report is to be transmitted by the node, wherein the destination may include a server configured for artificial intelligence, machine learning, or MDT.

[0158] Example 31 includes the method according to any of Examples 1 to 30, wherein the recorded measurement reports are received in multiple segments.

[0159] Example 32 includes the method according to any of Examples 1 to 31, wherein a signaling radio bearer (SRB) is used to receive the recorded measurement reports, and wherein the priority of the recorded measurement reports is configurable.

[0160] Example 33 includes an apparatus such as a UE, the apparatus including components for performing one or more elements of the methods described or associated with any of Examples 1, 3 to 32 or any other methods or processes described herein.

[0161] Example 34 includes one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device such as a UE, cause the electronic device to perform one or more elements of the methods or processes described or associated with any of Examples 1, 3 to 32 or any other methods or processes described herein.

[0162] Example 35 includes an apparatus such as a UE, the apparatus including one or more elements of a logic component, module, or circuit for performing the methods described or associated with any of Examples 1, 3 to 32, or any other methods or processes described herein.

[0163] Example 36 includes the methods, techniques, or processes described or associated with any one of Examples 1, 3 to 32, or any part or component thereof.

[0164] Example 37 includes an apparatus such as a UE, the apparatus comprising: one or more processors and one or more memories (e.g., one or more computer-readable media), the one or more memories including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described or associated with any one or more of Examples 1, 3 to 32 or a portion thereof.

[0165] Example 38 includes signals described or associated with any one of Examples 1, 3 to 32, or any part or component thereof.

[0166] Example 39 includes datagrams, information elements, packets, frames, segments, PDUs, or messages described or associated with any of Examples 1, 3 to 32, or in part or in part thereof, or otherwise described in this disclosure.

[0167] Example 40 includes a signal encoded with data described or associated with any one of Examples 1, 3 to 32 or a part or component thereof, or otherwise described in this disclosure.

[0168] Example 41 includes signals encoded as datagrams, IEs, packets, frames, segments, PDUs, or messages, as described or associated with any one of Examples 1, 3 to 32 or any part or component thereof, or otherwise described in this disclosure.

[0169] Example 42 includes an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique or process as described or associated with any one or a portion of Examples 1, 3 to 32.

[0170] Example 43 includes a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process as described or associated with any one or a portion of Examples 1, 3 to 32.

[0171] Example 44 includes a network comprising components for performing one or more elements of the methods described or associated with any of Examples 2 through 32, or any other methods or processes described herein.

[0172] Example 45 includes one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of the network, cause the network to perform one or more elements of the methods described or associated with any of Examples 2 to 32 or any other methods or processes described herein.

[0173] Example 46 includes a network comprising logic components, modules, or circuitry for performing one or more elements of the methods described or associated with any of Examples 2 through 32 or any other methods or processes described herein.

[0174] Example 47 includes a network comprising: one or more processors and one or more memories (e.g., one or more computer-readable media), the one or more memories including instructions that, when executed by the one or more processors, cause the one or more processors to perform methods, techniques, or processes as described or associated with any one or more of Examples 2 to 32.

[0175] Unless otherwise expressly stated, any embodiment described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments is illustrative and descriptive, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from practice of various embodiments.

[0176] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more processors; and One or more memories, the one or more memories storing instructions that, when executed by the one or more processors, cause the UE to: The network receives a Minimum Driven Test (MDT) configuration, which includes a model indicating that measurements should be performed and recorded by the UE across different Radio Resource Control (RRC) states, wherein the model includes an artificial intelligence model or a machine learning model, and wherein the model is configured to use inputs based on the measurements. Based on the MDT configuration, the first measurement is performed when the UE is in the RRC_INACTIVE state or the RRC_IDLE state; Based on the MDT configuration, a second measurement is performed when the UE is in the RRC_CONNECTED state; The first measurement and the second measurement are stored in a memory buffer; as well as The first and second measurements are transmitted to the network in the recorded measurement report.

2. The UE according to claim 1, wherein the execution of the instruction further configures the UE to: Switching from the RRC_INACTIVE state or the RRC_IDLE state to the RRC_CONNECTED state; and During the switch, the measurements continue to be performed and recorded based on the MDT configuration.

3. The UE of claim 1, wherein the MDT configuration is received in a LoggedMeasurementConfiguration RRC message including an indication for performing and recording the measurement across the RRC state, or in a HybridLoggedMeasurementConfiguration RRC message indicating that the MDT configuration is a hybrid MDT configuration.

4. The UE of claim 1, wherein the MDT configuration includes an indication of the start of the measurement, wherein the indication includes at least one of: absolute time, source time timing, measurement start upon receipt of the MDT configuration, triggering based on a measurement event, or conditional triggering provided by the network.

5. The UE of claim 1, wherein the MDT configuration includes an indication of the recording duration defined about at least one of the number of time slots used, the number of subframes used, or the number of measurements reported by the UE.

6. The UE of claim 1, wherein the MDT configuration indicates a measurement range, wherein the measurement range includes at least one of the following: a cell identifier list, a frequency list, a tracking area code (TAC) list, or a reference signal index list.

7. The UE of claim 1, wherein the MDT configuration indicates a measurement range, wherein the measurement range includes at least one of the following: a first number of the strongest cell-level measurements to be reported or a second number of the strongest beam-level measurements to be reported.

8. The UE of claim 1, wherein the MDT configuration indicates a set of measurements, wherein the set includes at least one of the following: cell reference signal received power (RSRP), cell reference signal received quality (RSRQ), cell signal-to-interference-plus-noise ratio (SINR), beam RSRP, or beam RSRQ.

9. The UE of claim 8, wherein the MDT configuration further indicates at least one of the following: a list of frequencies of cells or beams to be measured, or performing a layer 1 measurement or a layer 3 measurement.

10. The UE of claim 1, wherein the MDT configuration instructs the UE to report UE location data, the UE location data including at least one of ground real-time location data or line-of-sight (LoS) path data.

11. The UE of claim 1, wherein the MDT configuration indicates a measurement-based event for triggering the execution or recording of the measurement.

12. The UE of claim 11, wherein the measurement-based event includes at least one of the following: when the UE is in any RRC state, the cell reference signal received power (RSRP) or cell reference signal received quality (RSRQ) exceeds a first threshold; the first beam RSRP or first beam RSRQ of the serving cell or the camped cell is less than a second threshold; the second beam RSRP or second beam RSRQ of a neighboring cell exceeds the second threshold; or a condition provided by the network.

13. The UE of claim 1, wherein the MDT configuration indicates a memory buffer threshold for triggering a Measurement Object Short Data Transmission (MO-SDT) report in the RRC_INACTIVE state.

14. The UE of claim 1, wherein the MDT configuration indicates a plurality of MDT configurations recorded in parallel, wherein the recorded measurement report corresponds to one of the plurality of MDT configurations recorded in parallel.

15. The UE of claim 14, wherein the execution of the instructions further configures the UE to: The network is transmitted information indicating the maximum number of UE capability information for parallel-recorded MDT configurations supported by the UE, wherein the MDT configurations are based on the UE capability information.

16. One or more computer-readable storage media storing instructions that, when executed on a user equipment (UE), cause the UE to perform operations, the operations including: The network receives a Minimum Driven Test (MDT) configuration, which includes a model indicating that measurements should be performed and recorded by the UE across different Radio Resource Control (RRC) states, wherein the model includes an artificial intelligence model or a machine learning model, and wherein the model is configured to use inputs based on the measurements. Based on the MDT configuration, the first measurement is performed when the UE is in the RRC_INACTIVE state or the RRC_IDLE state; Based on the MDT configuration, a second measurement is performed when the UE is in the RRC_CONNECTED state; The first measurement and the second measurement are stored in a memory buffer; as well as The first and second measurements are transmitted to the network in the recorded measurement report.

17. One or more computer-readable storage media of claim 16, wherein the first measurement comprises at least one of a cell-level measurement or a beam-level measurement, and is stored in association with a cell identifier.

18. The computer-readable storage medium of claim 16, wherein the recorded measurement report comprises an ordered list of at least cell-level or beam-level measurements, and wherein the ordered list is based on the order of an index or the order of configured measurements.

19. The one or more computer-readable storage media of claim 16, wherein the recorded measurement report comprises an ordered list of cell-level measurements, cell identifiers, and cell layer 1 measurements.

20. The one or more computer-readable storage media of claim 16, wherein the recorded measurement report includes beam-level measurements, cell identifiers, reference signal types, beam indices, and an ordered list of layer 1 beam measurements.

21. The computer-readable storage medium of claim 16, wherein the memory buffer is an application buffer.

22. One or more computer-readable storage media of claim 16, wherein the recorded measurement report is transmitted when a condition is met and when the UE is in the RRC_CONNECTED state, wherein the condition includes at least one of the following: the size of the memory buffer exceeds a threshold, a downlink RRC message indicating a request for the recorded measurement report is received from the network, or the periodicity of the report.

23. One or more computer-readable storage media according to claim 16, wherein the recorded measurement report is transmitted when a condition is met and when the UE is in the RRC_INACTIVE state, wherein the recorded measurement report is transmitted at least by using a Measurement Object Short Data Transmission (MO-SDT) report in the RRC_INACTIVE state.

24. The computer-readable storage medium of claim 16, wherein the recorded measurement report is transmitted when the UE is in the RRC_INACTIVE state and a condition is met, and wherein the operation further comprises: Transmit to the network an indication of the availability of the recorded MDT data and the size of the memory buffer; Messages for transmitting the recorded MDT data are received from the network based on at least one of the indication or the size. as well as The UE switches to the RRC_CONNECTED state based on the message, wherein the recorded measurement report is transmitted when the UE is in the RRC_CONNECTED state.

25. One or more computer-readable storage media according to claim 16, wherein the recorded measurement report is transmitted when the UE is in the RRC_INACTIVE state or the RRC_IDLE state and a condition is met, and wherein the operation further includes: Based on the conditions being met, a request to enter the RRC_CONNECTED state is transmitted to the network; Based on the request, receive a message from the network indicating entry into the RRC_CONNECTED state; as well as The UE switches to the RRC_CONNECTED state based on the message, wherein the recorded measurement report is transmitted when the UE is in the RRC_CONNECTED state.

26. The one or more computer-readable storage media of claim 16, wherein the operation further comprises: Receive a paging message from the network indicating a request for the recorded measurement report, wherein the recorded measurement report is transmitted based on the request.

27. The one or more computer-readable storage media of claim 16, wherein the operation further comprises: Based on the MDT configuration, a third measurement is performed when the UE is in any of the RRC states; The third measurement is stored in the memory buffer; It is determined that the size of the memory buffer exceeds a threshold; as well as The third measurement is discarded from the memory buffer such that it is excluded from the recorded measurement report, wherein the third measurement is discarded based on at least one of the following: the priority of the third measurement, the timing of the third measurement, or the MDT configuration.

28. A method implemented by nodes of a network, the method comprising: Minimum Driven Test (MDT) configuration is transmitted to User Equipment (UE), the MDT configuration indicating that measurements should be performed and recorded by the UE across different Radio Resource Control (RRC) states, wherein the model is stored at the network, configured to use inputs based on the measurements, and includes an artificial intelligence model or a machine learning model; as well as Based on the MDT configuration, recorded measurement reports are received from the UE, including measurements performed and recorded by the UE when the UE is in the RRC_CONNECTED state.

29. The method of claim 28, wherein the recorded measurement report further comprises at least one of the following: the UE identifier, a Cell Radio Network Temporary Identifier (C-RNTI), a Globally Unique Temporary Identifier (GUTI), a timestamp for recording the measurement, an indication of when the UE received the MDT configuration, a cell identifier, an indication of the RRC state of the UE when the UE recorded the measurement, or UE location information.

30. The method of claim 28, wherein the MDT configuration indicates the type of data to be recorded, wherein the data is included in the recorded measurement report or transmitted separately from the recorded measurement report.

31. The method of claim 28, wherein the recorded measurement report indicates a destination address to which the recorded measurement report is to be transmitted by the node, wherein the destination may include a server configured for artificial intelligence, machine learning, or MDT.

32. The method of claim 28, wherein the recorded measurement report is received in multiple segments.

33. The method of claim 28, wherein a signaling radio bearer (SRB) is used to receive the recorded measurement report, and wherein the priority of the recorded measurement report is configurable.

Images