Method and apparatus for data collection across connection states in mobile communications

Abstract

Various solutions for data collection across connection states in mobile communications are described. A user equipment (UE) can send an indication related to a data collection configuration to a network node upon switching to a connected state. The UE can receive a data collection control related to the data collection configuration from the network node. Subsequently, the UE can determine an activated data collection configuration according to the data collection control. Furthermore, the UE can perform artificial intelligence (AI) or machine learning (ML) related to data collection based on the activated data collection configuration, and report collected data to the network node when a reporting condition is met. Based on the data collection control, the data collection configuration can be maintained even if the UE switches back and forth between different states, thus enabling data collection across connection states.

Description

[0001] Cross-referencing

[0002] This invention is part of a non-provisional application claiming priority to PCT application PCT / CN2024 / 084213 filed on March 27, 2024, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically, to the collection of data regarding the cross-connectivity state of user equipment (UE) and network devices in mobile communications. Background Technology

[0004] Unless otherwise stated herein, the methods described in this section are not prior art to the following claims, and are not considered prior art because they are included in this section.

[0005] Artificial intelligence (AI) and machine learning (ML) are increasingly important for optimizing performance and user experience in wireless networks. Effective AI / ML model development relies heavily on robust data collection, a critical step in the AI / ML lifecycle management (LCM) process. The quality and quantity of collected data directly impact model performance, thus requiring explicit air interface data collection solutions for model inference, monitoring, and training on both the user equipment (UE) and network sides. Therefore, developing an enhanced framework for collecting data and measurements from the UE for AI / ML model training, including when the UE switches between different states, is key to reducing specification and implementation workload. Summary of the Invention

[0006] The following abstract is for illustrative purposes only and is not intended to be limiting in any way. That is, the following abstract aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Some embodiments will be further elaborated in the detailed description below. Therefore, the following abstract is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0007] One objective of this disclosure is to propose solutions or schemes for data collection issues related to user equipment (UE) and network equipment in different connection states in mobile communications.

[0008] In one aspect, a method may involve a device sending an instruction related to a data collection configuration to a network node when switching to a connected state. The method may also involve the device receiving data collection control related to the data collection configuration from the network node. The method may further involve the device determining the active data collection configuration based on the data collection control. The method may also involve the device performing artificial intelligence (AI) or machine learning (ML) related to data collection based on the active data collection configuration. The method may further involve the device reporting the collected data to the network node when reporting conditions are met.

[0009] In another aspect, an apparatus may include a transceiver that wirelessly communicates with a network during operation. The apparatus may also include a processor communicatively connected to the transceiver. Operations that the processor can perform during operation include: sending an instruction related to a data collection configuration to a network node via the transceiver when the apparatus switches to a connected state. Further operations that the processor can perform include: receiving data collection control related to the data collection configuration from the network node via the transceiver. Further operations that the processor can perform include: determining an active data collection configuration based on the data collection control. Further operations that the processor can perform include: performing data collection-related AI or ML based on the active data collection configuration. Further operations that the processor can perform include: reporting the collected data to the network node when reporting conditions are met.

[0010] In another aspect, a method may involve a network node receiving from a UE an instruction related to a data collection configuration for AI / ML related to data collection. The method may also involve the network node sending data collection control related to the data collection configuration to the UE. The method may further involve the network node receiving data collected by the UE, wherein the data is collected based on an activated data collection configuration determined according to the data collection control.

[0011] It is worth noting that, although the content described herein may be set against the backdrop 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), Narrowband Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), B5G, and 6G, the proposed concepts, schemes, and any variations / derivatives thereof can be implemented, used, and implemented by other types of radio access technologies, networks, and network topologies. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0012] The accompanying drawings are included in this specification to further understand this disclosure and form part of this disclosure. The drawings illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual dimensions for clarity in illustrating the concepts of this disclosure.

[0013] Figure 1 The illustration depicts an example scenario of a communication environment under the implementation of this disclosure, including various solutions and schemes.

[0014] Figure 2 The illustration depicts an example scenario of data collection across connection states under an implementation of this disclosure.

[0015] Figures 3A-3H For illustrative purposes, an example subprocess for collecting artificial intelligence (AI) / machine learning (ML) related data across connection states is described in an embodiment of this disclosure.

[0016] Figure 4 The illustration depicts an example scenario of measuring cross-correlation between samples under an embodiment of this disclosure.

[0017] Figure 5A and 5B The illustration depicts an example scenario and process of data collection during a handover (HO) under an implementation of this disclosure.

[0018] Figure 6A and 6B The illustration depicts an example flow for handling data collection anomalies under an embodiment of this disclosure.

[0019] Figure 7 The diagram illustrates an example communication system implemented according to the present disclosure.

[0020] Figure 8 The flowchart illustrates an example process under an implementation of the present disclosure.

[0021] Figure 9 The flowchart illustrates another example flow under an implementation of this disclosure. Detailed Implementation

[0022] Detailed embodiments and implementations of the subject matter claimed in this application are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the subject matter claimed in this application and may be implemented in various forms. This disclosure may take many different forms and should not be construed as limited to the exemplary embodiments and implementations listed herein. Rather, these exemplary embodiments and implementations are intended to make the description of this disclosure exhaustive and complete, and to fully communicate the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0023] Overview

[0024] According to the implementation of this disclosure, various techniques, methods, schemes, and / or solutions for collecting data across connection states in mobile communications are involved. According to this disclosure, multiple possible solutions can be implemented individually or in combination. That is, although these possible solutions are described separately below, two or more of them can be implemented in one or another combination.

[0025] Figure 1 An example scenario 100 of a communication environment is illustrated, in which various solutions and schemes of this disclosure can be implemented. Scenario 100 involves a user equipment (UE) 110 communicating wirelessly with a wireless network consisting of an access network 125 and a core network (CN) 130. This wireless network can be a 5G NR network, a 5G-Advanced network, a 6G network, but this disclosure is not limited thereto. UE 110 can be a smartphone, wearable device, Internet of Things (IoT) device, tablet, etc. Alternatively, UE 110 can be a laptop (NB) or personal computer (PC) with a data card inserted or installed, the data card containing a modem and a radio frequency (RF) transceiver to provide wireless communication capabilities. CN 130 can include entities such as User Plane Function (UPF), Mobility Management Function (AMF), Session Management Function (SMF), and Unified Data Management (UDM). Access network 125 can include one or more base stations (BS), such as base station 120. Base station 120 can be an evolved Node B (eNB), a next-generation Node B (gNB), or a transceiver point (TRP). Base station 120 can provide communication coverage for a geographically covered area, supporting communication with UE110 within that area.

