Method and apparatus for configuring applicability reporting in a wireless communication system

Abstract

A method for configuring applicability reporting between a network node and a user equipment (UE) is provided. The method includes sending configuration information from the network node to the UE, the configuration information including one or more configurations associated with a full configuration for reasoning and a partial configuration for applicability reporting; determining, at the UE, whether the configurations are applicable for reasoning; and reporting, from the UE to the network node, applicability information indicating one or more applicable configurations.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 753,666, filed February 4, 2025, and U.S. Provisional Application No. 63 / 801,260, filed May 7, 2025, the disclosures of which are incorporated herein by reference in their entirety as if fully set forth herein. Technical Field

[0003] This disclosure generally relates to wireless communication systems. More specifically, the subject matter disclosed herein relates to improvements to configuring applicability reporting for AI / ML-based inference operations in user equipment (UE). Background Technology

[0004] Wireless communication systems typically employ configuration signaling between network nodes and UEs to manage reporting and inference operations. Machine learning (ML) and artificial intelligence (AI) capabilities are increasingly being integrated into such systems to enhance link adaptation, beam management, and performance prediction.

[0005] To support these operations, some systems use standardized configuration messages, such as Channel State Information (CSI) report configuration, which enables the network to obtain feedback from the UE for beam selection and link maintenance.

[0006] One problem with the above approach is that existing configuration frameworks do not distinguish between configurations used for applicability reporting and configurations used for inference, which can lead to inefficiency or ambiguity in determining whether and when a particular report should be activated. Summary of the Invention

[0007] To overcome these problems, this paper describes a system and method for configuring suitability reports between network nodes and UEs using one or more configuration formats associated with full and partial configurations, determining suitability based on received information, and selectively activating reporting functionality based on suitability determination.

[0008] The above methods improve upon previous approaches because they provide flexible control over reporting behavior, reduce unnecessary signaling, and allow for consistent coordination between applicability reporting and inference configuration without modifying the existing reporting structure.

[0009] In one embodiment, a method for configuring an applicability report between a network node and a UE includes: sending configuration information from the network node to the UE, the configuration information including one or more configurations associated with a full configuration for inference and a partial configuration for applicability reporting; determining at the UE whether the configuration is applicable to inference; and reporting applicability information from the UE to the network node indicating one or more applicable configurations.

[0010] In one embodiment, an electronic device configured for applicability reporting includes: a transceiver configured to transmit and receive wireless signals with a network node; and a controller operatively connected to the transceiver and configured to: receive configuration information from the network node, the configuration information including one or more configuration formats associated with a full configuration for inference and a partial configuration for applicability reporting; determine, based on the configuration information, whether an applicability report is required; transmit applicability information indicating one or more applicable configurations to the network node; and activate a reporting function associated with the full configuration when the applicability of the full configuration is indicated.

[0011] In one embodiment, a non-transitory computer-readable medium storing instructions that, when executed by a processor of a UE, cause the processor to perform a method for configuring an applicability report, the method comprising: sending applicability information from the UE to a network node indicating one or more applicable configurations; receiving configuration information at the UE from the network node, the configuration information including one or more configuration formats associated with a full configuration for reasoning and a partial configuration for applicability reporting; determining, based on the configuration information, whether an applicability report is required; and activating a reporting function associated with the full configuration when the applicability of the full configuration is indicated. Attached Figure Description

[0012] In the following sections, aspects of the subject matter disclosed herein will be described with reference to exemplary embodiments shown in the accompanying drawings, wherein:

[0013] Figure 1 This is a diagram illustrating an example wireless communication system including a network node and a UE according to an embodiment;

[0014] Figure 2 This is a diagram illustrating an example signaling process for configuring an applicability report between a network node and a UE according to an embodiment;

[0015] Figure 3 This is a diagram illustrating an example single-format configuration for an applicability report according to an embodiment;

[0016] Figure 4 This is a diagram illustrating an example dual-format configuration for an applicability report according to an embodiment;

[0017] Figure 5 This is a flowchart illustrating an example UE-side process for activation, reactivation, and applicability changes according to an embodiment; and

[0018] Figure 6 This is a block diagram of an electronic device in a network environment according to an embodiment. Detailed Implementation

[0019] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of this disclosure. However, those skilled in the art will understand that the disclosed aspects can be practiced without these specific details. In other instances, well-known methods, processes, components, and circuits have not been described in detail so as not to obscure the subject matter of this disclosure.

[0020] Throughout this specification, references to "an embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in connection with that embodiment may include in at least one embodiment disclosed herein. Therefore, the phrases "in one embodiment," "in an embodiment," or "according to an embodiment" (or other phrases with similar meanings) appearing in various places throughout this specification may not necessarily refer to the same embodiment. Furthermore, particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In this regard, as used herein, the term "exemplary" means "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" should not be construed as necessarily preferred or advantageous over other embodiments. Additionally, particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Moreover, depending on the context discussed herein, singular terms may include corresponding plural forms, and plural terms may include corresponding singular forms. Similarly, hyphenated terms (e.g., "two-dimensional", "predetermined", "pixel-specific", etc.) may occasionally be used interchangeably with their corresponding unhyphenated versions (e.g., "two-dimensional", "predetermined", "pixel-specific", etc.), and uppercase entries (e.g., "counter clock", "line selection", "pixel output", etc.) may be used interchangeably with their corresponding non-uppercase versions (e.g., "counter clock", "line selection", "pixel output", etc.). This occasional interchangeability should not be considered as inconsistency between them.

