Enhancing data collection configuration for UE-side data collection beam management use case

By enabling UEs to request and indicate preferences for data collection configurations, the system addresses inefficiencies in beam management, allowing efficient data collection for AI/ML models and reducing overhead in wireless networking.

WO2026234485A1PCT designated stage Publication Date: 2026-11-12NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/IB2026/053940
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-04-21
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless networking technologies face inefficiencies in beam management due to time-consuming and non-scalable beam scanning operations, particularly as antenna array sizes increase, and there is a need for improved data collection configurations for AI/ML-based beam prediction models at the UE side.

Method used

Implementing a system where UEs can request and indicate preferences for data collection configurations, allowing network nodes to efficiently manage activated and deactivated reference signal configurations, reducing overhead and ensuring fair distribution based on UE capabilities.

Benefits of technology

Enables efficient data collection for UE-side AI/ML beam prediction by allowing UEs to immediately begin measurements on activated configurations, optimizing resource use and reducing signaling overhead.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure IB2026053940_12112026_PF_FP_ABST
    Figure IB2026053940_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method includes: receiving, by a user equipment (UE) from a network node, a message containing one or more UE data collection configuration options, wherein each UE data collection option includes an indication of an activation state being activated or deactivated; identifying, by the UE, one or more UE data collection configuration options for which the activation state is indicated as activated; selecting, by the UE, zero or more of the identified UE data collection configuration options; and performing measurements on each of the selected UE data collection configuration options.
Need to check novelty before this filing date? Find Prior Art

Description

ENHANCING DATA COLLECTION CONFIGURATION FOR UE-SIDE DATA COLLECTION BEAM MANAGEMENT USE CASE CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority from, and the benefit of, US Provisional Application No.63 / 802777, filed May 9, 2025, the contents of which are hereby incorporated by reference in their entirety.FIELD

[0002] Various example embodiments relate generally to apparatuses, methods, and computer program products that support enhancing data collection configuration for user equipment (UE)-side data collection beam management use case.BACKGROUND

[0003] Wireless networking provides significant advantages for user mobility. A user’s ability to remain connected while on the move provides advantages not only for the user, but also provides greater efficiency and productivity for society as a whole. As expectations for connection reliability, data speed, and lower power consumption, become more demanding, technology for wireless networking must also keep pace with such expectations. Accordingly, there is continuing interest in improving wireless networking technology.SUMMARY

[0004] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Some example embodiments will now be described with reference to the accompanying drawings.

[0006] FIG. 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0007] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0008] FIG. 3 is a diagram of an example of operations for signaling between a UE and a network apparatus, according to one illustrated aspect of the disclosure;

[0009] FIG. 4 is a diagram illustrating an indication of a preference for an activated configuration, according to one illustrated aspect of the disclosure;

[0010] FIG. 5 is a diagram illustrating an indication of a preference for a deactivated configuration, according to one illustrated aspect of the disclosure;

[0011] FIG. 6 is a set of tables illustrating explicit vs implicit indications of the activation state, according to one illustrated aspect of the disclosure; and

[0012] FIG. 7 is a diagram of an example of components of a user equipment or of a network apparatus, according to one illustrated aspect of the present disclosure.DETAILED DESCRIPTION

[0013] To support a new artificial intelligence / machine learning (AIZML)-enabled radio interface for the next cellular systems, 3rd Generation Partnership Project (3GPP) is currently investigating a work item for Release (Rel) 19. Beam management is one of the different pilot use cases for applying AI / ML model in the new radio (NR) radio interface. The different pilot use cases will also serve to identify a common AI / ML framework, including functional requirements of AI / ML architecture, which could be used in subsequent releases and will pave the way for the design of native AI / ML 6G networks. In the following, some aspects or example embodiments may be described by taking the use case of beam management as an example.

