WO2025201385A1

WO2025201385A1 - Methods and apparatus of data collection across connection states in mobile communications

Info

Publication number: WO2025201385A1
Application number: PCT/CN2025/084974
Authority: WO
Inventors: Yao PENG; Hao Bi; Per Johan Mikael Johansson; Yuanyuan Zhang; Ta-Yuan LIU
Original assignee: MediaTek Singapore Pte Ltd
Current assignee: MediaTek Singapore Pte Ltd
Priority date: 2024-03-27
Filing date: 2025-03-26
Publication date: 2025-10-02
Anticipated expiration: 2026-09-27
Also published as: WO2025199824A1

Abstract

Various solutions for data collection across connection states in mobile communications are described. A user equipment (UE) may transmit an indication associated with a data collection configuration to a network node in an event that the UE transits to a connected state. The UE may receive a data collection control associated with the data collection configuration from the network node. Then, the UE may determine an activated data collection configuration according to the data collection control. Furthermore, the UE may perform an artificial intelligence (AI) or machine learning (ML) related data collection based on the activated data collection configuration, and report collected data to the network node in an event that a reporting condition is met. Based on the data collection control, the data collection configuration may be maintained even when the UE transitions back and forth between different states, so the data collection across connection states can be achieved.

Description

METHODS AND APPARATUS OF DATA COLLECTION ACROSS CONNECTION STATES IN MOBILE COMMUNICATIONS

CROSS REFERENCE TO RELATED PATENT APPLICATION (S)

The present disclosure is part of a non-provisional application claiming the priority benefit of PCT Application No. PCT/CN2024/084213, filed 27 March 2024, the content of which herein being incorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure is generally related to mobile communications and, more particularly, to data collection across connection states with respect to user equipment and network apparatus in mobile communications.

BACKGROUND

Unless otherwise indicated herein, approaches described in this section are not prior art to the claims listed below and are not admitted as prior art by inclusion in this section.

Artificial intelligence (AI) and machine learning (ML) are increasingly vital in wireless networks for optimizing performance and user experience. Effective AI/ML model development relies heavily on robust data collection, a crucial step in the AI/ML lifecycle management (LCM) process. The quality and quantity of collected data directly influence model performance, necessitating a well-defined over-the-air data collection solution for both UE-side and network-side model inference, monitoring, and training. Consequently, developing an enhanced framework to collect data and measurement results from UEs for AI/ML model training, including when UEs transition back and forth between different states, is essential to reduce specification and implementation effort.

SUMMARY

The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

An objective of the present disclosure is to propose solutions or schemes that address the aforementioned issue pertaining to data collection across connection states with respect to user equipment (UE) and network apparatus in mobile communications.

In one aspect, a method may involve an apparatus transmitting an indication associated with a data collection configuration to a network node in an event that the apparatus transits to a connected state. The method may also involve the apparatus receiving a data collection control associated with the data collection configuration from the network node. The method may also involve the apparatus determining an activated data collection configuration according to the data collection control. The method may also involve the apparatus performing an artificial intelligence (AI) or machine learning (ML) related data collection based on the activated data collection configuration. The method may further involve the apparatus reporting collected data to the network node in an event that a reporting condition is met.

In another aspect, an apparatus may comprise a transceiver which, during operation, wirelessly communicates with a network. The apparatus may also comprise a processor communicatively coupled to the transceiver. The processor, during operation, may perform operations comprising transmitting, via the transceiver, an indication associated with a data collection configuration to a network node in an event that the apparatus transits to a connected state. The processor may also perform operations comprising receiving, via the transceiver, a data collection control associated with the data collection configuration from the network node. The processor may also perform operations comprising determining an activated data collection configuration according to the data collection control. The processor may also perform operations comprising performing an AI or ML related data collection based on the activated data collection configuration. The processor may further perform operations comprising reporting collected data to the network node in an event that a reporting condition is met.

In yet another aspect, a method may involve a network node receiving an indication associated with a data collection configuration for an AI/ML related data collection from a UE. The method may also involve the network node transmitting a data collection control associated with the data collection configuration to the UE. The method may further involve the network node receiving data collected by the UE. In which, the data is collected based on an activated data collection configuration determined according to the data collection control.

It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as LTE, LTE-Advanced, LTE-Advanced Pro, 5G, NR, 5G-Advanced, Internet-of-Things (IoT) , Narrow Band Internet of Things (NB-IoT) , Industrial Internet of Things (IIoT) , beyond 5G (B5G) , and 6th Generation (6G) , the proposed concepts, schemes and any variation (s) /derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies. Thus, the scope of the present disclosure is not limited to the examples described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.

FIG. 1 is a diagram depicting an example scenario of a communication environment in which various solutions and schemes in accordance with implementations of the present disclosure.

FIG. 2 is a diagram depicting an example scenario of data collection across connection states in accordance with implementations of the present disclosure.

FIGs. 3A to 3H are diagrams depicting exemplary sub-procedures for AI/ML related data collection across connection states in accordance with implementations of the present disclosure.

FIG. 4 is a diagram depicting example scenarios of cross correlation between measurement samples in accordance with implementations of the present disclosure.

FIGs. 5A and 5B are diagrams depicting exemplary scenario and procedure related to data collection during handover (HO) in accordance with implementations of the present disclosure.

FIGs. 6A and 6B are diagrams depicting exemplary procedures related to abnormal case handling of data collection in accordance with implementations of the present disclosure.

FIG. 7 is a block diagram of an example communication system in accordance with an implementation of the present disclosure.

FIG. 8 is a flowchart of an example process in accordance with an implementation of the present disclosure.

FIG. 9 is a flowchart of another example process in accordance with an implementation of the present disclosure.
DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.
Overview

Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to data collection across connection states in mobile communications. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.

FIG. 1 illustrates an example scenario 100 of a communication environment in which various solutions and schemes in accordance with the present disclosure may be implemented. Scenario 100 involves a user equipment (UE) 110 in wireless communication with a wireless network consisting of an access network 125 and a core network (CN) 130. The wireless network may be a 5G NR network, 5G-Advanced network, 6G network, however, the present disclosure is not limited thereto. The UE 110 may be a smart phone, a wearable device, an IoT device, and a tablet, etc. Alternatively, the UE 110 may be a notebook (NB) or personal computer (PC) inserted or installed with a data card which includes a modem and radio frequency (RF) transceiver (s) to provide the functionality of wireless communication. The CN 130 may include entities such as user plane function (UPF) , mobility management function (AMF) , session management function (SMF) and unified data management (UDM) , etc. The access network 125 may include one or more base stations (BSs) , such as the BS 120. The BS 120 may be an evolved NodeBs (eNB) , a next generation NodeB (gNB) , or a transmission and reception point (TRP) . The BS 120 may provide communication coverage for a geographic coverage area where communications with the UE 110 is supported.