[0026] Scenario 100 also involves an Operations and Maintenance (OAM) device 140 and a UE server 150. The OAM device 140 may include a set of functions and protocols for managing and maintaining network devices and services. The UE server 150 (also referred to as an OTT server) is introduced for certain applications, such as artificial intelligence (AI), machine learning (ML), or other applications requiring model training. The UE server 150 is responsible for collecting and storing data reported by UEs (e.g., UE 110) and may also have model training capabilities. The UE server 150 can be a UE-side server, belonging to OTT and transparent to 3GPP. Alternatively, the UE server 150 can be a UE-side server, belonging to OTT but not transparent to 3GPP. The deployment of the UE server 150 can be within or outside the OAM domain (e.g., in the CN domain). The UE server 150 can receive and store data or data files and build datasets for model training. The UE server 150 can also use this dataset for model training. Specifically, the UE server 150 organizes the received data into a structured format (i.e., a dataset) that can be used for further analysis or processing. This may involve data cleaning, data transformation, and labeling.

[0027] Figure 2 This is a schematic diagram illustrating an example scenario of cross-connectivity data collection according to an implementation of this disclosure. As shown in scenario 200, a data collection session begins at time T2 and ends at time T10, spanning, for example, three connectivity states. More specifically, UE 110 can switch from a non-connectivity state (e.g., INACTIVE / IDLE state or Radio Resource Control (RRC) INACTIVE / IDLE state) to a connectivity state (e.g., RRC CONNECTED state) and establish a connection with base station 120 at time T1 (e.g., an RRC connection). For example, UE 110 can establish an RRC connection with base station 120 through an RRC connection establishment, RRC connection recovery, or RRC connection reconstruction procedure. Afterward, UE 110 can send a UE capability report 211 to base station 120, indicating its AI / ML-related capabilities. UE 110 can then receive a data collection configuration 215 from base station 120. When one or more collection initiation criteria are met at time T2, UE 110 initiates data collection according to the data collection configuration 215. At time T3, UE 110 releases the connection and switches from the connected state to the INACTIVE / IDLE state. From time T3 to time T4, data collection ceases. However, the data collection configuration 215 used in the previous connection is retained in UE 110.

[0028] In scenario 200, user equipment (UE) 110 re-enters the connected state at time T4. Given that UE 110 may lose Radio Resource Control (RRC) context in the Radio Access Network (RAN) when switching to an inactive / idle state (e.g., due to not being retained or transferred), UE 110 needs to report its current data collection configuration or status upon re-entering the connected state. Therefore, UE 110 sends an indication 221 related to data collection configuration 215 to base station (BS) 120. This indication 221 may include a data collection configuration identifier (ID) and / or the data collection configuration content of data collection configuration 215. Subsequently, UE 110 receives data collection control 225 related to data collection configuration 215 from BS 120. In scenario 200, data collection control 225 contains an acknowledgment (ACK) of the validity of data collection configuration 215. Upon receiving data collection control 225, UE 110 determines that data collection configuration 215 is active and resumes data collection at time T5. That is, the resumed data collection is performed based on data collection configuration 215. When data collection control 225 contains a validity ACK, UE 110 can keep the configuration release timer (e.g., T330) running. In another embodiment, if data collection control 225 contains a first pause message, UE 110 can pause data collection configuration 215. Specifically, UE 110 can retain the original data collection configuration 215 but treat it as inactive. UE 110 can pause the original configuration release timer, or UE 110 can keep the timer running. In yet another embodiment, if data collection control 225 contains a second pause message, UE 110 can pause the reporting configuration specified for data collection configuration 215. Specifically, UE 110 continues to perform data collection according to the measurement configuration defined in data collection configuration 215. However, UE 110 pauses data reporting. In this embodiment, the configuration release timer can continue to run.

[0029] From time point T6 to time point T7, data collection is stopped as UE 110 switches from a connected state to an inactive / idle state. During this period, the active data collection configuration used in the previous connection (i.e., data collection configuration 215) is retained in UE 110. At time point T7, UE 110 switches back to the connected state and sends an instruction 231 related to the retained active data collection configuration to BS 120. Subsequently, data collection control 235 is received. In scenario 200, data collection control 235 contains a reconfiguration message, and UE 110 reconfigures / updates data collection configuration 215 and determines the reconfigured data collection configuration as the active configuration. Data collection resumes at time point T8. As shown in scenario 200, after receiving a data collection deactivation command 247 from BS 120 at time point T9, UE 110 stops data collection at time point T10.

[0030] In scenario 200, instructions 221 and 231, as well as data collection controls 225 and 235, can be carried via Radio Resource Control (RRC) signaling. UE 110 can resume, suspend, or reconfigure its data collection configuration based on the information in the data collection control. Even if UE 110 switches between connected and inactive / idle states multiple times, it can maintain a data collection configuration. That is, as long as a valid ACK is received, UE 110 can maintain this configuration regardless of its state (e.g., idle, inactive, or connected), even if interrupted by state switching.

[0031] In this disclosure, data collection configuration can be carried by at least one RRC message, Media Access Control (MAC)-Control Element (CE) message, and Downlink Control Information (DCI) message. UE 110 can store the collected data in variables or data files. The collected data can also be referred to as measurement log, log, collected data / log, collected data, recorded measurement, measurement log, or recorded measurement information. In scenario 200, UE 110 can report the collected data to BS 120 when reporting conditions are met or a report message is received from BS 120. The collected data can also be further transmitted to UE server 150 via one or a combination of BS 120, Core Network (CN) 120, and Operations and Maintenance Management (OAM) equipment 140. The collected data can be used for various Artificial Intelligence (AI) / Machine Learning (ML) lifecycle management (LCM) purposes, including model training, model inference, and model monitoring, applicable to different use cases or AI / ML enabling features of UE-side, network-side, and dual-side models.

[0032] Figures 3A to 3HThis is a schematic diagram illustrating an exemplary sub-process for collecting AI / ML-related data across connectivity states, according to embodiments of this disclosure. The sub-process may include a UE capability reporting process, an activation data collection configuration control process, a data collection configuration provision process, a data collection process, and a data reporting process.

[0033] See Figure 3A The example illustrates a sub-process 300a of the UE capability reporting flow. It is assumed that UE 110 is initialized to a connected state, therefore no data collection configuration is stored in UE 110 (i.e., UE 110 has no active data collection configuration). In this case, UE 110 can follow and transmit a UE capability report upon receiving a capability query (e.g., UECapabilityEnquiry) from BS 120. BS 120 can 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 the following: memory size, remaining battery power, carrier aggregation (CA) capability, dual connectivity (DC) capability, supported use cases, AI or ML enabling features (e.g., AI-enabled beam management (BM), AI-enabled channel state information (CSI) prediction, AI-enabled location, AI-enabled mobility, etc.), supported data types collected for different AI / ML enabling features (e.g., raw channel data, CSI information, UE location information, UE speed, etc.), and other AI or ML information related to UE capabilities. In one example, the UE capability report can also indicate whether data collection / measurement logging is supported in connected mode. In another example, the UE capability report can provide information on whether non-standardized data types can be collected. In yet another example, the UE capability report can provide CA / DC capability information for different frequency bands and combinations thereof. Based on this information, the network can utilize the UE 110's CA / DC capabilities to collect data and measurement logs at different frequencies.