[0014] The Rel-19 beam management use case is further specified for spatial and / or time beam prediction. The scope of spatial beam prediction (denoted as BM-Case1) is to predict the best down link (DL) transmit (Tx) beam and / or DL Tx / Rx beam pairs in different spatial locations. Conversely, time-domain beam predictions (denoted as BM-Case2) aim to predict the best DL Tx beam and / or DL Tx / Rx beam pairs beam to use for next time instants. The primary motivation for supporting AI / ML-based beam management is overhead savings and latency reduction. It has been shown that ML algorithms enable predicting the serving beam for different user equipment (UE) locations and time instances, thus avoiding measuring the actual beam quality and saving those resources to be employed for data transmission and / or for the UE to increase the length of DRX. On the other hand, beam scanning operations such as those performed in procedure 1 (P1), procedure 2 (P2) and procedure 3 (P3) are time inefficient and not scalable when the size of antenna arrays increases. Therefore, ML algorithms can replace sequential beam scanning by recommending a reduced set of beams likely to contain the best beam index of the full beam scan.

[0015] It is noted that a set of beams to predict are indicated as “Set A” beams. The beam prediction model may predict the best beam ID and / or the RSRP value in Set A. Also, Set A may include Set B (when Set B is subset of Set A) or Set B may be different from Set A, e.g., Set B may be wide beams and Set A may be narrow beams.

[0016] For data collection for training beam prediction model, one of the main aspects currently discussed is data collection for training the AI / ML beam prediction model. Among the different aspects, the signaling aspect, the configuration of measurement and measurements report for data collection are considered.

[0017] Regarding the data collection for AI / ML model training at the UE side, some mechanisms focus on the potential specification impact of aspects such as data collection request triggered by UE, the UE reporting the supported / preferred configurations related to Set A and / or Set B beam measurements and the transmission of reference signals from the network. Regarding data collection for UE-side model training, UE may require flexibility to request the data collection. Channel State Information reference signal (CSI-RS) measurement enhancements may also be required for data collection at the UE side. For instance, by allowing the measurements of full or partial Set A beam (associated with a functionality) to have a longer periodicity than the Set B measurements. For the UE-side model, data collection configuration may be transmitted from gNB to UE to support the UE training of the model. One example is that the UE may have more details about the available beam codebook at the network.

[0018] Regarding UE behavior once initiating a request for UE-side data collection, UE provides its capabilities to the network (NW), indicating support for preference-based UE-side data collection configuration. NW provides the UE with a list of data collection configuration options, each identified by an index which can be referenced by the UE. The UE provides to the NW a list of zero or preferred data collection configurations afterwards. The NW decides accordingly whether to provide the UE a measurement configuration for UE-side data collection. The NW activates one or more data collection CSI-RS configurations based on its evaluation.

[0019] The present disclosure relates to products that support enhancing data collection configuration for user equipment (UE)-side data collection. Example use cases include beam management, channel state information (CSI) prediction, CSI compression, mobility, and positioning.

[0020] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled in the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0021] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0022] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS,3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.11 ax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0023] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit toward,” “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0024] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0025] FIG. 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5G NR and embodiments that involve aspects defined by 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0026] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-6) section 3.2, which is hereby incorporated by reference herein.

[0027] A gNB supports various protocol layers, e.g., Layer 1 (L1) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0028] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g.:o The physical layer offers to the MAC sublayer transport channels;o The MAC sublayer offers to the RLC sublayer logical channels;o The RLC sublayer offers to the PDCP sublayer RLC channels;o The PDCP sublayer offers to the SDAP sublayer radio bearers;o The SDAP sublayer offers to 5GC quality of service (QoS) flows;o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0029] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-6) section 6, which is hereby incorporated by reference herein.

[0030] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the F1 interface connected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0031] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en-gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0032] A gNB-CU-Control Plane (gNB-CU-CP) includes, e.g., a logical node hosting, e.g., the RRC and the control plane part of the PDCP protocol of the gNB-CU for an en-gNB or a gNB. The gNB-CU-CP terminates the E1 interface connected with the gNB-CU-User Plane (gNB-CU-UP) and the F1-C interface connected with the gNB-DU.

