Methods and apparatuses for data collection and reporting in mobile communications

The method and apparatus for data collection and reporting in 6G networks address energy efficiency and data continuity challenges by implementing RAN-controllable QoS management and DRB mapping, ensuring efficient data transmission across various states.

WO2026239232A1PCT designated stage Publication Date: 2026-11-19FAINITY INNOVATION CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/IB2026/054609
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-13
Filing Date
2026-05-09
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing mobile communication systems face challenges in efficiently collecting and reporting data while ensuring energy efficiency and data continuity during user equipment mobility and state transitions, particularly in the context of 6G networks, leading to increased energy consumption and potential disruption of power-saving modes.

Method used

Implementing a method and apparatus for data collection and reporting that involve configuring resource sets, functionalities, and reporting configurations, allowing for efficient data transmission and handling across different RRC states, including RAN-controllable QoS management and DRB mapping to ensure energy efficiency and data continuity.

Benefits of technology

The proposed solution enables energy-efficient data collection and reporting in 6G networks, maintaining data continuity during user equipment mobility and state transitions, thereby optimizing energy consumption and resource utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure IB2026054609_19112026_PF_FP_ABST
    Figure IB2026054609_19112026_PF_FP_ABST
Patent Text Reader

Abstract

Various solutions for data collection and reporting in mobile communications are described. A network node may determine a data collection configuration and transmit the data collection configuration to an apparatus. The data collection configuration may include at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration. The apparatus may receive the data collection configuration from the network node, generate a protocol data unit (PDU) according to the data collection configuration, construct a PDU session according to the at least one functionality configuration, and perform a transmission to report the PDU based on the least one reporting configuration to the network node via the PDU session.
Need to check novelty before this filing date? Find Prior Art

Description

DescriptionTitle of Invention: METHODS AND APPARATUSES FOR DATA COLLECTION AND REPORTING IN MOBILE COMMUNICATIONSCROSS REFERENCE TO RELATED PATENT APPLICATION(S)

[0001] The present disclosure is part of a non-provisional application claiming the priority benefit of U.S. Patent Application No. 63 / 804,793, filed 13 May 2025, the content of which herein being incorporated by reference in its entirety.TECHNICAL FIELD

[0002] The present disclosure is generally related to mobile communications and, more particularly, to data collection and reporting in mobile communications.BACKGROUND

[0003] 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.

[0004] In mobile communications, 6th Generation (6G) technology aims to support societal advancements and bring value to society in the 2030s and beyond in secure, resilient, environmentally sustainable, and economically sustainable ways. In addition to providing diverse and novel 6G services, other considerations are needed, e.g., capital expenditure (CAPEX) / operating expense (OPEX) reduction, improvement of overall 3rdGeneration Partnership Project (3GPP) system performance, and migration from and interworking with 5th Generation (5G) systems. The studies of 6G may include at least: (1) 6G radio for improvement of existing services and for new services; (2) Energy efficiency and energy saving for network and device; (3) Target scalable and forward compatible design for diverse device types; (4) Overall high-level aspects of 5G to 6G migration; (5) Fundamental 6G radio design aspects: waveform, numerology, channel coding, etc.

[0005] In the 6G era, two promising features known in 3GPP and International Telecommunication Union (ITU) as Artificial Intelligence (AI)ZMachine Learning (ML) and integrated sensing and communication (ISAC) are expected to be specified and introduced in 6G day one deployment. To support these two features, user equipment (UE) may be required to, or may be proactively initiated to collect all kinds of “Data” such as detecting and measuring a synchronization signaling block (SSB), a specific reference signal (RS), a specific object, a specific resource, etc. The measurement results may further include calculating the received signal strength indication (RS SI), received signal received power (RSRP), received signal received quality (RSRQ), and / or time difference of arrival (TDOA), subject to a signaling transmitted by a cell or a transmission / reception point (TRP) upon a time / frequency / spatial resource. Thebehavior may be defined as a data collection process for 6G functionality. Herein, 6G functionality may refer to collective nouns denoting applications of AI / ML, ISAC, Self-Organizing Network (SON), and / or Minimum Driving Test (MDT). By collecting data, the UE may report the data (e.g., collection results, collection status, database, training data, and / or inference data) to the network (NW), thereby facilitating the operation of 6G functionality.

[0006] Accordingly, proposing data collection and reporting procedures for a new generation communication system has become a critical issue in wireless communication systems, and there is an urgent need to provide such procedures to ensure efficient and reliable operation.SUMMARY

[0007] 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.

[0008] One objective of the present disclosure is proposing schemes, concepts, designs, systems, methods, and / or apparatus pertaining to data collection and reporting in mobile communications. It is believed that the above -de scribed issue would be avoided or otherwise alleviated by implementing one or more of the proposed schemes described herein.

[0009] In one aspect, a method may involve an apparatus receiving a data collection configuration from a network node, wherein the data collection configuration comprises at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration. The method may also involve the apparatus generating a protocol data unit (PDU) according to the data collection configuration. The method may further involve the apparatus constructing a PDU session according to at least one functionality configuration. The method may further involve the apparatus performing a transmission to report and / or forward the PDU to the network node via the PDU session according to at least one reporting configuration.

[0010] In one aspect, an apparatus may comprise a transceiver that, during operation, wirelessly communicates with a network node. The apparatus may also comprise a processor communicatively coupled to the transceiver. The processor may perform operations comprising receiving, via the transceiver, a data collection configuration from a network node, wherein the data collection configuration comprises at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration. The processor may also perform operations comprising generating a protocol data unit (PDU) according to the data collection configuration. The processor may further perform operations comprising constructing a PDU session according to at least one functionality configuration. The processor may further perform operations comprising performing, via the transceiver, a transmission to forward the PDU according to at least one reporting configuration to the network node via the PDU session.

[0011] In one aspect, a method may involve a network node determining at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration. The method may also involve the network node including at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration in a suspend configuration. The method may further involve the network node transmitting an RRC release message to a user equipment (UE), wherein the RRC release message comprises the suspend configuration.

[0012] In one aspect, a network node may comprise a transceiver which, during operation, wirelessly communicates with an apparatus. The network node may also comprise a processor communicatively coupled to the transceiver. The processor may perform operations comprising determining at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration. The processor may also perform operations comprising including the at least one resource set configuration, the at least one functionality configuration, and the at least one reporting configuration in a suspend configuration. The processor may further perform operations comprising transmitting, via the transceiver, an RRC release message to a UE, wherein the RRC release message comprises the suspend configuration.

[0013] It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, 5G, New Radio (NR), Intemet-of-Things (loT) and Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), beyond 5G (B5G), and 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

[0014] 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.

[0015] FIG. 1 is a diagram depicting an example scenario of a communication environment in which various solutions and schemes in accordance with the present disclosure may be implemented.

[0016] FIG. 2 is a diagram depicting an example scenario of data radio bearer (DRB) assignment in accordance with an implementation of the present disclosure.

[0017] FIG. 3 is a diagram depicting an example scenario of data collection configuration in accordance with an implementation of the present disclosure.

[0018] FIG. 4 is a diagram depicting an example scenario of data collection and reporting procedure in accordance with an implementation of the present disclosure.

[0019] FIG. 5 is a block diagram of an example communication system in accordance with an implementation of the present disclosure.

[0020] FIG. 6 is a flowchart of an example process in accordance with an implementation of the present disclosure.

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

[0022] 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

[0023] Implementations in accordance with the present disclosure relate to various techniques, methods, schemes, and / or solutions pertaining to data collection and reporting 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.

[0024] In a telecommunication system, the UE may perform downlink (DL) signaling measurements and report them over the uplink (UL) channel for data collection and reporting purposes. It is inevitable that the UE may face energy-consumption challenges when performing the data collection and reporting. The UE may not be able to power off its baseband / RF transceiver in an event that the data collection or reporting process is ongoing. In some cases, the UE may prolong the required reporting interval or increase the total transmission power in a case that a size of the collected data is extremely large. These may break out the requirements for the UEto stay in a power-saving mode. In addition, as the NW (e.g., abase station, a cell, or a TRP) schedules available resources for reporting, the UE may be required to perform Random Access (RA) for UL synchronization, to initiate a scheduling request (SR), or to reply buffer status report (BSR). In addition, UE identification associated with the procedures may incur significant overhead. All these aspects may significantly increase UE energy consumption and may not meet the energy-efficiency requirements of the 6G system.

[0025] On the other hand, UE mobility and state transition may also be taken into account. Data continuity is one of the requirements for 6G functionalities to operate appropriately. The UE may be able to continuously perform data collection and reporting regardless of changes to the camped or serving cell.The UE may be released to an idle state or inactive state or transitioned to a connected state during data collection or reporting. The present disclosure discloses whether an ongoing data collection process during the state transition should be stopped or continued, and the corresponding reporting that may be triggered or sustained during / after state transitions. Accordingly, various embodiments of the present disclosure describe how to perform energy -efficient data collection and reporting for 6G functionality operation while ensuring data continuity during UE mobility and RRC transitions.

[0026] In the present disclosure, the RAN (e.g., a base station (BS), a cell, or the TRP), the UE, or both may analyze and / or determine certain items or features for use in a reporting mechanism. The items or features may include one or more of reporting payload size, reporting container, applied quality of service (QoS) flow, e.g., reporting latency, reporting identification, reporting type, reporting state, reporting buffer management, reporting procedures, reporting resource, and transmission power.

[0027] In some implementations, the RAN, the UE, or both may evaluate and / or determine that the reporting payload size is variable (e.g., from 10 KB to 100 MBs). In some implementations, the RAN, the UE, or both may evaluate and / or determine that the reporting latency is variable (e.g., from 10 ms to hours). The determination may facilitate the grant of resources associated with relevant QoS.

[0028] In some implementations, the RAN, the UE, or both may evaluate and / or determine the reporting container and applied QoS flow. A radio bearer and reflective QoS management and mapping may be applied for the reporting payload. In some implementations, the container candidate may include User Plane (UP) Data Radio Bearer (DRB), Control Plane (CP) Signaling Radio Bearer (SRB), control signaling such as an RRC message, or a new bearer or a new plane.

[0029] In some implementations, the RAN, the UE, or both may identify the reporting functionality (e.g., AI / ML and / or ISAC and / or SON and / or MDT) and determine which ID to append to the reporting payload to represent the linkage between collection and reporting.

[0030] In some implementations, the RAN, the UE, or both may determine that the reporting is periodic, semi-persistent, aperiodic, or one-shot (on-demand) for the corresponding functionality and the associated setting (e.g., periodicity, trigger conditions for aperiodic) to guarantee the reporting performance (i.e., determine the reporting type).

[0031] In some implementations, the UE may be able to perform reporting in different RRC states, regardless of whether data collection is performed in the RRC Connected, idle, or inactive state. The present disclosure further discloses mechanisms for accomplishing the reporting, retransmission, and acknowledgment of successful reporting.

[0032] In some implementations, the RAN, the UE, or both may handle the situation and respond with reporting behavior (i.e., reporting buffer management). In one example, the reporting buffer may be retained or discarded after reporting. Whether to flush or reset the buffer across different UE mobility / RRC states is also disclosed herein.

[0033] While initiating reporting, the UE may perform RA, SR, or BSR, which are scheduled with a dynamic grant (DG) or configured with a configured grant (CG). These procedures may increase latency and degrade energy efficiency in conventional wireless systems. In some implementations, varioussolutions of the present disclosure are disclosed to improve it during data collection and reporting procedures, especially for an inactive UE. In addition, the present disclosure may determine which channel (e.g., physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH)) is used for transmission during the reporting procedure.

[0034] In some implementations, the RAN, the UE, or both may apply a modulation and coding scheme (MCS) (i.e., to allocate appropriate resources and transmission power) to shorten the necessary transmission time and power during the reporting procedure.