[0034] See Figure 3BThis illustrates an example sub-flow 300b of the activated data collection configuration control flow. In one embodiment, User Equipment (UE) 110 re-enters the connected state from an inactive / idle state. In this case, the data collection configuration is already stored in UE 110. Based on sub-flow 300a, UE 110 can determine whether to resume, suspend, or reconfigure the previously stored data collection configuration. Specifically, UE 110 sends a data collection configuration indication (e.g., ActiveLogConfigurationIndication) to Base Station (BS) 120 via a Radio Resource Control (RRC) message. In one example, the data collection configuration indication can be sent via a UE Assistance Information message (e.g., UEAssistanceInformation). The data collection configuration indication can include an identifier (ID) of the previously stored data collection configuration, which is assigned by the network. In one example, UE 110 can send the ID of the data collection configuration in a complete message (e.g., RRCSetupComplete, RRCResumeComplete, or RRCReestablishedComplete message) when switching to the connected state. The data collection configuration indication can also include the data collection configuration content configured by UE 110. In another embodiment, UE 110 is initialized to a connected state. Since UE 110 has no active data collection configuration, it can send a data collection configuration indication to BS 120, where the ID indicates that no active data collection configuration is available (e.g., 0 / null / NaN / None).

[0035] After sending a data collection configuration instruction, UE 110 receives data collection control (e.g., ActiveLogConfigurationControl) from BS 120. In one embodiment, if the data collection control includes an ACK confirming the validity of the original data collection configuration, UE 110 retains the original configuration, and the configuration release timer (e.g., T330) continues to run. In one embodiment, if the data collection control includes a reconfiguration message, UE 110 reconfigures / updates the original data collection configuration and restarts the configuration release timer (e.g., T330). In one embodiment, BS 120 decides to suspend the original data collection configuration and includes a corresponding message in the data collection control. Therefore, UE 110 suspends the original data collection configuration. UE 110 may retain the original configuration but consider it ineffective. In one embodiment, the information elements (IEs) in the data collection configuration may include a measurement configuration section and a reporting configuration section. The measurement configuration section contains measurement configurations related to performing data collection, such as measurement quantities and data types for different use cases, and log trigger events, etc. The report configuration section contains information related to the data collected in the report, including report trigger events, data recording session references, and report periodicity. BS 120 can decide to suspend the report configuration of the original data collection configuration and include a corresponding message in the data collection control. Therefore, UE 110 suspends the report configuration of the original data collection configuration. That is, UE 110 considers the report configuration ineffective and stops data reporting. However, UE 110 can consider the measurement configuration effective and continue data collection. The original configuration release timer (e.g., T330) continues to run. In one embodiment, BS 120 decides to suspend the measurement configuration of the data collection configuration and includes a corresponding message in the data collection control. Therefore, UE 110 suspends the measurement configuration of the data collection configuration, considers the measurement configuration ineffective, and only performs data reporting. In one embodiment, UE 110 considers the data collection configuration to be active in the connected state until the configuration release timer (e.g., T330) expires, which is used to control the validity period of the data collection configuration. In one embodiment, UE 110 considers the data collection configuration to be active in the connected state until it receives an explicit suspension / stop of the configuration from BS 120. When UE 110 receives a configuration pause / stop instruction, in one embodiment, UE 110 can pause / stop the original configuration release timer. In another embodiment, UE 110 can keep the configuration release timer running.

[0036] Figure 3C and Figure 3D This demonstrates different example sub-processes corresponding to the data collection configuration provision process. For example... Figure 3CAs shown, the data collection configuration can be provided via bidirectional RRC signaling. Specifically, BS 120 initiates sub-procedure 300c to UE 110 in RRC connection state by sending a bidirectional RRC message (e.g., RRCReconfiguration). UE 110 can store the data collection configuration and send a complete message (e.g., RRCReconfigurationComplete) to BS 120 as feedback. In one embodiment, UE 110 discards the original data collection configuration along with the collected data / recorded measurement information. In another embodiment, UE 110 modifies the data collection configuration and retains the collected data / recorded measurement information according to the previous configuration (if any); furthermore, UE 110 adds a jump or marker to the timestamp to indicate that this is the start of data / recorded measurements collected under the new configuration. In addition, UE 110 can start (or restart) the configuration release timer (e.g., T330) with the timer value set to loggingDuration to control the validity of the configuration.

[0037] Or, such as Figure 3D As shown, data collection configuration can be provided via one-way RRC signaling. Specifically, BS 120 can initiate sub-procedure 300d to UE 110 in RRC connection state by sending a one-way RRC message (e.g., LoggedMeasurementConfiguration). When UE 110 receives such an RRC message, UE 110 discards the current data collection configuration and the collected data / recorded measurement information, stores the received data collection configuration, and starts a configuration release timer (e.g., T330), with the timer value set to, for example, loggingDuration, to control the validity period of the configuration.

[0038] The data collection configuration received by UE 110 via sub-procedure 300c or 300d can be associated with an ID and stored by UE 110 in any state. In one embodiment, this ID is assigned by the network. The data collection configuration is stored in the UE's inactive access stratum (AS) context. When UE 110 switches from an inactive / idle state to a connected state, UE 110 sends the configuration ID so that the network can retrieve the data collection configuration. If the currently serving radio access network (RAN) node (e.g., BS 120) is able to retrieve the UE's inactive AS context, UE 110 restores the inactive AS context along with the data collection configuration. In one embodiment, the reporting tunnel is based on the user plane (UP), and UE 110 can establish or modify a data radio bearer (DRB) to transmit collected data / measurement logs.

[0039] Release operations are supported in both sub-processes 300c and 300d. In one embodiment, the release operation of the user equipment (UE) 110's data collection configuration is achieved by releasing the collected / recorded measurement data or by performing configuration clearing when the configuration release timer (e.g., T330) stops or expires. When the configuration release timer expires, the UE 110 can release the data collection configuration. In one embodiment, the UE 110 discards the data collection configuration along with the collected data / recorded measurement information. In another embodiment, the UE 110 discards the measurement configuration but retains the reporting configuration. In yet another embodiment, after the log configuration release timer expires, the UE 110 retains the collected data / logs and reporting configuration for a specific period of time (e.g., 48 hours) from that moment. In yet another embodiment, the UE 110 retains the reporting configuration as long as the collected data / logs are retained.