Scenario 100 further involves an operations, administration, and maintenance (OAM) device 140 and a UE server 150. The OAM device 140 may include a set of functions and protocols used to manage and maintain network equipment and services. The UE server 150 (may also be referred to as an over-the-top (OTT) server) is introduced for certain applications such as artificial intelligence (AI) , machine learning (ML) , or other applications that require model training. The UE server 150 is responsible for collecting and storing data reported by UEs (e.g., the UE 110) , and may also have functions for model training. The UE server 150 may be a UE-side server, which is over-the-top and 3GPP transparent. Alternatively, the UE server 150 may be a UE-side server which is over-the-top but non-3GPP transparent. The deployment of the UE server 150 may be within or outside the OAM domain (e.g., may be in the CN domain) . The UE server 150 may receive and store the data or data files and build up a dataset for model training. The UE server 150 may also perform model training with the dataset. Specifically, the UE server 150 organizes the received data into a structured format (i.e., the dataset) , which may be used for further analysis or processing. This might involve data cleaning, data transformation, and labeling.

FIG. 2 is a diagram depicting an example scenario of data collection across connection states in accordance with implementations of the present disclosure. As shown in scenario 200, a data collection session starts from time T2 to time T10, which spans, for example, three connection states. More specifically, the UE 110 may transit from a non-connected state (e.g., an INACTIVE/IDLE state or a radio resource control (RRC) INACTIVE/IDLE state) to a CONNECTED state (e.g., an RRC CONNECTED state) and establishes a connection (e.g., an RRC connection) with the BS 120 at time T1. For example, the UE 110 may establish the RRC connection with the BS 120 through RRC connection setup, RRC connection resume, or RRC connection re-establishment procedure. After that, the UE 110 may transmit a UE capability report 211 to the BS 120, indicating its AI/ML related capabilities. Then, the UE 110 may receive a data collection configuration 215 from the BS 120. When one or more collection start criteria are met at time T2, the UE 110 initiates data collection based on the data collection configuration 215. At time T3, the UE 110 releases the connection and transits from the CONNECTED state to the INACTIVE/IDLE state. From time T3 to time T4, the data collection is stopped. However, the data collection configuration 215 used in the last connection is kept in the UE 110.

In scenario 200, the UE 110 re-enters the CONNECTED state at time T4. Given the possibility that the RRC context may be lost (e.g., due to not being kept or transferred) at the radio access network (RAN) when the UE 110 transits to the INACTIVE/IDLE state, the UE 110 is required to report its current data collection configuration or status upon re-entering the CONNECTED state. Accordingly, the UE 110 transmits an indication 221 associated with the data collection configuration 215 to the BS 120. The indication 221 may include a data collection configuration identifier (ID) and/or a data collection configuration content of the data collection configuration 215. Then, the UE 110 receives a data collection control 225 associated with the data collection configuration 215 from the BS 120. In scenario 200, the data collection control 225 includes an effectiveness acknowledgement (ACK) of the data collection configuration 215. Upon receiving the data collection control 225, the UE 110 determines the data collection configuration 215 to be activated and resumes data collection at time T5. That is, the resumed data collection is performed based on the data collection configuration 215. The UE 110 may keep the configuration release timer (e.g., T330) running when the data collection control 225 includes the effectiveness ACK. In another embodiment, if the data collection control 225 includes a first suspending message, the UE 110 may suspend the data collection configuration 215. Specifically, the UE 110 may retain the original data collection configuration 215 but treat it as inactive. The UE 110 may suspend the original configuration release timer, alternatively, the UE 110 may keep the timer running. In yet another embodiment, if the data collection control 225 includes a second suspending message, the UE 110 may suspend a report configuration specified for the data collection configuration 215. To be specific, the UE 110 continues to perform the data collection according to the measurement configuration defined within the data collection configuration 215. However, the UE 110 suspends the data reporting. In this embodiment, the configuration release timer may continue to run.

From time T6 to time T7, the data collection is stopped as the UE 110 transits from the CONNECTED state to the INACTIVE/IDLE state. During this period, the activated data collection configuration used in the last connection (i.e., the data collection configuration 215) is kept in the UE 110. At time T7, the UE 110 transits to the CONNECTED state again, and then transmit an indication 231 associated with the kept activated data collection configuration to the BS 120. Then, a data collection control 235 is received. In scenario 200, the data collection control 235 includes a reconfiguration message, the UE 110 reconfigures/updates the data collection configuration 215 and determines the reconfigured data collection configuration as the activated configuration. The data collection is resumed at time T8. As shown in scenario 200, after receiving a data collection deactivation command 247 from the BS 120 at time T9, the UE 110 stops the data collection at time T10.

In scenario 200, the indications 221 and 231 and the data collection controls 225 and 235 may be carried by an RRC signaling. The UE 110 may restore, suspend, or reconfigure the data collection configuration based on information in the data collection control. One data collection configuration may be maintained even when the UE 110 transits between CONNECTED and INACTIVE/IDLE states multiple times. That is, as long as the effectiveness ACK is received, the UE 110 may maintain this configuration regardless of its state (e.g., IDLE, INACTIVE, or CONNECTED) , despite interruptions caused by state transitions.

In the present disclosure, the data collection configuration may be carried by at least one of an RRC message, a medium access control (MAC) -control element (CE) message, and a downlink control information (DCI) message. The UE 110 may store the collected data in a variable or in a data file. The collected data may also be referred to as measurement logs, logs, collected data/logs, data collected, logged measurement, measurement logging, or logged measurement information. In scenario 200, when a reporting condition is met or upon receiving a reporting message from the BS 120, the UE 110 may report the collected data to the BS 120. The collected data may be further transmitted to the UE server 150 via one or a combination of the BS 120, the CN 120, and the OAM device 140. The collected data may be used for various AI/ML life cycle management (LCM) purposes, including model training, model inference, and model monitoring, across different use cases or AI/ML enabled features of UE-side, network-side, and two-sided models.

FIGs. 3A to 3H are diagrams depicting exemplary sub-procedures for AI/ML related data collection across connection states in accordance with implementations of the present disclosure. The sub-procedures may comprise UE capabilities reporting process, activated data collection configuration control process, data collection configuration providing process, data collection process, and data reporting process.