[0035] It is noted that reporting aspects are configurable by the RAN (e.g., the BS, the cell, or the TRP) via at least one configuration, wherein the configuration may relate to characteristics of functionality (e.g., Al, ML, ISAC, SON, or MDT functionality) and data collection requirements. Reconfiguration may be required if either the RAN (e.g., the BS, the cell, or the TRP) or the UE may need to update the reporting settings. The reporting configuration may be included in an RRC release message and applied to the idle / inactive state. While the UE is in the idle / inactive state, the RAN (e.g., the BS, the cell, or the TRP) may not be able to know the UE condition. In addition, the previous report configuration setting may not be accurate. Accordingly, the present disclosure aims to support efficient data collection and reporting even when the UE is in the idle / inactive state.

[0036] 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 UE 110 in wireless communication with an access network 120 (e.g., a wireless network including a non-terrestrial network (NTN) and a TN) via at least a terrestrial network node 122 (e.g., a BS such as an evolved node B (eNB), a next generation node B (gNB), or a 6G network node, a cell, or a TRP) and / or at least a non-terrestrial network node 124 (e.g., a satellite), the access network 120, and a core network (CN) 130 wired or wirelessly connected to the access network 120. In some implementations, the terrestrial network node 122 may form a TN serving cell for wireless communication with the UE 110, or the terrestrial network node 122 and the non-terrestrial network node 124 may form an NTN serving cell for wireless communication with the UE 110. In some implementations, the access network 120 may be a radio access network (RAN) (e.g., 4G / 5G / B5G / 6G network), and the UE 110 may be a phone, a computer, an loT device, an Fixed Wireless Access (FWA) device an edge apparatus / device, or a sensing apparatus inserted or installed with a hardware module that includes a modem and radio frequency (RF) transceiver(s) to provide wireless communication functionality. In some examples, the UE 110 may be a smartphone, an edge computing device, a camera, a radar, a tablet computer, a laptop computer, or a notebook computer, etc. In some implementations, the UE 110 may be independent of the access network 120. In other implementations, the UE 110 may be part of the access network 120. In some implementations, the UE 110, the terrestrial network node 122, and / or the non-terrestrial network node 124 may be equipped with a sensing module that includes a signal processor and RF detector(s) to provide wireless sensing functionality (e.g., an ISAC functionality). In some implementations, the UE 110, the terrestrial network node 122, and / or the non-terrestrial network node 124 may be equipped with an Al-enabled processor that includes at least one integrated neural processing unit (NPU) to provide Al and / or ML functionality. Alternatively,the access network 120 may be an IoT / NB-IoT / IIoT network, and the UE 110 may be an loT device such as an NB-IoT UE, an NB-IoT NTN UE, or an enhanced machine-type communication (eMTC) UE (e.g., a bandwidth reduced low complexity (BL) UE or a coverage enhancement (CE) UE) or a Reduced Capability (RedCap) UE. In one embodiment, the access network 120 is connected to the core network 130 via a Next-Generation (NG) interface. The core network 130 may include entities such as an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a sensing management function, a data collection management function, and a user plane function (UPF). In such a communication environment, the UE 110, the access network 120, the terrestrial network node 122, and / or the non-terrestrial network node 124 may implement various schemes pertaining to data collection and reporting in mobile communications in accordance with the present disclosure, as described below. It is noteworthy that, while the various proposed schemes may be individually or separately described below, in actual implementations, some or all of the proposed schemes may be utilized or otherwise implemented jointly. Of course, each of the proposed schemes may be utilized or otherwise implemented individually or separately.

[0037] In the present disclosure, a RAN -controllable QoS for data collection and reporting is implemented for the RAN (e.g., the BS or the TRP) and the UE.

[0038] The data collection may be initiated by the RAN (e.g., the BS or the TRP) or the UE, wherein the data format, data payload size, data latency, and other QoS performance metrics may be highly related to the resource set and its collection configuration (e.g., the measurement subject to the resource source). Additionally, the reporting of collection results may be difficult to categorize with a static QoS flow with a fixed QoS Flow Identifier (QFI). On the other hand, the core network may not be able to configure the QFI appropriately, especially regarding the use of data collection, which is oriented toward the RAN (e.g., the BS or the TRP) and / or the UE and is transparent to the CN.

[0039] Although the data collection may be oriented from the RAN (e.g., the BS or the TRP) and / or the UE, which is transparent to the CN, in some embodiments, the CN may predefine one or more reflective QoS rule(s) (i.e., one or more QFI(s)) for data collection and reporting related to different functionalities. Based on the reflective QoS rule (or the QFIs) predefined by the CN for data collection and reporting related to different functionalities, the RAN (e.g., the BS or the TRP) may determine the reflective QoS rule (or QFI) for data collection and reporting (both linked with the same functionality) and map the functionality to a specific DRB. In some embodiments, the CN may predefine one or more reflective QoS rules (or one or more QFIs) for different conditions (e.g., data format, data payload size, data latency, QoS performance metric, RRC states, etc.). Based on these predefined reflective QoS rules (or QFIs), the RAN (e.g., the BS or the TRP) may determine which reflective QoS rule (or QFI) to use for data collection and reporting and map the functionality to a corresponding DRB.

[0040] It is noted that the criterion for the RAN (e.g., the BS or the TRP) to determine the reflective QoS rule (or the QFI) may be based on the conditions (e.g., data format, data payload size, data latency, QoS performance metric, RRC states, etc.) of data collection and reporting. In some embodiments, the CN may predefine a reflective QoS rule (or a QFI) for data collection and reporting associated with anyfunctionalities. Then the RAN (e.g., the BS or the TRP) may configure a specific DRB based on the predefined reflective QoS rule (or the QFI), and any PDU generated for the data collection and reporting process may be mapped to the specific DRB.

[0041] In some embodiments, the reflective QoS rule for data collection and reporting is predefined, and the RAN (e.g., the BS or the TRP) may determine to apply the reflective QoS rule or ignore the reflective QoS rule based on NW-side additional conditions. In one example, the RAN (e.g., the BS or the TRP) may provide the CN with additional NW-side conditions (e.g., an association ID) concurrently before negotiating the predefined reflective QoS rule with the CN. Once the association ID changes, the predefined reflective QoS rule may not be applicable. If the RAN (e.g., the BS or the TRP) ignores the predefined reflective QoS rule from the CN, it means the RAN (e.g., the BS or the TRP) determines the corresponding QFI or assigns DRBs for the PDU sessions used for data collection and reporting. In some embodiments, the NW-side additional conditions may refer to a NW-side status (which may comprise hardware, software, network deployment, and other factors on the NW-side) such that training data with the same NW-side additional conditions yields the same output (Al inference). If the NW-side additional condition changes, even with the same input, the Al inference module may produce a different output.

[0042] In the present disclosure, multiple default DRBs may be used for data collection and reporting. In some embodiments, for Al, ML, ISAC, SON, or MDT data collection and reporting, if no specific QFI is provided and mapped to a DRB, the PDU generated from the data collection may be mapped to a default data DRB, which is different from a data DRB. In comparison, in legacy, a default DRB is mapped for any PDU if there is no rule to map the packet onto a specific DRB.

[0043] In one embodiment of RAN-controllable QoS management, the RAN (e.g., the BS or the TRP) may configure a separate default DRB (i.e., the default data DRB). Any PDU generated for the data collection and reporting process may be mapped to the default data DRB if there is no reflective QoS rule to map the PDU generated for data collection and reporting to a specific DRB. The default data DRB may be mapped to a different logic channel (LCH) from the default DRB. It implies that the PDU may be managed separately by the corresponding logical channel prioritization (LCP) from other PDUs mapped to the default DRB. In one embodiment, the PDU generated for data collection and reporting may prioritize or deprioritize with the PDUs mapped into the legacy default DRB, and the UE shall perform multiplexing these PDUs upon transmission based on the associated priority.

[0044] In some embodiments, the RAN (e.g., the BS or the TRP) may configure a reflective QoS rule for data collection and reporting (both linked with the same functionality) and designate a specific DRB for the mapping. An end-marker control PDU may be constructed once a new PDU session with a reflective QoS flow to DRB Identifier (RDI) set to “1” is received, and the corresponding PDU in the PDU session may not be mapped to the default data DRB.

[0045] In some embodiments, the reflective QoS rule for the data collection and reporting may be bilateral (e.g., only valid for UE PDU (during the reporting behavior)). Specifically, a “bilateral” reflective QoS rule implies different QFI may be applied for DL PDU sessions or UL PDU sessions, even though these sessions are associated with the same functionality. Accordingly, the DL PDU and the UL PDU maybe mapped into different DRBs. To support the “biteral” QoS rule, the RAN (e.g., the BS or the TRP) may use one bit to label the configuration that is applied for “DL” or “UL”. If the one-bit indicator is absent, then the UE may interpret that the rule is applied for both DL and UL.

[0046] Lor conventional services or applications, the QoS may be marked or labeled by the CN, and the PDUs may be mapped into a default DRB (if there is no associated reflective QoS rule) or a specific DRB (if there is a stored reflective QoS rule).

