Configuring applicable data collection configuration in a ue
The UE's ability to assess and signal data collection configuration applicability addresses inefficiencies in conventional methods, enhancing the scalability and efficiency of AI/ML model training data collection by ensuring configurations align with its current status and resource availability.
Patent Information
- Application Number
- PCT/EP2026/061695
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-05
- Filing Date
- 2026-04-23
- Publication Date
- 2026-11-12
AI Technical Summary
Conventional data collection procedures for AI/ML models are not optimal, lacking mechanisms for UEs to determine and signal the applicability of data collection configurations based on their current status and resource availability, leading to inefficient and non-scalable UE feedback.
A method and apparatus for User Equipment (UE) to receive, evaluate, and transmit configuration information, indicating whether received data collection configurations meet specific conditions related to its status and resource availability, allowing it to perform data collection procedures efficiently.
Enables UEs to determine and signal preferred data collection configurations, optimizing resource utilization and improving the scalability and efficiency of data collection for AI/ML models.
Smart Images

Figure EP2026061695_12112026_PF_FP_ABST
Abstract
Description
[0001] TITLE
[0002] CONFIGURING APPLICABLE DATA COLLECTION CONFIGURATION IN A UE
[0003] TECHNOLOGICAL FIELD
[0004] Examples of the disclosure relate to apparatuses, methods and computer programs for data collection. Some examples relate to management of data collection configuration(s) for collecting training data for Artificial Intelligence / Machine Learning, AI / ML, use cases. Some examples, though without prejudice to the foregoing, relate to UE side data collection configuration(s) for UE side collecting of training data for UE side AI / ML models for Beam Management, BM.
[0005] BACKGROUND
[0006] Conventional apparatuses and procedures for data collection (e.g. data collection for collecting training data for AI / ML models) are not optimal. In some circumstances, it may be desirable to provide improved apparatuses and procedures for data collection. In some circumstances, it may be desirable to improve management of data collection configuration(s) (e.g. configuration(s) for collecting training data) to be applied in a data collection procedure. In some circumstances, it may be desirable to provide improved UE feedback on UE side data collection configuration(s). In some circumstances, it may be desirable to enable a UE to indicate whether and which UE side data collection configurations are applicable.
[0007] BRIEF SUMMARY
[0008] The invention is defined in the independent claims.
[0009] According to various, but not necessarily all, examples of the disclosure there are provided examples as claimed in the appended claims. Any examples and features described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the invention.According to various, but not necessarily all, examples there is provided there is provided a method, performed by a User Equipment, UE, wherein the method comprises:
[0010] receiving, from a network, configuration information comprising at least one configuration for configuring the UE to perform a data collection procedure; determining that the received at least one configuration does not meet at least one condition;
[0011] transmitting, to the network, first information, wherein the first information comprises at least one indication that the at least one received configuration has been determined not to meet the at least one condition; determining, after transmitting the first information, that the at least one configuration meets the at least one condition;
[0012] transmitting, to the network, second information comprising at least one indication that the at least one configuration meets the at least one condition; wherein the transmitting is based at least in part on the determining that the at least one configuration meets the at least one condition; and
[0013] performing the data collection procedure, wherein the performing of the data collection procedure is based at least in part on the transmitting of the second information, and wherein the data collection procedure is performed based at least in part on the at least one configuration that has been determined to have met the at least one condition.
[0014] According to at least some examples of the disclosure there is provided an apparatus comprising means for performing at least part of one or more methods described herein.
[0015] According to various, but not necessarily all, embodiments there is provided an apparatus comprising:
[0016] at least one processor; and
[0017] at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least a part of one or more methods described herein.According to various, but not necessarily all, examples of the disclosure there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least part of one or more methods described herein.
[0018] According to various, but not necessarily all, examples of the disclosure there is provided a non-transitory computer readable medium, when executed by an apparatus, causes the apparatus to perform at least a part of one or more methods described herein.
[0019] According to various, but not necessarily all, examples of the disclosure there is provided:
[0020] a module, circuitry, a chipset comprising processing circuitry, a device and / or a system
[0021] configured to (or comprising means for) perform(ing) at least a part of one or more methods described herein.
[0022] According to various, but not necessarily all, embodiments there are provided examples as claimed in the appended claims.
[0023] The following portion of this ‘Brief Summary’ section describes various features that can be features of any of the examples described in the foregoing portion of the ‘Brief Summary’ section mutatis mutandis.
[0024] In some but not necessarily all examples, wherein the first information further comprises information indicative of at least one cause of the at least one configuration not meeting the at least one condition.
[0025] In some but not necessarily all examples, the determining that the at least one configuration meets the at least one condition is performed a pre-determined amount of time after transmitting the first information.
[0026] In some but not necessarily all examples, the at least one configuration comprises at least one reporting configuration that refers to at least one set of resources for one ormore reference signals; and wherein performing the data collection procedure comprises:
[0027] receiving the one or more reference signals from the network, wherein the receiving is based at least in part on the at least one set of resources; performing one or more measurements on the one or more reference signals, wherein the measurements are performed based at least in part on at least one of:
[0028] the configuration information; or
[0029] the at least one reporting configuration.
[0030] In some but not necessarily all examples, the configuration information further comprises at least one indication of at least one type of reporting that the UE is to perform.
[0031] In some but not necessarily all examples, a first type of reporting is indicated in the configuration information, and
[0032] the UE further performs:
[0033] logging data collected via the data collection procedure, wherein the logging is based at least in part on receiving the indication of the first type of reporting.
[0034] In some but not necessarily all examples, the UE further performs:
[0035] transmitting the logged data to the network.
[0036] In some but not necessarily all examples, a second type of reporting is indicated in the configuration information, and
[0037] the UE further performs:
[0038] transmitting, to the network, data collected via the data collection procedure, wherein the transmitting is based at least in part on receiving, in the configuration information, the indication of the second type of reporting.
[0039] In some but not necessarily all examples, the transmitting comprises:establishing a data connection between the UE and the network, and wherein the establishing is based at least in part on receiving, in the configuration information, the indication of the second type of reporting.
[0040] In some but not necessarily all examples, the second information further comprises at least one indication that the UE is ready to perform the data collection procedure in accordance with the at least one configuration that has been determined to meet the at least one condition.
[0041] In some but not necessarily all examples, the performing of the data collection procedure is based at least in part on the transmitting of the indication that the UE is ready to perform the data collection procedure in accordance with the at least one configuration that has been determined to meet the at least one condition and wherein the at least one of the plurality of configurations is associated with at least one measurement configuration.
[0042] In some but not necessarily all examples, the at least one condition is based at least in part on at least one of the following:
[0043] a status of the UE;
[0044] a load on the UE;
[0045] a utilization status of at least one resource of the UE;
[0046] an availability of at least one resource of the UE; or
[0047] an ability of the UE to confirm to one or more requirements defined in the at least one configuration.
[0048] In some but not necessarily all examples, the UE further performs:
[0049] determining, after transmitting the second information, that the at least one configuration does not meet the at least one condition; and
[0050] transmitting, to the network, third information comprising at least one indication that the at least one configuration does not meet the at least one condition; wherein the at least one indication is based at least in part on the determining that the at least one configuration does not meet the at least one condition.In some but not necessarily all examples, determining, after transmitting the second information, that the at least one configuration does not meet the at least one condition occurs whilst the UE is performing the data collection procedure, and the UE further performs:
[0051] suspending, based at least in part on determining that the at least one configuration no longer meets the at least one condition, the data collection procedure.
[0052] In some but not necessarily all examples, the third information further comprises at least one of:
[0053] information indicative of at least one cause of the at least one configuration not meeting the at least one condition;
[0054] at least one indication that the UE has logged data that has been collected via the data collection procedure using the at least one configuration; or at least one indication of an amount of logged data that has been collected via the data collection procedure using the at least one configuration.
[0055] In some but not necessarily all examples, the UE further performs:
[0056] receiving, from a device, whilst the UE is in an idle connection state, a request to perform the data collection procedure; and
[0057] transmitting, to the network, a request to transition to a connected state, wherein the transmitting is based at least in part on receiving the request, and wherein the request to transition to the connected state comprises at least one indication that the request to transition to the connected state is for the purpose of performing the data collection procedure.
[0058] In some but not necessarily all examples, the UE further performs:
[0059] receiving, from a device, whilst the UE is in a connected state, a request to perform the data collection procedure;
[0060] transmitting, to the network, a request to initiate the data collection procedure, wherein the transmitting is based at least in part on receiving the request; and wherein the configuration information is received from the network based at least in part on the transmitted request.In some but not necessarily all examples:
[0061] the at least one configuration for configuring the UE to perform a data collection procedure comprises a plurality of configurations for configuring the UE to perform a data collection procedure;
[0062] determining, after transmitting the first information, that the at least one configuration meets the at least one condition comprises determining, after transmitting the first information, that a set of configurations of the received plurality of configurations meets the at least one condition;
[0063] wherein the second information further comprises at least one indication that the UE is ready to perform the data collection procedure in accordance with a subset of the set of configurations;
[0064] wherein the data collection procedure is performed based at least in part on the subset of the set of configurations; and
[0065] the UE further performs:
[0066] determining that the subset of configurations does not meet the at least one condition; and
[0067] switching:
[0068] from performing the data collection procedure based at least in part on the subset of configurations that does not meet the at least one condition, to performing the data collection procedure based at least in part on at least one of the remaining configurations of the set of configurations that meets the at least one condition, wherein the switching is based at least in part on determining that the subset of configurations does not meet the at least one condition.
[0069] While the above examples of the disclosure and optional features are described separately, it is to be understood that their provision in all possible combinations and permutations is contained within the disclosure. It is to be understood that various examples of the disclosure can comprise any or all the features described in respect of other examples of disclosure, and vice versa. Also, it is to be appreciated that any one or more or all the features, in any combination, may be implemented by / comprised in / performable by an apparatus, a method, and / or instructions as desired, and as appropriate.The description of a function and / or action should additionally be considered to also disclose any means suitable for performing that function and / or action. Functions and / or actions described herein can be performed in any suitable way using any suitable method. The description of a function and / or action should additionally be considered also to disclose instructions, which can be stored in at least one memory that, when executed by at least one processor, cause an apparatus to perform that function.
[0070] BRIEF DESCRIPTION
[0071] Some examples will now be described with reference to the accompanying drawings in which:
[0072] FIG. 1 shows an example of the subject matter described herein;
[0073] FIG. 2 shows another example of the subject matter described herein;
[0074] FIG. 3 shows another example of the subject matter described herein;
[0075] FIG. 4 shows another example of the subject matter described herein;
[0076] FIG. 5 shows another example of the subject matter described herein;
[0077] FIG. 6 shows another example of the subject matter described herein;
[0078] FIG. 7 shows another example of the subject matter described herein;
[0079] FIG. 8 shows another example of the subject matter described herein;
[0080] FIG. 9 shows another example of the subject matter described herein;
[0081] FIG. 10 shows another example of the subject matter described herein; and FIG. 11 shows another example of the subject matter described herein.
[0082] ABBREVIATIONS / DEFINITIONS
[0083] Certain abbreviations that may be found in the present disclosure are herein defined as follows:
[0084] Al Artificial Intelligence
[0085] AS Access Stratum
[0086] BM Beam Management
[0087] CSI Channel State Information
[0088] gNB Next generation NodeB, 5G / NR / NG Base Station
[0089] ML Machine LearningNW Network
[0090] OAM Operations, Administration and Management
[0091] OTT Over The Top
[0092] PDU Protocol Data Unit
[0093] RRC Radio Resource Control
[0094] RS Reference Signal
[0095] UE User Equipment
[0096] DETAILED DESCRIPTION
[0097] FIG. 1 schematically illustrates an example of a network 100 suitable for use with examples of the present disclosure. The network (which may be referred to as NW) comprises a plurality of nodes 101 (which may be referred to as network nodes or nodes of the network), including:
[0098] • terminal nodes 110 (which may be referred to as: terminal apparatuses, terminal devices or User Equipment, UE);
[0099] • access nodes 120 (which may be referred to as: access apparatuses, gNodeBs, gNBs, or Base Stations, BSs); and
[0100] • one or more core nodes 130 (which may be referred to as: core apparatuses, core functions, core entities, core network nodes or core network entities - one core node / function / entity of which being an Access and Mobility Management Function, AMF).
[0101] The access nodes 120 and core nodes 130 may be referred to as Network Entities, NE, 102.
[0102] The terminal nodes 110 and access nodes 120 communicate with each other. The access nodes 120 communicate with the core nodes 130. One or more access nodes 120 may, in some but not necessarily all examples, communicate with each other. One or more core network nodes 130 may, in some but not necessarily all examples, communicate with each other.
[0103] The network 100, in the example illustrated in FIG. 1, comprises a radio telecommunications network in which at least some of the terminal nodes 110 andaccess nodes 120 communicate with each other using transmission / reception of radio waves. In this regard, the network 100 comprises a Radio Access Network, RAN, such as a cellular network comprising a plurality of cells 122 each served by an access node 120. The access nodes 120 comprise cellular radio transceivers. The terminal nodes 110 comprise cellular radio transceivers.
[0104] In the example illustrated and discussed below, the network 100 is a New Radio, NR, network of the Third Generation Partnership Project, 3GPP, and its fifth generation, 5G, New Radio, NR, technology. It is to be appreciated, however, that in other examples, the network 100 may be a network beyond 5G, for example a next generation (i.e. sixth generation, 6G) Radio Network that is currently under development (i.e. an evolution of the NR network and its 5G technology).
[0105] The interfaces between the terminal nodes 110 and the access nodes 120 are radio interfaces 124 (e.g., Uu interfaces). The interfaces between the access nodes 120 and one or more core nodes 130 are backhaul interfaces 128 (e.g., S1 and / or Next Generation, NG, interfaces).
[0106] Depending on the exact deployment scenario, the access nodes 120 may be RAN nodes such as NG-RAN nodes. NG-RAN nodes may be gNodeBs, gNBs, that provide NG user plane and control plane protocol terminations towards the UE. The gNBs are connected by means of NG interfaces to a 5G Core, 5GC, not least for example to an Access and Mobility Management Function, AMF, by means of an NG Control Plane, NG-C, interface and to a User Plane Function, UPF, by means of an NG User Plane, NG-U, interface. The AMF may be connected by means of an N1 interface to the UE (not shown). The access nodes 120 may be interconnected with each other by means of Xn interfaces 126.
[0107] The cellular network 100 may be configured to operate in licensed frequency bands, or unlicensed frequency bands (not least such as: unlicensed bands that rely upon a transmitting device to sense the radio resources / medium before commencing transmission, such as via a Listen Before Talk, LBT, procedure; and a 60GHz unlicensed band where beamforming may be required to achieve required coverage).The access nodes 120 may be deployed in an NG standalone operation / scenario. The access nodes 120 may be deployed in a NG non-standalone operation / scenario. The access nodes 120 may be deployed in a Carrier Aggregation, CA, operation / scenario. The access nodes 120 may be deployed in a Dual Connectivity, DC, operation / scenario, i.e., Multi Radio Access Technology - Dual Connectivity, MR-DC, or NR-DC. The access nodes 120 may be deployed in a Multi Connectivity, MC, operation / scenario.
[0108] In such non-standalone / dual connectivity deployments, the access nodes 120 may be interconnected to each other by means of X2 or Xn interfaces, and connected to an Evolved Packet Core, EPC, by means of an S1 interface or to the 5GC by means of a NG interface.
[0109] One or more terminal nodes 110, in addition to being capable of communicating (i.e. with other terminal nodes) via access nodes 120 of the network 100, may also be capable of and configured to communicate directly with one or more other terminal nodes. In this regard, the terminal node may be capable of and configured to perform device-to-device, D2D, communication - which may be referred to as Sidelink, SL, communication. Such D2D / SL communication may use a PC5 interface. PC5 refers to a reference point where the terminal node communicates directly with another terminal node over a direct channel (i.e. communication via an access node is not required). D2D communications may be short-range, networkless, direct communications. SL in New Radio (NR) is defined in 3GPP’s release 16 of 5G NR.
[0110] In the example of FIG. 1 the core node 130 (i.e. 5GC) is shown as a single entity. In some examples the core node 130 could be distributed across a plurality of entities. For example, the core node 130 could be cloud based or distributed in any other suitable manner. The core node / core entities may provide one or more functions, not least such as: User Plane Function UPF, Session Management Function SMF, Policy Control Function PCF, Application Function AF, Location Management Function, LMF, and Access and Mobility Management Function, AMF.The access nodes 120 are network elements in the network responsible for radio transmission and reception in one or more cells 122 to or from the terminal nodes 110. The access nodes 120 are the network termination of a radio link. Each access node may be a Transmission Reception Point, TRP, or may host one or more TRPs.
[0111] An access node 120 may be implemented as a single network equipment, or have a split architecture that is disaggregated / distributed over two or more access nodes, such as a Centralized / Control Unit, CU, a Distributed Unit, DU, a Remote Radio Head-end, RRH, using different functional-split architectures and different interfaces.
[0112] The terminal nodes 110 are network elements in the network that terminate the user side of the radio link. They are devices allowing access to network services.
[0113] Terminal node 110 functionalities may be performed also by Mobile Termination, MT, part of an Integrated Access and Backhaul, IAB, node. The terminal nodes 110 may be referred to as User Equipment, UE, mobile equipment, mobile terminals, or mobile stations.
[0114] In the following description:
[0115] • a terminal node of a network (i.e. wherein the network comprises a RAN / cellular network not least such as a 5G or 6G next generation RAN) be referred to simply as UE 110;
[0116] • an access node of the network may be referred to interchangeably as BS 120 or gNB 120;
[0117] There now follows a brief discussion of data collection.
[0118] In the context of data collection for AI / ML use cases, a UE may make measurements and collect data needed to train an AI / ML model. Data collection configuration including measurement configuration, reporting configuration and logging configuration (if supported) may be provided by OAM, CN, OTT to the NGRAN (e.g. gNB). The measurements may be configured by a NG-RAN, particularly a gNB, based on a UE’s capability information. Data collection configuration may have two aspects - one aspect relates to what measurements the UE is to make (i.e. a measurement configuration) and the other relates to how to report the measured datato a data collection entity (i.e. a reporting configuration). The data collection entity can be either a training node where the training of the AI / ML is being performed or an intermediate node collecting all the measurements and forwarding the same one to the training node. The nodes can be: a CN entity; an entity within an Operations, Administration and Management, OAM, domain; a UE or a UE side training server (e.g. an Over The Top, OTT, server).
[0119] Even though a configuration of the measurements, for example, in a beam management use case, may be similar for both data collection at a UE for in UE side models and data collection at the NW for NW side models, a difference between UE side and NW side data collection may differ in how UE is to be involved in the choice of data collection configuration to be applied, as well as which entity is collecting the data. In both cases, logging could happen within the UE. However, UE using a control plane for data reporting may be in-efficient and non-scalable for UE side models. Even though the NW has a context of a UE, UE may be in the best position to collect data or measurements for UE side models.
[0120] A UE may be able to request the NW to start data collection and, in response, the NW may send to the UE a list of data collection configurations from which the UE may indicate its preference. However, currently there is no defined mechanism or signaling for the NW to determine whether a configuration sent to UE for data collection purposes is applicable or not (i.e. whether or not a data collection configuration is relevant / suitable for the UE, e.g. based on the UE’s current status / resource availability). Currently there is no defined mechanism or signaling for enabling a UE to signal that a previously in-applicable data collection configuration is no longer in-applicable but is now applicable. Currently there is no defined mechanism or signaling for enabling a UE to signal that a previously applicable data collection configuration is no longer applicable but is now in-applicable. Currently there is no defined mechanism for the NW to identify whether a UE’s connection request is explicitly for UE side data collection. Currently there is no defined UE behavior to evaluate and select preferred data collection configuration.
[0121] Various examples of the disclosure may seek to address such issues.Various examples of the disclosure may seek to provide a procedure and signalling for enabling a UE to determine one or more preferred data collection configurations and to report the same to the NW. Such a preferred data collection configuration may be based on whether or not the data collection configuration is applicable for the UE, i.e. whether a data collection configuration is relevant / suitable for the UE, e.g. based on the UE’s current status / resource availability.
[0122] As will be set out and discussed in further detail below, various examples of the disclosure may seek to provide a mechanism in which the UE determines applicability for each candidate data collection configuration it receives, and the UE reports the applicability of each candidate data collection configuration to the NW. In this regard, various examples of the disclosure may seek to provide a mechanism for the UE to inform the NW of the UE’s preference of candidate data collection configuration(s), and also for the UE to inform the NW of the UE’s readiness to perform data collection using its preferred / applicable candidate data collection configuration(s).
[0123] FIG. 2 schematically illustrates an example of a procedure 200 and a signaling framework - between a UE 110 and a NW 100 (e.g. a network entity, NE, 102 such as a gNB 120 serving the UE) for supporting the procedure 200.
[0124] In block 201, the UE receives, from the NW (e.g. from the gNB), configuration information 211. The configuration information 211 comprises at least one configuration 212 for configuring the UE to perform a data collection procedure.
[0125] In some examples, the data collection procedure is a procedure for collecting data (e.g. training data) for AI / ML based beam management of UE side models.
[0126] In some examples, the configuration information comprises one or more data collection configurations for performing a data collection procedure. In some examples, the one or more data collection configurations comprise one or more measurement configurations. In some examples, one or more measurement configurations comprise one or more configurations for configuring UE to measure one or more reference signals, RSs (e.g. CSI RS) and report the RS measurements(for example: CSI-RS Resource Indicator, CRI; SS / PBCH Block Resource Indicator. SSBRI; and / or Layer 1 Reference Signal Received Power, L1-RSRP). Such measurements may be used as training data for training UE-sided AI / ML models for BM.
[0127] As will be discussed in further detail below with regards to step 5 of FIG. 3, in some examples, the configuration information 211 is an RRC Reconfiguration message. For example, the NW may send an RRCReconfiguration message to configure or reconfigure, for example, CSI-MeasConfig related configurations. In some examples, the configuration information 211 comprises a measurement configuration, wherein the measurement configuration itself comprises:
[0128] • at least one configuration of resources for the RSs to be measured (for example Set A and Set B NZP-CSI-ResourceConfigs along with associated IDs for the same, where Set A comprises resources to be used as output of the AI / ML model, and Set B comprises resources to be used as input to the AI / ML model)
[0129] • at least one reporting configuration (which may be referred to as, for example, CSI-ReportConfig or CSI-ReportingConfig).
[0130] In some examples, the at least one configuration 212 comprises at least one reporting configuration (not least for example CSI-ReportConfig). The at least one reporting configuration may be associated with / refer to at least one set of resources for RS.
[0131] In block 202, the UE determines whether the received at least one configuration meets at least one condition 221. In the scenario illustrated in FIG. 2, the UE determines that the received at least one configuration meets at least one condition (by contrast, in the scenario illustrated in FIG. 9, in block 902 the UE determines that the received at least one configuration does not meet at least one condition).
[0132] In some examples, the at least one condition 221 is based at least in part on at least one of the following:
[0133] a status of the UE, e.g. a current internal status or state of the UE, or a current status or state of a component or resource of the UE (not least forexample such as: CPU usage (e.g. of usage of CSI processing unit(s)), availability of active CSI ports, a number of occupied CSI processing units, UE’s available memory / buffer / storage space, UE’s power consumption / energy level, and CSI processing unit(s) dedicated for AI / ML purposes);
[0134] a load on the UE (not least for example such as: the UE’s current: processing load, buffer / memory availability, power consumption, port usage);
[0135] a utilization status of at least one resource of the UE (not least for example such as the UE’s: CPU usage, availability of active CSI ports, a number of occupied CSI processing units, available memory / buffer / storage space, power consumption / energy level);
[0136] an availability of at least one resource of the UE; or
[0137] an ability of the UE to confirm to one or more requirements defined in the at least one configuration.
[0138] In some example, the determining of block 202 comprises determining an applicability of the at least one configuration, wherein determining whether or not the at least one configuration is applicable for the UE may be based, for not least for example on whether the UE’s current: status, load, resource utilization (such resources corresponding to, e.g. CPU usage, availability of active CSI ports, a number of occupied CSI processing units, availability of CSI processing unit(s) dedicated for AI / ML purposes, available memory / buffer / storage space, power consumption / energy level) crosses a threshold level / value (which may be a predefined or configurable threshold level or value).
[0139] In block 203, the UE transmits, to the network, first information 231 which comprises at least one indication 232 that the at least one received configuration 212 has been determined to meet the at least one condition.
[0140] In this regard, as will be discussed in further detail below with regards to step 7 of FIG. 3, in some examples, the first information 231 is an RRC Reconfiguration Complete message, not least for example an RRCReconfigurationComplete message, that comprises the indication 232 that indicates which of the receivedconfigurations 212 the UE determined to be applicable (not least for example such as the indicator CSI-ReportConfig(l) = applicable, as illustrated in step 7 of FIG. 3).
[0141] In some examples, the configuration information 211, that was received in block 201, comprises a plurality of configurations 212. Moreover, in addition to determining which of the received configurations 212 meet the condition(s) (i.e. which are applicable), the UE may also determine which of the received configurations 212 do not meet the condition(s) (i.e. which are configurations not applicable). Based at least in part on determining that one or more of the received plurality of configurations do not meet the condition(s), the UE may include, in the first information 231 transmitted in block 203, one or more indications that the one or more configurations do not meet the condition(s) (not least for example such as the indicator CSI-ReportConfig(2) = inapplicable, as illustrated in step 7 of FIG. 3).
[0142] In some examples, the UE may include, in the first information 231 transmitted in block 203, one or more indications of at least one cause or reason as to why the one or more configurations do not meet the condition(s) (not least for example such as the indicator “inapplicable_cause” as illustrated in step 7 of FIG. 3). Such indicated causes of inapplicability may include, not least for example:
[0143] the UE’s CPUs not being available, the UE's dedicated CPU for AI / ML purposes not being available, the UE’s CSI-port not being available, the UE being in a low power state, the UE’s logging buffer (e.g. AS buffer) not being available, or a mismatch between the configuration and an OTT configuration.
[0144] In some examples, the first information further comprises an indication that the UE is ready to perform the data collection procedure in accordance with the at configuration(s) that have been determined to meet the at least one condition (such an indication may be referred to as a ready_for_DC indication). In this regard the UE may thereby indicate to the network that it is able to immediately / substantially instantaneously perform data collection using the applicable configuration(s). In other words, the UE is thereby indicating to the network that the UE is prepared for (i.e. has resources available for) and able to perform data collection via the applicable configurations straight away.In some examples, a data collection procedure is performed (which is discussed below with regards to block 204, wherein the performing of the data collection procedure is based at least in part on the transmitting of the indication that the UE is ready to perform the data collection procedure in accordance with the at least one configuration that has been determined to meet the at least one condition. In this regard, the data collection procedure is initiated / triggered / caused by / responsive to the transmission of a ready_for_DC indication. In some examples, there may be a ready_for_DC indication associated with / for each configuration 212 indicated in the first information 231. For instance, there may be a ready_for_DC indication associated with / for each reporting configuration determined to be applicable. In this regard, whilst there may be a set of configurations that are determined to be applicable, the UE may indicate that it is ready to perform the data collection procedure in accordance with a subset of the set of configurations.
[0145] In block 204, the UE performs the data collection procedure based at least in part on the transmitting of the first information. In this regard, the performing of the data collection procedure may be in response to (e.g. started / initiated / triggered) the transmitting of the first information (e.g. the RRCReconfigurationComplete message sent in block 202). Moreover, the data collection procedure is also performed based at least in part on the at least one configuration that has been determined to have met the at least one condition. In this regard, the performing of the data collection procedure may use / be accordance with the at least one configuration that has been determined to have met the at least one condition (i.e. the configuration(s) determined to be applicable).
[0146] In some examples (not shown in FIG. 2 but shown in FIG. 3 for example in step 9), the performing of the data collection procedure may comprise receiving the one or more pilot RSs (e.g. CSI-RSs) from the network. The NW can send MAC CE and / or DCI to UE, so that the UE can be ready to measure semi persistent and aperiodic CSI RSs (in this regard, aperiodic CSI can be activated by using MAC-CE and semi persistent can be is activated by DCI). The receiving of the RSs may be based at least in part on at least one set of resources that were included in the configuration information 211 and which are referred to in at least one configuration 212, that was also included in the configuration information 211 and which was determined to have met the condition- e.g. a reporting configuration 212 that was determined to be applicable (the reporting configuration 212 being associated with at least one measurement configuration).
[0147] In some examples (not shown in FIG. 2 but shown in FIG. 3 for example in step 10), the performing of the data collection procedure may comprise performing one or more measurements on the one or more RSs, wherein the measurements are performed based at least in part on at least one of:
[0148] the configuration information 211; or
[0149] the at least one reporting configuration 212.
[0150] In this regard, the data collected in the performance of the data collection procedure are such measurements / measurement results.
[0151] In some examples the configuration information 211 further comprises an indication of a type of reporting that the UE is to perform (i.e. a manner of reporting of the data collected via the data collection procedure).
[0152] The reporting type may be, for example one of at least two types:
[0153] • a “logged” reporting type - i.e. wherein the UE logs the collected data (i.e. storing the collected data for subsequent retrieval by, or subsequent transmission to, an entity such as an AI / ML model training entity or an intermediate entity for collecting and aggregating collected data / training data for passing on to a training entity) - not least for instance such as via the indicator “reporting_type=logged” as illustrated in step 5 of each of FIGs. 3 to 6.
[0154] • a ’’real-time reporting” reporting type, i.e. wherein instead of logging / storing the collected data it is immediately reported, in real time, to an entity such as an AI / ML model training entity or an intermediate entity for collating collected data / training data for passing on to a training entity) - not least for instance such as via the indicator “reporting_type=real-time” as illustrated in step 5 of FIG. 7).
[0155] In some example, based at least in part on receiving (e.g. in the configuration information 211) an indication of a first type of reporting (for instance, in response to receiving an indication of reporting_type=logged), the UE logs the data that it collectsvia the data collection procedure. In this regard, the UE may log / store the collected data in the UE’s Access Stratum, AS, buffer. Such logging / storing of the collected data may be triggered / initiated / caused by the receipt of the indication that the reporting type is to be logged-based reporting. The collected data may be logged / stored for: subsequent retrieval by the network, subsequent transmission to a remote device [e.g. for the collected data to be used as training data for training a model, not least such as an AI / ML model for beam management], or even for use by the UE itself to train its own local model.
[0156] In some examples, the logged / stored data, which has been collected via the data collection procedure [such data collection procedure having been performed based on / in accordance with the data collection configuration(s) that have been determined, in block 202) to meet the condition(s)] is transmitted to the network. In this regard, the collected data is logged / stored for subsequent retrieval by the network. Such a logging of data for subsequent retrieval / transmission, is to be contrasted to a second type of reporting wherein the collected data is reported / transmitted to the network in real-time, i.e. i.e. it is reported substantively instantaneously or substantively at the same time as the data is being collected.
[0157] In some example, based at least in part on receiving (e.g. in the configuration information 211) an indication of a second type of reporting (for instance, in response to receiving an indication of reporting_type=real-time), the UE transmits the data collected via the data collection procedure to the network. In this regard, such transmission of the collected data may be triggered / initiated / caused by the receipt of the indication that the reporting type is to be real-time based reporting.
[0158] Such transmission of the collected data may involve the establishment of a data connection between the UE and the network (namely an establishment of a data connection between the UE and an entity to which the UE is to send the collected data - such an entity may be a CN or OAM). In this regard, in some example, based at least in part on receiving (e.g. in the configuration information 211) an indication of the second type of reporting (for instance, in response to receiving an indication of reporting_type=real-time), the UE transmits a request to establish a data connection between the UE and the network. For example, the can UE transmit, to the gNB, arequest to establish a data connection between the UE and a CN or OAM of the network, so that the UE can then transmit / send the collected data to the CN or OAM. In this regard, such transmission of the connection request may be triggered / initiated / caused by the receipt of the indication that the reporting type is to be real-time based reporting.
[0159] In some examples (not shown in FIG. 2 but shown in FIG. 3 for example in step 11), after block 203’s transmission of the first information, the UE continues to monitor whether the at least one configuration still meets the at least one condition (i.e. whether the at least one configuration still meets is still applicable). In this regard, the UE performs, after block 203’s transmission (e.g. a predetermined period of time after the transmission), another determination as to whether the at least one configuration still meets the at least one condition. Based at least in part on determining that the at least one configuration does not meet / no longer meets the at least one condition; the UE may transmit, to the network, second information comprising at least one indication that the at least one configuration does not meet the at least one condition. The second information may be a UE Assistance Information, UAI, message indicating that the configuration is no longer applicable but is now inapplicable (not least for instance such as via the sending of a UAI comprising the indicator “CSI-ReportConfig(1) inapplicable” as illustrated in step 12 of FIG.3).
[0160] In some examples, this further determining is performed whilst the UE is performing the data collection procedure. In which case, the UE suspends the data collection procedure, wherein the suspension is based at least in part on (e.g. responsive to, initiated by, or triggered by) determining that the at least one configuration no longer meets the at least one condition.
[0161] In some examples, the second information further comprises at least one of:
[0162] information indicative of at least one cause of the at least one configuration not meeting the at least one condition (not least for example such as the indicator “inapplicable_cause of UAI” illustrated in step 12 of FIG.3);
[0163] at least one indication that the UE has logged data that has been collected via the data collection procedure using the at least one configuration (i.e. the atleast one configuration which has transitioned from being applicable to being inapplicable); or
[0164] at least one indication of an amount of logged data that has been collected via the data collection procedure using the at least one configuration (not least for example such as the indicator “logged_data_size = Xbytes of UAI” illustrated in step 12 of FIG.3).
[0165] In some examples, the UE’s continual monitoring / re-determining (i.e. after block 202’s initial determining, for instance within a specified amount of time after block 202’s transmitting of the first information or after expiry of a specified amount of time from transmitting of the first information) of the applicability of configurations 212 received in block 201 may reveal that one or more configurations which were initially determined (in block 202) as being inapplicable, upon re-determination of their applicability are now deem applicable. In such a scenario, based at least in part on determining, after transmitting the first information, that one or more configurations have transitioned from being inapplicable to being applicable (i.e. they now meet the at least one condition), the UE may transmit, to the network, third information comprising one or more indications that the one or more configurations have been (re-)determined to meet the condition(s) / to now be applicable as well as ready for data collection (not least for instance such as the indicator “CSI-ReportConfig(2) applicable” as illustrated in step 12 of FIG.4).
[0166] The third information may further comprise one or more indications that the UE is ready to perform the data collection procedure in accordance with the one or more of the configurations that have now been (re-)determined to meet the condition(s) / to now be applicable as well as ready for data collection (not least for instance such as the indicator “ready_for_DC” as illustrated in step 12 of FIG.4). In this regard the UE may thereby indicate to the network that it is able to immediately / substantially instantaneously perform data collection using the newly / now applicable configuration(s) (or a subset thereof). In other words, the UE is thereby indicating to the network that the UE is prepared for (i.e. has resources available for) and able to perform data collection via the newly / now applicable configurations straight away.In some examples, a plurality of configurations for configuring the UE to perform a data collection procedure may be received in block 201 and a set of configurations of the received plurality of configurations are determined to meet the condition(s) / be applicable. In such a scenario, the first information, sent by the UE in block 203, may further comprise an indication that the UE is ready to perform the data collection procedure in accordance with a subset of the set of configurations. The data collection procedure may then be performed, in block 204, based at least in part on the subset of the set of configurations. The UE may then perform one or more further determinations of whether the subset of configurations meets the condition(s), i.e. to monitor and (re-) determine the applicability of the subset of configurations. Based at least in part on determining that the subset of configurations does not meet the condition(s) / is now inapplicable, the UE may switch:
[0167] from performing the data collection procedure based at least in part on the subset of configurations that now does not meet / no longer meets the at least one condition,
[0168] to performing the data collection procedure based at least in part on at least one of the remaining configurations of the set of configurations that do still meet the at least one condition.
[0169] In some examples, the UE receives (e.g. prior to block 201), from a device (e.g. a CN, an OAM, or an OTT server), whilst the UE is in an idle connection state, a request to perform the data collection procedure. The then UE transmits, to the network, a request to transition to a connected state, wherein the transmitting is based at least in part on receiving the request, and wherein the request to transition to the connected state comprises at least one indication that the request to transition to the connected state is for the purpose of performing the data collection procedure. Such an indication may correspond to the indicator “setup-cause - Data Collection” as illustrated in step 2 of each of FIGs 3 to 7). This indication can be for example for a generic data collection for UE side models, or for a specific data collection for UE side models associated with a particular use case. Such an indicator may be provided in an establishmentcause message in SRB0. In this regard, a mechanism is thereby provided for enabling the NW to identify that the UE’s connection request is explicitly for data collection, e.g. UE side data collection. The configuration information 211, received in block 201, may be received from the network based atleast in part on the transmitted request. In this regard the configuration information 211 may be sent to the UE at least in part in response to the UE’s request to initiate the data collection procedure.
[0170] Alternatively, in some examples (such as is discussed in further detail below and illustrated with respect to FIG. 8), the UE may already be in a connected state at a time of receipt, from the device, of the request to perform the data collection procedure. In such a scenario, the UE may transmit, to the network, a request to initiate the data collection procedure, wherein the transmitting is based at least in part on receiving the request. The configuration information 211, received in block 201, may be received from the network based at least in part on the transmitted request. In this regard the configuration information 211 may be sent to the UE at least in part in response to the UE’s request to initiate the data collection procedure.
[0171] In examples of the disclosure, when the NW sends a list of data collection configurations to a UE (i.e. as per block 201 of FIG. 2), the UE can determine which data collection configurations are applicable and which are notapplicable / inapplicable. The UE can also consider whether it needs to do data collection on one or multiple configurations. Furthermore, the UE can determine whether there are any changes of data collection configurations from being applicable to being in-applicable and vice-versa. Based on this, the following different scenarios can be considered:
[0172] i) scenario 1 - multiple data collection configurations are sent to the UE, but only one is determined to be applicable
[0173] ii) scenario 2 - data collection is ongoing on a preferred data collection configuration, but another in-applicable data collection configuration becomes applicable
[0174] iii) scenario 3 - multiple data collection configurations are sent to the UE, wherein all of them are determined to be applicable, and wherein the UE indicates its preferred data collection configuration
[0175] iv) scenario 4 - multiple data collection configurations are sent to the UE and all are determined to be in-applicable
[0176] v) scenario 5 - wherein real time reporting is performed - multiple data collection configurations are sent to the UE, each with an indication for the UE to performreal time reporting, and wherein only one data collection configuration is determined to be applicable.
[0177] It is also to be appreciated that examples of the disclosure can be applied to combinations and variations of the above scenarios. Not least for instance, wherein multiple data collection configurations are sent to the UE - some of which are determined to be applicable and some of which are determined to be inapplicable -data collection is performed using the applicable data collection configurations but subsequently the applicable data collection configurations become inapplicable whereas the inapplicable data collection configurations become applicable. Moreover, each of the scenarios could involve logged reporting or Realtime reporting.
[0178] FIG. 3 illustrates an example of a signaling diagram showing signaling (between a UE 110 and a network 100 - the network comprising as least one gNB 120 and at least one CN / OAM 130 - and an OTT server 340) for supporting procedure 300.
[0179] The example illustrated in FIG. 3 relates to scenario 1, namely wherein multiple configurations are sent to the UE (in this example there are two configurations: first and second CSI reporting configurations CSI-reportingConfig(l) and CSI-reportingConfig(2)), however only one configuration is determined to be applicable. It is to be appreciated that a reference to CSI-reportingConfig(N) corresponds to an NthCSI report configuration where N = 1, 2, ... up to a maximum number of received CSI report configurations.
[0180] In step 1, the UE, whilst in an RRC IDLE state, receives data collection request. The request may be received directly from an OTT server 340 (as shown in FIG. 3) or it may be received from the CN (not shown).
[0181] In step 2, responsive to receipt of the request in step 2, the UE sends an RRCSetupRequest message to the gNB to request establishment of an RRC connection to the network. In this regard an RRC connection establishment procedure may be initiated such as per the RRC connection establishment procedure defined in section 5.3.3.3 in TS 38.331 e.g. version 18.4.0). The RRCSetupRequest message comprises an indication of the cause / reason for requesting establishment of theconnection. In this regard, an establishmentcause message in SRB0 may comprise an indication that the establishment cause is due to a data collection request.
[0182] (section 5.3.3.3 in TS 38.331)
[0183] In step 3, based on the UE’s RRCSetupRequest message, the gNB decides whether to accept the request to establish an RRC connection or whether to queue the UE (e.g. so as to enable the gNB to handle any temporary load peak). The control can be limited via waitTime information in an RRCReject message.
[0184] In step 4, if UE receives an RRCSetup message from the gNB, then UE capability information can be exchanged between the UE and the gNB, wherein the UE can indicate its data collection capability / ies and logging capability / ies.
[0185] In step 5, the NW provides data collection configurations to the UE. This step may be considered as an example of block 201 of FIG. 2.
[0186] In the example illustrated in FIG. 3, the data collection configurations comprise first and second CSI reporting configurations (CSI-reportingConfig(l) and CSI-reportingConfig(2)), each reporting configuration being associated with a measurement configuration and / or resources for the CSI-RSs to be measured (e.g. Layer 1, L1 measurements of CSI-RSs - it being appreciated that the data that is to be collected may be based at least in part upon L1 measurements of CSI-RSs). The data collection configurations can additionally comprise logging and reporting configurations. The CSI reporting configuration can convey the measurement configuration for the data collection and the UE may not need to transmit any L1 reporting and may instead log the measurements.
[0187] The NW may provide a full configuration or a set of parameters, for example, in a CSI-ReportConfig. The NW may provide one configuration, e.g. Set A and Set B NZP-CSI-ResourseConfig(s), where set B is a subset of set A. Alternatively, in another configuration, set B may be different from set A. The NW can also indicate to the UE that the measurements can be logged (e.g. via indication “reporting_type=logged”). This enables the gNB to later retrieve collected data (e.g. measurements) via different means depending on what transport means are to be used. The transport means isthe data transfer protocol. In some examples, this can be retrieved via a UE Information Procedure. In other examples, a PDU session is established between the UE and the CN for data transfer. In yet other examples, the UE can send the data to the OTT directly.
[0188] In step 6, the UE determines which of the data collection configurations are applicable and which are inapplicable. Such a determination of applicability may be based on: CPU usage, availability of dedicated CPU(s) for data collection, availability of active CSI ports, the UE’s internal state (like memory and power consumption etc.). This step may be considered as an example of block 202 of FIG. 2.
[0189] In step 7, the UE sends a response to the gNB with an RRCReconfigurationComplete message that may include one or more of:
[0190] a list / indication of which data collection configurations are applicable (i.e. which data collection configurations, of the plurality of data collection configurations received in step 5, are applicable),
[0191] a list / indication of which of the applicable data collection configurations are ready for data collection,
[0192] a list / indication of which of the data collection configurations are inapplicable, a list / indication of a cause of the inapplicability of the inapplicable data collection configurations.
[0193] This step may be considered as an example of block 203 of FIG. 2.
[0194] In step 8, the UE may start data collection if the data collection configuration(s) are applicable and a report type is periodic. This step may be considered as an example of block 204 of FIG. 2.
[0195] In step 9, for periodic CSI-RSs, UE will receive a pilot CSI-RS to measure. Whereas, for semi-persistent, SP, CSI-RSs and aperiodic CSI-RSs, the NW can send one or more additional Medium Access Control Control Elements, MAC CEs, to activate resources.
[0196] In step 10, the UE measures the CSI-RSs and estimates a quantity to log. In this regard, the US may log the measurement data (e.g. CSI-RS measurements; estimatesof Reference Signal Received Power, RSRP; CSI-RS Resource Indicator, CRI; or L1 RSRP) in the UE’s AS buffer.
[0197] In steps 11 and 12, the UE actively monitors the activated CSI report configurations (i.e. the CSI report configurations being used for the data collection and measurement of step 10) to determine whether an activated CSI report configuration becomes inapplicable. In the scenario of FIG. 3, CSI-reportingConfig(l) was initially, in step 6, determined to be applicable, but then later on, in step 11 it is determined to be inapplicable. Responsive to such a determination, the UE suspends the data collection and sends a UAI containing an indication of the (now) inapplicable CSI report configuration. The UAI may also indicate at least one of:
[0198] a list / indication of which configurations are inapplicable,
[0199] a list / indication of a cause of the inapplicability of the inapplicable configurations.
[0200] that data is available for retrieval (e.g. data that was collection using the formerly applicable configuration);
[0201] an indication of an amount of data or data size within the buffer.
[0202] The NW can release or deconfigure the data collection configuration. The NW can also retrieve the data (i.e. the data that the UE had collected prior to suspending data collection). If the configuration is not released, then UE may continue the data collection until the UE indicates / signals, to the NW, an explicit stop; or until the UE is explicitly stopped by the NW (e.g. via appropriate signaling to indicate the UE is to stop data collection).
[0203] In step 13, if a Control Plane, CP, tunnel is enabled, the NW can retrieve the data and forward it to a training entity (which may be any entity suitable for training an AI / ML model, e.g. an OTT server or CN; in some examples the UE itself may be the training entity, i.e. to train its own UE side AI / ML BM model for beam management measurements / predictions). Alternatively, if a User Plane, UP, tunnel is required, the UE can send a request for establishing a PDU session. Upon successfully establishing a PDU session with the CN, the UE can send the data to the CN, which itself can then forward on to a training entity. UE can also forward the logged data to OTT without using a 5GC transport mechanism.FIG. 4 illustrates an example of a signaling diagram showing signaling (between a UE 110 and a network 100 - the network comprising as least one gNB 120 and at least one CN / OAM 130 - and an OTT server 340) for supporting procedure 400. The signaling and procedure of FIG. 4 has many similarities to that of FIG. 3. It is to be appreciated that many of the details additional features described above in relation to FIG. 3 may be equally applicable to FIG. 4 mutatis mutandis.
[0204] FIG. 4 relates to scenario 2, namely wherein data collection is ongoing on an applicable / preferred configuration, however, another configuration - that was previously in-applicable - becomes applicable.
[0205] Steps 1-11 are similar to steps 1-11 of FIG. 3. However, in step 11, the UE also monitors the in-activated CSI report configurations (i.e. the CSI report configurations that were determined, in step 6, to be inapplicable) to determine whether the inapplicable CSI report configurations become applicable. In step 6, CSI-reportingConfig(2) was initially determined to be inapplicable, but then, in the scenario of 2, it is determined to be applicable in step 11.
[0206] Accordingly in step 11, the UE determines that the previously applicable and currently activated CSI report configuration (i.e. CSI-reportingConfig(l)) has become inapplicable; and that the previously inapplicable configuration (i.e. CSI-reportingConfig(2)) has become applicable and ready for data collection.
[0207] In step 12, responsive to such a determination, the UE also includes, in the UAI, an indication of at least one of:
[0208] a list / indication of which data collection configurations are (now determined to be) applicable, or
[0209] a list / indication of which of the applicable data collection configurations are ready for data collection.
[0210] In this regard, the UE sends UAI to the gNB, wherein the UAI contains indications that:CSI-reportingConfig(1 )) has become inapplicable along with a cause of the inapplicability;
[0211] logged data is available for retrieval (e.g. data that was collection using CSI- reportingConfig(l));
[0212] an indication of an amount of logged data or logged data size within the buffer; CSI-reportingConfig(2)) has become applicable; and
[0213] CSI-reportingConfig(2) is ready for data collection.
[0214] In step 13, responsive to the UAI of step 12, the NW can retrieve the logged data of the first CSI report configuration and either deactivate or release the first CSI report configuration. The NW may then activate the newly applicable report configuration (i.e. CSI-reportingConfig(2)) and start transmitting pilot CSI-RSs using the CSI resources associated with CSI-reportingConfig(2) (which may have been previously provided to the UE in step 1).
[0215] FIG. 5 illustrates an example of a signaling diagram showing signaling (between a UE 110 and a network 100 - the network comprising as least one gNB 120 and at least one CN / OAM 130 - and an OTT server 340) for supporting procedure 500. The signaling and procedure of FIG. 5 has many similarities to that of FIG. 3. It is to be appreciated that many of the details additional features described above in relation to FIG. 3 may be equally applicable to FIG. 5 mutatis mutandis.
[0216] FIG. 5 relates to scenario 3, namely wherein multiple configurations (in this instance two configurations: first and second CSI reporting configurations CSI-reportingConfig(l) and CSI-reportingConfig(2)) are sent to the UE and all of them are applicable and the UE indicates a preferred applicable configuration.
[0217] Steps 1-6 are similar to steps 1-6 of FIG. 3. However, in step 6, the UE determines that all (i.e. both in this example) of the CSI reporting configurations received in step 5 are applicable.
[0218] In step 7, the UE indicates to the which of the multiple configurations are applicable, and also which of the multiple configurations UE is ready to collect data for. In the example scenario shown in FIG. 5, the UE indicates:that CSI-reportingConfig(l) and CSI-reportingConfig(2) are both applicable; and also
[0219] that CSI-reportingConfig(l) and CSI-reportingConfig(2) are both ready for data collection.
[0220] However, it is to be appreciated that in other scenarios, whilst both are applicable, the UE may have a preference that only one of them be activated. In which case, the UE could indicate that both CSI-reportingConfig(l) and CSI-reportingConfig(2) are applicable; but also indicate that only one of CSI-reportingConfig(l) and CSI-reportingConfig(2) is ready for data collection. In other words, the UE can select a preferred CSI reporting configuration.
[0221] In some examples, the UE can indicate a sorted list of preferred applicable configurations. In this regard, the UE may indicate / set / toggle ready_for_dc only for those configurations on which the UE will start the data collection. However, later if a previously applicable configuration becomes in-applicable and UE indicates the inapplicability with cause to the gNB, the UE can switch to the next applicable configuration in the list and continue measuring and logging the data. It is to be appreciated that such UE behavior may also be applicable to the other examples and scenarios discussed in the present disclosure.
[0222] In step 8, the UE starts data collection for both (or multiple) applicable configurations (and optionally for both (or multiple) applicable configurations that were indicated by the UE in step 7 to be ready for data collection.
[0223] In step 9, the NW sends the pilot reference signals.
[0224] In step 10, the UE measures the CSI-RS and estimates a measurement quantity and logs the same in the UE’s buffer.
[0225] In step 11, the UE monitors whether the configurations transition from being applicable to in-applicable.In step 12, in the example scenario illustrated, the UE determines that configuration CSI-ReportConfig(l) becomes in-applicable.
[0226] In step 13, the UE can send updated information to the NW via UAI indicating that CSI-ReportConfig(l) is now in-applicable and also indicating the inapplicable cause as well as an amount of data available for CSI-ReportConfig(l).
[0227] In step 14, the UE continues data collection with the other applicable configuration(s) namely CSI-ReportConfig(2) in the example scenario illustrated.
[0228] In step 15, the NW can optionally retrieve the logged data, if available, and the NW can release the in-applicable CSI-ReportConfig(l).
[0229] FIG. 6 illustrates an example of a signaling diagram showing signaling (between a UE 110 and a network 100 - the network comprising as least one gNB 120 and at least one CN / OAM 130 - and an OTT server 340) for supporting procedure 600. The signaling and procedure of FIG. 6 has many similarities to that of FIG. 3. It is to be appreciated that many of the details additional features described above in relation to FIG. 3 may be equally applicable to FIG. 6 mutatis mutandis.
[0230] FIG. 6 relates to scenario 4, namely wherein multiple configurations (in this instance two configurations: first and second CSI reporting configurations CSI-reportingConfig(l) and CSI-reportingConfig(2)) are sent to the UE and none of them are applicable.
[0231] Steps 1-6 are similar to steps 1-6 of FIG. 3. However, in step 6, the UE determines that none of the CSI reporting configurations received in step 5 are applicable.
[0232] In step 7, the UE reports that none of the configurations are applicable, i.e. that all of the candidate configurations provided by the NW in step 5 are in-applicable.
[0233] In step 8, the UE waits for some predetermined time. This can be either be a preconfigured amount of time (e.g. based on a timer, initiated upon step 7, and whose duration is configured by the NW; it is may be based on a timer, such as aprohibit timer, whose duration may be up to UE / vendor implementation or defined in a technical specification / standard).
[0234] In step 9, the UE determines that one of the previously inapplicable configurations (e.g. CSI-reportingConfig(l)) becomes applicable before the predetermined time / timer expires.
[0235] In step 10, the UE sends / indicates to the NW, the applicability of the configuration that has now become applicable (i.e. CSI-reportingConfig(l)) and that this configuration is ready for data collection.
[0236] If the timer were to expire before the UE were to determine (in step 9) that any of the data collection configurations are applicable, UE can indicate to the NW that it is not interested in data collection.
[0237] Following on from step 10’s sending of the applicability indication, the UE then performs steps 11 to 17 - which are similar to steps 8 to 13 of FIG. 3.
[0238] FIG. 7 illustrates an example of a signaling diagram showing signaling (between a UE 110 and a network 100 - the network comprising as least one gNB 120 and at least one CN / OAM 130 - and an OTT server 340) for supporting procedure 700. The signaling and procedure of FIG. 7 has many similarities to that of FIG. 3. It is to be appreciated that many of the details additional features described above in relation to FIG. 3 may be equally applicable to FIG. 7 mutatis mutandis.
[0239] FIG. 7 relates to scenario 5, namely wherein real time reporting occurs (i.e. instead of logged reporting as per FIGs. 3 to 6). Also, in the particular scenario shown, multiple data collection configurations are sent to the UE but only one is determined to be applicable.
[0240] Steps 1-7 are similar to steps 1-7 of FIG. 3, except that the “reporting_type” indicated in step 5 is set to real time. In real time reporting, the UE does not log the measured data, instead it will report to the NW (or to an OTT server, e.g. if the training entity is tobe the OTT server) whenever it is collected. The reporting is done using UP tunnel as an example.
[0241] In step 8, after receiving the applicable list in step 7, the network establishes a PDU session. This could be either initiated by UE or it would be NW triggered.
[0242] In step 9, the UE starts data collection, and, in this regard, it activates the CSI-RS resources associated with the applicable data collection configuration(s).
[0243] In step 10, the UE receives pilot CS-RSs to measure.
[0244] In step 11, the UE measures the CSI-RS and estimates the measurement data.
[0245] In step 12, the data is reported using the PDU session.
[0246] In steps 13 and 14, following a determination that a current data collection configuration becomes inapplicable, the UE suspends the data collection and sends, via UAI, an indication of inapplicability along with an indication of the cause of the inapplicability. The UE can also indicate how much data is left.
[0247] In step 15, if no data is available and the data collection configuration is not applicable, the PDU session may be released.
[0248] In examples where reporting_type is set to real time, a PDU session may be sought to be initiated as soon as possible as the UE starts measuring the measurements, i.e. such that the measurements can be immediately reported. It is to be appreciated that real time reporting could equally well be used instead of the logged reporting of FIGs. 3 to 6 mutatis mutandis.
[0249] In examples where reporting_type set to logged, then PDU session establishment can happen at later point of time (i.e. once the data collection procedure has stopped). There could be separate triggers to initiate PDU session (e.g. a NW-initiated trigger / request for retrieval of the collected data, or a UE-initiated trigger / request to transmit the collected data).In the above examples of FIGs. 3 to 7, the UE is initially in an RRC IDLE state when the UE received a data collection request. In other examples, the UE may be in an RRC connected state when the data collection request is received.
[0250] FIG. 8 illustrates an example of a signaling diagram showing signaling (between a UE 110 and a network 100 - the network comprising as least one gNB 120 and at least one CN / OAM 130 - and an OTT server 340) for supporting procedure 800.
[0251] The example illustrated in FIG. 8 relates to a scenario wherein the UE is already in a connected state with the network when a data collection request is received by the UE (i.e. from the OTT as shown, or from a CN or an OAM - not shown).
[0252] In the example of FIG. 8, similar steps to those of FIGs. 3 to 7 can happen, except for steps 1-4 of FIGs. 3 to 7.
[0253] After a UE capability exchange and the UE indicating it is able to perform UE side data collection at Step 1, the NW can allow the UE to indicate when the UE will initiate data collection as well as indicate the UE’s selection of its preferred data collection configurations whenever the NW provides a candidate list of configurations (which the NW does in Step 2).
[0254] In step 3, the UE can receive a data collection request trigger from an OTT or from a CN directly (not shown in the Figure). It is to be noted that step 3 could alternatively happen before Step 2.
[0255] The UE can only trigger sending UAI at Step 4 after the NW indicates to the UE that the UE is allowed / permitted to do so. The NW may send such an indication via the OtherConfig received by the UE in Step 2.
[0256] Before Step 5, the UE can indicate the initiation of data collection via the UAI.
[0257] The rest of the steps could be similar to this of FIG. 3 and its steps 5-14. Also, other variations may apply, not least such as those of FIGs. 4 to 7. Also, the variations ofapplicabi lity / inapplicability of multiple configurations as discussed above can also apply to the example of FIG. 8.
[0258] FIG. 9 schematically illustrates an example of a procedure 900 and a signaling framework - between a UE 110 and a NW 100 (e.g. a network entity, NE, 102 such as a gNB 120 serving the UE) for supporting the procedure 900.
[0259] The signaling and procedure of FIG. 9 is somewhat similar to that of FIG. 2; however, whereas in block 202 of FIG. 2, the data collection configuration(s) were determined to meet the condition(s) - i.e. were deemed to be applicable - in block 902 of FIG. 9 the data collection configuration(s) are determined not to meet the condition(s), i.e. are deemed to be inapplicable. It is to be appreciated that the additional features, details and discussions of aspects of FIG. 3’s example can be applied to FIG. 9 mutatis mutandis.
[0260] In block 901, the UE receives, from the NW (e.g. from the gNB), configuration information 911. The configuration information 911 comprises at least one configuration 912 for configuring the UE to perform a data collection procedure. The at least one configuration (e.g. CSI reporting configuration) may be associated with / refer to at least one set of resources for RS (e.g. resources of CSI-RS to be measured and whose measurements the collected data is based at least in part on).
[0261] In block 902, the UE determines whether the received at least one configuration meets at least one condition 921. In the scenario illustrated in FIG. 9, the UE determines that the received at least one configuration does not meet the at least one condition (by contrast, in the scenario illustrated in FIG. 2, the UE determines that the received at least one configuration does meet at least one condition). The at least one condition 921 may be the same as the at least one condition 221 of FIG. 2.
[0262] In block 903, the UE transmits, to the network, first information 931 (e.g. a RRCReconfigurationComplete message) which comprises at least one indication 932 (e.g. an indication “CSI-ReportingConfig(1)=inapplicable”) that the at least one received configuration 912 has been determined not to meet the at least one condition.In block 904, the UE monitors for any changes in the configuration’s applicability. In this regard, the UE performs at least one further determination, after transmitting the first information, whether the at least one configuration meets the at least one condition. In this regard, the UE determines whether the at least one configuration, that was determined in block 902 as being inapplicable, is now applicable (e.g. not least due to a change in the UE’s status in the intervening time resulting that the condition is now able to be met). In the scenario illustrated in FIG. 9, the UE determines, in step 904, that the at least one configuration does (now) meet the at least one condition.
[0263] In block 905, the UE transmits, to the network, second information 951 which comprises at least one indication 952 that the at least one received configuration 912 (which was previously inapplicable) has been determined to meet the at least one condition (i.e. is now applicable). The transmitting is based at least in part on the determining that the at least one configuration (now) meets the at least one condition. With reference to step 10 of FIG. 6, the second information and its indication may, for example, be i.e. UAI comprising an indication “CSI-ReportConfig(l) applicable”.
[0264] The determining of block 905 can be performed (i.e. triggered / initiated) a predetermined amount of time after transmitting the first information in block 906.
[0265] In block 906, the UE performs the data collection procedure based at least in part on the transmitting of the second information. In this regard, the performing of the data collection procedure may be in response to (e.g. started / initiated / triggered) the transmitting of the second information in block 205. Moreover, the data collection procedure is also performed based at least in part on the at least one configuration that has been determined, in block 904, to have met the at least one condition. In this regard, the performing of the data collection procedure may use / be accordance with the at least one configuration that was initially deemed (in block 902) to be inapplicable, but which is now deemed (in block 904) to applicable.It is to be appreciated that the various of the additional details and features of aspects of FIG. 3’s example that are discussed above can be applied to FIG. 9 mutatis mutandis, not least such as those relating to:
[0266] indicating a cause of inapplicability / why the condition(s) were not met (“inapplicable_cause” of UAI of block 903);
[0267] logging or real time reporting types;
[0268] receive a request for data collection from OTT or CN or GAM whilst the UE is in an Idle state or a connected state;
[0269] indicating data collection as cause / reason for requesting connection to the network;
[0270] indicating “ready_for_dc” for applicable configurations
[0271] providing an ordered list of applicable configurations
[0272] There now follows examples of protocol messages and information elements, lEs, that may be adopted and used with examples of the disclosure.
[0273] Protocol Message Embodiments - Sample Abstract Syntax Notation One, ASN.1
[0274] UEDCApplicableDCConfigReport
[0275] The UEDCApplicableDCConfigReportUEDC message is used to indicate applicable functionality for an US Side data collection of AIML enabled use-case.
[0276] Signaling radio bearer: SRB 1
[0277] RLC-SAP: AM
[0278] Logical channel: DCCH
[0279] Direction: UE to Network
[0280] — ASN1 START
[0281] — TAG-APPLICABLEFUNCTIONALITYREPORTUEDC-START
[0282] ApplicableDCConfigReportUEDC ::= SEQUENCE { applicableDCConfigToAddModListUEDC-r19 SEQUENCE (SIZE (1..maxNrof ApplicableDCConfigToAddModListUEDC)) OF ApplicableFunctionalityUEDC-r19,applicableFunctionalityToRemoveListUEDC-r19 SEQUENCE (Size (1.. ApplicableDCConfigToAddModListUEDC)) OF
[0283] ApplicableDCConfigIdUEDC-r19,
[0284] nonCriticalExtension
[0285] SEQUENCE {} OPTIONAL
[0286] }
[0287] ApplicableDCConfigUEDC-r19 ::= SEQUENCE {
[0288] applicableFunctionalityId CSI-ReportConfigID-r19, readyForDC BOOLEAN, applicability ENUMERATED { applicable, inapplicable },
[0289] inapplicabilityCause ENUMERATED
[0290] { CPUs_not_available, CSI-port_not_available, low_power_state, logging-buffer-not-available, mismatch_with_OTT_config, spare1, spare2 } OPTIONAL
[0291] }
[0292] RRCSetupRequest message
[0293] — ASN1 START
[0294] — TAG-RRCSETUPREQUEST-START
[0295] RRCSetupRequest:: = SEQUENCE { rrcSetupRe uest RRCSetupRequest- IE s }
[0296] RRCSetupRequest-IEs:: = SEQUENCE {
[0297] ue-Identity InitialUE- Identity, establishmentCause EstablishmentCause,spare BIT STRING ( SIZE ( 1 ) ) }
[0298] InitialUE-Identity:: = CHOICE {
[0299] ng-5G-S-TMSI-Partl BIT STRING ( SIZE ( 39 ) ),
[0300] randomValue BIT STRING (SIZE (39)) }
[0301] EstablishmentCause ::= ENUMERATED {
[0302] emergency, highPriorityAccess, mt-Access, mo-Signalling,
[0303] mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess, UE-AIML-DC, spare5, spare4, spare3, spare2, spare1}
[0304] — TAG-RRCSETUPREQUEST-STOP
[0305] — ASN1STOP
[0306] Advantageously, with examples of the present disclosure (i.e. such as those discussed above with respect to FIGs 2 to 9), the following features may be employed to enable continuous and efficient UE side data collection configuration:
[0307] - when the UE receives a data collection request from an OTT / CN / OAM, then, if the UE is in RRC IDLE state, it can request RRC setup with data collection as establishment cause (e.g. not least as illustrated in FIGs 3 to 7 and 9); - the UE can be configured to perform logged reporting (e.g. as illustrated in FIGs 3 to 7 and 9) or configured to perform real time data reporting (e.g. not least as illustrated in FIG. 8);
[0308] - the UE can indicate its readiness for data collection (e.g. not least as illustrated in FIGs 3 to 6 and 8), in some examples an explicit indicator in this regard might not be necessary as an indication of an applicable configuration can implicitly (or explicitly) indicate readiness;
[0309] - UE can indicate in-applicability of a data collection configuration and also indicate a defined cause value (e.g. not least as illustrated in FIGs 3 to 8)- the UE can indicate a change of applicability of a data collection configuration from applicable to in-applicable and also indicate an amount of data that had been logged during activated data collection (e.g. as illustrated in FIGs 3 to 5 and 7)
[0310] - the UE can indicate a switch between multiple data collection configurations while one becomes in-applicable whist other configurations are applicable and ready for data collection (e.g. as illustrated in FIG. 4)
[0311] - the UE can determine applicability of data collection configurations based on any one or more of the following criteria / conditions:
[0312] an availability of a Channel State Information, CSI, processing unit; an availability of a dedicated processing unit (if supported);
[0313] a number of active CSI ports;
[0314] Access Stratum, AS, layer buffer size;
[0315] whether the UE is in a low power state;
[0316] a conformance with a received OTT configuration of data collection request, etc.
[0317] - if none of the data collection configurations are applicable, the UE can wait a predetermined time before stopping the data collection for UE side models (e.g. as illustrated in FIG. 6).
[0318] Various of the benefits provided by examples of the present disclosure (i.e. such as those discussed above with respect to FIGs 2 to 9) include:
[0319] 1. providing a mechanism for the UE to determine configuration applicability for data collection and report to network
[0320] 2. provide a configuration mechanism to enable multiple data collection configurations
[0321] 3. provide a mechanism to configure the UE to report logged data or report in real time using a PDU session
[0322] 4. provide a method to support an applicable configuration that is not ready for data collection not getting released by the NW
[0323] 5. enable the NW to decide admission control for data collection specific RRCSetupReq coming from the UE.
[0324] 6. Based on an inapplicable cause value, the NW can identify which potential configurations can be selected as candidate for future usageThe procedures and signaling diagrams of FIGs. 3 to 9 can be considered to illustrate a plurality of methods, in the sense that each procedure and signaling diagram can be considered to illustrate one or more actions, processes or performed by / at a plurality of actors / entities (e.g. the UE and the network / network entity). The procedures and signaling diagrams can therefore be considered to illustrate a plurality of individual methods performed by each respective individual actor / entity of the plurality of the actors / entities.
[0325] The blocks and steps illustrated in FIGs. 3 to 9 can represent actions in a method, functionality performed by an apparatus, and / or sections of instructions, program or code. The illustration of a particular order to the blocks does not necessarily imply that there is a required or preferred order for the blocks and the order and arrangement of the block may be varied. Furthermore, it may be possible for some blocks to be omitted.
[0326] It will be understood that each block and combinations of blocks illustrated in FIGs. 3 to 9 as well as the further functionality described herein, can be implemented by various means, such as hardware, firmware, and / or software including one or more computer program instructions. For example, one or more of the functions described above can be performed by a duly configured apparatus (such as an apparatus [as shown in FIG. 10] comprising means for performing the above-described functionality). One or more of the functions / functionalities described above can be embodied by a duly configured computer program (such as a computer program [as shown in FIG. 11] comprising computer program instructions which embody the functions / functionality described above and which can be stored by a memory storage device and performed by a processor).
[0327] As will be appreciated, any such computer program instructions can be loaded onto a computer or other programmable apparatus (i.e. hardware) to produce a machine, such that the instructions when performed on the programmable apparatus create means for implementing the functions / functionality specified in the blocks. These computer program instructions can also be stored in a computer-readable medium that can direct a programmable apparatus to function in a particular manner, suchthat the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the blocks. The computer program instructions can also be loaded onto a programmable apparatus to cause a series of operational actions to be performed on the programmable apparatus to produce a computer-implemented process such that the instructions which are performed on the programmable apparatus provide actions for implementing the functions / functionality specified in the blocks.
[0328] The above described component blocks and steps (e.g. of the signaling diagrams) are functional and the functions, along with the further functions / functionalities described above, can be performed by a single physical entity (such as an apparatus as is described with reference to FIG. 10, which may be embodied in / as a UE or NE, not least such as gNB or CN or OAM). The functions described can also be implemented by a computer program (such as is described with reference to FIG. 11, which may be executed by a processor of a UE, or NE).
[0329] FIG. 10 schematically illustrates a block diagram of an apparatus 10, namely a controller 11, for performing the methods, processes, procedures and signaling described in the present disclosure, not least as illustrated in FIGs. 3 to 9. In this regard the apparatus can perform the roles of an entity (such as: UE or NE, not least such as gNB or CN or OAM) in the illustrated and above-described methods.
[0330] The component blocks of FIG. 10’s apparatus are functional, and the functions described can be performed by a single physical entity, not least such as a UE or NE.
[0331] The apparatus comprises a controller 11, which could be provided within a device / entity, not least such as a UE or NE. The controller 11 can be embodied by a computing device, not least such as those mentioned above. In some, but not necessarily all examples, the apparatus can be embodied as a chip, chip set, circuitry or module, i.e. for use in any of the foregoing. As used here ‘module’ refers to a unit or apparatus that excludes certain parts / components that would be added by an end manufacturer or a user.Implementation of the controller 11 can be as controller circuitry. The controller 11 can be implemented in hardware alone, have certain aspects in software including firmware alone or can be a combination of hardware and software (including firmware).
[0332] The controller 11 can be implemented using instructions that enable hardware functionality, for example, by using executable instructions, program or code 14 in a general-purpose or special-purpose processor 12 that can be stored on a computer readable storage medium 13, for example memory, or disk etc., to be executed by such a processor 12.
[0333] The processor 12 is configured to read from and write to the memory 13. The processor 12 can also comprise an output interface via which data and / or commands are output by the processor 12 and an input interface via which data and / or commands are input to the processor 12. The apparatus can be coupled to or comprise one or more other components 15 (not least for example: a radio transceiver, sensors, input / output user interface elements and / or other modules / devices / components for inputting and outputting data / commands).
[0334] The memory 13 stores instructions such as a computer program or code 14 comprising such instructions (e.g. computer program instructions, or computer program code) that controls the operation of the apparatus 10 when loaded into the processor 12. The instructions, program or code 14 provide the logic and routines that enables the apparatus to perform the methods, processes and procedures described in the present disclosure and illustrated in FIGs. 3 to 9. The processor 12 by reading the memory 13 is able to load and execute the instructions, program or code 14.
[0335] The instructions may be comprised in a computer program, a non-transitory computer readable medium, a computer program product, a machine-readable medium. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e. tangible, not a signal) as opposed to a limitation on data storage persistency (e.g. RAM vs. ROM). In some but not necessarily all examples, thecomputer program instructions may be distributed over more than one computer program.
[0336] Although the memory 13 is illustrated as a single component / circuitry it can be implemented as one or more separate components / circuitry some or all of which can be integrated / removable and / or can provide permanent / semi-permanent / dynamic / cached storage.
[0337] Although the processor 12 is illustrated as a single component / circuitry it can be implemented as one or more separate components / circuitry some or all of which can be integrated / removable. The processor 12 can be a single core or multi-core processor.
[0338] The apparatus can include one or more components for effecting the methods, processes and procedures described in the present disclosure and illustrated in FIGs. 3 to 9. It is contemplated that the functions of these components can be combined in one or more components or performed by other components of equivalent functionality. The description of a function should additionally be considered to also disclose any means suitable for performing that function.
[0339] Where a structural feature has been described, it can be replaced by means for performing one or more of the functions of the structural feature whether that function or those functions are explicitly or implicitly described.
[0340] Although examples of the apparatus have been described above in terms of comprising various components, it should be understood that the components can be embodied as or otherwise controlled by a corresponding controller or circuitry such as one or more processing elements or processors of the apparatus. In this regard, each of the components described above can be one or more of any device, means or circuitry embodied in hardware, software or a combination of hardware and software that is configured to perform the corresponding functions of the respective components as described above.The apparatus can be, for example: a user equipment, network entity, base station or network node of a mobile cellular telecommunication system. The apparatus can be embodied by a computing device, not least such as those mentioned above.
[0341] However, in some examples, the apparatus can be embodied as a chip, chip set, circuitry or module, i.e. for use in any of the foregoing.
[0342] In one example, the apparatus is embodied on a client device, a UE, a mobile cellular telephone, a hand held portable electronic device, a mobile communication device, a wearable computing device or a personal digital assistant, that can additionally provide one or more audio / text / video communication functions (for example telecommunication, video-communication, and / or text transmission (Short Message Service (SMS) / Multimedia Message Service (MMS) / emailing) functions), interactive / non-interactive viewing functions (for example web-browsing, navigation, TV / program viewing functions), music recording / playing functions (for example Moving Picture Experts Group-1 Audio Layer 3 (MP3) or other format and / or (frequency modulation / amplitude modulation) radio broadcast recording / playing), downloading / sending of data functions, image capture function (for example using a (for example in-built) digital camera), and gaming functions, or any combination thereof.
[0343] In some examples (such as wherein the apparatus is provided within a UE 110), the apparatus 10 comprises:
[0344] at least one processor 12; and
[0345] at least one memory 13 storing instructions that, when executed by the at least one processor 12, cause the apparatus at least to:
[0346] receiving, from a network, configuration information comprising at least one configuration for configuring the UE to perform a data collection procedure; determining that the received at least one configuration meets at least one condition;
[0347] transmitting, to the network, first information, wherein the first information comprises at least one indication that the at least one received configuration has been determined to meet the at least one condition; and
[0348] performing the data collection procedure, wherein the performing of the data collection procedure is based at least in part on the transmitting of the firstinformation, and wherein the data collection procedure is performed based at least in part on the at least one configuration that has been determined to have met the at least one condition.
[0349] In some examples (such as wherein the apparatus is provided within a UE 110), the apparatus 10 comprises:
[0350] at least one processor 12; and
[0351] at least one memory 13 storing instructions that, when executed by the at least one processor 12, cause the apparatus at least to:
[0352] receiving, from a network, configuration information comprising at least one configuration for configuring the UE to perform a data collection procedure; determining that the received at least one configuration does not meet at least one condition;
[0353] transmitting, to the network, first information, wherein the first information comprises at least one indication that the at least one received configuration has been determined not to meet the at least one condition; determining, after transmitting the first information, that the at least one configuration meets the at least one condition;
[0354] transmitting, to the network, second information comprising at least one indication that the at least one configuration meets the at least one condition; wherein the transmitting is based at least in part on the determining that the at least one configuration meets the at least one condition; and
[0355] performing the data collection procedure, wherein the performing of the data collection procedure is based at least in part on the transmitting of the second information, and wherein the data collection procedure is performed based at least in part on the at least one configuration that has been determined to have met the at least one condition.
[0356] The above described examples find application as enabling components of: telecommunication systems; tracking systems, automotive systems; electronic systems including consumer electronic products; distributed computing systems; media systems for generating or rendering media content including audio, visual and audio visual content and mixed, mediated, virtual and / or augmented reality; personal systems including personal health systems or personal fitness systems; navigationsystems; user interfaces also known as human machine interfaces; networks including cellular, non-cellular, and optical networks; ad-hoc networks; the internet; the internet of things (IOT); Vehicle-to-everything (V2X), virtualized networks; and related software and services.
[0357] The apparatus can be provided in an electronic device, for example, a mobile terminal, according to an example of the present disclosure. It should be understood, however, that a mobile terminal is merely illustrative of an electronic device that would benefit from examples of implementations of the present disclosure and, therefore, should not be taken to limit the scope of the present disclosure to the same. While in certain implementation examples, the apparatus can be provided in a mobile terminal, other types of electronic devices, such as, but not limited to: mobile communication devices, hand portable electronic devices, wearable computing devices, portable digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices and other types of electronic systems, can readily employ examples of the present disclosure. Furthermore, devices can readily employ examples of the present disclosure regardless of their intent to provide mobility.
[0358] FIG. 11, illustrates instructions, program or code 14 which may be conveyed via a delivery mechanism 20. The delivery mechanism 20 can be any suitable delivery mechanism, for example, a machine readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a solid-state memory, a record medium or an article of manufacture that comprises or tangibly embodies the instructions, program or code 14. The delivery mechanism can be a signal configured to reliably transfer the instructions 14. An apparatus can receive, propagate or transmit the instructions 14 as a data signal.
[0359] In certain examples of the present disclosure, the instructions 14 cause an apparatus (e.g. UE 110) to perform at least the following or for causing performing at least the following:
[0360] receiving, from a network, configuration information comprising at least one configuration for configuring the UE to perform a data collection procedure;determining that the received at least one configuration meets at least one condition;
[0361] transmitting, to the network, first information, wherein the first information comprises at least one indication that the at least one received configuration has been determined to meet the at least one condition; and
[0362] performing the data collection procedure, wherein the performing of the data collection procedure is based at least in part on the transmitting of the first information, and wherein the data collection procedure is performed based at least in part on the at least one configuration that has been determined to have met the at least one condition.
[0363] In certain examples of the present disclosure, the instructions 14 cause an apparatus (e.g. UE 110) to perform at least the following or for causing performing at least the following:
[0364] receiving, from a network, configuration information comprising at least one configuration for configuring the UE to perform a data collection procedure; determining that the received at least one configuration does not meet at least one condition;
[0365] transmitting, to the network, first information, wherein the first information comprises at least one indication that the at least one received configuration has been determined not to meet the at least one condition; determining, after transmitting the first information, that the at least one configuration meets the at least one condition;
[0366] transmitting, to the network, second information comprising at least one indication that the at least one configuration meets the at least one condition; wherein the transmitting is based at least in part on the determining that the at least one configuration meets the at least one condition; and
[0367] performing the data collection procedure, wherein the performing of the data collection procedure is based at least in part on the transmitting of the second information, and wherein the data collection procedure is performed based at least in part on the at least one configuration that has been determined to have met the at least one condition.References to ‘instructions’ ‘computer program’, ‘computer-readable storage medium’, ‘computer program product’, ‘tangibly embodied computer program’ etc. or a ‘controller’, ‘computer’, ‘processor’ etc. should be understood to encompass not only computers having different architectures such as single / multi- processor architectures and sequential (Von Neumann) / parallel architectures but also specialized circuits such as field-programmable gate arrays (FPGA), application specific circuits (ASIC), signal processing devices and other processing circuitry including quantum processing circuitry. References to computer program, instructions, code etc. should be understood to encompass software for a programmable processor or firmware such as, for example, the programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device etc.
[0368] As used in this application, the term ‘circuitry’ may refer to one or more or all the following:
[0369] (a) hardware-only circuitry implementations (such as implementations in analog, digital and / or quantum circuitry) and
[0370] (b) combinations of hardware circuit(s) and software, such as (as applicable):
[0371] i. a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and
[0372] ii. any or all portions of hardware processor(s) (including digital and / or quantum processor(s)) with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, computing device or server, to perform various functions and
[0373] (c) any or all portions of hardware circuit(s), such as a microprocessor(s) and / or quantum processors, that requires software (for example, firmware) for operation, but the software may not be present when it is not needed for operation.
[0374] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to a particular claim element, a baseband integrated circuit orprocessor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.
[0375] Although various examples of the present disclosure have been described in the preceding paragraphs, it should be appreciated that modifications to the examples given can be made without departing from the scope of the invention as set out in the claims.
[0376] Various, but not necessarily all, examples of the present disclosure can take the form of a method, an apparatus, or a computer program. Accordingly, various, but not necessarily all, examples can be implemented in hardware, software or a combination of hardware and software.
[0377] Various, but not necessarily all, examples of the present disclosure are described using flowchart illustrations and schematic block diagrams. It will be understood that each block (of the flowchart illustrations and block diagrams), and combinations of blocks, can be implemented by computer program instructions of a computer program. These program instructions can be provided to one or more processor(s), processing circuitry or controller(s) such that the instructions which execute on the same create means for causing implementing the functions specified in the block or blocks, i.e. such that the method can be computer implemented. The computer program instructions can be executed by the processor(s) to cause a series of operational block / steps / actions to be performed by the processor(s) to produce a computer implemented process such that the instructions which execute on the processor(s) provide block / steps for implementing the functions specified in the block or blocks.
[0378] Accordingly, the blocks support: combinations of means for performing the specified functions; combinations of actions for performing the specified functions; and computer program instructions / algorithm for performing the specified functions. It will also be understood that each block, and combinations of blocks, can be implemented by special purpose hardware-based systems which perform the specified functions or actions, or combinations of special purpose hardware and computer program instructions.Various, but not necessarily all, examples of the present disclosure provide both a method and corresponding apparatus comprising various modules, means or circuitry that provide the functionality for performing / applying the actions of the method. The modules, means or circuitry can be implemented as hardware, or can be implemented as software or firmware to be performed by a computer processor. In the case of firmware or software, examples of the present disclosure can be provided as a computer program product including a computer readable storage structure embodying computer program instructions (i.e. the software or firmware) thereon for performing by the computer processor.
[0379] Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
[0380] Features described in the preceding description can be used in combinations other than the combinations explicitly described.
[0381] Although functions have been described with reference to certain features, those functions can be performable by other features whether described or not.
[0382] Although features have been described with reference to certain examples, those features can also be present in other examples whether described or not.
[0383] Accordingly, features described in relation to one example / aspect of the disclosure can include any or all of the features described in relation to another example / aspect of the disclosure, and vice versa, to the extent that they are not mutually inconsistent.
[0384] The term ‘comprise’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising Y indicates that X can comprise only one Y or can comprise more than one Y. If it is intended to use ‘comprise’ with an exclusive meaning, then it will be made clear in the context by referring to “comprising only one...” or by using “consisting”.
[0385] In this description, the wording ‘connect’ and ‘communication’ and their derivatives mean operationally connected / in communication. It should be appreciated that any number or combination of intervening components can exist (including no intervening components), i.e. so as to provide direct or indirect connection / communication. Any such intervening components can include hardware and / or software components.As used herein, the term "determine / determining" (and grammatical variants thereof) can include, not least: evaluating, calculating, computing, processing, deriving, measuring, investigating, identifying, looking up (for example, looking up in a table, a database or another data structure), ascertaining and the like. Also, "determining" can include receiving (for example, receiving information), retrieving / accessing (for example, retrieving / accessing data in a memory), obtaining and the like. Also, " determine / determining" can include resolving, selecting, choosing, establishing, inferring and the like.
[0386] As used herein, a description of an action should also be considered to disclose enabling, and / or causing, and / or controlling that action. For example, a description of transmitting information should also be considered to disclose enabling, and / or causing, and / or controlling transmitting information. Similarly, for example, a description of an apparatus transmitting information should also be considered to disclose at least one means or controller of the apparatus enabling, and / or causing, and / or controlling the apparatus to transmit the information.”
[0387] The term “means” as used in the description and in the claims may refer to one or more individual elements configured to perform the corresponding recited functionality or functionalities, or it may refer to several elements that perform such functionality or functionalities. Furthermore, several functionalities recited in the claims may be performed by the same individual means or the same combination of means. For example, performing such functionality or functionalities may be caused in an apparatus by a processor that executes instructions stored in a memory of the apparatus.
[0388] References to a parameter, or value of a parameter, should be understood to refer to “data indicative of’, “data defining” or “data representative of’ the relevant parameter / parameter value if not explicitly stated (unless the context demands otherwise). The data may be in any way indicative of the relevant parameter / parameter value and may be directly or indirectly indicative thereof.In this description, reference has been made to various examples. The description of features or functions in relation to an example indicates that those features or functions are present in that example. The use of the term ’example’ or ‘for example’, ‘can’ or ‘may’ in the text denotes, whether explicitly stated or not, that such features or functions are present in at least the described example, whether described as an example or not, and that they can be, but are not necessarily, present in some or all other examples. Thus ‘example’, ‘for example’, ‘can’ or ‘may’ refers to a particular instance in a class of examples. A property of the instance can be a property of only that instance or a property of the class or a property of a sub-class of the class that includes some but not all of the instances in the class.
[0389] In this description, references to “a / an / the” [feature, element, component, means...] are used with an inclusive not an exclusive meaning and are to be interpreted as “at least one” [feature, element, component, means...] unless explicitly stated otherwise. That is any reference to X comprising a / the Y indicates that X can comprise only one Y or can comprise more than one Y unless the context clearly indicates the contrary. If it is intended to use ‘a’ or ‘the’ with an exclusive meaning, then it will be made clear in the context. In some circumstances the use of ‘at least one’ or ‘one or more’ can be used to emphasize an inclusive meaning but the absence of these terms should not be taken to infer any exclusive meaning.
[0390] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0391] As used herein, the terms “the at least one” and “the one or more” mean “any one of the at least one” and “any one of the one or more”, respectively.
[0392] The presence of a feature (or combination of features) in a claim is a reference to that feature (or combination of features) itself and also to features that achieve substantially the same technical effect (equivalent features). The equivalent features include, for example, features that are variants and achieve substantially the same result in substantially the same way. The equivalent features include, for example,features that perform substantially the same function, in substantially the same way to achieve substantially the same result.
[0393] In this description, reference has been made to various examples using adjectives or adjectival phrases to describe characteristics of the examples. Such a description of a characteristic in relation to an example indicates that the characteristic is present in some examples exactly as described and is present in other examples substantially as described.
[0394] In the above description, the apparatus described can alternatively or in addition comprise an apparatus which in some other examples comprises a distributed system of apparatus, for example, a client / server apparatus system. In examples where an apparatus provided forms (or a method is implemented as) a distributed system, each apparatus forming a component and / or part of the system provides (or implements) one or more features which collectively implement an example of the present disclosure. In some examples, an apparatus is re-configured by an entity other than its initial manufacturer to implement an example of the present disclosure by being provided with additional software, for example by a user downloading such software, which when executed causes the apparatus to implement an example of the present disclosure (such implementation being either entirely by the apparatus or as part of a system of apparatus as mentioned hereinabove).
[0395] The above description describes some examples of the present disclosure however those of ordinary skill in the art will be aware of possible alternative structures and method features which offer equivalent functionality to the specific examples of such structures and features described herein above and which for the sake of brevity and clarity have been omitted from the above description. Nonetheless, the above description should be read as implicitly including reference to such alternative structures and method features which provide equivalent functionality unless such alternative structures or method features are explicitly excluded in the above description of the examples of the present disclosure.
[0396] Whilst endeavoring in the foregoing specification to draw attention to those features of examples of the present disclosure believed to be of particular importance itshould be understood that the applicant may seek protection via the claims in respect of any patentable feature or combination of features hereinbefore referred to and / or shown in the drawings whether or not particular emphasis has been placed thereon.
[0397] The examples of the present disclosure and the accompanying claims can be suitably combined in any manner apparent to one of ordinary skill in the art. Separate references to an “example”, “in some examples” and / or the like in the description do not necessarily refer to the same example and are also not mutually exclusive unless so stated and / or except as will be readily apparent to those skilled in the art from the description. For instance, a feature, structure, process, block, step, action, or the like described in one example may also be included in other examples but is not necessarily included.
[0398] Each and every claim is incorporated as further disclosure into the specification and the claims are embodiment(s) of the present disclosure. Further, while the claims herein are provided as comprising specific dependencies, it is contemplated that any claims can depend from any other claims and that to the extent that any alternative embodiments can result from combining, integrating, and / or omitting features of the various claims and / or changing dependencies of claims, any such alternative embodiments and their equivalents are also within the scope of the disclosure.
[0399] SUPPORTING PARAGRAPHS
[0400] There now follows different sets of numbered paragraphs: A1.1 and A1.2 as well as B1.1 to B1.4. The first paragraph in each set of paragraphs could form the basis for an independent claim. Features present in one set of paragraphs can be combined with features present in other sets of paragraphs mutatis mutandis.
[0401] A1.1
[0402] 1. A User Equipment, UE, (110) comprising means (10, 11) for:
[0403] receiving (901), from a network (100), configuration information (911) comprising at least one configuration (912) for configuring the UE to perform a data collection procedure;determining (902) that the received at least one configuration does not meet at least one condition (921);
[0404] transmitting (903), to the network, first information (931), wherein the first information comprises at least one indication (932) that the at least one received configuration has been determined not to meet the at least one condition;
[0405] determining (904), after transmitting the first information, that the at least one configuration meets the at least one condition; transmitting (905), to the network, second information (951) comprising at least one indication (952) that the at least one configuration meets the at least one condition; wherein the transmitting is based at least in part on the determining that the at least one configuration meets the at least one condition; and performing (906) the data collection procedure, wherein the performing of the data collection procedure is based at least in part on the transmitting of the second information, and wherein the data collection procedure is performed based at least in part on the at least one configuration that has been determined to have met the at least one condition.
[0406] 2. The UE of any previous paragraph, wherein the first information further comprises information indicative of at least one cause of the at least one configuration not meeting the at least one condition.
[0407] 3. The UE of any previous paragraph, wherein the determining that the at least one configuration meets the at least one condition is performed a predetermined amount of time after transmitting the first information.
[0408] 4. The UE of any previous paragraph, wherein the at least one configuration comprises at least one reporting configuration that refers to at least one set of resources for one or more reference signals; and wherein performing the data collection procedure comprises:receiving the one or more reference signals from the network, wherein the receiving is based at least in part on the at least one set of resources;
[0409] performing one or more measurements on the one or more reference signals, wherein the measurements are performed based at least in part on at least one of:
[0410] the configuration information; or
[0411] the at least one reporting configuration.
[0412] 5. The UE of any previous paragraph, wherein the configuration information further comprises at least one indication of at least one type of reporting that the UE is to perform.
[0413] 6. The UE of paragraph 5, wherein a first type of reporting is indicated in the configuration information, and
[0414] the UE further comprises means for:
[0415] logging data collected via the data collection procedure, wherein the logging is based at least in part on receiving the indication of the first type of reporting.
[0416] The UE of paragraph 6, wherein the UE further comprises means for:
[0417] transmitting the logged data to the network.
[0418] 7. The UE of paragraph 5, wherein a second type of reporting is indicated in the configuration information, and wherein the UE further comprises means for:
[0419] transmitting, to the network, data collected via the data collection procedure, wherein the transmitting is based at least in part on receiving, in the configuration information, the indication of the second type of reporting.
[0420] 8. The UE of paragraph 8, wherein the transmitting comprises:
[0421] establishing a data connection between the UE and the network, and wherein the establishing is based at least in part on receiving, in theconfiguration information, the indication of the second type of reporting.
[0422] 9. The UE of any previous paragraph, wherein the second information further comprises at least one indication that the UE is ready to perform the data collection procedure in accordance with the at least one configuration that has been determined to meet the at least one condition.
[0423] 10. The UE of paragraph 10, wherein the performing of the data collection procedure is based at least in part on the transmitting of the indication that the UE is ready to perform the data collection procedure in accordance with the at least one configuration that has been determined to meet the at least one condition and wherein the at least one of the plurality of configurations is associated with at least one measurement configuration.
[0424] 11. The UE of any previous paragraph, wherein the at least one condition is based at least in part on at least one of the following:
[0425] a status of the UE;
[0426] a load on the UE;
[0427] a utilization status of at least one resource of the UE;
[0428] an availability of at least one resource of the UE; or
[0429] an ability of the UE to confirm to one or more requirements defined in the at least one configuration.
[0430] 12. The UE of any previous paragraph, wherein the UE further comprises means for:
[0431] determining, after transmitting the second information, that the at least one configuration does not meet the at least one condition; and transmitting, to the network, third information comprising at least one indication that the at least one configuration does not meet the at least one condition; wherein the at least one indication is based at least in part on the determining that the at least one configuration does not meet the at least one condition.13. The UE of paragraph 13, wherein determining, after transmitting the second information, that the at least one configuration does not meet the at least one condition occurs whilst the UE is performing the data collection procedure, and wherein the UE further comprises means for:
[0432] suspending, based at least in part on determining that the at least one configuration no longer meets the at least one condition, the data collection procedure.
[0433] 14. The UE of paragraph 13 or 14, wherein the third information further comprises at least one of:
[0434] information indicative of at least one cause of the at least one configuration not meeting the at least one condition;
[0435] at least one indication that the UE has logged data that has been collected via the data collection procedure using the at least one configuration; or
[0436] at least one indication of an amount of logged data that has been collected via the data collection procedure using the at least one configuration.
[0437] 15. The UE of any previous paragraph, wherein the UE further comprises means for:
[0438] receiving, from a device, whilst the UE is in an idle connection state, a request to perform the data collection procedure; and transmitting, to the network, a request to transition to a connected state, wherein the transmitting is based at least in part on receiving the request, and wherein the request to transition to the connected state comprises at least one indication that the request to transition to the connected state is for the purpose of performing the data collection procedure.
[0439] 16. The UE of paragraphs 1 to 15, wherein the UE further comprises means for:
[0440] receiving, from a device, whilst the UE is in a connected state, a request to perform the data collection procedure;transmitting, to the network, a request to initiate the data collection procedure, wherein the transmitting is based at least in part on receiving the request; and
[0441] wherein the configuration information is received from the network based at least in part on the transmitted request.
[0442] 17. The UE of any previous paragraph, wherein:
[0443] the at least one configuration for configuring the UE to perform a data collection procedure comprises a plurality of configurations for configuring the UE to perform a data collection procedure;
[0444] the determining, after transmitting the first information, that the at least one configuration meets the at least one condition comprises determining, after transmitting the first information, that a set of configurations of the received plurality of configurations meets the at least one condition;
[0445] wherein the second information further comprises at least one indication that the UE is ready to perform the data collection procedure in accordance with a subset of the set of configurations;
[0446] wherein the data collection procedure is performed based at least in part on the subset of the set of configurations; and
[0447] wherein the UE further comprises means for:
[0448] determining that the subset of configurations does not meet the at least one condition; and
[0449] switching:
[0450] from performing the data collection procedure based at least in part on the subset of configurations that does not meet the at least one condition,
[0451] to performing the data collection procedure based at least in part on at least one of the remaining configurations of the set of configurations that meets the at least one condition, wherein the switching is based at least in part on determining that the subset of configurations does not meet the at least one condition.
[0452] A1.21. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform:
[0453] receiving, from a network, configuration information comprising at least one configuration for configuring the UE to perform a data collection procedure; determining that the received at least one configuration does not meet at least one condition;
[0454] transmitting, to the network, first information, wherein the first information comprises at least one indication that the at least one received configuration has been determined not to meet the at least one condition; determining, after transmitting the first information, that the at least one configuration meets the at least one condition;
[0455] transmitting, to the network, second information comprising at least one indication that the at least one configuration meets the at least one condition; wherein the transmitting is based at least in part on the determining that the at least one configuration meets the at least one condition; and
[0456] performing the data collection procedure, wherein the performing of the data collection procedure is based at least in part on the transmitting of the second information, and wherein the data collection procedure is performed based at least in part on the at least one configuration that has been determined to have met the at least one condition.
[0457] B1.1
[0458] 1. A method comprising:
[0459] receiving, from a network, configuration information comprising at least one configuration for configuring the UE to perform a data collection procedure;
[0460] determining that the received at least one configuration meets at least one condition;
[0461] transmitting, to the network, first information, wherein the first information comprises at least one indication that the at least one received configuration has been determined to meet the at least one condition; andperforming the data collection procedure, wherein the performing of the data collection procedure is based at least in part on the transmitting of the first information, and wherein the data collection procedure is performed based at least in part on the at least one configuration that has been determined to have met the at least one condition.
[0462] B1.2.1
[0463] 1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform the method of B1.1.
[0464] B1.2.2
[0465] 1. An apparatus comprising means for performing the method of B1.1.
[0466] B1.3.1
[0467] 1. A non-transitory computer readable medium, when executed by an apparatus, causes the apparatus to perform the method of B1.1.
[0468] B1.3.2
[0469] 1. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method of B1.1.
[0470] B1.4
[0471] 1. A module, circuitry, a chipset comprising processing circuitry, a device and / or a system configured to (or comprising means for) perform(ing) the method of B1.1.
[0472] I / we claim:
Claims
CLAIMS1. A User Equipment, UE, comprising:at least one processor; andat least one memory including computer program code, the at least one memory storing instructions that, when executed by the at least one processor, cause the UE to perform at least the following:receiving, from a network, configuration information comprising at least one configuration for configuring the UE to perform a data collection procedure; determining that the received at least one configuration does not meet at least one condition;transmitting, to the network, first information, wherein the first information comprises at least one indication that the at least one received configuration has been determined not to meet the at least one condition; determining, after transmitting the first information, that the at least one configuration meets the at least one condition;transmitting, to the network, second information comprising at least one indication that the at least one configuration meets the at least one condition; wherein the transmitting is based at least in part on the determining that the at least one configuration meets the at least one condition; andperforming the data collection procedure, wherein the performing of the data collection procedure is based at least in part on the transmitting of the second information, and wherein the data collection procedure is performed based at least in part on the at least one configuration that has been determined to have met the at least one condition.
2. The UE of any previous claim, wherein the first information further comprises information indicative of at least one cause of the at least one configuration not meeting the at least one condition.
3. The UE of any previous claim, wherein the determining that the at least one configuration meets the at least one condition is performed a pre-determined amount of time after transmitting the first information.
4. The UE of any previous claim, wherein the at least one configuration comprises at least one reporting configuration that refers to at least one set of resources for one or more reference signals; and wherein performing the data collection procedure comprises:receiving the one or more reference signals from the network, wherein the receiving is based at least in part on the at least one set of resources; performing one or more measurements on the one or more reference signals, wherein the measurements are performed based at least in part on at least one of:the configuration information; orthe at least one reporting configuration.
5. The UE of any previous claim, wherein the configuration information further comprises at least one indication of at least one type of reporting that the UE is to perform.
6. The UE of claim 5, wherein a first type of reporting is indicated in the configuration information, and wherein the at least one memory stores instructions that, when executed by the at least one processor, further cause the UE to perform:logging data collected via the data collection procedure, wherein the logging is based at least in part on receiving the indication of the first type of reporting.
7. The UE of claim 6, wherein the at least one memory stores instructions that, when executed by the at least one processor, further cause the UE to perform:transmitting the logged data to the network.
8. The UE of claim 5, wherein a second type of reporting is indicated in the configuration information, and wherein the at least one memory stores instructions that, when executed by the at least one processor, further cause the UE to perform:transmitting, to the network, data collected via the data collection procedure, wherein the transmitting is based at least in part on receiving, in the configuration information, the indication of the second type of reporting.
9. The UE of claim 8, wherein the transmitting comprises:establishing a data connection between the UE and the network, and wherein the establishing is based at least in part on receiving, in the configuration information, the indication of the second type of reporting.
10. The UE of any previous claim, wherein the second information further comprises at least one indication that the UE is ready to perform the data collection procedure in accordance with the at least one configuration that has been determined to meet the at least one condition.
11. The UE of claim 10, wherein the performing of the data collection procedure is based at least in part on the transmitting of the indication that the UE is ready to perform the data collection procedure in accordance with the at least one configuration that has been determined to meet the at least one condition and wherein the at least one of the plurality of configurations is associated with at least one measurement configuration.
12. The UE of any previous claim, wherein the at least one condition is based at least in part on at least one of the following:a status of the UE;a load on the UE;a utilization status of at least one resource of the UE;an availability of at least one resource of the UE; oran ability of the UE to confirm to one or more requirements defined in the at least one configuration.
13. The UE of any previous claim, wherein the at least one memory stores instructions that, when executed by the at least one processor, further cause the UE to perform:determining, after transmitting the second information, that the at least one configuration does not meet the at least one condition; andtransmitting, to the network, third information comprising at least one indication that the at least one configuration does not meet the at least one condition; wherein the at least one indication is based at least in part on thedetermining that the at least one configuration does not meet the at least one condition.
14. The UE of claim 13, wherein determining, after transmitting the second information, that the at least one configuration does not meet the at least one condition occurs whilst the UE is performing the data collection procedure, and wherein the at least one memory stores instructions that, when executed by the at least one processor, further cause the UE to perform:suspending, based at least in part on determining that the at least one configuration no longer meets the at least one condition, the data collection procedure.
15. The UE of claim 13 or 14, wherein the third information further comprises at least one of:information indicative of at least one cause of the at least one configuration not meeting the at least one condition;at least one indication that the UE has logged data that has been collected via the data collection procedure using the at least one configuration; or at least one indication of an amount of logged data that has been collected via the data collection procedure using the at least one configuration.
16. The UE of any previous claim, wherein the at least one memory stores instructions that, when executed by the at least one processor, further cause the UE to perform:receiving, from a device, whilst the UE is in an idle connection state, a request to perform the data collection procedure; andtransmitting, to the network, a request to transition to a connected state, wherein the transmitting is based at least in part on receiving the request, and wherein the request to transition to the connected state comprises at least one indication that the request to transition to the connected state is for the purpose of performing the data collection procedure.
17. The UE of claims 1 to 15, wherein the at least one memory stores instructions that, when executed by the at least one processor, further cause the UE to perform:receiving, from a device, whilst the UE is in a connected state, a request to perform the data collection procedure;transmitting, to the network, a request to initiate the data collection procedure, wherein the transmitting is based at least in part on receiving the request; and wherein the configuration information is received from the network based at least in part on the transmitted request.
18. The UE of any previous claim, wherein:the at least one configuration for configuring the UE to perform a data collection procedure comprises a plurality of configurations for configuring the UE to perform a data collection procedure;determining, after transmitting the first information, that the at least one configuration meets the at least one condition comprises determining, after transmitting the first information, that a set of configurations of the received plurality of configurations meets the at least one condition;wherein the second information further comprises at least one indication that the UE is ready to perform the data collection procedure in accordance with a subset of the set of configurations;wherein the data collection procedure is performed based at least in part on the subset of the set of configurations; andwherein the at least one memory stores instructions that, when executed by the at least one processor, further cause the UE to perform:determining that the subset of configurations does not meet the at least one condition; andswitching:from performing the data collection procedure based at least in part on the subset of configurations that does not meet the at least one condition, to performing the data collection procedure based at least in part on at least one of the remaining configurations of the set of configurations that meets the at least one condition, wherein the switching is based at least in part on determining that the subset of configurations does not meet the at least one condition.