Referring to FIG. 3A, which illustrates an exemplary sub-procedure 300a of UE capabilities reporting process. It is assumed that the UE 110 is initiated to the CONNECTED state, thus there is no data collection configuration stored in the UE 110 (i.e., the UE 110 has no activable data collection configuration) . In such a case, the UE 110 may comply and transfer a UE capability report upon receiving a capability enquire (e.g., UECapabilityEnquiry) from the BS 120. The BS 120 may determine the data collection configuration based on the UE capability report. The UE capability report (e.g., UECapabilityInformation) may include information related to one or a combination of a memory size, a remaining battery power, a carrier aggregation (CA) capability, a dual connectivity (DC) capability, a supported use case, an AI or ML enabled feature (e.g., AI-enabled beam management (BM) , AI-enabled channel state information (CSI) prediction, AI-enabled positioning, AI-enabled mobility, etc. ) , a supported data type to be collected (e.g., raw channel data, CSI information, UE position information, UE speed, etc. ) for different AI/ML-enabled features, and other information associated with the UE capability related to AI or ML. In one example, the UE capability report may further indicate whether data collecting/measurement logging in CONNECTED state is supported or not. In another example, the UE capability report may provide information on whether non-standardized data type can be collected. In yet another example, the UE capability report may provide information on the CA/DC capability for different bands and band combinations. Based on this information, the network may utilize the CA/DC capability of the UE 110 to collect the data and measurement logs across different frequencies.

Referring to FIG. 3B, which illustrates an exemplary sub-procedure 300b of activated data collection configuration control process. In one embodiment, the UE 110 re-enters the CONNECTED state from the INACTIVE/IDLE state. In such a case, a data collection configuration has been stored in the UE 110. Based on sub-procedure 300a, the UE 110 may determine whether to restore, suspend, or reconfigure the data collection configuration previously stored. To be specific, the UE 110 transmits a data collection configuration indication (e.g., ActiveLogConfigurationIndication) to the BS 120 through an RRC message. In one example, the data collection configuration indication may be transmitted by a UE assistance information message (e.g., UEAssistanceInformation) . The data collection configuration indication may include an ID of the data collection configuration previously stored, which is assigned by the network. In one example, the UE 110 may transmit the ID of the data collection configuration in a complete message (e.g., RRCSetupComplete, RRCResumeComplete or RRCReestablishedComplete message) when transits to the CONNECTED state. The data collection configuration indication may further include the content of the data collection configuration the UE 110 configured. In another embodiment, the UE 110 is initiated to the CONNECTED state. Since the UE 110 has no activable data collection configuration, it may transmit a data collection configuration indication to the BS 120 with an ID indicating the absence of an activable data collection configuration (e.g., 0/null/NaN/None) .

After transmitting the data collection configuration indication, the UE 110 receives a data collection control (e.g., ActiveLogConfigurationControl) from the BS 120. In one embodiment, if the data collection control includes an effectiveness ACK of the original data collection configuration, the UE 110 keeps the original configuration, and the configuration release timer (e.g., T330) keeps running. In one embodiment, if the data collection control includes a reconfiguration message, the UE 110 reconfigures/updates the original data collection configuration, and restarts the configuration release timer (e.g., T330) . In one embodiment, the BS 120 determines to suspend the original data collection configuration and includes the corresponding message in the data collection control. Consequently, the UE 110 suspends the original data collection configuration. The UE 110 may keep the original configuration but considers it not to take effect. In one embodiment, information elements (IEs) in the data collection configuration may include a measurement configuration part and a report configuration part. The measurement configuration part includes measurement configuration (s) relating to information about performing the data collection, such as the measurement quantity and the data type for different use cases, and the logging triggering event (s) , etc. The report configuration part includes report configuration (s) relating to information about reporting the collected data, including the reporting triggering event (s) , data recording session reference, and reporting periodicity, etc. The BS 120 may determine to suspend the report configuration of the original data collection configuration and includes the corresponding message in the data collection control. Consequently, the UE 110 suspends the report configuration of the original data collection configuration. That is, the UE 110 considers the report configuration not to take effect and stops data reporting. However, the UE 110 may consider the measurement configuration to take effect and continue to perform data collection. The original configuration release timer (e.g., T330) keeps running. In one embodiment, the BS 120 determines to suspend the measurement configuration of the data collection configuration and includes the corresponding message in the data collection control. Consequently, the UE 110 suspends the measurement configuration of the data collection configuration, considers the measurement configuration not to take effect and only performs data reporting. In one embodiment, the UE 110 considers the data collection configuration is active in the CONNECTED state until the configuration release timer (e.g., T330) expires, which is used to control the validity period of a data collection configuration. In one embodiment, the UE 110 considers the data collection configuration is active in the CONNECTED state until explicit suspending/stopping of the configuration is received from the BS 120. When the UE 110 receives suspending/stopping of the configuration, in one embodiment, the UE 110 may suspend/stop the original configuration release timer. In another embodiment, the UE 110 may keep the configuration release timer running.

FIGs. 3C and 3D illustrate different exemplary sub-procedures corresponding to data collection configuration providing process. As shown in FIG. 3C, the data collection configuration may be provided by bidirectional RRC signaling. Specifically, the BS 120 initiates sub-procedure 300c to the UE 110 in the RRC CONNECTED state by transmitting a bidirectional RRC message (e.g., RRCReconfiguration) . The UE 110 may store the data collection configuration and transmit a complete message (e.g., RRCReconfigurationComplete) back to the BS 120. In one embodiment, the UE 110 discards the original data collection configuration as well as the collected data/logged measurement information. In another embodiment, the UE 110 modifies the data collection configuration and maintains the collected data/logged measurement information per previous configuration if exists; additionally, the UE 110 adds a leap in timestamp or a mark indicating it’s the starting of collected data/logged measurement for the new configuration. Besides, the UE 110 may start (or restart) a configuration release timer (e.g. T330) to control the effectiveness of the configuration with the timer value set to the loggingDuration.

Alternatively, as shown in FIG. 3D, the data collection configuration may be provided by unidirectional RRC signaling. To be specific, the BS 120 may initiate sub-procedure 300d to the UE 110 in the RRC CONNECTED state by transmitting a unidirectional RRC message (e.g., LoggedMeasurementConfiguration) . When the UE 110 receives such RRC message, the UE 110 discards the current data collection configuration as well as the collected data/logged measurement information, stores the received data collection configuration, and starts a configuration release timer (e.g. T330) to control the validity of the configuration with the timer value set to, for example, loggingDuration.