[0047] In some implementations of the present disclosure, the PDUs generated for data collection and reporting may be divided into different functionalities (e.g., Al function#!, Al fiinction#2, ML function#!, ML fiinction#2, ISAC function#!, ISAC fiinction#2, etc), wherein different functions or functionalities may be associated with a corresponding functionality configuration (and the functionality configuration may be part of data collection configuration). In some embodiments, the RAN (e.g., the BS or the TRP) may assign a QLI value as part of the functionality configuration. Then the UE may map the PDU generated for data collection and report under the associated functionality into a specific DRB (i.e., no reflective QoS rule) in a case that the QLI provision is received. In contrast, the UE may not map the PDU generated for data collection and reporting under the associated functionality into a specific DRB (i.e., no reflective QoS rule) in a case that the QLI provision is absent.

[0048] In some embodiments, one indicator (one bit) may be additionally configured as part of the functionality configuration when the QLI provision is absent. In one embodiment, the PDU may be mapped to the default data DRB if the bit is set to “1” (or the field corresponding to the indicator set to “default data DRB”); otherwise, the PDU may be mapped to the default DRB.

[0049] In some embodiments, a specific QLI value is configured, and the UE may interpret that the corresponding PDU is mapped to the default data DRB; otherwise (i.e., if the QLI value is absent), the PDU is mapped to the default DRB as legacy behavior.

[0050] In some embodiments, the indicator is provided that is common to the functionalities. In one embodiment, if the indicator is set to a first value (e.g., 0), the PDUs associated with functionalities without QLI may be mapped to the default DRB; if the indicator is set to a second value (e.g., 1), the PDUs associated with the functionalities without QLI may be mapped to the default data DRB.

[0051] In some embodiments, the RAN (e.g., the BS or the TRP) may add the new assigned QLIs into one or more specific DRBs through reconfiguring the DRB configuration. With the update, the UE may obtain the reflective QoS rule and the mapped DRBs during the reporting. In other embodiments, on the contrary, if the QFI value is assigned in functionality configuration but no corresponding DRB reconfiguration, the UE may map the PDU generated for data collection and reporting to a default data DRB or map the PDU generated for data collection and reporting to either a default data DRB or a default DRB based on an indication. In some implementations, the indication may be provided via an RRC configuration, a medium access control (MAC) control element (CE), or a control PDU (e.g., a bit in end-marker Control PDU). In one example, for a QFI value assigned in functionality configuration without corresponding DRB configuration, a bit in the control PDU taking a first value (e.g., 0) may indicate that the UE may map the PDU generated for data collection and reporting to the default data DRB; the bit taking a second value (e.g.,1) may indicate that the UE may map the PDU generated for data collection and reporting to the default DRB.

[0052] FIG. 2 is a diagram depicting an example scenario of data radio bearer (DRB) assignment in accordance with an implementation of the present disclosure. In some embodiments, As illustrated in FIG.2, in a case that a data collection is initiated for AI / ML function #1, the RAN (e.g., the BS or the TRP) may not configure any QFI but set the indicator to “1”, the UE may map the generated PDU into the default data DRB and proceed following the MAC entity process for the reporting. In some embodiments, as illustrated in FIG. 2, the RAN (e.g., the BS or the TRP) may configure a QFI value for AI / ML function #n and add the QFI value to specific DRB#2. Consequently, the UE may map the generated PDU to the specific DRB #2 for reporting associated with AI / ML function #n. In another embodiment, the RAN (e.g., the BS or the TRP) may not configure any QFI but set the indicator to “0” while performing functionality configuration for ISAC function #k. The UE may then map the generated PDU to the default DRB for reporting associated with ISAC function #k.

[0053] In the present disclosure, the RAN (e.g., the BS or the TRP) may configure respective QFI values for the UE in different RRC states. Multiple QFIs may be mapped to Al, ML, ISAC, SON, or MDT functionality, and the adaptation may be based on the state (i.e., RRC states) of the UE.

[0054] Typically, the UE may perform reporting in different RRC states, which may require different power consumption and create different signaling overhead. Accordingly, the RAN (e.g., the BS or the TRP) may configure different QFI values in the functionality configuration, and the respective QFIs may map to different DRBs based on the RRC state; reporting may then be permitted, prioritized, or deprioritized in the associated RRC state. It should be noted that the CN may not be aware of the UE's RRC state transitions in legacy systems; thus, a unified QFI value may be applied regardless of the RRC state in which the UE operates.

[0055] In some implementations, if the UE transitions from the RRC connected state to either the RRC idle state or the RRC inactive state, the UE may retain a first set of DRB configurations and release a second set of DRB configurations. In some embodiments, the first set of DRB configurations may correspond to the DRBs that may be mapped from QFIs for data collection and reporting when the UE is in RRC IDLE / INACTIVE state, and the second set of DRBs may correspond to the DRBs that may not be mapped from the QFIs for data collection and reporting. It should be noted that the release of DRB for corresponding applications in either the RRC idle state or the RRC inactive state refers either (1) the application is prohibited for transmission accordingly or (2) the transmission for the corresponding application is only mapped to a default DRB.

[0056] In some embodiments, separate QFIs for different states are applied to indicate multiple QFIs in the functionality configuration. The QFI values may be enumerated, and each value may be configured or added in a corresponding DRB configuration. In one example, a first presented QFI may be applied to the RRC connected state, a second presented QFI may be applied to the RRC inactive state, and a third presented QFI may be applied to the RRC idle state. While the UE transitions to another RRC state andperforms reporting in that state, the UE may generate PDUs and map them into designated DRBs based on the applied QFI and reflective QoS rule for the current state.

[0057] Several solutions of the present disclosure are proposed for a case that the QFI value is absent for a particular state. In one embodiment, the UE may apply the same QFI value as configured in the previous state. In one embodiment, the UE may have no configured QFI for the state and may map PDUs to either the default DRB or the default data DRB for reporting. In one embodiment, the UE may select a QFI for processing the PDU and DRB mapping in that state (i.e., up to UE implementation). The UE implementation may include selecting a QFI from among the QFI values configured for the other states or selecting any QFI value. In one embodiment, the UE may determine that data collection and reporting for the functionality are not allowed in the state. Then the UE may not generate PDUs for the functionality while in this state. The UE may discard the collection results if transitioning into this state.

[0058] In some embodiments, the data collection and reporting may be configured via a system information block (SIB) and may apply to the inactive or idle state with a given quality of service (QoS) or a given QFI. In some embodiments, dedicated RRC signaling with corresponding different quality of service (or corresponding different QFIs) may be implemented for data collection and reporting in an event that the UE is in the RRC state.

[0059] In some embodiments, the RAN (e.g., the BS or the TRP) may reconfigure data collection configuration for the corresponding RRC state, and the UE may apply the configured QFI for PDU / DRB mapping. In one embodiment, the RAN (e.g., the BS or the TRP) may send an RRC release message comprising a suspend configuration to the UE while releasing the UE to the inactive state, wherein the data collection and relevant QFI value may be configured within the suspend configuration. Afterward, the inactive state UE may apply the configured QFI while UE is camped with the same cell, or the UE may apply the configured QFI regardless of the camped cell. It should be noted that the DRB configuration may also be reconfigured before releasing the UE to the RRC inactive state in an event that the configured QFI has not been added to a specific DRB. Regarding the idle state UE, the RAN (e.g., the BS or the TRP) may provide a data collection configuration via the SIB and configure relevant QFI based on the data collection configuration. If the UE doesn’t have a stored QFI value (received via a dedicated RRC message), the idle state UE may use the configured QFI from the SIB for reporting. In one embodiment, the idle state UE may ignore (e.g., not apply) the QFI value indicated in the SIB if the UE has a stored QFI value for the functionality upon being released to the idle state.

[0060] In some embodiments, the RAN (e.g., the BS or the TRP) may designate one or more DRBs without providing the QFI. Since the PDU generated for data collection and reporting is controllable by the RAN (e.g., the BS or the TRP), the RAN may directly specify the mapping DRBs rather than assigning a QFI. In one embodiment, the RAN (e.g., the BS or the TRP) may configure at least one of a whitelist (allowed DRBs for mapping) and a blacklist (restricted DRBs for mapping) upon functionality configuration. With these lists present, the UE may map the generated PDUs to the designated DRB for the corresponding functionality.

[0061] In the present disclosure, various embodiments are disclosed for more than one DRBs being satisfied for mapping. In one embodiment, the UE may select one of the DRBs (up to UE implementation). In one embodiment, the UE may always select one allowable DRB with the highest QoS priority. In one embodiment, the UE may be configurable to apply (i.e., UE implementation or the one with the highest QoS priority) based on an indicator in the functionality configuration. In one embodiment, the UE may map to all satisfied DRBs. In some embodiments, an indicator (one bit) may be appended to the functionality configuration. The UE may be permitted to duplicate the generated PDUs and map them into multiple DRBs if the bit is set to “1”; otherwise, the UE may select one DRB for mapping by option 1 (i.e., UE implementation), or option 2 (i.e., the one with the highest QoS priority). The UE may select multiple DRBs being mapped based on the UE’s implementation.

[0062] If no designated DRB (e.g., neither white list nor blacklist) is provided in the functionality configuration, the UE may map the PDUs either to the default DRB or to the default data DRB based on an indication from the RAN (e.g., the BS or the TRP). If the stored reflective QoS rule is present (e.g., is stored) and the corresponding configured DRB (via DRB configuration) differs from the designated DRB in the functionality configuration, the UE may skip the stored reflective QoS rule for that functionality during data collection and reporting. The whitelist or the blacklist may be provided via a dedicated RRC message or via system information. The dedicated RRC message may be an RRC configuration message or an RRC release message.

[0063] Except for the whitelist and / or blacklist, the RAN (e.g., the BS or the TRP) may implement the designation on a particular DRB by enabling or disabling the service data adaptation protocol (SDAP). If the SDAP is enabled, it implies that the UE may be required to acquire a QFI and apply the reflective QoS rule to map the generated PDU to the corresponding DRB. If the QFI is absent or no stored reflective QoS rule exists, the UE may map the PDU to the default DRB or the default data DRB. If the SDAP is disabled, it implies the UE may be required to acquire designated DRBs for the direct mapping. If the designated DRB information is absent, the UE may map the PDU to the default DRB or the default data DRB.

[0064] The enablement or disablement of SDAP (e.g., one bit) may be signaled via a dedicated RRC message, a MAC CE, a downlink control information (DCI), or system information. The granularity of SDAP enable / disable may be at the UE SDAP entity level (e.g., common to all functionalities, per functionality, per HARQ process, or per cell). It should be noted that the SDAP may provide functionality for QoS and DRB mapping, and it may operate with packet data convergence protocol (PDCP) in 6G or be specified as a new protocol entity in 6G. If UE is connected to 6G and 5G simultaneously, the described QFI mapping for data collection and reporting may be limited to 6G, e.g., the UE entity under 5G may map the PDU generated from data collection and reporting to the default DRB.

[0065] In the present disclosure, solutions for QFI adaptation based on conditions during data collection and reporting are disclosed. In general, the reporting payload size may vary based on data collection and reporting configurations, and it may be desirable to handle the corresponding PDUs by adapting QoS management. Similarly, sufficient buffer space / capacity to keep the continuity of data collection may be important, and it may be helpful if the UE could report the stored results before the buffer is full. The UEmay flush the corresponding memory after reporting to ensure buffer space / capacity availability. Accordingly, the reporting interval or the reporting trigger event may be based on the memory management. In addition to memory space, the UE power level is another factor: the UE may reduce the reporting interval to lower power consumption if the UE power level is below a threshold. To reflect the change in the reporting interval, the UE may need to update the corresponding QFI. However, the RAN (e.g., the BS or the TRP) may not know the UE conditions while configuring QFI.

[0066] In some embodiments, the RAN (e.g., the BS or the TRP) may configure a set of QFIs with multiple thresholds to support QFI adaptation based on data collection and / or UE conditions (e.g., reporting payload size, buffer management, UE power level, etc.). In one embodiment, the applied QFI may be updated if at least one of the above thresholds meets a trigger condition (e.g., exceeds or falls below the threshold). In one embodiment, QFI#1 and QFI#2 are configured for functionality #a. The UE may apply QFI#1 for DRB mapping in an event that the reporting payload size is smaller than IM bytes; otherwise, the UE may apply QFI#2 for DRB mapping.

[0067] In some embodiments, a default entry table is specified or configured by the RAN (e.g., the BS or the TRP) or predefined by the UE. The UE may apply the corresponding QFI based on the classification in the default entry table. In one embodiment, as illustrated in Table 1, each of the M entries may specify a QFI value (e.g., A, B, C, ... , M) that is bundled with a combination of a particular payload size, buffer management status, and a power level. The UE may determine the adopted entry while initiating the data collection and reporting. Consequently, the UE may determine the mapped DRB based on the selected QFI and proceed with the reporting. In this embodiment, the UE may select the QFI without receiving QFI assignments from the RAN (e.g., the BS or the TRP), and may send an end-marker control PDU to indicate the applied QFI for the associated PDU sessions.

[0068] [Table 1]Table 1, entry for QFI adaptationEntry No QFI value Payload size Buffer status Power level1 A <1M byte <50% <50% 2 B >1M byte <50% <50% 3 C <1M byte >50% <50%M M >1M byte >50% >50%

[0069] In one embodiment, the QFI adaptation may be applied only to data collection and reporting. There may be another QFI entry table used for other applications. In another embodiment, a new table entry that comprises all profiles and factors is unified and applied for all applications in the 6G network. The UE may indicate the selected entry to the RAN (e.g., the BS or the TRP) or the CN, and the indication may be transmitted via user assistance information (UAI), an UL Control MAC CE, or a control PDU.

[0070] In the present disclosure, various solutions for efficient data collection and reporting in an inactive state are disclosed. Small data transmission (SDT) is a procedure that allows data and / or signallingtransmission while the UE remains in an RRC inactive state without transiting to the RRC connected state. The SDT transmission may be enabled on a radio bearer basis and initiated by the UE only if there is less than a configured amount of UL data for which SDT transmission is enabled. Otherwise, the normal data transmission scheme may be used. Specifically, based on scheduling operations, the SDT transmission may be further categorized into Random Access (RA)-SDT and configured grant (CG)-SDT. The first operation (i.e., RA-SDT) is that the UE may trigger RA (either 2-step or 4-step), and the data payload is transmitted via MsgA or via UL grant provided by random access response (RAR). No reserved resources are pregranted, and the UE may initiate the RA-SDT on the corresponding SSB in an event that the SSB’s RSRP is better than a configured threshold and data is suitable for SDT. The UE may determine the SSB’s RSRP level and whether the data is suitable for SDT when data arrives in a buffer. The “suitable” data for SDT may be defined as the applicable DRBs and a sufficiently small data payload size. The second operation (i.e., CG-SDT) is that the UE may receive a CG configuration upon suspend configuration while being released to the inactive state. The inactive UE may transmit payload via the CG resources on the corresponding SSB if the SSB’s RSRP is better than a configured threshold, the time advance (TA) is still valid, and the data is suitable for SDT.

[0071] If the random access procedure is used for the SDT procedure and is successfully completed, the UE may continue monitoring the physical downlink control channel (PDCCH) addressed to the cell -radio network temporary identifier (C-RNTI) (e.g., temporary C-RNTI) received in the RAR until the SDT procedure is terminated.

[0072] On the other hand, if the CG-SDT is used and an initial transmission for the CG-SDT has already been performed, the UE may continue monitoring the PDCCH addressed to the C-RNTI as stored in the UE inactive access stratum (AS) context or addressed to CS-RNTI until the SDT procedure is terminated. With these approaches, the UE may perform subsequent SDT for data transmission without transiting to the RRC connected state, and it is the UE's implementation whether to segment the data payload to construct a suitable data session and keep the corresponding transmission occurring only in the RRC inactive state.

[0073] In some embodiments, the UE may be configured with NW-side data collection and reporting. In some embodiments, the UE may be configured with UE-side data collection and reporting. In some embodiments, the UE may be configured with both the NW-side and the UE-side data collection and reporting.

[0074] In some embodiments, under the NW-side data collection and reporting, the RAN (e.g., the BS or the TRP) may request the UE to report its measurement results, subject to a resource set transmitted / activated by the RAN. Then the RAN may use the measurement results (i.e., the reporting) to facilitate the training of its NW-side model for at least one corresponding functionality. In some embodiments of UE-side data collection and reporting, the UE may request the RAN (e.g., the BS or the TRP) or the CN to transmit a specific resource set. Then the UE may measure the resource set, or the UE may measure a common resource set transmitted by the RAN for UE-side model training. Afterward, theUE may report the measurement results to either a UE-side modem, a UE vendor, or the chipset vendor’s training entity to facilitate training of the UE-side model for the functionality.

[0075] In the present disclosure, several solutions for the UE in the inactive state are disclosed for three scenarios below.

[0076] Scenario 1 : The UE may indicate capability support for the data collection and reporting for a particular functionality (e.g., the UE may support data collection and reporting for this functionality) in the RRC connected state e.g., UE capability support may be different for different functionality; consequently, the resource set configuration is provided for either the NW-side (e.g., the RAN-side) or UE-side data collection, and the data collection process is activated. The collection process may not be discarded after the UE releases to the RRC inactive state. In one embodiment, the transmission of a resource set by the RAN (e.g., the BS or the TRP), even from different cells, may be continued, and the UE may be required to measure the set based on the configuration.

[0077] Scenario 2: The UE may indicate capability support for the data collection and reporting configuration for a particular functionality in the RRC connected state; consequently, the resource set configuration is provided for data collection. However, the data collection process is deactivated after the UE releases to the RRC inactive state. In one embodiment, the UE may retain the resource set configuration but be instructed to stop the measurement, wherein the RAN (e.g., the BS or the TRP) or the CN may stop transmitting the resource set and / or release the resource set configuration for the UE. Then the UE may not need to perform the corresponding measurement.

[0078] Scenario 3 : The UE may not indicate the capability support for the data collection and reporting configuration for a particular functionality (e.g., the UE may not collect and report the resource set measurements for the functionality) in the RRC connected state, and no resource set configuration is provided before the UE releases to the RRC inactive state.

[0079] The present disclosure further discloses several solutions for managing data collection and reporting while the UE is in the RRC inactive state under different scenarios. Specifically, these solutions may involve applying either an RA-SDT transmission or a CG-SDT transmission with data collection and reporting.

[0080] In some embodiments, the RAN (e.g., the BS or the TRP) may configure a data collection configuration for UEs in the inactive state, wherein the data collection configuration may be valid for an area and the association between AI / ML functionality, input (resource set), and output report (inference report) or valid for an area and the association between ISAC functionality, input (resource set), and output report (detection report). FIG. 3 is a diagram depicting an example scenario of the relationship under the data collection configuration in accordance with an implementation of the present disclosure.

[0081] In some embodiments, the reporting may be controlled by the RAN (e.g., the BS or the TRP) via the data collection configuration. In some embodiments, the RAN (e.g., the BS or the TRP) may configure a plurality of sets of resources and corresponding functionalities within the data collection configuration, wherein the RAN (e.g., the BS or the TRP) may assign respective resource set IDs and respective functionality IDs. In some embodiments, the RAN (e.g., the BS or the TRP) may configure only therespective resource set IDs and functionality IDs within the data collection configuration, and the UE may determine the corresponding resource sets and functionalities based on the respective resource set IDs and functionality IDs.

[0082] In one embodiment, one resource set ID may be mapped into more than one functionality ID. In one embodiment, a resource set ID may be mapped to a functionality ID. The mapping between resource set IDs and functionality IDs may be one-to-one, one-to-many, or many-to-many. Additionally, a reporting ID representing a reporting configuration may be linked to a functionality ID.

[0083] In some implementations, a functionality within the data collection configuration may represent a data collection purpose for a particular application. One functionality may be associated with a QFI (assigned by the CN or the RAN) or a DRB (assigned by the RAN), and the collection results may be constructed as a PDU session for the reporting, wherein the PDU session may be followed by either a configured QFI, a default QFI, a default DRB, a default data DRB, or an assigned DRB (e.g., a specific DRB). In some embodiments, a functionality ID may be assigned per functionality configuration, and the functionality ID is global within an area, wherein UEs within the area may be configured via the functionality configuration. In some embodiments, a resource set under a data collection process may represent a list of reference signaling, SSB, or measurement sources, and the resource set ID is used to identify the union of measurement targets for the functionality.

[0084] In some embodiments, the resource set and configuration may be unified within an area that is defined by the functionality configuration. In some embodiments, as illustrated in FIG.3, a plurality of resource sets may be linked to or associated with a single functionality (e.g., resource set IDs 3 and 4 linked to or associated with functionality ID 3). In some embodiments, as illustrated in FIG. 3, a single resource set may be reused for multiple functionalities (e.g., resource set ID 4 linked to or associated with functionality IDs 3 and 4).

[0085] In some embodiments, a functionality may be linked to or associated with a reporting configuration, and different functionalities may apply the same reporting configuration (e.g., functionality IDs 1 and 2 apply to reporting ID 1). In some embodiments, a functionality may be linked to or associated with a plurality of reporting configurations, and the collection results may be reported via different reporting configurations under different conditions or under different RRC states. In some embodiments, a reporting configuration may specify the reporting type, supporting SDT type, and other related parameters. The reporting configuration may be valid only within an area or within a cell, or always valid if the UE is in the RRC inactive state. In some embodiments, a reporting configuration may be linked to or associated with a plurality of CG-SDT configurations, if configured to do so.

[0086] In some embodiments, the RAN (e.g., the BS or the TRP) may configure a repoting configuration (which is different from the reporting configuration that the UE applies for reporting in the RRC connected state) for the data collection process when the UE transitions from the RRC connected state to the RRC inactive state or the RRC idle state, and there is a data collection process ongoing. It is noted that the report configuration may comprise at least one of a periodicity, first physical resources, and second physical resources. In one embodiment, the periodicity may be a periodicity that the UE needs to monitor the controlsignalling used to schedule UL resources for reporting, or the periodicity that the UE is granted with the UL resources for reporting. In one embodiment, the first physical resources may be used to monitor control signalling used to schedule UL resources for reporting. In one embodiment, the second physical resources may be physical resources that the UE may transmit a UL signal (e.g., preamble, wake-up signal) to the RAN (e.g., BS or TRP) for UL resources request for reporting.

[0087] In some embodiments, a functionality may not be applied with any reporting configuration. The UE may be required to store the collection results and may be permitted to report only upon an on-demand request from the RAN (e.g., the BS or the TRP) or the CN. In one embodiment, the on-demand request may be a paging message that the RAN (e.g., the BS or the TRP) or the CN may use to request that a particular UE in the RRC idle or RRC inactive state report the collection results. In one embodiment, the on-demand request may be an RRC message that the RAN (e.g., the BS or the TRP) may request a particular UE to report collection results while it is attempting to establish an RRC connection. In addition, the reporting configuration may also be used for inference reporting in a case that the functionality configuration indicates the behavior of the UE-side AI / ML model.

[0088] In some embodiments, the RAN (e.g., the BS or the RP) may configure the functionality configuration comprising or indicating the data collection reporting if the NW-side AI / ML model is used and inference reporting if the UE-side AI / ML model is used separately, and link to different reporting configurations. On the contrary, if a two-sided AI / ML model is used, the reporting configuration linked with the functionality may represent a configuration to support model transfer. In some embodiments, an information element (IE) presented in functionality configuration may be used to indicate which kind of model is used for the functionality, and then the report configuration may implicitly be referred to as data collection reporting, inference reporting, or model transfer.

[0089] In some embodiments, the reporting configuration may provide at least one of a reporting interval, a reporting duration, an absolute time stamp, a reporting transmission power, a reporting buffer management indication, a reporting trigger event, a maximum reporting payload size, a reporting state, and a reporting content. The reporting configuration may further specify the inference reporting format, the inference content, the inference quantity, and other parameters for the inference.

[0090] In some embodiments, the reporting interval may specify the reporting periodicity, and the value may be a multiple of the CG periodicity for the linked CG-SDT configuration.

[0091] In some embodiments, the reporting duration may specify a timer to enable reporting, and the timer value may be longer than the CG-SDT timer value. If the parameter is absent, the UE may use a CG-SDT timer as a valid duration for reporting.

[0092] In some embodiments, the absolute time stamp may serve as a time reference to the UE. The UE may receive the configuration on the absolute time stamp. The UE may use the time difference to represent when the data was collected.

[0093] In some embodiments, the reporting transmission power may specify an initial power for the reporting. Moreover, a power ramping step may be configured to increase the power for the subsequent SDT transmission, and the maximum transmission power may be specified as well.

[0094] In some embodiments, the reporting buffer management indication may specify that a buffer should be retained or discarded after reporting. In one embodiment, at least one threshold may be configured to identify whether the buffer is close to full. Whether the buffer is close to full or full may be determined by the UE implementation.

[0095] In some embodiments, the reporting trigger event may specify at least one of an event threshold, hysteresis, and time-to-trigger, wherein the UE may use the nearest available and valid CG resource for reporting if the trigger event is met.

[0096] In some embodiments, the maximum reporting payload size may specify the maximum payload that can be transmitted via a single CG resource. Additionally, the applied MCS may be indicated. Alternatively, the applied MCS may be indicated while a DCI is used to activate the CG resource.

[0097] In some embodiments, the reporting state may specify that the configuration is applied to the RRC connected state, the RRC idle state, the RRC inactive state, or an RRC state other than those three.

[0098] In some embodiments, the reporting content may specify N of time instances that the UE can report how many instances the corresponding data collection report or inference within a report, and M of frequency instances that the UE can report how many frequency instances the corresponding data collection reporting or inference within a report.

[0099] In the present disclosure, capability indications for initiating or stopping data collection, inference, sensing detection, or reporting processes are disclosed. In some implementations, the capability indication may indicate at least one of a data collection process, an inference process, a functionality indicated in the functionality configuration, and reporting of the PDU is inapplicable or applicable. In some embodiments, multiple RSRP thresholds are provided to determine whether a capability change in data collection and reporting is allowed via SDT transmission. In some embodiments, the UE may include the capability indication in an RRC message (e.g., in an RRC resume request message or in a UAI).

[0100] In some implementations, capabilities to support data collection of functionality (including AI / ML, ISAC, SON, MDT, and other 6G functions) may be changed during the RRC inactive state. It may not be feasible to continue the data collection process and reporting if the capability to support data collection for associated functionality changes is inapplicable under scenario 1. In some embodiments, a one-bit indicator may be used to reflect “applicable to support” or “inapplicable to support” for a functionality. In this regard, after confirming the UE identity during SDT, the inactive UE may indicate the inapplicability of the capability for a functionality and further provide a simple cause value together with inapplicability reporting.

[0101] In the present disclosure, two design options are disclosed for the inapplicability indication.

[0102] Option 1: The UE may include the information that comprises a functionality ID, one bit for capability indication, and x bits for simple cause value in an RRC message (e.g., in the UAI of the RRC message). The RRC message may be transmitted via an SRB via either RA-SDT or CG-SDT.

[0103] Option 2: The UE may separately transmit functionality ID, capability indication (one bit), and simple cause (x bits) in respective SDT transmissions that the UE may indicate corresponding functionality during the initial SDT transmission and then transmit capability and cause in subsequent SDT transmissions .In one embodiment, the simple cause may be a special value of inference (to show the UE-side model fails to run normally and is unable to have valid inference) that the UE may transmit the inference via the subsequent SDT, followed by CG-SDT configuration. In some implementations, the UE may indicate there is remaining information after each step of capability indication. In one example, the UE may transmit the functionality ID, the capability, and the indication of remaining information in a single SDT transmission; if the indication of remaining information is a specific value (e.g., 1), the UE may transmit the cause in the subsequent SDT transmission; if the indication is another value or the indication is not present, the UE may not transmit the cause in the subsequent SDT.

[0104] It may be critical to indicate the capability to support data collection and reporting for a functionality, and the information bit may be very compact (which may be encoded with a robust MCS). In some embodiments, a separate lower RSRP threshold may be additionally configured in a CG-SDT configuration or a reporting configuration, allowing the UE to transmit the capability indication via the RA-SDT or CG-SDT transmission, even over a worse channel. In some implementations, when the UE fails to report the collected data to the RAN (e.g., the BS or the TRP) in the RRC inactive state or the RRC idle state, the UE may initiate a cell selection / reselection procedure to connect to a cell#n for transmitting collected data and / or sensing data. It is noted that the cells that UE selected may be a set of cells configured to the UE when the UE transitions from RRC connected state to RRC inactive state / RRC idle state. In one embodiment, if the UE may not connect to any configured cells (e.g., a set of cells configured to the UE when the UE transitions from RRC connected state to RRC inactive state / RRC idle state), the UE may stop the data collection process (and then release the corresponding configurations). In another embodiment, if the UE fails to transmit collected data to the RAN (e.g., the BS or the TRP) and the re-attempt amount reaches a configured maximum value, the UE may stop the data collection process and then release the corresponding configurations. It is noted that the maximum re-attempt value may be configured to the UE by the RAN (e.g., the BS or the TRP) when the UE transitions from the RRC connected state to the RRC inactive state or RRC idle state.

[0105] In some embodiments for the enhancement of capability, a list of preambles may be reserved, and the RAN (e.g., the BS or the TRP) may obtain an early indication by the reception of an individual preamble. In one embodiment, preamble #1 is reserved and may be interpreted as functionality #1 is inapplicable, so that the UE may transmit preamble #1 in case functionality #1 becomes inapplicable to support data collection and reporting. In one embodiment, preamble #2 is reserved and may be interpreted as functionality #2 is inapplicable; the UE may transmit preamble #2 in an event that functionality #2 becomes inapplicable to support data collection and reporting. In some embodiments, separate CG-SDT configurations may be applied for capability indication, and the RAN (e.g., the BS or the TRP) may interpret which functionality becomes inapplicable for a UE to perform data collection and reporting upon receiving the corresponding CG during the RRC inactive state.

[0106] In some embodiments, in scenario 1, after receiving the capability indication from an UE in RRC inactive state and the capability indication indicates inapplicability to support data collection and reporting, the RAN (e.g., the BS or the TRP) may not transmit the RRC resume message but may communicate withthe UE to provide the new configuration / reconfiguration. In some embodiments, the UE may autonomously stop the data collection and / or the reporting before or after indicating the applicability (changed to inapplicable). The UE may retain all full data collection configuration(s), regardless of whether it supports full data collection configuration, until the RAN (e.g., the BS or the TRP) explicitly releases them. Similarly, for scenario 3, the UE may check the broadcasted functionality with relevant configurations and then indicate the capability via SDT. The UE may negotiate with the RAN (e.g., the BS or the TRP) on the preferred data collection (e.g., transmit data collection configuration and receive the confirmation message) via subsequent SDT.

[0107] FIG. 4 is a diagram depicting an example scenario of data collection and reporting procedure in accordance with an implementation of the present disclosure. The method may proceed from step 410 to 460. In step 410, the RAN (e.g., the BS or the TRP) may send an RRCReconfiguration message to the UE and configure the available resource set for the corresponding functionality in a data collection process. Specifically, the available resource set is configured by resource set configuration and may be linked to a functionality configuration. In some embodiments, the RRCReconfiguration message may comprise a first data collection configuration. In some embodiments, the first data collection configuration may be a full data collection configuration. In some embodiments, the first data collection configuration may comprise the available resource set and the corresponding functionality. In some embodiments, the first data collection configuration may comprise only resource set IDs for the available resource set and IDs for the corresponding functionality. In some embodiments, the first data collection configuration may be set up in the format shown in FIG. 3. Then, the method proceeds to step 420.

[0108] In step 420, the UE may send an RRCReconfigurationComplete message in response to the RRC reconfiguration, and the UE may indicate capabilities for respective functionalities and a preferred resource set for data collection if the BS makes a capability inquiry. In some embodiments, the capabilities for respective functionalities and the preferred resource set may be included or indicated in a second data collection configuration. The UE may determine the second data collection based on the first data collection configuration. That is, the UE may determine the capabilities for respective functionalities and the preferred resource set based on the first data collection configuration. In some embodiments, the second data collection configuration may be included in the RRCReconfigurationComplete message. In some embodiments, for each functionality, the UE may use 1 bit to indicate the preference for data collection. In one embodiment, for a supportable functionality for data collection and reporting, the UE may set the bit to a first value (e.g., 1) to indicate that the UE prefers to use the provided resource sets associated with the functionality for data collection; the UE may set the bit to a second value (e.g., 0) to indicate that the UE does not prefer to use the provided resource sets associated with the functionality for data collection. In some embodiments, the second data collection configuration may be configured in the format shown in FIG. 3. Then, the method proceeds to step 430.

[0109] In step 430, the RAN (e.g., the BS or the TRP) may transmit an RRCRelease message to the UE. In some embodiments, the RAN (e.g., the BS or the TRP) may select and activate the resource set for data collection, which was intended to be performed by the UE during the RRC inactive state, and theconfiguration may be included in the RRCRelease message. In some embodiments, the RAN (e.g., the BS or the TRP) may determine the resource set for data collection included in the RRCRelease message according to the second data collection configuration.

[0110] In some embodiments, a CG-SDT configuration linked to a data collection reporting configuration may be provided, and the UE may follow the reporting configuration to perform either data collection and reporting (NW-side model) or inference reporting (UE-side model). In some embodiments, the CG-SDT configuration and the data collection configuration may be included in a suspend configuration and configured in the format as shown in FIG. 3.

[0111] In some embodiments, a RA-SDT configuration linked to a data collection reporting configuration may be provided, and the UE may follow the reporting configuration to perform either data collection and reporting (NW-side model) or inference reporting (UE-side model). Then, the method proceeds to step 431.

[0112] In step 431, the UE transitions from the RRC connected state to the RRC inactive state. Then, the method proceeds to step 440, 441, or 460.

[0113] In step 440, the UE may transmit an RRC resume request and report the data collection results to the RAN (e.g., the BS or the TRP). After the UE releases to the RRC inactive state and certain conditions are met, the UE may determine whether the CG-SDT is valid for reporting. In one embodiment, if CG-SDT is valid (e.g., SSB’s RSRP level is sufficient and TA is valid), the UE may send the RRC resume request (as for indicating UE identity) and data collection reporting payload to the RAN (e.g., the BS or the TRP) without transiting to the RRC connected state. Then, the method proceeds to step 441.

[0114] In step 441 , the UE in the RRC inactive state may determine that at least one of the data collection processes, the inference process, the functionality indicated in the data collection configuration, and reporting of the PDU is inapplicable. Then, the method proceeds to step 450.

[0115] In step 450, the UE may transmit an RRC resume request and indicate inapplicable capability to the RAN (e.g., the BS or the TRP) via the CG-SDT resource. In one embodiment, if the UE determines that the capability is changed to inapplicable to support the data collection and reporting, and the CG-SDT is valid, the UE may send the RRC resume request (as for indicating UE identity) and indicate the changes to the RAN (e.g., the BS or the TRP) without transiting to the RRC connected state. Afterward, the UE may autonomously stop the data collection. It is noted that the UE may perform an RRC resume request and send an indication of capability changes in an event that there is no valid CG-SDT or RA-SDT, and the UE may autonomously stop the data collection before resuming.

[0116] In step 460, data collection reconfiguration is performed between the UE and the RAN (e.g., the BS or the TRP) via a subsequent CG-SDT transmission addressed by CS-RNTI or via a subsequent RA-SDT transmission.

[0117] In some embodiments, in scenario 2, the UE may request a preferred resource set for data collection of functionality via a subsequent SDT. The request may include at least an indication to start / stop data collection and a list of preferred configurations from the configured resource set. In some embodiments, the RAN (e.g., the BS or the TRP) may transmit an acknowledgment in response to therequest to the UE via the common RA search space or the common SDT search space. In some embodiments, the UE may determine that the preferred resource set for data collection is activated upon receiving the acknowledgment from the RAN (e.g., the BS or the TRP). In some embodiments, the preference reporting on the resource set may be enabled or disabled by the RAN (e.g., a flag may be configured to indicate it). In some embodiments, a prohibit timer may be provided to prevent the UE from requesting a preferred resource set more than once within a period.

[0118] In the present disclosure, availability indications for the reporting processes are disclosed. In some embodiments, while the UE is in the RRC inactive state and the data collection process is activated for facilitating an NW-side functionality (e.g., resource set is provided and activated), the UE may trigger a first availability indication in order to further proceed with the reporting in an event that at least one of the following first conditions is met:S Full buffer being reached (if configured), i.e., the buffer is full.S Buffer threshold being reached (if configured), e.g., a used capacity of the buffer is greater than a first threshold.RSRP is being exceeded by a threshold (if configured), e.g., the RSRP of a received reference signal exceeds a second threshold.S CG-SDT Timer is going to expire (e.g., less than the remaining timer value, or a running time of the CG-SDT timer or an RA-SDT timer is less than a third threshold) (if configured).S Low power (if configured), e.g., a power level of the apparatus is lower than a fourth threshold. S At least one DRB associated with a particular application met the validity of SDT transmission (e.g., the CG-SDT transmission or the RA-SDT transmission).S Area ID or tracking area ID changed.There is remaining data after transmitting a part of the segmented PDUs.

[0119] In some embodiments, while one of the first conditions is met, the UE may initiate either a RA-SDT transmission or a CG-SDT transmission and transmit the first availability indications. In some embodiments, the first availability indications may comprise: 1) Data is available, 2) Reason fortrigger, 3) Data size, 4) preferred QFI, 5) Low power indication, 6) which associated cell / frequency / area has availability of the functionality.