[0021] Furthermore, depending on the context discussed herein, singular terms may include corresponding plural forms, and plural terms may include corresponding singular forms. It should also be noted that the various figures shown and discussed herein (including component drawings) are for illustrative purposes only and are not drawn to scale. For example, the dimensions of some elements may be enlarged relative to others for clarity. Additionally, reference numerals are repeated in the figures where appropriate to indicate corresponding and / or similar elements.

[0022] The terminology used herein is for the purpose of describing some exemplary embodiments only and is not intended to limit the claimed subject matter. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that, when used in this specification, the terms “comprising” and / or “including” specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or combinations thereof.

[0023] It will be understood that when an element or layer is referred to as being on, "connected to," or "coupled to" another element or layer, the element or layer may be directly on, directly connected to, or directly coupled to the other element or layer, or there may be intermediate elements or layers. Conversely, when an element is referred to as being "directly on," "directly connected to," or "directly coupled to" another element or layer, there are no intermediate elements or layers. The same reference numerals always denote the same elements. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0024] As used herein, the terms “first,” “second,” etc., serve as labels for nouns that follow them and do not imply any kind of ordering (e.g., spatial, temporal, logical, etc.) unless explicitly defined as such. Furthermore, the same reference numerals may be used in two or more figures to refer to parts, components, blocks, circuits, units, or modules having the same or similar functions. However, this usage is merely for simplicity of description and ease of discussion; it does not imply that the construction or architectural details of these components or units are identical in all embodiments, or that these commonly referenced parts / modules are the only way to implement some of the exemplary embodiments disclosed herein.

[0025] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this subject pertains. It will be further understood that terms such as those defined in commonly used dictionaries shall be interpreted as having the same meaning as their meaning in the context of the relevant field, and shall not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0026] As used herein, the term "module" means any combination of software, firmware, and / or hardware configured to provide the functionality described herein in conjunction with modules. For example, software may be embodied as a software package, code, and / or instruction set or instructions, and the term "hardware" as used in any implementation described herein may, for example, individually or in any combination, include assemblies, hardwired circuitry, programmable circuitry, state machine circuitry, and / or firmware storing instructions executed by programmable circuitry. Modules may be embodied collectively or individually as circuitry forming part of a larger system, such as, but not limited to, integrated circuits (ICs), system-on-a-chip (SoCs), assemblies, etc.

[0027] As used herein, “suitability report” can refer to a process by which a UE notifies a network node whether the operation or reporting format of one or more configurations is suitable under current network or device conditions. Examples of a “suitability report” may include: a UE sending an indication from the network node of the suitability of a configuration used in CSI reporting, inference-based measurement, or other network control reporting functions; or updating the suitability status in response to performance changes, configuration updates, or reactivation triggers. As used herein, “user equipment” can refer to a wireless communication device configured to transmit, receive, or process signals communicating with a network node. Examples of “user equipment” may include smartphones, tablets, laptops, wearable devices, vehicle terminals, or any other electronic device capable of performing wireless communication functions such as suitability reporting, channel measurement, or inference-based data transmission. As used herein, “network node” can refer to a communication device used to manage wireless connectivity, transmit control information, and coordinate signaling with one or more UEs in a wireless communication system. Examples of “network node” may include base stations, access points (APs), gNodeBs (gNBs), eNodeBs (eNBs), or any other network-side device capable of transmitting configuration information, receiving suitability reports, and controlling the activation or reactivation of reporting functions. As used in this document, "configuration information" can refer to control data sent from a network node to the UE to define parameters, formats, or conditions for performing specific operations or reporting functions. Some examples of "configuration information" may include CSI report configuration, inference-related configuration formats, applicability reporting parameters, identifiers linking multiple configuration formats, or activation and reactivation indicators used to manage applicability reporting behavior.

[0028] As used herein, "full configuration for inference" can refer to a set of parameters or instructions that enable the UE to perform full inference or measurement operations based on configuration data provided by the network. Examples of "full configuration for inference" may include configurations defining resources, reporting periodicity, measurement types, and processing parameters for CSI reporting, beam prediction, or other AI / ML-based inference functions utilizing full network and device resources. "Partial configuration for suitability reporting" as used herein can refer to a subset of configuration parameters provided by the network node to the UE to determine and report whether the corresponding full configuration is suitable under current operating conditions. Examples of "partial configuration for suitability reporting" may include configurations specifying suitability reporting triggers, thresholds, or identifiers linked to the full configuration for inference, such as the CSI-ReportConfig (Channel State Information - Report Configuration) format used to indicate suitability status or initiate a reactivation process. "Suitability information" as used herein can refer to messages / information sent from the UE to the network node indicating whether one or more configurations provided by the network node are currently suitable for reporting or inference operations. Examples of “applicability information” may include a bitmask indicating an applicable configuration index, a list of identifiers or message elements, an applicability status flag associated with a full or partial configuration, or a reactivation indication sent by the UE to update the applicability status of a previously configured reporting function. As used herein, “reporting function” may refer to an operational procedure or module within the UE that performs measurement, inference, or applicability-related information transmission to network nodes based on configured parameters. Examples of “reporting function” may include periodic CSI reporting procedures, event-triggered inference result transmission, or applicability status update functions that are activated, deactivated, or reactivated in response to configuration information or network control signaling.