The data collection configuration received by the UE 110 through sub-procedure 300c or 300d may be associated with an ID and is stored by the UE 110 in any state. In one embodiment, the ID is assigned by the network. The data collection configuration is stored in the UE inactive access stratum (AS) context. When the UE 110 transits from the INACTIVE/IDLE state to the CONNECTED state, the UE 110 sends the configuration ID for the network to retrieve the data collection configuration. If the UE inactive AS context can be retrieved by the current serving RAN node (e.g., the BS 120) , the UE 110 restores the inactive AS context as well as the data collection configuration. In one embodiment, the report tunnel is user plane (UP) based, the UE 110 may establish or modify a data radio bearer (DRB) to send the collected data/measurement logging.

A release operation is supported in both sub-procedures 300c and 300d. In one embodiment, a release operation for the data collection configuration in the UE 110 is realized by either releasing the data collected/logged measurement or by configuration clearance in case a configuration release timer (e.g. T330) stops, or an expiration condition is met. Upon expiry of the configuration release timer, the UE 110 may release the data collection configuration. In one embodiment, the UE 110 discards the data collection configuration as well as the collected data/logged measurement information. In another embodiment, the UE 110 discards the measurement configuration but keeps the report configuration. In yet another embodiment, the UE 110 keeps the collected data/logs and the report configuration for a specific time period (e.g., 48 hours) from the moment the configuration release timer for logging expired. In still another embodiment, the UE 110 keeps the report configuration as long as the collected data/logs are kept.

The UE 110 may release the measurement configuration and/or the report configuration when a release procedure is initiated. In one embodiment, the UE 110 may initiate the release procedure upon receiving an RRC message to disable data collected/logged measurement. In one embodiment, the UE 110 may initiate the release procedure when the configuration is overwritten or by configuration clearance in case a duration timer stopping or expiration condition is met. In one embodiment, the UE 110 may initiate the release procedure when it is in another radio access technology (RAT) . In one embodiment, the UE 110 may initiate the release procedure when it is in a wrong public land mobile network (PLMN) . In one embodiment, the UE 110 may initiate the release procedure when power off or upon deregistration. In these situations, the UE 110 may stop the running configuration release timer (e.g. T330) . In one embodiment, the UE 110 may discard the data collection configuration as well as the collected data/logged measurement information. In one embodiment, the UE 110 may discard the measurement configuration but keep the report configuration. In one embodiment, the UE 110 may keep the collected data/logs and the report configuration for 48 hours from the moment the configuration release timer for logging expired. In one embodiment, the UE 110 may keep the report configuration as long as the collected data/logs are kept.

In one embodiment, UP based data/log report is supported. For the configuration release procedure, in one embodiment, the UE 110 may discard the data collection configuration as well as the collected data/logged measurement information. The UE 110 releases the DRB used for sending the collected data/measurement logging. In another embodiment, the UE 110 may discard the measurement configuration but keep the report configuration and keep the collected data/log. The UE 110 suspends the DRB and reports the data/log when it backs to the normal state (e.g., power on/in a PLMN in PLMN list/registration) .

In the present disclosure, the data collection configuration may correspond to one or a combination of a measurement quantity for different use cases, a data type, use case related information, a logging triggering event, a data collecting or logging duration, a data collecting or logging interval, a reporting triggering event, a reporting periodicity, a network absolute time stamp, a server internet protocol (IP) address, a server identifier (ID) (e.g., the IP address/ID of the UE server 150, and may be indicated by the OAM configuration) , a data collecting or logging reference (may be indicated by the OAM configuration) , a data collecting or logging session reference (may be indicated by the OAM configuration) , a logging area, a data collecting or logging PLMN list, a correlation between measurement samples (e.g., in frequency, temporal or spatial domain) , and vendor specific measurement information (e.g., whether to allow taking vendor specific measurements supported by configuration container) . In one embodiment, the data collection configuration may further specify the use case, AI/ML-enabled feature, or gNB/cell/UE configuration conditions targeted by the data collection session.

In one embodiment, the configuration associated with vendor specific measurement information is provided by a configuration container. Accordingly, the collected data/logs for the vendor specific measurement may be carried in a reporting container when reporting. For example, the configuration container may carry one or a combination of the use cases or AI/ML enabled feature, vendor specific ID, the specific format for reporting (e.g., abstract syntax notation one (ASN. 1) or extensible markup language (XML) ) .

In one embodiment, the correlation between measurement samples is configured. Specifically, certain measurement (s) may be designated as primary, and secondary measurement (s) shall be collected whenever a sample of a primary measurement is taken. Several example scenarios of cross correlation between measurement samples are shown in FIG. 4. In one example, as shown in scenario 410, the primary measurement is the measurement on the serving cell and the secondary measurements are the measurements on the neighboring cells. That is, the serving cell (e.g., the primary cell) measurement may be designated as primary, while the neighboring cell (e.g., the secondary cell) measurements are designated as secondary. In another example, as shown in scenario 420, the primary measurement is the measurement on one frequency (e.g., the frequency of the serving cell primary cell) and the secondary measurements are the measurements on other frequencies. Namely, the primary measurement is the measurement on a specific frequency (e.g., the frequency of the serving cell/primary cell) and the secondary measurements are the measurements on other frequencies, which are correlated to the primary measurement objective of the serving cell. In yet another example, as shown in scenario 430, the primary measurements are the measurements on a primary set of beams and the second measurements are the measurements on a secondary set of beams. In still another example, as shown in scenario 440, the primary measurements are the measurements on a primary set of timeslots/subframes/frames/time durations and the second measurement are the measurement on a secondary set of timeslots/subframes/frames/time durations. Further, as shown in scenario 450, the correlation between the primary measurement and the secondary measurement may be the combination of time/frequency resources between different cells and frequencies. In the foregoing examples, the correlation between the primary measurement (s) and the secondary measurement (s) is assigned by an ID (e.g., correlation ID) .

In one embodiment, for the configuration of the logging triggering event (s) , a periodic measurement trigger is supported, for which the logging interval is configurable. The parameter in the data collection configuration may specify the periodicity for storing minimization of drive test (MDT) measurement results. Alternatively, an event-based trigger is supported, for which the logging interval is configurable, which determines periodical logging of available data. Examples of such events may include enable of certain features, and measurement quantity-based event layer 1 (L1) , for which the event threshold, hysteresis, and time to trigger are configurable.

In another embodiment, for the configuration of the reporting triggering event (s) , an event-based trigger is supported. Examples of such events may include enable of certain features, measurement quantity-based event L1, event A1, A2, A3, A4, A5, A6, D1, or I1, for which the event threshold, hysteresis, and time to trigger are configurable. Data volume is above a threshold, which is configurable. Alternatively, a periodic report trigger is supported, for which the report periodicity, report amount, etc, are configurable.