[0120] It is noted that availability indications (either the first or the second availability indication) may be per application, per data collection configuration, per functionality, or per logical channel group (LCG). Together with availability indication, the UE may append a functionality ID for identification. Considering that the data collection and the model may be vendor-specific, the UE identity may not need to be included (it implies there is no RRC resume request sent from the UE) while performing availability indication during the SDT transmission. In some embodiments, the UE in the inactive state may transmit the second availability indication in an event that a second condition is met. In some embodiments, the second availability indication may comprise at least one of the following:S The camped cell changed.S The prohibit timer was not running .■ Other configurations triggered the availability indication.S The UE sent the RRC resume request.

[0121] In some embodiments, after receiving the availability indication, the RAN (e.g., the BS or the TRP) may decide to retrieve the collection results and request that the UE transitions to the RRC connected state by sending an RRC resume message. In some embodiments, after receiving the availability indication, the RAN (e.g., the BS or the TRP) may decide to retrieve the collection results and communicate with the UE by using the common RA search space or the common SDT search space, and retrieve the data via a subsequent SDT transmission, e.g., the UE doesn’t transition to the RRC connected state. In some embodiments, the collection results may be deleted after reporting, but the data collection may continue according to the data collection configuration. In some embodiments, on the contrary, the RAN (e.g., the BS or the TRP) may decide not to retrieve the collection results even when receiving the availability, and the RAN (e.g., the BS or the TRP) may further indicate the UE not to report the collection results via the subsequent SDT. In this case, the UE may store the non-retrieved data beyond a duration. Moreover, if the buffer is full, the UE may stop the data collection unless the UE receives further instructions from the RAN (e.g., the BS or the TRP).