[0040] When initiating the release procedure, UE 110 may release the measurement configuration and / or reporting configuration. In one embodiment, UE 110 may initiate the release procedure upon receiving an RRC message to disable the collection / recording of measurement data. In one embodiment, UE 110 may initiate the release procedure by clearing the configuration when it is overwritten or when a persistent timer stops or an expiration condition is met. In one embodiment, UE 110 may initiate the release procedure when switching to another radio access technology (RAT). In one embodiment, UE 110 may initiate the release procedure when in an incorrect public land mobile network (PLMN). In one embodiment, UE 110 may initiate the release procedure upon power-off or deregistration. In these cases, UE 110 may stop the running configuration release timer (e.g., T330). In one embodiment, UE 110 discards the data collection configuration and the collected data / recorded measurement information. In one embodiment, UE 110 discards the measurement configuration but retains the reporting configuration. In one embodiment, UE 110 retains the collected data / logs and reporting configuration for 48 hours from the time the log configuration release timer expires. In one embodiment, UE 110 retains the reporting configuration as long as the collected data / logs are retained.

[0041] In one embodiment, user plane (UP) based data / log reporting is supported. For the configuration release procedure, in one embodiment, UE 110 discards the data collection configuration and the collected data / recorded measurement information. UE 110 releases the data radio bearer (DRB) used to transmit the collected data / measurement logs. In another embodiment, UE 110 discards the measurement configuration but retains the reporting configuration and the collected data / logs. UE 110 suspends the DRB and reports the data / logs upon returning to a normal state (e.g., power-on / PLMN in the PLMN list / registration).

[0042] In this disclosure, the data collection configuration may correspond to one or more different use cases, including measurement quantities, data types, use case-related information, log triggering events, data collection or logging duration, data collection or logging interval, report triggering events, report periodicity, network absolute timestamps, server Internet Protocol (IP) addresses, server identifiers (IDs) (e.g., the IP address / ID of UE server 150, which may be indicated by OAM configuration), data collection or logging references (which may be indicated by OAM configuration), data collection or logging session references (which may be indicated by OAM configuration), log areas, a list of public land mobile networks (PLMNs) for data collection or logging, correlations between measurement samples (e.g., in the frequency, time, or spatial domain), and vendor-specific measurement information (e.g., whether vendor-specific measurements supported by the configuration container are allowed). In one embodiment, the data collection configuration may further specify the use case, AI / ML enabling features, or the gNB / cell / UE configuration conditions to which the data collection session is targeted.

[0043] In one embodiment, configuration associated with vendor-specific measurement information is provided by a configuration container. Therefore, the data / logs collected for vendor-specific measurements can be carried in a reporting container when reported. For example, the configuration container can carry one or more use cases or AI / ML enabling features, a vendor-specific ID, and a specific report format (e.g., Abstract Syntax Markup 1 (ASN.1) or Extensible Markup Language (XML)).

[0044] In one embodiment, the correlation between measurement samples is configured. Specifically, certain measurements can be designated as primary measurements, and secondary measurements should be collected during the sampling of the primary measurements. Several example scenarios for cross-correlation between measurement samples are as follows: Figure 4As shown in the examples, in one example, as shown in scenario 410, the primary measurement is a measurement of the serving cell, and the secondary measurement is a measurement of neighboring cells. That is, the serving cell (e.g., the primary cell) measurement is designated as the primary measurement, while the neighboring cell (e.g., the secondary cell) measurement is designated as the secondary measurement. In another example, as shown in scenario 420, the primary measurement is a measurement of a frequency (e.g., the frequency of the serving cell / primary cell), and the secondary measurement is a measurement of other frequencies. That is, the primary measurement is a measurement of a specific frequency (e.g., the frequency of the serving cell / primary cell), and the secondary measurement is a measurement of other frequencies that are related to the primary measurement objective of the serving cell. In yet another example, as shown in scenario 430, the primary measurement is a measurement of a set of primary beams, and the secondary measurement is a measurement of a set of secondary beams. In yet another example, as shown in scenario 440, the primary measurement is a measurement of a set of primary time slots / subframes / frames / time periods, and the secondary measurement is a measurement of a set of secondary time slots / subframes / frames / time periods. Furthermore, as shown in scenario 450, the correlation between the primary and secondary measurements can be a combination of time / frequency resources between different cells and frequencies. In the example above, the correlation between the primary and secondary measurements is assigned via an ID (e.g., a correlation ID).

[0045] In one embodiment, the configuration for log-triggered events supports periodic measurement triggering, where the log interval is configurable. Parameters in the data collection configuration can specify the periodicity used to store Minimum Drive Test (MDT) measurement results. Alternatively, event-based triggering is supported, where the log interval is configurable and determines the periodic recording of available data. Examples of such events include enabling certain features and measurement-based event layer 1 (L1), where event thresholds, hysteresis, and trigger time are configurable.

[0046] In another embodiment, the configuration of report trigger events supports event-based triggering. Examples of such events include enabling certain functions, measurement-based events L1, A1, A2, A3, A4, A5, A6, D1, or I1, where event thresholds, hysteresis, and trigger times are configurable. The data volume exceeds a configurable threshold. Alternatively, periodic report triggering is supported, where report periodicity, number of reports, etc., are configurable.

[0047] refer to Figure 3E and Figure 3FThese diagrams illustrate example sub-procedures of a cross-connectivity data collection process for artificial intelligence (AI) / machine learning (ML) related data collection. As shown in sub-procedure 300e, the data collection configuration can indicate whether data collection is explicitly started / stopped (e.g., via an indication / flag). That is, the user equipment (UE) 110 can start and stop data collection based on indications from the network. In sub-procedure 300f, data collection is enabled by the network, and the UE 110 can start a data collection timer upon receiving such an indication / flag and stop data collection when the timer expires. Specifically, the data collection timer is set to control the data collection process. The UE 110 starts the data collection timer when data collection is initiated. The UE 110 stops the timer when one or more collection stop criteria are met.

[0048] In this disclosure, UE 110 initiates or resumes data collection in a connected state when one or more collection initiation criteria are met, and stops data collection when one or more collection stop criteria are met or when in an inactive / idle state. In one embodiment, UE 110 performs use case-specific measurements only when the corresponding feature is available, and only for the logging interval where that feature is available. In one embodiment, when a logging area is configured, data collection can be performed as long as UE 110 is within that logging area (e.g., a cell list). In one embodiment, when one or more Public Land Mobile Networks (PLMNs) are configured, UE 110 performs data collection when it is within a PLMN list. In one embodiment, UE 110 collects data and records measurements, and continues data collection / logging according to the data collection configuration until the memory reserved for data collection is full. In this case, UE 110 stops logging, stops the data collection timer, and starts another timer, such as a 48-hour timer. UE 110 retains the collected / recorded data until the timer (e.g., the 48-hour timer) expires.

[0049] UE 110 can store collected data in variables or data files during the data collection process. UE 110 can maintain the data collection configuration and collected data / logs in any state (e.g., idle / inactive / connected state), although state transitions may cause multiple interruptions.