Referring back to FIGs. 3E and 3F, which illustrate exemplary sub-procedures of a data collection process for AI/ML related data collection across connection states. As shown in sub-procedure 300e, the data collection configuration may indicate whether to start/stop the data collection explicitly (e.g., by an indication/flag) . That is, the UE 110 may start and stop the data collection as indicated by the network. In sub-procedure 300f, the data collection is enabled by the network and the UE 110 may start a data collection timer upon receiving such indication/flag, and stop the data collection when the data collection timer expires. To be specific, the data collection timer is set to control the data collection process. The UE 110 starts the data collection timer when it starts data collection. The UE 110 stops the timer when one or more collection stop criteria are satisfied.

In the present disclosure, the UE 110 starts or resumes the data collection in the CONNECTED state when one or more collection start criteria are satisfied and stops the data collection when one or more collection stop criteria are satisfied or in the INACTIVE/IDLE state. In one embodiment, the UE 110 performs use case specific measurements only when the corresponding feature is available and only for logging intervals for which the feature is available. In one embodiment, when a logging area is configured, the data collection may be performed as long as the UE 110 is within this logging area (e.g., a cell list) . In one embodiment, when one or multiple PLMNs are configured, the UE 110 performs the data collection when it is within the PLMN list. In one embodiment, the UE 110 collects data and logs measurements and continues data collecting/logging according to the data collection configuration until its memory reserved for data collection is full. In this case the UE 110 stops logging, stops the data collection timer and starts another timer, e.g. 48 hours timer. The UE 110 keeps the collected/logged data until the timer (e.g., 48-hour timer) expires.

The UE 110 may store the collected data in a variable or a data file during the data collection process. The UE 110 may maintain the data collection configuration and collected data/logs when it is in any state (e.g., IDLE/INACTIVE/CONNECTED state) despite multiple periods interrupted by state transitions.

In the present disclosure, the collection start criteria may include one or a combination of reception of a data collection activation command/message (e.g., through RRC MAC-CE, or DCI) , enabling of a target use case or AI or ML feature, moving to a new cell which is in the configured data collecting/logging area, being in an associated PLMN, battery power being equal to or above a power threshold (e.g., in a high-battery state) , having a good radio condition (e.g., T310 timer is stopped when a layer 3 (L3) reference signal received power (RSRP) is equal to or above a specific threshold) , and configuration of the BS 120 or UE 110 matching a data collection target. The collection stop criteria may include one or a combination of reception of a data collection deactivation command/message (e.g., through RRC MAC-CE, or DCI) , a data collection timer being expired, memory full, disabling of a target use case or AI or ML feature, being outside of a data collection or logging area, being outside of an associated PLMN, battery power being below a threshold (e.g., in a low-battery state) , having a bad radio condition (e.g., T310 timer is running when a L3 RSRP is below a specific threshold) , configuration of the BS 120 or UE 110 not matching a data collection target, a connection between the UE 110 and the BS 120 being released, and the activated data collection configuration being released.

In the present disclosure, the collected data may include information corresponding to one or a combination of a use case, an AI or ML enabled feature, a physical cell identity (PCI) of a logged cell, a carrier frequency, a signal quality measurement, a RSRP, a reference signal received quality (RSRQ) , a received signal strength indicator (RSSI) , a L1-RSRP, a beam index, a position information of the apparatus, a time stamp, a channel matrix, a CSI feedback, a channel impulse response (CIR) , a power delay profile (PDP) , a performance indicator (e.g., system level key performance indicators (KPI) or immediate KPI such as throughput, prediction accuracy, handover failure (HOF) rate, etc. ) , a vendor specific measurement in reporting container, a correlation between measurement samples (e.g., the correlation between the primary measurement samples and the secondary measurement samples in form of, for example, correlation ID) , an equipment ID, logging of additional information, an RAN configuration, a cell configuration, and a UE condition.

FIGs. 3G and 3H illustrate different exemplary sub-procedures for a data reporting process for AI/ML related data collection across connection states. The UE 110 may report the collected data to the BS 120 when receiving a reporting message from the BS 120 or when a preconfigured event is satisfied, and the collected data may be reported through an RRC message or a DRB. More specifically, the UE 110 may establish or modify the DRB according to the data collection configuration, and a priority is assigned to the DRB. For example, the DRB configured for reporting the collected data has the lowest priority than other DRBs. As shown in sub-procedure 300g, when the BS 120 decides to retrieve the data/logs collected by the UE 110, it may initiate a UE Information procedure by transmitting an RRC message (e.g., UEInformationRequest) . Then the UE 110 sends the collected data/logs through another RRC message (e.g., UEInformationResponse) . In one embodiment, transport of collected data/logs in multiple RRC messages is supported. With every request, the BS 120 may receive a part of the total collected data/logs. To indicate the collected data/logs is a segment, the UE 110 may include a data availability indicator in UEInformationResponse message to convey the information that further collected data/logs is available. In multiple RRC transmissions for segmented data/logs reporting, a first-in first-out (FIFO) order is followed. That is, the UE 110 may provide the oldest available measurement entries in the earliest message. In one example, each reported part is self-decodable (i.e., interpretable) even if all the other parts are not available. On the other hand, as shown in sub-procedure 300h, the UE 110 may check whether the reporting triggering event (s) configured by the BS 120 is met. When at least one reporting triggering event is met, the UE 110 may start the data/logs reporting. For example, the UE 110 may send the availability indication or report data/logs when the memory for the collected data/logs is equal to or below a threshold (i.e., low memory) . In one embodiment, the collected data/logs are transmitted through an RRC message (e, g., MeasurementReport) .

In sub-procedure 300g or 300h, the collected data may be reported through the DRB. In one example, the DRB is suspended by default, until a resume indication/request is received from the BS 120 before data reporting. Then the UE 110 resumes the DRB for reporting the collected data/logs. In another example, the DRB is resumed by default. The UE 110 may indicate the availability of the collected data/logs through a scheduling request (SR) or a buffer status report (BSR) procedure and sends the collected data/logs through a logical channel prioritization (LCP) procedure when uplink (UL) grant is received from the BS 120. In one example, if the reporting triggering event is configured, the UE 110 indicates the availability of the collected data/logs through the SR/BSR procedure when the event is satisfied (e.g., the stored data/logs volume is above a threshold) .

In normal operation, the UE 110 may discard the old data collection configuration and the collected data/logs for the old data collection configuration when the configuration release timer expires, the UE memory is full, or the UE 110 is configured with a new data collection configuration. In one embodiment, the report is stored if the UE 110 cannot report the collected data (e.g., due to change of PLMN or no valid server address available) . Under abnormal circumstances, there may be instances where power off/deregistration/UE in wrong PLMN/in another RAT, the UE 110 may store the report and starts another timer (e.g., 48 hours) , and keeps the collected/logged data till the timer expires.