[0033] A gNB-CU-User Plane (gNB-CU-UP) includes, e.g., a logical node hosting, e.g., the user plane part of the PDCP protocol of the gNB-CU for an en-gNB, and the user plane part of the PDCP protocol and the SDAP protocol of the gNB-CU for a gNB. The gNB-CU-UP terminates the E1 interface connected with the gNB-CU-CP and the F1-U interface connected with the gNB-DU, e.g., according to 3GPP TS 38.401 V16.6.0 (2021-07) section 3.1, which is hereby incorporated by reference herein.

[0034] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, a gNB-DU, a gNB-CU-CP, or a gNB-CU-UP, or any combination of them.

[0035] A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or atleast one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 7 below.

[0036] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open-RAN (O-RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0037] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0038] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection with FIG. 7. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0039] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0040] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0041] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. 1 such that the UE 150 is in communication with the network system 100 through the radio access network (RAN) 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”, and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0042] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0043] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility management function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0044] Additional components and functions of the core network 210 may include an application function (AF) 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221 , management data analytics function (MDAF) 222, and operations and management function (OAM) 223.

[0045] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The UPF 226 identifies services from service providers, Internet access, and third party services, for example.

[0046] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data unit (PDU) session management, as well as manages session context with the UPF 226.

[0047] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide service to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0048] The UDM 217 generates authentication vectors for use by the AUSF 211 and AMF 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0049] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics in the providing of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The 0AM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0050] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system may not include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0051] As mentioned above, in accordance with aspects of the present disclosure, the present disclosure relates to control plane packet filter.

[0052] FIG. 3 is a diagram of example operations for signaling user equipment (UE) capability information to a network apparatus. The operations are performed by the components shown at the top of FIG. 3, which include a UE, and one or more network apparatus (e.g., network node, gNB, RAN node). Such components may be, for example, the same components described in connection with FIG. 1 and FIG. 2 or otherwise described above.

[0053] The UE may request among data collection configurations for the purpose of monitoring, training, or validating UE-side models from a set of data collection configuration options provided by the network node. One example of data collection signals are reference signals (RS). In one example, every UE which wants to collect data makes a request to the network node through a UEAssistancelnformation message. The network node may decide to transmit data collection signals which are useful to a large quantity of UEs, which means that the data collection reference signals associated with a data collection configuration might already be transmitting in the cell. UEs should be able to immediately collect data on activated data collection configurations without further configuration from the network node.

[0054] A problem that this causes is that all UEs of a particular vendor or hardware model may request the same data collection configuration option from the network node. Although the network node can disable requests, the network node has no basis for understanding which UEs to accept and which to deny as it doesn’t immediately know the signal quality experienced by the UE or whether the UE is an ideal candidate for data collection. Additionally, the network node can’t know the vendor or hardware model of the UE, so it is difficult to ensure fairness in data collection configurations among UEs.

[0055] The present disclosure enables the technical solution of providing an efficient way to collect data collection configuration preferences from UEs without extra overhead and to aggregate preferences from many UEs to determine the best data collection configuration.

[0056] The disclosed systems and methods determine and indicate activated and / or deactivated data collection configuration options for UE-side data collection, providing a solution to the above noted technical issues for UE-side data collection, enabling the UE to take appropriate actions on sending data collection request along with minimum overhead at the network node side.

[0057] At operation 301 a, the network node transmits a UECapabilityEnquiry message to the UE. The UE receives from the network node the UECapabilityEnquiry message.

[0058] At operation 301 b, the UE transmits to the network node a UECapabilitylnformation message. The network node receives from the UE the UECapabilitylnformation message.

[0059] At operation 302a, the network node transmits to the UE, a message containing data collection preferences. For example, this message may be an RRCReconfiguration message. The data collection preferences may be indexed. Each data collection configuration option includes a flag indicating whether the reference signals for the data collection configuration are transmitted or not, i.e., whether the reference signals are activated or deactivated. In aspects, the absence of the flag may imply an activation state of “deactivated.”