[0029] As used herein, "single configuration format" can refer to a unified configuration structure that includes parameters for inference operations and suitability reports within the same format sent from the network node to the UE. Examples of a "single configuration format" may include a combined configuration message defining full configuration parameters for inference and partial configuration parameters for suitability reporting, such as the unified CSI-ReportConfig format, which allows the UE to determine suitability and activate reporting without a separate configuration message. "First configuration format for full configuration" as used herein can refer to a configuration structure sent from the network node that defines the parameters required to perform full inference or reporting operations at the UE. Examples of a "first configuration format for full configuration" may include a CSI-ReportConfig that defines measurement resources, reporting periodicity, and reference signal configurations, or inference-related configurations that specify processing parameters and activation conditions used by the UE to perform full inference or measurement reporting. "Second configuration format for partial configuration" as used herein can refer to a configuration structure sent from the network node to the UE that defines parameters for suitability reporting or for determining whether a corresponding full configuration is suitable. Examples of a “second configuration format for partial configuration” may include set-InferenceConfig or other signaling formats that specify an identifier for triggering applicability reports, linking to the corresponding full configuration, or a threshold used by the UE to evaluate and report applicability status to network nodes. As used herein, “AI” can refer to artificial intelligence techniques that enable devices or systems to perform tasks or make decisions based on learned patterns, data analysis, or predictive modeling. Examples of “AI” may include machine learning algorithms for beam prediction, channel estimation, interference management, or inference-based reporting operations performed by a UE or network node in a wireless communication system. As used herein, “ML” can refer to machine learning processes that enable devices or systems to improve their performance or decision-making by training on data and identifying relationships between input and output parameters. Examples of “ML” may include supervised, unsupervised, or reinforcement learning models applied to wireless communication tasks such as channel state prediction, beam selection, signal quality estimation, or determining the applicability of inference-based reporting in a UE or network node.

[0030] This disclosure relates to techniques for configuring suitability reporting between a network node and a UE in a wireless communication system supporting AI / ML-based inference operations. In one example, configuration information sent from the network node to the UE may include one or more configuration formats associated with a full configuration for inference and a partial configuration for suitability reporting. The UE may determine whether suitability reporting is required based on the received configuration information and report suitability information to the network node indicating one or more applicable configurations. Based on the suitability indication, the UE can selectively activate reporting functionality associated with the full configuration.

[0031] In some embodiments, full and partial configurations may be represented by a single configuration format that includes parameters for both inference and suitability reporting, while in other embodiments, separate configuration formats may be adopted and linked using identifiers or associated fields. The UE may also reactivate previously deactivated configurations in response to a reactivation indication from a network node and may determine suitability changes based on performance monitoring events that meet threshold conditions. These methods allow for flexible and efficient management of suitability reporting, supporting accurate and adaptive coordination between AI / ML-based inference capabilities and network control processes.

[0032] Figure 1 An example communication system is shown that may include a UE 105 and a network node or gNB 110 communicating with each other. The UE 105 may include a radio 115 and processing circuitry (or means for processing) 120, which may be configured to perform one or more of the methods described herein, such as... Figure 2 The method illustrated herein. Processing circuitry 120 may receive configuration information and other signaling from network node 110 via radio 115, and may send suitability information or other uplink signaling to network node 110 via radio 115.

[0033] Figure 2 This is a signaling diagram illustrating an example process for configuring an suitability report between a network node 110 (e.g., a base station, gNB, or another access node) and a UE 105 according to an embodiment. The illustrated process may include a series of signaling exchanges that enable the network node 110 and the UE 105 to establish and activate a suitability report based on configuration information. Although four operations (205-220) are shown, the order of these operations may vary in other embodiments, and one or more operations may be combined, repeated, or omitted depending on network configuration or implementation constraints. While this example relates to configuration information for a suitability report associated with ML or inference operations, the same principles can be applied to other types of measurement or reporting functions.

[0034] In step 205, network node 110 may send configuration information to UE 105 to support applicability reporting. The configuration information may include one or more configuration formats identifying parameters used for inference operations (full configuration) and parameters used for applicability reporting (partial configuration). Sending may occur via higher-level control signaling such as RRC reconfiguration or another dedicated configuration message. Each configuration format may specify the reporting period, activation conditions, or measurement context associated with the inference or reporting function.

[0035] In some embodiments, configuration information is represented by a single format including fields for both inference parameters and applicability reporting parameters. For example, a single CSI-ReportConfig may contain flags or subfields that explicitly indicate whether an applicability report is required. Alternatively, UE 105 may implicitly determine the need for an applicability report based on characteristics of the received configuration, such as the presence of inference-related identifiers, resource assignments, or predefined parameter values. This single-format embodiment allows network node 110 to signal inference setup and applicability reporting requirements within a unified configuration structure.

[0036] In other embodiments, the configuration information may include two separate formats, such as set-InferenceConfig for applicability reports and CSI-ReportConfig for the full configuration used for inference. These two formats can be linked via an identifier field or another reference parameter, allowing UE 105 to determine the full configuration for inference corresponding to each applicability report format. Network node 110 can send these formats together or separately, providing flexibility in how applicability reports are activated and reactivated later.

[0037] The configuration information may also include control attributes defining when or how the applicability report is executed, such as timer values, periodicity, threshold conditions, or event triggering. Network node 110 may optionally include these attributes, depending on whether the applicability report is expected to be executed immediately upon configuration reception or only after UE 105 has confirmed the configuration is applicable. The transmission in step 205 may occur during initial setup or reconfiguration, or when network node 110 provides updated inference parameters.

[0038] In step 210, UE 105 may determine whether an applicability report is required based on configuration information received from network node 110. This operation is performed by processing circuitry 120 of UE 105 and may depend on parameters or indicators included in the configuration information sent in step 205. The applicability determination enables UE 105 to identify which configurations in one or more received formats will be considered active for inference or measurement reporting.