FIGs. 5A and 5B are diagrams depicting exemplary scenario and procedure related to data collection during handover (HO) in accordance with implementations of the present disclosure. As shown in scenario 500a, the source cell 510 may retrieve the collected data/logs by transmitting a reporting message or waiting for a preconfigured event to be satisfied. After the HO is completed, the target cell 520 may retrieve the collected data/logs. More specifically, as shown in procedure 500b, when the network is about to perform the HO for the UE 110, the source cell 510 will coordinate with the target cell 520 regarding the data collection configuration. The data collection configuration for the UE 110 may be propagated during the UE context retrieving process of the HO procedure. After the HO, the UE 110 transmits a data availability indication to the target cell 520 to indicate the availability of the previously stored collected data/logs. The target cell 520 may then decide whether to retrieve the remaining data/logs or let the UE 110 release them. In one embodiment, data retrieval and reporting may use the UE Information procedure. In another embodiment, if a DRB is used for data/log reporting, the reporting of the collected data/logs may continue with packet data convergence protocol (PDCP) data recovery or PDCP re-establishment if the DRB is not released. Otherwise, the previously stored collected data/logs are discarded if the DRB is released by the target cell 520.

FIGs. 6A and 6B are diagrams depicting exemplary procedures related to abnormal case handling of data collection in accordance with implementations of the present disclosure. When a HOF or a radio link failure (RLF) occurs, the UE 110 may trigger an RRC re-establishment procedure, and release the data collection configuration when initiating the RRC re-establishment procedure. In one embodiment, as shown in procedure 600a, the UE 110 discards the previously stored collected data/logs when initiating the RRC Re-establishment procedure. In another embodiment, as shown in procedure 600b, the UE 110 keeps the previously stored collected data/logs when initiating the RRC Re-establishment procedure. When the UE 110 receives an RRC re-establishment or setup message (e.g., RRCReestablishment or RRCSetup) , the UE 110 transmits a data availability indication to the BS 120 to indicate the availability of the collected data/logs. The data availability indication may be transmitted in an RRC re-establishment complete or setup complete message (e.g., RRCReestablishmentComplete or RRCSetupComplete) . Then, the BS 120 may decide whether to retrieve the remaining data/logs.
Illustrative Implementations

FIG. 7 illustrates an example communication system 700 having at least an example communication apparatus 710 and an example network apparatus 720 in accordance with an implementation of the present disclosure. Each of the communication apparatus 710 and network apparatus 720 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to data collection across connection states in mobile communications, including scenarios/schemes described above as well as processes 800 and 900 described below.

Communication apparatus 710 may be a part of an electronic apparatus, which may be a UE such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus. For instance, communication apparatus 710 may be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Communication apparatus 710 may also be a part of a machine type apparatus, which may be an IoT, NB-IoT, or IIoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus. For instance, communication apparatus 710 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. Alternatively, communication apparatus 710 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. Communication apparatus 710 may include at least some of those components shown in FIG. 7 such as a processor 712, for example. Communication apparatus 710 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device) , and, thus, such component (s) of communication apparatus 710 are neither shown in FIG. 7 nor described below in the interest of simplicity and brevity.

Network apparatus 720 may be a part of a network apparatus, which may be a network node such as a satellite, a base station, a small cell, a router or a gateway. For instance, network apparatus 720 may be implemented in an eNB in an LTE network, in a gNB in a 5G/NR, IoT, NB-IoT or IIoT network or in a satellite or base station in a 6G network. Network apparatus 720 may include at least some of those components shown in FIG. 7 such as a processor 722, for example. Processor 722 may further include protocol stacks and a set of control functional modules and circuits. Network apparatus 720 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device) , and, thus, such component (s) of network apparatus 720 are neither shown in FIG. 7 nor described below in the interest of simplicity and brevity.

In one aspect, each of the processor 712 and processor 722 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though a singular term “aprocessor” is used herein to refer to processor 712 and processor 722, each of the processor 712 and processor 722 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of the processor 712 and processor 722 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of the processor 712 and processor 722 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks in a device (e.g., as represented by communication apparatus 710) and a network (e.g., as represented by network apparatus 720) in accordance with various implementations of the present disclosure.

In some implementations, communication apparatus 710 may also include a memory 714 coupled to processor 712 and capable of being accessed by processor 712 and storing data therein. In some implementations, communication apparatus 710 may further include a transceiver 716 coupled to processor 712 and capable of wirelessly transmitting and receiving data.

In some implementations, network apparatus 720 may further include a memory 724 coupled to processor 722 and capable of being accessed by processor 722 and storing data therein, and a transceiver 726 coupled to processor 722 and capable of wirelessly transmitting and receiving data. Accordingly, communication apparatus 710 and network apparatus 720 may wirelessly communicate with each other via transceiver 716 and transceiver 726, respectively.

For illustrative purposes and without limitation, descriptions of capabilities of the communication apparatus 710 and network apparatus 720 are provided below with process 800 and process 900. In which, communication apparatus 710 is implemented in or as a communication apparatus or a UE, and network apparatus 720 is implemented in or as a network node of a communication network (e.g., a base station) .
Illustrative Processes

FIG. 8 illustrates an example process 800 in accordance with an implementation of the present disclosure. Process 800 may be an example implementation of above scenarios/schemes, whether partially or completely, with respect to data collection across connection states in mobile communications. Process 800 may represent an aspect of implementation of features of communication apparatus 710. Process 800 may include one or more operations, actions, or functions as illustrated by one or more of blocks 810, 820, 830, 840, and 850. Although illustrated as discrete blocks, various blocks of process 800 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 800 may be executed in the order shown in FIG. 8 or, alternatively, in a different order. Process 800 may be implemented by communication apparatus 710 or any suitable UE (e.g., UE 110) or machine type devices. Solely for illustrative purposes and without limitation, process 800 is described below in the context of communication apparatus 710 as a UE. Process 800 may begin at block 810.

At block 810, process 800 may involve processor 712 of communication apparatus 710 transmitting, via transceiver 716, an indication associated with a data collection configuration to a network node (e.g., network apparatus 720) in an event that communication apparatus 710 transits to a connected state. Process 800 may proceed from block 810 to block 820.

At block 820, process 800 may involve processor 712 receiving, via transceiver 716, a data collection control associated with the data collection configuration from the network node. Process 800 may proceed from block 820 to block 830.

At block 830, process 800 may involve processor 712 determining an activated data collection configuration according to the data collection control. Process 800 may proceed from block 830 to block 840.

At block 840, process 800 may involve processor 712 performing an AI/ML related data collection based on the activated data collection configuration. Process 800 may proceed from block 840 to block 850.