[0122] In the present disclosure, various solutions for energy-efficient (SDT) transmission during data collection reporting are disclosed. In general, it is desirable to transmit a large payload within a limited time rather than transmit a small piece of payload multiple times. However, current RA-SDT or CG-SDT transmissions have limitations in data volume, and their subsequent SDT may degrade energy performance. Accordingly, the present disclosure discloses three enhancements.

[0123] Enhancement #1: Retransmission -less CG-SDT.

[0124] Enhancement #2: Allowing multiple transmissions at one time.

[0125] Enhancement #3: Link adaptation under a CG-SDT configuration.

[0126] In some embodiments of enhancement #1, to avoid unnecessary monitoring on the PDCCH during a CG-SDT transmission, it may be configured by the RAN (e.g., the BS or the TRP) to enable or disable a hybrid automatic repeat request (HARQ) process for a given functionality. While HARQ is disabled, the inactive UE may utilize all available CG resources during the mapped CG-SDT configuration to perform collection reporting without waiting for an acknowledgment of the uplink transmission. As a result, the transmission time may be shortened and the UE's power consumption reduced.

[0127] In some embodiments of enhancement #2, the RAN (e.g., the BS or the TRP) may configure multiple CG-SDT configurations linked to a reporting configuration for a functionality. Moreover, the RAN (e.g., the BS or the TRP) may permit the inactive UE to initiate multiple CG-SDT or RA-SDT transmissions at one time and separately transmit the segmented PDUs within a short interval. In one embodiment, the UE may check the RSRP threshold per SSBs and initiate all CG-SDT transmission if any corresponding SSB’s link performance is sufficiently high. Different from legacy CG-SDT (e.g., NR CG-SDT), which only allows the UE to select one of the SSB indices to initiate the CG-SDT, the proposed enhancement allows the UE to utilize more than one SSB index to initiate the CG-SDT transmission. In one embodiment, a single indicator (one bit) in the report configuration is used to enable / disable (turnon / off) simultaneous SDT (the default behavior is to disable simultaneous SDT). In spite of explicit indication, implicit indication by checking the reporting data size and then deciding to enable / disable simultaneous SDT is another design option. In one embodiment, multiple PUSCH occasions per CG configuration are applied to a CG-SDT configuration for data collection reporting, and an inactive UE may prioritize this resource if the data collection reporting size is large.