[0050] In this disclosure, collection initiation criteria may include one or a combination of the following: receiving a data collection activation command / message from a network node (e.g., via Radio Resource Control (RRC) MAC-CE or Downlink Control Information (DCI)), enabling a target use case or artificial intelligence (AI) or machine learning (ML) function, moving to a new cell within a configured data collection / logging area, being in an associated public land mobile network (PLMN), having a battery level equal to or higher than a power threshold (e.g., being in a high power state), having good radio conditions (e.g., the T310 timer stops when the Layer 3 (L3) Reference Signal Received Power (RSRP) is equal to or higher than a specific threshold), and the configuration of the base station (BS) 120 or UE 110 matching the data collection target. Collection stop criteria may include one or a combination of the following: receiving a data collection deactivation command / message from a network node (e.g., via RRCMAC-CE or DCI), data collection timer expiration, full memory, disabling the target use case or AI or ML function, being outside the data collection or log area, being outside the associated PLMN, battery power below a threshold (e.g., in a low power state), poor radio conditions (e.g., T310 timer running when L3 RSRP is below a specific threshold), mismatch between the configuration of BS 120 or UE 110 and the data collection target, release of the connection between UE 110 and BS 120, and release of the activated data collection configuration.

[0051] In this disclosure, the collected data may include information relating to one or a combination of the following: use cases, AI or ML enabling features, physical cell identifiers (PCIs) of recorded cells, carrier frequencies, signal quality measurements, reference received power (RSRP), reference received quality (RSRQ), received signal strength indication (RSSI), layer 1 (L1)-RSRP, beam index, device location information, timestamps, channel matrix, channel state information (CSI) feedback, channel impulse response (CIR), power delay characteristics (PDP), performance metrics (e.g., system-level key performance indicators (KPIs) or immediate KPIs such as throughput, prediction accuracy, handover failure (HOF) rate, etc.), vendor-specific measurements in a reporting container, correlations between measurement samples (e.g., correlations between primary and secondary measurement samples, in the form of correlation identifiers (IDs)), device identifiers (IDs), logs of additional information, radio access network (RAN) configuration, cell configuration, and user equipment (UE) status.

[0052] Figure 3G and Figure 3HDifferent example sub-procedures of the cross-connectivity data reporting flow for artificial intelligence (AI) / machine learning (ML) related data collection are illustrated. UE 110 can report collected data to BS 120 upon receiving a report message from base station (BS) 120 or upon fulfilling a pre-configured event. The collected data can be reported via Radio Resource Control (RRC) messages or Data Radio Bearer (DRB). More specifically, UE 110 can establish or modify DRBs based on data collection configuration and assign priorities to DRBs. For example, the DRB used for reporting collected data has a lower priority than other DRBs. As shown in sub-procedure 300g, when BS 120 decides to retrieve data / logs collected by UE 110, it can initiate the UE information flow by sending an RRC message (e.g., UEInformationRequest). Subsequently, UE 110 sends the collected data / logs via another RRC message (e.g., UEInformationResponse). In one embodiment, the transmission of collected data / logs in multiple RRC messages is supported. BS 120 can receive a portion of the total collected data / logs upon each request. To indicate that the collected data / logs are segmented, UE 110 may include a data availability indication in the UEInformationResponse message to convey information about the availability of subsequently collected data / logs. In multiple RRC transmissions used for segmented data / log reporting, a first-in, first-out (FIFO) order is followed. That is, UE 110 may provide the earliest available measurement entry in the earliest message. In one example, each report segment is self-decoding (i.e., interpretable) even if other segments are unavailable. Alternatively, as shown in sub-procedure 300h, UE 110 may check whether the report triggering event configured in BS 120 is met. When at least one report triggering event is met, UE 110 may initiate data / log reporting. For example, when the memory of the collected data / logs is equal to or below a threshold (i.e., low memory), UE 110 may send an availability indication or report the data / logs. In one embodiment, the collected data / logs are transmitted via RRC messages (e.g., MeasurementReport).

[0053] In sub-procedures 300g or 300h, the collected data can be reported via the data radio bearer (DRB). In one example, the DRB is paused by default until a recovery indication / request is received from the base station (BS) 120 before data reporting. The user equipment (UE) 110 then resumes the DRB to report the collected data / logs. In another example, the DRB is resumed by default. The UE 110 can indicate the availability of the collected data / logs via a scheduling request (SR) or buffer status report (BSR) procedure, and upon receiving uplink (UL) authorization from the BS 120, it sends the collected data / logs via a logical channel prioritization (LCP) procedure. In one example, if a report trigger event is configured, the UE 110 indicates the availability of the collected data / logs via an SR / BSR procedure when the event is met (e.g., the amount of stored data / logs exceeds a threshold).

[0054] During normal operation, when the configuration release timer expires, the UE memory is full, or the UE 110 is configured with a new data collection configuration, the UE 110 may discard the old data collection configuration and its collected data / logs. In one embodiment, if the UE 110 is unable to report the collected data (e.g., due to a change in the public land mobile network (PLMN) or the lack of a valid server address), the report is stored. In exceptional circumstances, such as power off / logout / UE in an incorrect PLMN / using a different radio access technology (RAT), the UE 110 may store the report and start another timer (e.g., 48 hours), retaining the collected / recorded data until the timer expires.

[0055] Figure 5A and Figure 5BThis is a schematic diagram illustrating example scenarios and procedures related to data collection during handover (HO) according to embodiments of this disclosure. As shown in scenario 500a, source cell 510 can retrieve collected data / logs by sending a report message or waiting for a pre-configured event to be satisfied. After the HO is completed, target cell 520 can retrieve the collected data / logs. More specifically, as shown in procedure 500b, when the network is about to perform an HO for UE 110, source cell 510 will coordinate data collection configuration with target cell 520. The data collection configuration of UE 110 can be propagated during the UE context retrieval process of the HO procedure. After the HO, UE 110 sends a data availability indication to target cell 520 to indicate the availability of previously stored collected data / logs. Target cell 520 can then decide whether to retrieve the remaining data / logs or have UE 110 release them. In one embodiment, data retrieval and reporting can use the UE information procedure. In another embodiment, if DRB is used for data / log reporting, the reporting of collected data / logs can continue via Packet Data Convergence Protocol (PDCP) data recovery or PDCP reconstruction even if the DRB is not released. Otherwise, if the DRB is released by target cell 520, the previously stored collected data / logs are discarded.

[0056] Figure 6A and Figure 6BThis is a schematic diagram illustrating an example flow related to handling abnormal data collection situations according to embodiments of this disclosure. When a handover failure (HOF) or radio link failure (RLF) occurs, UE 110 may trigger a radio resource control (RRC) reconstruction procedure and release the data collection configuration upon initiating the RRC reconstruction procedure. In one embodiment, as shown in procedure 600a, UE 110 discards previously stored collected data / logs upon initiating the RRC reconstruction procedure. In another embodiment, as shown in procedure 600b, UE 110 retains previously stored collected data / logs upon initiating the RRC reconstruction procedure. When UE 110 receives an RRC reconstruction or establishment message (e.g., RRCReestablishment or RRCSetup), UE 110 sends a data availability indication to BS 120 to indicate the availability of the collected data / logs. The data availability indication may be sent in an RRC reconstruction complete or establishment complete message (e.g., RRCReestablishmentComplete or RRCSetupComplete). Then, BS 120 can decide whether to retrieve the remaining data / logs.