At block 850, process 800 may involve processor 712 reporting collected data to the network node in an event that a reporting condition is met.

In some implementations, the indication associated with the data collection configuration may include a data collection configuration identifier (ID) or a data collection configuration content.

In some implementations, at least one of the indication and the data collection control associated with the data collection configuration is carried by an RRC signaling.

In some implementations, process 800 may involve processor 712 determining the data collection configuration as the activated data collection configuration in an event that the data collection control includes an effectiveness acknowledgement of the data collection configuration. Also, process 800 may involve processor 712 determining a reconfigured data collection configuration as the activated data collection configuration in an event that the data collection control includes a reconfiguration message.

In some implementations, process 800 may involve processor 712 suspending the data collection configuration in an event that the data collection control includes a first suspending message.

In some implementations, process 800 may involve processor 712 suspending a report configuration specified for the data collection configuration in an event that the data collection control includes a second suspending message.

In some implementations, the activated data collection configuration is released based on a configuration release timer.

In some implementations, at least one of a measurement configuration and a report configuration specified for the activated data collection configuration is released in an event that a release procedure is initiated.

In some implementations, the release procedure is initiated in an event that at least one initiation condition is met. The initiation condition may include the activated data collection configuration being overwritten, a configuration clearance being performed in case a duration timer stopping or expiration condition is met, transitioning to another RAT, being in a wrong PLMN list, powering off, or deregistering.

In some implementations, the activated data collection configuration is released in an event that an RRC re-establishment procedure is initiated.

In some implementations, process 800 may further involve processor 712 discarding the collected data previously stored in communication apparatus 710 in an event that the RRC re-establishment procedure is initiated.

In some implementations, process 800 may further involve processor 712 transmitting, via transceiver 716, a data availability indication to the network node during the RRC re-establishment procedure.

In some implementations, process 800 may involve processor 712 starting a data collection in an event that one or more collection start criteria are satisfied.

In some implementations, process 800 may involve processor 712 stopping the data collection in an event that one or more collection stop criteria are satisfied.

In some implementations, process 800 may involve processor 712 storing the collected data in a variable or in a data file.

In some implementations, the collection start criteria may include one or a combination of reception of a data collection activation command from the network node, enabling of a target use case or AI or ML feature, moving to a new cell, being in an associated PLMN, battery power being equal to or above a threshold, having a first specific radio condition, and configuration of the network node or communication apparatus 710 matching a data collection target.

In some implementations, the collection stop criteria may include one or a combination of reception of a data collection deactivation command from the network node, a data collection timer being expired, memory full, disabling of a target use case or AI or ML feature, being outside of a data collection or logging area, being outside of an associated PLMN, battery power being below a threshold, having a second specific radio condition, configuration of the network node or communication apparatus 710 not matching a data collection target, a connection between communication apparatus 710 and the network node being released, and the activated data collection configuration being released.

In some implementations, at least one of the activated data collection configuration and the collected data previously stored in communication apparatus 710 is kept in an event that communication apparatus 710 transits from the connected state to the non-connected state.

In some implementations, the reporting condition is met by receiving a reporting message from the network node or in an event that a preconfigured event is satisfied.

In some implementations, the collected data is reported to the network node through an RRC signaling or a DRB.

In some implementations, the collected data is reported to the network node through the DRB, and the DRB is suspended by default, and a resume request is received from the network node before reporting the collected data through the DRB.

In some implementations, the collected data is reported to the network node through the DRB, and the DRB is resumed by default, and communication apparatus 710 transmits a data availability indication through an SR or a BSR.

In some implementations, at least one of the data collection configuration and the activated data collection configuration corresponds to one or a combination of a measurement quantity, a data type, use case related information, a logging triggering event, a data collecting or logging duration, a data collecting or logging interval, a reporting triggering event, a reporting periodicity, a network absolute time stamp, a server IP address, a server ID, a data collecting or logging reference, a data collecting or logging session reference, a logging area, a data collecting or logging PLMN list, a correlation between measurement samples, and vendor specific measurement information.

In some implementations, the collected data may include information corresponding to one or a combination of a use case, an AI/ML enabled feature, a PCI of a logged cell, a carrier frequency, a signal quality measurement, a RSRP, a RSRQ, a RSSI, an L1-RSRP, a beam index, a position information of communication apparatus 710, a time stamp, a channel matrix, a CSI feedback, a CIR, a PDP, a performance indicator, a vendor specific measurement in reporting container, a correlation between measurement samples, an equipment ID, logging of additional information, an RAN configuration, a cell configuration, and a UE condition.

In some implementations, process 800 may further involve processor 712 transmitting, via transceiver 716, a data availability indication to a target cell in an event that an HO associated with the target cell is completed.

FIG. 9 illustrates an example process 900 in accordance with an implementation of the present disclosure. Process 900 may be an example implementation of above scenarios/schemes, whether partially or completely, with respect to data collection across connection states in mobile communications. Process 900 may represent an aspect of implementation of features of network apparatus 720. Process 900 may include one or more operations, actions, or functions as illustrated by one or more of blocks 910.920, and 930. Although illustrated as discrete blocks, various blocks of process 900 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 900 may be executed in the order shown in FIG. 9 or, alternatively, in a different order. Process 900 may be implemented by network apparatus 720 or any base stations (e.g., BS 120) or network nodes. Solely for illustrative purposes and without limitation, process 900 is described below in the context of network apparatus 720. Process 900 may begin at block 910.

At block 910, process 900 may involve processor 722 of network apparatus 720 receiving, via transceiver 726, an indication associated with a data collection configuration for an AI/ML related data collection from a UE (e.g., communication apparatus 710) . Process 900 may proceed from block 910 to block 920.

At block 920, process 900 may involve processor 722 transmitting, via transceiver 726, a data collection control associated with the data collection configuration to the UE. Process 900 may proceed from block 920 to block 930.

At block 930, process 800 may involve processor 712 receiving, via transceiver 726, data collected by the UE. In which, the data is collected based on an activated data collection configuration determined according to the data collection control.

In some implementations, the indication associated with the data collection configuration may include a data collection configuration ID or a data collection configuration content.

In some implementations, the data collection control may include an effectiveness acknowledgement of the data collection configuration, a reconfiguration message for the data collection configuration, a data collection configuration suspending message, or a report configuration suspending message.
Additional Notes

The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected" , or "operably coupled" , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable" , to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Further, with respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to, ” the term “having” should be interpreted as “having at least, ” the term “includes” should be interpreted as “includes but is not limited to, ” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an, " e.g., “a” and/or “an” should be interpreted to mean “at least one” or “one or more; ” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two recitations, " without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B. ”