[0128] In some embodiments of enhancement #3, the UE may send the availability indication via the initial SDT, together with the preferred physical layer profile. The physical layer profile comprises the preferred MCS, the preferred MIMO layers, the preferred TDRA / FDRA, the preferred bandwidth, and the preferred transmission power. Without receiving the termination from the RAN (e.g., the BS or the TRP) on the subsequent SDT, the UE may apply the preferred physical layer profile to subsequent SDT and achieve higher data rate transmission. The preferred physical layer profile may be transmitted via UAI or UL MAC CE. In one embodiment, the preferred layer profile is applied to every subsequent SDT (e.g., a single parameter set for all transmission occasions). In one embodiment, multiple preferred layer profiles may be provided, and each profile is suggested for an individual subsequent SDT transmission occasion. In one embodiment, the BS provides several physical layer profile configurations in the SIB, and the UE indicates the preferred profile ID via the Msg3.Illustrative Implementations

[0129] FIG. 5 illustrates an example communication system 500 having an example communication apparatus 510 and an example network apparatus 520 in accordance with an implementation of the present disclosure. Each of communication apparatus 510 and network apparatus 520 may perform various functions to implement schemes, techniques, processes, and methods described herein pertaining to data collection and reporting in mobile communications, including scenarios / schemes described above as well as processes 600 and 700 described below.

[0130] Communication apparatus 510 may be a part of an electronic apparatus, which may be a dualsteer device containing one or more UEs such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus, or a computing apparatus. For instance, communication apparatus 510 may be implemented in a smartphone, a smartwatch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing equipment such as a tablet computer, a laptop computer, or a notebook computer. Communication apparatus 510 may also be a part of a machine type apparatus, which may be an loT, NB-IoT, eMTC, IIoT UE, such as an immobile or a stationary apparatus, a home apparatus, a roadside unit (RSU), a wire communication apparatus, or a computing apparatus. For instance, communication apparatus 510 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 510 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 510 may include at least some of those components shown in FIG.5, such as a processor 512, for example. Communication apparatus 510 may further include one or more other components not pertinent to the proposed schemes of the present disclosure (e.g., internal power supply, display device, and / or user interface device), and, thus, such component(s) of communication apparatus 510 are neither shown in FIG. 5 nor described below in the interest of simplicity and brevity.

[0131] Network apparatus 520 may be a part of an electronic apparatus, which may be a network node such as a satellite, a BS, a small cell, a router, or a gateway of a 4G / 5G / B5G / 6G, a Central Unit (CU), a Distributed Unit (DU) or a Radio Unit (RU), NR, loT, NB-IoT, or IIoT network. Alternatively, network apparatus 520 may be implemented in the form of one or more IC chips, such as, for example, and without limitation, one or more single-core processors, one or more multi -core processors, or one or more RISC or CISC processors. Network apparatus 520 may include at least some of those components shown in FIG. 5, such as a processor 522, for example. Network apparatus 520 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 520 are neither shown in FIG. 5 nor described below in the interest of simplicity and brevity.

[0132] In one aspect, each of processor 512 and processor 522 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 “a processor” is used herein to refer to processor 512 and processor 522, each of processor 512 and processor 522 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 processor 512 and processor 522 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 processor 512 and processor 522 is a special-purpose machine specifically designed, arranged, and configured to perform specific tasks in a device (e.g., as represented by communication apparatus 510) and a network node (e.g., as represented by network apparatus 520) in accordance with various implementations of the present disclosure.

[0133] In some implementations, communication apparatus 510 may also include a transceiver 516 coupled to processor 512 and capable of wirelessly transmitting and receiving data. In some implementations, transceiver 516 may be capable of wirelessly communicating with different types of UEs and / or wireless networks of different RATs. In some implementations, transceiver 516 may be equipped with a plurality of antenna ports (not shown), such as, for example, four antenna ports. That is, transceiver 516 may be equipped with multiple transmit antennas and multiple receive antennas for multiple -input multiple-output (MIMO) wireless communications. In some implementations, network apparatus 520 may also include a transceiver 526 coupled to processor 522. Transceiver 526 may include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, transceiver 526 may be capable of wirelessly communicating with different types of UEs of different RATs. In some implementations,transceiver 526 may be equipped with a plurality of antenna ports (not shown) or a plurality of panels, such as, for example, four antenna ports. That is, transceiver 526 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.

[0134] In some implementations, communication apparatus 510 may further include a memory 514 coupled to processor 512 and capable of being accessed by processor 512 and storing data therein. In some implementations, network apparatus 520 may further include a memory 524 coupled to processor 522 and capable of being accessed by processor 522 and storing data therein. Each of memory 514 and memory 524 may include a type of random-access memory (RAM) such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively, or additionally, each of memory 514 and memory 524 may include atype of read-only memory (ROM) such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively, or additionally, each of memory 514 and memory 524 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0135] Each of communication apparatus 510 and network apparatus 520 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, a description of capabilities of communication apparatus 510, as a UE, and network apparatus 520, as a network node (e.g., BS), is provided below with processes 600, 700, and 800.Illustrative Processes

[0136] FIG. 6 illustrates an example process 600 in accordance with an implementation of the present disclosure. Process 600 may be an example implementation of above scenarios / schemes, whether partially or completely, with respect to data collection and reporting in mobile communications. Process 600 may represent an aspect of implementation of features of communication apparatus 510. Process 600 may include one or more operations, actions, or functions as illustrated by one or more of blocks 610 to 640. Although illustrated as discrete blocks, various blocks of process 600 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 600 may be executed in the order shown in FIG. 6 or, alternatively, in a different order. Process 600 may be implemented by or in communication apparatus 510 or any suitable UE or machine type device . Solely for illustrative purposes and without limiting the scope, process 600 is described below in the context of communication apparatus 510, as a UE, and network apparatus 520, as a network node (e.g., a BS, a cell, or a TRP). Process 600 may begin at block 610.

[0137] At block 610, process 600 may involve processor 512 of communication receiving, via transceiver 516, a data collection configuration from network apparatus 520, wherein the data collection configuration comprises at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration. Process 600 may proceed from block 610 to block 620.

[0138] At block 620, process 600 may involve processor 512 generating a PDU according to the data collection configuration. Process 600 may proceed from block 620 to block 630.

[0139] At block 630, process 600 may involve processor 512 constructing a PDU session according to the at least one functionality configuration. Process 600 may proceed from block 630 to block 640.

[0140] At block 640, process 600 may involve processor 512 performing, via transceiver 516, a transmission to report the PDU based on the least one reporting configuration to network apparatus 520 via the PDU session.

[0141] In some implementations, the data collection configuration is comprised in a suspended configuration received from an RRC release message in a case that communication apparatus 510 is in a connected state. In some implementations, the data collection configuration is received from a downlink SDT transmission or via SIB in a case that communication apparatus 510 is in an inactive state. In some implementations, the data collection configuration is received via the SIB in a case that communication apparatus 510 is in an idle state.

[0142] In some implementations, process 600 may further involve processor 512 receiving, via transceiver 516, a CG-SDT configuration or an RA-SDT configuration from network apparatus 520, wherein the transmission to report or forward the PDU based on the least one reporting configuration is an SDT transmission, and the SDT transmission is performed according to the CG-SDT configuration or the RA-SDT configuration.

[0143] In some implementations, process 600 may further involve processor 512 obtaining a QFI from the at least one functionality configuration. Process 600 may further involve processor 512 mapping the PDU session to either a specific DRB, a default DRB, or a default data DRB according to the QFI.

[0144] In some implementations, the PDU session is mapped to the default data DRB in a case that the QFI is absent in the data collection configuration.

[0145] In some implementations, process 600 may further involve processor 512 obtaining an indicator from the data collection configuration. Process 600 may further involve processor 512 mapping the PDU session to either a default DRB or a default data DRB according to the indicator.

[0146] In some implementations, process 600 may further involve processor 512 receiving, via transceiver 516, a DRB configuration from network apparatus 520. The process 600 may further involve processor 512 obtaining QFI or an indicator from at least one functionality configuration. Process 600 may further involve processor 512 skipping a QoS mapping rule associated with a DRB designated in the DRB configuration in an event that a DRB designated in the QFI or the indicator is different from the DRB designated in the DRB configuration. Process 600 may further involve processor 512 mapping the PDU session to the DRB designated in the QFI or the indicator in a case that the reflective QoS mapping rule is skipped, wherein the DRB designated in the QFI or the indicator is either the specific DRB or the default data DRB.