[0039] In one embodiment, UE 105 can explicitly determine applicability based on fields or flags included in the received configuration. For example, the configuration format may contain explicit information elements indicating whether an applicability report is required for the associated full configuration. In this case, UE 105 can directly interpret this indicator as an instruction from network node 110 to activate the corresponding applicability reporting function.

[0040] In another embodiment, UE 105 can implicitly determine applicability by evaluating contextual information, such as the presence or absence of inference-related parameters, resource assignments, or scheduling references in the configuration. For example, when network node 110 omits fields associated with inference activation and only provides reporting-related parameters, UE 105 can infer that the configuration corresponds to a partial configuration for applicability reporting. Conversely, when both inference and reporting parameters are provided, UE 105 can interpret the configuration as a complete configuration indicating that an applicability report is expected to be performed.

[0041] In some embodiments, UE 105 can evaluate multiple configuration formats, such as set-InferenceConfig and CSI-ReportConfig, to determine their relationship and whether an applicability report applies to one or both of them. UE 105 can use identifiers or association fields provided in the partial configuration to match it with the corresponding full configuration. Based on this association, UE 105 can determine which configurations should be considered applicable and which configurations should remain inactive until acknowledged.

[0042] The determination process may further incorporate local performance information or historical inference results maintained by UE 105. For example, if UE 105 observes recurring failure conditions associated with a given configuration (e.g., poor beam prediction accuracy or unstable channel estimation), the UE may determine that the configuration is temporarily unsuitable and prevent suitability reporting until the conditions improve. Conversely, when the most recent measurement meets the suitability threshold, UE 105 may determine that the configuration has become suitable and is ready to send suitability information to network node 110.

[0043] In step 215, UE 105 may send applicability information to network node 110. The applicability information identifies one or more configurations that the UE has determined to be applicable based on the evaluation performed in step 210. Reports can be transmitted using uplink control signaling such as dedicated RRC messages, MAC control elements, or Physical Uplink Control Channel (PUCCH) reports. In one example, the applicability information includes a bitmask, index list, or identifier value corresponding to the configuration format previously provided by network node 110. This information enables network node 110 to understand which configurations the UE will actively use for subsequent reporting or inference operations.

[0044] In some embodiments, UE 105 may send applicability information immediately after receiving a partial configuration. This behavior corresponds to the partial configuration mode, where an applicability report is performed without first activating the full configuration. Therefore, UE 105 can indicate the applicability of one or more candidate configurations even before the full inference setup is completed. In other embodiments, UE 105 may send applicability information only after confirming the applicability of the full configuration, for example, by including an applicability indicator within the reconfiguration completion message.

[0045] In embodiments using two separate configuration formats, UE 105 can report the applicability of both CSI-ReportConfig and set-InferenceConfig, even if set-InferenceConfig is provided for applicability reporting. For example, UE 105 may include fields indicating the applicability of CSI-ReportConfig when linked to a specific set-InferenceConfig. UE 105 can also report a change in the applicability of either format if the applicability status has changed (e.g., due to channel changes or updated performance metrics). Network node 110 selects which format to use for applicability reporting; that is, the network indicates whether CSI-ReportConfig or set-InferenceConfig is used for applicability reporting.

[0046] The suitability information may also include auxiliary fields specifying the reasons or criteria for determining suitability. For example, UE 105 may indicate that the configuration is suitable because the measured beam prediction accuracy value or received signal strength exceeds a threshold. In other examples, the UE may report a counter value representing the number of successful measurements or valid inference outputs. This optional information allows network node 110 to better understand the basis of the UE's suitability report and adjust the configuration criteria in future updates.

[0047] In an alternative embodiment, UE 105 may combine suitability information for multiple configurations into a single report. This approach can reduce signaling overhead when many configurations are active or under evaluation. In some cases, UE 105 may send suitability information periodically or, as determined in step 210, when a significant change in suitability status is detected.

[0048] In step 220, when the applicability of the configuration is indicated, UE 105 can activate the reporting function associated with the full configuration. This activation can be triggered directly by UE 105, by a control instruction from network node 110, or by a combination of both. Once activated, the reporting function enables UE 105 to perform periodic or event-based transmission of measurement or inference results based on parameters defined in the full configuration. Activation ensures that reporting operations occur only for configurations that UE 105 has determined to be applicable, thereby avoiding unnecessary signaling and saving processing resources.

[0049] In one embodiment, UE 105 may activate the reporting function immediately upon receiving configuration information corresponding to a partial configuration. This behavior corresponds to a partial configuration mode, where the UE immediately begins applicability reporting and subsequently switches to full reporting upon confirmation of applicability. In another embodiment, UE 105 may activate the reporting function only after indicating applicability to network node 110 (e.g., after sending applicability information in step 215). In this case, network node 110 may send an explicit confirmation or activation command to confirm that the corresponding full configuration should be activated.

[0050] In some embodiments, network node 110 may further send an explicit activation or reactivation indication after receiving the applicability information. Such an indication may be a new RRC information element or a dedicated control signal that identifies which configurations should transition to an active state. Alternatively, UE 105 may activate the reporting function when its internal applicability criteria are met, without waiting for a separate command. The activation indication may also specify whether the activation is initial or a reactivation corresponding to a previously deactivated configuration.

[0051] After activation, UE 105 can periodically perform reporting operations or measurements defined by the full configuration (e.g., periodic CSI reporting, beam prediction updates, or inference output signaling). UE 105 can continue to monitor performance or channel conditions to determine if the configuration is still applicable. If a degradation event or counter threshold is detected, UE 105 can suspend or deactivate the reporting function until reactivation criteria are met. Network node 110 can also release the inactive configuration or replace it with a new configuration with updated parameters.