From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Claims

A method, comprising:

transmitting, by a processor of an apparatus, an indication associated with a data collection configuration to a network node in an event that the apparatus transits to a connected state;

receiving, by the processor, a data collection control associated with the data collection configuration from the network node;

determining, by the processor, an activated data collection configuration according to the data collection control;

performing, by the processor, an artificial intelligence (AI) or machine learning (ML) related data collection based on the activated data collection configuration; and

reporting, by the processor, collected data to the network node in an event that a reporting condition is met.
The method of Claim 1, wherein the indication associated with the data collection configuration comprises a data collection configuration identifier (ID) or a data collection configuration content.
The method of Claim 1, wherein at least one of the indication and the data collection control associated with the data collection configuration is carried by a radio resource control (RRC) signaling.
The method of Claim 1, wherein the determining of the activated data collection configuration according to the data collection control further comprises:

determining the data collection configuration as the activated data collection configuration in an event that the data collection control comprises an effectiveness acknowledgement of the data collection configuration; and

determining a reconfigured data collection configuration as the activated data collection configuration in an event that the data collection control comprises a reconfiguration message.
The method of Claim 1, further comprising:

suspending, by the processor, the data collection configuration in an event that the data collection control comprises a first suspending message; or

suspending, by the processor, a report configuration specified for the data collection configuration in an event that the data collection control comprises a second suspending message.
The method of Claim 1, wherein:

the activated data collection configuration is released based on a configuration release timer;

at least one of a measurement configuration and a report configuration specified for the activated data collection configuration is released in an event that a release procedure is initiated; or

the activated data collection configuration is released in an event that a radio resource control (RRC) re-establishment procedure is initiated.
The method of Claim 6, wherein the release procedure is initiated in an event that at least one initiation condition is met, wherein the initiation condition comprises:

the activated data collection configuration being overwritten;

a configuration clearance being performed in case a duration timer stopping or expiration condition is met;

transitioning to another radio access technology (RAT) ;

being in a wrong public land mobile network (PLMN) list;

powering off; or

deregistering.
The method of Claim 6, further comprising:

discarding, by the processor, the collected data previously stored in the apparatus in an event that the RRC re-establishment procedure is initiated; or

transmitting, by the processor, a data availability indication to the network node during the RRC re-establishment procedure.
The method of Claim 1, wherein the performing of the AI or ML related data collection further comprises:

starting a data collection in an event that one or more collection start criteria are satisfied;

stopping the data collection in an event that one or more collection stop criteria are satisfied or the apparatus transits from the connected state to a non-connected state; or

storing the collected data in a variable or in a data file.
The method of Claim 9, wherein the one or more collection start criteria comprise one or a combination of:

reception of a data collection activation command from the network node;

enabling of a target use case or AI or ML feature;

moving to a new cell;

being in an associated public land mobile network (PLMN) ;

battery power being equal to or above a threshold;

having a first specific radio condition; and

configuration of the network node or the apparatus matching a data collection target.
The method of Claim 9, wherein the one or more collection stop criteria comprise one or a combination of:

reception of a data collection deactivation command from the network node;

a data collection timer being expired;

memory full;

disabling of a target use case or AI or ML feature;

being outside of a data collection or logging area;

being outside of an associated public land mobile network (PLMN) ;

battery power being below a threshold;

having a second specific radio condition;

configuration of the network node or the apparatus not matching a data collection target;

a connection between the apparatus and the network node being released; and

the activated data collection configuration being released.
The method of Claim 9, wherein at least one of the activated data collection configuration and the collected data previously stored in the apparatus is kept in an event that the apparatus transits from the connected state to the non-connected state.
The method of Claim 1, wherein the reporting condition is met by receiving a reporting message from the network node or in an event that a preconfigured event is satisfied.
The method of Claim 1, wherein the collected data is reported to the network node through a radio resource control (RRC) signaling or a data radio bearer (DRB) .
The method of Claim 14, wherein the collected data is reported to the network node through the DRB, and wherein:

the DRB is suspended by default, and a resume request is received from the network node before reporting the collected data through the DRB; or

the DRB is resumed by default, and the apparatus transmits a data availability indication through a scheduling request (SR) or a buffer status report (BSR) .
The method of Claim 1, wherein at least one of the data collection configuration and the activated data collection configuration corresponds to one or a combination of a measurement quantity, a data type, use case related information, a logging triggering event, a data collecting or logging duration, a data collecting or logging interval, a reporting triggering event, a reporting periodicity, a network absolute time stamp, a server internet protocol (IP) address, a server identifier (ID) , a data collecting or logging reference, a data collecting or logging session reference, a logging area, a data collecting or logging public land mobile network (PLMN) list, a correlation between measurement samples, and vendor specific measurement information.
The method of Claim 1, wherein the collected data comprises information corresponding to one or a combination of a use case, an AI or ML enabled feature, a physical cell identity (PCI) of a logged cell, a carrier frequency, a signal quality measurement, a reference signal received power (RSRP) , a reference signal received quality (RSRQ) , a received signal strength indicator (RSSI) , a layer 1 (L1) -RSRP, a beam index, a position information of the apparatus, a time stamp, a channel matrix, a channel state information (CSI) feedback, a channel impulse response (CIR) , a power delay profile (PDP) , a performance indicator, a vendor specific measurement in reporting container, a correlation between measurement samples, an equipment identifier (ID) , logging of additional information, a radio access network (RAN) configuration, a cell configuration, and a user equipment (UE) condition.
The method of Claim 1, further comprising:

transmitting, by the processor, a data availability indication to a target cell in an event that a handover (HO) associated with the target cell is completed.
A method, comprising:

receiving, by a processor of a network node, an indication associated with a data collection configuration for an artificial intelligence (AI) or machine learning (ML) related data collection from a user equipment (UE) ;

transmitting, by the processor, a data collection control associated with the data collection configuration to the UE; and

receiving, by the processor, data collected by the UE, wherein the data is collected based on an activated data collection configuration determined according to the data collection control.
An apparatus, comprising:

a transceiver which, during operation, communicates wirelessly; and

a processor communicatively coupled to the transceiver such that, during operation, the processor performs operations comprising:

transmitting, via the transceiver, an indication associated with a data collection configuration to a network node in an event that the apparatus transits to a connected state;

receiving, via the transceiver, a data collection control associated with the data collection configuration from the network node;

determining an activated data collection configuration according to the data collection control;

performing an artificial intelligence (AI) or machine learning (ML) related data collection based on the activated data collection configuration; and

reporting collected data to the network node in an event that a reporting condition is met.