[0060] At operation 302b, the UE may transmit to the network node, a message containing zero or more data collection preferences. The UE can indicate a preference for a data collection configuration whether the data collection configuration option is activated or deactivated.

[0061] At operation 303, the UE may transmit to the network node, a message indicating an update in data collection configuration preference.

[0062] For example, the preferences may be provided by RRCReconfigurationComplete or UEAssistancelnfonvation messages.

[0063] In aspects, the measurement configurations may be provided from the network node via RRCReconfiguration (e.g., periodic CSI configuration) as in steps 305a and 305b. In aspects, measurement configurations may be activated or deactivated with a MAC-CE as in step 305c.

[0064] The measurement configuration corresponds, but is not limited to, at least one of the following measurements or measurement signals: Channel State Information Reference Signal; Demodulation Reference Signal; Phase Tracking Reference Signal; Synchronization Signal Block Reference Signal; or Positioning Reference Signal.

[0065] At operation 305a, the network node transmits to the UE, a second message containing Channel State Information Reference Signal (CSI-RS) configuration information.

[0066] At operation 305b, the UE transmits to the network node, a second response message acknowledging the configuration of operation 305a and containing zero or more data collection preferences. The UE may indicate a preference for a data collection configuration whether it is activated or deactivated.

[0067] The reference signal measurement configuration corresponds to, but is not limited to, one or more of the following configurations: CSI-ReportConfig; CSI-ReportConfigld; CSI-ResourceConfig; CSI-ResourceConfigld; NZP-CSI-RS-Resource; NZP-CSI-RS-Resourceld; NZP-CSI-RS-ResourceSet; NZP-CSI-RS-ResourceSetld; Measld; MeasObjectNR; MeasObjectld; ReportConfigNR; or ReportConfigld.

[0068] For example, the UE can provide its data collection configuration preference in RRCReconfigurationComplete after receiving data collection options from the network node or in UEAssistancelnfonvation after receiving data collection options from the network node, but after acknowledging the configuration in RRCReconfigurationComplete wherein preferences were not previously provided (e.g., can be provided for the first time) or where preferences are being updated. The UE can provide the preference regardless of whether the network node indicates that the data collection configuration is activated or deactivated.

[0069] Optionally, at operation 305, the network node transmits to the UE, an activation command for a data collection configuration option. The activation command could be carried in a MAC-CE. In one example, the UE receives from the network node, the MAC-CE for semipersistent CSI-RS activation. For example, to configure reference signal transmission for a data collection option, the the network node could have configured semipersistent CSI-RS, which may be enabled or disabled using a MAC-CE. Alternatively, a new MAC-CE specific to activating and deactivating a data collection configuration option could be used. If the network node enables an initially deactivated preferred data collection configuration, which was indicated as preference by a UE.

[0070] If the network node disables an activated data collection configuration, the network node can indicate that the data collection configuration is deactivated through disabling semi-persistent CSI-RS or the data collection configuration through a MAC-CE.

[0071] At operation 306, the network node transmits to the UE, one or more CSI-RS configurations.

[0072] The technical effect of the inclusion of the flag indicating whether reference signals for the data collection configuration are activated or deactivated is that a UE can immediately begin collecting measurements on activated reference signals for data collection without further signaling.

[0073] The ability for the UE to indicate a preference for an already activated data collection configuration enables the network node to determine whether or not to continue to transmit reference signals for data collection for a particular data collection option based on the number of UEs which have indicated the same data collection preference.

[0074] The use of semi-persistent CSI-RS or a controllable, i.e., capable of being activated and deactivated, data collection configuration provides the benefit of allowing the network node to enable or disable CSI-RS transmission or the data collection configuration for UEs which were previously informed that a data collection configuration was deactivated or activated, respectively.