[0052] Figure 2 The process illustrates an example signaling flow that enables network node 110 and UE 105 to configure and activate applicability reporting in a flexible manner. Depending on the implementation, the configuration information in step 205 can be represented in a single or multiple formats, and UE 105 can use explicit or implicit signaling to determine, report, and activate applicability. (Refer to...) Figure 3 and Figure 4Another example of a configuration structure that supports these operations is described.

[0053] Figure 3 This is a block diagram illustrating an example single-format configuration for applicability reporting according to an embodiment. As shown, UE 105 can receive configuration format 320 from a network node (e.g., gNB). Configuration format 320 may include parameters corresponding to a full configuration for reasoning and a partial configuration for applicability reporting. Within UE 105, configuration format 320 may be processed by parser 305, applicability logic 310, and reporting unit 315, which operate together to determine and report the applicability of the received configuration.

[0054] Parser 305 can receive and decode configuration format 320. In some embodiments, parser 305 can extract inference-related parameters and applicability report parameters from the uniform structure. The extracted information can be provided to applicability logic 310, which determines whether an applicability report is required. Applicability logic 310 can explicitly determine applicability based on flags or indicators included in configuration format 320, or implicitly determine applicability based on the presence or absence of certain configuration parameters or internal operating conditions. When applicability is indicated, applicability logic 310 enables reporting unit 315 to initiate or update an applicability report operation.

[0055] Reporting unit 315 can send applicability information to network nodes and subsequently activate reporting functions associated with full configuration when applicability is confirmed. This single-format implementation enables UE 105 to use a unified configuration structure to handle inference and applicability parameters, thereby reducing signaling overhead and simplifying configuration management.

[0056] Figure 4 This is a signaling diagram illustrating an example dual-format configuration for applicability reporting according to an embodiment. As shown, network node 110 can send a first configuration format 405 and a second configuration format 410 to UE 105. The first configuration format 405 may correspond to a full configuration for inference, while the second configuration format 410 may correspond to a partial configuration for applicability reporting. These two configuration formats can be linked to each other by an identifier, enabling UE 105 to determine which partial configuration is associated with which full configuration.

[0057] In one embodiment, the first configuration format 405 may include parameters defining a full configuration for inference, such as channel measurement resources, reporting periodicity, and activation conditions. The second configuration format 410 may include applicability-related parameters, such as applicability report triggering, thresholds, or identifiers. Association fields within the second configuration format 410 may reference the first configuration format 405, thereby allowing the UE 105 to identify that the two configurations are related. Therefore, the UE 105 can determine whether to perform an applicability report for a specific full configuration based on the association between the two formats.

[0058] In another embodiment, network node 110 may send the first configuration format and the second configuration format together in a single configuration message, or send them separately at different times. When sent together, UE 105 can immediately interpret the association between them. When sent separately, UE 105 may temporarily store the first configuration format 405 and later link it to the second configuration format 410 when a shared identifier is detected. This dual-format approach allows network node 110 to independently configure inference and applicability reports.

[0059] Figure 4 The dual-format configuration shown provides more than Figure 3 The single-format implementation offers greater flexibility because it allows network node 110 to adjust its applicability reporting behavior without reconfiguring the full inference settings. See later. Figure 5 Describe the corresponding procedures for activating and reactivating such configurations.

[0060] In some embodiments, reference Figure 4 The described dual-format and hybrid-format configurations can be represented using explicit higher-level signaling structures. These signaling structures enable network nodes to configure applicability reporting and inference operations using a uniform format, a single format, or a hybrid format (where each configuration element specifies which format it uses). Examples of such signaling structures are shown in Table 1 below.

[0061] Table 1

[0062]

[0063] Alternatively, signaling can support mixed-format operation, where each configuration element indicates whether to use full-CSI-ReportConfig or set-InferenceConfig. This allows network nodes to flexibly combine applicability-reporting structures and inference-related structures within the same configuration framework.

[0064] Table 2

[0065]

[0066] These signaling examples demonstrate how network nodes can use a single uniform structure, two separate structures, or a combination thereof to specify applicability reporting and inference-related parameters. The UE can decode these formats to identify the corresponding applicability-reporting requirements, infer the correlation between full and partial configurations, and activate or update reporting behavior accordingly. These signaling examples can be used in conjunction with the CSI-ReportConfig structure described below.

[0067] In some embodiments, the electronic device can use structured configuration parameters to process inference-based CSI reports. These parameters specify how the device selects, measures, and reports channel state information and inference-related metrics. These parameters can be represented using a configuration sequence referred to herein as CSI-ReportConfig, which defines resource associations, measurement resource sets, CSI reference signal configuration, and inference-related elements for generating inference frames or IFCs. CSI-ReportConfig enables the UE to interpret signaling provided by the network, determine applicable measurement and reporting resources, and generate appropriate inference data to be sent to network nodes.

[0068] Table 3 below shows an example of this configuration structure. The structure includes Part A and Part B, where Part A describes the CSI configuration parameters related to inference, and Part B describes an optional set of inference-related parameters used to extend the reporting mode. Although an example is shown, depending on the implementation, the configuration may include additional fields, fewer fields, or alternative field definitions.

[0069] Table 3

[0070]

[0071] The CSI-ReportConfig structure provides explicit definitions of the measurement resources, interference resources, and inference parameter sets associated with IFC generation. When the UE receives signaling referencing these fields, it can use identifiers to select the appropriate resource set from a configuration provided by memory or the network, thereby determining which CSI-RS resources, interference measurement resources, or inference parameter sets are suitable for the current reporting time. Therefore, this configuration structure can be used as input to the methods described herein, including the generation, encoding, and reporting of inference frames.