[0147] In some implementations, process 600 may further involve processor 512 transmitting, via transceiver 516, a capability indication to network apparatus 520, wherein the capability indication is comprised in an RRC message.

[0148] In some implementations, process 600 may further involve processor 512 reserving a preamble of an uplink signal to indicate that at least one of a data collection process, an inference process, a functionality indicated in the data collection configuration, and reporting of the PDU is inapplicable or applicable. Process 600 may further involve processor 512 transmitting, via transceiver 516, the uplink signal to network apparatus 520.

[0149] In some implementations, the transmission is a CG-SDT transmission or an RA-SDT transmission. The capability indication may indicate at least one of a data collection process, an inference process, a functionality indicated in the data collection configuration, and reporting of the PDU is inapplicable or applicable.

[0150] In some implementations, the capability indication may be included in a UAI of the RRC message.

[0151] In some implementations, the RRC message is an RRC reconfiguration complete message or an RRC resume request message.

[0152] In some implementations, process 600 may further involve processor 512 transmitting, via transceiver 516, a first availability indication to network apparatus 520, wherein the first availability indication is comprised in an RRC message.

[0153] In some implementations, the first availability indication comprises at least one of the following:S Data of the PDU is available.S a cause of triggering the first availability indication.S data size of the PDU.a QFI.S a low power indication.S An associated cell, an associated frequency, or an associated area has availability of a functionality indicated in at least one functionality configuration.

[0154] In some implementations, the first availability indication is transmitted to report or forward the PDU in an inactive state in a case that a first condition is met, wherein the transmission is a CG-SDT or RA-SDT transmission. The first condition comprises at least one of the following:S A buffer of communication apparatus 510 is full.S A used capacity of the buffer is greater than a first threshold.An RSRP of a received reference signal exceeds a second threshold.S A CG-SDT timer or an RA-SDT timer is going to expire, e.g., less than a third threshold.S The power level of the apparatus is lower than a fourth threshold.S At least one DRB associated with a functionality meets the validity of the CG-SDT transmission or the RA-SDT transmission.An area ID or a tracking ID is changed.There is remaining data after part of the PDU is forwarded or reported.

[0155] In some implementations, process 600 may further involve processor 512 transmitting, via transceiver 516, a second availability indication to network apparatus 520 in a case that a second condition is met, wherein the second condition comprises at least one of the following:S a camped cell is changed;a prohibit timer is not running;S a reconfigured data collection configuration is received; andAn RRC resume request message is transmitted.

[0156] In some implementations, process 600 may further involve processor 512 receiving, via transceiver 516, an indication from network apparatus 520. Process 600 may further involve processor 512 disabling a HARQ process for a functionality in the at least one functionality configuration according to the indication.

[0157] In some implementations, process 600 may further involve processor 512 receiving, via transceiver 516, a plurality of CG-SDT configurations from network apparatus 520, wherein the CG-SDT configurations are linked with the at least one reporting configuration. In some implementations, the PDU is reported or forwarded to network apparatus 520 according to at least one reporting configuration and the linked CG-SDT configurations.

[0158] In some implementations, process 600 may further involve processor 512 transmitting, via transceiver 516, a physical layer profile via the transmission to network apparatus 520. Process 600 may further involve processor 512 performing, via transceiver 516, a subsequent transmission according to the physical layer profile.

[0159] In some implementations, the physical layer profile is transmitted via UAI or an MAC-CE, and the transmission and the subsequent transmission are SDT transmissions . The physical layer profile may comprise at least one of an MCS, a MIMO layer, a TDRA, an FDRA, and a transmission power.

[0160] In some implementations, process 600 may further involve processor 512 performing at least one of a data collection process, an inference process, and a reporting process according to the data collection configuration in a case that the apparatus is in an inactive state, wherein the data collection process or the inference process is performed based on the at least one resource set configuration and the at least one functionality configuration, and wherein the PDU is generated according to the at least one of the data collection process, the inference process, and the reporting process.

[0161] In some implementations, process 600 may further involve processor 512 receiving, via transceiver 516, an RRC release message from network apparatus 520. The RRC release message may comprise a suspend configuration. The suspend configuration may comprise a CG-SDT configuration and a data collection configuration. Process 600 may further involve processor 512 transiting the apparatus from a connected state to an inactive state. Process 600 may further involve processor 512 performing a CG-SDT transmission to forward the PDU to network apparatus 520 via the PDU session according to the CG-SDT configuration.

[0162] In some implementations, process 600 may further involve processor 512, including a capability indication in an RRC resume request message. The capability indication may indicate at least one of a datacollection process, an inference process, a functionality indicated in at least one functionality configuration, and forwarding or reporting of the PDU is inapplicable or applicable. Process 600 may further involve processor 512 transmitting, via transceiver 516, the RRC resume request message to the network node via a subsequent CG-SDT transmission.

[0163] In some implementations, process 600 may further involve processor 512 determining whether a third condition is met after the apparatus is transited to the inactive state. The third condition comprises at least one of the following:An RSRP of an SSB is greater than a first threshold; andS A TA value is valid.

[0164] Process 600 may further involve processor 512 including a capability indication in an RRC resume request message in an event that the third condition is met. The capability indication may indicate at least one of a data collection process, an inference process, a functionality indicated in the at least one functionality configuration, and forwarding of the PDU is inapplicable or applicable. Process 600 may further involve processor 512 transmitting, via transceiver 516, the RRC resume request message to network apparatus 520 via a subsequent CG-SDT transmission in an event that the third condition is met.

[0165] In some implementations, process 600 may further involve processor 512 receiving, via transceiver 516, an RRC reconfiguration message from network apparatus 520. The RRC reconfiguration message may comprise a first data collection configuration. Process 600 may further involve processor 512 determining a second data collection configuration according to the first data collection configuration. Process 600 may further involve processor 512 transmitting, via transceiver 516, an RRC reconfiguration complete message to the network node before receiving the RRC release message or performing a subsequent CG-SDT transmission, or after performing the CG-SDT transmission. The RRC reconfiguration complete message may comprise a capability indication and the second data collection configuration.

[0166] FIG. 7 illustrates an example process 700 in accordance with an implementation of the present disclosure. Process 700 may be an example implementation of above scenarios / schemes, whether partially or completely, with respect to data collection and reporting in mobile communications. Process 700 may represent an aspect of implementation of features of network apparatus 520. Process 700 may include one or more operations, actions, or functions as illustrated by one or more of blocks 710 to 730. Although illustrated as discrete blocks, various blocks of process 700 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 700 may be executed in the order shown in FIG. 7 or, alternatively, in a different order. Process 700 may be implemented by or in network apparatus 520 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 700 is described below in the context of communication apparatus 510, as a UE, and network apparatus 520, as a network node (e.g., a BS such as BS). Process 700 may begin at block 710.

[0167] At block 710, process 700 may involve processor 522 of network apparatus 520, determining at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration. Process 700 may proceed from block 710 to block 720.

[0168] At block 720, process 700 may involve processor 522, including at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration in a suspend configuration. Process 700 may proceed from block 720 to block 730.

[0169] At block 730, process 700 may involve processor 522 of network apparatus 520, transmitting, via transceiver 526, an RRC release message to communication apparatus 510, wherein the RRC release message comprises the suspend configuration.

[0170] In some implementations, process 700 may further involve processor 522 of network apparatus 520 determining a CG-SDT configuration for a CG-SDT transmission. The process 700 may further involve processor 522 of network apparatus 520 including the CG-SDT configuration in the suspend configuration. Process 700 may further involve processor 522 of network apparatus 520 receiving, via transceiver 526, a PDU from the UE via the CG-SDT transmission.

[0171] In some implementations, process 700 may further involve processor 522 of network apparatus 520 receiving, via transceiver 526, an RRC resume request message from communication apparatus 510 via a subsequent transmission, wherein the RRC resume request message comprises a capability indication, and the capability indication indicates at least one of a data collection process, an inference process, a functionality indicated in the at least one functionality configuration, and reporting of the PDU is inapplicable or applicable.

[0172] In some implementations, process 700 may further involve processor 522 of network apparatus 520 including at least one designated resource set configuration, at least one designated functionality configuration, and at least one designated reporting configuration in a first data collection configuration. Process 700 may further involve processor 522 of network apparatus 520 transmitting, via transceiver 526, an RRC reconfiguration message to the UE, wherein the RRC reconfiguration message comprises the first data collection configuration. Process 700 may further involve processor 522 of network apparatus 520 receiving, via transceiver 526, an RRC reconfiguration complete message from the UE before transmitting the RRC release message or a subsequent CG-SDT transmission, or after the CG-SDT transmission. The RRC reconfiguration complete message may comprise a capability indication and a second data collection configuration. The at least one resource set configuration, the at least one functionality configuration, and the at least one reporting configuration may be determined according to the second data collection configuration.

[0173] In some implementations, process 700 may further involve processor 522 of network apparatus 520 receiving, via transceiver 526, an availability indication associated with the PDU. The availability indication may comprise at least one of the following:S Data of the PDU is available;S A cause of triggering the availability indication (e.g., triggering either a CG-SDT transmission or an RA-SDT transmission);Data size of the PDU;A QFI;S A low power indication; andS An associated cell, an associated frequency, or an associated area has availability of a functionality indicated in the suspend configuration.

[0174] In some implementations, process 700 may further involve processor 522 of network apparatus 520 determining that a QFI or an indicator for a functionality in the at least one functionality configuration, wherein the QFI or the indicator is associated with either a specific DRB, a default DRB, or a default data DRB. Process 700 may further involve processor 522 of network apparatus 520 including the QFI or the indicator in the functionality configuration.

[0175] In some implementations, process 700 may further involve processor 522 of network apparatus 520 determining, by the processor, a QFI for a connected state or an inactive state and a QFI for an idle state for a functionality in the at least one functionality configuration, wherein each of the QFI for the connected state or the inactive state and the QFI for the idle state is associated with either a specific DRB or a default data DRB. Process 700 may further involve processor 522 of network apparatus 520 including the QFI for the connected state or the inactive state in the suspend configuration. Process 700 may further involve processor 522 of network apparatus 520 transmitting, via transceiver 526, the QFI for the idle state to the UE via system information.

[0176] In some implementations, process 700 may further involve processor 522 of network apparatus 520 determining a plurality of QFIs and a plurality of thresholds for a functionality in the at least one functionality configuration, wherein the plurality of QFIs is associated with either a specific DRB, a default DRB, or a default data DRB. Process 700 may further involve processor 522 of network apparatus 520 including the plurality of QFIs and the plurality of thresholds in the suspend configuration.

[0177] In some implementations, the at least one reporting configuration comprises at least one of the following:S a periodicity that the UE needs to monitor a control signalling used to schedule UL resources for reporting;S or a periodicity that the UE is granted with the UL resources for reportingS physical resources used to monitor the control signaling used to schedule the UL resources for reporting; andS physical resources for the UE transmitting an UL signal for UL resources request for reporting.

[0178] In some implementations, the at least one reporting configuration comprises a reporting type, a supporting small data transmission (SDT) type, at least one of a reporting interval, a reporting duration, an absolute time stamp, a reporting transmission power, a reporting buffer management indication, a reporting trigger event, a maximum reporting payload size, a reporting state, and a reporting content.

[0179] In light of the above -de scribed embodiments, it is noteworthy that, by applying the schemes of the present disclosure, the UE in the inactive state may perform one or more of the data collection procedureand the inference procedure associated with AI / ML functionality, ISAC functionality, or SON / MDT functionality and report or forward the result of the procedures to the RAN (e.g., the BS or the TRP) in time while the UE is still in the inactive state. In addition, the RAN (e.g., the BS or the TRP) may determine which of the DRBs are used to report the results of the procedures through QFIs or indicators. Accordingly, the adaptive procedures may provide the UE and the RAN with efficient and effective support of data reporting for AI / ML, ISAC, SON, and MDT services.Additional Notes

[0180] 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

CLAIMSWHAT IS CLAIMED IS:

1. A method, comprising:receiving, by a processor of an apparatus, a data collection configuration from a network node, wherein the data collection configuration comprises at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration;generating, by the processor, a protocol data unit (PDU) according to the data collection configuration;constructing, by the processor, a PDU session according to the at least one functionality configuration; andperforming, by the processor, a transmission to forward the PDU based on the least one reporting configuration to the network node via the PDU session.

2. The method of Claim 1, wherein the data collection configuration is comprised in a suspended configuration received from a radio resource control (RRC) release message in a case that the apparatus is in a connected state.

3. The method of Claim 1, further comprises:receiving, by the processor, a configured grant (CG)-small data transmission (SDT) configuration or a random access-based (RA)-SDT configuration from the network node, wherein the transmission to forward the PDU based on the least one reporting configuration is an SDT transmission, and the SDT transmission is performed according to the CG-SDT configuration or the RA-SDT configuration.

4. The method of Claim 1, further comprises:obtaining, by the processor, a quality of service (QoS) flow identifier (QFI) from the at least one functionality configuration; andmapping, by the processor, the PDU session to either a specific data radio bearer (DRB) or a default DRB or a default data DRB according to the QFI.

5. The method of Claim 4, wherein the PDU session is mapped to the default data DRB in a case that the QFI is absent in the data collection configuration.

6. The method of Claim 1, further comprises:obtaining, by the processor, an indicator from the data collection configuration; and mapping, by the processor, the PDU session to either a default data radio bearer (DRB) or a default data DRB according to the indicator.

7. The method of Claim 1, further comprises:receiving, by the processor, a DRB configuration from the network node;obtaining, by the processor, a quality of service (QoS) flow identifier (QFI) or an indicator from the at least one functionality configuration;skipping, by the processor, a QoS mapping rule associated with a DRB designated in the DRB configuration in an event that a DRB designated in the QFI or the indicator is different from the DRB designated in the DRB configuration; andmapping, by the processor, the PDU session to the DRB designated in the QFI or the indicator in a case that the reflective QoS mapping rule is skipped, wherein the DRB designated in the QFI or the indicator is either the specific DRB or the default data DRB.

8. The method of Claim 1, further comprises:transmitting, by the processor, a capability indication to the network node, wherein the capability indication is comprised in a radio resource control (RRC) message.

9. The method of Claim 1, further comprises:reserving, by the processor, a preamble of an uplink signal to indicate that at least one of a data collection process, an inference process, a functionality indicated in the data collection configuration, and forwarding of the PDU is inapplicable or applicable; andtransmitting, by the processor, the uplink signal to the network node.

10. The method of Claim 8, wherein the transmission is a configured grant (CG)-small data transmission (SDT) transmission or a random access-based (RA)-SDT transmission, and wherein the capability indication indicates at least one of a data collection process, an inference process, a functionality indicated in the data collection configuration, and forwarding of the PDU is inapplicable or applicable.

11. The method of Claim 8, wherein the capability indication is comprised in a user assistance information (UAI) of the RRC message, or wherein the RRC message is an RRC reconfiguration complete message or an RRC resume request message.

12. The method of Claim 1, further comprises:transmitting, by the processor, a first availability indication to the network node, wherein the first availability indication is comprised in a radio resource control (RRC) message.

13. The method of Claim 12, wherein the first availability indication comprises at least one of that:data of the PDU is available;a cause of triggering the first availability indication;data size of the PDU;a quality of service (QoS) flow identifier (QFI);a low power indication; andan associated cell, an associated frequency, or an associated area has availability of a functionality indicated in the at least one functionality configuration.

14. The method of Claim 12, wherein the first availability indication is transmitted to forward the PDU in an inactive state in a case that a first condition is met, wherein the transmission is a configured grant (CG)-small data transmission (SDT) transmission or a random access-based (RA)-SDT transmission, and wherein the first condition comprises at least one of that:a buffer of the apparatus is full;a used capacity of the buffer is greater than a first threshold;a reference signal received power (RSRP) of a received reference signal exceeds a second threshold; a running time of a CG-SDT timer or an RA-SDT timer is less than a third threshold;a power level of the apparatus is lower than a fourth threshold;at least one data radio bearer (DRB) associated with a functionality meets validity of the CG-SDT transmission or the RA-SDT transmission;an area identifier (ID) or a tracking ID is changed; andthere is remaining data after part of the PDU is forwarded or reported.

15. The method of Claim 14, further comprises:transmitting, by the processor, a second availability indication to the network node in a case that a second condition is met, wherein the second condition comprises at least one of that:a camped cell is changed;a prohibit timer is not running;a reconfigured data collection configuration is received; andan RRC resume request message is transmitted.

16. The method of Claim 1, further comprises:receiving, by the processor, an indication from the network node; anddisabling, by the processor, a hybrid automatic repeat request (HARQ) process for a functionality in the at least one functionality configuration according to the indication.

17. The method of Claim 1, further comprises:receiving, by the processor, a plurality of configured grant (CG) -small data transmission (SDT) configurations from the network node, wherein the CG-SDT configurations are linked with the at least one reporting configuration; andwherein the PDU is forwarded to the network node according to the at least one reporting configuration and the linked CG-SDT configurations.

18. The method of Claim 1, further comprises:transmitting, by the processor, a physical layer profile via the transmission to the network node; andperforming, by the processor, a subsequent transmission according to the physical layer profile .

19. The method of Claim 18, wherein the physical layer profile is transmitted via user assistance information (UAI) or a medium access control (MAC) control element (CE), and the transmission and the subsequent transmission are small data transmission (SDT) transmissions, and wherein the physical layer profile comprises at least one of a modulation and coding scheme (MCS), a multiple inputs multiple outputs (MIMO) layers, a time domain resource allocation (TDRA) or frequency domain resource allocation (FDRA), and a transmission power.

20. The method of Claim 1, further comprises:performing, by the processor, at least one of a data collection process, an inference process, and a reporting process according to the data collection configuration in a case that the apparatus is in an inactivestate, wherein the data collection process or the inference process is performed based on the at least one resource set configuration and the at least one functionality configuration, and wherein the PDU is generated according to the at least one of the data collection process, the inference process, and the reporting process.

21. The method of Claim 1, further comprises:receiving, by the processor, a radio resource control (RRC) release message from the network node, wherein the RRC release message comprises a suspend configuration, and the suspend configuration comprises a configured grant (CG)-small data transmission (SDT) configuration and the data collection configuration;transiting, by the processor, the apparatus from a connected state to an inactive state; and performing, by the processor, a CG-SDT transmission to forward the PDU to the network node via the PDU session according to the CG-SDT configuration.

22. The method of Claim 21, further comprises:including, by the processor, a capability indication in an RRC resume request message, wherein the capability indication indicates at least one of a data collection process, an inference process, a functionality indicated in the at least one functionality configuration, and forwarding of the PDU is inapplicable or applicable; andtransmitting, by the processor, the RRC resume request message to the network node via a subsequent CG-SDT transmission.

23. The method of Claim 21, further comprises:determining, by the processor, whether a third condition is met after the apparatus is transited to the inactive state, wherein the third condition comprises at least one of that:a reference signal received power (RSRP) of a synchronization signal block (SSB) is greater than a fifth threshold; anda time advance value is valid;including, by the processor, a capability indication in an RRC resume request message in an event that the third condition is met, wherein the capability indication indicates at least one of a data collection process, an inference process, a functionality indicated in the at least one functionality configuration, and forwarding of the PDU is inapplicable or applicable; andtransmitting, by the processor, the RRC resume request message to the network node via a subsequent CG-SDT transmission in an event that the third condition is met.

24. The method of Claim 21, further comprises:receiving, by the processor, an RRC reconfiguration message from the network node, wherein the RRC reconfiguration message comprises a first data collection configuration;determining, by the processor, a second data collection configuration according to the first data collection configuration; andtransmitting, by the processor, an RRC reconfiguration complete message to the network node before receiving the RRC release message or performing a subsequent CG-SDT transmission, or afterperforming the CG-SDT transmission, wherein the RRC reconfiguration complete message comprises a capability indication and the second data collection configuration.

25. A method, comprising:determining, by a processor of a network node, at least one resource set configuration, at least one functionality configuration, and at least one reporting configuration;including, by the processor, the at least one resource set configuration, the at least one functionality configuration, and the at least one reporting configuration in a radio resource control (RRC) message; and transmitting, by the processor, the RRC message to a user equipment (UE).

26. The method of Claim 25, wherein the at least one resource set configuration, the at least one functionality configuration, and the at least one reporting configuration are included in a suspend configuration, and wherein the RRC message is an RRC release message comprising the suspend configuration.

27. The method of Claim 26, further comprises:determining, by the processor, a configured grant (CG)-small data transmission (SDT) configuration for a CG-SDT transmission;including, by the processor, the CG-SDT configuration in the suspend configuration; and receiving, by the processor, a protocol data unit (PDU) from the UE via the CG-SDT transmission.

28. The method of Claim 25, further comprises:receiving, by the processor, an RRC resume request message from the UE via a subsequent transmission, wherein the RRC resume request message comprises a capability indication, and the capability indication indicates at least one of a data collection process, an inference process, a functionality indicated in the at least one functionality configuration, and reporting for the data collection process or the inference process is inapplicable or applicable.

29. The method of Claim 27, further comprises:including, by the processor, at least one designated resource set configuration, at least one designated functionality configuration, and at least one designated reporting configuration in a first data collection configuration;transmitting, by the processor, an RRC reconfiguration message to the UE, wherein the RRC reconfiguration message comprises the first data collection configuration; andreceiving, by the processor, an RRC reconfiguration complete message from the UE before transmitting the RRC release message or a subsequent CG-SDT transmission, or after the CG-SDT transmission, wherein the RRC reconfiguration complete message comprises a capability indication and a second data collection configuration, wherein the at least one resource set configuration, the at least one functionality configuration, and the at least one reporting configuration is determined according to the second data collection configuration.

30. The method of Claim 27, further comprises:receiving, by the processor, an availability indication associated with the PDU, wherein the availability indication comprises at least one of that:data of the PDU is available;a cause of triggering the availability indication;data size of the PDU;a quality of service (QoS) flow identifier (QFI);a low power indication; andan associated cell, an associated frequency, or an associated area has availability of a functionality indicated in the suspend configuration.

31. The method of Claim 25, further comprises:determining, by the processor, that a quality of service (QoS) flow identifier (QFI) or an indicator for a functionality in the at least one functionality configuration, wherein the QFI or the indicator is associated with either a specific data radio bearer (DRB), a default DRB, or a default data DRB; and including, by the processor, the QFI or the indicator in the functionality configuration.

32. The method of Claim 25, further comprises:determining, by the processor, a quality of service (QoS) flow identifier (QFI) for a connected state or an inactive state and a QFI for an idle state for a functionality in the at least one functionality configuration, wherein each of the QFI for the connected state or the inactive state and the QFI for the idle state is associated with either a specific data radio bearer (DRB) or a default data DRB;including, by the processor, the QFI for the connected state or the inactive state in the suspend configuration; andtransmitting, by the processor, the QFI for the idle state to the UE via system information.

33. The method of Claim 25, further comprises:determining, by the processor, a plurality of quality of service (QoS) flow identifiers (QFIs) and a plurality of thresholds for a functionality in the at least one functionality configuration, wherein the plurality of QFIs is associated with either a specific data radio bearer (DRB), a default DRB, or a default data DRB; andincluding, by the processor, the plurality of QFIs and the plurality of thresholds in the suspend configuration.

34. The method of Claim 25, wherein the at least one reporting configuration comprises at least one of that:a periodicity that the UE needs to monitor a control signaling used to schedule uplink (UL) resources for reporting;a periodicity that the UE is granted with UL resources for reporting;physical resources used to monitor the control signaling used to schedule the UL resources for reporting; andphysical resources for the UE transmitting an UL signal for UL resources request for reporting