[0057] Exemplary Implementation

[0058] Figure 7 An example communication system 700 according to an embodiment of this disclosure is illustrated, comprising at least one example communication device 710 and one example network device 720. The communication device 710 and the network device 720 are capable of performing various functions to implement the schemes, techniques, processes and methods related to data collection across connection states in mobile communications described herein, including the scenarios / schemes described above and processes 800 and 900 described below.

[0059] The communication device 710 may be part of an electronic device, which may be a user interface (UE), such as a portable or mobile device, wearable device, wireless communication device, or computing device. For example, the communication device 710 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, tablet, laptop, or other computing device. The communication device 710 may also be part of a machine-type device, such as an Internet of Things (IoT), narrowband Internet of Things (NB-IoT), or industrial Internet of Things (IIoT) device, such as a non-movable or fixed device, home device, wired communication device, or computing device. For example, the communication device 710 may be implemented in a smart thermostat, smart refrigerator, smart door lock, wireless speaker, or home control center. Alternatively, the communication device 710 may be implemented in the form of one or more integrated circuit (IC) chips, such as, but not limited to, 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. The communication device 710 may include... Figure 7 The communication device 710 may include at least some of the components shown, such as processor 712. It may also include one or more other components unrelated to this disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, these components of the communication device 710 are not included in this disclosure. Figure 7 This is shown in the text and not described below, for the sake of simplicity and conciseness.

[0060] Network device 720 may be part of a network device, which may be a network node such as a satellite, base station, cell, router, or gateway. For example, network device 720 may be implemented in an eNB in ​​an LTE network, a gNB in ​​a 5G / New Radio (NR) network, an IoT, NB-IoT, or IIoT network, or a satellite or base station in a 6G network. Network device 720 may include... Figure 7 The diagram shows at least some components, such as processor 722. Processor 722 may also include a protocol stack and a set of control function modules and circuitry. Network device 720 may also include one or more other components unrelated to the present disclosure (e.g., internal power supply, display device, and / or user interface device); therefore, these components of network device 720 are not included in this disclosure. Figure 7This is shown in the text and not described below, for the sake of simplicity and conciseness.

[0061] In one aspect, each processor 712 and processor 722 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more Complex Instruction Set Computer (CISC) processors. That is, although the singular term "processor" is used herein to refer to processor 712 and processor 722, each processor 712 and processor 722 may comprise multiple processors in some embodiments and a single processor in other embodiments, according to this disclosure. In another aspect, each processor 712 and processor 722 may be implemented in hardware (and optionally firmware) and include electronic components, such as, but not limited to, 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 transformers, which are configured and arranged to achieve a particular purpose according to this disclosure. In other words, in at least some embodiments, each processor 712 and processor 722 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks in a device (e.g., represented by communication device 710) and a network (e.g., represented by network device 720), consistent with various embodiments of this disclosure.

[0062] In some embodiments, the communication device 710 may further include a memory 714 coupled to the processor 712, the memory being accessible to the processor 712 and storing data therein. In some embodiments, the communication device 710 may further include a transceiver 716 coupled to the processor 712, the transceiver being capable of wirelessly transmitting and receiving data.

[0063] In some embodiments, network device 720 may further include a memory 724 coupled to processor 722, which can be accessed by processor 722 and stores data therein, and a transceiver 726 coupled to processor 722, which is capable of wirelessly transmitting and receiving data. Therefore, communication device 710 and network device 720 can communicate wirelessly via transceiver 716 and transceiver 726, respectively.

[0064] For illustrative purposes only and without limitation, the capabilities of communication device 710 and network device 720 are described below, in conjunction with procedures 800 and 900. In these procedures, communication device 710 is implemented as a communication device or user equipment (UE), and network device 720 is implemented as a network node of a communication network (e.g., a base station).

[0065] Explanatory process

[0066] Figure 8An example flow 800 according to an embodiment of this disclosure is illustrated. Flow 800 may be an example implementation of the scenario / solution described above, whether in part or in whole, involving data collection across connection states in mobile communications. Flow 800 may represent one aspect of the functional implementation of communication device 710. Flow 800 may include one or more operations, actions, or functions, as shown in one or more modules 810, 820, 830, 840, and 850. Although shown as discrete modules, the individual modules of flow 800 may be divided into more modules, merged into fewer modules, or omitted depending on the desired implementation. Furthermore, the modules of flow 800 may be arranged according to... Figure 8 The process can be executed in the order shown, or in a different order. Process 800 can be implemented by communication device 710 or any suitable user equipment (e.g., UE 110) or machine-type device. For illustrative purposes only and without limitation, process 800 is described below in the context of communication device 710 as a UE. Process 800 may begin with module 810.

[0067] In module 810, process 800 may involve the processor 712 of communication device 710 sending, via transceiver 716, instructions related to data collection configuration to a network node (e.g., network device 720) when communication device 710 switches to a connected state. Process 800 can proceed from module 810 to module 820.

[0068] In module 820, process 800 may involve processor 712 receiving data collection control related to data collection configuration from a network node via transceiver 716. Process 800 can then transition from module 820 to module 830.

[0069] In module 830, process 800 may involve processor 712 determining the active data collection configuration based on data collection control. Process 800 can then proceed from module 830 to module 840.

[0070] In module 840, process 800 may involve processor 712 performing data collection-related artificial intelligence (AI) or machine learning (ML) based on an activated data collection configuration. Process 800 can proceed from module 840 to module 850.

[0071] In module 850, process 800 may involve processor 712 reporting the collected data to network nodes when reporting conditions are met.

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

[0073] In some implementations, at least one indication and data collection control associated with the data collection configuration is carried via Radio Resource Control (RRC) signaling.

[0074] In some implementations, process 800 may involve processor 712 determining the data collection configuration as the active data collection configuration when the data collection control includes a validity verification of the data collection configuration. Furthermore, process 800 may involve processor 712 determining the reconfigured data collection configuration as the active data collection configuration when the data collection control includes a reconfiguration message.

[0075] In some implementations, process 800 may involve processor 712 suspending the data collection configuration when the data collection control includes a first pause message.

[0076] In some implementations, process 800 may involve processor 712 suspending the reporting configuration specified for the data collection configuration when the data collection control contains a second pause message.

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

[0078] In some implementations, when the release process is initiated, at least one measurement configuration and reporting configuration specified for the active data collection configuration are released.