[0072] Figure 5 This is a flowchart illustrating an example process for activating and reactivating an applicability report at UE 105 according to an embodiment. It can be implemented as follows: Figure 2-4The process described herein is executed after the initial configuration suitability report. This process enables UE 105 to monitor suitability conditions, detect changes in status, and trigger the activation or reactivation of the corresponding configuration when specific criteria are met.

[0073] In step 505, UE 105 may begin monitoring one or more performance conditions related to configuration suitability. The monitored conditions may include beam prediction accuracy, received signal strength, channel quality indicators, or counter values ​​indicating repeated measurement failures. UE 105 may maintain these parameters over time and compare them to thresholds stored locally or provided by network node 110.

[0074] At step 510, UE 105 can determine whether a change in applicability has occurred. This determination can be based on one or more monitoring parameters exceeding a threshold, or on a time-based or event-driven trigger. If UE 105 determines that no change has occurred, the process returns to step 505 and monitoring continues. If UE 105 detects that an applicability threshold has been met (e.g., improved beam stability or restored link quality), the process proceeds to step 520.

[0075] In step 520, UE 105 may send a reactivation indication to network node 110 to signal that a previously inactive or suspended configuration should be reactivated. In some embodiments, this indication is sent as an RRC or MAC-CE message identifying the configuration to be reactivated. In response, network node 110 may optionally send an acknowledgment or updated configuration message to complete the reactivation (step 525). In an alternative embodiment, UE 105 may autonomously reactivate the configuration without waiting for a network response. This mechanism allows the system to maintain accurate applicability and minimize signaling overhead when transitioning between inactive and active configurations.

[0076] Reference Figure 1-5 The described embodiments illustrate examples of systems and methods for configuring and managing suitability reports in wireless communication systems. By using a uniform or dual configuration format, explicit and implicit suitability determination, and controlled activation and reactivation procedures, the described methods achieve efficient coordination between network nodes and UEs. These techniques can reduce signaling overhead, improve adaptability to changing channel conditions, and provide consistent control over reporting behavior across different configuration types.

[0077] Figure 6 This is a block diagram of an electronic device in a network environment 600 according to an embodiment.

[0078] refer to Figure 6In network environment 600, electronic device 601 can communicate with electronic device 602 via a first network 698 (e.g., a short-range wireless communication network), or with electronic device 604 or server 608 via a second network 699 (e.g., a long-range wireless communication network). Electronic device 601 can communicate with electronic device 604 via server 608. Electronic device 601 may include processor 620, memory 630, input device 650, sound output device 655, display device 660, audio module 670, sensor module 676, interface 677, haptic module 679, camera module 680, power management module 688, battery 689, communication module 690, subscriber identification module (SIM) card 696, or antenna module 697. In one embodiment, at least one component (e.g., display device 660 or camera module 680) may be omitted from electronic device 601, or one or more other components may be added to electronic device 601. Some components may be implemented as a single integrated circuit (IC). For example, sensor module 676 (e.g., fingerprint sensor, iris sensor, or illuminance sensor) may be embedded in display device 660 (e.g., display).

[0079] The processor 620 can execute software (e.g., program 640) to control at least one other component (e.g., hardware or software component) of the electronic device 601 coupled to the processor 620, and can perform various data processing or calculations.

[0080] As at least part of data processing or computation, processor 620 can load commands or data received from another component (e.g., sensor module 676 or communication module 690) into volatile memory 632, process the commands or data stored in volatile memory 632, and store the resulting data in non-volatile memory 634. Processor 620 may include a main processor 621 (e.g., a central processing unit (CPU) or application processor (AP)) and an auxiliary processor 623 (e.g., a graphics processing unit (GPU), image signal processor (ISP), sensor hub processor, or communication processor (CP)), wherein the auxiliary processor 623 may operate independently of or in conjunction with the main processor 621. Additionally or alternatively, the auxiliary processor 623 may be adapted to consume less power than the main processor 621 or to perform specific functions. The auxiliary processor 623 may be implemented separately from or as part of the main processor 621.

[0081] When the main processor 621 is inactive (e.g., in sleep mode), the auxiliary processor 623 may replace the main processor 621 in controlling at least some of the functions or states associated with at least one component of the electronic device 601 (other than the main processor 621) (e.g., display device 660, sensor module 676, or communication module 690). Alternatively, when the main processor 621 is active (e.g., running an application), the auxiliary processor 623 may work with the main processor 621 to control at least some of the functions or states associated with at least one component of the electronic device 601 (e.g., display device 660, sensor module 676, or communication module 690). The auxiliary processor 623 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., camera module 680 or communication module 690) functionally associated with the auxiliary processor 623.

[0082] Memory 630 may store various data used by at least one component of electronic device 601 (e.g., processor 620 or sensor module 676). The various data may include, for example, software (e.g., program 640) and input or output data for commands associated with it. Memory 630 may include volatile memory 632 or non-volatile memory 634. Non-volatile memory 634 may include internal memory 636 and / or external memory 638.

[0083] The program 640 can be stored as software in the memory 630 and may include, for example, an operating system (OS) 642, middleware 644, or application 646.

[0084] Input device 650 can receive commands or data from outside electronic device 601 (e.g., a user) that will be used by another component of electronic device 601 (e.g., processor 620). Input device 650 may include, for example, a microphone, mouse, or keyboard.

[0085] The sound output device 655 can output sound signals to the outside of the electronic device 601. The sound output device 655 may include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as playing multimedia or recording, and the receiver can be used to receive incoming calls. The receiver can be implemented separately from the speaker or as part of the speaker.