[0075] The operations of FIG. 3 are merely examples, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include others not illustrated in FIG.3. In embodiments, the operations may not include every operation illustrated in FIG. 3. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 3. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0076] FIG. 4 is a diagram of example operations for signaling by a user equipment (UE) an indication of a preference for an activated configuration to a network apparatus. The operations are performed by the components shown at the top of FIG. 4, which include a UE, and one or more network apparatus (e.g., network node, gNB, RAN node). Such components may be, for example, the same components described in connection with FIG. 1 and FIG. 2 or otherwise described above.

[0077] Here, the UE may indicate a preference for an activated data collection option. This helps ensure that the configuration remains activated while the UE has a need to collect data based on its preferred data collection configuration option.

[0078] At operation 401, the network node transmits to the UE, data collection configuration options. For example, these may include 0: deactivated, 1: activated etc.

[0079] At operation 402, the UE transmits to the network node data collection configuration options.

[0080] The operations of FIG. 4 are merely examples, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include others not illustrated in FIG.4. In embodiments, the operations may not include every operation illustrated in FIG. 4. In embodiments,the operations may be implemented in a different order than that illustrated in FIG. 4. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0081] FIG. 5 is a diagram of example operations for signaling by a first user equipment (DE) an indication of a preference for a deactivated configuration to a network apparatus. The operations are performed by the components shown at the top of FIG. 5, which include a first UE, a second UE, and one or more network apparatus (e.g., network node, gNB, RAN node). Such components may be, for example, the same components described in connection with FIG. 1 and FIG. 2 or otherwise described above.

[0082] At operation 501, the network node transmits to the first UE, data collection configuration options. For example, these may include 0: deactivated, 1: activated, 2: deactivated.

[0083] At operation 502, the first UE provided a preference for a deactivated data collection configuration option (e.g., option 0), which the network node decided to activate.

[0084] At operation 503, in a case where the network node decides to activate data collection option, 0, the network node transmits to the first UE a message indicating an activation of data collection option 0.

[0085] At operation 504, the second UE may optionally provide its preference for an activated data collection configuration, but the second UE does not have to. The second UE may simply start measuring. At operation 505, the second UE may provide to the network node a preference for a deactivated data collection configuration option (e.g., 0).

[0086] FIG. 5 illustrates that the second UE can benefit from the previous activation of what happened to be the preference of the second UE through signaling “activated.”

[0087] The operations of FIG. 5 are merely examples, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include others not illustrated in FIG.5. In embodiments, the operations may not include every operation illustrated in FIG. 5. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 5. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0088] The following describes operations from the perspective of a UE. From such a perspective, a method may include: receiving, by a user equipment (UE) from a network node, a message containing one or more UE data collection configuration options, wherein each UE data collection option includes an indication of an activation state being activated or deactivated (e.g., FIG. 5, operation 501); identifying, by the UE, one or more UE data collection configuration options for which the activation state is indicated as activated (e.g., FIG. 5, operation 502); selecting, by the UE, zero or more of the identified UE data collection configuration options (e.g., FIG. 5, operation 503); and performing measurements on each of the selected UE data collection configuration options (e.g., FIG. 5, operation 504).

[0089] The following describes operations from the perspective of a network apparatus. From such a perspective, a method may include: transmitting, by a network node to a user equipment (UE), amessage including DE data collection options (e.g., FIG. 5, operation 501); receiving, by the network node from the DE, an indication of DE data collection preferences; and activating or deactivating one or more DE data collection options (e.g., FIG. 5, operation 501); and transmitting, by the network node to the DE, a message containing DE data collection configuration options, wherein each activated DE data collection configuration option includes a flag with an indication of activated (e.g., FIG. 5, operation 503).

[0090] FIG. 6 is a set of tables illustrating the explicit vs. implicit indication of activated vs deactivated. The tables shows several examples configuration IDs that are used in the flow diagrams of FIGS 4 and 5. In the first example table, for each configuration ID, an activation state of activated or deactivated is explicitly indicated. For the second example table, for configuration ID 2, the Activation state field is absent.