[0079] In some implementations, the release process is initiated upon meeting at least one initiation condition. This initiation condition may include the active data collection configuration being overwritten, configuration clearing being performed when a persistent timer stops or expires, switching to another radio access technology (RAT), being in an incorrect Public Land Mobile Network (PLMN) list, powering off, or deregistering.

[0080] In some implementations, the activated data collection configuration is released when the Radio Resource Control (RRC) re-establishment process is initiated.

[0081] In some implementations, process 800 may also involve processor 712 discarding previously collected data stored in communication device 710 when initiating the RRC reconstruction process.

[0082] In some implementations, process 800 may also involve processor 712 sending a data availability indication to a network node via transceiver 716 during the RRC rebuild process.

[0083] In some implementations, process 800 may involve processor 712 initiating data collection when one or more collection initiation criteria are met.

[0084] In some implementations, process 800 may involve processor 712 stopping data collection when one or more collection stop criteria are met.

[0085] In some implementations, process 800 may involve processor 712 storing the collected data in variables or data files.

[0086] In some implementations, collection initiation criteria may include one or a combination of the following: receiving a data collection activation command from a network node, enabling a target use case or artificial intelligence (AI) or machine learning (ML) function, moving to a new cell, being in an associated public terrestrial mobile network (PLMN), having a battery level equal to or higher than a threshold, having a first specific radio condition, and the configuration of the network node or communication device 710 matching the data collection target.

[0087] In some implementations, collection stop criteria may include one or a combination of the following: receiving a data collection deactivation command from a network node, data collection timer expiration, full memory, disabling the target use case or artificial intelligence (AI) or machine learning (ML) function, being outside a data collection or log area, being outside an associated public land mobile network (PLMN), battery power below a threshold, having a second specific radio condition, the configuration of the network node or communication device 710 not matching the data collection target, the connection between the communication device 710 and the network node being released, and the activated data collection configuration being released.

[0088] In some implementations, when the communication device 710 switches from a connected state to a disconnected state, at least one active data collection configuration and the collected data previously stored in the communication device 710 are retained.

[0089] In some implementations, reporting conditions are met by receiving a report message from a network node or by satisfying a pre-configured event.

[0090] In some implementations, the collected data is reported to network nodes via Radio Resource Control (RRC) signaling or Data Radio Bearer (DRB).

[0091] In some implementations, the collected data is reported to the network node via a Data Radio Bearer (DRB), and the DRB is paused by default, receiving a resumption request from the network node before the collected data is reported via the DRB.

[0092] In some implementations, the collected data is reported to the network node via a Data Radio Bearer (DRB), and the DRB is restored by default. The communication device 710 sends a data availability indication via a Scheduling Request (SR) or Buffer Status Report (BSR).

[0093] In some implementations, at least one data collection configuration and the activated data collection configuration correspond to one or more measurements, data types, use case related information, log triggering events, data collection or logging duration, data collection or logging interval, report triggering events, report periodicity, network absolute timestamps, server Internet Protocol (IP) addresses, server identifiers (IDs), data collection or logging references, data collection or logging session references, log areas, data collection or logging Public Land Mobile Network (PLMN) lists, correlations between measurement samples, and vendor-specific measurement information.

[0094] In some implementations, the collected data may include information related to one or more use cases, artificial intelligence (AI) / machine learning (ML) enabling features, physical cell identifiers (PCI) of recorded cells, carrier frequencies, signal quality measurements, reference received power (RSRP), reference received quality (RSRQ), received signal strength indication (RSSI), layer 1 (L1)-RSRP, beam index, location information of communication device 710, timestamps, channel matrix, channel state information (CSI) feedback, channel impulse response (CIR), power delay characteristics (PDP), performance metrics, vendor-specific measurements in a report container, correlations between measurement samples, device identifiers (IDs), logs of additional information, radio access network (RAN) configuration, cell configuration, and user equipment (UE) status.

[0095] In some implementations, process 800 may further include processor 712 sending a data availability indication to the target cell via transceiver 716 when a handover (HO) associated with the target cell is completed.

[0096] Figure 9 An example flow 900 according to an embodiment of this disclosure is illustrated. Flow 900 may be part or all of the example embodiments of the above-described scenario / scheme, for data collection across connection states in mobile communications. Flow 900 may represent a functional implementation of network device 720. Flow 900 may include one or more operations, actions, or functions as shown in blocks 910, 920, and 930. Although shown as discrete blocks, the blocks of flow 900 may be divided into more blocks, merged into fewer blocks, or omitted, depending on the desired implementation. Furthermore, the blocks of flow 900 may be arranged according to... Figure 9 The process can be executed in the order shown, or in a different order. Process 900 can be implemented by network device 720 or any base station (e.g., base station 120) or network node. For illustrative purposes only and without limitation, process 900 is described below in the context of network device 720. Process 900 may begin at block 910.

[0097] In block 910, process 900 may include the processor 722 of network device 720 receiving, via transceiver 726, instructions related to data collection configuration for artificial intelligence (AI) / machine learning (ML) related to data collection from user equipment (UE) (e.g., communication device 710). Process 900 may proceed from block 910 to block 920.

[0098] In block 920, process 900 may include processor 722 sending data collection control related to data collection configuration to user equipment via transceiver 726. Process 900 may proceed from block 920 to block 930.

[0099] In block 930, process 800 may include processor 712 receiving data collected by user equipment via transceiver 726. This data is collected based on an active data collection configuration determined according to data collection control.

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

[0101] In some implementations, data collection control may include validation of the validity of the data collection configuration, reconfiguration messages for the data collection configuration, pause messages for the data collection configuration, or pause messages for the reported configuration.

[0102] Additional notes

[0103] The topics described herein sometimes demonstrate that different components are contained within or connected to other different components. It should be understood that the architectures shown are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to achieve a specific function can be considered “associated with each other” to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered “operationally connected” or “operationally coupled” to achieve the desired function, and any two components that can be so associated can also be considered “operationally coupled” to achieve the desired function. Specific examples of operational coupling include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive components.

[0104] Furthermore, regarding the use of almost all plural and / or singular terms in this document, those skilled in the art can convert from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly listed herein.