[0086] Display device 660 can visually provide information to the outside of electronic device 601 (e.g., to a user). Display device 660 may include, for example, a display, a holographic device, or a projector, and control circuitry for controlling a respective one of the display, holographic device, and projector. Display device 660 may include touch circuitry adapted to detect touch, or sensor circuitry (e.g., a pressure sensor) adapted to measure the intensity of the force caused by touch.

[0087] Audio module 670 can convert sound into electrical signals and vice versa. Audio module 670 can acquire sound via input device 650, or output sound via sound output device 655 or headphones of external electronic device 602 directly (e.g., wired) or wirelessly coupled to electronic device 601.

[0088] Sensor module 676 can detect the operating state of electronic device 601 (e.g., power or temperature) or the environmental state outside electronic device 601 (e.g., user state), and then generate an electrical signal or data value corresponding to the detected state. Sensor module 676 may include, for example, a gesture sensor, gyroscope sensor, atmospheric pressure sensor, magnetic sensor, accelerometer, grip sensor, proximity sensor, color sensor, infrared (IR) sensor, biometric sensor, temperature sensor, humidity sensor, or illuminance sensor.

[0089] Interface 677 may support one or more specific protocols used to enable direct (e.g., wired) or wireless connection between electronic device 601 and external electronic device 602. Interface 677 may include, for example, a High Definition Multimedia Interface (HDMI), a Universal Serial Bus (USB) interface, a Secure Digital Card (SD) interface, or an audio interface.

[0090] Connection end 678 may include a connector through which electronic device 601 can be physically connected to external electronic device 602. Connection end 678 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0091] The haptic module 679 can convert electrical signals into mechanical stimulation (e.g., vibration or motion) or electrical stimulation that can be recognized by a user through touch or kinesthesia. The haptic module 679 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0092] Camera module 680 can capture still or moving images. Camera module 680 may include one or more lenses, an image sensor, an image signal processor, or a flash. Power management module 688 manages the power supply to electronic device 601. Power management module 688 may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

[0093] Battery 689 can supply power to at least one component of electronic device 601. Battery 689 may include, for example, a non-rechargeable primary battery, a rechargeable rechargeable battery, or a fuel cell.

[0094] Communication module 690 can support the establishment of a direct (e.g., wired) or wireless communication channel between electronic device 601 and external electronic devices (e.g., electronic device 602, electronic device 604, or server 608), and perform communication via the established communication channel. Communication module 690 may include one or more communication processors that can operate independently of processor 620 (e.g., AP), and supports direct (e.g., wired) or wireless communication. Communication module 690 may include wireless communication module 692 (e.g., cellular communication module, short-range wireless communication module, or Global Navigation Satellite System (GNSS) communication module) or wired communication module 694 (e.g., local area network (LAN) communication module or power line communication (PLC) module). One of these communication modules can communicate with an external electronic device via a first network 698 (e.g., a short-range communication network such as Bluetooth™, Wi-Fi Direct, or the Infrared Data Association (IrDA) standard) or a second network 699 (e.g., a long-range communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN))). These various types of communication modules can be implemented as a single component (e.g., a single IC) or as multiple components separate from each other (e.g., multiple ICs). The wireless communication module 692 can use user information (e.g., the International Mobile Subscriber Identity (IMSI)) stored in the user identification module 696 to identify and authenticate the electronic device 601 in the communication network (such as the first network 698 or the second network 699).

[0095] Antenna module 697 can transmit or receive signals or power to or from the outside of electronic device 601 (e.g., external electronic device). Antenna module 697 may include one or more antennas, from which at least one antenna suitable for a communication scheme used in a communication network (such as a first network 698 or a second network 699) can be selected, for example, by communication module 690 (e.g., wireless communication module 692). Signals or power can then be transmitted or received between communication module 690 and external electronic device via the selected at least one antenna.

[0096] Commands or data can be sent or received between electronic device 601 and external electronic device 604 via server 608 coupled to a second network 699. Each of electronic devices 602 and 604 can be a device of the same or different type as electronic device 601. All or some operations to be performed at electronic device 601 can be performed at one or more of the external electronic devices 602, 604, or 608. For example, if electronic device 601 is required to automatically perform a function or service, or in response to a request from a user or another device, electronic device 601 can request one or more external electronic devices to perform at least a portion of that function or service, rather than performing that function or service, or other than performing that function or service. The one or more external electronic devices receiving the request can perform at least a portion of the requested function or service, or additional functions or services related to the request, and transmit the result of the performance to electronic device 601. Electronic device 601 can provide the result as at least a part of its response to the request, with or without further processing. For this purpose, cloud computing, distributed computing, or client-server computing technologies can be used, for example.

[0097] Figure 6 The electronic device 601 may correspond to or be implemented as the UE 105 or network node (gNB 110) described in the foregoing figures. (See reference...) Figure 1-5 The described method steps, such as receiving configuration information, determining suitability, sending suitability information, and activating or reactivating the reporting function, can be executed by the processor 620 of the electronic device 601 based on instructions stored in the memory 630. The communication module 690 and the antenna module 697 can perform wireless transmission and reception operations associated with the suitability reporting process between the UE 105 and the gNB 110.

[0098] The logic for performing suitability determination and report activation can be embodied in dedicated circuitry or firmware within processor 620, or distributed between processor 620 and communication module 690. When processor 620 executes program 640 stored in memory 630, device 601 can operate as a UE or network node according to stored configuration and control instructions. Therefore, Figure 6 Provides the ability to perform combination Figure 1-5 The hardware representation of the devices and components of the described method.