[0091] FIG. 7 is a block diagram of a wireless station or node (e.g., UE, user device, AP, BS, eNB, gNB, RAN node, network node, transmission reception point (TRP), or other node) 700, according to one illustrated aspect of the present disclosure. The wireless station 700 may include, for example, one or more (e.g., two as shown in FIG. 7) RF (radio frequency) or wireless transceivers 702A, 702B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit / entity (controller) 708 to execute instructions or software and control transmission and receptions of signals, and a memory 706 to store data and / or instructions.

[0092] Processor 704 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 704, which may be a baseband processor, for example, may generate messages, packets, frames, or other signals for transmission via wireless transceiver 702 (702A or 702B). Processor 704 may control transmission of signals or messages over a wireless network and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 702, for example). Processor 704 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 704 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and / or any combination of these. Using other terminology, processor 704 and transceiver 702 together may be considered as a wireless transmitter / receiver system, for example.

[0093] In addition, referring to FIG. 7, a controller (or processor) 708 may execute software and instructions, and may provide overall control for the station 700, and may provide control for other systems not shown in FIG. 7, such as controlling input / output devices (e.g., display, keypad), and / or may execute software for one or more applications that may be provided on wireless station 700, such as, for example, an email program, audio / video applications, a word processor, a Voice over IP application, or other application or software.

[0094] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 704, or other controller or processor, performing one or more of the functions or tasks described above.

[0095] According to another example embodiment, RF or wireless transceiver(s) 702A / 702B may receive signals or data and / or transmit or send signals or data. Processor 704 (and possibly transceivers 702A / 702B) may control the RF or wireless transceiver 702A or 702B to receive, send, broadcast or transmit signals or data.

[0096] Example embodiments are provided or described for each of the example methods, including: An apparatus (e.g., 700, FIG. 7) including means (e.g., processor 704, RF transceivers 702A and / or 702B, and / or memory 706, in FIG. 7) for carrying out any of the methods; a non-transitory computer-readable storage medium (e.g., memory 706, FIG. 7) comprising instructions stored thereon that, when executed by at least one processor (processor 704, FIG. 7), are configured to cause a computing system (e.g., 700, FIG.7) to perform any of the example methods; and an apparatus (e.g., 700, FIG. 7) including at least one processor (e.g., processor 704, FIG. 7), and at least one memory (e.g., memory 706, FIG. 7) including computer program code, the at least one memory (706) and the computer program code configured to, with the at least one processor (704), cause the apparatus (e.g., 700) at least to perform any of the example methods.

[0097] Further embodiments of the present disclosure include the following examples.

[0098] Example 1.1. A method comprising:receiving, by a user equipment (UE) from a network node, a message containing one or more UE data collection configuration options, wherein each UE data collection option includes an indication of an activation state being activated or deactivated;identifying, by the UE, one or more UE data collection configuration options for which the activation state is indicated as activated;selecting, by the UE, zero or more of the identified UE data collection configuration options; and performing measurements on each of the selected UE data collection configuration options.

[0099] Example 1.2. The method of Example 1.1, wherein the indication of activated or deactivated state further comprises an explicit activation state of deactivated.

[0100] Example 1.3. The method of Example 1.1, wherein the message including UE data collection configuration options is included in an RRC Reconfiguration message.

[0101] Example 1.4. The user equipment (UE) of Example 1.1, further comprising: transmitting, by the UE to the network node, a message including UE data collection configuration preferences.

[0102] Example 1.5. The method of Example 1.4, wherein the message including UE data collection configuration preferences is contained in either an RRCReconfigurationComplete message or a UEAssistancelnformation message.

[0103] Example 1.6. The method of Example 1.4, wherein the UE data collection configuration preferences include a preference for a UE data collection configuration whether any UE data collection configuration option of the UE data collection configuration options are activated or deactivated.