[0105] Furthermore, those skilled in the art will understand that terms commonly used herein, particularly in appended claims, such as the body portion of appended claims, are generally considered "open-ended" terms. For example, "comprising" should be interpreted as "including but not limited to," "having" should be interpreted as "having at least," and "includes" should be interpreted as "including but not limited to," etc. Those skilled in the art will also further understand that if the specific number of introduced claim elements is expressly stated in the claim, then that intention is explicitly stated in the claim; if such a statement is not made, then this intention does not exist. For example, for ease of understanding, the appended claims below may contain the use of the introductory phrases "at least one" and "one or more" to introduce claim elements. However, the use of such phrases should not be construed as limiting any particular claim containing that claim element to containing only one of that element when introduced by the indefinite article "a" or "an," even if the same claim contains both the introductory phrase "one or more" or "at least one" and the indefinite article such as "a" or "an," for example, "a" and / or "an" should be interpreted as "at least one" or "one or more"; similarly, definite articles also apply when used to introduce claim elements. Furthermore, even if the claims explicitly specify the number of introduced elements, those skilled in the art will recognize that such a statement should be interpreted as at least the number stated. For example, stating "two elements" alone, without further modification, implies at least two elements, or two or more elements. Additionally, in cases employing conventions such as "at least one A, B, and C," such structures should generally be interpreted in the manner understood by those skilled in the art. For example, "a system having at least one A, B, and C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. Similarly, in cases employing conventions such as "at least one A, B, or C," such structures should generally be interpreted in the manner understood by those skilled in the art. For example, "a system having at least one A, B, or C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. Those skilled in the art will further understand that virtually any separate words and / or phrases appearing in the specification, claims, or drawings, when presenting two or more alternative terms, should be understood to include the possibility of including one term, any two terms, or all terms. For example, the phrase "A or B" should be understood to include the possibility of including "A", including "B", or including both "A" and "B".

[0106] As can be seen from the foregoing, various embodiments of this disclosure have been described for illustrative purposes, and various modifications can be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are defined by the following claims.

Claims

1. A method comprising: When the device switches to a connected state, the device's processor sends instructions related to data collection configuration to the network node; The processor receives data collection control related to the data collection configuration from the network node; The processor determines the active data collection configuration based on the data collection control. Based on the activated data collection configuration, the processor performs artificial intelligence (AI) or machine learning (ML) related to data collection. as well as The processor reports the collected data to the network node when the reporting conditions are met.

2. The method of claim 1, wherein the indication associated with the data collection configuration includes a data collection configuration identifier ID or data collection configuration content.

3. The method of claim 1, wherein at least one of the indication and the data collection control associated with the data collection configuration is transmitted via Radio Resource Control (RRC) signaling bearer.

4. The method of claim 1, wherein determining the activated data collection configuration according to the data collection control further comprises: When the data collection control includes a validity check of the data collection configuration, the data collection configuration is determined to be the active data collection configuration; as well as When the data collection control contains a reconfiguration message, the reconfigured data collection configuration is determined as the active data collection configuration.

5. The method of claim 1, further comprising: When the data collection control contains a first pause message, the processor pauses the data collection configuration; or When the data collection control contains a second pause message, the processor pauses the reporting configuration specified for the data collection configuration.

6. The method of claim 1, wherein: The activated data collection configuration is released based on the configuration release timer. When the release process is initiated, at least one of the measurement configuration and reporting configuration specified for the activated data collection configuration is released; or Release the activated data collection configuration when starting the RRC rebuild process.

7. The method of claim 6, wherein the release process is initiated when at least one initiation condition is met, wherein the initiation condition includes: The activated data collection configuration was overridden; Perform configuration clearing when the persistent timer stops or the expiration condition is met; Switch to another radio access technology, RAT; It is in the wrong list of Public Land Mobile Networks (PLMNs). Power off; or Cancel.

8. The method of claim 6, further comprising: When the RRC reconstruction process is initiated, the processor discards the collected data previously stored in the device; or During the RRC reconstruction process, the processor sends a data availability indication to the network node.

9. The method of claim 1, wherein performing the AI ​​or ML related to the data collection further comprises: Data collection is initiated when one or more collection initiation criteria are met; Data collection is stopped when one or more collection stop criteria are met or when the device switches from the connected state to the disconnected state. or The collected data is stored in a variable or data file.

10. The method of claim 9, wherein the one or more collection initiation criteria include one or a combination of the following: Receive the data collection activation command from the network node; Enable the target use case or AI or ML function; Moved to a new neighborhood; Located within an associated PLMN; The battery level is equal to or higher than the threshold. Having a first specific radio condition; and The configuration of the network node or the device matches the data collection objective.

11. The method of claim 9, wherein the one or more collection stopping criteria include one or a combination of the following: Receive data collection deactivation command from the network node; The data collection timer expired; Memory full; Disable the target use case or AI or ML functionality; Located outside the data collection or log area; Outside of the associated PLMN; Battery level is below the threshold; It has a second specific radio condition; The configuration of the network node or the device does not match the data collection objectives; The connection between the device and the network node is released; as well as The activated data collection configuration is released.

12. The method of claim 9, wherein when the device switches from the connected state to the disconnected state, at least one of the activated data collection configuration and the collected data previously stored in the device is retained.

13. The method of claim 1, wherein the reporting condition is satisfied when a report message is received from the network node or when a pre-configured event is satisfied.

14. The method of claim 1, wherein the collected data is reported to the network node via RRC signaling or a data radio bearer DRB.

15. The method of claim 14, wherein the collected data is reported to the network node via the DRB, and: The DRB is paused by default, and a recovery request is received from the network node before the collected data is reported through the DRB; or The DRB is restored by default, and the device sends a data availability indication via a Schedule Request (SR) or Buffer Status Report (BSR).

16. 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 the following: measurement quantity, data type, use case related information, log triggering event, data collection or logging duration, data collection or logging interval, report triggering event, report periodicity, network absolute timestamp, server Internet Protocol IP address, server identifier ID, data collection or logging reference, data collection or logging session reference, log area, data collection or logging PLMN list, correlation between measurement samples, and vendor-specific measurement information.

17. The method of claim 1, wherein the collected data includes information corresponding to one or a combination of the following: use cases, AI or ML enabling features, Physical Cell Identifier (PCI) of recorded cells, carrier frequency, signal quality measurements, Reference Received Power (RSRP), Reference Received Quality (RSRQ), Received Signal Strength Indicator (RSSI), Layer 1 RSRP, beam index, device location information, timestamp, channel matrix, Channel State Information (CSI) feedback, Channel Impulse Response (CIR), Power Delay Parameter (PDP), performance metrics, vendor-specific measurements in a report container, correlations between measurement samples, device identifier (ID), logs of additional information, Radio Access Network (RAN) configuration, cell configuration, and information related to User Equipment (UE) status.

18. The method of claim 1, further comprising: When the handover HO associated with the target cell is completed, the processor sends a data availability indication to the target cell.

19. A method comprising: The network node's processor receives instructions from the UE related to data collection configuration, specifically for AI or ML related to data collection. The processor sends data collection control related to the data collection configuration to the UE; as well as The processor receives data collected by the UE, wherein the data is collected based on an active data collection configuration determined according to the data collection control.

20. An apparatus comprising: A transceiver that enables wireless communication during operation; as well as A processor, communicatively coupled to the transceiver, performs the following operations during operation: When the device switches to connected state, it sends instructions related to data collection configuration to the network node via the transceiver; The transceiver receives data collection control related to the data collection configuration from the network node. The activated data collection configuration is determined based on this data collection control. Based on the activated data collection configuration, perform AI or ML related to data collection; and When the reporting conditions are met, the collected data is reported to the network node.

Images