[0099] Embodiments of the subject matter and operation described in this specification can be implemented in digital electronic circuits, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or combinations thereof. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs (i.e., one or more modules of computer program instructions) encoded on a computer storage medium for execution by a data processing device or for controlling the operation of a data processing device. Alternatively or additionally, the program instructions can be encoded on artificially generated propagating signals, such as machine-generated electrical, optical, or electromagnetic signals, which are generated to encode information for transmission to a suitable receiver device for execution by the data processing device. The computer storage medium can be or is included in a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof. Furthermore, although the computer storage medium is not a propagating signal, it can be a source or destination of computer program instructions encoded in an artificially generated propagating signal. The computer storage medium can also be or be included in one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices). Furthermore, the operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.

[0100] While this specification may contain numerous specific implementation details, these details should not be construed as limiting the scope of any claimed subject matter, but rather as descriptions of features specific to particular embodiments. Certain features described in the context of individual embodiments in this specification may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as functioning in certain combinations and even initially claimed in this way, in some cases one or more features from the claimed combination may be removed from the combination, and the claimed combination may be for sub-combinations or variations thereof.

[0101] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order shown or sequentially, or to perform all the shown operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of the various system components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0102] Therefore, specific embodiments of the subject matter have been described herein. Other embodiments are within the scope of the following claims. In some cases, the actions set forth in the claims may be performed in a different order and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific order or sequential sequence shown to achieve the desired result. In some embodiments, multitasking and parallel processing may be advantageous.

[0103] As those skilled in the art will recognize, the innovative concepts described herein can be modified and varied across a wide range of applications. Therefore, the scope of the claimed subject matter should not be limited to any of the specific exemplary teachings discussed above, but is defined by the appended claims.

Claims

1. A method for configuring an applicability report between a network node and a user equipment (UE), the method comprising: The network node sends configuration information to the UE, which includes one or more configurations associated with a full configuration for inference and a partial configuration for applicability reporting; Determine at the UE whether the configuration is suitable for inference; and The UE reports applicability information indicating one or more applicable configurations to the network node.

2. The method of claim 1, wherein, The full configuration and the partial configuration are represented by a single configuration format, which includes parameters for inference and applicability reporting.

3. The method of claim 1, wherein, The configuration information includes a first configuration format for the full configuration and a second configuration format for the partial configuration, wherein the first configuration format and the second configuration format are different from each other.

4. The method of claim 3, wherein, The UE report provides information on the applicability of the full configuration and the partial configuration.

5. The method of claim 3, wherein, The UE reports applicability information for the full configuration or the partial configuration.

6. The method of claim 4, wherein, When an applicability report for the full configuration is allowed, the UE receives a network NW indication.

7. The method of claim 4, wherein, When an applicability report for the aforementioned configuration is permitted, the UE receives a network NW indication.

8. The method of claim 1, wherein, The UE activates the reporting function immediately upon receiving the configuration information corresponding to the partial configuration, and activates the reporting function corresponding to the full configuration only after indicating applicability to the network node.

9. The method of claim 1, further comprising: In response to a reactivation instruction received from the network node, the previously deactivated configuration is reactivated.

10. The method of claim 1, wherein, The UE determines the change in applicability based on one or more performance monitoring events that meet a threshold condition.

11. The method of claim 10, wherein, The performance monitoring events include at least one of the following: beam prediction accuracy value is below a threshold, received signal strength value is below a threshold, or the counter value indicating consecutive failures exceeds a threshold number.

12. An electronic device configured for applicability reporting, comprising: A transceiver is configured to send and receive wireless signals with network nodes; and A controller, operably connected to the transceiver and configured to: Receive configuration information from the network node, the configuration information including one or more configuration formats associated with a full configuration for inference and a partial configuration for applicability reporting; Based on the configuration information, determine whether an applicability report is required; Send applicability information indicating one or more applicable configurations to the network node; and When the applicability of the full configuration is indicated, the reporting function associated with the full configuration is activated.

13. The electronic device of claim 12, wherein, The full configuration and the partial configuration are represented by a single configuration format that includes parameters for inference and applicability reporting.

14. The electronic device of claim 12, wherein, The configuration information includes a first configuration format for the full configuration and a second configuration format for the partial configuration, wherein the first configuration format and the second configuration format are different from each other.

15. The electronic device of claim 14, wherein, The second configuration format includes an identifier associated with the first configuration format, and the controller determines applicability based on the association between the identifier and the first configuration format.

16. The electronic device of claim 12, wherein, The controller activates the reporting function immediately upon receiving the configuration information corresponding to the partial configuration, and activates the reporting function corresponding to the full configuration only after indicating applicability to the network node.

17. The electronic device of claim 12, wherein, The controller is also configured to reactivate a previously deactivated configuration in response to a reactivation instruction received from the network node.

18. The electronic device of claim 12, wherein, The controller determines changes in applicability based on one or more performance monitoring events that meet threshold conditions.

19. A non-transitory computer-readable medium storing instructions, said instructions, when executed by a processor of a user equipment (UE), causing the processor to perform a method for configuring an suitability report, said method comprising: The UE sends applicability information indicating one or more applicable configurations to the network node; At the UE, configuration information is received from the network node, the configuration information including one or more configuration formats associated with a full configuration for inference and a partial configuration for applicability reporting; Based on the configuration information, determine whether an applicability report is required; and When the applicability of the full configuration is indicated, the reporting function associated with the full configuration is activated.

20. The non-transitory computer-readable medium of claim 19, wherein, The full configuration and the partial configuration are represented by a single configuration format, which includes parameters for inference and applicability reporting.

Images