[0104] Example 1.7. The method of any previous Example, wherein the UE data collection option corresponds to a reference signal measurement configuration.

[0105] Example 1.8. The method of Example 1.7, wherein the reference signal measurement configuration corresponds to at least one of the following configurations:CSI-ReportConfig;CSI-ReportConfigld;CSI-ResourceConfig;CSI-ResourceConfigld;NZP-CSI-RS-Resource;NZP-CSI-RS-Resourceld;NZP-CSI-RS-ResourceSet;NZP-CSI-RS-ResourceSetld;Measld;MeasObjectNR;MeasObjectld;ReportConfigNR; orReportConfigld.

[0106] Example 1.9. The method of Example 1.8, wherein the measurement configuration corresponds to at least one of the following measurements or measurement signals:Channel State Information Reference Signal;Demodulation Reference Signal;Phase Tracking Reference Signal;Synchronization Signal Block Reference Signal; orPositioning Reference Signal.

[0107] Example 1.10. The method of any of the preceding Examples, further comprising:receiving, by the UE from the network node, a second message containing including UE data collection configuration options; andtransmitting, by the UE to the network node, a message indicating an update of preference for one or more a data collection configuration option.

[0108] Example 1.11. The method of any of Example 1.1 to Example 1.3, further comprising: receiving, by the UE from the network node, a second message containing UE data collection configuration options; anddetermining, by the UE based on an activation state of deactivated associated with a UE data collection configuration option, that a UE data collection configuration option is deactivated; and ceasing to perform measurements on a UE data collection configuration option which has been indicated as deactivated.

[0109] Example 1.12. The method of Example 1.1, further comprising:receiving, by the UE from the network node, a Medium Access Control Control Element (MAC-CE) message that activates or deactivates a UE data collection configuration corresponding to a UE data collection configuration option.

[0110] Example 1.13. The method of Example 1.12, further comprising:activating, by the UE, a UE data collection configuration in response to receiving the MAC-CE message indicating that the UE data collection configuration is activated.

[0111] Example 1.14. The method of Example 1.12, further comprising:deactivating, by the UE, a UE data collection configuration in response to receiving the MAC-CE message indicating that the UE data collection configuration is deactivated.

[0112] Example 1.15. The method of Example 1.1, wherein absence of the indication of a state of deactivated comprises an implicit activation state of deactivated.

[0113] Example 1.16. A method, comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, cause the UE at least to perform a method as in any one of Examples 1.1 to 1.15.

[0114] Example 1.17. A processor-readable medium storing instructions which, when executed by at least one processor of a user equipment (UE), cause the UE at least to perform a method as in any one of Examples 1.1 to 1.15.

[0115] Example 1.18. A method, comprising:transmitting, by a network node to a user equipment (UE), a message including UE data collection options;receiving, by the network node from the UE, an indication of UE data collection preferences; activating or deactivating one or more UE data collection options; andtransmitting, by the network node to the UE, a message containing UE data collection configuration options, wherein each activated UE data collection configuration option includes a flag with an indication of activated.

[0116] Example 1.19. A network apparatus comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, cause the network apparatus at least to perform a method as in Example 1.18.

[0117] Example 1.20. A processor-readable medium storing instructions which, when executed by at least one processor of a network apparatus, causes the network apparatus at least to perform a method as in Example 1.18.

[0118] The preceding Examples may be implemented in algorithm(s), encoded in a distribution medium or computer program product(s), and as method(s) performed by apparatus(es). An apparatus may comprise means for causing the apparatus at least to perform the method(s). The means may comprise at least one processor; and at least one memory storing algorithm as instructions that, when executed by the at least one processor, cause the apparatus at least to perform the method(s).

[0119] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[0120] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of” may refer to two or more.

[0121] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).”

[0122] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta-languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinctionis made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[0123] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

WHAT IS CLAIMED IS:

1. A method, comprising:receiving, by a user equipment (UE) from a network node, a message containing one or more UE data collection configuration options, wherein each UE data collection option includes an indication of an activation state being activated or deactivated;identifying, by the UE, one or more UE data collection configuration options for which the activation state is indicated as activated;selecting, by the UE, zero or more of the identified UE data collection configuration options; and performing measurements on each of the selected UE data collection configuration options.

2. The method of claim 1 , wherein the indication of activated or deactivated state further comprises an explicit activation state of deactivated.

3. The method of claim 1 , wherein the message including UE data collection configuration options is included in an RRC Reconfiguration message.

4. The method of claim 1 , further comprising:transmitting, by the UE to the network node, a message including UE data collection configuration preferences.

5. The method of claim 4, wherein the message including UE data collection configuration preferences is contained in either an RRCReconfigurationComplete message or a UEAssistancelnformation message.

6. The method of claim 4, wherein the UE data collection configuration preferences include a preference for a UE data collection configuration whether any UE data collection configuration option of the UE data collection configuration options is activated or deactivated.

7. The method of any previous claim, wherein the UE data collection option corresponds to a reference signal measurement configuration.

8. The method of claim 7, wherein the reference signal measurement configuration corresponds to at least one of the following configurations:CSI-ReportConfig;CSI-ReportConfigld;CSI-ResourceConfig;CSI-ResourceConfigld;NZP-CSI-RS-Resource;NZP-CSI-RS-Resourceld;NZP-CSI-RS-ResourceSet;NZP-CSI-RS-ResourceSetld;Measld;MeasObjectNR;MeasObjectld;ReportConfigNR; orReportConfigld.

9. The method of claim 8, wherein the measurement configuration corresponds to at least one of the following measurements or measurement signals:Channel State Information Reference Signal;Demodulation Reference Signal;Phase Tracking Reference Signal;Synchronization Signal Block Reference Signal; orPositioning Reference Signal.

10. The method of any of the preceding claims, further comprising:receiving, by the UE from the network node, a second message containing including UE data collection configuration options; andtransmitting, by the UE to the network node, a message indicating an update of preference for one or more a data collection configuration option.

11. The method of any of claim 1 to claim 3, further comprisingreceiving, by the UE from the network node, a second message containing UE data collection configuration options; anddetermining, by the UE based on an activation state of deactivated associated with a UE data collection configuration option, that a UE data collection configuration option is deactivated; andceasing to perform measurements on a UE data collection configuration option which has been indicated as deactivated.

12. The method of claim 1, further comprising:receiving, by the UE from the network node, a Medium Access Control Control Element (MAC-CE) message that activates or deactivates a UE data collection configuration corresponding to a UE data collection configuration option.

13. The method of claim 12, further comprising:activating, by the UE, a UE data collection configuration in response to receiving the MAC-CE message indicating that the UE data collection configuration is activated.

14. The method of claim 12, further comprising:deactivating, by the UE, a UE data collection configuration in response to receiving the MAC-CE message indicating that the UE data collection configuration is deactivated.

15. The method of claim 1 , wherein absence of the indication of a state of deactivated comprises an implicit activation state of deactivated.

16. A user equipment (UE), comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, cause the UE at least to perform a method as in any one of claims 1 to 15.

17. A processor-readable medium storing instructions which, when executed by at least one processor of a user equipment (UE), cause the UE at least to perform a method as in any one of claims 1 to 15.

18. A method, comprising:transmitting, by a network node to a user equipment (UE), a message including UE data collection options;receiving, by the network node from the UE, an indication of UE data collection preferences; activating or deactivating one or more UE data collection options; andtransmitting, by the network node to the UE, a message containing UE data collection configuration options, wherein each activated UE data collection configuration option includes a flag with an indication of activated.

19. A network apparatus comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, cause the network apparatus at least to perform a method as in claim 18.

20. A processor-readable medium storing instructions which, when executed by at least one processor of a network apparatus, causes the network apparatus at least to perform a method as in claim 18.